Loop "missing data: glucose data not available" but dexcom working #837
Comments
|
This happened again last night. Issue report uploaded in this gist: https://gist.github.com/mitchellhenke/089054cf1f92eed5878ba1a102723ac6 As before, Apple Health doesn't have glucose data for the time period. This time starting around 2am: |
|
It happened to me too two times in 5 days |
Kdisimone
changed the title
|
This is not happening to me. It has in the past. I’ve had a lot of Signal loss issues and other Bluetooth issues with Dexcom. My chats with the reps have resulted in many recommendations to reboot my iPhone nightly. I’m not great about doing it nightly, but I do it about once a day. I think that helps a lot. This seems to be an issue with Dexcom not connecting to the Internet. At night, I run my Nightscout app, my Garmin app, Dexcom G5 app, and Loop. I don’t let my phone automatically update anything. Those kinds of things keep me connected pretty well. And I run everything on WiFi. |
|
We have the 2 am problem (loop red, glucose data not available) but checking HK records, there is no gap visible which is weird. We are following FB troubleshooting steps and will report back. Starting by deleting server from loop. |
|
Deleting dex server from Loop did not work. One again a 2 am drop that persisted until wake-up. Interestingly no NS data uploaded during that period. Need to understand what that could indicate - more of an iPhone issue than a Loop issue? which is consistent with the idea that it's contemporaneous with iOS12. HK BG records are weird - Dex is the source but then Loop records twice, and then stops and there is no record of either app recording BGs - and this begins around the time that loop seems to have turned red (Loop is the blue icon). I disabled that, but it makes me wonder. Only way to get back to green was to add back Dex server, and have it go to the cloud. During the day cloud icon is gone. This is iOS 12 with a 1.5.7 modified version. We will upgrade to 1.9.3 over the weekend but this is definitely a new problem that seems contemporaneous with iOS12, so while it will be nice if 1.9.3 solves it, it's not clear why that would be the case, unless it's something very subtle about the interaction between the new rileylink frameworks in 1.9.x, the heartbeat, the sniffing of the transmitter signal, and iOS12. Will try turning off WiFi tonight. |
|
@jeremybarnum you need to check with @Kdisimone or @ps2 , but if I look at your issue report I think loop had crashed until moments before you sent the report (ie you interacted wtih the app). The launch date of the device manager is 26 seconds before the report date. That indicates that after a crash it didnt restart, which used to be a problem that @ps2 had fixed but i cant remeber if that was in 1.5.7 or after (I fought it for a long time but after he made some adjustments to how data gets saved to HK I think all was good). I believe it restarts based on the transmitter heartbeart, so if the dex app is crashing there is nothing to restart loop with (again check with the experts). If NS didnt have data then I assume share didnt have data so likely its a dex app issue, but that is just my opinion. We just upgraded my sons phone to ios 12 - first night the dex app crapped out after the ios 12 upgrade. Last few nights he takes the password off and leave the dex app up on the screen all night - rock solid last few nights - but that is just a few data points. check the analytics logs to see if you can see any crashes around that 2 am timeframe - dex app, loop, watch etc. |
|
Thanks @kenstack, very helpful, will do. I also just noticed that even though I thought I had gotten rid of all the old apps that might be conflicting (a thing that I believe was also fixed in 1.9.x ) there was one. So we've deleted that. |
|
I got same issue. I am using miaomiao and libre with spike, loop version 1.9.3 katie. Ios 12.0.1 Get missing data but after I open loop it comes straight on. Been doing I think everything now but no luck. Just wondering to clear my phone and start from scrateches. |
|
FWIW we tried removing screen lock and having the Dexcom app up and that worked last night. |
|
Also, FWIW, (again, I don’t have the issue of Loop turning red), I
typically use my iPhone 7 at my bedside to alert me for hypo and
hyperglycemia at night. I leave my phone on the Nightscout app either
Nightscout X or the original Nightscout app), with the “screen lock
override” on (so my phone screen doesn’t lock).
On Wed, Oct 24, 2018 at 16:47 jeremybarnum ***@***.***> wrote:
FWIW we tried removing screen lock and having the Dexcom app up and that
worked last night.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#837 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIjz3Ix7RW6xGjJ9flhZzKipdAyqzB6lks5uoNHWgaJpZM4Xi08b>
.
--
Sent from Gmail Mobile Please excuse typos & brevity.
|
|
Just to update. I also kept phone unlocked over night and loop worked great :) |
|
Which phone do you have? I have an iphone se |
|
I have Iphone 5s. Unfortunatelly daughter is in school and we lost already connection as phone was locked all the time |
|
Probably worth having everyone clarify their platforms and versions to clarify whether this problem exists in 1.9.3 or is fixed? @Piotras625 post would suggest the problem still exists but if so why is everyone not seeing it, and @kenstack seems to think some recent improvements should have fixed it. Good news is leaving Dex open and phone unlocked seems to do the trick but that's not a proper solution. We are on iPhone SE with iOS12. UPDATE: I believe, but for reasons of branch management sloppiness I can't be totally sure, that the installed version is based on 1.5.2, with Loopkit 1.5.4 and rileylink_ios 1.2.2. Here it is - branch "1.5.2-x15-and-absorb-fix". Our version has been the same for months, but the problem arose after iOS12 update, although I can't definitely prove the causality there. We will probably update to 1.9.3 this weekend and we can't afford to try to reproduce tonight so I guess if the problem is gone in latest version, who cares. I'll report back. |
|
@jeremybarnum I think it would also be useful to make sure people clarify if they were getting dexcom bg data and the loop app didn't restart. For many people I think you will find the core issue is the dex app simply not restarting / working. If the dex app isnt getting data, likely that means there there is no heartbeat for Loop to wake up too. If there is dex data in someone's nightscout site and loop doesnt wake up, then that is a different story. Also, be careful to make sure you dont get fooled with backfill on dex data - if the dex app is down and then you restart it and it backfills, then that is not an issue with loop itself. Again I am not saying there isnt an issue with loop - but having been thru this before the first key is to make sure the dexcom app is live the whole time loop is down. One other point - even through all of the earlier issues we had, very very few people saw the issue even though we were running the exact same code. The dex app data issue seems to be resource related, so depending on how someone uses the phone, and phone resources itself, what else is running , etc. One repeatable example from this summer was my son playing fortnight on his Iphone X - the dex app would often stop working even during the day. also apple carplay - we sometimes get intermittent data when he gets into his car and uses maps and music. But, these are one off experiences fwiw. |
|
@mitchellhenke Please edit your original post to indicate which Loop version and CGM source you're using. i.e. Dexcom G6 with Dexcom app, or Spike, etc. In the future, an issue report is usually very helpful. |
|
@ps2 I wasn't able to grab an issue report the first time, but I linked a gist above when it happened again: https://gist.github.com/mitchellhenke/089054cf1f92eed5878ba1a102723ac6 |
|
Hi guys. I just done everything from begining, so deleted my phone and started new one. Installed only Spike and Loop. All setup according to instruction. I get green loop for about 2 hours and if phone is not used than I get red circle and message that CGM data is missing. I definately got good password and login in the integration dexcom server as got BG for some time. Leave phone unlocked is solving the problem. When loop stops getting data from spike I still got NS running properly and can see BG on the followers devices. Could be situation that Spike is susspending internal server when screen is locked but keep sending data to NS? |
|
Piotras625 your issue is a different issue than the one being discussed in this thread. it sounds like a Spike integration issue specifically. Quite possible that there's an issue with spike and ios. A long time ago, there was a version of nightscoutshareserver that required the phone to remain unlocked to function too. @dabear might know more about that. Perhaps try sending him a message in gitter. |
|
Ok thanks. At the moment I am trying to set up master bersion with nightscoutshareserver and see if that works. I will also build 1.9.3- katie version on different device to see if problem will continue |
|
I think I’m having a similar issue again, this time in the daytime. I’m working in the ICU today, so I don’t have time to be attentive to my phone. I’ve had a lot of red loops. I captured an issue report really quickly earlier, and emailed it to myself. I’m on G5. IOS 12.0.1. iPhone 7. Loop 1.9.1-KATIE. Dexcom has BGs but seemed not to be uploading them properly. Loop had lost BGs. I’ll try to upload my issue report and Loop screenshot. I don’t have Amplitude set up. When I tapped the dotted triangle in Dexcom, and BGs resumed uploading, Loop was able to get going again. I’m low at this point, as Loop wasn’t able to head off the low (don’t worry; I’m eating lunch). ADDENDUM: I don’t know how to upload on my phone. I’ll have to do that from my Mac tonight. |
|
Happened again last night on Loop 1.9.3-dev Issue report: https://gist.github.com/mitchellhenke/0ac6b7481663009befaebfb135164f29 I hadn't force closed the app or anything. |
|
@mitchellhenke was the dex app getting data the whole time ? or was the dex app missing data for some reason before you noticed loop not working. Thanks! |
|
@kenstack Dex was getting data the whole time, but Apple Health stopped receiving data Dexcom screenshot
Apple Health screenshot
|
|
We have had two clean nights post upgrading to dm61-IRC, which is based on 1.9.3 dev. Interesting and concerning that you have the problem on that branch. We'll keep a lookout. We did have a sticky problem on the first night with pump comms which wasn't solved with usual tuning, button press, loop and phone restart, etc, but was solved with a RL power cycle. Seems intuitive that RL power cycle is a good idea post upgrade, but that's pure guesswork. |
|
@mitchellhenke I wonder why the dexcom app - if it was running - didnt write the bg data 3 hours later to HK. @Kdisimone may have more insight here. You have data on the display - could it be backfill ? Just wondering. Thanks for the posts |
|
correction - we are in fact seeing the same problem despite being on 1.9.3 dev. While I can't be totally sure, it might actually be the case that it's happened every night. Tonight we are going back to unlocked screen with Dexcom app up and running. Unfortunately the issue report was captured as a screen shot. Here are screenshots of the error and also the analytics file showing a crash in the middle of the night. I am told the dex app was in fact running at the time but I can't be totally sure of that. We'll try to improve error capture/reporting but we can't afford to try to reproduce it tonight. |
|
I have had the same happen to me using Spike. Seems like I need to delete my Spike account from Loop and restart the app to get it working again. Sometimes there is a long delay too before it starts picking up readings again. Next time I see it I will create an issue report too. |
|
We were planning to remove screen lock last night but didn't do it, and therefore reproduced the error again. Seems like it's pretty much guaranteed to happen in the middle of the night. Enclosed are full issue report and also analytics log. To be clear, this is dev branch of 1.9.3, a slightly modified version of dm61's IRC branch, running on a fully updated iPhone SE, with only dex and loop running overnight. No Spike integration. And it seems like dex was running - or at least, that dex succesfully rebooted itself. I very seriously doubt that my modifications have anything to do with this problem, but if it's not that, and only some people are having it, then what is it? (my modifications are the 515 fix to rileylink_ios and the #577 change to loopkit - both of which I've used for some time with no issues). Any suggestions welcome. |
|
iOS 12.1.2 This issue happens at least once every other week and only at night. iPhone plugged in charging and not charging. I have a video of my phone screen upon waking I can upload if it will help. Updates: Added screenshots. When I received the "Missing Data" error Loop will return green a few moments later. |
|
Has anyone found a solution to this issue? I had tried keeping the phone without auto lock at night. It worked for a little while but has recently started with more frequency again. iOS 12.1.2 TIA. |
* As described in LoopKit/Loop#837 * Update dependency revisions
|
This fix is in Loop dev now. Please test! |
|
Nice! |
|
Thank you so much for fixing this issue that I'm assuming wasn't easy to track down. I haven't had the issue since changing phones, but I've updated my app to include the fix and will share any issues if I come across them. |
|
Same here - no recurrence on iPhone8 but will try to test on old offending SE with a test rig. Thanks @ps2. |
|
Ran into the "Missing Data: Glucose Data not Available" on Loop 1.9.4 Dev at 3am last night. iOS 12.1.3 Loop Report 2019-01-15 03_07_38-08_00.zip
|
|
@human911 did that happen with or without last week's fix? |
|
@human911 your case looks a bit different. In your case the dexcom truly is out (timestamp and BG is old). The issue before was that loop had failed despite dexcom picking back up. I think you have a dexcom issue. Try the usual dexcom tricks. Delete unused transmitter IDs from BT. Close unused apps. Keep apps updated. Restart phone before bed (anecdotal). |
|
@human911 Your issue report shows 40k pump events in Loop's db, likely caused by a bug on dev that was fixed here: 1746a75. Have you run loop with this fix? If not, please update to a recent version of dev, run loop for a while until you see a valid upload to NS, and then check your issue report (or attach another copy here for me to review). I am hoping that your events will get cleared out. I'm not sure this is related to your crash (@Kdisimone, he does have a crash), but having those events seems to indicate that maybe you're not running the updated dev. |
|
Hey Everyone, I did not uninstall Loop 1.9.3 prior to building Loop Dev 1.9.4 with the fix last night. Loop Dev has also crashed a few times... the screen just freezes. Let me know if you need another other info. I will try removing and rebuilding Loop Dev tonight.
|
|
@human911, The ips (crash report) file you attached is from 6:21am, and it shows that Loop had been running for three hours (since 3:06 your time). Do you have a crash from 3am? |
|
@ps2 I just had it crash again at 10:30am pst Thanks for the help and feedback everyone. |
|
Could you symbolicate those crashes? |
|
Experiencing this issue again in 2.1.0 (automatic bolus). My phone is an iPhone se with 13.3.1. Now I deleted all BG entries from Loop in health, denied Dexcom to upload BG to Health and re-enabled, deleted its entries, deleted in Mlab part of my data to empty space in NS. Loop Report 2020-03-01 18:24:26+01:00.txt Managing it using BG via Dexcom share atm. This is the error in loop:
EDIT: After 2 or 3 rebuild I have it working again...Here is the log right now Loop Report 2020-03-01 19:06:11+01:00.txt Will check in the next days if it Will appear again |
|
This morning I had it again |
|
And this morning again. Could be a iPhone SE issue? I am the lonely one having this at this time |
|
@francesc0-cgm I think there’s some correlation. I experienced it on my SE, but have not since using a different phone (XR) |
Ok thank you. Will try to change phone |
|
@francesc0-cgm We have this issue as well and we are not using an SE. The BG just goes missing but numbers still show in Dexcom app. I usually close apps, restart phone and then enter the Dexcom number into Apple Health which Loop then pulls in and that usually fixes it. The next update typically shows up in Loop. |
|
I’m having similar issues with my Dexcom G6. Loop is "missing data: glucose data not available" but dexcom working just fine. Attached are screenshots. (I do own a 2nd RileyLink as emergency backup)
|
|
I frequently get the "missing data: glucose data not available" while Dexcom still shows a value. I recently started getting it more often, and I can't help but think it was related to my recent "upgrade" from a G5 to a G6. I use an iPhone 8. Good news is that turning bluetooth on and off from the iPhone settings seems to fix it, but it does cause some trouble with my basal rates. |
Discussed a little bit here where Loop shows
Missing data: Glucose data not available, though the Dexcom app shows no gaps and appears to otherwise be functioning fine.It is mentioned by @Kdisimone in the thread that this may be due to an iOS resource issue, but I was hoping there would be a way to make Loop reconnect? Someone else suggested that it's due to Apple Health lagging, but it never seemed to catch up in my case.
Looking back, Apple Health has no Glucose measurements from Loop during that time, but Dexcom shows no interruptions. I can get back into a working Loop state when it happens by toggling Bluetooth on and off.
I have set up Amplitude so I'll have that if it happens again in the future, but is there anything else I could do to help narrow down where the issue may be?
I’m using Dexcom G5 and Dexcom app and have seen the issue on Loop 1.9.2.
The text was updated successfully, but these errors were encountered: