Fast drop (and rise) alarm: add setting for number of consecutive readings above limit needed to trigger alarm

[bjornoleh]

The fast drop (and rise) alarms could use adding a setting for the number of consecutive reading above limit needed to trigger alarm. A single drop is not always “clinically significant”, and may be just noise. Alarms for such events may cause alarm fatigue.

Loop Follow fast drop alarm settings also has an option to set an upper BG limit for when the alarm is active, which may also reduce alarm fatigue:

Please also note how different alarm sounds can be defined per event without creating new alarm types, as is the case with xdripswift. This is a little easier to manage in my view.

[paulplant]

This makes sense from a usability point of view. Fast Drops shouldn't be triggered when BG is high, and vice-versa for Fast Rises when BG is low.

[LiroyvH]

@paulplant cough https://github.com/JohanDegraeve/xdripswift/issues/186 cough

[Atharon]

@paulplant As @LiroyvH said, cough cough 😜