I think I’m going to add another ZigBee network using a second coordinator and Zigbee2MQTT - alongside ZHA. I’ll then move the E1s to that network. Hopefully this will solve the issue as well as open up some opportunities for other devices not available in ZHA yet.
Yes it does. See screenshot. And when I press down and let it stop somewhere in between completely closed or open it updates the percentage of the current position.
did anyone manage to get this working in ZHA? Just got one of these and have it connected but there’s no battery sensor at all and the cover operations don’t have any effect. using a TubesZB as a zha bridge to HA running on a VM.
I purchased e1 2 days ago.
It is manufactured 2022.11.
I use sonoff zb dongle-p.
But e1 did not 100% work with zha from out of the box. Now it works.
I tryed 3-4 diferent sonoff zb dongle-p firmwares, many times use reconfigurations, ha restarts, e1 delete, additigs. Nothing help.
The problem is with zha device configuration process. For some reason zha did not correctly do device cofiguration-installation when the pairing is going. Recofiguration also did not work for me correctly, and ands with whe errors.
My solution: sonoff zb dongle-p 221226 firmware. In HA > Developer tools > services > zha.remove+e1 ieee address > push call service. After that i remove device in zha from device page. I restarted HA and do pairing again and after that HA recognized device as zhaquirks.xiaomi.aqara.roller_curtain_e1.RollerE1AQ in signature page. And that config works for 100% in ZHA
In my case I use a Conbee II on my Debian host with HA running in docker. I had to update the ConbeeII firmware in Windows and didn’t lose any config. Just plugged out the conbee, plugged it into my Windows PC, followed the flash instructions here: Update deCONZ manually · dresden-elektronik/deconz-rest-plugin Wiki · GitHub
Then plugged back into my linux host and restarted HA. Then used the zha.remove service call and re-paired the device. All working well now.