J’ai testé avec ZHA et avec Zigbee2Mqtt : Même problème avec les 2 solutions.
Avec Zigbee2Mqtt, je peux voir dans les logs que 2 messages sont reçus par le module, le premier à off, puis le second à on, d’où le clignotement.
Debug 2023-10-03 14:53:23Received MQTT message on 'zigbee2mqtt/0x9035eafffea4b322/set' with data '{"state_l2":"OFF"}'
Debug 2023-10-03 14:53:23Publishing 'set' 'state' to '0x9035eafffea4b322'
Info 2023-10-03 14:53:23MQTT publish: topic 'zigbee2mqtt/0x9035eafffea4b322', payload '{"linkquality":81,"power_on_behavior_l2":"previous","state_l1":"OFF","state_l2":"OFF","update":{"installed_version":516,"latest_version":541,"state":"available"},"update_available":null}'
Debug 2023-10-03 14:53:23Received Zigbee message from '0x9035eafffea4b322', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 2 with groupID 0
Debug 2023-10-03 14:53:23Received Zigbee message from '0x9035eafffea4b322', type 'commandToggle', cluster 'genOnOff', data '{}' from endpoint 2 with groupID 0
Debug 2023-10-03 14:53:23No converter available for 'SIN-4-2-20' with cluster 'genOnOff' and type 'commandToggle' and data '{}'
Debug 2023-10-03 14:53:23Received Zigbee message from '0x9035eafffea4b322', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 2 with groupID 0
Info 2023-10-03 14:53:24MQTT publish: topic 'zigbee2mqtt/0x9035eafffea4b322', payload '{"action":"on_l2","linkquality":81,"power_on_behavior_l2":"previous","state_l1":"OFF","state_l2":"ON","update":{"installed_version":516,"latest_version":541,"state":"available"},"update_available":null}'
Info 2023-10-03 14:53:24MQTT publish: topic 'zigbee2mqtt/0x9035eafffea4b322', payload '{"action":"","linkquality":81,"power_on_behavior_l2":"previous","state_l1":"OFF","state_l2":"ON","update":{"installed_version":516,"latest_version":541,"state":"available"},"update_available":null}'
Info 2023-10-03 14:53:24MQTT publish: topic 'zigbee2mqtt/0x9035eafffea4b322/action', payload 'on_l2'