Closed mackworthy closed 8 months ago
I found a copy of the sniffed key (starting 2a09a64...) in config/zigbee2mqtt/coordinator_backup.json
but couldn't see it anywhere else, so still not sure where it's getting it from, and why it's not loaded from the config/zigbee2mqtt/configuration.yaml
file
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
Description of the issue
I’ve generated and added a network_key to the Zigbee2MQTT config via both the YAML editor in the addon, and manually editing the
config/zigbee2mqtt/configuration.yaml
file via the terminal, and restarted the whole OS, but it does not appear to be using the network key, as the existing devices can still connect and be controlled.To try and debug this further, I’ve sniffed the pairing of a new device and extracted the key in use:
Which does not match the key I set in the config. I’m guessing it's being overridden somewhere else or something. Not sure if this is a bug, or I'm doing something silly!
Addon version
v1.35.3-1
Platform
HassOS v2024.2.2
Logs of the issue (if applicable)
No response