Open victorhooi opened 3 months ago
Not sure if this is related, but to be sure check this: #23355
rm opt/zigbee2mqtt/data/coordinator_backup.json
systemctl restart zigbee2mqtt.service
Also looks like your port is missing for mqtt.
I have a similar problem running version 1.40.1, trying to change Zigbee adapter from Sonoff USB to SLZB-06 Ethernet and regardless of where I change the settings it always defaults back to using /dev/ttyUSB0. I have tried changing to tcp://slzb-06.local:6638/ in configuration.yaml and via the GUI but it just connects to /dev/ttyUSB0, the GUI switches back instantly but the configuration.yaml file has the correct settings.
configuration.yaml: serial: port: tcp://slzb-06.local:6638 baudrate: 115200 adapter: zstack disable_led: true
GUI:
I have tried removing the coordinator_backup.json but that makes no difference.
What happened?
I have zigbee2mqtt 1.39.0 running in a Docker container.
It is connected to a Ethernet-based Zigbee coordinator device (UZG-01).
I had to power-cycle the UZG-01 device, as I was trying to diagnose an issue with it. This caused the IP address to change, after a while - which then caused my zigbee2mqtt container to repeatedly crash and restart (assumedly because it couldn't open that serial port).
I edited the
/var/opt/zigbee2mqtt/data/configuration.yaml
to point to the new IP address for the UZG-01.However, ever after this, the zigbee2mqtt container is repeatedly crashing.
I checked the logs, and it seems that it's still attempting to find the UZG-01 at the old IP address (10.5.1.45) - even though the configuration.yaml file reflects the new IP address:
It seems for some reason, zigbee2mqtt is not picking up the changed configuration.yaml - and is simply somehow remembering the old IP address somewhere?
What did you expect to happen?
zigbee2mqtt should pickup the changed IP address, and start normally, without crashing.
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.39.0
Adapter firmware version
20240710
Adapter
UZG-01
Setup
Docker container
Debug log
No response