Woox smoke alarms don't re-pair after adapter upgrade

[JanvdW304]

Yesterday I upgraded my CC2531 adapter (which corrupted frequently) to a CC2652RB based adapter (Slaesh's). All Zigbee devices reconnected without problems, except my WOOX R7049 smoke alarm devices. I don't understand what is going wrong.

• WOOX devices report 'Offline' availability in the Zigbee2MQTT frontend
• The devices can't be controlled, not by Domoticz and not by the Zigbee2MQTT frontend
• On the other hand the last seen status in Domoticz is updated frequently
• I removed one of the smoke detectors from the Zigbee network and deleted the corresponding Domoticz devices. After that I re-paired the device. This doesn't help at all: the device has still the 'offline' status in Zigbee2MQTT, new devices are created in Domoticz and the last seen status is frequently updated, but I can't control the device

What can be wrong?

Additional information Zigbee2MQTT version: 1.25.2-dev commit: [92f7bc8e] Python version: 3.7.3 Domoticz version: 2022.2 (build 14880) Coordinator revision: 20220219 Coordinator type: zStack3x0

Log Zigbee2MQTT (when you swith on alarm in Domoticz): Error 2022-12-29 20:28:41Publish 'set' 'alarm' to 'Rookmelder voor 1' failed: 'Error: Command 0xbc33acfffe4e6fd2/1 manuSpecificTuya.dataRequest({"seq":0,"dpValues":[{"dp":20,"datatype":4,"data":[0]}]}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))' Info 2022-12-29 20:28:41MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'alarm' to 'Rookmelder voor 1' failed: 'Error: Command 0xbc33acfffe4e6fd2/1 manuSpecificTuya.dataRequest({\"seq\":0,\"dpValues\":[{\"dp\":20,\"datatype\":4,\"data\":[0]}]}, {\"sendWhen\":\"immediate\",\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":true,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (Data request failed with error: 'No network route' (205))'","meta":{"friendly_name":"Rookmelder voor 1"},"type":"zigbee_publish_error"}'

Log Domoticz (when you swith on alarm in Domoticz): 2022-12-29 20:28:41.489 Error: Zigbee2MQTTServer: A Zigbee publish error occured for device 'Rookmelder voor 1' with error message: Publish 'set' 'alarm' to 'Rookmelder voor 1' failed: 'Error: Command 0xbc33acfffe4e6fd2/1 manuSpecificTuya.dataRequest({"seq":0,"dpValues":[{"dp":20,"datatype":4,"data":[0]}]}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))

[JanvdW304]

It appeared that all my routers were not properly configured after setting up the new coordinator (tested with this. script). I followed this instructions and it works again