Setting autoheal: false

Configuration Z-Wave
1

How do I set autoheal: false in version 0.89?
I don’t have the zwave: entry in configuration.yaml anymore.
I tried this in core.config_entries:
“data”: {
“network_key”: “xxxx”,
“usb_path”: “xxxx”,
“autoheal”: false
},
But it still performs an autoheal at midnight.

2

You mar want to look in toe config/.storage folder. (yes, the name starts with a ‘.’ making is hidden sometimes)
That is where the “magic” is stored.

3

That’s what I’m doing. The core.config_entries file is in that folder.

4

I assume you restarted HA after any changes.

You could delete the zwave binding & then set it up in the configuration.yaml.

I initially started in the configuration.yaml, deleted it & then went to the Lovelace config.

5

You still use configuration.yaml for settings besides the network_key and usb_path. See the note in the configuration docs.

This is my current config:

zwave:
  autoheal: false
  device_config: !include zwave_device_config.yaml
6

You can, but not if it is also defined through lovelace. HA only permits 1 zwave configuration.

7

Not sure what you mean, but as I mentioned, only the usb_path and network_key are configured by the integration. Everything else is configured in configuration.yaml.

8

I initially had my zwave defined in configuration.yaml and it would not let me configure through lovelace, giving an error.
image

I them deleted the configuration.yaml entries to use the lovelace config. I do not think you can mix them like that,

9

You still use configuration.yaml for settings besides the network_key and usb_path.

10

Thanks @anon34565116 and@freshcoast!
I removed the autoheal from core.config-entries and added
zwave:
autoheal: false
to configuration.yaml yesterday.
And there was no trace of any healing last midnight.
Now I’m curious as to how my system will behave after a few days.

1 Like