[GH-ISSUE #171] AP not updating tags #2298

Closed
opened 2026-03-20 21:05:20 +01:00 by sascha_hemi · 2 comments
Owner

Originally created by @paveldn on GitHub (Dec 2, 2023).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/171

Describe the bug
Everything worked perfectly but AP suddenly stopped updating tag images. No changes where made. Tags are communicating but every time after updating the tag image (from home assistant integration or manually from AP web interface). For every update attempt, I see the log records:
17:57:12 Resending image //current/0000021F7DC13B12.raw
17:57:12 new image is the same as current or already pending image. not updating tag.
17:57:11 Updating 0000021F7DC13B12

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Originally created by @paveldn on GitHub (Dec 2, 2023). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/171 **Describe the bug** Everything worked perfectly but AP suddenly stopped updating tag images. No changes where made. Tags are communicating but every time after updating the tag image (from home assistant integration or manually from AP web interface). For every update attempt, I see the log records: 17:57:12 Resending image //current/0000021F7DC13B12.raw 17:57:12 new image is the same as current or already pending image. not updating tag. 17:57:11 Updating 0000021F7DC13B12 **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.
sascha_hemi added the bug label 2026-03-20 21:05:20 +01:00
Author
Owner

@nlimper commented on GitHub (Dec 2, 2023):

So, it appears the new image cannot be written to the file system. I can think of two possible situations:

  • the file system is full. Especially on eso32-s2 based AP's, file system space is really tight. Delete all unneccesairy files using the file editor (/edit).
  • or, for some reason, the file system is corrupted, sometimes cause littlefs to refuse to write to it. Reflash the file system. If you use vscoce/platformio, use 'upload filesystem image'. Or if you don't, the easiest method is to reflash everything, using install.openepaperlink.de . Your filesystem will be overwritten, so backup any files you want to keep before doing this.
    good luck!
<!-- gh-comment-id:1837212078 --> @nlimper commented on GitHub (Dec 2, 2023): So, it appears the new image cannot be written to the file system. I can think of two possible situations: - the file system is full. Especially on eso32-s2 based AP's, file system space is *really* tight. Delete all unneccesairy files using the file editor (`/edit`). - or, for some reason, the file system is corrupted, sometimes cause littlefs to refuse to write to it. Reflash the file system. If you use vscoce/platformio, use 'upload filesystem image'. Or if you don't, the easiest method is to reflash everything, using install.openepaperlink.de . Your filesystem will be overwritten, so backup any files you want to keep before doing this. good luck!
Author
Owner

@paveldn commented on GitHub (Dec 2, 2023):

Thanks. Not sure if was it corruption or full flash but reflashing helped.
Thanks for the amazing work!

<!-- gh-comment-id:1837229910 --> @paveldn commented on GitHub (Dec 2, 2023): Thanks. Not sure if was it corruption or full flash but reflashing helped. Thanks for the amazing work!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#2298