It's great having my CGM in the Cloud and being able to share that blood sugar data with others, and giving myself more access to viewing my data when and where I want in a form that helps me.
First impressions were strongly positive, and I stand by all of that.
Additional observations, from my first six weeks of using my "early Christmas gift" strapped to my waist and wrist:
- The alerts annoy me at 80 and 180. I'd prefer 70 and 200. -- (UPDATE: I have learned, thanks to Sara, that a Pebble update allows me to customize alert ranges -- so that's awesome!!!)
- Most of the time, I keep my Pebble on "Quiet Mike" mode which uses a CGM Sleep Mode watchface created by a fellow Nightscouter. But when not quiet, I've seen the tighter range makes me work harder to stay in that range and have tighter control just to avoid the annoying vibrations. Interesting...
- Recent trip to California was a big test drive for this, but problems with battery life and a charging cable mishap made it so it didn't charge one night and the phone battery died. And that caused my wife at home not be tuned in to a 40mg/dL that hovered in the early morning for a couple hours. Luckily, I woke up and treated.
- It has given her more piece of mind when we're both at work and apart, and if I'm caught up and not answering the phone or email, she knows it's not BG-related.
- Nightscout is totally a conversation starter, especially when you're wearing the Pebble watch and you tend to be checking it regularly...
- I wore this to a recent endo appointment and explained Nightscout to him, and Dr. Health Bug
- My endo also had some sage advice that I've heard before: "It's very cool, but don't lose sight of the fact it's just a tool. In reality, it comes down to you managing the way you want to."
Nightscout is awesome... when it works.
Remember, before you take all of this as gospel applying to anyone other than me, factor in this simple truth: I'm one of those guys who doesn't like connection cables, and grumbles when needing to do anything from reprogramming the microwave clock, re-connecting the wireless printer, or hooking up a new TV or DVR. I just don't like those things, and so that paints my perception of CGM in the Cloud.
community support and setup guides, I've found the worry and hassle after it's all initially set up is the real culprit.
Yes, despite all the love I've had for Nightscout in these first couple months, I have anxiously been waiting for the other shoe to drop. And now, it finally has.
Truly, I feel like I am always on the hunt for a battery charger and I'm being held hostage by the fear that some little cable will become disconnected or even might break my very important Dexcom CGM. And after the first month of this, my fears have been realized: It seems my Dexcom G4 receiver is compromised.
No, I can't 100% blame this on Nightscout. After all, my G4 receiver is 16 months old (for those wondering, that's 4 months longer than the one-year warranty it comes with).
A little over a week ago, my system stopped connecting to the cloud and sending my Dexcom data there. For those who care, the message I received was "CGM Connection Error."
Now, there's a number of things that could mean -- and you pretty much have to run through the list to figure out what it is and isn't. I tried all the simple things first -- making sure my CGM was working, that my connection cable was attached, that there wasn't a data or WiFi problem or something going on with the uploader phone. All was OK on those. Yes, my connection cable was charging the G4 receiver from the uploader phone. I did a hard reset, and changed my sensor, and did all that might have caused the issue. Nothing changed. I was worried the phone port might have been damaged, but it was also charging.
Hmmm, mysteries of the Nightscout Rig... what to do?!
|My Nightscout Rig, complete with Tallygear case.|
So, I tried connecting the G4 receiver to my laptop for Dexcom Studio. And it wouldn't recognize the receiver. Yes, I've been using a workaround to make it work and that's not been an issue before.
This made me all think it's an issue with my G4 receiver, possibly the port being damaged (which is one of the big worries Nightscout warns you about going in).
I have a backup receiver ready to get started, but this whole experience has made me a little more cautious and concerned. My original receiver appears to still be working for the most part, it just won't connect to Studio or Nightscout. Now: Do I want to connect my only backup to Nightscout, risking the same port problems a month or two later without having any backup on hand?
I'm just not sure.
And yes, then there's the battery issues. Sure, I've followed the community guidance about battery-saving tips and lifehacks. But especially when I'm out traveling, I have found it's limiting to have to rely on this at key times of the day and night without any backup battery. Or without having a charger that isn't an electrical outlet. That cut me down recently when traveling, where I couldn't find an outlet at the airport or bar and ended up having to turn off my Nightscout phone thanks to a dead battery. I have found a workaround, buying a portable charger that may help on that front. We'll see what effect it has.
Nightscout is cool, and I do believe that it's saved me from a few scary hypos and provided our family an extra level of security when I'm traveling or flying solo. But again: Does that outweigh the hassles? Especially when I've invested so much $ into this?
These are simple realities I knew would come up, eventually. The drawback of any Do-It-Yourself project or piece of technology is that it might require more fiddling and reworking than, say, a polished off-the-shelf product or system sold by a company. I knew that going in, and I was just hoping it wouldn't happen too much so it got to the point of making me question if Nightscout is worth it.
I'm still making up my mind on that.
To be continued...