Yes, that seems common. I don’t actually have that much problem with the Configuration menu personally, but that’s how hiding attributes in a collapsed panel happened. One person proposed it, submitted the code to change it, and it added a few to hundreds of clicks per day for hundreds of thousands of Home Assistant installs. It’s nice that features can be added that easily, but it’s a bit scary when changes to the main UI that hide/reduce usability happen so easily.
I wonder if the Customization UI removal was similar or more involved. I can’t customize a lot of sensors any other way, as they don’t support unique IDs. I’m wondering if all template-sensors can be converted to the new style with unique_id’s, but for instance I know filter and rest sensors don’t support it. Have a lot of those…
I am seeing this error in numerous places: TypeError: function() argument 'code' must be code, not str Notify platform (both Alexa & Pushover) as well as Restart Home Assistant, etc., etc.
taking occasion after seeing you are talking about it. Mentioned by you settings has to be set for each device separately. Also each user has to set it on his own.
I suspect it was the easiest way to program, but it starts to be suboptimal while having more users. Asking every user for access to his/her mobile device is hmm awkward.
Don’t you know managing this option centrally by admin for all users regardless a device is under consideration?
Maybe there is some discussion I missed
Remove the alexa_media custom component and then the upgrade will work, I had the exact same issue and reported it on git hub. The log files don’t actually indicate this but it fixed my upgrade issue.
It looks like you aren’t using the built-in rest integration, you’ve overridden it by copying the files into your custom_components folder and there have been changes since you’ve done this which mean your version is not compatible with 2021.12.
You either need to remove your custom version or update it to match the latest code in the official version.