I haven’t used share because my wife has a flip phone that is never turned on unless she wants to call her brothers. I just installed on my Garmin bicycle computer an app that uses Share to display BG and a trend arrow. This is something I wanted for a long time.
I was able to get everything working and the BG display on my 3 cycling profiles OK. I did a 30 minute ride after dinner hoping to see a drop. I did, but there is a considerable delay from my iPhone/ Apple Watch display and the Garmin. Is this true for family members who use Share for their diabetic children and spouses.
Because I did this stationary cycling I wasn’t overly concerned. My BG was sitting at 94mg/dl steady on both watch and Garmin, when it suddenly dropped to 74mg/dl on watch while still at 94 on the Garmin for some 5 minutes. This could be dangerous out on the road. And it could lead to trouble with a child, if the parent didn’t catch a faster drop.
I think 5 minutes is as good as it gets. I used to have software that could see all the Dexcom data points which look a little more like a scatter graph before the Dexcom algorithm flattens out the data. I believe that is why we only get 1 dot on our Dexcom CGM receivers or compatible phones every 5 minutes. You can use the relatively new urgent low soon setting in the Dexcom CGM app that gives you a 15-20 minute predictive low warning to help avoid the dangerous situation you fear.
My wife and I both have iPhone 7+. So of course I share to her phone. I is more then normal she’ll be at work and I’m home working in the yard that she calls me to tell me I’m starting to go low, or she’ll call and ask me what I just ate when I go high.
I share with sugarmate, which sends to my Apple Watch.
Usually they are the same value, but when it isn’t updated it says “old” next to the reading
It happens when I go through a tunnel or a place that has bad cell reception.
Yogi Berra once answered “What time is it?” with “You mean right now?”
I think in the future we will see shorter time-delay sharing of data without going through the Dexcom mothership. If this isn’t done by Dexcom it’ll be done by a competitor’s CGM. Ideally there would be an open standard for real-time CGM data sharing between nearby (bluetooth? Near field?) devices.
FWIW, another data point: I use several apps/widgets that get data from Share: SugarmateGlance on my laptop and iPhone, and the clockface I use on my Versa 2 Fitbit. Occasionally I see a little latency, but never more than ~20 seconds or so on all those devices. Where I DO see longer lag times is on the Share app itself. Sometimes several minutes or more. Don’t know why that should be, but I never have that kind of delay on the other widgets.
To @CJ114, @John70@Timothy@Tim12 and @DrBB I thank you all for sharing your knowledge. I was more wondering than concerned for myself. Spending a life using measuring equipment that can be false (not related to diabetes) I always take data with a grain of salt, especially when dealing with wireless and distant servers.
Yes, and having a specific number value tends to imply a precision the device may not actually possess. In T1 discussions we all the time see people using fingerstick values to judge the precision of their CGM, when the MOE for finger sticks is way bigger than people think. “It says 119 right here!” Sure, but I’ve seen 5-15 point spreads between two finger sticks taken at the same time, or in close succession. I sometimes think the old reagent strips we had back before meters, where you compare the color to the patches on the tube might have been more “accurate,” in the sense that it didn’t actually give the impression of being precise to a single number. Your BODY isn’t that precise.
And split 'em in half the long way to get two for the price of one. I’m not eager to go back either (you can still get 'em, for veterinary usage). But I do try to keep in mind that the numbers I see on my CGM and CountourNext contain a pretty big fudge factor.
A man with one clock thinks he knows the time, but doesn’t know it’s slow (or fast). A man with two clocks knows one of them is off, but not which. I beleive a minimum of three clocks was normal on sailing ships back in the day. Just sayin’…
Yeah, John70, that is why I took the Share feature OFF my husband’s phone. Having the CGM beep at me is bad enough without him harping at me to eat something or to take more insulin, too.
My son shares with me - I do not see this kind of delay at all. Maybe a minute lag, but that may be manual (when I’m looking v when he is looking) not technical.