I’m a little embarassed to say that having said (on numerous occasions) that I will not be moving forward with new releases here I have in fact done so and (surprise, surprise) I found that (for my config) this release is proving to be (by far) the best release I have moved to since leaving 0.94.2.
I approached this upgrade from a totally different direction than my usual method. Initially I was just interested to see what a new install from scratch was like really and I had no intention of moving my config across. So, I set this up as a brand new docker with a blank /config folder. After the onboarding I switched the new container to a different port so it could run along with my production system (running 0.107.7) on the same network.
# Configure a default setup of Home Assistant (frontend, api, etc)
# Text to speech
- platform: google_translate
||Home Assistant Core on Docker
Once I was satisfied how well it was running I installed a couple of the minor built-in UI installed integrations and let it run for a few days. It ended up running so well I edited the config.yaml to enable lovelace and added my full (unedited) ui-lovelace.yaml and checked how that went.
No problems with all the views except no entities were available due to the config being unpopulated with my config at that time.
So…with my interest pricked I just added my complete config (and a few other required folders)…restarted my container and with great surprise I found literally everything worked with minimal errors and warnings in the log.
The only errors pertained to the one and only ‘custom_component’ I run and that is the safepay Fronius Component.
These errors have existed since 0.107.7 and pertain to not generating unique ID’s.
## Log Details (ERROR)
Integration: Sensor ([documentation](https://www.home-assistant.io/integrations/sensor), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+sensor%22))
First occurred: 7:15:11 PM (9 occurrences)
Last logged: 7:15:11 PM
* Entity id already exists - ignoring: sensor.fronius_ac_current. Platform fronius_inverter does not generate unique IDs
* Entity id already exists - ignoring: sensor.fronius_ac_voltage. Platform fronius_inverter does not generate unique IDs
* Entity id already exists - ignoring: sensor.fronius_ac_frequency. Platform fronius_inverter does not generate unique IDs
* Entity id already exists - ignoring: sensor.fronius_dc_current. Platform fronius_inverter does not generate unique IDs
* Entity id already exists - ignoring: sensor.fronius_dc_voltage. Platform fronius_inverter does not generate unique IDs
So its now been about 5 days and I can not fault how this release is running so ‘hats off’ to all who had anything to do with it really.
I would like to ask the developers to please consider halting the removal of YAML as for me the total removal of YAML functionality would be a dealbreaker to me moving further forward with new releases.
Failing that I would ask you to consider ensuring that Nabu Casa remains 100% compatible with ALL releases back to say 0.90.xx as it seems clear to me that a great many users are still running installations at least back to there. No doubt many of those may also be using Nabu Casa as well?
If at all possible could the quality and quantity of communication between developers and the wider user base be improved significantly as right now it is at an unsustainably low level IMHO.
If you must continue to remove YAML functionality I personally will stop on whatever release suits my purposes best. In fact I am right now working on finding the best place to dig in.
That is of course UNLESS you remove Nabu Casa backwards compatibility as at that point I will totally abandon this project.
Thanks for listening!