My thoughts on this:
Thanks for looking into this, I’ll take a peek ASAP.
Hi all & especially hi @ChristopheHD,
I´m a little bit confused about all the forked and opened repositories.
Could you or someone else explain the current difference of both? Te HA_enoceanmqtt & HA_enoceanmqtt-addon?
For me it seems that most (or already all?) functions are already implemented into the enoceanmqtt repo. Will this be the new one and the others will be outdated?
Thanks for all your support! It already help me a lot wil struggeling with a lot of starting problems.
BR Tobias
The HA_enoceanmqtt repo contains the code for the bridge and all material to build a standalone docker installation.
The HA_enoceanmqtt-addon repo relies on the repo HA_enoceanmqtt to build an HA addon for the build.
So both repo are up to date and their usage depends on your needed installation (standalone docker or HA addon).
I should review documentation of those 2 repos to clarify those points.
Ah ok, got it. Thanks for the clarification! 
This is such a great add-on, thank you for you work!
I managed to get Thermokon temp/hum sensors(A5-04-01 and A5-04-02), window/door contacts(D5-00-01) and motion sensors(A5-07-01) all working with the help of your add-on.
Some issues reported in github but all working very well now 
Were you able to test it ?
Sheesh, time flies like an arrow.
Sorry, nope. Not yet anyway.
Right now I have a pile of paperwork threatening to kill me. As soon as that’s out of the way, I’ll give it a go.
Don’t hold your breath, though. It’s a LARGE pile 
@ChristopheHD Thank you, your addin saved my day. Finally I got my Eltako FFG7B window handle to work. I receive now packet like this:
2026-02-09 12:20:57,364 DEBUG: 05:A4:88:FE->FF:FF:FF:FF (-85 dBm): 0x01 ['0xa5', '0x98', '0x0', '0x0', '0xe', '0x5', '0xa4', '0x88', '0xfe', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x55', '0x0'] OrderedDict()
2026-02-09 12:20:57,364 INFO: received: 05:A4:88:FE->FF:FF:FF:FF (-85 dBm): 0x01 ['0xa5', '0x98', '0x0', '0x0', '0xe', '0x5', '0xa4', '0x88', '0xfe', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x55', '0x0'] OrderedDict()
2026-02-09 12:20:57,365 DEBUG: enoceanmqtt/window_office_l: SVC (Supply voltage / super cap. (linear))=3.04 V
2026-02-09 12:20:57,365 DEBUG: enoceanmqtt/window_office_l: CT (Contact)=Open
2026-02-09 12:20:57,365 DEBUG: enoceanmqtt/window_office_l: Sent MQTT: {"_RSSI_": -85, "_DATE_": "2026-02-09T12:20:57.364075", "_RAW_DATA_": "98:00:00:0E:00", "SVC": 3.04, "CT": 3}
But how can I show now the states of each window in the dashboard? Something lilke this (must not be graphical, cold also be open/tilt/closed…
BR
sp00ky
According to the code, you should already have an entity state_2p in the HA device which correctly display as a window.
Found it, merci! Do you also know how to make this kind of graphical overview?
I guess this is a glance card (Glance card - Home Assistant)
@holzgewaechs can you provide feedback on the custom mapping for Flextron 300621 ?
@olwin, did you had a change to test the custom mapping ? If yes, please provide feedback in Github : Update position and tilt templates to handle None by ChristopheHD · Pull Request #37 · ChristopheHD/HA_enoceanmqtt · GitHub
As a matter of fact, I just did.
Not without minor trouble, I might add, but now it works.
With just the standard installation and the device file I used in mak’s version, my window handles worked properly right away.
The D2-05-02 covers, however, didn’t.
They didn’t report position or “last seen” anymore.
The new mapping file didn’t change that.
I just moved one of the shutters down for a bit and then stopped it again.
Curiously, there’s only one telegram from the drive in question in the logs:
2026-04-24 10:46:15,719 INFO: received: 05:19:9F:6E->FF:FF:FF:FF (-91 dBm): 0x01 ['0xd2', '0x7f', '0x7f', '0x0', '0x4', '0x5', '0x19', '0x9f', '0x6e', '0x80'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()
With the old version, I’d get one telegram when the drive starts moving (with position 127) and one after it stopped (with the current position 0…100).
Moving to new repo shouldn’t change the behavior. Only 1 telegram out of 2 received suggests a wireless range issue confirmed by the RSSI confirmed by the value of RSSI (-91 dBm is very low). Repeater should be put in place if possible.
When receiving this telegram, what is the value of the position in HA ?
Hm. Never mind my post, it seems to be a connection issue indeed.
Of course, I randomly picked the drive with the worst connection.
All the others work as expected, last seen info, position and all.
I’ll need to move the repeater to a better location.
OK, thanks for the feedback.
Can you confirm that the reported position is unknown when shutter is moving ?
No. There’s no hint that the cover is moving, the position remains at the last known number until movement has stopped.