Pairing Legrand relay 412170 devices with v1.35.1 leave network after pairring

[Eoras]

What happened?

Hello
I'm using : LEGRAND DIN smart relay for light control ref: 412170

When i try to pair my relay, all work fine on Z2M but after configuration, device leave from the network (and my relay reset)

-> Reset my relay (fixed red led => waiting to join network)
-> Z2M : Permit join
-> Z2M: The relay is detected
-> Z2M : The relay is paired, all configuration is ok. At this moment, led had to become GREEN (success pairring) but he don't, he leave red fix.
-> Z2M : I can control my light but after 5/6 second the relay look like resets and leave network. At this moment, led red flash 1 time and fixe red (waiting to join network)
-> Z2M: The relay is detected
-> Z2M : The relay is paired ....
-> This repeat until i'm on permit joint on Z2M.

With ZHA he work fine, i don't know what happen with Z2M

What did you expect to happen?

I expected that relay pair correctly without leaving automaticly after pairraing.

How to reproduce it (minimal and precise)

Trying to pair 412170 with Z2M and with SONOFF ZigBee P CC2652P (Same with SONOFF ZigBee E EFR32MG21 i tryed)

Zigbee2MQTT version

1.35.1

Adapter firmware version

20210708

Adapter

SONOFF ZigBee 3.0 USB Dongle Plus, TI CC2652P Coordinator

Debug log

Info 2024-01-07 21:52:29MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_leave"}'
Info 2024-01-07 21:52:31Device '0x0004740001241a63' joined
Info 2024-01-07 21:52:31MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_joined"}'
Info 2024-01-07 21:52:31Starting interview of '0x0004740001241a63'
Info 2024-01-07 21:52:31MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63","status":"started"},"type":"device_interview"}'
Debug 2024-01-07 21:52:31Device '0x0004740001241a63' announced itself
Info 2024-01-07 21:52:31MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_announce"}'
Debug 2024-01-07 21:52:31Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'genBasic', data '{"appVersion":0}' from endpoint 1 with groupID 0
Debug 2024-01-07 21:52:31Skipping message, still interviewing
Info 2024-01-07 21:52:31Successfully interviewed '0x0004740001241a63', device has successfully been paired
Info 2024-01-07 21:52:31Device '0x0004740001241a63' is supported, identified as: Legrand DIN smart relay for light control (412170)
Info 2024-01-07 21:52:31MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"DIN smart relay for light control","exposes":[{"features":[{"access":7,"description":"On/off state of the switch","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"},{"access":7,"description":"On/off (works only if device is in \"switch\" mode)","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":5,"description":"Instantaneous measured power","label":"Power","name":"power","property":"power","type":"numeric","unit":"W"},{"access":7,"description":"switch: allow on/off, auto will use wired action via C1/C2 on teleruptor with buttons","label":"Device mode","name":"device_mode","property":"device_mode","type":"enum","values":["switch","auto"]},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"412170","options":[{"access":2,"description":"Calibrates the power value (percentual offset), takes into effect on next report of device.","label":"Power calibration","name":"power_calibration","property":"power_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for power, takes into effect on next report of device. This option can only decrease the precision, not increase it.","label":"Power precision","name":"power_precision","property":"power_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"State actions will also be published as 'action' when true (default false).","label":"State action","name":"state_action","property":"state_action","type":"binary","value_off":false,"value_on":true}],"supports_ota":true,"vendor":"Legrand"},"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63","status":"successful","supported":true},"type":"device_interview"}'
Info 2024-01-07 21:52:31Configuring '0x0004740001241a63'
Debug 2024-01-07 21:52:39Received Zigbee message from '0x0004740001241a63', type 'read', cluster 'genBasic', data '[61440]' from endpoint 1 with groupID 0
Error 2024-01-07 21:52:41Failed to configure '0x0004740001241a63', attempt 1 (Error: Bind 0x0004740001241a63/1 genIdentify from '0x00124b002c3ac33e/1' failed (AREQ - ZDO - bindRsp after 10000ms) at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (node:internal/timers:569:17) at processTimers (node:internal/timers:512:7))
Warning 2024-01-07 21:52:42Device '0x0004740001241a63' left the network
Info 2024-01-07 21:52:42MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_leave"}'
Info 2024-01-07 21:52:44Device '0x0004740001241a63' joined
Info 2024-01-07 21:52:44MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_joined"}'
Info 2024-01-07 21:52:44Starting interview of '0x0004740001241a63'
Info 2024-01-07 21:52:44MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63","status":"started"},"type":"device_interview"}'
Debug 2024-01-07 21:52:44Device '0x0004740001241a63' announced itself
Info 2024-01-07 21:52:44MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_announce"}'
Debug 2024-01-07 21:52:44Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'genBasic', data '{"appVersion":0}' from endpoint 1 with groupID 0
Debug 2024-01-07 21:52:44Skipping message, still interviewing
Info 2024-01-07 21:52:44Successfully interviewed '0x0004740001241a63', device has successfully been paired
Info 2024-01-07 21:52:44Device '0x0004740001241a63' is supported, identified as: Legrand DIN smart relay for light control (412170)
Info 2024-01-07 21:52:44MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"DIN smart relay for light control","exposes":[{"features":[{"access":7,"description":"On/off state of the switch","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"},{"access":7,"description":"On/off (works only if device is in \"switch\" mode)","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":5,"description":"Instantaneous measured power","label":"Power","name":"power","property":"power","type":"numeric","unit":"W"},{"access":7,"description":"switch: allow on/off, auto will use wired action via C1/C2 on teleruptor with buttons","label":"Device mode","name":"device_mode","property":"device_mode","type":"enum","values":["switch","auto"]},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"412170","options":[{"access":2,"description":"Calibrates the power value (percentual offset), takes into effect on next report of device.","label":"Power calibration","name":"power_calibration","property":"power_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for power, takes into effect on next report of device. This option can only decrease the precision, not increase it.","label":"Power precision","name":"power_precision","property":"power_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"State actions will also be published as 'action' when true (default false).","label":"State action","name":"state_action","property":"state_action","type":"binary","value_off":false,"value_on":true}],"supports_ota":true,"vendor":"Legrand"},"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63","status":"successful","supported":true},"type":"device_interview"}'
Info 2024-01-07 21:52:44Configuring '0x0004740001241a63'
Debug 2024-01-07 21:52:45Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'haElectricalMeasurement', data '{"acCurrentMultiplier":0,"acVoltageDivisor":0,"acVoltageMultiplier":0}' from endpoint 1 with groupID 0
Debug 2024-01-07 21:52:45Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'haElectricalMeasurement', data '{"acCurrentDivisor":0,"acPowerDivisor":1,"acPowerMultiplier":1}' from endpoint 1 with groupID 0
Info 2024-01-07 21:52:45Successfully configured '0x0004740001241a63'
Debug 2024-01-07 21:52:48Received MQTT message on 'zigbee2mqtt/bridge/request/device/configure_reporting' with data '{"attribute":"onOff","cluster":"genOnOff","id":"0x0004740001241a63/1","maximum_report_interval":65535,"minimum_report_interval":0,"reportable_change":0,"transaction":"rx21c-2"}'
Info 2024-01-07 21:52:48Configured reporting for '0x0004740001241a63/1', 'genOnOff.onOff'
Info 2024-01-07 21:52:48MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure_reporting', payload '{"data":{"attribute":"onOff","cluster":"genOnOff","id":"0x0004740001241a63/1","maximum_report_interval":65535,"minimum_report_interval":0,"reportable_change":0},"status":"ok","transaction":"rx21c-2"}'
Debug 2024-01-07 21:52:54Received Zigbee message from '0x0004740001241a63', type 'read', cluster 'genBasic', data '[61440]' from endpoint 1 with groupID 0
Warning 2024-01-07 21:52:54Device '0x0004740001241a63' left the network
Info 2024-01-07 21:52:54MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_leave"}'
Warning 2024-01-07 21:52:54Device '0x0004740001241a63' left the network
Info 2024-01-07 21:52:54MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_leave"}'
Info 2024-01-07 21:52:56Device '0x0004740001241a63' joined
Info 2024-01-07 21:52:56MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_joined"}'
Info 2024-01-07 21:52:56Starting interview of '0x0004740001241a63'
Info 2024-01-07 21:52:56MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63","status":"started"},"type":"device_interview"}'
Debug 2024-01-07 21:52:57Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'genBasic', data '{"appVersion":0}' from endpoint 1 with groupID 0
Debug 2024-01-07 21:52:57Skipping message, still interviewing
Info 2024-01-07 21:52:57Successfully interviewed '0x0004740001241a63', device has successfully been paired
Info 2024-01-07 21:52:57Device '0x0004740001241a63' is supported, identified as: Legrand DIN smart relay for light control (412170)
Info 2024-01-07 21:52:57MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"DIN smart relay for light control","exposes":[{"features":[{"access":7,"description":"On/off state of the switch","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"},{"access":7,"description":"On/off (works only if device is in \"switch\" mode)","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":5,"description":"Instantaneous measured power","label":"Power","name":"power","property":"power","type":"numeric","unit":"W"},{"access":7,"description":"switch: allow on/off, auto will use wired action via C1/C2 on teleruptor with buttons","label":"Device mode","name":"device_mode","property":"device_mode","type":"enum","values":["switch","auto"]},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"412170","options":[{"access":2,"description":"Calibrates the power value (percentual offset), takes into effect on next report of device.","label":"Power calibration","name":"power_calibration","property":"power_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for power, takes into effect on next report of device. This option can only decrease the precision, not increase it.","label":"Power precision","name":"power_precision","property":"power_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"State actions will also be published as 'action' when true (default false).","label":"State action","name":"state_action","property":"state_action","type":"binary","value_off":false,"value_on":true}],"supports_ota":true,"vendor":"Legrand"},"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63","status":"successful","supported":true},"type":"device_interview"}'
Info 2024-01-07 21:52:57Configuring '0x0004740001241a63'
Debug 2024-01-07 21:52:57Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'haElectricalMeasurement', data '{"acCurrentMultiplier":0,"acVoltageDivisor":0,"acVoltageMultiplier":0}' from endpoint 1 with groupID 0
Debug 2024-01-07 21:52:57Device '0x0004740001241a63' announced itself
Info 2024-01-07 21:52:57MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_announce"}'
Debug 2024-01-07 21:52:57Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'haElectricalMeasurement', data '{"acCurrentDivisor":0,"acPowerDivisor":1,"acPowerMultiplier":1}' from endpoint 1 with groupID 0
Info 2024-01-07 21:52:57Successfully configured '0x0004740001241a63'
Debug 2024-01-07 21:52:59Retrieving state of '0x0004740001241a63' after reconnect
Debug 2024-01-07 21:52:59Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Info 2024-01-07 21:52:59MQTT publish: topic 'zigbee2mqtt/0x0004740001241a63', payload '{"device_mode":"auto","led_if_on":"OFF","led_in_dark":"OFF","linkquality":81,"power":null,"state":"OFF","update":{"installed_version":-1,"latest_version":-1,"state":null},"update_available":null}'
Debug 2024-01-07 21:53:07Received Zigbee message from '0x0004740001241a63', type 'read', cluster 'genBasic', data '[61440]' from endpoint 1 with groupID 0
Warning 2024-01-07 21:53:07Device '0x0004740001241a63' left the network
Info 2024-01-07 21:53:07MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_leave"}'
Warning 2024-01-07 21:53:07Device '0x0004740001241a63' left the network
Info 2024-01-07 21:53:07MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_leave"}'
Info 2024-01-07 21:53:09Device '0x0004740001241a63' joined
Info 2024-01-07 21:53:09MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_joined"}'
Info 2024-01-07 21:53:09Starting interview of '0x0004740001241a63'
Info 2024-01-07 21:53:09MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63","status":"started"},"type":"device_interview"}'
Debug 2024-01-07 21:53:09Device '0x0004740001241a63' announced itself
Info 2024-01-07 21:53:09MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_announce"}'
Debug 2024-01-07 21:53:09Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'genBasic', data '{"appVersion":0}' from endpoint 1 with groupID 0
Debug 2024-01-07 21:53:09Skipping message, still interviewing
Info 2024-01-07 21:53:10Successfully interviewed '0x0004740001241a63', device has successfully been paired
Info 2024-01-07 21:53:10Device '0x0004740001241a63' is supported, identified as: Legrand DIN smart relay for light control (412170)
Info 2024-01-07 21:53:10MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"DIN smart relay for light control","exposes":[{"features":[{"access":7,"description":"On/off state of the switch","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"},{"access":7,"description":"On/off (works only if device is in \"switch\" mode)","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":5,"description":"Instantaneous measured power","label":"Power","name":"power","property":"power","type":"numeric","unit":"W"},{"access":7,"description":"switch: allow on/off, auto will use wired action via C1/C2 on teleruptor with buttons","label":"Device mode","name":"device_mode","property":"device_mode","type":"enum","values":["switch","auto"]},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"412170","options":[{"access":2,"description":"Calibrates the power value (percentual offset), takes into effect on next report of device.","label":"Power calibration","name":"power_calibration","property":"power_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for power, takes into effect on next report of device. This option can only decrease the precision, not increase it.","label":"Power precision","name":"power_precision","property":"power_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"State actions will also be published as 'action' when true (default false).","label":"State action","name":"state_action","property":"state_action","type":"binary","value_off":false,"value_on":true}],"supports_ota":true,"vendor":"Legrand"},"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63","status":"successful","supported":true},"type":"device_interview"}'
Info 2024-01-07 21:53:10Configuring '0x0004740001241a63'
Debug 2024-01-07 21:53:11Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'haElectricalMeasurement', data '{"acCurrentMultiplier":0,"acVoltageDivisor":0,"acVoltageMultiplier":0}' from endpoint 1 with groupID 0
Debug 2024-01-07 21:53:11Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'haElectricalMeasurement', data '{"acCurrentDivisor":0,"acPowerDivisor":1,"acPowerMultiplier":1}' from endpoint 1 with groupID 0
Info 2024-01-07 21:53:11Successfully configured '0x0004740001241a63'
Debug 2024-01-07 21:53:11Retrieving state of '0x0004740001241a63' after reconnect
Debug 2024-01-07 21:53:11Received Zigbee message from '0x0004740001241a63', type 'readResponse', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Info 2024-01-07 21:53:11MQTT publish: topic 'zigbee2mqtt/0x0004740001241a63', payload '{"device_mode":"auto","led_if_on":"OFF","led_in_dark":"OFF","linkquality":84,"power":null,"state":"OFF","update":{"installed_version":-1,"latest_version":-1,"state":null},"update_available":null}'
Debug 2024-01-07 21:53:13Received MQTT message on 'zigbee2mqtt/bridge/request/permit_join' with data '{"device":null,"time":254,"transaction":"rx21c-3","value":false}'
Info 2024-01-07 21:53:13Zigbee: disabling joining new devices.
Info 2024-01-07 21:53:13MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254,"value":false},"status":"ok","transaction":"rx21c-3"}'
Debug 2024-01-07 21:53:17Received Zigbee message from '0x0004740001241a63', type 'read', cluster 'genBasic', data '[61440]' from endpoint 1 with groupID 0
Warning 2024-01-07 21:53:17Device '0x0004740001241a63' left the network
Info 2024-01-07 21:53:17MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_leave"}'
Warning 2024-01-07 21:53:17Device '0x0004740001241a63' left the network
Info 2024-01-07 21:53:17MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x0004740001241a63","ieee_address":"0x0004740001241a63"},"type":"device_leave"}'
Debug 2024-01-07 21:54:54Saving state to file /config/zigbee2mqtt/state.json
Debug 2024-01-07 21:57:05Received Zigbee message from 'Chambre ZG-227Z', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,238],"type":"Buffer"},"datatype":2,"dp":1}],"seq":26112}' from endpoint 1 with groupID 0
Info 2024-01-07 21:57:05MQTT publish: topic 'zigbee2mqtt/Chambre ZG-227Z', payload '{"battery":100,"humidity":36,"humidity_calibration":null,"linkquality":81,"temperature":23.8,"temperature_calibration":null,"temperature_unit":"celsius"}'
Debug 2024-01-07 21:57:05Received Zigbee message from 'Chambre ZG-227Z', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,36],"type":"Buffer"},"datatype":2,"dp":2}],"seq":26368}' from endpoint 1 with groupID 0
Info 2024-01-07 21:57:05MQTT publish: topic 'zigbee2mqtt/Chambre ZG-227Z', payload '{"battery":100,"humidity":36,"humidity_calibration":null,"linkquality":81,"temperature":23.8,"temperature_calibration":null,"temperature_unit":"celsius"}'
Debug 2024-01-07 21:57:05Received Zigbee message from 'Chambre ZG-227Z', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2380}' from endpoint 1 with groupID 0
Debug 2024-01-07 21:57:05No converter available for 'ZG-227Z' with cluster 'msTemperatureMeasurement' and type 'attributeReport' and data '{"measuredValue":2380}'
Debug 2024-01-07 21:57:06Received Zigbee message from 'Chambre ZG-227Z', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":3610}' from endpoint 1 with groupID 0
Debug 2024-01-07 21:57:06No converter available for 'ZG-227Z' with cluster 'msRelativeHumidity' and type 'attributeReport' and data '{"measuredValue":3610}'
Debug 2024-01-07 21:59:54Saving state to file /config/zigbee2mqtt/state.json
Debug 2024-01-07 22:04:54Saving state to file /config/zigbee2mqtt/state.json
Debug 2024-01-07 22:09:54Saving state to file /config/zigbee2mqtt/state.json

[mircolino]

I'm experiencing the exact same issue with Bticino L4411C/N4411C/NT4411C

In my case this problem started with v1.35.0-1 and was working fine with 1.34.0-1

So if you have a 1.34.0 backup you can downgrade and this will allow to pair your devices.

[Eoras]

I don't have the possibility to downgrade to 1.34.0 but some people have the same problem with both version and this divice...
I think Z2M forgot to send something to finalize the pairring and therefore the divice resets. I don't know, i need help

[Gjuju]

I have the exact same problem with 4 TS011F_plug_1 and a xiaomi lywsd03mmc.

With 1.35.1 (1.35.0 didn't start) and with my 1.34 backup.

Edit // tried with 1.33.n backup with same result

[Eoras]

Hello, I purchased a LEGRAND 4 121 81 control module in order to update my remote switches. I was on version 37 and they were updated to version 82.
I then reset the toggle switch, and reconnected it to Z2M and it works perfectly well now, the problem was fixed with the update. This requires having a Legrand Modul Control for the first update but it works perfectly well.

[Koenkk]

@mircolino could you provide the herdsman debug log with both 1.34.0 (working) and 1.35.1 (not working)

See this on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files.

[Eoras]

I can't do it now but I ordered new switches, when I receive them, I won't update them right away to have the logs.

But with SONOFF ZigBee E EFR32MG21 and updated switch relay it's working fine. But better fix this to update OTA for free and not buy Modul control ;)

[JiDW]

Hey!
I have the same issue.
I do not have the 1.34 logs at this moment as I'm not sure how to safely downgrade the HA add-on version of z2mqtt.

Here is the 1.35.1 log files tho
legrandlogfile.log

Thanks for your help!

[steve41200]

Hey. I have the same pb.
During this week I've update Z2M add-on on HA.
This Sunday I discover 2 on my 3 https://www.zigbee2mqtt.io/devices/412170.html#legrand-412170
who my automatization via NodeRed seems works.
But the command from Z2M WebUi or dashboard d'ont work. But when the device is off, it really launch on (light is on in the house) but. don't see it.
I see some time log like this

<small>2024-01-14 18:57:55</small>Publish 'set' 'state' to 'lumières allée jardin' failed: 'Error: Command 0x000474000085569a/1 genOnOff.on({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 42668 - 1 - 190 - 6 - 11 after 10000ms)'``

I have try to unpaired it. And when I repair I have the problem of device join well but leave the network quickly, rejoin ...
and light indicator on device stay on red and don't come green.

After some hours of trying it finally will work, but an another similar device do the same thing ....

I have discover to late this problem to downgrade the last version of z2m my backup was gone :(

[tangane]

Hello. I have also exactly the same problem. Should I move to ZHA (not possible to downgrade Z2M) or do you think a fix might be available in the coming days ?
Thanks a lot!

[nicozocco]

I've been using a solution posted in a separate issue for this same thing and has been working, although it's a bit burdensome

• Reset switch (blink red)
• Put it in pairing mode (blinking green)
• Allow join in Z2M
• Pay attention to the config messaged, once it states it Successfully Setup (and before it leaves the network) stop Z2M instance (docker or service), while the switch is still blinking green.
• Wait till the switch stops blinking
• Restart Z2M
• Reset switch and pair it again, it'll blink green, in Z2M it will setup successfuly and after a couple of blinks it'll blinkg magenta (successful pair)

[steve41200]

did you have seen an another pb with the last update ?
Sometimes the teleruptor legrand did'nt respond (in HA or in Z2M) but when you click on it in HA he light on in realife. But don't respond in z2m or HA.I see in log Publish 'set' 'state' to 'lumières allée jardin' failed: 'Error: Command 0x000474000085569a/1 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 42668 - 1 - 141 - 6 - 11 after 10000ms)'

I cannot light off then from HA or z2M but with my automation from node red it works ...

Sunday it works like this for 2 of my 3 legrand and today 1 of the 3 ...

And in z2m the last seen is 7H, just aftet the warning message and the light is lighthning in reality ....

[tangane]

After having pulled the last dev branch of z2m (not sure it helped actually) I tried what nicozocco wrote.
Delete from z2m
Reset the 412170
Put it back in pairing mode and allow pairing on z2m
Killed z2m juste after "pairing success"
And after a couple of pushes on the setup button the led lighted magenta (never saw this color before)
z2m up again and... miracle, it works !
I did the same on all my 5 412170
This is a little bit blurry, but it worked ;)
Thanks a lot

[nicozocco]

@steve41200 yes, im having similar issues, sometimes i press a switch and it does nothing at all. I haven't looked at the logs yet, will do it this weekend.

[jngdan]

Hi, Thanks a lot, specially to nicozocco and tangane to provide this (a little bit special) procedure. I can correctly linked my 412171 module now, without any very short net leaving issues after a successful pairing as I experimented previously.
Congrats !

[steve41200]

It is really strange. I try to reconnect my last (of 3 Legrand device teleruptor). One time I see the magenta light on dev branch. It will work, but after an another Legrand device who work will have the same comportement (light on but no return).

I'll be crazy with that

[bonjour81]

Hi, I experience same with Legrand 412173 .
it's my 1st legrand device, and the first time I install it in z2m.
1.35.1 => "loop" in pairing / leaving.
1.34 => not sure what I did but after some tries, it seems finally paired and stays (some people talked about reboot z2m once it's paired, before it leaves)
I don't have magenta led, but green (maybe magenta is for 412170).

[skwat75]

On my side, the version 1.34 works fine, 1.35.1 -> "loop" in pairing / leaving. Iv'e got yhis behavior with all my legrand devices
Event if the dowgrade process is easy, it is painfull top switch version just to pair a device

[sjorge]

Mine has been paired fine for a few months but I had a power outage and it was not responding, after trying to reset I also see the leave/join behavior and the device never leaves the red led state.

Whatever the manual seems seems incorrect as it never starts flashing (It says to hold >5 to reset, >3 (I assume between 3-5) to enter pair mode, the once green, push once to confirm and exit pair mode.

Mine just never turns green and seems to try and read an unknown attribute, then it imediatly leaves after

debug 2024-02-06 23:38:18: Received Zigbee message from '0x0004740000a1a444', type 'read', cluster 'genBasic', data '[61440]' from endpoint 1 with groupID 0

I'm guessing we need to reply to this one to have it stick, but not sure what.

[hervespitz]

Hello,
Same issue here under HAOS and Z2M 1.35.3, I have a pairing/leaving loop. It's impossible to add a Legrand device to my fresh Z2M install

[ddrag001]

I have the same issue with brand new BTicino FC80CC (Legrand 412171). As soon as the device joins, it leaves the network within 5 sec and then rejoins again.. basically a loop.

[thk-socal]

I have the same issue. I have tried the following devices:

Coordinators: SkyConnect, SONOFF Dongle E, and now PoE TubesZB (ALL EZSP chips)
Devices: Inovelli Switches Blue 2-1 and Blue Fan, Over 12 different models of Hue Lights

At about 30 devices in the network EVERY device starts to join, interview, configure, successfully configure and then about 5-10 seconds later leaves the network. Brand and coordinator do not seem to matter at all.

The following will work to keep them on:
Inovelli: pull the air gap to cut power to the switch the second it "successfully configured"
Hue: Cut the power to the light the second it "successfully configured"
Restart Z2M or change where joining is for a device

My guess is that there is some message that is either sent or expected after "successfully configured" and it is delayed as the network gets larger with lots of routers. Need someone who knows the code better to determine. I can also say it feels that if I join a new switch and use that switch as the place to permit joining that it seems to last a bit longer. This was not a problem in previous versions, as I was well over 200 devices in a single network and did not experience this until recently, not sure latest fully working Z2M version to avoid this though.

[sjorge]

This is probably related to Koenkk/zigbee-herdsman#979, until this is fixed you can theoretically manually comment the readResponse coming from inside zh. I've tried this and then the device pairs again.