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 #346] Loss of connection after a few hours of use #1858

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

Originally created by @canoben on GitHub (Jul 3, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/346

Describe the bug
I have a few tags and they work fine using a Home Assistant automation. But after a few hours of use, the connection to the AP is lost, the built-in screen turns black and the RGB LED displays a constant blue or green light (instead of pulsating). Disconnecting the power and rebooting the device restores functionality.

To Reproduce
Steps to reproduce the behavior:

  1. Connect the OpenEPaperLink AP to wifi network
  2. Use it for a few hours
  3. Unit stops working

Expected behaviour
The device should work continuously without needing a reboot every day.

Screenshots
screen goes completely black

Additional context
I'm using latest firmware 2.60b

Originally created by @canoben on GitHub (Jul 3, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/346 **Describe the bug** I have a few tags and they work fine using a Home Assistant automation. But after a few hours of use, the connection to the AP is lost, the built-in screen turns black and the RGB LED displays a constant blue or green light (instead of pulsating). Disconnecting the power and rebooting the device restores functionality. **To Reproduce** Steps to reproduce the behavior: 1. Connect the OpenEPaperLink AP to wifi network 2. Use it for a few hours 3. Unit stops working **Expected behaviour** The device should work continuously without needing a reboot every day. **Screenshots** screen goes completely black **Additional context** I'm using latest firmware 2.60b
sascha_hemi added the bug label 2026-03-20 20:06:50 +01:00
sascha_hemi commented 2026-03-20 20:06:51 +01:00
Author
Owner
Copy Link

@Misiu commented on GitHub (Jul 4, 2024):

I have a similar issue.
I'm using BLE_ONLY firmware on ESP32S3 (installed via https://install.openepaperlink.de/), on the firmware updates page I see these variables:

env:                BLE_ONLY_AP
build date:         2024-05-07 18:05
esp32 version:      ble_test3
filesystem version: unknown <- not matching!
psram size:         8378503
flash size:         16777216
--------------------------

I have a single BLE GICIsky 2.9 display and I'm controlling if from Home Assistant.
After some time I noticed errors in Home Assistant logs and was unable to access Access Point via IP, restarting the ESP solved the issue.
This situation happened 3 times till now.

Not sure how to debug this or get any logs that could help with fixing the issue.

<!-- gh-comment-id:2208942792 --> @Misiu commented on GitHub (Jul 4, 2024): I have a similar issue. I'm using BLE_ONLY firmware on ESP32S3 (installed via https://install.openepaperlink.de/), on the firmware updates page I see these variables: ``` env: BLE_ONLY_AP build date: 2024-05-07 18:05 esp32 version: ble_test3 filesystem version: unknown <- not matching! psram size: 8378503 flash size: 16777216 -------------------------- ``` I have a single BLE GICIsky 2.9 display and I'm controlling if from Home Assistant. After some time I noticed errors in Home Assistant logs and was unable to access Access Point via IP, restarting the ESP solved the issue. This situation happened 3 times till now. Not sure how to debug this or get any logs that could help with fixing the issue.
sascha_hemi commented 2026-03-20 20:06:51 +01:00
Author
Owner
Copy Link

@r2kch commented on GitHub (Jul 6, 2024):

had the same issue with my MiniAP V4 - downgraded to 2.52. Please be aware that there is no or limited ble support.
Can you grab the logs via the UART port? (see: https://docs.espressif.com/projects/esp-idf/en/stable/esp32/get-started/establish-serial-connection.html)

<!-- gh-comment-id:2211795245 --> @r2kch commented on GitHub (Jul 6, 2024): had the same issue with my MiniAP V4 - downgraded to 2.52. Please be aware that there is no or limited ble support. Can you grab the logs via the UART port? (see: https://docs.espressif.com/projects/esp-idf/en/stable/esp32/get-started/establish-serial-connection.html)
sascha_hemi commented 2026-03-20 20:06:51 +01:00
Author
Owner
Copy Link

@Misiu commented on GitHub (Jul 16, 2024):

@r2kch thank you for the reply.
I'm aware that BLE is "experimental". I've had to restart my AP two days ago.
I'm using Windows, any steps I should follow? When should I connect the USB to UART? Should I unplug the the power and only have a single cable connected from UART to PC?
The AP works fine for a couple of days and then it crashes. Not sure when and for how long I should gather the logs.

<!-- gh-comment-id:2230701975 --> @Misiu commented on GitHub (Jul 16, 2024): @r2kch thank you for the reply. I'm aware that BLE is "experimental". I've had to restart my AP two days ago. I'm using Windows, any steps I should follow? When should I connect the USB to UART? Should I unplug the the power and only have a single cable connected from UART to PC? The AP works fine for a couple of days and then it crashes. Not sure when and for how long I should gather the logs.
sascha_hemi commented 2026-03-20 20:06:52 +01:00
Author
Owner
Copy Link

@Derek-K commented on GitHub (Sep 1, 2024):

For reference, I saw this update was supposed rolled into 2.07
fix: in rare cases, an AP didn't connect to a WiFi network due to some tight timing
1d03eedfd6

<!-- gh-comment-id:2323396545 --> @Derek-K commented on GitHub (Sep 1, 2024): For reference, I saw this update was supposed rolled into 2.07 **fix: in rare cases, an AP didn't connect to a WiFi network due to some tight timing** https://github.com/OpenEPaperLink/OpenEPaperLink/commit/1d03eedfd65354ccd801277451e95338da093976
sascha_hemi commented 2026-03-20 20:06:52 +01:00
Author
Owner
Copy Link

@Derek-K commented on GitHub (Sep 1, 2024):

For reference, I saw this update was supposed rolled into 2.07 fix: in rare cases, an AP didn't connect to a WiFi network due to some tight timing 1d03eed

However, I looked at the code change, it doesn't really explain why there is a WiFi disconnection in the first place.

1d03eedfd6/ESP32_AP-Flasher/src/wifimanager.cpp (L140-L145)

1d03eedfd6/ESP32_AP-Flasher/src/wifimanager.cpp (L211-L214)

It just adds delay(100) in wifimanager

<!-- gh-comment-id:2323404921 --> @Derek-K commented on GitHub (Sep 1, 2024): > For reference, I saw this update was supposed rolled into 2.07 **fix: in rare cases, an AP didn't connect to a WiFi network due to some tight timing** [1d03eed](https://github.com/OpenEPaperLink/OpenEPaperLink/commit/1d03eedfd65354ccd801277451e95338da093976) However, I looked at the code change, it doesn't really explain why there is a WiFi disconnection in the first place. https://github.com/OpenEPaperLink/OpenEPaperLink/blob/1d03eedfd65354ccd801277451e95338da093976/ESP32_AP-Flasher/src/wifimanager.cpp#L140-L145 https://github.com/OpenEPaperLink/OpenEPaperLink/blob/1d03eedfd65354ccd801277451e95338da093976/ESP32_AP-Flasher/src/wifimanager.cpp#L211-L214 It just adds `delay(100)` in `wifimanager`
sascha_hemi commented 2026-03-20 20:06:52 +01:00
Author
Owner
Copy Link

@foorschtbar commented on GitHub (Sep 4, 2024):

Same problem here with 2.60b. Lost wifi connection nearly every day with my ESP32S3 mini AP

Maybe some changes in the ESP SDK!?

<!-- gh-comment-id:2329294637 --> @foorschtbar commented on GitHub (Sep 4, 2024): Same problem here with 2.60b. Lost wifi connection nearly every day with my ESP32S3 mini AP Maybe some changes in the ESP SDK!?
sascha_hemi commented 2026-03-20 20:06:52 +01:00
Author
Owner
Copy Link

@nlimper commented on GitHub (Sep 4, 2024):

It can be caused by all kinds of reasons. The people who react 'me too!' could have a very different cause as the original poster. Without extensive debugging, it's impossible to fix. It can be caused by all kinds of things, including your Wifi AP settings, including using an instable power supply for the OEPL AP.

When BLE is enabled: it's experimental, and the BLE stack is kind of buggy. Won't fix.

The reference to 1d03eed: that's completely unrelated

To debug, capture the serial output of the AP, to see if there's anything interesting happening. Also, check whether it also hangs if you don't make a HA connection. Also, change the power supply of your AP to a different one to rule that out too, it has happened more often that that was the problem.

<!-- gh-comment-id:2329326021 --> @nlimper commented on GitHub (Sep 4, 2024): It can be caused by all kinds of reasons. The people who react 'me too!' could have a very different cause as the original poster. Without extensive debugging, it's impossible to fix. It can be caused by all kinds of things, including your Wifi AP settings, including using an instable power supply for the OEPL AP. When BLE is enabled: it's experimental, and the BLE stack is kind of buggy. Won't fix. The reference to [1d03eed](https://github.com/OpenEPaperLink/OpenEPaperLink/commit/1d03eedfd65354ccd801277451e95338da093976): that's completely unrelated To debug, capture the serial output of the AP, to see if there's anything interesting happening. Also, check whether it also hangs if you don't make a HA connection. Also, change the power supply of your AP to a different one to rule that out too, it has happened more often that that was the problem.
sascha_hemi commented 2026-03-20 20:06:52 +01:00
Author
Owner
Copy Link

@foorschtbar commented on GitHub (Sep 4, 2024):

You can also see it differently. I notice a problem and first check if there is already a similar one and then someone describes a similar problem. What should I do? Open a new issue? I think it would be helpful to tell the OP in which constellation (hardware + firmware) I also have the wifi issue, so that WE can look for similarities to solve the error.

<!-- gh-comment-id:2329397802 --> @foorschtbar commented on GitHub (Sep 4, 2024): You can also see it differently. I notice a problem and first check if there is already a similar one and then someone describes a similar problem. What should I do? Open a new issue? I think it would be helpful to tell the OP in which constellation (hardware + firmware) I also have the wifi issue, so that WE can look for similarities to solve the error.
sascha_hemi commented 2026-03-20 20:06:52 +01:00
Author
Owner
Copy Link

@nlimper commented on GitHub (Sep 4, 2024):

Fair enough. As long as all participants realise that 'the wifi issue' can be different (and will have different causes) for everybody :-)

<!-- gh-comment-id:2329405333 --> @nlimper commented on GitHub (Sep 4, 2024): Fair enough. As long as all participants realise that 'the wifi issue' can be different (and will have different causes) for everybody :-)
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#1858
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?