Yep, risen from the ghosts. There were a couple of Tims who posted a lot there, but I don’t recall the reputations so I won’t mention names. A few people from those days are still on my Xmas card list …
edward at paleo dot org
Yep, risen from the ghosts. There were a couple of Tims who posted a lot there, but I don’t recall the reputations so I won’t mention names. A few people from those days are still on my Xmas card list …
edward at paleo dot org
Edward, if it helps jog your memory, I was at Caltech but I wasn’t Carl Lydick :-).
Keep in mind the unused transmitters are still draining battery (slowly), so by the time you get to them may have limited days of use.
The G4 transmitters were shipped with packing that reduced battery drain, but not G5, G6.
Ah, Tim Shoppa. Definitely not Carl! (Who died way back then anyway.)
I confess to having some archives from the newsgroup …
Edward
Thanks - Is Xdrip available for iOS? I’m not using Android.
I know it’s also possible with Spike, but I’ve had a hard time locating it recently.
There’s also a way to build an app just to reset the clock, but it’s rather cumbersome. I believe @mohe0001 already posted the link.
@Paytone You have to download Spike on the computer and while there are detailed instructions, it’s not always completely clear. But when you download you connect your phone to the computer and it puts the link on your phone. I just did it over the weekend.
But you can ask for any help at Spike’s facebook page
Now I see on my spike ap where I can reset transmitters, but I haven’t done it yet, if I do, it will be within a few days as my transmitter is running past it’s allowable use time.
But I am at a quandary because I have 2 new transmitters here and the extra was put in by my DE, but she loves to look at my Clarity reports and I think if I use Spike it might mess up the Clarity report so…not completely sure what I am going to do yet.
I love to be able to restart my sensors.
I believe on the xdrip facebook page someone has said xdrip will work but only works with nightscout on an iphone?
Does anyone know if you use xdrip can you still get clarity reports or something similar?
Thanks @Marie20. I’ll try this.
I reset my transmitter once before spike disappeared for a period. It does mess up Clarity, but I only think it effects the graphs. I recall the underlying data remains intact for purposes like TIR, etc. but I’m not 100% sure. Anyone else have experience with this?
You wanna talk to @BradP
He was here for a quick minute. I know hes using iPhone because he’s Omni Looping. I think he has XDrip. And, we was complaining about Clarity account when Dexcom was working on their servers. So, I think hes the guy to ask.
Good work, Marie20. I’l post the Spike method in the summary section. Your the only one who has done that, I think.
Excellent notes! Thank you for posting!!
I am really having trouble keeping all this straight, @Trying. I’m gonna wait for @BradP to respond again. But, I think my next moves are to delete Loop, reinstall Loop in combination with Xdrip and attempt some sensor restarts. If you want me to post u as a reference under a specific transmitter type or note that you have verified a particular restart method worked/didn’t work, just let me know. I’m scared I’m gonna break something. I am also on my last sensor so it might be a while before I’m setup.
Unfortunately, I’ve yet to reset a transmitter or restart a sensor! My G6 sensors don’t last past 10 days, and usually fewer than 10 days. I just put a new transmitter on and didn’t attempt to reset since Dexcom will not replace failed sensors if they know the transmitter is past 90 days. I’m not sure whether they can tell age based on the transmitter id, but I think they can
Guys, you’ll want to bookmark this web site. Here’s the update for restarts: Restarting Dexcom G6 sensors – Updated – See My CGM . I have stockpile of sensors so right now I’m not restarting since looping. Just not worth the risk. Data for me starts to go wonky anywhere from day 8 to 10 anyway, even with skintac and the overtapes.
I think (hope) she merges the docs at some point. But for now, the 8/1 link has info on different transmitters.
What’s your source for it being a federal crime? The DMCA has an exemption for personal medical devices. As long as someone doesn’t sell a product to hack devices, it’s perfectly legal for an individual to do so.
The transmitter info is good, but those are the same restart instructions I’ve seen elsewhere, and they don’t work, at least not for me with an 8G transmitter and the iPhone app. The problem is here:
Forget/delete Dexcom from Bluetooth list in phone’s settings. iPhone users, tap the little “i” next to every Dexcom ID in your bluetooth list and forget the pairing(s).
“Stop Sensor”, “New Sensor”, enter code, “Start Sensor”
Once you do step 2, you can’t do step 3. The app just gives you a “not connected to transmitter” message and those sensor options don’t appear. To get them back you have to re-pair, at which point you’re back where you started.
I think this looks like app behavior. It’s just not letting you do anything until it sees a connection to the transmitter. Dunno if the Android version of the app behaves the same way, but this seems like a pretty basic programming decision on the app side.
I need to replace my 81 transmitter in the next few days with the 8g. I’ll try a restart and see what happens, I’m most likely going to end up exactly like you with no option to restart it.
I think Dexcom isn’t going to sell as many more sensors as they think by making it impossible to extend sensors, because there will be folks who used to be able to do that who will sometimes have sensors not making it the full 10 days that will now demand a replacement, even if the sensor fails just an hour shy of 10 days. AAMOF, I would think clever people could make the sensor fail just before 10 days. What do you think?
Depends on if they keep screwing around with the adhesive formula. My last few boxes of sensors have not needed skin tac or over tape to get the full 10 days of the session. I agree @Dave44, this new no restart implementation will probably bite them in the a$$