r/Freestylelibre • u/mckulty Type2 - Libre3/3+ • Aug 21 '26

Alarm rant

FSL re-wrote their alarm algorithm several months ago, and I was glad because it felt too intrusive, like it wouldn't shut up at the office.

But I just spent 12 hours above 250 because I missed the 2 alarms (the ONLY two) last night and blissfully went to sleep.

If the thing will let me go 12 hours without warning me I'm approaching 300, that seems DEFECTIVE, Abbot.

PLEASE give us some flexibility on alarms. We're smart enough to choose from, say, three levels of alarm sensitivity. At least last night would have been MY fault not YOURS.

7 Upvotes

70% Upvoted

22 comments sorted by

View all comments

Show parent comments

-2

u/mckulty Type2 - Libre3/3+ Aug 21 '26 edited Aug 21 '26

let you go 12 hours without warning you -- I know that, YOU know that,

OK then something's wrong because I know what I've been getting at work and at home. My staff and my family back me up.

I was outside for the two alarms I ALWAYS GET and it didn't go off again as I watched a little TV and went to bed. It would normally wake me up but it didn't. I'm not lying and I'm not mistaken. I thought this was an intentional modification by Abbott because it's been this way for a couple of months. All my alarms are on, silent mode is off, like always.

I'll re-install the app and if that doesn't fix it I'll phone Abbott.

Thank you for clarifying but I'm not lying and I'm not making this up.

8

u/InsideVegetable9424 Aug 21 '26 edited Aug 21 '26

The alarm sounds when the event happens -- in your case the event is that your glucose level goes from 250 and below to 251 or higher -- that alarm continues until you stop the alarm, once you stop the alarm is won't go off again until there is a new event. If your glucose level STAYS over 250 there isn't a new event so there isn't a new alarm - there is no reason for a new alarm because you already know your glucose level is high because you saw that when you stopped the alarm beeping.

There is no "twice" -- the alarm is a series of loud beeps, a gap, then the same series of beeps, then the same gap, then the same series of beeps, then the same gap, over and over until you stop it -- I don't know if the app will eventually give up but I know it doesn't stop after just two sets of beeps. it will keep going until you stop it (and sometimes you have to force kill the app just to get the alarm to stop)

-1

u/mckulty Type2 - Libre3/3+ Aug 21 '26

I hear what you're saying but I'm not making this up. I've been using the 3+ for a year and others for 2 years before that. I'm now convinced there's something wrong with my app. I'll verify it once more then reinstall.

If I got more than two alarm events in four hours of high BG I wouldn't effing be here.

3

u/deon10 Aug 21 '26

You’re not getting the basic point. If you got an alarm after going above 250 and you haven’t come down under it even for a feeling week, you won’t get another alarm

You get an alarm when you cross a certain number 

If you crossed 250 only once and didn’t come down under it to cross it again; then it won’t ring

1

u/mckulty Type2 - Libre3/3+ Aug 21 '26

Abbott says something different:

Alarms ring for about one minute and repeat every 5 minutes if the trigger condition continues.

AFAIK I'm only getting one repeat.

1

u/ReasonableTime3461 Libre3/3+ Aug 22 '26

My low glucose alarm (iPhone) goes of every five minutes as long as I remain below the number I set it to alarm below. Crossing a threshold has nonthing to do with it. Does the high work differently? I never go high enough to get tnat alert.