Source Routing Config is not stored properly

deCONZ 3rd Party Integrations
1

I am running deconz on a conbee 2 using the addon of home assistant with a raspberry pi.

Recently i discovered the source routing config, which is really great and improves the stability of my network a lot.

My problem is: the config will never be stored when i either do a restart of the plugin or ha itself.

I read about a config file that i have to change, but i can not even find that file.

I also checked the code of the deconz core and found those settings are only stored on a proper deconstruction of the controller, but i cant not really debug if this is happening when restarting or not.

It would be really great to get this issue solved, as it really decreases my user experience as i have to reset the source routing on every restart and wait for the source routing discovery

2

The configuration from the UI should be stored in the config.ini file.
Is that file writable by deCONZ? Sometimes there are cases where the ownership is root from starting with sudo etc., might be worth to check with ls -l config.ini

The config can also be edited manually while deCONZ is not running.
For example here are my settings for enabled source routing:

[source-routing]
enabled=true
max-hops=5
min-lqi=150
min-lqi-display=0
3

The ha addon probably doesn’t store it in the correct storage.

4

From what i understand, the addon will mainly run deconz in a docker container that has a given deconz version preinstalled (addons/deconz/Dockerfile at master · home-assistant/addons · GitHub)

This is what makes it very hard for me to check and access the config file in the first place. As the other settings are picked up, i assume that either those are corretly stored in the container, and the config file is not, or the other configs are stored in a location that is mapped to the raspbees storage, whereas the location of the config file is not

5

The code is now changed so that source routing configuration changes are stored after a 10 second delay. This should fix the issue that configuration isn’t stored if deCONZ isn’t closed proper.

https://github.com/dresden-elektronik/deconz/commit/4d93d8ff55bc232734445eba3d751815536d0b64

Iirc, the container shouldn’t have problems with write access, this is more a problem in native setups if the file permissions are messed up.

1 Like