[GH-ISSUE #434] websocket sys message deviating value to webinterface #3574

New Issue

sascha_hemi · 2026-03-20T23:06:53+01:00

sascha_hemi commented

2026-03-20 23:06:53 +01:00

Originally created by @micklafisch on GitHub (Jan 29, 2025).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/434

Originally assigned to: @nlimper on GitHub.

Describe the bug
i check the syslog messages for monitoring the system and a lot of "timeout" tags are reported. In the webinterface there is only 1 tag with timeout, see down below. I think the problem is related to the maximul sleep time (i set it to 30mins)

To Reproduce
Steps to reproduce the behavior:

set maximum sleep timer of AP to 30mins
wait a little, maybe 30 minutes =)
check syslog message and compare the value with the webinterace

Expected behavior
same values no matter where the value is queried

Screenshots

{"sys":{"currtime":1738159020,"heap":178232,"recordcount":37,"dbsize":7157,"littlefsfree":5222400,"psfree":8179991,"apstate":1,"runstate":2,"rssi":-34,"wifistatus":3,"wifissid":"GHFN","uptime":39653,"lowbattcount":2,"timeoutcount":24}}

Originally created by @micklafisch on GitHub (Jan 29, 2025). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/434 Originally assigned to: @nlimper on GitHub. **Describe the bug** i check the syslog messages for monitoring the system and a lot of "timeout" tags are reported. In the webinterface there is only 1 tag with timeout, see down below. I think the problem is related to the maximul sleep time (i set it to 30mins) **To Reproduce** Steps to reproduce the behavior: 1. set maximum sleep timer of AP to 30mins 2. wait a little, maybe 30 minutes =) 3. check syslog message and compare the value with the webinterace **Expected behavior** same values no matter where the value is queried **Screenshots** `{"sys":{"currtime":1738159020,"heap":178232,"recordcount":37,"dbsize":7157,"littlefsfree":5222400,"psfree":8179991,"apstate":1,"runstate":2,"rssi":-34,"wifistatus":3,"wifissid":"GHFN","uptime":39653,"lowbattcount":2,"timeoutcount":24}} ` ![Image](https://github.com/user-attachments/assets/a4760dee-d568-49bb-827f-0de29981a67d)

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

sascha_hemi commented

2026-03-20 23:06:53 +01:00

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

Thanks for noting.
I found the reason of the discrepancy, that's fixed (in a future commit). But some tags are marked as timed out, because they are sleeping for the 'max sleep time' (that's by design) but the expected checkin time is not correctly saved. I'm investigating.

@nlimper commented on GitHub (Mar 25, 2025): Thanks for noting. I found the reason of the discrepancy, that's fixed (in a future commit). But some tags are marked as timed out, because they are sleeping for the 'max sleep time' (that's by design) but the expected checkin time is not correctly saved. I'm investigating.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#3574