PersistentHigh-alert does sometimes not get triggered

[slimSpencer]

Version: 61ec19d-2025.04.30
Phone:Samsung SM-A346B 34 14 A346BXXS9CYD1
DB-Size: 67M
Source: Other App (juggluco with Libre 3)

Hello,

the PersistentHigh-alert sometimes does not get triggered. In the log it then says for example: "2025-05-14 07:45:59 ^ PersistentHigh ^ High not persistent as reading at: 2025-05-14 02:18:59 does not exceed 140 mgdl / high mark"
It uses a very old value (many hours ago) to determine that high is not persistent. However, it should alert after 25 minutes of a too high value.

This night was a good example - see screenshot:

• glucose was around 160 at 01:30
• injected 2u and went to bed
• i snoozed all alerts for likely 1 hour, as glucose was trending in the right direction
• however, glucose started rising again and was above mark (140) at around 02:40
• PersistentHigh never triggered the whole night

In the log it says multiple times for example "2025-05-14 07:45:59 ^ PersistentHigh ^ High not persistent as reading at: 2025-05-14 02:18:59 does not exceed 140 mgdl / high mark" (see attached log).

PersistentHigh-alert is configured to use high-value under glucose-units (140 mg/dl) and set to trigger when above limit longer than 25 minutes. So it should have triggered at ~02:40+25m (~03:05). There are no other alerts configured.

This problem occurs in the nightly build from 20250430 and 20250425. I am not 100% sure, but i think it also happened in the latest release version.

Best Regards

xDrip-log2.txt

[Navid200]

Can you post a screenshot of the Persistent High Alert settings page?

[slimSpencer]

No, it is not. Should i enable it?

[Navid200]

No, you should not enable engineering mode.

---

You have identified a log that looks suspicious:
2025-05-14 07:55:37 ^ PersistentHigh ^ High not persistent as reading at: 2025-05-14 02:18:59 does not exceed 140 mgdl / high mark

However, I believe the log that tells us what really needs attention is this:
2025-05-14 07:55:37 ^ LibreTrendGraph ^ Error getting data from getLatestBgForXMinutes. Returning

According to that, xDrip does not believe that it is receiving valid values.

[Navid200]

Libre is not my expertise.
Does xDrip not support the sensor you use?

@PhilTU

[PhilTU]

With Libre 2 patched app as the hardware data source I don't get any log messages normally.

So I enabled "show libre trend" and generated about 12 errors per minute along the lines above.

Therefore I suggest turning off the Libre trend display in Settings and at least the log will not then be full of Error getting data from getLatestBgForXMinutes-messages

[slimSpencer]

thx, turned that off and the log-spamming stopped.

[slimSpencer]

To be honest, i dont know if Libre 3 works natively in xdrip. The tutorials and community-posts i found point out that juggluco is the way to go as it behaves like the old patched libre app. From an end-user perspective, it seems to work flawlessly, but ofc you are absolutely right about the mass of log-entries.

One finding: in the attached log, when you go to line ~688, you see there is a valid persistentHigh-alert at 13/5/25 23:59, but it is also covered with the Error getting data from getLatestBgForXMinutes-messages. This alert was working properly.

Another thought: at the time this night, when the glucose was briefly below 140 (at around 02:18), the alerts were in a snooze-state. The snooze lasted til ~03:00. So maybe there is a coherence? The log-message always refers to this point in time: "...reading at: 2025-05-14 02:18:59 does not exceed 140 mgdl / high mark"

[PhilTU]

Libre 3 does not work natively in xDrip+

options are juggluco (and diabox) connecting to sensor and feeding data to xDrip+ as "Libre patched app" source, or the internet connected following of LibreLinkUp data which is also prone to vendor disruption.

[slimSpencer]

In the past, i used web follower with the official libre app. However, the official app is inefficient, slow and lacks essential features. So i tossed it and switched to juggluco and xdrip. It is amazing what you guys (and jka/juggluco) did what a big company can't - and how it improves our quality of life.

Big thanks and kudos from my site!