[GH-ISSUE #433] Tag display wrong - 2.13" GiSky tag #3022

Closed
opened 2026-03-20 22:06:39 +01:00 by sascha_hemi · 3 comments
Owner

Originally created by @bogd on GitHub (Jan 25, 2025).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/433

Describe the bug
BLE tag seems to be (correctly?) identified, but display is wrong (rotated/multiplied?)

To Reproduce
I have a BLE tag of... unknown manufacturer - purchased from AliExpress. Black/white, 2.13". The tag is identified by the AP as:

Gicisky BLE TFT 2.13"
250x136 fw:33025 0x8101
RSSI -62, LQI 194, 2.9V

However, the display seems completely wrong - see screenshots below.

Expected behavior
Correct display

Screenshots
See here. I tried displaying a days counter (showing 0), and the current date. You can see the image as sent by the AP (screenshot taken from the AP web interface), and a photo of what the tag is actually displaying.

I am aware that the answer may simply be "get a different tag" :) , but... I thought I should post this, maybe someone has seen this problem before and has a solution.

Originally created by @bogd on GitHub (Jan 25, 2025). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/433 **Describe the bug** BLE tag seems to be (correctly?) identified, but display is wrong (rotated/multiplied?) **To Reproduce** I have a BLE tag of... unknown manufacturer - purchased from AliExpress. Black/white, 2.13". The tag is identified by the AP as: Gicisky BLE TFT 2.13" 250x136 fw:33025 0x8101 RSSI -62, LQI 194, 2.9V However, the display seems completely wrong - see screenshots below. **Expected behavior** Correct display **Screenshots** See [here](https://imgur.com/a/TipBAOC). I tried displaying a days counter (showing 0), and the current date. You can see the image as sent by the AP (screenshot taken from the AP web interface), and a photo of what the tag is actually displaying. I am aware that the answer may simply be "get a different tag" :) , but... I thought I should post this, maybe someone has seen this problem before and has a solution.
sascha_hemi added the bug label 2026-03-20 22:06:39 +01:00
Author
Owner

@atc1441 commented on GitHub (Jan 25, 2025):

https://github.com/OpenEPaperLink/OpenEPaperLink/issues/383

<!-- gh-comment-id:2613926370 --> @atc1441 commented on GitHub (Jan 25, 2025): https://github.com/OpenEPaperLink/OpenEPaperLink/issues/383
Author
Owner

@bogd commented on GitHub (Jan 25, 2025):

My apologies, I did search before creating a new issue - apparently, not with the right keywords :)

Thank you for pointing me in the right direction!

<!-- gh-comment-id:2613927906 --> @bogd commented on GitHub (Jan 25, 2025): My apologies, I did search before creating a new issue - apparently, not with the right keywords :) Thank you for pointing me in the right direction!
Author
Owner

@atc1441 commented on GitHub (Jan 25, 2025):

No worries :)

<!-- gh-comment-id:2613929641 --> @atc1441 commented on GitHub (Jan 25, 2025): No worries :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#3022