Robot Curtain Driver ZM85EL-2Z into ZHA

Hi everyone, i need a particular zigbee solution and ZM85EL-2Z from zemismart is the only slution i’ve found

BUT, a big one.

is that i have everything on zha and from https://zigbee.blakadder.com/ the said it only work on z2m

soooo, anyone have tried it with zha? or can advice me in something else similar zigbee (not wifi).

really thanks

Just getting a pair of those from AliExpress, should be coming in this week. I do see Bakadder saying they should work with ZHA right now. So I’ll see, hopefully should work.

That is not how device/support compatibility works with the ZHA integration, so no database is accurate for ZHA as for most devices the ZHA integration work out-out-the-box without needing custom device handler code (e.g. quirk/converter that parse/translate non-standard devices into standard Zigbee attributes and parameters), read → https://www.home-assistant.io/integrations/zha#knowing-which-devices-are-supported and https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling

Summery in relevant technical layman’s terms;

Most Zigbee devices with Chinese brands are either made by Tuya or Aqara/Xiaomi and both of those manufacturers are infamous for making device firmware for those products that do not strictly follow Zigbee specification standards, in fact, deviating from standard attributes and values (as well as standard Zigbee clusters) will break practically all Zigbee solutions until they implement custom workarounds for each and every individual device that does not follow the standards of the set specifications, and manufacturers keep releasing new devices so to developers of any third-party Zigbee solutions that did not make that non-standard device it is like a never-ending game of playing catch-up in order to implement a new custom workaround for each new such device that is found in the wild.

To make things a little bit easier such workarounds for individual devices in different Zigbee solutions are implemented in the same way so much can be reused via shared device handlers that deal with conversions of non-standard quirks and deviations from the official specification standards set by the Zigbee Alliance.

Therefore each brand new device needs parsing and translation to convert the messages so are presented as virtual device representations that actually do follow the Zigbee specification standards. That is when someone needs to write a custom “quirk” (sometimes also referred to as a “converter”).

Device handlers/converters parse and translate/convert any non-standard Zigbee attribute(s) and value(s) or other deviating quirks into standard Zigbee attribute(s) and value(s) which then the ZHA integration can understand.

By the way, unlike some proprietary Zigbee solutions such as for example Tuya or Aqara/Xiaomi own Zigbee gateways the ZHA integration implementation and its zigpy dependency has been designed to follow the official Zigbee specification standard and therefore all devices that actually do follow the Zigbee specification standard should just work out-of-the-box without the need of any custom device handlers.

PS: Zigbee2MQTT however always require device converter for each (“zigbee-herdsman converters”):

https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

https://github.com/Koenkk/zigbee-herdsman-converters/tree/master/

As per my comment, works more or less just fine.

FYI, regarding changing/flipping direction for covers in ZHA (i.e. InvertedCover) for ZHA inegration you can see/follow developers work in progress → https://github.com/home-assistant/core/pull/76982 …it looks like they would like some users as testers now to test that code before it is merged?

@Hedda oh, that looks great! How can I pull those bits to use/test in a stock HA install? Never done that. Or do I need to do a full build?

Best if probably to ask @javicalle in GitHub PR → https://github.com/home-assistant/core/pull/76982