[Dark epic film-teaser voice] And so it begins. In a world…
I went to do my first sensor-restart yesterday after getting a new transmitter last week, and all the ill-omens and dark murmurings you’ve heard are true. It blocks you from doing the forget-code/restore-code restart method. About half an hour into the warm-up it threw up a No Restart Allowed message. I did try the more elaborate method where you have to “forget this device” in the Bluetooth preferences (IOS) but that just caused me a lot of trouble, either b/c the instructions I had were inadequate or I did something wrong (pretty sure it was the former) and I finally broke down and put in a new sensor.
So dang. I’m not concerned about the expense so much as the fact that I’ve been having difficulty finding trouble-free insertion spots and I hate having to deal with the the initial 24-hour wobbles when I’ve got a good pain-free location and stable sensor going.
Also: what about pre-soaking, is that going to be blocked too? Because supposedly the new algorithm is validating on the basis of “insertion trauma,” i.e., if your data looks too smooth it assumes you’re restarting an existing sensor. And the whole point of pre-soak is that you initiate the session after the sensor has been in there long enough to stabilize. So that could be a really annoying downside. If an actual new sensor gets rejected on this basis, will Dexcom replace it? Do they even know people are doing this in order to get better first-day results?
And yeah, xDrip, but I have the latest version and couldn’t seem to get it to connect when I tried it at the end of my last transmitter.
Has anyone found a good hack for this?