You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to make a feature request to have separate thresholds for highs/lows on the chart versus the alarms
I would like to be able to set my personal range as between 3.9 and 10 mmol/l for the graph itself - as that's what I'd consider to be in range; but I'd like to use the alarms as a heads up to prompt me if I am still in range but heading low - so an alarm set at 4.4 for example - so I can decide whether I need to treat it before I actually head low, and for the higher range I'd only like an alarm when I'm going particularly high - above 13 for example - as even though I'd consider 10-13 to be out of range, it's more common to creep up above 10 temporarily anyway and don't always need an alarm for it
I think having a separate threshold for lows would be particularly useful in situations such as when I'm driving to ensure my levels are good.
The text was updated successfully, but these errors were encountered:
Hi there!
I'd like to make a feature request to have separate thresholds for highs/lows on the chart versus the alarms
I would like to be able to set my personal range as between 3.9 and 10 mmol/l for the graph itself - as that's what I'd consider to be in range; but I'd like to use the alarms as a heads up to prompt me if I am still in range but heading low - so an alarm set at 4.4 for example - so I can decide whether I need to treat it before I actually head low, and for the higher range I'd only like an alarm when I'm going particularly high - above 13 for example - as even though I'd consider 10-13 to be out of range, it's more common to creep up above 10 temporarily anyway and don't always need an alarm for it
I think having a separate threshold for lows would be particularly useful in situations such as when I'm driving to ensure my levels are good.
The text was updated successfully, but these errors were encountered: