Some L3 sensors seem to send the new glucose value not every 60s, sometimes even faster.
As soon as juggluco receives a value it broadcasts the value to other apps (xdrip ie) and this can lead to problems, as other apps do have sanity checks for new values not before 60s+.
In xdrip this causes values to forwarded to AAPS.
xdrip is needed for calibrating wrong sensor values thou!
The smartest solution would be to keep the receiving value back until 60s from last received value have passed and then send a broadcast. Not as soon as receiving a new value.
j-kaltes
commented
1 year ago
Some L3 sensors seem to send the new glucose value not every 60s, sometimes even faster.
As soon as juggluco receives a value it broadcasts the value to other apps (xdrip ie) and this can lead to problems, as other apps do have sanity checks for new values not before 60s+. In xdrip this causes values to forwarded to AAPS. xdrip is needed for calibrating wrong sensor values thou!
The smartest solution would be to keep the receiving value back until 60s from last received value have passed and then send a broadcast. Not as soon as receiving a new value.
This can lead to errors like this: