Exactly. Thanks for making tha clear. You are correct, migrating them out of the package kind of defeats the reason for having the automations in a package in the first place.
The other issue is that youāll lose your comments when you save it back to YAML, since HA uses JSON internally.
Thatās a good point. I heavily comment my packages. Just the round trip for YAML will remove the comments (Iāve never tried ruamel.yaml?)
Myabe something like vim where it watches the file and alerts you of changes and allows reloading inside the editor? Or just live with how it is, migrate the automation and after testing cut-n-paste it back to the package.
I use the description for commenting in my automations, which isnāt ideal of course. I use alias the same way. I have often thought having comment as part schema that isnāt ever used elsewhere would be nice.
Just made the upgrade from 2025.9.4 to 2025.10.1 on my production instance.
Glad I have a test system so I could mitigate the ever changing frontend.
I checked the breaking changes and didnāt find anything which was going to break my install, however I didnāt check the āall changesā for frontend issues.
2025.10.x broke my card-mod themes due to changes to frontend name changes- yet again!
If it wasnāt for @mariusthvdb and his card_mod themeing github site I would still be looking at the browser dev tool. His examples with correct syntax were invaluable in amending my card mod theme yamls - thank you.
Also, I agree the media player needs the volume + and - buttons back.
Update: now with the correct Marius handle and the link to his site that helped me no end.
4 Likes
When will the slider be fixed?
Totally agreeā¦
has the name logic for the weather card been changed, I now spot this āNoneā
Suppose they want a manual name there? I didnt set that as Knmi is sufficient to me. Dont believe I noticed this before.
not happening on eg Buienradar
trying to redo the entity_ids reveals thisā¦
why? silly this.
Depends on what the integration is doing. Thatās what creates entities. What integration is creating that?
the KNMI integration ā¦ 
itās custom btw.
Yep, youād take this up with them
Otoh, seems HA is suggesting something silly in the naming. Why on earth should it suggest to name something _noneā¦
Makes no sense
naming issue in HA Frontend
opened an issue in the KNMI repo too
I donāt know when this started happening, but the charts on all my sensors are not showing up for some reason
This problem is only happening on the Android companion app. The desktop is showing them fine
Any ideas?
The integration suggests the entity_id, not HA.
Did you try clearing the companion app cacheā¦
Is it just me or has it become really hard to click on volume sliders?
I seem to be accidentally getting the media player card pop-up a lot more than I used to.
4 Likes
I have portainer but am currently not using the integration because the uptima kuma integration basically already gives me all the info plus more
I use the Eshome bang-bang thermostat. After the update, the HomeAssistant Thermostat card no longer displays the set minimum and maximum temperatures.
Refresh your app and browser caches, and check that your device is exposing all the expected entities and are available.
Canāt read the language on your screenshot, but if your Thermostat is in Auto mode, then this is an intended change. See here for more info 2025.10 Thermostat with Auto mode
It has 3 buttons - āheat to a peakā, āswitch off when a peak reachedā, āwarm up a boilerā, perhaps it is related to actual smthā¦