Should I need to re-pair when switching from default to source-routed firmware

Greetings all!

I have a network with mostly powered devices - IKEA Tradfri bulbs and remotes, for the most part. There’s about 15 devices in all. I’ve been having some instability in the CC2531 coordinator (requiring a restart of z2m), and I saw that the source-routed firmware can help with this (sorry, I can’t find the link now, I think it was on one of the z2m GitHub issues)

So, I went ahead and flashed the source-routed firmware. Looking at the logs on startup, the devices are all still present, but z2m can’t actually control any of them. Any attempt to send a command results in this kind of thing:

debug 2019-12-09T22:55:15: Received MQTT message on 'zigbee2mqtt/lounge_bulb_1/set' with data '{"state": "ON", "brightness": 100}'
debug 2019-12-09T22:55:15: Publishing 'set' 'brightness' to 'lounge_bulb_1'
error 2019-12-09T22:55:16: Publish 'set' 'brightness' to 'lounge_bulb_1' failed: 'Error: Data request failed with error: 'No network route' (205)'
info  2019-12-09T22:55:16: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Publish 'set' 'brightness' to 'lounge_bulb_1' failed: 'Error: Data request failed with error: 'No network route' (205)'","meta":{"friendly_name":"lounge_bulb_1"}}'

I had a look at the network diagram via the graphviz endpoint, and it appears that coordinator still has many devices directly attached:

The lounge_bulb_1 device does seem to be connected though…

So, more than 5 devices connected to the coordinator. Do I need to repair devices away from the coordinator, or should the network sort itself out?

I think you need to set ‘permit_join: true’ and let the network sort itself out.

1 Like