FYI: ESL-29BRW from gicisky does not work with hass-gicisky tried one from Ali which fail 
I had similar - but I think it’s because mine is ESL-29BRWY - because it seems to be able to do yellow
I dont think that ESL-29BRW or ESL-29BRWY are from gicisky.
Gicisky uses other modelnumbers like ESL_TFT_2.1.
There are indeed ESL that can be found with ESL-29BRW and gicisky in the product name on aliexpress. But the name gicisky apear nowhere in the description.
My personal opinion is that a reseller tries to optimize his search results by using the name gicisky.
The ESL-29BRW does not even look like the gicisky counterpart
The new revision of the screens are BWRY and have a different encoding, I did some reverse engineering of the official APK and did a quick implementation, code in the link below
I only have the 2,9 inch BWRY to test on. Additional testing would be good.
Based on Eigger’s great work!
I got a device that was recognized by hass-gicisky as EPD 2.9" BWRY 296x128 with the following details:
- by Gicisky
- Firmware: 0x8101
- Hardware: 0x402E
AliExpress link https://www.aliexpress.us/item/3256802579992115.html
Store info: GICIsky Official Store
But it doesn’t appear to be able to send updates to the screen, fails after three attempts.
Anyone have any experience with this new one? Do I need a BTProxy device? Or to move the tag closer to my HASS Yellow?
Well after some time, it appears some updates have gone through, so it looks like I’ll need to look into a proxy after all.
What about OpenDisplay integration? It is an official integration (was added in 2026.4). You just need to flash displays with a custom firmware (it can be done via Bluetooth)
If you still havent found it (or someone finds this thread looking for solution) setting up esp bluetooth proxy exactly like in documentation did the job.
Initially put some custom yaml from AI that seemed to work but gicisky.write was failing after 3 attempts:
Write failed to FF:FF:92:99:24:37 (attempt 1/3)
Write failed to FF:FF:92:99:24:37 (attempt 2/3)
Write failed to FF:FF:92:99:24:37 (attempt 3/3)
after changing config to exactly:
esp32_ble_tracker:
scan_parameters:
active: true
bluetooth_proxy:
active: true
it is working:
