Well, there’s not much this time around other than a few changes and some bug fixes.
The notable changes are:
- KNX Climate humidity DPT, thanks to @farmio – Change on GitHub: #155942
- Fix for corrupt restored state in Miele consumption sensors, thanks to @astrandb – #155966
- Handle empty fields in SolarEdge config flow, thanks to @tronikos – Change on GitHub: #155978
- Fix SolarEdge unload failing when there are no sensors, thanks to @tronikos – Change on GitHub: #155979
- Fix Growatt integration authentication error for legacy config entries, thanks to @johanzander – Change on GitHub: #155993
- Fix the exception caused by the missing Foscam integration key @Foscam-wangzhengyu – Change on GitHub: #156022
The breaking changes remain the same as in 2025.11.0:
Set the assumed state to group if at least one child has an assumed state
Previously, the group’s assumed state was always false, regardless of the state of its child entities.
This has now changed:
The group will now have an assumed state of true if at least one child entity has an assumed state.
This makes the group’s assumed state reflect the uncertainty of its children more accurately.
These domains have been added: switch, fan, light, and cover.
Thanks to: @piitaya – Change on GitHub: #154163
Asuswrt
The last_time_reachable attribute has been removed from the asuswrt device tracker.
Use the last_changed attribute instead in your automations.
Thanks to: @ollo69 – Change on GitHub: #154219
LG webOS TV
The state of LG webOS TV media player entities that do not have an automation trigger to turn on the device will be set to unavailable instead of off.
Thanks to: @thecode – Change on GitHub: #155164
Mealie
The mealie Integration now requires Mealie version 2 or later.
Mealie version 1 is no longer supported. Version 2 was released in October 2024, so over a year ago.
Given the differences between versions 1 and 2, we are no longer able to support or test backward compatibility with version 1.
Thanks to: @andrew-codechimp – Change on GitHub: #153203
Motion Blinds
The tilt position of motion_blinds devices have been corrected to align with the Home Assistant standards.
The new tilt position will be: 0 = closed/covering the window opening, 100 = open/letting light through.
The previous tilt position can be converted to the new tilt position as follows:
new=100 - oldcurrent_tilt_position=100 -> 0current_tilt_position=75 -> 25current_tilt_position=50 -> 50current_tilt_position=25 -> 75current_tilt_position=0 -> 100open_cover_tilt->close_cover_tiltclose_cover_tilt->open_cover_tilt
Any automations concerning Motion Blinds devices that use the current_tilt_position attribute or use tilt open/close will need to be adjusted.
Thanks to: @starkillerOG – Change on GitHub: #149777
Mobile App
The mobile_app integration, which supports the iPhone and Android companion apps, now handles zone-only updates better.
When your companion app sends just the zone name (not the exact coordinates), the device tracker will show the zone’s friendly name.
The person entity now shows the zone’s friendly name (not its object ID) for custom zones. This might break existing automations that trigger on a person’s state.
As an example, if you have a zone named zone.kids_school with the friendly name School:
- Before this change, the state of the corresponding
personanddevice_trackerentities would bekids_schoolwhen the “Location Sent” in the companion app was set to send “Zone Name Only” andSchoolwhen it was set to “Exact”. - After this change, the state of the corresponding
personanddevice_trackerentities will beSchoolfor both the “Location Sent” settings in the companion app.
Nederlandse Spoorwegen
The Nederlandse Spoorwegen entity is now displayed as a timestamp entity, rather than a string. Please adapt your automations and scripts.
Thanks to: @joostlek – Change on GitHub: #154011
ONVIF
The Speed parameter in the ONVIF GoToPreset action is now optional.
The default of 0.5 is no longer set. If you want to restore the previous behaviour, you have to set speed to 0.5 in your action.
Thanks to: @carlos-sarmiento – Change on GitHub: #149636
OralB
In the OralB integration, states and attributes have changed.
In multiple places, spaces have been replaced with underscores:
- Toothbrush state:
flight menu→flight_menuselection menu→selection_menufinal test→final_testpcb test→pcb_test
- Brushing mode:
daily clean→daily_cleangum care→gum_caretongue cleaning→tongue_cleaningsuper sensitive→super_sensitivedeep clean→deep_clean
- Pressure:
power button pressed→power_button_pressedbutton pressed→button_pressed
- Sector:
no sector→no_sectorsector 1→sector_1sector 2→sector_2sector 3→sector_3sector 4→sector_4
Automations should be updated to use the new states and attributes.
Thanks to: @tr4nt0r – Change on GitHub: #153605
Renault
The discovery of Renault functionality was previously based on assumptions that may have created invalid and non-functional entities. These will no longer be created.
Thanks to: @epenet – Change on GitHub: #154137
Traccar Server
The Traccar integration has been updated to use a more secure API Token for authentication.
This is a required, one-time breaking change to align with Traccar’s security recommendations and ensure the integration continues to work.
This release migrates the integration away from the older username/password method, ensuring continued stability and security for all users while also allowing users with SSO-based setups to use the integration.
When you update Home Assistant, the existing Traccar integration will need to be re-authenticated:
- Generate an API Token on your Traccar server (you’ll find this option in your Traccar server’s user settings).
- Go to Settings > Devices & Services > Traccar Server.
- Click “Reconfigure” and enter your new API Token when prompted.
Once you’ve done this, your Traccar devices and entities will work exactly as they did before.
Thanks to: @pantherale0 – Change on GitHub: #155297
Xbox
The Account tier and Gold tenure sensors have been retired, as they no longer receive updates following the transition from Xbox Live Gold to Xbox Game Pass.
Additionally, the In party and In multiplayer binary sensors have been removed, since they’ve been non-functional for quite some time.
Thanks to: @tr4nt0r – Change on GitHub: #154891
Remember to at least glance through the breaking changes in case one of your automations or scripts relies on one of them.
Send me a message or comment here if you need any help!
I hope you all have a great day and have fun with Home Assistant!