After using and expanding this new Z2M setup for about 1-2 months successfully tonight all stopped working. Rebooting does not help and I do not know where to start…
Is use this stick:
SONOFF ZigBee 3.0 USB Dongle Plus, TI CC2652P Coördinator
The logging:
https://dpaste.org/sQZJH
help me please…
Some things to try:
Oh gosh… why?
Because it’s a Sonoff, and some Sonoff sticks have dodgy NVRAM
Thank you for helping me out! I did it and indeed it is now working back again.
But… this makes me little worried… can this happen again without warning or would this have been a bug in the firmware? I hope things stay stable… I would not want this to happen when away from home longer time…
You have a Sonoff stick you know to be faulty… what do you think?
I don’t know what to think, that’s why I am asking. I bought a spare one. Is it just as easy to replace a faulty stick with a new ond and all will work again?
As in the z2m addon will hold all config, etc?
Well, your current stick is apparently faulty. It’s obvious that it can fail again.
Your spare stick may not be faulty, and Z2M has an FAQ entry about migrating to a new stick.
I guess my question is more or less… is my stick a TI one?
according to this link it should be? But I am not so experienced with Zigbee…
https://www.zigbee2mqtt.io/guide/adapters/
https://www.zigbee2mqtt.io/guide/faq/#how-do-i-migrate-from-one-adapter-to-another
I mean… what you posted says TI … 
I have to come back to this topic… I had to power cycle and now I have no access to my zigbee devices.
I have tried replugging the zigbee sonoff stick, reflashed it but to no avial.
then I have taken a replacement stick, flashed it, copied the IEEE adress and reflashed it again.
But it gives me the same situation as the original stick…
I do not know how to proceed on this. Help :-)…
Logging:
Zigbee2MQTT:info 2023-05-22 22:02:05: Zigbee2MQTT started!
Zigbee2MQTT:error 2023-05-22 22:03:02: Publish 'set' 'state' to 'bol_woonkamer' failed: 'Error: Command 0x0017880108b0a15f/11 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 (Data request failed with error: 'No network route' (205))'
Zigbee2MQTT:error 2023-05-22 22:03:40: Publish 'set' 'state' to 'bol_woonkamer' failed: 'Error: Command 0x0017880108b0a15f/11 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 (Data request failed with error: 'No network route' (205))'
Zigbee2MQTT:error 2023-05-22 22:04:05: Publish 'set' 'brightness' to 'bol_woonkamer' failed: 'Error: Command 0x0017880108b0a15f/11 genLevelCtrl.moveToLevelWithOnOff({"level":76,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
Zigbee2MQTT:error 2023-05-22 22:04:30: Publish 'set' 'brightness' to 'bol_woonkamer' failed: 'Error: Command 0x0017880108b0a15f/11 genLevelCtrl.moveToLevelWithOnOff({"level":165,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
Zigbee2MQTT:error 2023-05-22 22:04:55: Publish 'set' 'brightness' to 'bol_woonkamer' failed: 'Error: Command 0x0017880108b0a15f/11 genLevelCtrl.moveToLevelWithOnOff({"level":193,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
Zigbee2MQTT:error 2023-05-22 22:05:21: Publish 'set' 'brightness' to 'bol_woonkamer' failed: 'Error: Command 0x0017880108b0a15f/11 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
EDIT:
I think it is coming back to life after “randomly” powering main powered devices… is this expected behavior?