Closed andriej closed 4 years ago
Hey there @mvn23, mind taking a look at this issue as its been labeled with a integration (opentherm_gw
) you are listed as a codeowner for? Thanks!
Thanks for the report, I will have time to take a look later this weekend.
FYI, I attempted to completely remove the OpenTherm gateway entry from configuration.yaml
alltogether and just re-add it using the Integrations panel. However, it will throw the same exception as mentioned above.
Yes, I did the same (threw away YAML) and same error in log so I guess it will be fixed altogether.
Try going through the options flow once, that should get rid of the error for now.
Forgot to add: after going thru it once, it disappeared further on.
Home Assistant release with the issue: 0.101.0 Last working Home Assistant release (if known): n/a (no conflig flow before) Operating environment (Hass.io/Docker/Windows/etc.): linux/venv Integration: https://www.home-assistant.io/integrations/opentherm_gw/ Description of problem: The automatic 'move' from configuration.yaml to config flow throws an error.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: I see the adnotation in docs 'The precision and floor_temperature settings that were supported in configuration.yaml entries have been lost upon import of the configuration.yaml entry into the Integrations panel. You can now configure them as per the following Options paragraph.' although it could be done in informational way, not by error and whole climate entity being unavailable. If it's by design please close the issue