Closed Duckle29 closed 3 years ago
This is due to option validation that expects an array https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/blob/dev/zigbee2mqtt/config.json#L124
I will have to check if options allow multiple option types in the schema.
makes sense :) I stuck with the string option for now. I actually never checked if that supports generate, or if it'll cause issues with the key changing on reboots.
Related to https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/issues/39 (new issues should go to new repo)
zigbee2mqtt add-on version (if edge, please report commit hash): 1.17.0.1
Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant): HassOS RPi 4 - 4GB Boot from USB SSD
Description of problem: Setting the network key to "GENERATE" causes saving the config to fail .
Your entire configuration from the frontend (with sensitive fields redacted):
Your logs from Home Assistant
Failed to save addon configuration, not a valid value for dictionary value @ data['options']. Got ...