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

[JanvdW304]

What happened?

1. I had a working setup with (among others) WOOX R7049 fire alarms
2. Because of frequent corruption of my CC2531 adapter I upgraded to a CC2652RB based adapter (Slaesh's). All Zigbee devices reconnected without problems, except my WOOX R7049 smoke alarm devices. The WOOX devices report 'Offline' availability in the Zigbee2MQTT frontend . The devices can't be controlled, not by Domoticz (2022.2 (build 14880)) and not by the Zigbee2MQTT frontend. On the other hand the last seen status in Domoticz is updated frequently

I tried several things to solve the issue without succes:

• re-pair the WOOX devices
• remove one of devices in the configuration.yaml and deleted the corresponding Domoticz devices. After a restart of Z2M and Domoticz the device was gone. After re-pairing the smoke detector the device is back in the Z2M frontend and new devices were created in Domoticz. Unfortunately the device has still the 'offline' status in Zigbee2MQTT and I can't control the device in Domoticz.
• remove the batteries from a device, placed them back (after a period of time) and re-paired the device.

What can cause this behaviour?

What did you expect to happen?

I expected that the device got the online availability status in Z2M and that I can switch on the alarm in Domoticz

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.25.2-dev commit: [92f7bc8]

Adapter firmware version

20220219

Adapter

Slaesh's CC2652RB stick

Debug log

opt/data/log:
info 2023-01-02 19:04:12: Rookmelder achter 2 (0xbc33acfffe28aee8): R7049 - Woox Smart smoke alarm (EndDevice)
info 2023-01-02 19:04:12: Rookmelder voor 2 (0xbc33acfffe26e32e): R7049 - Woox Smart smoke alarm (EndDevice)
info 2023-01-02 19:04:12: Rookmelder achter 1 (0xbc33acfffe28ae69): R7049 - Woox Smart smoke alarm (EndDevice)
info 2023-01-02 19:04:12: Rookmelder voor 1 (0xbc33acfffe4e6fd2): R7049 - Woox Smart smoke alarm (EndDevice)
info 2023-01-02 19:04:12: Rookmelder hal (0xbc33acfffe5281b4): R7049 - Woox Smart smoke alarm (EndDevice)
info 2023-01-02 19:04:12: Rookmelder keuken (0xbc33acfffe289da7): R7049 - Woox Smart smoke alarm (EndDevice)

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]

I found this solution for similar problems after upgrading from CC2531 and followed the procedure, but that doesn't solve the problem.

In the meantime (2 of 3) motion sensors (Xiaomi RTCGQ01LM) are reported as offline as well; this is after the availability timeout period is passed.

[JanvdW304]

Update: I tried to re-pair one of the IKEA bulbs to see if it has something to do with routing issues (I planned to pair one of the devices close to this bulb to see if it fixes my problem). But now the IKEA bulb is not showing up any more in the Z2M interface. I am lost...

[JanvdW304]

Found the problem, thanks to the post of Fabiancrg; thanks a lot for the nice script!

It appeared that all the routers were not correctly set up. So I removed them all, repaired them and voila: it works