I upgraded to 0.84, and everything went sideways on me. Aside from needing to update my config to use the new spec to indicate I’ve got a yaml already configured, none of my glance cards are working. I’ve had to revert to 0.83 until I can figure this out.
Where can I get a list of the breaking changes? Aside from combing through the release notes (yes, I do read those, but not every pull request). How can I know ahead of time that hitting that update button isn’t going to take my whole system offline?
This is not the first time I’ve been caught off guard by breaking changes (mqtt_json disappeared in this release as well, btw). How do other folks stay up to date without driving themselves crazy trying to fix things at midnight when none of the lights will turn off?
Yes, I get the fact that the solution is most likely written somewhere in the release notes, but sometimes its not that easily found without having to read through the whole documentation. Also, this particular documentation posted links to other documents which posted links to the solution, which made it a somewhat frustrating easter egg hunt to get to the solution. So its kinda nice to be able to come here and ask if some knows how to fix the problem and get a quick answer sometimes. It also helps others who may be new to HA and are not quite sure where to find the answers. I thought that that was whole purpose of having a forum.
Telling people to go look it up is not helpful. If that’s all you can contribute to the thread, then maybe its best not to comment at all…just my opinion.
Eh, you know what… beta is beta. Having to include a “breaking changes” section in your release notes is, I’m sorry, not a cool thing. As a developer of nearly 35 years, things can exist in beta for years, with new features added - or in HA’s case - standardized, but you shouldn’t disable the existing behavior.
Sure, the new way is more consistent with the rest of the system, but was it really necessary to delete the old behavior? I’m working on a picture-entity remote control card, and now, instead of working on the AppDaemon logic, I’ve got to go through and replace 30 tap-taction entries. Yes, I know about search-and-replace, but that’s not the point.
My point isn’t that I “want my money back” from the HA volunteer developers; I’m just asking for a little more respect for the users. It can be done to add the “new & proper” syntax without just breaking the existing syntax and aggravating your users.
If your Linux distro pushed an upgrade and broke a handful of the applications you use on a regular basis, you’d be annoyed. Schedule these breaking changes to be phased out in Version XX.y instead. Give us a chance. Most beta updates add features, not break existing ones.
There is little guidance provided to any users who were previously using mqtt_json lights (which almost all of my lights happen to be, as I’m a prolific DIYer). Yes, I did read through the documentation, and discovered that I’ll need to specify a schema property for each light to set each to JSON.
I’m also a subscriber to the HassIO podcast, and listened to it in depth before applying any updates.
It would be a great addition to provide users with a ‘migration guide’ for any breaking changes they might encounter. I’ll work on putting one together for this release and share it in this thread (once I’ve managed to successfully upgrade to 0.84, which may not be until after the holidays).
I agree. I’ve thought the same thing since v.6x,xx broke all my YAML entries for Broadlink, and finding out that the developers had made a change to the syntax after hours of scouring the internet for a fix.
Now, with that said, do understand that interest of progress or making the YAML more easier to organize, or whatever the reason they decide to make these breaking changes, I do think that sometimes its necessary to make these changes. For example, for the change to Lovelace, we all may be up in arms over the seemingly “unnecessary” change they made to the way we need to code the tap_action, but perhaps in later version, there will be better functionality provided because of this.
But of course, if this all turned out to be something that was done “just because”, well then I think they should really reconsider their change process.
If the document are wrong u can update them also u should read the breaking changes first before updating most changes that made is so that everything line up correctly Eg adding the action to the tap-action make cents cause in automation u have action so it make cent to have it there also
The good thing about lovelace is that unless you are modifying your resources, you don’t need to restart HA after every change. Just click refresh either in the top right of the screen or in the info section. If you get errors you can just modify and refresh till its working.
Totally agree with you mate, I just don’t get people who reply with harsh words… Just don’t reply at all!
Make the world better and help people out, be a good person, treat people with respect as what goes around always comes around