Alarm for lost signal not working / help requested

[GerritosSteen]

Hello guys,

I'm new to this forum as my five year old son was diagnosed with diabetes three months ago and using Nightscout is a big help managing the illness.

There is an issue I am not able to correct: the alarm for a signal-loss won't work. Neither in the Xdrip-app installed on the cell phone of our son nor on the Nightguard app installed on my wife's and my cell phone when our phones are locked. However, the alarm works with a massive time delay in case the app is open and on the screen. High and low alerts work correct on all phones.

Do you have any suggestions for me? It happens often that the connection is being lost in the night but we are not being alerted.

Setup: my son has a NFC-capable cell phone that was used to activate the freestyle libre 2 sensor with a patched freestyle libre app. Xdrip is installed and uploads the data to the cloud (heroku). My wife and I access the data with the Nightguard app.

[seankenny]

It might be related to #4542, specifically line 81 in lib/plugins/timeago.js (since then it has been updated). I use Spike rather than xDrip but the result appears the same - data is not being uploaded to my heroku instance (in my case, my daughter's Spike master phone died during the night) but my nightscout app on my phone didn't trigger the stale data alert.

if (timeSinceLastSuspended < (15 * 10000)) {

As a temp fix, I updated this on my branch to always return false - see line 81 https://github.com/seankenny/cgm-remote-monitor/blob/master/lib/plugins/timeago.js

Not really familiar with the code but this, when I depoyed to heroke, seems to have done the trick for now.

[sulkaharo]

This should work in the dev branch. The delay to not alarm immediately is included so the site won't issue false alarms on mobile phones / browser tabs that suspend the site, when user resumes the execution.

[sulkaharo]

(Trying to get a release packaged soon to get the fix out.)