Kjeld wrote: ↑Sunday 04 December 2022 10:12 I've tested with MQexplorer and had the same results. But I see it's already been picked up and solved, waiting for the next release.

Thanks

If you're on beta, you can now update to the latest version

Thanks waltervl.

I've just posted the issue https://github.com/domoticz/domoticz/issues/5440

I suppose the Domoticz AD developers have not encountered this type of double chanel device yet. So I would advise to make a GitHub issue with al the data (mqtt discover, config and state payloads) necessary to recreate the device. I'll create an issue 👍 Just in the main domoticz repo? I can see th ...

Same dimmer, same setup (with autodiscover), same issue. Domoticz seems to target the first dimmer by encoding `l1` in the device path, while Zigbee2MQTT, when using its frontend, does target the "whole" device and encodes the `l1` dimmer in the brightness property of the data. Is this some issue ...