starred/OpenEPaperLink
1
0
Fork 0
mirror of https://github.com/OpenEPaperLink/OpenEPaperLink.git synced 2026-03-21 00:04:28 +01:00
Code Issues 472 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #386] Possible problem with "Nightly reboot" #2992

New Issue
Closed
opened 2026-03-20 22:06:22 +01:00 by sascha_hemi · 5 comments
sascha_hemi commented 2026-03-20 22:06:22 +01:00
Owner
Copy Link

Originally created by @jurasjo on GitHub (Oct 29, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/386

Originally assigned to: @nlimper on GitHub.

Describe the bug
It is a continuation of this issue: https://github.com/OpenEPaperLink/Home_Assistant_Integration/issues/188

I think, because of "Nightly reboot", jobs/automatons might not be properly sent to tags if those are scheduled at this time.
Now it is clear why I have been observing problems around that particular time.

Looks like this reboot functionality might have something to do with that. Maybe it should be optional or configurable, so it can be set at a time, when there is no planned job.

Full hour might not be the best time for reboot.

To Reproduce
Steps to reproduce the behavior:

Schedule jobs/automations in HA which run around 4:00 and there is a big chance it will not be properly sent to AP/tags, because AP is not available for about 30 sec to 1min at that time.

Expected behavior

Reboot of the AP should not interfere with sending data to tags.

Originally created by @jurasjo on GitHub (Oct 29, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/386 Originally assigned to: @nlimper on GitHub. **Describe the bug** It is a continuation of this issue: [https://github.com/OpenEPaperLink/Home_Assistant_Integration/issues/188](https://github.com/OpenEPaperLink/Home_Assistant_Integration/issues/188) I think, because of "Nightly reboot", jobs/automatons might not be properly sent to tags if those are scheduled at this time. Now it is clear why I have been observing problems around that particular time. Looks like this reboot functionality might have something to do with that. Maybe it should be optional or configurable, so it can be set at a time, when there is no planned job. Full hour might not be the best time for reboot. **To Reproduce** Steps to reproduce the behavior: Schedule jobs/automations in HA which run around 4:00 and there is a big chance it will not be properly sent to AP/tags, because AP is not available for about 30 sec to 1min at that time. **Expected behavior** Reboot of the AP should not interfere with sending data to tags.
sascha_hemi added the bug label 2026-03-20 22:06:22 +01:00
sascha_hemi commented 2026-03-20 22:06:22 +01:00
Author
Owner
Copy Link

@nlimper commented on GitHub (Oct 29, 2024):

I will make it optional, and use 3:56 instead of 4:00

<!-- gh-comment-id:2443724632 --> @nlimper commented on GitHub (Oct 29, 2024): I will make it optional, and use 3:56 instead of 4:00
sascha_hemi commented 2026-03-20 22:06:22 +01:00
Author
Owner
Copy Link

@jurasjo commented on GitHub (Oct 29, 2024):

This sounds great.
HA integration has an option for restarting implemented, so if you make it optional in AP, then we can setup an automation in HA.
Thank you.

<!-- gh-comment-id:2443738291 --> @jurasjo commented on GitHub (Oct 29, 2024): This sounds great. HA integration has an option for restarting implemented, so if you make it optional in AP, then we can setup an automation in HA. Thank you.
sascha_hemi commented 2026-03-20 22:06:23 +01:00
Author
Owner
Copy Link

@nlimper commented on GitHub (Nov 2, 2024):

done, in a57c797542

<!-- gh-comment-id:2453091373 --> @nlimper commented on GitHub (Nov 2, 2024): done, in https://github.com/OpenEPaperLink/OpenEPaperLink/commit/a57c797542536004cba3298d91e1668260b49106
sascha_hemi commented 2026-03-20 22:06:23 +01:00
Author
Owner
Copy Link

@jurasjo commented on GitHub (Nov 3, 2024):

Thanks for that. So in order to apply this change, the new release must be available?

<!-- gh-comment-id:2453298385 --> @jurasjo commented on GitHub (Nov 3, 2024): Thanks for that. So in order to apply this change, the new release must be available?
sascha_hemi commented 2026-03-20 22:06:23 +01:00
Author
Owner
Copy Link

@nlimper commented on GitHub (Nov 3, 2024):

That's right. There will be a new release shortly.

<!-- gh-comment-id:2453401635 --> @nlimper commented on GitHub (Nov 3, 2024): That's right. There will be a new release shortly.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
88MZ100 FW
ARM Tag FW
ap fw
bug
documentation
enhancement
good first issue
nRF FW
pull-request
Mirrored from GitHub Pull Request
 question
tag fw
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
sascha_hemi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#2992
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?