Tag: Updates

  • Home Assistant 2025.11.2 Update

    We have a bunch of bug fixes in this release!

    @dgomes bumped cronsim to 2.7 in #155648

    @puddly made it so that we avoid firing discovery events when flows immediately create a config entry in #155753 and added firmware flashing debug loggers to hardware integrations in #156480

    @xE1H removed the arbitrary forecast limit for meteo_lt in #155877

    @emontnemery fixed the progress step bugs in #155923, corrected migration to recorder schema 51 in #156267, as well as the checking of collation of statistics_meta DB table in #156327

    @TimoPtr made sure to clean register callbacks when mobile_app reloads in #156028

    @erwindouna bumped pyportainer to 1.0.13 and 1.0.14 in #155783 and  #156072 respectivly

    @TheJulianJES HomeAssistantError logging in ZHA config flow in #156075 and Bump ZHA to 0.0.78 and 0.0.79 in #15593 and #156571 respectivly

    @jrieger bumped aio-ownet to 0.0.5 in #156157

    @abmantis fixed the MFA Notify setup flow schema in #156158

    @farmio updated xknx to 3.10.1 in #156177

    @PaulAnnekov made it so that it is forbidden to choose state in Ukraine Alarm integration in #156183

    @starkillerOGfFixed set_absolute_position angle in #156185 and bumped reolink-aio to 0.16.5  in #156553

    @chemelli74 fixed the config flow reconfigure for Comelit in #156193 and added a debounce to the Alexa Devices coordinator in #156609

    @cdnninja bumped pyvesync to 3.2.1 and 3.2.2 in #156195 and #156423 respectivly

    @mib1185 fixed the Climate state reproduction when the target temperature is None in #156220

    @Foscam-wangzhengyu added a couple of changes to the Foscam Integration by adding Legacy Model Compatibility in #156226 and URL-encoding the RTSP URL in #156488

    @dotvav bumped pypalazzetti lib from 0.1.19 to 0.1.20 in #156249

    @joostlek bumped pySmartThings to 3.3.2 and 3.3.3 in #156250 and #156528 respectivly as well as bumped python-open-router to 0.3.3 in #156563

    @astrandb improved the logging of failing Miele action commands in #156275

    @shmuelzon added to Ituran: Don’t cache properties in #156281

    @rytilahti  added to tplink: handle repeated, unknown thermostat modes gracefully in #156310

    @antoniocifu  fixed support for Hyperion 2.1.1 in #156343

    @Danielhiversen updated pyMill to 0.14.1 in #156396

    @tr4nt0r prevented sensor updates caused by fluctuating “last seen” timestamps in Xbox integration in #156419

    @Bre77 fixed the update progress in Teslemetry in #156422

    @zweckj fixed the Lamarzocco update status in #156442

    @sairon updated the Home Assistant base image to 2025.11.0 in #156517

    @liudger updated bsblan to python-bsblan version 3.1.1 in #156536

    @epenet fixed the sfr_box entry reload in #156593

    @Thomas55555 fixed the model_id in Husqvarna Automower in #156608

    The are no backward-incompatible changes!

    Here’s the normal changelog as well as the full changelog

    Send me a message if you need any help, or join the Home Assistant Community if you are not already a part of it!

    If you missed the patch notes for the major release this month, you can read them here.

    I hope you all have a great day!

  • HA 2025.11.1 Update

    Well, there’s not much this time around other than a few changes and some bug fixes.

    The notable changes are:

    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 - old
    • current_tilt_position = 100 -> 0
    • current_tilt_position = 75 -> 25
    • current_tilt_position = 50 -> 50
    • current_tilt_position = 25 -> 75
    • current_tilt_position = 0 -> 100
    • open_cover_tilt -> close_cover_tilt
    • close_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 person and device_tracker entities would be kids_school when the “Location Sent” in the companion app was set to send “Zone Name Only” and School when it was set to “Exact”.
    • After this change, the state of the corresponding person and device_tracker entities will be School for both the “Location Sent” settings in the companion app.

    Thanks to: @Ashus – Change on GitHub: #149453

    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_menu
      • selection menu → selection_menu
      • final test → final_test
      • pcb test → pcb_test
    • Brushing mode:
      • daily clean → daily_clean
      • gum care → gum_care
      • tongue cleaning → tongue_cleaning
      • super sensitive → super_sensitive
      • deep clean → deep_clean
    • Pressure:
      • power button pressed → power_button_pressed
      • button pressed → button_pressed
    • Sector:
      • no sector → no_sector
      • sector 1 → sector_1
      • sector 2 → sector_2
      • sector 3 → sector_3
      • sector 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:

    1. Generate an API Token on your Traccar server (you’ll find this option in your Traccar server’s user settings).
    2. Go to Settings > Devices & Services > Traccar Server.
    3. 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!

    View the patch notes

    Home Assistant 2025.11 Release Party

    I hope you all have a great day and have fun with Home Assistant!