Closed denvergail closed 9 years ago
The low alarm is triggered when the forecasted value is below approximately 72, seems like you would have hit that but maybe you just missed it
Silly question... But you did push the speaker button when starting the session? If you don't it won't audibly sound on some devices.
Overnight last night, BG was <80 for an extended period. Rose to over 80, then back down again for a few hours. The low alarm never went off. I asked someone else to verify on their computer if the alarm was working for them viewing my site. It was not.
I was able to look at our computer and verified that the alarm was not working, even though the alarm was enabled and had been open to our site all night.
[image: screen shot 2014-11-08 at 8 29 44 am] https://cloud.githubusercontent.com/assets/8145371/4965905/952e038a-679d-11e4-9652-be635eb274ac.png [image: screen shot 2014-11-08 at 8 29 50 am] https://cloud.githubusercontent.com/assets/8145371/4965904/9528ddba-679d-11e4-9bbd-bd27833f5238.png
— Reply to this email directly or view it on GitHub https://github.com/nightscout/cgm-remote-monitor/issues/233.
It works otherwise.
Jason C stated that the alarm doesn’t actually trigger until somewhere closer to 72. We found that on some browsers it is closer to 64.
On Nov 10, 2014, at 7:49 AM, Rob Strickland notifications@github.com wrote:
Silly question... But you did push the speaker button when starting the session? If you don't it won't audibly sound on some devices.
- Rob On Nov 8, 2014 5:19 PM, "denvergail" notifications@github.com wrote:
Overnight last night, BG was <80 for an extended period. Rose to over 80, then back down again for a few hours. The low alarm never went off. I asked someone else to verify on their computer if the alarm was working for them viewing my site. It was not.
I was able to look at our computer and verified that the alarm was not working, even though the alarm was enabled and had been open to our site all night.
[image: screen shot 2014-11-08 at 8 29 44 am] https://cloud.githubusercontent.com/assets/8145371/4965905/952e038a-679d-11e4-9652-be635eb274ac.png [image: screen shot 2014-11-08 at 8 29 50 am] https://cloud.githubusercontent.com/assets/8145371/4965904/9528ddba-679d-11e4-9bbd-bd27833f5238.png
— Reply to this email directly or view it on GitHub https://github.com/nightscout/cgm-remote-monitor/issues/233.
— Reply to this email directly or view it on GitHub https://github.com/nightscout/cgm-remote-monitor/issues/233#issuecomment-62393800.
@jasoncalabrese Here are some comments I made to the Support Team message thread on FB re: low / high alerts on website vs. Pebble vs. Dex. Hope they help in some way... but maybe there's nothing new here.
I think the issue is that the website alerts are a little fuzzy in comparison with the Pebble. The Pebble user experience is a hard alert the first time the BG crosses a given threshold... just like Dex.
The website OTOH uses predictive algorithms and can alert either before or after Dex would alert, depending on context. I've seen rapid rises / drops that were alerted on the website 5-10 minutes before the BG actually crossed the hard alert threshold. The predictive modeling can be like a DAD's nose during rapid rises and drops... beating the CGM. OTOH, with a slow downward or upward drift, the predictive model doesn't revert to a hard threshold, sometimes causing a late alert (relative to Dex / Pebble), as Gail has seen.
I like the concept of predictive modeling, but I think it needs to be combined with a hard alert when crossing the high / low threshold in order to remain consistent with Dex / Pebble
Should be taken care of with https://github.com/nightscout/cgm-remote-monitor/pull/305
Can this be closed now that Dreamsicle is out?
yes
Sent from my iPhone
On Jan 23, 2015, at 2:49 AM, Jim Sifferle notifications@github.com wrote:
Can this be closed now that Dreamsicle is out?
— Reply to this email directly or view it on GitHub.
Overnight last night, BG was <80 for an extended period. Rose to over 80, then back down again for a few hours. The low alarm never went off. I asked someone else to verify on their computer if the alarm was working for them viewing my site. It was not.
I was able to look at our computer and verified that the alarm was not working, even though the alarm was enabled and had been open to our site all night.