[GH-ISSUE #447] AP Info Panel show timeout #3588

New Issue

sascha_hemi · 2026-03-20T23:07:03+01:00

sascha_hemi commented

2026-03-20 23:07:03 +01:00

Originally created by @DunklerPhoenix on GitHub (Mar 10, 2025).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/447

Describe the bug
heho
The AP Info panel shows too much timeouts. The webpanel show less

To Reproduce
Steps to reproduce the behavior:

set maximum sleep to 1h
set display (t-lily) to AP Info
see more timeouts on AP display than on webpage

Expected behavior
timeout on AP Panel Info should reflect real timeouts.

Screenshots

Additional context
Maybe the maximum sleep is a bit buggy. Because some Tags are expected to react on the old setting (10min instead of 1h)

Originally created by @DunklerPhoenix on GitHub (Mar 10, 2025). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/447 **Describe the bug** heho The AP Info panel shows too much timeouts. The webpanel show less **To Reproduce** Steps to reproduce the behavior: 1. set maximum sleep to 1h 2. set display (t-lily) to AP Info 3. see more timeouts on AP display than on webpage **Expected behavior** timeout on AP Panel Info should reflect real timeouts. **Screenshots** ![Image](https://github.com/user-attachments/assets/9fa1bfca-49b9-4ff2-949a-82fc49e640fa) ![Image](https://github.com/user-attachments/assets/330e6d62-836e-4625-aac6-fdfa915de2e2) ![Image](https://github.com/user-attachments/assets/5e9e0ea1-ad58-45ce-8b3e-973b721393e0) ![Image](https://github.com/user-attachments/assets/0131b268-d5a2-4692-8ea7-c14756dac049) **Additional context** Maybe the maximum sleep is a bit buggy. Because some Tags are expected to react on the old setting (10min instead of 1h)

sascha_hemi added the bug label 2026-03-20 23:07:03 +01:00

sascha_hemi closed this issue

2026-03-20 23:07:03 +01:00

sascha_hemi commented

2026-03-20 23:07:03 +01:00

@nlimper commented on GitHub (Mar 19, 2025):

Your system had just freshly started (uptime 22 minutes). When a tag content is not updated yet and the tag is not seen yet, there is no expected checkin time known. For that reason, the webinterface never shows any timed out tags for the first 30 minutes after AP boot. The AP info screen does try to make a guess (but, because the next checkin time is unknown, it just counts a timeout for all tags that didn't checkin for the last 10 minutes). After 30 minutes of uptime, the timout count values will be equal.
I'm not planning to fix this.

@nlimper commented on GitHub (Mar 19, 2025): Your system had just freshly started (uptime 22 minutes). When a tag content is not updated yet and the tag is not seen yet, there is no expected checkin time known. For that reason, the webinterface never shows any timed out tags for the first 30 minutes after AP boot. The AP info screen does try to make a guess (but, because the next checkin time is unknown, it just counts a timeout for all tags that didn't checkin for the last 10 minutes). After 30 minutes of uptime, the timout count values will be equal. I'm not planning to fix this.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#3588