• Battlefield 2042: Increased GPU Crashing when calling CDXGISwapChain::Present() [5446395]
• Forza Horizon 4: light flickering on RTX 50 series [5404555]
• Planet Coaster 2: crashes after driver update [5447412]
• FPS significantly drops when using Smooth Motion with RivaTuner FPS cap [5476266]
• R580 drivers causing stuttering in games using GODOT engine [5466820]

• Adobe After Effects / Premiere Pro: crash on launch when Smooth Motion is enabled globally [5515256]
• Adobe Premiere Pro: Some system configurations can freeze during export using hardware encoding [5431822]
• When Video Noise Reduction is enabled the chroma is grayscale [5401959]

Boo! 👻

We just celebrated our birthday 🥳, which means it is time for spooky season; get ready for Halloween! And, hello to the October release of Home Assistant 2025.10! 🎃

This release iterates on some of the features we introduced in the last couple of releases, but also introduces some brand-new ones!

The highlight of this release is definitely the iterations of the automation editor, which gained a sidebar last release, and now has gained undo/redo functionality, a resizable sidebar, improved copy/paste, and more! Thanks for all the feedback you provided on the previous release; it made a massive difference in this release.

Using multiple wake words for voice assistants is now possible, which opens up a lot of possibilities, especially for dual-language households (like mine 😉). Dashboards get more intelligent by suggesting entities based on your usage patterns, and the AI Task can now generate images, which I’m curious to see what the community will do with it!

Enjoy the release!

../Frenck

• Automation editor
  • The sidebar is resizable
  • CTRL+V
  • The overflow menu is back
  • Undo/Redo
  • Repeat repeat repeat repeat
  • Automation editor feedback
• AI Task - Draw me a sheep
• Dashboards get smarter - let your home suggest what to show
• Voice
  • Hello, hola
  • Beep boop
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
• Other noteworthy changes
  • New more information dialog for media player entities
  • Sync zooming charts in the history panel
  • Template & YAML editors get a toolbar
• Patch releases
  • 2025.10.1 - October 3
  • 2025.10.2 - October 10
  • 2025.10.3 - October 17
  • 2025.10.4 - October 24
• Need help? Join the community
• Backward-incompatible changes
• All changes

A huge thank you to all the contributors who made this release possible! And a special shout-out to @JLo, @laupalombi, and @piitaya who helped write the release notes this release. Also, @googanhiem, @SeraphicRav, @tronikos, and @richardpolzer for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️

Automation editor

In the last release, we introduced a new layout for the automation editor, and your feedback has been invaluable in helping us refine it!

This release fixes a few of the most common issues we managed to gather from all of you. Thanks for all the feedback! ❤️

The sidebar is resizable

Working on an action that is too complex for a small sidebar? Maybe one with a few YAML fields? You can now resize the sidebar to adapt the layout to your current task!

CTRL+V

We previously introduced keyboard shortcuts to copy and cut.

Pasting was more complex to bring to life because you can paste a block (trigger, condition, action) in many different locations in your automation. In this release, we introduce a really simple pattern. If you previously copied a block, you can paste it below any block simply by selecting it and pressing CTRL+V.

Another very simple, but very welcome, quality-of-life improvement to the automation editor!

The overflow menu is back

We initially relocated the overflow menu (the menu that appears when you click the ⋮) with all the options related to a block on the sidebar, thinking this would make the flow cleaner.

Due to popular demand and helpful feedback that some actions were more difficult to reach (such as testing a condition or running an action), we decided to bring it back to the main section of the editor as well.

Undo/Redo

We’ve all been there: you’re building a complex automation, make a mistake, and want to revert it, only to find out that it’s really not simple. Up until now, the only way to revert some unsaved changes made to an automation was to close it and start over again… A very painful workflow.

This release introduces an Undo functionality (and its associated Redo). You can now undo up to 75 steps back in your automation editing history (and redo them if you want). Standard keyboard shortcuts (CTRL+Z and CTRL+Y) are also available! An amazing contribution from @jpbede, thanks!

Repeat repeat repeat repeat

Finally, we noticed some unwanted complexity in our “repeat” building block, which allows you to repeat one or multiple actions for as long as you need to.

This complexity stemmed from the fact that we were trying to cover four main use cases in a single block.

We decided to split this building block into four smaller ones, with simpler descriptions explaining each use case. Nice!

Here’s how they were separated:

• Repeat multiple times - Repeat a sequence of actions a fixed number of times.
• Repeat until - Repeat a sequence of actions until a condition is satisfied. The condition is checked after each run of the sequence.
• Repeat while - Repeat a sequence of actions as long as a condition is satisfied. The condition is checked before each run of the sequence.
• Repeat for each - Repeat a sequence for each element of a list.

Automation editor feedback

AI Task - Draw me a sheep

In 2025.8, we introduced a way to generate data using the LLM of your choice, paving the way to more AI-driven automations, dashboards, and other smart home interactions.

In this release, we introduce a way to generate images!

Now every time someone rings your doorbell, you can receive a notification with a cartoon version of the doorbell snapshot. @JLo has made this example a reality, and here’s his demo with the associated automation!

alias: Demo Doorbell
triggers:
  - trigger: state
    entity_id:
      - binary_sensor.doorbell_demo
    to: "on"
actions:
  - action: notify.mobile_app_iphone
    data:
      title: "🔔 Doorbell "
      message: Processing image ...
      data:
        tag: doorbell
  - action: ai_task.generate_data
    data:
      task_name: Doorbell description
      instructions: |-
        Someone rang my doorbell.

        Instructions:
        - Describe the scene, describe every person on the scene
        - Count People
        - Count Animals
      entity_id: ai_task.ai_task_gpt_4o
      structure:
        summary:
          description: >-
            Summary of the scene and the people inside it. Keep it under 180
            characters
          selector:
            text: null
        person_count:
          description: Number of person in the scene
          selector:
            number: null
        animal_count:
          description: Number of animal in the scene
          selector:
            number: null
      attachments:
        media_content_id: media-source://media_source/local/doorbell_test.png
        media_content_type: image/png
        metadata:
          title: doorbell_test.png
          thumbnail: null
          media_class: image
          children_media_class: null
          navigateIds:
            - {}
            - media_content_type: app
              media_content_id: media-source://media_source
    response_variable: ai
  - action: notify.mobile_app_iphone
    data:
      title: >-
        🔔 Doorbell ({{ai.data.person_count}} 🧑🏻‍🦱 / {{ai.data.animal_count}}
        🐊)
      message: "{{ai.data.summary}}"
      data:
        tag: doorbell
  - action: ai_task.generate_image
    data:
      task_name: Manga
      instructions: Transform this image into a super cute manga!
      entity_id: ai_task.google_ai_task
      attachments:
        media_content_id: media-source://media_source/local/doorbell_test.png
        media_content_type: image/png
        metadata:
          title: doorbell_test.png
          thumbnail: null
          media_class: image
          children_media_class: null
          navigateIds:
            - {}
            - media_content_type: app
              media_content_id: media-source://media_source
    response_variable: ai_image
    enabled: true
  - action: notify.mobile_app_iphone
    data:
      title: >-
        🔔 Doorbell ({{ai.data.person_count}} 🧑🏻‍🦱 / {{ai.data.animal_count}}
        🐊)
      message: "{{ai.data.summary}}"
      data:
        tag: doorbell
        image: http://homeassistant.local:8123{{ai_image.url}}
    enabled: true
mode: single

Image generation is already working great, and we cannot wait to see what you will build with this!

Dashboards get smarter - let your home suggest what to show

In the last release, we introduced the Home dashboard, offering a simpler way to control and monitor your smart home if you don’t have the time, energy, or need to customize your own dashboard in detail.

Now we’ve added a new concept: sections of suggested entities. This follows a basic algorithm that suggests entities you have interacted with the most in the past. It then shows these entities based on the hour of the day, with only relevant controls being suggested.

strategy:
  type: common-controls
  title: Common controls

Voice

Hello, hola

For a very long time, ESPHome-based voice assistants (even the tiny Atom Echo) secretly supported multiple wake words under the hood. With this release, we’re finally opening up this feature to you!

You can now define two wake words and two assistants for every voice assistant in your home!

This makes it straightforward to support dual-language households by assigning different wake words to different languages. For example, “Okay Nabu” could be used for French, while “Hey Jarvis” is used for English.

Multiple wake words and assistants can be used for other purposes as well. Want to keep your local and cloud-based voice assistants separate? Easy! “Okay Nabu” could be used for a cloud-based assistant while “Hey Jarvis” is used for a local one.

We’d love to hear feedback on how you plan to use multiple wake words in your home!

Beep boop

After a voice command, Assist responds with a short confirmation like “Turned on the lights” or “Brightness set”. This lets you know that it understood your command and took the appropriate actions. However, if you’re in the same room as the voice assistant, this confirmation can feel redundant since you can see or hear that the appropriate actions were taken.

Starting with this release, Assist will detect if your voice command’s actions all took place within the same area as the satellite device. If so, a short confirmation “beep” will be played instead of the full verbal response. Besides being less verbose, this also serves as a quick reminder that your voice command only affected the current area.

Integrations

Thanks to our community for keeping pace with the new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] and improvements to existing ones! You’re all awesome 🥰

New integrations

We welcome the following new integrations in this release:

• Compit, added by @Przemko92
  The Compit integration allows you to integrate air conditioning, ventilation, and heating controllers with Home Assistant.
• Cync, added by @Kinachi249
  Connect your GE Lighting Cync smart devices—including smart lighting (formerly known as C by GE)—with Home Assistant.
• Droplet, added by @sarahseidman
  Connect your Droplet devices to Home Assistant. Droplet accurately monitors your home’s water usage in real time.
• ekey bionyx, added by @richardpolzer
  Integrate your ekey bionyx biometric access control systems to receive events for individual finger scans and digital inputs in your smart home.
• IRM KMI, added by @jdejaegh
  Get accurate weather data from Belgium’s Royal Meteorological Institute (IRM-KMI) for precise regional forecasting.
• Libre Hardware Monitor, added by @Sab44
  Monitor your computer’s hardware sensors, including CPU temperature, GPU usage, fan speeds, and system performance metrics.
• Portainer, added by @erwindouna
  Manage and monitor your Docker containers, keeping track of the status of your running containers.
• Smart Meter B Route, added by @SeraphicRav
  Connect your smart meter via the B Route protocol—designed for the Japanese market—to access real-time energy consumption data.
• SFTP Storage, added by @maretodoric
  Set up secure remote backup locations using SFTP/SSH protocols for your Home Assistant backups and data storage.
• Usage Prediction, added by @balloob
  An internal integration that provides predictions of what entities you are most likely to interact with. Used by our new Home dashboard.
• Victron Remote Monitoring, added by @AndyTempel
  The Victron Remote Monitoring (VRM) integration pulls site statistics and solar production and consumption forecasts from Victron Energy’s VRM portal.

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have been added; existing integrations are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• Philips Hue expanded with support for MotionAware sensors on the new Hue Bridge Pro! Thanks, @marcelveldt!
• LG added support to the LG ThinQ integration to now provide energy usage sensors for better energy monitoring of your devices! Nice!
• Amazing work from @natekspencer: Litter-Robot got several enhancements: last feeding sensors, food dispensed today tracking, next feeding sensors, gravity mode switch, and globe light settings for Litter-Robot 4!
• AccuWeather now provides hourly forecasts, giving you more detailed weather predictions throughout the day! Thanks, @bieniu!
• The Blue Current integration got a new start charge session action for managing your EV charging! Nice work, @NickKoepr!
• The Ecowitt integration now supports the LDS01 sensor! Great addition, @GSzabados!
• Reolink cameras got several new features including encoding select entity, Home Hub siren support, and color temperature support for light entities! Awesome work from @starkillerOG!
• Geocaching enthusiasts will love the new cache sensors added to the Geocaching integration by @marc7s! Nice if you have hidden one!
• Lutron Caseta now supports multi-tap actions for more advanced button control! Thanks, @rlopezdiez!
• Thanks to @alexqzd, SmartThings air conditioners can now control the AC display light!
• Shelly devices received massive updates including illuminance sensor for Plug US Gen4, presence component entities, virtual buttons support, object-based entities, presence zone component support, and cable unplugged sensor for Flood Gen4! Great work from @chemelli74, @bieniu, and @thecode!
• The SwitchBot integration expanded device support with Plug Mini EU, RelaySwitch 2PM, and K11+ Vacuum! Thanks, @zerzhang!
• The SwitchBot Cloud integration got several improvements including AC off support, humidifier platform, Plug-Mini-EU support, and Climate Panel support! Great work from @SeraphicRav and @XiaoLing-git!
• Thanks to @timmo001, the System Bridge integration now includes a power usage sensor for better system monitoring!
• Exciting to see that the Tasmota integration now supports camera functionality! Nice addition from @anishsane!
• Using the Tibber integration? It now provides 15-minute price data, which goes into effect on October 1st. Good timing, @Danielhiversen!
• The Tuya integration received extensive updates with support for various new device categories and sensors: energy sensors for TDQ devices, power sensors for ZNDB devices, energy sensors for DLQ devices, solar inverter support, energy consumption for several smart switches, PM10 air quality monitoring, motor rotation mode for curtains that support it, charge state for siren alarms, cooking thermometer support, cat toilet support, electric desk support, white noise machine support, and water quality sensor support! What an impressive list! Thanks, @zzysszzy, @rokam, and @mhalano!
• The Workday integration now has a calendar that you can view from the calendar sidebar! Thanks, @gjohansson-ST!
• The ntfy integration got a big upgrade! You can now send richer, customizable notifications with tags, icons, URLs, and attachments. Plus, with the new event platform, you can subscribe to topics and trigger automations from incoming messages. Thanks, @tr4nt0r!

Integration quality scale achievements

One thing we are incredibly proud of in Home Assistant is our integration quality scale. This scale helps us and our contributors to ensure integrations are of high quality, maintainable, and provide the best possible user experience.

This release, we celebrate several integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have improved their quality scale:

• 3 integrations reached platinum 🏆

  • Android TV Remote, thanks to @tronikos
  • Miele, thanks to @astrandb
  • Sleep as Android, thanks to @tr4nt0r

• 2 integrations reached silver 🥈

  • Samsung Smart TV, thanks to @chemelli74
  • Whirlpool Appliances, thanks to @abmantis

• 3 integrations reached bronze 🥉

  • NextDNS, thanks to @bieniu
  • Opower, thanks to @tronikos
  • Sonos, thanks to @PeteRager

This is a huge achievement for these integrations and their maintainers. The effort and dedication required to reach these quality levels is significant, as it involves extensive testing, documentation, error handling, and often complete rewrites of parts of the integration.

A big thank you to all the contributors involved! 👏

Now available to set up from the UI

While most integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] can be set up directly from the Home Assistant user interface, some were only available using YAML configuration. We keep moving more integrations to the UI, making them more accessible for everyone to set up and use.

The following integrations are now available via the Home Assistant UI:

• Nederlandse Spoorwegen (NS), done by @heindrichpaul
• Satel Integra, done by @Tommatheussen

Other noteworthy changes

There are many more improvements in this release; here are some of the other noteworthy changes:

• The “Logbook” has been renamed to “Activity” in the UI. This better reflects its purpose of showing a timeline of activities and events in your Home Assistant instance.
• Matter continues to expand with occupancy sensing hold time, climate running state for heat/cool fans, and thermostat outdoor temperature sensors! Great contributions from @lboue and @virtualbitzz!
• Lawn mower entities now support start mowing and dock intents for better voice control! Thanks, @piitaya!
• The analog clock we introduced last release got some more options! You can now enable a smooth motion for the seconds hand. Beautiful, @timmo001!
• Need the version of the Home Assistant Mobile Companion App you are using? If you have installed the latest versions of our apps, the version is now shown on the about page in the settings menu! Nice one, @TimoPtr!
• The thermostat card now supports water heater entities. Thanks, @karwosts!
• Thanks to @cr7pt0gr4ph7, the add-on configuration UI has gotten support for more complex configurations; this means you will get a better experience when configuring add-ons with more complex options (like lists or user accounts). Well done!
• Talking about add-ons, we now include switch entities for those, making it easier to control your add-ons. Thanks, @felipecrs!
• Using a webhook trigger in your automation? You can now make it even more dynamic by using a template for the webhook_id. Thanks, @RoboMagus!
• We now have support for MCF (1000 Cubic Feet) as an alternate unit of measure for volume, thanks to @ekobres, @xtimmy86x added m/min for speed sensors, and @pioto added inH₂O pressure unit support. Nice!

New more information dialog for media player entities

This one, we have @jpbede and @matthiasdebaat to thank for! The ‘more information’ dialogs for media players have a revamped design, offering a cleaner and more intuitive interface.

Sync zooming charts in the history panel

When you have multiple charts in the history panel, zooming in on one chart will now automatically zoom in on all other charts as well. This makes it easier to compare data across different entities. Well done, @birrejan!

Template & YAML editors get a toolbar

@TCWORLD has contributed a toolbar for the YAML and template code editors in our UI. This solves an issue where the previous floating button would float over the content of the editor and obscure it from view.

The new toolbar also includes undo and redo buttons, bringing the same convenient undo and redo functionality we introduced for the automation editor to these code editors as well. Plus, there’s a nice little copy button to quickly copy your code! Nice!

Patch releases

We will also release patch releases for Home Assistant 2025.10 in October. These patch releases only contain bug fixes. Our goal is to release a patch release once a week, aiming for Friday.

2025.10.1 - October 3

• Bump airOS dependency (@CoMPaTech - #153065)
• Bump airOS module for alternative login url (@CoMPaTech - #153317)
• Bump aiohasupervisor to 0.3.3 (@agners - #153344)
• Do not reset the adapter twice during ZHA options flow migration (@puddly - #153345)
• Fix Nord Pool 15 minute interval (@gjohansson-ST - #153350)
• Explicitly check for None in raw value processing of modbus (@alengwenus - #153352)
• Set config entry to None in ProxmoxVE (@mib1185 - #153357)
• Explicit pass in the config entry to coordinator in airtouch4 (@mib1185 - #153361)
• Add Roborock mop intensity translations (@starkillerOG - #153380)
• Correct blocking update in ToGrill with lack of notifications (@elupus - #153387)
• Bump python-roborock to 2.49.1 (@Lash-L - #153396)
• Pushover: Handle empty data section properly (@linuxkidd - #153397)
• Increase onedrive upload chunk size (@zweckj - #153406)
• Bump pyportainer 1.0.2 (@erwindouna - #153326)
• Bump pyportainer 1.0.3 (@erwindouna - #153413)
• Disable thinking for unsupported gemini models (@Shulyaka - #153415)
• Fix Satel Integra creating new binary sensors on YAML import (@Tommatheussen - #153419)
• Update markdown field description in ntfy integration (@tr4nt0r - #153421)
• Fix Z-Wave RGB light turn on causing rare ZeroDivisionError (@TheJulianJES - #153422)
• Bump aiohomekit to 3.2.19 (@bdraco - #153423)
• Fix sentence-casing in user-facing strings of slack (@NoRi2909 - #153427)
• Add missing translation for media browser default title (@timmo001 - #153430)
• Fix missing powerconsumptionreport in Smartthings (@joostlek - #153438)
• Update Home Assistant base image to 2025.10.0 (@agners - #153441)
• Disable baudrate bootloader reset for ZBT-2 (@puddly - #153443)
• Add translation for turbo fan mode in SmartThings (@joostlek - #153445)
• Fix next event in workday calendar (@gjohansson-ST - #153465)
• Update OVOEnergy to 3.0.1 (@timmo001 - #153476)
• Fix missing parameter pass in onedrive (@zweckj - #153478)
• Bump pyTibber to 0.32.2 (@Danielhiversen - #153484)
• Bump reolink-aio to 0.16.1 (@starkillerOG - #153489)
• Fix VeSync zero fan speed handling (@cdnninja - #153493)
• Bump universal-silabs-flasher to 0.0.35 (@puddly - #153500)
• Debounce updates in Idasen Desk (@abmantis - #153503)
• Z-Wave to support migrating from USB to socket with same home ID (@balloob - #153522)
• When discovering a Z-Wave adapter, always configure add-on in config flow (@balloob - #153575)

2025.10.2 - October 10

• Prevent reloading the ZHA integration while adapter firmware is being updated (@puddly - #152626)
• Wallbox fix Rate Limit issue for multiple chargers (@hesselonline - #153074)
• Fix power device classes for system bridge (@timmo001 - #153201)
• Bump PyCync to 0.4.1 (@Kinachi249 - #153401)
• Updated VRM client and accounted for missing forecasts (@AndyTempel - #153464)
• Bump python-roborock to 2.50.2 (@Lash-L - #153561)
• Bump aioamazondevices to 6.2.8 (@chemelli74 - #153592)
• Switch Roborock to v4 of the code login api (@Lash-L - #153593)
• Fix MQTT Lock state reset to unknown when a reset payload is received (@jbouwh - #153647)
• Gemini: Use default model instead of recommended where applicable (@Shulyaka - #153676)
• Fix ViCare pressure sensors missing unit of measurement (@CFenner - #153691)
• Bump pyvesync to 3.1.0 (@cdnninja - #153693)
• Modbus Fix message_wait_milliseconds is no longer applied (@peetersch - #153709)
• Bump opower to 0.15.6 (@tronikos - #153714)
• Version bump pydaikin to 2.17.0 (@fredrike - #153718)
• Version bump pydaikin to 2.17.1 (@fredrike - #153726)
• Fix missing google_assistant_sdk.send_text_command (@tronikos - #153735)
• Bump airOS to 0.5.5 using formdata for v6 firmware (@CoMPaTech - #153736)
• Align Shelly presencezone entity to the new API/firmware (@bieniu - #153737)
• Synology DSM: Don’t reinitialize API during configuration (@oyvindwe - #153739)
• Upgrade python-melcloud to 0.1.2 (@Sander0542 - #153742)
• Fix sensors availability check for Alexa Devices (@chemelli74 - #153743)
• Bump aioamazondevices to 6.2.9 (@chemelli74 - #153756)
• Remove stale entities from Alexa Devices (@chemelli74 - #153759)
• vesync correct fan set modes (@cdnninja - #153761)
• Handle ESPHome discoveries with uninitialized Z-Wave antennas (@balloob - #153790)
• Fix Tuya cover position when only control is available (@epenet - #153803)
• Bump pySmartThings to 3.3.1 (@joostlek - #153826)
• Catch update exception in AirGradient (@joostlek - #153828)
• Add motion presets to SmartThings AC (@joostlek - #153830)
• Fix delay_on and auto_off with multiple triggers (@Petro31 - #153839)
• Fix PIN validation for Comelit SimpleHome (@chemelli74 - #153840)
• Bump aiocomelit to 1.1.1 (@chemelli74 - #153843)
• Limit SimpliSafe websocket connection attempts during startup (@bachya - #153853)
• Handle timeout errors gracefully in Nord Pool services (@gjohansson-ST - #153856)
• Add plate_count for Miele KM7575 (@derytive - #153868)
• Fix restore cover state for Comelit SimpleHome (@chemelli74 - #153887)
• fix typo in icon assignment of AccuWeather integration (@CFenner - #153890)
• Add missing translation string for Satel Integra subentry type (@Tommatheussen - #153905)
• Do not auto-set up ZHA zeroconf discoveries during onboarding (@TheJulianJES - #153914)
• sharkiq dependency bump to 1.4.2 (@Freebien - #153931)
• Fix HA hardware configuration message for Thread without HAOS (@TheJulianJES - #153933)
• Adjust OTBR config entry name for ZBT-2 (@TheJulianJES - #153940)
• Bump pylamarzocco to 2.1.2 (@zweckj - #153950)
• Bump holidays to 0.82 (@gjohansson-ST - #153952)
• Fix update interval for AccuWeather hourly forecast (@bieniu - #153957)
• Bump env-canada to 0.11.3 (@michaeldavie - #153967)
• Fix empty llm api list in chat log (@arturpragacz - #153996)
• Don’t mark ZHA coordinator as via_device with itself (@joostlek - #154004)
• Filter out invalid Renault vehicles (@epenet - #154070)
• Bump aioamazondevices to 6.4.0 (@chemelli74 - #154071)
• Bump brother to version 5.1.1 (@bieniu - #154080)
• Fix for multiple Lyrion Music Server on a single Home Assistant server for Squeezebox (@peteS-UK - #154081)
• Z-Wave: ESPHome discovery to update all options (@balloob - #154113)
• Add missing entity category and icons for smlight integration (@piitaya - #154131)
• Update frontend to 20251001.2 (@bramkragten - #154143)
• IOmeter bump version v0.2.0 (@jukrebs - #154150)
• Bump deebot-client to 15.1.0 (@edenhaus - #154154)
• Fix Shelly RPC cover update when the device is not initialized (@thecode - #154159)
• Fix shelly remove orphaned entities (@thecode - #154182)

2025.10.3 - October 17

• Bump aioasuswrt to 1.5.1 (@kennedyshead - #153209)
• PushSafer: Handle empty data section properly (@LennartC - #154109)
• Remove redudant state write in Smart Meter Texas (@srirams - #154126)
• Fix state class for Overkiz water consumption (@Yvan13120 - #154164)
• Bump frontend 20251001.4 (@piitaya - #154218)
• Bump aioamazondevices to 6.4.1 (@chemelli74 - #154228)
• Move URL out of Mealie strings.json (@andrew-codechimp - #154230)
• Move URL out of Mastodon strings.json (@andrew-codechimp - #154231)
• Move URL out of Switcher strings.json (@thecode - #154240)
• Remove URL from ViCare strings.json (@CFenner - #154243)
• Fix August integration to handle unavailable OAuth implementation at startup (@bdraco - #154244)
• Fix Yale integration to handle unavailable OAuth implementation at startup (@bdraco - #154245)
• Move url like strings to placeholders for nibe (@elupus - #154249)
• Add description placeholders in Uptime Kuma config flow (@tr4nt0r - #154252)
• Add description placeholders to pyLoad config flow (@tr4nt0r - #154254)
• Fix home wiziard total increasing sensors returning 0 (@jbouwh - #154264)
• Bump pyprobeplus to 1.1.0 (@pantherale0 - #154265)
• Update Snoo strings.json to include weaning_baseline (@dschafer - #154268)
• Move Electricity Maps url out of strings.json (@jpbede - #154284)
• Bump aioamazondevices to 6.4.3 (@chemelli74 - #154293)
• Move URL out of Overkiz Config Flow descriptions (@iMicknl - #154315)
• AsusWRT: Pass only online clients to the device list from the API (@Vaskivskyi - #154322)
• Move Ecobee authorization URL out of strings.json (@ogruendel - #154332)
• Move URLs out of SABnzbd strings.json (@shaiu - #154333)
• Move developer url out of strings.json for coinbase setup flow (@ogruendel - #154339)
• Fix Bluetooth discovery for devices with alternating advertisement names (@bdraco - #154347)
• Bump opower to 0.15.7 (@tronikos - #154351)
• update pysqueezebox lib to 0.13.0 (@wollew - #154358)
• Move URL out of sfr_box strings.json (@epenet - #154364)
• Move translatable URLs out of strings.json for huawei lte (@sonianuj287 - #154368)
• Bump aioairq to 0.4.7 (@Sibgatulin - #154386)
• Bump aiocomelit to 1.1.2 (@chemelli74 - #154393)
• Use async_schedule_reload instead of async_reload for ZHA (@puddly - #154397)
• Move igloohome API access URL into constant placeholders (@DannyS95 - #154430)
• Add missinglong_press entry for trigger_type in strings.json for Hue (@mvdwetering - #154437)
• Move translatable URLs out of strings.json for isy994 (@sonianuj287 - #154464)
• OpenUV: Fix update by skipping when protection window is null (@wbyoung - #154487)
• Bump aioamazondevices to 6.4.4 (@chemelli74 - #154538)
• Move URL out of Nuheat strings.json (@tstabrawa - #154580)
• Bump pyvesync version to 3.1.2 (@cdnninja - #154650)

2025.10.4 - October 24

• Bump aioautomower to v2.3.1 (@Thomas55555 - #151795)
• Fix history coordinator in Tesla Fleet and Teslemetry (@Bre77 - #153068)
• Increase connect and configuration time for rfxtrx (@alec-pinson - #153834)
• Return default temp range if API responds 0 in Huum. (@vincentwolsink - #153871)
• Improve error message for unsupported hardware in Overkiz (@iMicknl - #154314)
• Bump pyprobeplus to 1.1.1 (@pantherale0 - #154523)
• Move translatable URL out of strings.json for airnow integration (@akanksha106-code - #154557)
• Moved non-translatable elements out of strings.json for nuki (@sonianuj287 - #154682)
• Handle location scope in Tesla Fleet vehicle coordinator (@Bre77 - #154731)
• Fix units for Shelly TopAC EVE01-11 sensors (@bieniu - #154740)
• Fix pterodactyl server config link (@electricsteve - #154758)
• Move URL out of Tomorrow.io strings.json (@andrew-codechimp - #154759)
• Move URL out of TheThingsNetwork strings.json (@andrew-codechimp - #154760)
• Move url out of simplisafe strings (@andrew-codechimp - #154762)
• Move url out of sensorpush_cloud strings.json (@andrew-codechimp - #154768)
• Move URLs out of strings.json for auth (@jbouwh - #154769)
• Move url out of starline strings.json (@andrew-codechimp - #154773)
• Move url out of orsoenergy strings.json (@andrew-codechimp - #154776)
• Move url out of motionblinds strings.json (@andrew-codechimp - #154777)
• Move url out of rachio strings.json (@andrew-codechimp - #154781)
• Move url out of Flume strings.json (@andrew-codechimp - #154787)
• Remove opower violation from hassfest requirements check (@cdce8p - #154797)
• Bump opower to 0.15.8 (@tronikos - #154811)
• Move url out of nightscout strings and change to field descriptions (@andrew-codechimp - #154812)
• vesync show fan speed for smart tower fans (@cdnninja - #154842)
• Bump bring-api to v1.1.1 (@tr4nt0r - #154854)
• Bump PyCync to 0.4.2 (@Kinachi249 - #154856)
• Bump aioamazondevices to 6.4.6 (@chemelli74 - #154865)
• YoLink remove unsupported remoters (@matrixd2 - #154918)
• Fix BrowseError import in yamaha_musiccast media_player.py (@wimb0 - #154980)
• Remove async-modbus exception from hassfest requirements check (@cdce8p - #154988)
• Lametric remove translatable URL (@erwindouna - #154991)
• Add SensorDeviceClass and unit for LCN humidity sensor. (@alengwenus - #155044)
• Add shared BleakScanner to probe_plus (@pantherale0 - #155051)
• Improve migration to Uptime Kuma v2.0.0 (@tr4nt0r - #155055)
• Move URL out of system_bridge strings.json (@MichaelMKKelly - #155067)
• Update aioairzone to v1.0.2 (@Noltari - #155088)
• Bump pydroplet version to 2.3.4 (@sarahseidman - #155103)
• Bump holidays to 0.83 (@gjohansson-ST - #155107)

Need help? Join the community

Home Assistant has a great community of users who are all more than willing to help each other out. So, join us!

Our very active Discord chat server is an excellent place to be, and don’t forget to join our amazing forums.

Found a bug or issue? Please report it in our issue tracker to get it fixed! Or check our help page for guidance on more places you can go.

Are you more into email? Sign up for the Open Home Foundation Newsletter to get the latest news about features, things happening in our community, and other projects that support the Open Home straight into your inbox.

Backward-incompatible changes

We do our best to avoid making changes to existing functionality that might unexpectedly impact your Home Assistant installation. Unfortunately, sometimes, it is inevitable.

We always make sure to document these changes to make the transition as easy as possible for you. This release has the following backward-incompatible changes:

If you are a custom integration developer and want to learn about changes and new features available for your integration: Be sure to follow our developer blog. The following changes are the most notable for this release:

• Deprecate hass argument in service helpers
• Improved API for registering platform entity services

All changes

Of course, there is a lot more in this release. You can find a list of all changes made here: Full changelog for Home Assistant Core 2025.10

Every September, we celebrate the anniversary of Home Assistant’s first PR in 2013 – for our 12th birthday, we’re going all in on community again. Last month, we asked for submissions on how Home Assistant helps you, and today we will highlight our favorites! We will also take a look at all the cool milestones over the past year in the project, thanks to contributions from you all, and the new things coming up for the community.

It’s a communal effort

When I (Missy Quarry) joined as the Community & Social Media Manager in February 2024, I was still new to how an open source project the size of Home Assistant manages its community. Over the past 18 months, I’ve seen Home Assistant community members from all walks of life — whether DIY tinkerers or people simply looking to make small improvements at home — contribute in their own ways. By sharing your stories and inspiring others, you’ve helped the project grow.  For our 12th birthday, I want to celebrate these contributions, no matter the size or complexity. 😌

Before I jump into celebrating all your amazing contributions and how they shape the projects managed by the Open Home Foundation, I have a couple of birthday presents for you. 🎁

First, I’m thrilled to share our new Community website! Right now, it’s a simple hub to find community information with ease, but we expect to evolve this over the coming months (or so). You’ll find links to our official community platforms, information on events, and details on meetups, including how to get reimbursed for certain fees as a host. In the future, I’d like to include links to regional communities we’re aware of and showcase more of the kinds of stories I’ll be sharing today.

Feel like something’s missing from this new page? Let me know!

Next, we’ve been working hard to do more of our development in the open. Last September, I redesigned the Discord server and in doing so I gated the Developer category behind a role. This has made it more difficult to develop in the open with the channels hidden behind a role, so we’re switching things up.

As of this week, the Developer category is now read-only for every member. Want to take a peek into the future of Home Assistant? Head to the #projects channel and see what contributors are talking about! Want to join in and contribute with either your feedback or skills? I’ve created an info thread for the channel that explains how to assign yourself either the Developer or Designer role and unlock the ability to chat in the threads.

Let’s jump into those submitted stories now… 🤩

Happily ever after

In my opinion, the best thing about Home Assistant is its flexibility - you can integrate such a wide range of devices into it and use their data to build a unique-to-your-home experience. And that’s exactly why I wanted to hear how you, the community, use it in your own home to benefit you. Here are my favorite stories you submitted - I hope one inspires your next project. ✨

• A coffee automation to improve Home Approval Factor. ☕️ Jordan made a morning automation to avoid having the coffee grinder grind his morning mood.

• u/katschung helped their girlfriend fully accept Home Assistant by creating a dashboard with a retrogame-style floor plan. 🕹️

• Sythsaz uses Home Assistant to make sure their pupper is fed. 🐾 “I’ve managed to make it so my dog’s food auto emails the vet then the response to the email gets put on my calendar so I know how long a bag of food lasts as well as adding the receipts to Google Drive.”

• Inspired by PowerDisplayESPHome, JannickBlmndl made an LED matrix that helps their household be more sustainable by being energy flexible. It displays the live energy prices from their energy provider. 📊

• Tano Spirits in Melbourne, Australia, uses Home Assistant to automate their Japanese Shochu distillery, inspired by a small brewing company in Singapore. 🍻

• Several years ago, HillPhantom found that Home Assistant wasn’t quite ready for him. Over the past year, though, he’s now got Ollama set up with his Home Assistant Voice Preview Edition and has been building guides on how to make your own mmWave radar sensors in Home Assistant. 👋🏻

• Over just a few weeks, Pieter van Kampen recently integrated 190 devices that respond to voice control and more than 1200 active entities from his KNX home to create over 30 automations to help with everything from mowing the lawn to controlling shades based on the sun’s location and intensity. 🪟

• MB used Zigbee buttons to help collect data for their son’s doctor after he developed some trouble sleeping. This gave excellent insight for the doctor to start looking into causes, and they even used the system remotely while doing further evaluation. 📈

• Graham Hosking took automations to another level (before we did) with his AI Automation Suggester and Automation Inspector. It takes the load off your brain by helping come up with new, clever automations! 🤖

• Wessam Lauf fell down the rabbit hole that is Home Assistant once he got his setup running. Inspired by the Graphite theme and after some LLM vibe-coding, he wrote a template for his very own theme, Frosted Glass - now available in HACS. 🎨

• Too many of us anthropomorphize our homes, telling it to chill out when five things break the same day. Biofects took that to heart and created this Home Assistant avatar for his home (here’s a bonus, nightmare fuel first version). 🫣

Developers! 👏🏻 Developers! 👏🏻 Developers! 👏🏻

Our community is more than developers, it’s true. But we wouldn’t be the largest open source project on GitHub if we didn’t have a vibrant and active developer community. This ship sails largely due to their contributions, and we genuinely appreciate all of their efforts.

That’s why we’re eager to interview community members when we open new roles at the foundation. We’ve employed community members like Joostlek (who designed the new Integration Quality Scale and helps onboard new integrations into Core), Timo (who is our first ever Android developer and has focused on polishing the Android app), and Maxim (a talented developer from the Music Assistant community who works on both Music Assistant and ESPHome and is one of our newest additions to the team). Their contributions have helped shape how things work around here, but it was their contributions as community members that helped pave the way for their joining the foundation. These are just a select few of the several new hires at the foundation who were active community members.

(Have you checked our jobs page recently to see what roles are open? 👀)

With our community of contributors and working with Nabu Casa on the hardware design, we have successfully launched a few new pieces of hardware. The Home Assistant Voice Preview Edition brought in language experts from every corner of the world to help ensure our language coverage is the most robust in the industry. Thanks to contributors, we support languages like Greek, Icelandic, and more recently Irish Gaeilge! 😎 We had community contributors help make sure the Home Assistant Connect ZWA-2 was prepared for launch last month. Sincerely, we couldn’t be more grateful for your support and efforts in these spaces.

Here are some fun stats from our GitHub contributors (commits on our Core repo):

• Last 12 months (Sept - Aug) - 14,385
• Previous 12 months - 14,503

A SPECIAL CONGRATULATIONS to bdraco, who just last week surpassed balloob (the founder of Home Assistant) as the contributor with the most commits!

The top 8 contributors of all time in home-assistant/core👏🏻

This is just a small peek into all the hard work that goes into maintaining Home Assistant - we have more repositories than just Core, and every single contribution is valued.

Honorable dev mention from the submitted community stories - I couldn’t leave Joostlek’s (joke) submission out. 🤣

• Our very own Head of Developer Relations (his words), Joost Lekkerkerker, says Home Assistant helps keep him off the street. He’s just launched his new blog that talks about his vision of a smart home, and how he was inspired to not buy Tuya Wi-Fi lights after seeing my experience with some path lights.

Our humble gratitude

Community is the core of what we do and the heart of Home Assistant. We thrive because you care and contribute your valuable time to support our collective success. Whether you found our platform because you wanted more privacy from big tech, were intrigued by the number of choices implemented into a single app, or needed something to track your sustainability efforts — you support our values every day. Thanks for choosing us, and thank you for all you do to help support the foundation and the projects we maintain.

A very special thanks to all our Home Assistant Cloud subscribers and anyone who has purchased our official Home Assistant hardware. These support the full-time development of Home Assistant (along with ESPHome, Music Assistant, and so much more), and are the easiest way to ensure these projects keep getting cool new features!

We have more things coming down the line for you. In the near future, we plan on announcing a new merch store 👕. In the first half of next year, I’ll announce when Home Assistant Community Day 2026 will be. We’re already working with Nabu Casa on the next exciting hardware announcement (no spoilers…for now). And that’s not even touching the industry events we plan on attending, the State of the Open Home, and so much more. I’m excited to take you all on the journey we’re already working on over the next 12 months, and I’m always looking forward to another year of amazing contributions. 😌

• Marvel Rivals: Negative performance impact when using some 581.xx drivers [5444816]

• N/A

Last year, we laid out our vision for AI in the smart home, which opened up experimentation with AI in Home Assistant. In that update, we made it easier to integrate all sorts of local and cloud AI tools, and provided ways to use them to control and automate your home. A year has passed, a lot has happened in the AI space, and our community has made sure that Home Assistant has stayed at the frontier.

We beat big tech to the punch; we were the first to make AI useful in the home. We did it by giving our community complete control over how and when they use AI, making AI a powerful tool to use in the home. As opposed to something that takes over your home. Our community is taking advantage of AI’s unique abilities (for instance, its image recognition or summarizing skills), while having the ability to exclude it from mission-critical things they’d prefer it not to handle. Best of all, this can all be run locally, without any data leaving your home!

Moreover, if users don’t want AI in their homes, that’s their choice, and they can choose not to enable any of these features. I hope to see big tech take an approach this measured, but judging by their last couple of keynotes, I’m not holding my breath.

Over the past year, we’ve added many new AI features and made them easy to use directly through Home Assistant’s user interface. We have kept up with all the developments in AI land and are using the latest standard to integrate more models and tools than ever before. We’re also continuing to benchmark local and cloud models to give users an idea of what works best. Keep reading to check out everything new, and maybe you can teach your smart home some cool new tricks.

Local AI is making the home very natural to control

Big thanks to our AI community contributor team:
@AllenPorter, @shulyaka, @tronikos, @IvanLH, @Joostlek!

Supercharging voice control with AI

We were doing voice assistants before AI was cool. In 2023, we kicked off our Year of the Voice. Since then, we’ve worked towards our goal of building all the parts needed for a local, open, and private voice assistant. When AI became the rage, we were quick to integrate it.

Today, users can chat with any large language model (LLM) that is integrated into Home Assistant, whether that’s in the cloud or run locally via a service like Ollama. Where Assist, our home-grown (non-AI) voice assistant agent, is focused on a predetermined list of mostly home control commands, AI allows you to ask more open-ended questions. Summarize what’s happening across the smart home sensors you’ve exposed to Assist, or get answers to trivia questions. You can even give your LLM a personality!

Users can also leverage the power of AI to speak the way they speak, as LLMs are much better at understanding the intent behind the words. By default, Assist will handle commands first. Only questions or commands it can’t understand will be sent to the AI you’ve set up. For instance, “Turn on the kitchen light” can be handled by Assist, while “It’s dark in the kitchen, can you help?” could be processed by an AI. This speeds up response times for simple commands and makes for a more sustainable voice assistant.

Another powerful addition from the past year is context sharing between agents. So your Assist agent can share the most recent commands with your chosen AI agent. This shared context lets you say something like “Add milk to my shopping list,” which Assist will act on, and to add more items, just say “Add rice.” The AI agent understands that these commands are connected and can act accordingly.

Here is an excellent walkthrough video of JLo's AI-powered home, showing many of these new features in action

Another helpful addition keeps the conversation going; if the LLM asks you a question, your Assist hardware will listen for your reply. If you say something like “It’s dark”, it might ask whether you’d like to turn on some lights, and you could tell it to proceed. We have taken this even further than other voice assistants, as you can now have Home Assistant initiate conversations. For example, you could set up an automation that detects when the garage door is open and asks if you’d like to close it (though this can also be done without AI with a very clever Blueprint).

AI pushed us to completely revamp our Text-to-Speech (TTS) system to take advantage of streaming responses from LLMs. While local AI models can be slow, we use a simple trick to make the delay almost unnoticeable. Now, both Piper (our local TTS) and Home Assistant Cloud TTS can begin generating audio as soon as the LLM produces the first few words, improving the speed of the spoken response by a factor of ten.

Prompt: “Tell me a long story about a frog”

Ollama gemma3:4b on an RTX 3090, and Piper on an i5

Great hardware to work with AI

People built some really cool voice hardware, from landline telephones to little talking robots, but the fact that it was so DIY was always a barrier to entry. To make our voice assistant available to everyone, we released the Home Assistant Voice Preview Edition. This is an easy and affordable way to try Home Assistant Voice. It has some seriously powerful audio processing hardware inside its sleek package. If you were on the fence about trying out voice, it really is the best way to get started.

Voice Preview Edition is not only open and powerful, but it looks and feels great too!

It’s now easier than ever to set up your Assist hardware to work with LLMs with our Voice Assistants settings page, and you can even assign a different LLM to each device. The LLM can recognize the room it’s in and the devices within it, making its responses more relevant. Assist was built to be a great way to control devices in your home, but with AI, it becomes so much more.

AI-powered suggestions

Last month, Home Assistant launched a new opt-in feature to leverage the power of AI when automating with Home Assistant. The goal is to shorten the journey from a blank slate to your finished idea.

When saving an automation or script, users can now leverage the new Suggest button: When clicked, it will send your automation configuration along with the titles of your existing automations and labels to AI to suggest a name, description, category, and labels for your new automation. Over the coming months, we’re going to explore what other features can benefit from AI suggestions.

To opt-in to this feature, you need to take two steps. First, you need to configure an integration that provides an AI Tasks entity. For local AI, you can configure Ollama, or you can also leverage cloud-based AI like Google, OpenAI, or Anthropic. Once configured, you need to go to the new AI Task preferences pane under System -> General and pick the AI Task entity to power suggestions in the UI. If you don’t configure an AI Tasks entity, the Suggest button will not be visible.

AI Tasks gets the job done

Enabling AI Tasks does more than quickly label and summarize your automations; its true superpower is making AI easy to use in templates, scripts, and automations. AI Tasks allow other code to leverage AI to generate data, including options to attach files and define how you want that data output (for instance, a JSON schema).

We have all seen those incredible community creations, where a user leverages AI image recognition and analysis to detect available parking spots or count the number of chickens in the chicken coop. It’s likely that AI Tasks can now help you easily do this in Home Assistant, without the need for complex scripts, extra add-ons, or HACS integrations.

Below is a template entity that counts chickens in a video feed, all via a short and simple set of instructions.

template:
 - triggers:
     - trigger: homeassistant
       event: start
     - trigger: time_pattern
       minutes: "/5"
   actions:
     - action: ai_task.generate_data
       data:
         task_name: Count chickens
         instructions: >-
           This is the inside of my coop. How many birds (chickens, geese, and
           ducks) are inside the coop?
         structure:
           birds:
             selector:
               number:
         attachments:
           media_content_id: media-source://camera/camera.chicken_coop
           media_content_type: image/jpeg
       response_variable: result
   sensor:
     - name: "Chickens"
       state: "{{ result.data.birds }}"
       state_class: total

This template sends a snapshot of the camera to the AI, asking it to analyze what is going on. It defines that the output should always be a number, since we want to use that information in Home Assistant. All of this is embedded in a template entity that automatically updates every 5 minutes. An AI Task could also be embedded in an automation, a script, or any other place that can execute actions.

An automation triggers an AI Task to identify what caused motion on a camera.

Lastly, users can set a default AI Task entity. This allows users to skip picking an entity ID when creating AI automations. It also lets you migrate everything that uses AI Tasks to the latest model with a single click. This also makes it easy to share blueprints that leverage AI Tasks, like this blueprint that analyzes a camera snapshot when motion is detected:

MCP opens a whole new world

Model Context Protocol (MCP) is a thin layer allowing LLMs to integrate anything. When the specification was announced, we quickly jumped on it and integrated it into Home Assistant. Effectively, these servers give Home Assistant’s Assist conversation agent access to all sorts of new tools. You could connect MCP servers that give Assist access to the latest news stories, your to-do lists, or a server that catalogues your vinyl collection, allowing you to have richer conversations (“Okay Nabu, which Replacements albums do I have, and which aren’t on my Vinyl-to-Purchase list?”).

On the flip side, you can also turn Home Assistant into an MCP server, allowing an AI system to access information about your home. For instance, you could create a local AI that’s great at making Home Assistant automations, and it could include all your entity names or available actions. MCP keeps gaining more support, and there are some great cloud and self-hosted solutions available.

How to pick a model

There are a lot of models available, it’s hard to know where to start. Luckily, Home Assistant’s resident AI guru @AllenPorter is here to help. He has put together an incredibly useful Home LLM Leaderboard. This dataset includes his extensive tests of cloud and local LLM options, and even has tests that give small local LLMs a fighting chance (see assist-mini).

Currently, the charts show the big cloud players’ most recent models ranking pretty close to each other, while recent local models that use 8GB or more of VRAM are nearly keeping up. In the past, there was a big disparity between most models, but now it’s hard to go wrong.

This is especially helpful as the options for LLMs in Home Assistant have just grown exponentially with the addition of OpenRouter, a unified interface for LLMs. With OpenRouter, users can access over 400 new models in Home Assistant, and it supports AI Tasks right from day one. We really are spoiled for choice.

The future is Open, and Open Source

Home Assistant is open. We believe that you should be in control of your data, and your smart home. All of it. Local LLMs and the way we have architected Home Assistant extends this choice to the AI space, all while maintaining your privacy.

Most crucially, we’ve made all of this open source. We are community-driven and work on this together with our community. The Open Home Foundation has no investors and is not beholden to anyone but our users. Our work is funded through hardware purchases and Home Assistant Cloud subscriptions, allowing us to make all the technology we build free and open.

Home Assistant 2025.9! 🎉

But before we dive into this release: Did you see we launched a new product? 👀

We’ve introduced the Home Assistant Connect ZWA-2, the ultimate way to connect Z-Wave devices to Home Assistant. You can read all about it in our announcement blog 📰 or re-watch the product launch live stream on YouTube 📺.

It was a busy month, as we also had two new Works with Home Assistant program partners joining this month as well: AirGradient and Frient! 🎉

While the above was happening this month, as if the project wasn’t already busy enough, we kept on pushing to prepare for this release; and it is an absolute massive one! 🤯

This month introduces a new experimental Home dashboard, which aims to become the new default dashboard for Home Assistant in a future release. A first iteration, of which we love to see your feedback and input on. As you know, we develop and iterate in the open. Give it a shot and let us know what you think!

Talking about dashboards, my personal favorite card is definitely the tile card; it is just so versatile. And this release brings in a staggering amount of new features for it! Most notably, the ability to add a trend graph to the tile card! 📈

I’m the most excited about the visual changes to the automation editor this release brings: a sidebar. It is a huge and very visible change, that just makes so much sense. This release denotes the start of a whole series of improvements to the automation editor in this, and upcoming releases. As automations make a smart home feel magical, I personally can’t wait to see how this evolves. 🤖

Enjoy the release!

../Frenck

• Automation editor sidebar
• Introducing the Home dashboard
• New tile card features
  • Trend chart
  • Media player controls
  • Bar gauge
  • Fan direction and oscillation controls
  • Buttons
  • Valve open/close and position controls
  • Setting the date
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
  • Farewell to the following
• Other noteworthy changes
  • Analog clock
  • Storage insights
• Patch releases
  • 2025.9.1 - September 5
  • 2025.9.2 - September 12
  • 2025.9.3 - September 13
  • 2025.9.4 - September 19
• Need help? Join the community!
• Backward-incompatible changes
• All changes

Automation editor sidebar

On this year’s Home Assistant roadmap, we have set the goal of making automations easier to create. We have big plans, all based on tons of research, and with this release… we are shipping the first part of all this work, with the intent to gradually add more improvements over multiple releases!

This release tweaks the automation editor user interface experience by introducing a sidebar! If you select an item in your automation, instead of that item expanding, it will open a new sidebar to the right with the settings for that selected item.

This allows you to keep an overview of your automation on the left side of your screen, while you can tweak its behavior on the right. Of course, we have thought of smaller screens as well. On mobile, instead of the sidebar, a sheet will pop up at the bottom of the screen. This pop-up is also resizable, making it easier than ever to edit an action while reviewing your triggers.

Besides the sidebar, we have made tons of other little improvements as well. Tiny layout and styling changes that you will definitely notice as they really help with the overall readability. For example, small lines and borders around grouped elements have been added, making it easier to distinguish between different parts of your automation. Oh! And drag-and-drop support is now available on mobile! 🎉

Introducing the Home dashboard

Over the past year, we have focused on dashboards and their capabilities a lot. We’ve looked at a lot of your dashboards you’ve shared on socials, and talked to many of you about how you organize all your smart home devices and services. The goal? Making dashboards faster and easier to create, while still making them very customizable.

With this release, we’re introducing a brand-new Home dashboard. The purpose is simple: to give you easy access to the right information at the right time.

The dashboard adapts to your Home Assistant experience level: powerful enough for advanced users, yet approachable for newcomers. We’re working to have it earn its name, and hope it will eventually become your new Home page. As always, it’s optional; you can always pick your own dashboard. This is the first iteration, and we’ll continue developing it in the open.

When you first open the Home dashboard, it gives you a quick way to navigate to useful summaries for your light, climate, security, and media devices. You can also browse by areas, getting an overview of all the devices and services associated with that part of your home.

We’re also introducing Favorites. You can pin any entity to the top, whether it’s a light, climate, or a person. We’d love to see what you choose (more on this in the future).

The Home dashboard is not just about quick control. It also brings insights and information about your home. This first release includes weather and energy cards. It’s a simple start, and we have a lot of ideas to explore with you. For example, helping you create your first automation, or show discovered devices.

For now, the Home dashboard is considered experimental. Configuration options are limited, and it’s guaranteed to evolve. It won’t appear automatically, and if you want to try it you’ll need to add it manually in the dashboard settings, by adding a new “Home” dashboard.

New tile card features

The tile card is the most versatile card we have in our arsenal of cards for our dashboards.

One superpower of the tile card is its “features”, which are small additions where you can add quick interactions to these cards. For example, a slider to control the brightness of a light or buttons for the speed presets of a fan. Features have been extended quite a bit in this release by a dedicated group of community members.

Trend chart

This release, an absolute banger is the addition of the trend chart features for tile cards created by @MindFreeze.

This feature adds a handy quick graph to the tile card, showing the history of a specific entity over time. For this initial version, the time window shown is 24 hours.

Media player controls

@timmo001, added tile card features for media player controls and volume! This makes the tile card now a viable alternative to the media player card. Awesome!

Bar gauge

A new tile card feature, made by @MindFreeze: The bar gauge!

For this initial version, it works with sensors that use a percentage (%) for their unit of measurement. This makes the card great, for example, for a battery overview dashboard. Nice work!

Fan direction and oscillation controls

Thanks to @pcan08 we now have a tile card feature to control fan direction and oscillation!

Buttons

Thanks to @dhoeben we now have a tile card feature for buttons! He added these buttons for automation, script, and button entities. The text can be changed to display standard button text or custom text.

Valve open/close and position controls

Thanks to @timmo001 we now have a tile card feature to control the open/close and the position of valves.

Setting the date

@timmo001 continued and also added a new tile card feature to support date and datetime entities (including the input datetime helpers). It allows you to add a feature that allows for setting a date.

Integrations

Thanks to our community for keeping pace with the new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] and improvements to existing ones! You’re all awesome 🥰

New integrations

We welcome the following new integrations in this release:

• Aladdin Connect, added by @swcloudgenie
  Control and monitor your Genie Aladdin Connect garage doors directly from Home Assistant.
• SEKO PoolDose, added by @lmaertin
  Integrate your SEKO water treatment system of your pool or spa to monitor temperature and chemical levels.
• Sleep as Android, added by @tr4nt0r
  Connects the Sleep as Android app to Home Assistant, allowing you to trigger automations based on alarm clock or sleep cycle events.
• ToGrill Bluetooth BBQ thermometers, added by @elupus
  Connect your ToGrill-compatible Bluetooth grill thermometer and monitor your BBQ efforts to cook steaks to absolute perfection.

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have been added; existing integrations are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• Husqvarna Automower got some nice additions from @Thomas55555! You can now reset cutting blade usage time and track error events with a new event entity. Perfect for keeping track of your lawn mowing robot!
• The Reolink integration now includes speak and doorbell volume controls, plus a chime silent time number entity! Nice @starkillerOG!
• You can now send notifications with the PlayStation Network integration! Send direct messages to your friends! Thanks, @tr4nt0r!
• Network admins will love @Tomeroeni bringing individual (enable/disable) switch port control to UniFi switches!
• The OpenWeatherMap integration now includes a wind gust sensor, thanks to @gjohansson-ST!
• @kizovinh added support for battery status and online status sensors to the EZVIZ integration, making it easier to monitor your EZVIZ cameras. Nice!
• If you own a Russound RIO device, you can now browse your device’s saved presets directly from the media browser! Thanks, @noahhusby!
• @mbo18 added an absolute humidity sensor to the Awair integration. Nice!
• The Teslemetry integration added charging and preconditioning actions for your Tesla vehicle. Thanks, @Bre77!
• @catsmanac added IQ Meter Collar and C6 Combiner support to the Enphase Envoy integration. Good work!

Integration quality scale achievements

One thing we are incredibly proud of in Home Assistant is our integration quality scale. This scale helps us and our contributors to ensure integrations are of high quality, maintainable, and provide the best possible user experience.

This release, we celebrate several integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have improved their quality scale:

• 2 integrations reached platinum 🏆

  • Network UPS Tools (NUT), thanks to @tdfountain
  • Uptime Kuma, thanks to @tr4nt0r

• 1 integration reached bronze 🥉

  • Mastodon, thanks to @andrew-codechimp

This is a huge achievement for these integrations and their maintainers. The effort and dedication required to reach these quality levels is significant, as it involves extensive testing, documentation, error handling, and often complete rewrites of parts of the integration.

A big thank you to all the contributors involved! 👏

Now available to set up from the UI

While most integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] can be set up directly from the Home Assistant user interface, some were only available using YAML configuration. We keep moving more integrations to the UI, making them more accessible for everyone to set up and use.

The following integration is now available via the Home Assistant UI:

• Bayesian, done by @HarvsG

Farewell to the following

The following integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] is no longer available as of this release:

• Uonet+ Vulcan has been removed. Vulcan has changed their API and their policies forbid using the API from unofficial software.

Other noteworthy changes

There are many more improvements in this release; here are some of the other noteworthy changes:

• Based on feature requests from the community, all modern template entity syntax now supports setting a default entity ID directly in YAML. Thanks @Petro31 for implementing that!
• @Petro31 also added support for two new entity types to the template integration. You can now create your own templated event entities and update entities. Awesome!
• Home Assistant now supports m³/min as a volume flow rate unit. Nice addition @fetzerch!
• Our voice guy @synesthesiam has been busy with some great QoL improvements this release as well.
  • The intent handling for the default agent (non-LLM) now supports fuzzy matching. The technique ensures voice pipelines recognize many more sentences. This improvement is available for English only, while we are looking for ways to extend this to other languages.
  • We now have built-in intents to control the volume of (active) media players! Like the song? Just ask Home Assistant to turn it up a notch!
  • After all that dancing, you might have gotten a little warm. Hence in this release, we now also have intents to control fan speeds. Nice!

Analog clock

In Home Assistant 2025.4, we introduced the clock card, which provides a digital clock display for your dashboards.

For this release, @timmo001 made this card more feature-rich by adding support for displaying the clock in a customizable analog clock style. Nice!

Storage insights

Disk almost full? You might wonder where your storage space has gone…

This release adds disk metrics to the storage configuration panel, letting you see usage at a glance, helping you identify what is taking up space.

You can find these metrics by navigating to Settings > System > Storage, or by selecting the My Home Assistant button down below.

Patch releases

We will also release patch releases for Home Assistant 2025.9 in September. These patch releases only contain bug fixes. Our goal is to release a patch release once a week, aiming for Friday.

2025.9.1 - September 5

• Add support for migrated Hue bridge (@marcelveldt - #151411)
• Add missing device trigger duration localizations (@karwosts - #151578)
• Correct capitalization of “FRITZ!Box” in FRITZ!Box Tools integration (@tr4nt0r - #151637)
• Fix Sonos Dialog Select type conversion (@PeteRager - #151649)
• Fix WebSocket proxy for add-ons not forwarding ping/pong frame data (@felipecrs - #151654)
• Fix, entities stay unavailable after timeout error, Imeon inverter integration (@Imeon-Energy - #151671)
• Bump aiohue to 4.7.5 (@marcelveldt - #151684)
• Update frontend to 20250903.3 (@bramkragten - #151694)
• Require OhmeAdvancedSettingsCoordinator to run regardless of entities (@dan-r - #151701)
• Bump ohmepy version to 1.5.2 (@dan-r - #151707)
• Update Mill library 0.13.1 (@Danielhiversen - #151712)
• Handle match failures in intent HTTP API (@synesthesiam - #151726)
• Bump pyschlage to 2025.9.0 (@dknowles2 - #151731)
• Bump bimmer_connected to 0.17.3 (@rikroe - #151756)
• Fix recognition of entity names in default agent with interpunction (@arturpragacz - #151759)
• Fix enable/disable entity in modbus (@janiversen - #151626)

2025.9.2 - September 12

• Fix XMPP not working with non-TLS servers (@Human - #150957)
• Update SharkIQ authentication method (@funkybunch - #151046)
• Add event entity on websocket ready in Husqvarna Automower (@Thomas55555 - #151428)
• Fix Aladdin Connect state not updating (@hbludworth - #151652)
• Fix support for Ecowitt soil moisture sensors (@blotus - #151685)
• Fix update of the entity ID does not clean up an old restored state (@jbouwh - #151696)
• Revert “Jewish Calendar add coordinator “ (@tsvi - #151780)
• Remove device class for Matter NitrogenDioxideSensor (@lboue - #151782)
• Improve config entry migration for edge cases in Alexa Devices (@chemelli74 - #151788)
• Bump habluetooth to 5.3.1 (@bdraco - #151803)
• Fix KNX BinarySensor config_store data (@farmio - #151808)
• Fix KNX Light - individual color initialisation from UI config (@farmio - #151815)
• Mark Tractive switches as unavailable when tacker is in the enegy saving zone (@bieniu - #151817)
• Allow delay > 1 in modbus. (@janiversen - #151832)
• max_temp / min_temp in modbus light could only be int, otherwise an assert was provoked. (@janiversen - #151833)
• removed assert fron entity in modbus. (@janiversen - #151834)
• Bump pydrawise to 2025.9.0 (@dknowles2 - #151842)
• Bump aioharmony to 0.5.3 (@bdraco - #151853)
• Update pysmarty2 to 0.10.3 (@martinssipenko - #151855)
• fix rain sensor for Velux GPU windows (@wollew - #151857)
• Bump aioecowitt to 2025.9.1 (@edenhaus - #151859)
• Use native_visibility property instead of visibility for OpenWeatherMap weather entity (@bieniu - #151867)
• Bump aiontfy to v0.5.5 (@tr4nt0r - #151869)
• Bump aiolifx-themes to 1.0.2 to support newer LIFX devices (@Djelibeybi - #151898)
• Bump aiovodafone to 1.2.1 (@chemelli74 - #151901)
• Avoid cleanup/recreate of device_trackers not linked to a device for Vodafone Station (@chemelli74 - #151904)
• Fix _is_valid_suggested_unit in sensor platform (@epenet - #151912)
• Bump habluetooth to 5.5.1 (@bdraco - #151921)
• Bump bleak-esphome to 3.3.0 (@bdraco - #151922)
• Bump habluetooth to 5.6.0 (@bdraco - #151942)
• Fix invalid logger in Tuya (@epenet - #151957)
• Fix for squeezebox track content_type (@peteS-UK - #151963)
• Fix playlist media_class_filter in search_media for squeezebox (@peteS-UK - #151973)
• Bump habluetooth to 5.6.2 (@bdraco - #151985)
• Bump yt-dlp to 2025.09.05 (@joostlek - #152006)
• Bump accuweather to version 4.2.1 (@bieniu - #152029)
• Fix HomeKit Controller stale values at startup (@bdraco - #152086)
• Fix duplicated IP port usage in Govee Light Local (@abmantis - #152087)
• Fix DoorBird being updated with wrong IP addresses during discovery (@bdraco - #152088)
• Fix supported _color_modes attribute not set for on/off MQTT JSON light (@jbouwh - #152126)
• Fix reauth for Alexa Devices (@chemelli74 - #152128)
• Bump hass-nabucasa from 1.1.0 to 1.1.1 (@ludeeus - #152147)
• Update frontend to 20250903.5 (@bramkragten - #152170)
• Use position percentage for closed status in Velux (@wollew - #151679)

2025.9.3 - September 13

• Bump habluetooth to 5.6.4 (@bdraco - #152227)

2025.9.4 - September 19

• Bump habiticalib to v0.4.4 (@tr4nt0r - #151332)
• Bump habiticalib to v0.4.5 (@tr4nt0r - #151720)
• Fix bug with the hardcoded configuration_url (asuswrt) (@Vaskivskyi - #151858)
• Fix HomeKit Controller overwhelming resource-limited devices by batching characteristic polling (@bdraco - #152209)
• Upgrade waterfurnace to 1.2.0 (@sdague - #152241)
• Bump aiohomekit to 3.2.16 (@bdraco - #152255)
• Bump bluetooth-auto-recovery to 1.5.3 (@bdraco - #152256)
• Add proper error handling for /actions endpoint for miele (@astrandb - #152290)
• Bump aiohomekit to 3.2.17 (@bdraco - #152297)
• Update authorization server to prefer absolute urls (@allenporter - #152313)
• Bump imeon_inverter_api to 0.4.0 (@Imeon-Energy - #152351)
• Bump pylamarzocco to 2.1.0 (@zweckj - #152364)
• Add La Marzocco specific client headers (@zweckj - #152419)
• Fix KNX UI schema missing DPT (@farmio - #152430)
• Bump pyemoncms to 0.1.3 (@alexandrecuer - #152436)
• Fix Sonos set_volume float precision issue (@PeteRager - #152493)
• Bump opower to 0.15.5 (@tronikos - #152531)
• Bump holidays to 0.80 (@gjohansson-ST - #152306)
• Bump holidays to 0.81 (@gjohansson-ST - #152569)
• Bump asusrouter to 1.21.0 (@Vaskivskyi - #151607)

Need help? Join the community!

Home Assistant has a great community of users who are all more than willing to help each other out. So, join us!

Our very active Discord chat server is an excellent place to be, and don’t forget to join our amazing forums.

Found a bug or issue? Please report it in our issue tracker to get it fixed! Or check our help page for guidance on more places you can go.

Are you more into email? Sign up for the Open Home Foundation Newsletter to get the latest news about features, things happening in our community, and other projects that support the Open Home straight into your inbox.

Backward-incompatible changes

We do our best to avoid making changes to existing functionality that might unexpectedly impact your Home Assistant installation. Unfortunately, sometimes, it is inevitable.

We always make sure to document these changes to make the transition as easy as possible for you. This release has the following backward-incompatible changes:

If you are a custom integration developer and want to learn about changes and new features available for your integration: Be sure to follow our developer blog. The following changes are the most notable for this release:

• Standardize encoding of μ in units of measurement
• The DeviceEntry.suggested_area attribute is deprecated and will be removed

All changes

Of course, there is a lot more in this release. You can find a list of all changes made here: Full changelog for Home Assistant Core 2025.9

We’re making new frients this week, and they’re bringing an extensive line of Zigbee devices to our Works With Home Assistant program. Each device is tested by our team, ensuring they provide the best experience possible for Home Assistant. Frient is widely available across Europe, and are well-known for their sleek, unobtrusive designs that its customers love for their high Home Approval Factor.

Our newest frient

Based in Denmark, the frient brand was developed by Onics, (formerly Develco Products), and they have years of experience with Zigbee devices. Frient is bringing its proven technology to the Works With Home Assistant program, as well as their Danish design that easily blends into almost any home.

Recent Works With partners have brought Z-Wave, Matter, and even Bluetooth devices to Home Assistant, but it’s been a couple of years 😅 since Zigbee-specific devices have joined the program. Zigbee is one of the most popular open protocols that is used with Home Assistant, with hundreds of thousands of users making use of it today. It’s a proven technology that connects directly to Home Assistant, no cloud or Wi-Fi connection required. Zigbee is a mesh protocol, where some devices act as repeaters, strengthening the network as more are added. It was built from the ground up to power the smart home, and has been optimized to give devices really long (sometimes multi-year) battery life.

All you need to get started with Zigbee in Home Assistant is a Zigbee adapter or ‘stick’, such as the Home Assistant Connect ZBT-1 (wow, we released this in 2022, I wonder when we’re finally going to build a successor? 😉). By plugging the adapter into a USB port on your Home Assistant system, it should then discover the device and add the ZHA integration. After that is set up, you can start adding devices to your Zigbee network.  We’ve even added in a cool new visualization so that you can see how your Zigbee devices interact with each other.

ZHA is built with the support of the Open Home Foundation, and it even has a full-time developer (@puddly) dedicated to improving it and helping certify new Works With partner devices. Your support makes this possible, whether through a Home Assistant Cloud subscription or by purchasing official hardware.

Devices

When your energy company won’t provide your raw usage data, there’s always another way 😉

In case you didn’t know, Works With Home Assistant differs from other certification programs as products are rigorously tested in-house to ensure they work seamlessly out of the box with Home Assistant. Any company joining also commits to providing long-term support and firmware updates while being a positive force in the Home Assistant community. Works With Home Assistant is operated by the Open Home Foundation, and the support of Home Assistant Cloud subscribers funds this work.

Our team has worked extensively with frient to ensure that the following items work seamlessly with Home Assistant.

• frient Motion Sensor Pro

• frient IO Module

• frient Smart Plug Mini

• frient Entry Sensor 2 Pro

• frient Smart Siren UK

• frient Smart Siren EU

• frient Intelligent Keypad

• frient Water Leak Detector

• frient Smart Button

• frient Intelligent Smoke Alarm

• frient Air Quality Sensor

• frient Smart Humidity Sensor

• frient Electricity Meter Interface 2 LED

This is a big portion of frient’s product line, and provides energy monitoring, device control, safety, and security sensors. The frient IO Module is the first certified Zigbee module that can be used to turn low-voltage dumb devices like electric blinds or garage doors into devices that can be controlled by Home Assistant.

There are some great devices here for building a more sustainable smart home. The Electricity Meter Interface 2 LED allows you to get the data off your energy meter and record it into Home Assistant. Another win for sustainability is their use of AA and AAA batteries wherever practical, meaning you can use rechargeables instead of constantly buying and recycling coin cells.

I also selfishly love to see some great UK-specific devices being brought into the program with the frient Smart Siren having both UK and EU versions.

Best frients forever

It’s great to see Zigbee get some high-quality certified Works With Home Assistant devices after a multi-year wait. Frient has put a good deal of work into this launch and are big fans of our work and the community. There are more exciting Zigbee developments to come, so stay tuned!

FAQs

Q: If I have a device that is not listed under “Works With Home Assistant” does this mean it’s not supported?

A: No! It just means that it hasn’t gone through a testing schedule with our team or doesn’t fit the requirements of the program. It might function perfectly well but be added to the testing schedule later down the road, or it might work under a different connectivity type that we don’t currently test under the program.

Q: Ok, so what’s the point of the Works With program?

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have full functionality within Home Assistant, operate locally without the need for cloud, and will continue to do so long-term.

Q: How were these devices tested?

A: All devices in this list were tested using a standard HA Green Hub with the ZBT-1 and with the ZHA integration. We haven’t tested these devices with Zigbee2MQTT, so we would recommend checking their device compatibility documentation. If you have another hub, Zigbee adapter, or integration, that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.

Q: Will you be adding more frient devices to the program?

A: Why not! We’re thrilled to foster a close relationship with the team at frient to work together on any upcoming releases or add in further products that are not yet listed here.

• Marvel's Avengers - The Definitive Edition: Game crashes to desktop on startup [5350712]

• Certain monitors may display a random flicker when hot plugged over HDMI [5280259]

We’re excited to announce that AirGradient is the latest manufacturer to join the fast-growing Works With Home Assistant program! They bring their air quality monitors to the program, with both indoor and outdoor models.

AirGradient is the first partner in the program focused on building advanced indoor and outdoor air quality monitors. They are also well known within our community for their powerful tech, and for their focus on open source and dedication to local air quality projects around the world.

A breath of fresh air

AirGradient is the first partner to join that operates out of Thailand, and they initially started making their air monitors to help their local community. They actively support air quality improvement projects both in Thailand itself, but also globally. AirGradient donates monitors and has partnered with a variety of different organisations and NGOs, including UNICEF. These monitors are often placed in schools, helping young people to better understand and work to protect their air quality.

An Open Air Monitor in Vietnam

Community is central to our work with AirGradient. Their hardware and software are open source, just like our own. Plus, they’ve taken an active role in integrating into Home Assistant, bringing their local Wi-Fi integration up to not just the gold, but the platinum tier on our integration quality scale. Like all of our Works With partners, the devices work completely locally with no need for a cloud connection. What’s more, they really embrace the DIY aspect of the smart home, with their devices available fully assembled or as a build-it-yourself kit!

AirGradient’s open approach even extends to the data collected by their community of users. Whilst completely optional, users can share their air quality readings with the world (which they visualize into an amazing map). This helpful air quality map grows every time a user opts to share their data, and is a fantastic open resource for climate researchers, students, or anyone concerned about air quality in their local area. If your area is a blank spot on this map, that is all the more reason to buy an AirGradient outdoor monitor.

Each kit comes with a screwdriver and is designed for easy repair. Broken sensor? Swap it out. Firmware update needed? Flash it yourself. Sustainability is one of the core guiding principles of the Open Home Foundation, and we love that repairability is built in. AirGradient also donates at least 1% of annual sales to non-profits and community direct donations. In fact, they asked us to include in this blog an open invitation to our community: If you have a local project that you think would benefit from open source air quality monitors, get in touch through this link.

Certified Devices

In case you’re new to Works With Home Assistant, unlike some certification programs, it’s not just a badge. We rigorously test items in-house and provide feedback to the manufacturers to ensure that products work easily out of the box and provide a seamless experience. The Works With program is operated by the Open Home Foundation and funded by the support of Home Assistant Cloud Subscribers.

AirGradient has certified the following devices with us:  

• AirGradient One - Indoor Air Quality Monitor

• AirGradient Open Air - Outdoor Air Quality Monitor

Finally, a metric to show precisely how badly you burned your dinner

When we talk about sustainability in relation to the smart home, it’s easy to focus on energy management and reducing our carbon impact. However, with AirGradient, you can deep dive into the impacts of the release of CO2 and other air pollutants, better understanding what you, your family, and friends breathe in every day. With an in-house science team of atmospheric chemists and public health experts, they ensure that the monitors are accurate and each of the fully assembled monitors are tested in a dedicated test chamber.

Whether you want to see if your new furniture is putting dangerous VOCs into the air, or if a smelly candle is going to aggravate any allergies, the use cases are endless. The AirGradient One also has a built-in display with both detailed data and a set of LEDs to show general air quality at a glance. Both devices measure carbon dioxide, VOCs, nitrogen oxides, particulate matter, temperature, and humidity. AirGradient also provides helpful documentation on their website that helps you understand these measurements and the impact they can have on your household.

These devices can not only give you in-depth information about the air in and out of your home, but they can also unlock powerful automations. We often see these devices paired with door or window open/close sensors, air purifiers, dehumidifiers, or air conditioners to reduce particulates in the home from pets or carpets.

Clearing the air

We’re so excited to be partnered with AirGradient. Their mission is important, and their open and sustainable approach is precisely what we love to see. Partnerships like this are only possible with the support of Home Assistant Cloud subscribers. Many of us at the Open Home Foundation have picked up AirGradient monitors and are sharing our air quality data today, and we’d love for you to join us on the map!

FAQs

Q: If I have a device that is not listed under Works With Home Assistant, does this mean it’s not supported?

A: No! It just means that it hasn’t gone through a testing schedule with our team or doesn’t fit the requirements of the program. It might function perfectly well, but be added to the testing schedule later down the road, or it might work under a different connectivity type that we don’t currently test under the program.

Q: Ok, so what’s the point of the Works With program?

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have full functionality within Home Assistant, operate locally without the need for cloud and will continue to do so long-term.

Q: How were these devices tested?

A: All devices in this list were tested using a standard HA Green Hub with the local AirGradient integration and a Wi-Fi network. HA will automatically discover them after they join your network (following the device’s instructions to add it to the WiFi). If you have another setup, that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.

Q: Will you be adding more AirGradient devices to the program?

A: Why not! We’re thrilled to foster a close relationship with the team at AirGradient to work together on any upcoming releases or add in further products that are not yet listed here.

• Support for Global DLSS Overrides and NVIDIA Smooth Motion support for GeForce RTX 40 Series GPUs

• Cyberpunk 2077: Crash when using Photo Mode to take a screenshot with path tracing enabled [5076545]
• Marvel Rivals: Negative performance impact when using 580.88 driver [5444816]
• Forza Motorsport: Game crashes if using Smooth Motion while bringing up NVIDIA App overlay statistics [5412757]
• Gray Zone Warfare: Game stability issues [5371781]
• ARK: Survival Ascended: Game stability issues [5441616]

• Potential memory leak when using NVENC hardware encoding [5442678]
• Power cycling monitor can result in monitor flickering when NVIDIA App is installed [5434811]
• NVIDIA App game filter issues after driver update [5429651]

Introducing the Home Assistant Connect ZWA-2, the ultimate way to connect Z-Wave devices to Home Assistant. Between its optimized antenna and seamless integration with Home Assistant, it should be a big upgrade for anyone using Z-Wave today.

If you’re not using Z-Wave, it’s time to take a second look, as Connect ZWA-2 is a different beast. It might be just what you need to reach that tricky spot in your home… or even beyond. Connect ZWA-2 supports Z-Wave Long Range, and this modern take on the standard delivers exceptional reach along with more responsive, battery-efficient devices. Every home is different, but our testers have managed connections in places they once thought impossible.

Join the smart home range revolution for $69 or €59 (that’s the recommended MSRP, and pricing will vary by retailer). For quick details, specs, and where to buy, visit our Home Assistant Connect ZWA-2 page. It’s available for purchase today. Read on to learn what goes into the ultimate Z-Wave upgrade.

We love open standards

Open standards let you connect devices directly to Home Assistant for local, private control, and keep working for years, even if the manufacturer disappears. To make connecting these standards as seamless as possible, we like to build our own hardware.

In late 2022, we launched Home Assistant Connect ZBT-1 (formerly SkyConnect), a USB adapter for Zigbee and Thread. It made both protocols much easier to get started with, and sales helped fund Home Assistant development. We knew the next standard to tackle was Z-Wave, and after another couple of hardware launches (Home Assistant Green and Voice Preview Edition), we finally had the time to do it right.

Why Z-Wave?

If you’re new to Z-Wave, its key advantage over other open standards is its use of sub-GHz radio waves, which are better at getting through thick walls and reaching across large households. While Wi-Fi, Bluetooth, Zigbee, and Thread all compete for the same crowded airspace (2.4 GHz), Z-Wave operates in its own much quieter spectrum (865-926 MHz). Z-Wave is great for range, but its new Z-Wave Long Range variant builds even further on this… but more on that later.

As the standard is over two decades old, it’s had a lot of time to iron out any kinks, but it also has over 4,500 certified devices to choose from. Our opt-in stats show over 130,000 Home Assistant households are using Z-Wave today. Several Works with Home Assistant partners are building amazing Z-Wave products, including Zooz, Shelly, Ultraloq, Leviton, and Homeseer. You can also go to any local marketplace and pick up any working Z-Wave smart device, no matter how old, and it will still connect with Home Assistant!

Connect ZWA-2 in-depth

We’ve learned a lot about hardware since the launch of Connect ZBT-1, and we also knew we could breathe some new life into Z-Wave on Home Assistant. Making this device was the start of us leveling up the Connect platform and establishing our second generation, which is all about building the most performant and open design. That is why we jumped straight to two for this Connect ZWA-2!

Go big or go home

To be the most performant, we knew we had to ditch the “stick” form factor. It was never ideal, as USB ports can output a lot of interference. We even shipped a USB extender with Connect ZBT-1, and urged people to use it, as it kept the device away from any noisy components. Instead of building a stick we built an adapter, which includes an optimized standalone antenna and base that connects to your Home Assistant system with a USB cable.

We’re not compensating for anything; a big antenna does make a big difference. For starters, you need an antenna that’s the right size for your wavelength. As Z-Wave is in the sub-GHz, this means the antenna has to be longer than your average Wi-Fi antenna (about 33 cm or a foot is the sweet spot).

You need to optimize not just the antenna, but also the base of the device (also known as the ground plane). Our hardware experts really went deep into all the physics involved, and the results speak for themselves. Basically, by choosing the right ratio of antenna to base, the two work in harmony to maximize the range and reliability of the signal.

While some Z-Wave adapters may claim they can hit the maximum transmit levels with their postage-stamp-sized antennas, that can sometimes come with a lot of interference. We’ve engineered away that problem. Connect ZWA-2 can speak loudly and clearly 🗣️, and what’s even more important, it’s a great listener 👂.

Positioning is everything

Having a big optimized antenna is great, but placement is almost as important. Its sturdy base and good-sized USB cable allow it to be placed in the right spot. No more will you have a dangling dongle hidden behind a server cabinet. We even put in an accelerometer to ensure people position the antenna upright, this ensures devices are in the sweet spot of the antenna. If you place it on its side, it will subtly blink the status light at the top.

All the Z-Wave

Inside Connect ZWA-2, we include the latest Z-Wave 800 chip, which supports all Z-Wave devices. We’re also Z-Wave certified, giving you that extra peace of mind. This, combined with Home Assistant’s industry-leading Z-Wave software, means Z-Wave has never been this good. On your certified smart devices, you might see Security 2 (S2), SmartStart, Z-Wave Plus, or Z-Wave Plus V2 — don’t worry, we support it all. One new feature we support that is getting people very excited is Z-Wave Long Range👇.

Go long

Combining Z-Wave’s natural abilities with an optimized antenna has given us some impressive range, but we took it a few steps further. We added Z-Wave Long Range to Connect ZWA-2, which might be one of the most substantial updates to Z-Wave yet.

Z-Wave Long Range is different enough that it needs its own separate network. Connect ZWA-2 can run both Z-Wave and Z-Wave Long Range at the same time. When you add a Long Range capable device to Home Assistant, the setup wizard lets you choose which network to use. This way, you get the best of both worlds: a strong mesh network for your older devices, and the reach of Long Range for the newest devices that include support.

How long?

See that bridge in the background? Our prototype connected to a device all the way over there.

People are getting some impressive results with ZWA-2:

• You might have seen our range testing in a previous blog. Since then, we’ve optimized the design and achieved a line-of-sight range of 1.5 kilometers (0.9 miles) 🤯. This was under less than ideal circumstances (raining and within a car), and we think we could go even further.

• The certifying engineer said it was “the best range she had ever seen”.

• Another test had it communicating via Z-Wave Long Range through several floors of concrete.

• Testers with outdoor lights and internal brick walls have commented on how this is the first time they’ve had reliable connections with devices.

• Interesting Long Range use cases have included smart mailboxes that notify you when you’ve got mail, or contact sensors on garden gates.

Every home and setup is different, so we can’t definitively say how far your devices will span. What we can say is that nothing else we’ve tested comes close to what Connect ZWA-2 can do.

Built for Home Assistant

Whenever we build new hardware, we step up our software development to match. You may have noticed a lot of love going into Z-Wave for Home Assistant. All Z-Wave users benefit from this, and when people buy Connect ZWA-2, they’re helping fund this development.

Connect ZWA-2 is built for Home Assistant, and because of this, it’s super easy to get started with. We’ve built Connect ZWA-2 to support every region, no matter where you buy it from. When you plug in Connect ZWA-2, it automatically detects and sets your region using the location configured in your Home Assistant system.

We’ve built handy wizards to help you set up your first Z-Wave network and to guide you in setting up new devices. A wizard also helps you quickly migrate from most Z-Wave adapters to Connect ZWA-2 in a couple of clicks. We also have the ability to update the firmware of Connect ZWA-2 right from Home Assistant, and update the firmware over-the-air (OTA) of Z-Wave devices in a single click.

ESP inside

I’ll save you the time opening it up; here is the front and back of the PCB.

As always, we’ve made Connect ZWA-2 easy to open. Just pop out the rubber feet and remove the four Phillips screws, with no glue or clips to get in the way. If you do open it up, you’ll see a familiar sight, an ESP32-S3. We’re using it as a USB controller, and it’s not running ESPHome. Yes, it does have a “Wi-Fi antenna”, but we’re not using it. We’ve provided a lot of easily accessible pins/pads, open source firmware files, unlocked bootloader, and good documentation, so feel free to tinker. We’ll also provide all the files to allow you to 3D-print the outer casing.

Blending into the home

It’s no small feat to make something 33 cm (1 ft) long look so subtle in the home. We’ve modeled its design after a candle and even used the top of the antenna as a status indicator. Its quality injection-molded exterior has a premium feel and shares many design cues from our sleek-looking Voice Preview Edition.

Join the smart home range revolution

Last year, we proclaimed in a blog that “Z-Wave is not dead”, and this hardware is a testament to that belief. Even with new technologies being released every week, there’s still room to innovate with something tried and tested. We will always support technology that respects your privacy, allows you to control your devices without the cloud, all while keeping the things you already have in your home running for years to come.

After 1600 words on a Z-Wave adapter, we’re obviously very proud of what we’ve built and excited to see what amazing things people will do with this labor of love. So, whether you’re a Z-Wave veteran or just interested in cool new technology, take a look at Home Assistant Connect ZWA-2 today.

• N/A

• Samsung 57" Odyssey Neo G9 Flicker/Underflow when idle at desktop [5361116]
• Some notebook displays may appear dim when an external HDR monitor is connected and display mode is set to "NVIDIA GPU only" [5429667]

Home Assistant 2025.8! 🎉

In most parts of the world, summer mode is in full effect! ☀️ Many at the Open Home Foundation and many of our contributors are enjoying a well-deserved break from work and open source. I hope that you are maybe enjoying a well-deserved break as well! 🏖️

Summer breaks or not, we are currently very busy with our next product launch! In case you have missed it, this upcoming Wednesday, August 13 (12:00 PM PT, 3:00 PM ET, 21:00 CEST), we will have an extra live stream to announce the next big thing in the Home Assistant Connect series! Be sure to head over to YouTube to hit the reminder button so you don’t miss it! Z-Wave is not dead! 🌊

Alright, on to the release! We keep moving during summer and are excited to bring you the August release of Home Assistant!

Let’s start with my personal favorite of this release: The improved experience when viewing a group, for example, a group helper with lights. 💡 When viewing such a group entity, you can now control the individual members of that group directly in that dialog. Super useful! I’m pretty sure that will be used a lot in our house.

But as the release title suggests, this release brings in an important foundation for new AI opportunities in Home Assistant: AI Tasks. Think of it as a way to delegate tasks to AI and get back the result of that task in a structured way so it can be used. Sounds vague? Dive into the release notes below!

Enjoy the release!

../Frenck

• AI in Home Assistant in 2025
  • Streaming Text-to-Speech for Home Assistant Cloud
  • Integrate AI into your workflow using AI Task
  • Work faster with Suggest with AI buttons
• Area dashboard improvements
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
• Other noteworthy changes
  • Control individual members of a group
  • Weekdays in time trigger
  • Energy flow on your energy dashboard
• Patch releases
  • 2025.8.1 - August 11
  • 2025.8.2 - August 15
  • 2025.8.3 - August 21
• Need help? Join the community!
• Backward-incompatible changes
• All changes

AI in Home Assistant in 2025

We introduced our first AI integration in Home Assistant 2023.2 where users could let OpenAI handle their interactions with Home Assistant Voice. Since that time, AI has seen a big surge in popularity within the Home Assistant community for all kinds of use cases. Funny notifications when the laundry is done, analyzing what’s happening on a camera or skipping the song when AI determines it’s a country song 😅.

Though AI gets many people excited, there are still people who would prefer not to have this technology in their smart homes. We want to accommodate everyone’s choices, whether that’s to use AI or not. These features won’t appear unless you set up an AI integration and configure some specific settings.

Last year, we sat down to determine how all these use cases, all complicated to achieve, could be made accessible to everyone. The first thing that came out of this was integration sub-entries, which we shipped in the last release. It allows users to configure their Ollama server or API key for OpenAI once, and then create many different agents using different models or configuration underneath. In this release we’re building two new things you can optionally enable via these new sub-entries for AI integrations: AI tasks and Suggest with AI. We’re also introducing a new integration, OpenRouter, which is a unified LLM interface giving access to over 400 extra LLM models.

Big thanks to our AI community contributors: @AllenPorter, @shulyaka, @tronikos, @IvanLH, and @joostlek!

Streaming Text-to-Speech for Home Assistant Cloud

When you use Home Assistant Voice to talk to an AI, you can do a lot more than just control your home. LLMs can summarize the state of your home, and when using LLMs from Google and OpenAI, they can search the web to answer your questions with up-to-date information. This is great, but these answers can become quite long. Previously, voice responses wouldn’t begin until the AI had finished generating the entire answer, so longer replies meant a longer wait before anything was read aloud.

When a user waits for Home Assistant Voice to respond, long wait times really hurt the experience. We have overhauled Home Assistant so our Text-to-Speech system can start generating the response audio before the full response is done generating. Last release we launched this for Piper, our local Text-to-Speech system. In this release we’re making this available to the voices included in Home Assistant Cloud – the best way of supporting the Home Assistant project.

This improvement will especially benefit users who use local AI (which can be slow in generating responses) or users who play long announcements on their speakers.

Integrate AI into your workflow using AI Task

AI Task is a new integration that allows you to generate data using AI. After you add the “AI Task” sub-entry in your AI of choice, the entity will appear in the integration. This allows you to attach files or cameras and ask it what is happening. The output can either be given in text or formatted in a data structure of your choice. This is all accessible from the new ai_task.generate_data action, which can be embedded in automations, scripts, and template entities.

Below is an example of a template entity that updates every five minutes and counts the number of chickens in the coop. Example inspired by this blog post.

template:
  - triggers:
      - trigger: homeassistant
        event: start
      - trigger: time_pattern
        minutes: "/5"
    actions:
      - action: ai_task.generate_data
        data:
          task_name: Count chickens
          instructions: >-
            This is the inside of my goose coop. How many birds (chickens, geese, and
            ducks) are inside the coop?
          structure:
            birds:
              selector:
                number:
          attachments:
            media_content_id: media-source://camera/camera.chicken_coop
            media_content_type: image/jpeg
        response_variable: result
    sensor:
      - name: "Chickens"
        state: "{{ result.data.birds }}"
        state_class: total

To help get started with AI task, we’ve prepared a blueprint to analyze camera footage:

Work faster with Suggest with AI buttons

The AI Task integration has one extra feature under its belt: default entities. You can go to Settings > System > General and configure what AI Task entity you want to use as the default. With a default set, you no longer have to specify an entity when generating data, making it easier to share blueprints.

Setting a default also does more: When a default is configured, and only then, a new type of button will start showing up in different places in Home Assistant:

This button is not visible by default and will only appear if you enable it in the “AI suggestions” settings. For this release, the button has been added to the save dialog for automations and scripts. It helps users come up with a name, description, category, and label, while taking into account your current labels and other automation/script names. Keep in mind that generating this text sends the full contents of the automation or script, along with the names of your other automations/scripts and labels, to the LLM. So, this may be a task you will want to relegate to your shiny new local LLM.

Area dashboard improvements

We’ve added a small improvement to the areas dashboard based on your feedback. You can now choose to show the first camera in an area, or its image or icon, in the area dashboard editor. It’s a simple way to make certain area cards stand out a bit more—especially handy if you want quicker visual access to specific spaces.

Integrations

Thanks to our community for keeping pace with the new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] and improvements to existing ones! You’re all awesome 🥰

New integrations

We welcome the following new integrations in this release:

• OpenRouter, added by @joostlek
  Access over 400 different large language models through the OpenRouter API, providing a unified interface for AI integrations in your automations.
• Ubiquiti UISP airOS, added by @CoMPaTech
  Monitor and manage airOS devices through their local API, providing performance metrics and device status information of your wireless point-to-point infrastructure.
• Uptime Kuma, added by @tr4nt0r
  Monitor the uptime and status of your services and websites with Uptime Kuma, keeping track of your infrastructure health directly in Home Assistant.
• Volvo, added by @thomasddn
  Connect your Volvo vehicle to Home Assistant for remote monitoring of battery status, location, and other vehicle information.

This release also has new virtual integrations. Virtual integrations are stubs that are handled by other (existing) integrations to help with findability. These ones are new:

• Bauknecht, provided by Whirlpool Appliances, added by @thost96
• Z-Box Hub, provided by Fibaro, added by @rappenze

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have been added; existing integrations are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• The PlayStation Network integration received major updates from @tr4nt0r and @JackJPowell, adding sensors to track your and your friends’ online status, currently playing game, and last online time. Also a binary sensor for your PS Plus subscription status, and a notification platform. PS Vita is now supported as well!
• Reolink cameras got multiple enhancements from @starkillerOG: WiFi signal sensors for IP cameras, post-recording time controls, and pre-recording entities.
• The AI Task and OpenAI Conversation integrations now support camera and file attachments, thanks to @balloob.
• YoLink device support expanded with @matrixd2 adding support for the YS8009, YS7A12, and YS6614 devices.
• @ricohageman added dew point sensors to the Awair integration.
• @bieniu enhanced both GIOS and IMGW PIB integrations with new sensors, including water flow monitoring for IMGW PIB.
• WiZ now supports fans, added by @arturpragacz.
• SwitchBot Cloud gained fan platform support from @XiaoLing-git.
• Velux windows with rain sensors can now detect precipitation, thanks to @wollew.
• SmartThings added vacuum support, implemented by @jennoian.
• AmberElectric now provides forecast services, added by @madpilot.
• OSO Energy got holiday mode services and custom away mode functionality from @osohotwateriot.
• Nord Pool gained normalized price indices service, thanks to @gjohansson-ST.
• Matter continues to expand with microwave oven and temperature control device support from @lboue.
• @noahhusby added play media support to Russound RIO.
• Pi-hole users can now leverage API v6 functionality, enabled by @HarvsG.
• Immich users can now upload files directly through a new action, implemented by @mib1185.
• KNX now includes a new group monitor with improved filtering and search options, thanks to @philippwaller.

Integration quality scale achievements

One thing we are incredibly proud of in Home Assistant is our integration quality scale. This scale helps us and our contributors to ensure integrations are of high quality, maintainable, and provide the best possible user experience.

This release, we celebrate several integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have improved their quality scale:

• 5 integrations reached platinum 🏆

  • AirGradient, thanks to @joostlek
  • inexogy, thanks to @jpbede
  • EHEIM Digital, thanks to @autinerd
  • Pegel Online, thanks to @mib1185
  • Tankerkönig, thanks to @mib1185

• 3 integrations reached silver 🥈

  • Amazon Alexa Devices, thanks to @chemelli74
  • Homee, thanks to @Taraman17
  • Mealie, thanks to @andrew-codechimp

• 2 integrations reached bronze 🥉

  • Onkyo, thanks to @arturpragacz
  • Ring, thanks to @sdb9696

This is a huge achievement for these integrations and their maintainers. The effort and dedication required to reach these quality levels is significant, as it involves extensive testing, documentation, error handling, and often complete rewrites of parts of the integration.

A big thank you to all the contributors involved! 👏

Now available to set up from the UI

While most integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] can be set up directly from the Home Assistant user interface, some were only available using YAML configuration. We keep moving more integrations to the UI, making them more accessible for everyone to set up and use.

The following integration is now available via the Home Assistant UI:

• Datadog, done by @avedor

Other noteworthy changes

There are many more improvements in this release; here are some of the other noteworthy changes:

• Home Assistant’s interface has received a refresh for better accessibility! The primary color and button colors have been updated to meet WCAG AA accessibility standards, improving contrast and readability throughout the interface. All buttons have been redesigned with distinct styles, sizes, and visual priority variants, making it much easier to distinguish between primary, secondary, and less prominent actions. This marks the beginning of a broader effort to update other UI components for improved accessibility and consistency across Home Assistant.
• @mib1185 added a new device class for absolute humidity with support for both sensor and number entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more]. Nice!
• Group management was improved by @piitaya, who added the ability to reorder members within a group, making it easier to organize your device groups exactly how you want them. Thanks!
• System diagnostics was extended by @balloob with the addition of a device analytics dump download feature. Awesome!
• The History Stats integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] now includes a preview in the options flow, thanks to @karwosts. This makes it easier to configure your history statistics.
• The Template integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] received a massive update from @Petro31! Here’s what’s new:
  • Trigger-based numeric sensors can now be set to unknown state
  • The cover, fan, light, lock, and vacuum platforms are now supported in the UI
  • Availability templates are now supported in the UI for all available platforms
  • Preview entity has been added to the UI for alarm control panel and select platforms
  • Template locks now support the opening state
  • The alarm control panel, fan, light, lock, switch, and vacuum platforms now support all optimistic YAML modes

Control individual members of a group

Groups are a great way to control multiple entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] at once, but sometimes you want to control individual members of a group.

So, for this release, @piitaya and @MindFreeze improved the entity information dialog to show the individual members of a light and cover group, allowing you to control them directly from that dialog. Super useful!

Weekdays in time trigger

The time trigger is already very useful, but @hmmbob had a feature request that could improve it even more.

He suggested adding the ability to specify weekdays in the time trigger, allowing users to create automations that only trigger at a specific time on specific days of the week.

This feature has been implemented in this release, allowing you to specify the weekdays in the time trigger. This is especially useful for automations that need to run on specific days, such as weekdays or weekends.

Energy flow on your energy dashboard

The Home Assistant energy dashboard is great, but as of this release it’s even a little better!

Based on the Sankey Chart custom card, @MindFreeze added a new energy flow visualization for the energy dashboard, which shows exactly where your energy is coming from and where it is going to.

Really cool addition to the energy dashboard @MindFreeze!

Patch releases

We will also release patch releases for Home Assistant 2025.8 in August. These patch releases only contain bug fixes. Our goal is to release a patch release once a week, aiming for Friday.

2025.8.1 - August 11

• Make Tuya complex type handling explicit (@epenet - #149677)
• Fix Enigma2 startup hang (@BlackBadPinguin - #149756)
• Fix dialog enhancement switch for Sonos Arc Ultra (@PeteRager - #150116)
• Bump ZHA to 0.0.67 (@puddly - #150132)
• Bump airOS to 0.2.6 improving device class matching more devices (@CoMPaTech - #150134)
• Handle HusqvarnaWSClientError (@Thomas55555 - #150145)
• Fix Progettihwsw config flow (@gaspa85 - #150149)
• Bump imgw_pib to version 1.5.3 (@bieniu - #150178)
• Fix description of button.press action (@NoRi2909 - #150181)
• Migrate unique_id only if monitor_id is present in Uptime Kuma (@tr4nt0r - #150197)
• Silence vacuum battery deprecation for built in integrations (@MartinHjelmare - #150204)
• Bump ZHA to 0.0.68 (@puddly - #150208)
• Bump hass-nabucasa from 0.111.1 to 0.111.2 (@ludeeus - #150209)
• Fix JSON serialization for ZHA diagnostics download (@puddly - #150210)
• Ignore MQTT vacuum battery warning (@MartinHjelmare - #150211)
• Handle Unifi Protect BadRequest exception during API key creation (@RaHehl - #150223)
• Fix Tibber coordinator ContextVar warning (@MartinHjelmare - #150229)
• Fix handing for zero volume error in Squeezebox (@peteS-UK - #150265)
• Fix error on startup when no Apps or Radio plugins are installed for Squeezebox (@peteS-UK - #150267)
• Volvo: fix missing charging power options (@thomasddn - #150272)
• Constraint num2words to 0.5.14 (@edenhaus - #150276)
• Volvo: fix distance to empty battery (@thomasddn - #150278)
• Add GPT-5 support (@Shulyaka - #150281)
• Volvo: Skip unsupported API fields (@thomasddn - #150285)
• Remove misleading “the” from Launch Library configuration (@NoRi2909 - #150288)
• Set suggested display precision on Volvo energy/fuel consumption sensors (@steinmn - #150296)
• Bump airOS to 0.2.7 supporting firmware 8.7.11 (@CoMPaTech - #150298)
• Update knx-frontend to 2025.8.9.63154 (@philippwaller - #150323)
• Update frontend to 20250811.0 (@bramkragten - #150404)
• Handle empty electricity RAW sensors in Tuya (@epenet - #150406)
• Lower Z-Wave firmware check delay (@MartinHjelmare - #150411)
• Fix issue with Tuya suggested unit (@epenet - #150414)

2025.8.2 - August 15

• Add pymodbus to package constraints (@epenet - #150420)
• Fix enphase_envoy non existing via device warning at first config. (@catsmanac - #149010)
• Handle non-streaming TTS case correctly (@synesthesiam - #150218)
• Pi_hole - Account for auth succeeding when it shouldn’t (@HarvsG - #150413)
• Bump habiticalib to version 0.4.2 (@tr4nt0r - #150417)
• Fix optimistic set to false for template entities (@Petro31 - #150421)
• Fix error of the Powerfox integration in combination with the new Powerfox FLOW adapter (@DavidCraftDev - #150429)
• Bump python-snoo to 0.7.0 (@kevin-david - #150434)
• Fix brightness command not sent when in white color mode (@wedsa5 - #150439)
• Bump cookidoo-api to 0.14.0 (@miaucl - #150450)
• Fix YoLink valve state when device running in class A mode (@matrixd2 - #150456)
• Additional Fix error on startup when no Apps or Radio plugins are installed for Squeezebox (@peteS-UK - #150475)
• Fix re-auth flow for Volvo integration (@thomasddn - #150478)
• Improve Z-Wave manual config flow step description (@MartinHjelmare - #150479)
• Add missing boost2 code for Miele hobs (@astrandb - #150481)
• Bump airOS to 0.2.8 (@CoMPaTech - #150504)
• Bump aiowebostv to 0.7.5 (@thecode - #150514)
• Bump bleak-retry-connector to 4.0.1 (@bdraco - #150515)
• Bump aiodhcpwatcher to 1.2.1 (@bdraco - #150519)
• Bump python-snoo to 0.8.1 (@Lash-L - #150530)
• Bump uv to 0.8.9 (@edenhaus - #150542)
• Bump python-snoo to 0.8.2 (@Lash-L - #150569)
• Change Snoo to use MQTT instead of PubNub (@Lash-L - #150570)
• Make sure we update the api version in philips_js discovery (@elupus - #150604)
• Bump pymiele to 0.5.3 (@astrandb - #150216)
• Bump pymiele to 0.5.4 (@astrandb - #150605)
• Bump airOS to 0.2.11 (@CoMPaTech - #150627)
• Bump uiprotect to 7.21.1 (@bdraco - #150657)
• Bump onvif-zeep-async to 4.0.3 (@bdraco - #150663)
• Bump python-snoo to 0.8.3 (@Lash-L - #150670)
• Fix missing labels for subdiv in workday (@gjohansson-ST - #150684)
• Improve handling decode errors in rest (@gjohansson-ST - #150699)

2025.8.3 - August 21

• Bump to zcc-helper==3.6 (@markhannon - #150608) (zimi docs)
• fix(amberelectric): add request timeouts (@JP-Ellis - #150613) (amberelectric docs)
• Bump renault-api to 0.4.0 (@epenet - #150624) (renault docs)
• Update hassfest package exceptions (@cdce8p - #150744)
• Bump boschshcpy to 0.2.107 (@tschamm - #150754) (bosch_shc docs)
• Fix for bosch_shc: ‘device_registry.async_get_or_create’ referencing a non existing ‘via_device’ (@tschamm - #150756) (bosch_shc docs)
• Fix volume step error in Squeezebox media player (@peteS-UK - #150760) (squeezebox docs)
• Show charging power as 0 when not charging for the Volvo integration (@thomasddn - #150797) (volvo docs)
• Pin gql to 3.5.3 (@joostlek - #150800)
• Bump opower to 0.15.2 (@tronikos - #150809) (opower docs)
• Include device data in Withings diagnostics (@joostlek - #150816) (withings docs)
• Abort Nanoleaf discovery flows with user flow (@joostlek - #150818) (nanoleaf docs)
• Bump yt-dlp to 2025.08.11 (@joostlek - #150821) (media_extractor docs)
• Initialize the coordinator’s data to include data.options. (@LG-ThinQ-Integration - #150839) (lg_thinq docs)
• Handle Z-Wave RssiErrorReceived (@MartinHjelmare - #150846) (zwave_js docs)
• Use correct unit and class for the Imeon inverter sensors (@Imeon-Energy - #150847) (imeon_inverter docs)
• Bump holidays to 0.79 (@gjohansson-ST - #150857) (workday docs) (holiday docs)
• Bump aiorussound to 4.8.1 (@noahhusby - #150858) (russound_rio docs)
• Add missing unsupported reasons to list (@agners - #150866) (hassio docs)
• Fix icloud service calls (@epenet - #150881) (icloud docs)
• Bump pysmartthings to 3.2.9 (@joostlek - #150892) (smartthings docs)
• Fix PWA theme color to match darker blue color scheme in 2025.8 (@balloob - #150896) (frontend docs)
• Bump bleak-retry-connector to 4.0.2 (@bdraco - #150899) (bluetooth docs)
• update pyatmo to v9.2.3 (@cgtobi - #150900) (netatmo docs)
• Fix structured output object selector conversion for OpenAI (@balloob - #150916) (openai_conversation docs)
• Matter valve Open command doesn’t support TargetLevel=0 (@kepstin - #150922) (matter docs)
• Bump ESPHome minimum stable BLE version to 2025.8.0 (@bdraco - #150924) (esphome docs)
• Bump imgw-pib to version 1.5.4 (@bieniu - #150930) (imgw_pib docs)
• Fix update retry for Imeon inverter integration (@Imeon-Energy - #150936) (imeon_inverter docs)
• Bump python-mystrom to 2.5.0 (@elsi06 - #150947) (mystrom docs)
• Ask user for Z-Wave RF region if country is missing (@MartinHjelmare - #150959) (zwave_js docs)
• Bump onvif-zeep-async to 4.0.4 (@bdraco - #150969) (onvif docs)
• Except ujson from license check (@emontnemery - #150980)
• Enable country site autodetection in Alexa Devices (@chemelli74 - #150989) (alexa_devices docs)
• Update frontend to 20250811.1 (@bramkragten - #151005) (frontend docs)

Need help? Join the community!

Home Assistant has a great community of users who are all more than willing to help each other out. So, join us!

Our very active Discord chat server is an excellent place to be, and don’t forget to join our amazing forums.

Found a bug or issue? Please report it in our issue tracker to get it fixed! Or check our help page for guidance on more places you can go.

Are you more into email? Sign up for the Open Home Foundation Newsletter to get the latest news about features, things happening in our community, and other projects that support the Open Home straight into your inbox.

Backward-incompatible changes

We do our best to avoid making changes to existing functionality that might unexpectedly impact your Home Assistant installation. Unfortunately, sometimes, it is inevitable.

We always make sure to document these changes to make the transition as easy as possible for you. This release has the following backward-incompatible changes:

If you are a custom integration developer and want to learn about changes and new features available for your integration: Be sure to follow our developer blog. The following changes are the most notable for this release:

• Handling open file limit in add-ons since OS 16
• The media player STANDBY state is deprecated
• The result attribute has been removed from the FlowResult typed dict
• Updated guidelines for helper integrations linking to other integration’s device
• Vacuum battery properties are deprecated

All changes

Of course, there is a lot more in this release. You can find a list of all changes made here: Full changelog for Home Assistant Core 2025.8

We’re excited to welcome Shelly to the Works with Home Assistant program! Shelly is very well-established in both our ecosystem and the smart home world, so it’s great to formally certify a selection of their Z-Wave devices.

Their retrofit smart switches and relays are amazing for turning all sorts of dumb devices, like light fixtures or ceiling fans, into devices you can easily control in smart new ways. Also, being Works with certified means they have been thoroughly tested, ensuring they give the best possible experience with Home Assistant.

The variety of complex settings and functionality, like energy monitoring, makes them popular with our community doing advanced smart retrofits, like connecting an old garage door or motorized shutters. These are perfect for keeping non-smart devices out of the landfill and working for years to come.

From A to Z-Wave

Shelly, originally launched in Bulgaria in 2017, has been a mainstay in our community for some years. They became known initially for their WiFi smart switches and relays that could be easily used locally, but now offer a wide range of smart devices and ways to connect them. For this first round of Works with Home Assistant certified products, the focus is firmly on the Z-Wave lines.

 If you’re not familiar with Z-Wave, it’s a well-established low-powered wireless technology designed with the smart home in mind. It uses an entirely different bit of radio spectrum than WiFi, meaning it has less chance of experiencing interference. This spectrum makes it better at getting through thick walls and communicating over longer distances — with the recent Long Range iteration of the standard, they can communicate even further.

Given our focus on local control, items that work on Z-Wave are ideal if you want to avoid the cloud. Home Assistant will act as your Z-Wave controller using the Z-Wave JS add-on (another awesome Open Home Foundation project). So, all you need is a Z-Wave adapter to use alongside these devices. If you haven’t purchased one yet, you might want to wait before hitting that buy button 😉.

Shelly shares our focus on interoperability, with items using a variety of protocols, while being available worldwide. These items are also super helpful for the energy-conscious. They have low power consumption, power metering, and can easily blend in with your current home decor, as they sit in the wall behind your existing switches.

Mini? This thing is microscopic!

Getting Involved

We’ve been lucky enough to meet the Shelly team on several occasions, and they were kind enough to showcase how the Las Vegas Mob Museum uses Shelly and Home Assistant during our annual ‘State of the Open Home’ event. In May, they went one step further and hosted one of our Community Days in South Florida. It’s really exciting to see that partners who join the ‘Works with’ program don’t just see it as a badge to stick on a box, but a real chance to engage with, and contribute to, this amazing community.

Devices

In case you didn’t know, Works with Home Assistant differs from other certification programs as products are rigorously tested in-house to ensure they work seamlessly out of the box. Any company joining also commits to providing long-term support and firmware updates while being a positive force in the Home Assistant community. Works with Home Assistant is operated by the Open Home Foundation, and the support of Home Assistant Cloud subscribers funds this work.

What devices have been certified?

• Shelly Wave PM Mini

• Shelly Wave i4

• Shelly Wave 1PM Mini

• Shelly Wave 2PM

• Shelly Wave Pro 1PM

Whilst the Shelly Wave Pro 1PM sits in an electrical box, the remaining devices sit behind a standard plug, switch or device. This means they are a super cost-effective way to retrofit devices, which in turn reduces e-waste. The Minis are very small (duh), and so should fit in most tight places around the home, even with low-profile installations. The Shelly Wave 1PM Mini is the world’s smallest Z-Wave smart switch. In some areas of the world, you may need professional installation by a qualified electrician, so be sure to check your region’s regulations. If you’re a confident DIYer, Shelly has a lot of helpful guides on their site to walk you through installing it yourself.

The first of many waves

These devices are the first from Shelly to join the program, but certainly won’t be the last, as we look forward to many exciting developments with Z-Wave Long Range. Keep your eyes peeled for our upcoming hardware announcement that will work perfectly with our Z-Wave partners.

Thanks again for your support (by subscribing to Home Assistant Cloud and buying official hardware), which allows the Open Home Foundation to build these partnerships and certify new devices to join Works with Home Assistant.

FAQs

Q: If I have a device that is not listed under ‘Works with Home Assistant does this mean it’s not supported?

A: No! It just means that it hasn’t gone through a testing schedule with our team yet or doesn’t fit the requirements of the program. It might function well but be added to the testing schedule later down the road, or it might work under a different connectivity type that we don’t currently test under the program. It may also have a feature missing in Home Assistant that we’re working to add.

Q: Ok, so what’s the point of the Works with program?

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must work well within Home Assistant, operate locally without the need for cloud and will continue to do so long-term.

Q: How were these devices tested?

A: All devices in this list were tested using a standard HA Green Hub, a Z-Wave adapter and with our Z Wave integration. If you have another hub / adapter / integration that’s not a problem but we test against these as they are the most effective way for our team to certify within our ecosystem.

Q: Will you be adding more Shelly devices to the program?

A: Absolutely. Shelly has a huge number of product lines and will be expanding their Z-Wave Long Range list. We’re sure they’ll keep our testers busy with a steady stream of devices to add.

The Home Assistant companion app for Android just keeps getting better with every release, and recently, it gained some dedicated support to help accelerate its development. Several months ago, I (Timothy Nibeaudeau, also known as @TimoPtr) joined the Open Home Foundation as our dedicated Android developer 🎉.

It’s been over two years, and hundreds of thousands of installs, since we’ve published a dedicated update for our community on the development of the app, and I’d like to give you a quick update on recent improvements and what’s coming next.

Behind the Screens

In the beginning, all of Home Assistant’s official companion apps were developed by the community in their spare time, with many still being part-time projects. It’s incredible the work they put into building these apps. This gives you not just the ability to view your Home Assistant instance on the go (or around the house) and takes advantage of many of the sensors available on the device while providing rich notifications to users.

Very impressive growth in installs over the years!

The Android app alone has seen over 2,700 contributions! It’s a lot of work keeping up with Android versions, new capabilities of Home Assistant, and bug fixes. This app doesn’t just support Android phones and tablets but also devices they connect to, specifically Android Auto, Android Automotive, and Wear OS.

Progress in the millions

They did all this work while reaching nearly 1.5 million installs, with over 6 million total installs over the years. There are 400,000 daily active users and 1 million monthly active users. The phone app also has a very nice 4.3-star rating on the Play Store and 2,800 stars on GitHub 🤩. This feedback really helps us improve.

It’s been over a year and a half since the Apple companion apps gained a full-time developer with the addition of the amazing Bruno Pantaleão 😎. Around the same time as Bruno was hired, we began looking for an Android developer, and let’s say that took a little longer.

My name is Timothy Nibeaudeau, and as mentioned at the start, I’m your new dedicated Android engineer. As someone who has been using Home Assistant since 2018, I’m passionate about open source and smart home technology. I’ve been working in software development for nearly a decade, developing apps for all sorts of projects from medical-grade IoT products to smart toothbrushes 🪥.

I am committed to bringing my talents to the project, but I cannot do it alone. The community is what makes Home Assistant special, and together, we can achieve even more. Specifically, I’d like to thank @dshokouhi, @jpelgrom, and @JBassett for their years of work making this app what it is today!

I’d also like to thank you! Your support (by subscribing to Home Assistant Cloud and buying official hardware) allows the Open Home Foundation to hire dedicated developers. Dedicated developers keep development focused, helping the community to work together in delivering the feature they’re passionate about.

Since our last blog

Like I said at the top, it’s been a long time (over two years 🫢) since we’ve published a blog highlighting the improvements made to the Android app. You’ve probably been enjoying these new features for some time, but in case you missed it, here are some of the biggest improvements made by the community over that time.

• Health Connect sensors linked to your Android phone have been added, including heart rate, fitness data, and glucose levels (as always, you have complete control over what you share with your Home Assistant instance, and that data stays local).

• By working with Android natively, Assist can now replace your phone’s (or Wear OS devices’) assistant.

• You can now set the Home Assistant app as your device’s default launcher, which is great for wall panel setups.

• We’ve updated our widgets to support some of the new features, like To-do lists.

• Wear OS has had its Tile capabilities improved and a new thermostat tile was added.

• There are now more Android Auto sensors, like speed and remaining range.

• A simpler way to connect Wi-Fi compatible devices to your home network (such as the Home Assistant Voice Preview Edition) using Improv Wi-Fi over Bluetooth (an open standard for connecting devices to Wi-Fi using Bluetooth, built by the Open Home Foundation).

• The Z-Wave device onboarding experience has been improved with the addition of a QR code scanner.

• We’ve also improved the speed and stability of the app.

• It’s now easier than ever for new contributors to jump in and start helping with the app (much more on that below 👇).

For a full list of the app’s capabilities, check out our breakdown of the companion apps from the companion documentation.

What’s next for our Android app

In our latest update of the Android app 2025.7.1, we’ve added a couple of useful features. Including a new basic invite flow, which will be shared between Android and iOS, adding a good layer of consistency between our most-used companion apps. The idea is to make it much more seamless to add new users or set up new devices (no need to type the URL in your Android Automotive device!).

We’ve also made My Links work better. If you’re unfamiliar with My Links, they’re those cool links (that anyone can make) that bring you right to an integration, blueprint, add-on, or settings page. They have always worked great on desktop, but up until recently, they were a bit clunky to use on mobile. Now you can get to the link’s destination with a single click.

Android has many different screen sizes and layouts, and we’re working to better leverage them with edge-to-edge support. Our recent update has edge-to-edge working on Android native UI elements like the settings page, and we’re looking to implement them elsewhere in future updates so we can make the most of your screen real estate.

Important changes for Android users

A huge percentage of our users are on pretty new versions of Android, but we want to support as many older devices as possible.

One significant change on the horizon is ending support for Android 5.0 and 5.1 (also known as Android Lollipop, released in 2014… it had a good run 🫡). Google has announced that starting in June 2025, many AndroidX libraries will require a minimum of Android 6.0 (API 23). Google has already updated Firebase Cloud Messaging to require this as well. This means we will need to stop supporting Android 5.0 and 5.1 (API 21 and 22) to keep up with new features and security updates. Less than 0.3% of installs are on Android versions below API 23 (Android 6.0), and we always work to keep older devices working, but sometimes our hand is forced. If you are using an older device, the app will not be removed, but you will not receive new updates once we make this change. We plan to make one final release for these older versions before support ends. This release is expected before the end of the summer, so you will have the latest updates available for your device before we move on.

Let’s work together

We want to make it easier for you to contribute, whether you are a seasoned developer or just getting started. This includes making the contribution journey smoother and giving people an easy place to start. We’ve even compiled a list of “first issues” to tackle for prospective developers looking to help out. We’ve started work on dedicated Android developer documentation, which will give in-depth information about the inner workings of this app.

We’ve made many behind-the-scenes changes to improve the developer experience (defining best practices, linters for faster/automated feedback, and continuous integration for quicker feedback on PRs). Our focus is always on improving stability, reducing crash rates, and catching issues early. One example of this is our new fail-fast approach, which has already helped us catch and fix issues early.

We want more Android native/exclusive features while also balancing the need to keep parity between the Android and iOS companion apps (the iOS app is excellent, and each app’s community is learning so much from each other).

How you can help

The companion app for Android is a community effort, and your help makes a real difference. Here is how you can get involved:

• Join the beta program to test new features.

• Suggest a feature and share your ideas.

• Help triage issues on GitHub, Discord, or the Home Assistant forum.

• Join the Android Project thread on Discord. (Head to Channels & Roles and select “I want to contribute developer skills!” to assign yourself the Developer role if you can’t see the thread.)

• Submit issues, review pull requests, start your first pull request, and ask questions — your feedback is valuable.

• Help us translate the app.

Thanks again for making all this possible. I look forward to your help making this app even more amazing!

Our Works with Home Assistant program is expanding once again, and this time we’re excited to announce Zooz is joining us! We have tested many new devices of all different types, ensuring they provide the best experience possible with Home Assistant. As well as classic staples for the smart home, they also bring some very cool flood protection devices to help safeguard your home.

These will be the first certified Z-Wave devices added to the program in some time, and are just part of the exciting future the Home Assistant community and Zooz see for this smart home protocol.

Zooz zooms in

Zooz started out not as a manufacturer, but as a retailer of smart devices. They focused so much on customer support that they soon realized they could do a better job than manufacturers already in the market, and so turned instead to creating their own products. They focus on Z-Wave for its interoperability and security, and they include easy-to-understand installation guides with these devices. They also have a wide knowledge base on their website and a very responsive support team.

As Z-Wave experts, they’re members of the Z-Wave Alliance (where Paulus is also a member as the voice of the open source community). While Zooz is based in the USA, many of their products are available worldwide.

It takes Zooz

Zooz has really embraced the Home Assistant community. Agnes, their VP of Brand and Partnership Support, recently spoke to the team over at the Home Assistant podcast about their startup journey. She also came along to our Community Day in Brooklyn, hosted by our very own Product Lead, Madelena. It’s awesome to see manufacturers get out and connect with our community members.

Devices

In case you didn’t know, Works with Home Assistant differs from other certification programs as products are rigorously tested in-house to ensure they work seamlessly out of the box. Any company joining also commits to providing long-term support and firmware updates while being a positive force in the Home Assistant community. Works with Home Assistant is operated by the Open Home Foundation, and the support of Home Assistant Cloud subscribers funds this work.

Zooz has had a large group of devices certified, one of the largest number of devices we’ve ever certified for a launch into the program. Kudos to the foundation team, and Zooz for making such a great variety of new devices available to our community.

Leak Protection

ZAC36 Titan Water Valve Actuator

Plugs

ZEN04 Smart Plug

ZEN05 Outdoor Plug

Relays

ZEN16 Multi Relay

ZEN51 Dry Contact Relay

ZEN52 Double Relay

ZEN53 DC Motor Controller

Lighting Switches

ZEN30 Double Switch

ZEN32 Scene Controller

ZEN71 On Off Switch

ZEN72 Dimmer

ZEN74 Toggle Dimmer

ZEN76 S2 On Off Switch

ZEN77 S2 Dimmer

Sensors

ZSE11 Q Sensor (4in1)

ZSE18 Motion Sensor

ZSE41 Open / Close XS Sensor

ZSE42 Water Leak XS Sensor

ZSE43 Tilt Shock XS Sensor

ZSE44 Temperature Humidity XS Sensor

ZSE70 Outdoor Motion Sensor

Frequencies and firmware

If you’re based in North America, all new devices will come with Z-Wave Long Range (ZWLR) as standard. If you are based elsewhere, like in Europe, Long Range won’t be enabled quite yet. The reason is that even though the Z-Wave Long Range protocol has been available for some time in North America, it was only released in Europe in April 2025, as certification took a bit longer. The nice thing about Zooz’s North American 700 series and European 800 series Z-Wave, is that ZWLR can be enabled via an over-the-air (OTA) firmware update, so hopefully everyone will be taking part in the Z-Wave Long Range revolution soon. Watch this space for a not-so-secret Home Assistant Z-Wave hardware announcement coming your way…

Z-Wave Long Range opens up a whole new world of options and makes for an even more flexible smart home. Maybe you have a large backyard, or an awkwardly shaped long, but narrow home that is hard to get other protocols to cover adequately. Or perhaps you have devices that are just too far away for other protocols. A common example is wanting a way to get notified when the mailbox at the front of your driveway is opened or closed.

Many of the certified devices can function outdoors or be purchased with accessories to make them waterproof. Speaking on a personal note, we had a leak in our garage a year or so ago after some bad weather. Other protocols couldn’t reach that far, and we had no way to be notified. I cannot wait for an easy way to be notified across that bigger distance, and avoid all the unpleasant clean-up.

It’s great to read stories on social media or our forums where smart home devices have kicked in and saved the day, like getting that all-important notification or cutting off the water supply with something like Zooz’s valve actuator.

Z-Wave, like other open standards we support, works locally, and all of the devices listed above will work locally, without the need for any extra cloud connection or apps. Remember, if you’re also looking for remote access to make sure you don’t miss any critical notifications while you’re away from home, an easy way to get this set up is to subscribe to Home Assistant Cloud. Not only will this help you monitor your smart home remotely, but you’ll also be supporting the development of Home Assistant.

FAQs

Q: If I have a device that is not listed under “Works with Home Assistant” does this mean it’s not supported?

A: No! It just means that it hasn’t gone through a testing schedule with our team or doesn’t fit the requirements of the program. It might function perfectly well, but be added to the testing schedule later down the road, or it might work under a different connectivity type that we don’t currently test under the program.

Q: OK, so what’s the point of the Works with program?

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have the expected functionality within Home Assistant, operate locally without the need for cloud, and will continue to do so long-term.

Q: How were these devices tested?

A: All devices in this list were tested using a standard HA Green Hub with our Z-Wave Integration. If you have another hub integration that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.

Q: Will you be adding more Zooz devices to the program?

A: Absolutely! We’re thrilled to foster a close relationship with the team at Zooz to work together on any upcoming releases or add in further products that are not yet listed here.

We’re thrilled to welcome Nuki to the Works with Home Assistant program! Nuki creates some slick-looking smart locks that you can fit to most doors (or even on top of existing locks). They are constantly pioneering new and exciting features, while also using the open standards we support. Nuki is today bringing three different lock types to the program, all certified by our team to provide the best experience possible with Home Assistant.

Unlocking their origin

Nuki started just over 10 years ago, with their first smart lock that was called the ‘magic black box’. It was this award-winning design that evolved into the sleek Nuki Smart Locks that are available today. Keeping everything in the family, the brand was started by brothers Martin and Jürgen. Frustrated with the hassle of carrying a door key in their sports kit, the brothers launched a successful Kickstarter and have been innovating ever since. They design their smart locks in Austria and manufacture them in Europe. Their locks are available across Europe, and in early July, they launched the Nuki Smart Lock in the U.S.

Nuki devices are certified for use with the Home Assistant Matter integration, which is now officially certified. Like all ‘Works with’ certified devices, Nuki locks prioritize local control, so you can manage your day-to-day home security without relying on a cloud connection.

Devices

This lock is turning heads faster than it turns bolts

In case you didn’t know, Works with Home Assistant differs from other certification programs as products are rigorously tested in-house to ensure they work seamlessly out of the box. Any company joining also commits to providing long-term support and firmware updates while being a positive force in the Home Assistant community. Works with Home Assistant is operated by the Open Home Foundation, and the support of Home Assistant Cloud subscribers funds this work.

Our team has been busy testing the Nuki locks for some time and has certified the following Matter-over-Thread enabled devices. It’s important to note that to set up the lock, calibrate it, and activate Matter you will need to use the Nuki app. However, there is no hard requirement for a cloud account or account registration in order to use these locks. Once the device is active and connected via Matter, you can manage it purely through Home Assistant, and can even delete the app.

• Nuki Smart Lock Go
• Nuki Smart Lock Pro
• Nuki Smart Lock Ultra

Insane speeds, literally

The devices certified include two cylindrical models, the Nuki Smart Lock Pro and the Nuki Smart Lock Ultra, which both feature a brushless motor and three speed settings. The speediest of these is called the ‘Insane’ setting. This ultra-fast setting is ideal for those in a hurry, but you can also pick from ‘standard’ or ‘gentle’ to move at a more leisurely pace. The gentle setting is also perfect for quieter unlocking, so you’re not disturbing others if you’re coming home after a night shift or an early morning jog.

We love that the cylindrical devices come with a rechargeable battery to reduce e-waste. Each cylindrical lock comes with both white and black band options, so you can match your existing hardware or your home’s style. The Nuki Smart Lock Pro can retrofit over a current lock, whereas the Nuki Smart Lock Ultra comes with its own cylinder.

If you’re looking for a solid entry-level choice instead, the Nuki Smart Lock Go is a great option, which uses four AA batteries. Both the Smart Lock Go and Smart Lock Pro can be installed in under five minutes, with no drilling or special tools required, which may mean even if you’re renting you could install a smart lock. Works with Home Assistant is all about providing more choice to the community, and Nuki is expanding the smart lock offerings.

A keyless future

All of the models listed work locally, as this is a requirement of the ‘Works with’ program so that you can ensure you feel safe and secure in your smart home. However, some users may wish to access these devices remotely too, allowing you to unlock the door for guests, contractors, family, or friends. If you’re looking for remote access, this can either be provided by the Nuki App, or via your Home Assistant system with something like Home Assistant Cloud (which supports the development of Home Assistant but also helps bring more ‘Works with’ partners to the program 🤝).

We’re really excited to have Nuki join our certified devices, and see the use cases the community will come up with to integrate their smart locks into the rest of their smart home.

FAQ ON WORKS WITH HOME ASSISTANT

Q: If I have a device that is not listed under ‘Works with Home Assistant’ does this mean it’s not supported?

A: Most Nuki locks will work via Matter with Home Assistant and we have even tried out a couple of older locks with good results. However, we have only officially tested and certified the devices listed above. If there is any other device missing from this list it just means that it hasn’t gone through testing with our team or doesn’t fit the requirements of the program. It might function well, and may be added to the testing schedule later down the road, or it might work under a different connectivity type that we don’t currently test under the program.

Q: Ok, so what’s the point of the Works with program?

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. We look for brands that will bring their key functionality into Home Assistant, operate locally without the need for cloud logins, and continue to do so long-term.

Q: How were these devices tested?

A: All devices in this list were tested using a standard Home Assistant Yellow with the built-in Thread border router and our certified Matter Integration.  If you have another hub, border router setup, or integration, that’s not a problem. We test against these as they are the most effective way for our team to certify within our ecosystem.

Q: Will you be adding more Nuki devices to the program?

A: All of the locks Nuki currently sells are now represented here in the ‘Works with’ program. We’re thrilled to foster a close relationship with the team at Nuki to work together on any upcoming releases or add in further products that are not yet listed here.

Home Assistant 2025.7! 🎉

Whew! It’s hot out there! 🌡️ While most of Europe is dealing with a heat wave right now, we’re here to cool things down with an exciting July release that’s packed with features I’m genuinely excited about.

Before we dive in, if you missed it, we recently published Voice Chapter 10 where we explored moving beyond reactive voice assistants that only respond when you talk to them. Instead, we envisioned a future where your voice assistant can be conversational and initiate conversations. Speaking of that, this release delivers on that vision in a big way!

I’m absolutely stoked about the new Ask Question action for Assist! 🗣️ This is something that sets Home Assistant apart from every other voice assistant out there. Finally, your voice assistant can take the initiative and ask you what your smart home should do. No more waiting for wake words, your assistant can start the conversation when it makes sense. It’s the kind of feature that gets me really excited thinking about all the possibilities.

The redesigned Area card is another winner! 🏠 I’ll probably be replacing a few tile cards I’ve been using to navigate to my area dashboards with this new, more flexible version. It integrates beautifully with the Sections dashboard and gives you so many more options for controlling your spaces.

And that’s just the beginning! We’ve got integration sub-entries making integrations even more extensible, full-screen code editors for those lengthy YAML and template edits, and tons of quality-of-life improvements throughout.

Stay cool, and enjoy the release!

../Frenck

• Let Assist ask the questions!
• Redesigned Area card
• Improving the Areas dashboard overview
• Integration sub-entries
• Integration page gets an overhaul
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
  • Farewell to the following
• Other noteworthy changes
• Full-screen code editors
• Improved dashboard creation experience
• Patch releases
  • 2025.7.1 - July 4
  • 2025.7.2 - July 14
  • 2025.7.3 - July 18
  • 2025.7.4 - July 28
• Need help? Join the community!
• Backward-incompatible changes
• All changes

Let Assist ask the questions!

In our latest roadmap, we shared our goal to make Assist more conversational. Until now, Assist was mostly transactional, meaning when you would say something, you would get a response or it would perform an action, and that would be the end of it (unless some LLM magic jumped in). With this release, we’re taking a big step forward: meet the new Ask Question action.

This lets you build custom conversations from the comfort of our automation engine. Ask a question, handle the answer, and keep the interaction going.

This action even allows you to define expected answers so that our extremely fast speech engine, Speech-to-Phrase, can train on them. Yes, fully local, custom conversations!

To help you get started, we have provided a blueprint that covers the most common use case — Asking a closed Yes/No question:

This blueprint allows you to focus on what you want to do if you answer positively or negatively to any question that your voice assistant will ask. The blueprint supports 50 different ways of saying “Yes” and “No” (including phrases like “Make it so” and “Let’s not”). Here it is in action!

In case you want to dive deeper into conversation building, here is an example on how to ask a question and process the different answers:

actions:
  - action: assist_satellite.ask_question
    data:
      entity_id: assist_satellite.living_room_voice_assistant
      preannounce: true   # optional
      preannounce_media_id: media-source://...   # optional
      question: "What kind of music do you want to listen to?"
      answers:
        - id: genre
          sentences:
            - "genre {genre}"
        - id: artist
          sentences:
            - "artist {artist}"
    response_variable: answer
  - choose:
      - conditions: "{{ answer.id == 'genre' }}"
        sequence:
          - action: music_assistant.play_media
            data:
              media_id: "My {{ answer.slots.genre }} playlist"
              media_type: playlist
            target:
              entity_id: media_player.living_room_speakers
      - conditions: "{{ answer.id == 'artist' }}"
        sequence:
          - action: music_assistant.play_media
            data:
              media_id: "{{ answer.slots.artist }}"
              media_type: artist
            target:
              entity_id: media_player.living_room_speakers

Redesigned Area card

Originally introduced a few years ago, the Area card offered a way to display an areaAn area in Home Assistant is a logical grouping of devices and entities that are meant to match areas (or rooms) in the physical world: your home. For example, the living room area groups devices and entities in your living room. [Learn more] overview within the dashboard. However, it wasn’t fully compatible with the Sections dashboard, which limited its practical use in that context.

The card has now been completely redesigned with a look and feel similar to the Tile card. It integrates seamlessly into the Sections dashboard thanks to its flexible layouts. You can choose between a compact version that shows only an icon and the area name, or a more detailed view featuring elements like your camera feed and buttons to toggle your lights or fans.

The control section itself has also been revamped, allowing you to choose which controls to include and rearrange them as you want. As a result of these changes, if you’re currently using the area cards, you’ll need to reconfigure the controls on them.

Additionally, the card now supports controlling cover entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more].

Improving the Areas dashboard overview

The April release introduced an experimental Areas dashboard, designed to automatically generate a ready-to-use interface based on the configured areas within the home. However, the preview could become cluttered if you had a lot of devices in a room.

This release introduces an all-new overview that leverages the redesigned Area card, making it easy to view and control your main devices by room with a single click. It also acts as a navigation hub, giving you quick access to detailed views of each area.

Please note that this is experimental, meaning it is subject to change and may not always work as intended. We would love your feedback if you notice some aspects we can improve. The community’s dashboards, shared over the years, have helped shape this design, and we would love to see how it works with a wide variety of your homes. Even if you already have the perfect dashboard built for your home, try it!

Use this feedback form to let us know your thoughts!

Integration sub-entries

Ever wondered why you had to enter your API keys for every AI agent you created, even though they all used the same key? Or why you had to authenticate for every calendar you added, regardless of the fact that they all shared the same account? Or why you couldn’t add MQTT devices from the UI?

This release solves that with the introduction of integration sub-entries. This allows you to add a sub-entry to an existing integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] entry. In practice, this means that your integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] entry has your credentials, and all the sub-entries use these credentials. In the sub-entry, you can then configure what should be done with these credentials, such as fetching a specific calendar, adding three AI agents with different prompts using the same OpenAI account, or in the case of MQTT, configuring devices that are connected to your MQTT broker.

The following integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] now support sub-entries as of this release: Anthropic, Google Generative AI, MQTT, Ollama, OpenAI Conversation, and Telegram Bot.

Integration page gets an overhaul

The integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] page got a big overhaul! It now has support for sub-entries, allowing you to easily add a sub-entry to an integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] entry along with being able to see which devices and services belong to which sub-entry.

But we took the opportunity to do more. Instead of just showing your integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] entries, it now also shows the devices and services provided by that configuration entry. This makes it much easier to manage your devices and see the relationship between your devices and their integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] at a glance.

Integrations

Thanks to our community for keeping pace with the new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] and improvements to existing ones! You’re all awesome 🥰

New integrations

We welcome the following new integrations in this release:

• Altruist, added by @LoSk-p
  Monitor air quality and environmental conditions with the Altruist sensor, providing local data for temperature, humidity, PM2.5/PM10, CO2, noise levels, and more.
• PlayStation Network, added by @JackJPowell
  Integrate with the PlayStation Network to track your currently playing games and display game information on your dashboard.
• Tilt Pi, added by @michaelheyman
  Monitor your Tilt Pi hydrometer for brewing temperature and specific gravity measurements during your brewing process.
• VegeHub, added by @Thulrus
  Monitor and control your garden with the Vegetronix VegeHub, gathering sensor data and controlling irrigation relays for automated plant care.

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have been added; existing integrations are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• Love that song? @marcelveldt added a button entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] to Music Assistant that lets you add the currently playing item to your favorites with a single click. It works with queues, external sources, and even radio stations!
• ESPHome now supports sub-devices! Thanks to @bdraco, you can now represent multiple logical devices with a single ESP device in Home Assistant. This is particularly useful for RF bridges, Modbus gateways, and other devices that can control multiple devices. This feature requires the soon-to-be-released ESPHome 2025.7. Awesome addition!
• Paperless-ngx now includes an update entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] to keep your document management system up to date. Thanks, @fvgarrel!
• Battery management control has been added to HomeWizard with @DCSBL implementing battery group mode, allowing you to modify the charging and discharging behavior of your HomeWizard batteries!
• Reolink cameras received a ton of love (again) from @starkillerOG! New features include IR brightness control, baby cry sensitivity adjustment, privacy mask switches, and full support for both PoE and WiFi floodlights with multiple command ID pushes. Impressive!
• @mib1185 added an update entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] to the Immich integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more]. Nice!
• The Homee integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] expanded significantly! @Taraman17 added a siren platform for security alerts and support for the HeatIt Thermostat TF056. Nice!
• Energy monitoring got better in Adax with @parholmdahl adding energy sensors, so you can track your heating consumption!
• @ViViDboarder made Ollama more flexible by adding a config option for controlling the think parameter. More control over your local AI!
• Samsung refrigerator owners! @mswilson added ice bites control and water filter replacement/usage sensors to the SmartThings integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more].
• Russound RIO got a major upgrade from @noahhusby, adding sub-device support plus new number and switch entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] for enhanced zone control.
• @chemelli74 expanded Alexa Devices with sensor platforms and additional binary sensors. Now you can get more data from your Echo devices!
• Matter keeps growing! @lboue added dishwasher alarm support and battery storage capabilities. Thanks!
• YAML fans will appreciate @frenck adding unique ID support to Trend integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] configuration.
• The LaMetric Time got an update entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] as well, thanks @joostlek!
• Google Generative AI now defaults to the newer, faster Gemini 2.5 Flash model. A noteworthy performance boost by @tronikos!
• Google Generative AI now supports text-to-speech (TTS) with 30 voices and 24 languages. It supports fine-grained control over style and sound, for example, “Say cheerfully: Have a wonderful day!”. Thanks @lanthaler!
• Enphase Envoy users get detailed DC voltage and current readings from their solar panels thanks to @Bidski. This is perfect for monitoring individual panel health and optimizing production!
• @zerzhang brought evaporative humidifier support to SwitchBot, expanding your climate control options.

Integration quality scale achievements

One thing we are incredibly proud of in Home Assistant is our integration quality scale. This scale helps us and our contributors to ensure integrations are of high quality, maintainable, and provide the best possible user experience.

This release, we celebrate several integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have improved their quality scale:

• 2 integrations reached platinum 🏆

  • Bosch Alarm, thanks to @sanjay900
  • Home Connect, thanks to @Diegorro98

• 1 integration reached gold 🥇

  • ista EcoTrend, thanks to @tr4nt0r

• 1 integration reached silver 🥈

  • KNX, thanks to @farmio

• 2 integrations reached bronze 🥉

  • Samsung TV, thanks to @chemelli74
  • Telegram Bot, thanks to @hanwg

This is a huge achievement for these integrations and their maintainers. The effort and dedication required to reach these quality levels is significant, as it involves extensive testing, documentation, error handling, and often complete rewrites of parts of the integration.

A big thank you to all the contributors involved! 👏

Now available to set up from the UI

While most integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] can be set up directly from the Home Assistant user interface, some were only available using YAML configuration. We keep moving more integrations to the UI, making them more accessible for everyone to set up and use.

The following integration is now available via the Home Assistant UI:

• Telegram Bot, done by @hanwg

Farewell to the following

The following integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] are also no longer available as of this release:

• JuiceNet has been removed as they shut down their API services.

Other noteworthy changes

There are many more improvements in this release; here are some of the other noteworthy changes:

• Shopping list now has a complete intent function that allows you to check off or mark items on your shopping list as completed, making it easier to interact with your shopping lists using voice commands. Thanks, @Lesekater!
• Device and entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] management got better! @emontnemery made it so Home Assistant now restores user customizations when you re-add deleted devices or entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more]. No more losing your carefully crafted names and settings!
• The Template integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] received a major boost from @Petro31! You can now use variables, icons, and pictures across all compatible template platforms, create trigger-based template alarm control panels, locks, vacuum entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more], and fans. Plus, there’s a new label_description template method that allows you to dynamically fetch the description you’ve added to a label from your templates. This is a noteworthy enhancement for better template organization.
• Camera snapshots just got better! @edenhaus added support for taking snapshots via go2rtc. There is nothing for you to do on this one, it works out of the box, but it is nice to know snapshots are now faster and take fewer resources from your system.
• Object selectors now support fields and multiple selections, thanks to @piitaya. These additions are particularly interesting for integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] and blueprint developers, as they provide much more flexibility in your UI representations.
• Wind direction sensors got a visual upgrade with @edenhaus adding range icons for the wind_direction sensor device class. Different icons are now shown depending on the state of wind direction sensors, which is indeed a nice visual upgrade!

Full-screen code editors

Working with snippets of YAML or templates in Home Assistant just got a BIG improvement! We’ve added a new full-screen mode for all code editors throughout the interface.

Whether you’re editing automations, scripts, templates, or any other YAML configuration, you can now expand the code editor to take up your entire screen. This is especially helpful when working with longer configurations or when you need more space to see your code clearly.

Simply click the maximize button in the top-right corner of any code editor to enter full screen mode. Press the button again to return to the normal view.

This makes building a more complex and advanced smart home more comfortable and productive, especially on smaller mobile or tablet screens where every pixel of editing space counts!

Improved dashboard creation experience

The dialog for adding a new dashboard has been redesigned with a cleaner interface that matches recent redesigns we’ve seen to other dialogs. This improvement was designed by @marcinbauer85 and implemented by @quinnter. Great teamwork!

Patch releases

We will also release patch releases for Home Assistant 2025.7 in July. These patch releases only contain bug fixes. Our goal is to release a patch release every Friday.

2025.7.1 - July 4

Happy Fourth of July! 🇺🇸

• Set timeout for remote calendar (@Thomas55555 - #147024)
• Fix missing port in samsungtv (@epenet - #147962)
• Bump ZHA to 0.0.62 (@puddly - #147966)
• Bump aiounifi to v84 (@Kane610 - #147987)
• Fix state being incorrectly reported in some situations on Music Assistant players (@marcelveldt - #147997)
• Bump hass-nabucasa from 0.104.0 to 0.105.0 (@ludeeus - #148040)
• Fix Telegram bots using plain text parser failing to load on restart (@hanwg - #148050)
• Bump pyenphase to 2.2.0 (@catsmanac - #148070)
• Cancel enphase mac verification on unload. (@catsmanac - #148072)
• Bump aioamazondevices to 3.2.3 (@chemelli74 - #148082)
• Update frontend to 20250702.1 (@bramkragten - #148131)
• [ci] Fix typing issue with aiohttp and aiosignal (@cdce8p - #148141)
• Bump venstarcolortouch to 0.21 (@mlfreeman2 - #148152)

2025.7.2 - July 14

• Squeezebox: Fix track selection in media browser (@Hypfer - #147185)
• Squeezebox: Fix tracks not having thumbnails (@Hypfer - #147187)
• Bump pysmlight to v0.2.7 (@tl-sl - #148101)
• Fix REST sensor charset handling to respect Content-Type header (@bdraco - #148223)
• Fix UTF-8 encoding for REST basic authentication (@bdraco - #148225)
• Bump pylamarzocco to 2.0.10 (@zweckj - #148233)
• Bump sharkiq to 1.1.1 (@funkybunch - #148244)
• bump motionblinds to 0.6.29 (@starkillerOG - #148265)
• Bump aiowebostv to 0.7.4 (@thecode - #148273)
• Bump gios to version 6.1.0 (@bieniu - #148274)
• Restore httpx compatibility for non-primitive REST query parameters (@bdraco - #148286)
• Bump pyenphase to 2.2.1 (@catsmanac - #148292)
• Add lamp states to smartthings selector (@jvits227 - #148302)
• Fix Switchbot cloud plug mini current unit Issue (@XiaoLing-git - #148314)
• Bump pyswitchbot to 0.68.1 (@zerzhang - #148335)
• Handle binary coils with non default mappings in nibe heatpump (@elupus - #148354)
• Bump aioamazondevices to 3.2.8 (@chemelli74 - #148365)
• Create own clientsession for lamarzocco (@zweckj - #148385)
• Bump pylamarzocco to 2.0.11 (@zweckj - #148386)
• Bump pySmartThings to 3.2.7 (@joostlek - #148394)
• Bump uiprotect to version 7.14.2 (@RaHehl - #148453)
• Bump hass-nabucasa from 0.105.0 to 0.106.0 (@ludeeus - #148473)
• Revert “Deprecate hddtemp” (@edenhaus - #148482)
• Fix entity_id should be based on object_id the first time an entity is added (@jbouwh - #148484)
• Bump aioimmich to 0.10.2 (@mib1185 - #148503)
• Add workaround for sub units without main device in AVM Fritz!SmartHome (@mib1185 - #148507)
• Add Home Connect resume command button when an appliance is paused (@Diegorro98 - #148512)
• Use the link to the issue instead of creating new issues at Home Connect (@Diegorro98 - #148523)
• Ensure response is fully read to prevent premature connection closure in rest command (@jpbede - #148532)
• Fix for Renson set Breeze fan speed (@krmarien - #148537)
• Remove vg argument from miele auth flow (@astrandb - #148541)
• Bump aiohttp to 3.12.14 (@bdraco - #148565)
• Update frontend to 20250702.2 (@bramkragten - #148573)
• Fix Google Cloud 504 Deadline Exceeded (@luuquangvu - #148589)
• Fix - only enable AlexaModeController if at least one mode is offered (@jbouwh - #148614)
• snoo: use correct value for right safety clip binary sensor (@falconindy - #148647)
• Bump nyt_games to 0.5.0 (@hexEF - #148654)
• Fix Charge Cable binary sensor in Teslemetry (@Bre77 - #148675)
• Bump PyViCare to 2.50.0 (@CFenner - #148679)
• Fix hide empty sections in mqtt subentry flows (@jbouwh - #148692)
• Bump aioshelly to 13.7.2 (@thecode - #148706)
• Bump aioamazondevices to 3.2.10 (@chemelli74 - #148709)

2025.7.3 - July 18

• Handle connection issues after websocket reconnected in homematicip_cloud (@hahn-th - #147731)
• Fix Shelly n_current sensor removal condition (@bieniu - #148740)
• Bump pySmartThings to 3.2.8 (@joostlek - #148761)
• Bump Tesla Fleet API to 1.2.2 (@Bre77 - #148776)
• Use ffmpeg for generic cameras in go2rtc (@edenhaus - #148818)
• Add guard to prevent exception in Sonos Favorites (@PeteRager - #148854)
• Fix button platform parent class in Teslemetry (@Bre77 - #148863)
• Bump pyenphase to 2.2.2 (@catsmanac - #148870)
• Bump gios to version 6.1.1 (@bieniu - #148414)
• Bump gios to version 6.1.2 (@bieniu - #148884)
• Bump async-upnp-client to 0.45.0 (@StevenLooman - #148961)
• Pass Syncthru entry to coordinator (@joostlek - #148974)
• Update frontend to 20250702.3 (@bramkragten - #148994)
• Bump PySwitchbot to 0.68.2 (@bdraco - #148996)
• Ignore MQTT sensor unit of measurement if it is an empty string (@jbouwh - #149006)
• Bump aioamazondevices to 3.5.0 (@chemelli74 - #149011)

2025.7.4 - July 28

• Keep entities of dead Z-Wave devices available (@AlCalzone - #148611)
• Fix warning about failure to get action during setup phase (@mback2k - #148923)
• Fix a bug in rainbird device migration that results in additional devices (@allenporter - #149078)
• Fix multiple webhook secrets for Telegram bot (@hanwg - #149103)
• Bump pyschlage to 2025.7.2 (@dknowles2 - #149148)
• Fix Matter light get brightness (@jvmahon - #149186)
• Fix brightness_step and brightness_step_pct via lifx.set_state (@Djelibeybi - #149217)
• Add Z-Wave USB migration confirm step (@MartinHjelmare - #149243)
• Add fan off mode to the supported fan modes to fujitsu_fglair (@crevetor - #149277)
• Update Tesla OAuth Server in Tesla Fleet (@Bre77 - #149280)
• Update slixmpp to 1.10.0 (@gaaf - #149374)
• Bump aioamazondevices to 3.5.1 (@chemelli74 - #149385)
• Bump pysuezV2 to 2.0.7 (@jb101010-2 - #149436)
• Bump habiticalib to v0.4.1 (@tr4nt0r - #149523)

Need help? Join the community!

Home Assistant has a great community of users who are all more than willing to help each other out. So, join us!

Our very active Discord chat server is an excellent place to be, and don’t forget to join our amazing forums.

Found a bug or issue? Please report it in our issue tracker to get it fixed! Or check our help page for guidance on more places you can go.

Are you more into email? Sign up for the Open Home Foundation Newsletter to get the latest news about features, things happening in our community, and other projects that support the Open Home straight into your inbox.

Backward-incompatible changes

We do our best to avoid making changes to existing functionality that might unexpectedly impact your Home Assistant installation. Unfortunately, sometimes, it is inevitable.

We always make sure to document these changes to make the transition as easy as possible for you. This release has the following backward-incompatible changes:

If you are a custom integration developer and want to learn about changes and new features available for your integration: Be sure to follow our developer blog.

All changes

Of course, there is a lot more in this release. You can find a list of all changes made here: Full changelog for Home Assistant Core 2025.7

Please welcome the latest addition to the Works with Home Assistant program, SwitchBot! This year has seen a lot of ‘firsts’ within the program, and this launch certainly keeps up this trend. Read on to see the first Air Purifiers and Vacuums / Cleaning Robots! What’s more, SwitchBot is bringing this first set of devices into the program with multiple connectivity options. Pick from their Bluetooth integration, Matter via a hub, or standalone Matter devices as well. All this gives you even more choice in how you set up your smart home, while providing the best experience with Home Assistant.

Making the Switch…Bot

SwitchBot quickly gained traction in the smart home industry with their original finger bots, which sit over non-smart switches and physically press them down on your behalf. Since then, they’ve expanded to include many other smart home devices like curtain robots, hubs, air purifiers, and cleaning robots. We were excited to see these new products in person at CES earlier this year and meet up with their team.

SwitchBot even got involved with Community Day, hosting a meet-up in Shenzhen, China. We love that the ‘Works with’ partners show that they’re passionate about engaging with our community, taking the partnership much further than just a label on a box.

Devices

In case you didn’t know, Works with Home Assistant differs from other certification programs as products are rigorously tested in-house to ensure they work seamlessly out of the box with Home Assistant. Any company joining also commits to providing long-term support and firmware updates while being a positive force in the Home Assistant community. Works with Home Assistant is operated by the Open Home Foundation, and the support of Home Assistant Cloud subscribers funds this work.

The SwitchBot team have put special focus on integrating specifically for Home Assistant and have been working hard on their Bluetooth integration. Though the community played a central role in the development of the integration, and SwitchBot is very thankful for this work, they took a more active role in its development.

One of the terms of the ‘Works with’ program is that Bluetooth devices must connect over an integration that is kept up to a certain code quality (we call this our ‘Gold tier’ on our quality scale). It also must be maintained by the manufacturers themselves, rather than overly relying on community members to do the hard work. This puts the responsibility on the shoulders of the manufacturers to make sure they’re responding to bugs and keeping the integration up long term. If you’re interested in SwitchBot’s Bluetooth products but your Home Assistant system doesn’t have built-in Bluetooth, the easiest way to connect them is by using a Bluetooth Proxy.

If you prefer Matter, SwitchBot also has devices that are certified for use with one of their Matter hubs: either the SwitchBot Hub 2 or the Hub 3. There are also some that can work via Matter-over-WiFi as standalone devices. We are currently testing even more of SwitchBot’s Matter devices for the program.

Bluetooth

• SwitchBot Lock Ultra
• SwitchBot Air Purifier
• SwitchBot Air Purifier Table
• SwitchBot Leak Detector - also works using Matter via a hub
• SwitchBot Meter  - also works using Matter via a hub 
• SwitchBot Meter Pro - also works using Matter via a hub
• SwitchBot Meter Pro CO2 - also works using Matter via a hub
• SwitchBot Indoor/Outdoor Thermo-Hygrometer - also works using Matter via a hub
• SwitchBot Curtain 3 - also works using Matter via a hub
• SwitchBot Contact Sensor - also works using Matter via a hub
• SwitchBot Roller Shade - also works using Matter via a hub
• SwitchBot Lock Pro - also works using Matter via a hub

Matter-Over-WiFi (standalone, without requiring a hub)

• SwitchBot Air Purifier
• SwitchBot Air Purifier Table
• SwitchBot Multitasking Robot K20 + Pro

Note: Home Assistant Container does not support Matter, and requires Home Assistant OS.

A smart home is a clean home

Eat your heart out Wall-E

SwitchBot’s K20 is the first cleaning robot in the Works with Home Assistant program as well as the world’s first multi-tasking household robot. This wacky robot can be paired with lots of other items in the range, including the certified air purifiers, to make some really cool Home Assistant use cases. Just imagine, you’re making some delicious dinner, but oh no, you’ve left a pan alone for too long and it starts to smell and burn. You could summon the K20 with an air purifier on top using the Home Assistant Voice Preview Edition. A few moments later, it’s found its way to you and gets started on clearing the air in your kitchen. Plus, as these can both work via Matter, there’s no need for cloud involvement. Some of the items also come with a table top so this device has some great applications for anyone with limited mobility.

Bot to the future

These devices are the first certified items, but SwitchBot is working to get many more tested and fully feature-rich with Home Assistant. We’re excited to keep expanding this list over time, but if you can’t wait (and this work is only possible with the support of our Home Assistant Cloud subscribers), you can see the list of the other devices they are working on here.

FAQs

Q: If I have a device that is not listed under ‘Works with Home Assistant’ does this mean it’s not supported?

A: No! It just means that it hasn’t gone through a testing schedule with our team or doesn’t fit the requirements of the program. It might work fine and be added to our testing later down the road. Though it might only have limited functions that are being worked on, or use a connectivity type we don’t currently test for in the program.

Q: Ok, so what’s the point of the Works with program?

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have full functionality within Home Assistant, operate locally without the need for cloud, and will continue to do so long-term.

Q: How were these devices tested?

A: The Bluetooth devices in this list were tested using a standard Home Assistant Green Hub, the SwitchBot Bluetooth Integration, a USB Bluetooth adapter, and an ESPHome Bluetooth Proxy. The Matter-over-WiFi devices were also tested with Home Assistant Green and our certified Matter Integration. If you have another hardware setup or integration, that is often not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.

Q: Will you be adding more SwitchBot devices to the program?

A: Absolutely! SwitchBot has a quickly growing set of product lines that we’re working to certify together, subject to the integrations fully covering all the functions.

Welcome to Voice chapter 10 🎉, a series where we share all the key developments in Open Voice. This chapter includes improvements across every element of Open Voice. Improvements that allow it to support more languages, be used on more hardware, make it easier to contribute to, all while making it faster and more reliable.

Help steer Open Voice

Before we get going, we just want to say that Voice Chapter 10 isn’t just a broadcast; it’s an invitation ✉️. Our public Voice project board lives on GitHub, and it shows what we’re fixing, currently building, and what we’ll work on next. Every card is open for comments, so please feel free to have a look and participate in the discussion.

👉 Project board: https://github.com/orgs/OHF-Voice/projects/2

ESPHome gains a voice

When we began designing and building the firmware for our open voice assistant hardware, the Home Assistant Voice Preview Edition, we had several specific features in mind:

1. Run wake words on the device.
2. Use a fully open-sourced media player platform that can decode music from high-quality sources.
3. Wake words can be enabled and disabled on the fly; for example, “stop” is only activated when a long-running announcement is playing or when a timer is ringing.
4. Mix voice assistant announcements on top of reduced volume (a.k.a. “ducked”) music.

These features needed to run within ESPHome, the software that powers the device. In the beginning, ESPHome could only do 1 and 2, but not even at the same time!

To include all these features, we initially built them as external components, allowing us to iterate fast (and of course break many things along the way). We always intended to bring these components into ESPHome, and the process of bringing them in is called upstreaming. This would allow anyone to easily build a voice assistant that includes all the features of Voice Preview Edition, and that’s what we’ve been working on since its launch last December.

No device left behind!

ESPHome version 2025.5.0 has all these components included!  We didn’t just spend this time copying the code over, but we also worked hard to improve it by making it more generalizable, easier to configure, and much faster.

As an example of these speed improvements, the highest CPU load on the Voice Preview Edition happens when music is being mixed with a long announcement. In this situation, it is decoding two different FLAC audio streams while also running three microWakeWord models (a Voice Activity Detector, “Okay Nabu”, and “Stop”). With the original December firmware, this used 72% of the CPU 😅. With the new optimizations, which are all now available in ESPHome, the current Voice Preview Edition firmware only uses 35%❗ These improvements even allow the extremely resource-constrained ATOM Echo to support many of these features, including media playback and continuing conversations.

Make your own Voice Preview Edition

I'll just pretend I understand all this

Speaking of voice hardware becoming more like Voice Preview Edition, why not use that class-leading hardware as the basis for your own creations? We’ve now got the KiCad project files, which include the electrical schematic and circuit board layout, along with other helpful documents available for download on GitHub. Combined with our open source firmware files, this will allow anyone to build on the work we’ve done and make the open voice assistant of their dreams. Bigger speaker, built-in presence sensor, a display featuring a smiling Nabu mascot — the options are nearly endless. Building Voice Preview Edition was always meant to bootstrap an entire ecosystem of voice hardware, and we’re already seeing some amazing creations with this open technology.

Now you’re speaking my language

Speech-to-Phrase gets more fluent

In case you missed it, we built our own locally run speech-to-text (STT) tool that can run fast even on hardware-constrained devices. Speech-to-Phrase works slightly differently from other STT tools, as it only accepts specific predetermined phrases, hence the name. We have been making large strides in making this the best option for local and private voice control in the home.

The sentence format for Speech-to-Phrase is getting an upgrade! Besides making it simpler for community members to contribute, it now allows for more thorough testing to ensure compatibility with existing Home Assistant commands.

We have also begun experimenting with more precise sentence generation, restricting sentences like “set the {light} to red” only to lights that support setting color. Another improvement is making Speech-to-Phrase more careful about combining names and articles in certain languages. For instance, in French, a device or entity that starts with a vowel or an “h” will have an “l” apostrophe at its beginning, such as l’humidificateur or l’entrée. Allowing Speech-to-Phrase to understand this avoids it guessing pronunciations for nonsensical combinations.

Speech-to-Phrase currently supports six languages, namely English, French, German, Dutch, Spanish, and Italian. We are now engaging with language leaders to add support for Russian, Czech, Catalan, Greek, Romanian, Portuguese, Polish, Hindi, Basque, Finnish, Mongolian, Slovenian, Swahili, Thai, and Turkish — this takes our language support to 21 languages 🥳!

These new models were originally trained by community members from the Coqui STT project (which is now defunct, but luckily their work was open source — another example of FOSS saving the day), and we are very grateful for the chance to use them! Performance and accuracy vary heavily by language, and we may need to train our own models based on feedback from our community.

Piper is growing in volume

Piper is another tool we built for local and private voice in the home, and it quickly turns text into natural-sounding speech. Piper is becoming one of the most comprehensive open source text-to-speech options available and has really been building momentum. Recently, we have added support for new languages and provided additional voices for existing ones, including,

• Dutch - Pim and Ronnie - new voices
• Portuguese (Brazilian) - Cadu and Jeff - new voices
• Persian/Farsi - Reza_ibrahim and Ganji - new language
• Welsh - Bu_tts - new voices
• Swedish - Lisa - new voices
• Malayalam - Arjun and Meera - new language
• Nepali - Chitwan - new voices
• Latvian - aivar- new voices
• Slovenian - artur - new voices
• Slovak - lili - new voices
• English - Sam (non-binary) and Reza_ibrahim - new voices

This brings Piper’s supported languages and dialects from 34 to now 39 🙌! This allows a nice majority of the world’s population (give or take 3 billion people) the ability to generate speech in their native tongue 😎!

Scoring language support

This is the score sheet for just intents... it can get complicated

Home Assistant users, when starting their voice journey, typically ask one question first: “Is my language supported?” Due to how flexible voice assistants in Home Assistant are, this seemingly simple question is quite complicated to answer! At a high level, a voice assistant needs to convert your spoken audio into text (speech-to-text), figure out what you want it to do (intent recognition), and then respond back to you (text-to-speech). Each part of this pipeline can be mixed and matched, and intent recognition can even be augmented with a fallback to a large language model (LLM), which is great at untangling misunderstood words or complex queries.

Considering the whole pipeline, the question “Is my language supported?” becomes “How well does each part support my language?” For Home Assistant Cloud, which uses Microsoft Azure for voice services, we can be confident that all supported languages work well.

Local options like Whisper (speech-to-text) and, to a lesser extent, Piper (text-to-speech), may technically support a language but perform poorly in practice or within the limits of a user’s hardware. Whisper, for example, has models with different sizes that require more powerful hardware to run as they get larger. A language like French may work well enough with the largest Whisper model (which requires a GPU), but is unusable on a Raspberry Pi or even an N100-class PC.

Our own Speech-to-Phrase system supports French well and runs well on a Raspberry Pi 4 or Home Assistant Green. The trade-off is that only a limited set of pre-defined voice commands are supported, so you can’t use an LLM as a fallback (because unexpected commands can’t be converted into text for the LLM to process).

Finally, of course, not everyone wants to (or can) be reliant on the cloud, and they need a fully local voice assistant. This means that language support depends as much on the user’s preferences as their hardware and the available voice services. For these reasons, we have split out language support into three categories based on specific combinations of services:

• Cloud - Home Assistant Cloud
• Focused Local - Speech-to-Phrase and Piper
• Full Local - Whisper and Piper

Each category is given a score from 0 to 3, with 0 meaning it is unsupported and 3 meaning it is fully supported. Users who choose Home Assistant Cloud can look at the Cloud score to determine the level of language support. For users wanting a local voice assistant, they will need to decide between Focused Local (limited commands for low-powered hardware) and Fully Local (open-ended commands for high-powered hardware). Importantly, these scores take into account the availability of voice commands translated by our language leaders. A language’s score in every category will be lowered if it has minimal coverage of useful voice commands.

With these language scores, we hope users will be able to make informed decisions when starting on their voice journeys in Home Assistant. They’re currently featured in our voice setup wizard in Home Assistant, and on our language support page.

What’s in a name

Voice commands in Home Assistant trigger intents, which are flexible actions that use names instead of IDs. Intents handle things like turning devices on or off, or adjusting the color of lights. Until now, sentence translations focused on whether a language supported an intent (like turning devices on/off) but didn’t clearly show whether the command supported device names, areas names, or both. This can change from language to language, which made gaps hard to spot. We’re switching to a new format that highlights these combinations, making it easier for contributors to see what names are supported, which should make for simpler translations.

Continued conversation updates

Since the last voice chapter, the voice team has worked on making Assist more conversational for LLM-based agents. We started with LLM-based agents because it was simpler to iterate on. If the LLM returns with a question, we will detect that and keep the conversation going, without the need for you to say “Ok Nabu” again.

On top of that, you can now initiate a conversation with a new action called start_conversation directly from an automation, or a dashboard. This provides the full spectrum of conversation to LLM-based agents.

Here is a quick demonstration of two features working hand-in-hand:

Media Search and Play intent

What’s great about Home Assistant and open source is that sometimes the best ideas come from other projects in the community. Early on, many people were interested in driving Music Assistant with voice, but central pieces were missing on Home Assistant, such as the ability to search a media library.

We worked hard on bringing this functionality to the core experience of Home Assistant and created a new intent, the Search and Play intent. You can now speak to your voice assistant and ask it to play music in any room in your home.

The intent can be used by an LLM-based conversation agent, but we also have sentences that work without any LLM magic. You can find the English sentences here. As it’s a new feature, support may vary based on your language, and please be patient while our amazing language leaders make these translations.

Future work - Assist will have something to say

Talking to your home should feel as natural as chatting with a friend across the kitchen counter. Large-language models (LLMs) already prove how smooth that back-and-forth can be, now we want every Home Assistant installation to enjoy the same experience. We’re therefore zeroing in on three key use-cases for the default conversation agent, which include critical confirmations, follow-ups, and custom conversations. Just note these are still at the early stages of development and it may be some time before you see some of these features.

Critical confirmations

Some actions are too important to execute without a quick double-check. Unlocking the front door, closing shutters, or running a “leaving home” script. We want you to be able to mark those entities as protected. Whenever you speak a command that touches one of those entities, Assist will ask for verbal confirmation before acting:

Ok Nabu, unlock the front door
Are you sure?
Yes
Unlocked

Because every household is different, we are thinking about managing these confirmations per entity and making them fully user-configurable.

Follow-up on missing parameters

Sometimes Assist grasps what you want, but needs more detail to carry it out. Instead of failing, we want Assist to ask for the missing piece proactively. Here is an example to illustrate.

Ok Nabu, set a timer
For how long?
15 minutes
Timer started

For now, we are still assessing the relevant sentences for that use case. We’re implementing follow-ups with timers, though finding more is not currently our top priority. We are, however, open to suggestions.

Custom conversations

As with any other part of Home Assistant, we want the conversation aspect of Assist to be personalized. Simple voice transactions can already be created with our automation engine using the conversation trigger and the set_conversation_response action.

We want to bring the same level of customization to conversations, allowing you to create fully local, predefined conversations to be triggered whenever you need them, such as when you enter a room, start your bedtime routine, etc.

We are focusing first on making custom conversations possible, so that you can show us what you are building with this new powerful tool. We will then tackle the critical confirmations use case, and finally, the follow-ups when parameters are missing.

Let’s keep moving Open Voice forward

Only a couple of years ago, voice control was the domain of data-hungry corporations, and basically none of this open technology existed. Now, as a community, we’ve built all the parts needed to have a highly functional voice assistant, which is completely open and free for anyone to use (or even build on top of).
Every chapter, we make steady progress, which is only possible with your support. Whether from those who fund its development by supporting the Open Home Foundation (by subscribing to Home Assistant Cloud, and buying official Home Assistant hardware) or those who contribute their time to improving it. As always, we want to support every language possible, and if you don’t see your native tongue on our supported list, please consider contributing to this project.

Our first Home Assistant Community Day was a humbling success — we knew that the community had a desire to have something coordinated like this, but we really did not expect just how widely this would spread. 💖

So much happened in such a short window of time, so let’s talk about how this year’s event went and what the future looks like for Home Assistant meetups.

It started with a question…

Home Assistant Community Day was born from a conversation last year where we asked, “Would the community even want this?” We dropped hints here and there to test how y’all would react to a worldwide event, and after weeks of planning, the response to the event announcement was overwhelmingly positive. 🤩

First, THANK YOU 🙏🏻 to all the hosts for their local coordination, community members who showed up, and the venues that made all this possible. I learned so much with your help, and it will make next year’s Community Day one to remember.

…that turned into a movement…

When I announced Home Assistant Community Day, I didn’t give hosts a lot to work with. I didn’t want the community to think they had to fit into a specific format, and wanted it to be unique to their region. It became clear pretty quickly what information was missing and what people wanted guidance on. For example, some asked for suggestions on what types of venues to book or which activities could make the event more interactive, such as quizzes or presentations. Your questions helped us make it easier for hosts to build cool events, thank you for those!  

All around the world, everyone came together to talk about Home Assistant (and its related projects). You swapped hardware, you showed off your automations or dashboards, you participated in quizzes, and you formed new bonds with people in your area who share your passion for Home Assistant. Some people had custom swag printed, others received hardware from a couple of our Works With Home Assistant partners, and one group had a Hackathon event the day before! So many great photos were shared from the events that we can’t possibly include them all here! You can find plenty more by searching #HADay2025 on social media or by checking the Discord meetup thread for this event. It was seriously one of the most uplifting things I’ve had the pleasure to not only facilitate, but also witness. 🥰

…but not without complications

Swag was an unexpected complication. When I first announced the day, we planned to have me order the merch and then send it off to the hosts. This would require collecting addresses and sending packages to people around the world, and we realized quickly that the logistics of that would end up a mess.  Instead, we made the sticker designs (along with the Luma calendar invite graphic) publicly available for the hosts to print something locally.

When we did this, we (as the Open Home Foundation) committed to reimbursing the hosts for these swag purchases, along with venue fees or other reasonable expenses they might have on the day. The idea being that no host should be out of pocket for supporting their local Home Assistant community. You support us (by contributing time or by being Home Assistant Cloud subscribers), and we want to give back to the community in any way we can.

I’m excited to share that we plan on using those same guidelines for any community meetup, not just the ones that happen on Community Day! 👏🏻 We’re building a new community page where all of these details will be available, so stay tuned for more information.

Some stats for the nerds

We had 82 events with over 1,600 registered guests, spanning nearly every corner of the globe. The events started in New Zealand and ended on the West Coast of North America. This meant we had meetups held from 10 pm May 23 to midnight May 25 (UTC time), that’s over 26 hours of constant partying! 🥳

We had events in every major region except Australia! Most meetups were in Europe and North America — probably not too surprising for most. The smallest events had 2 registered guests, and the event that had the largest number of registered guests was Utrecht, with 200!

With an average of 20 people attending a meetup, we know that we can advise a lower capacity limit for future events. This will be included as part of the guidelines we’ll have on that new community page I mentioned above.

Keep the fun going!

Many hosts told me that they’ve created a new space for the attendees to chat or that they were going to start doing some regular meetups (some have done both!). Since Luma worked so well for us for Community Day, I’ve created a general calendar for meetups! I also have graphic assets publicly available for your Luma event and any social media you’d like to post your event on — use the 1:1 ratio image for the invite image on Luma. There are two events live there now, way to go Chile (Santiago) and Belgium (Hasselt)! 🤩

While we don’t have a solid date for next year’s Home Assistant Community Day, I can at least let you know that it will not be in May and instead later in the year. I’m aiming to give you at least a two-month heads-up for when it will be this time. We’re planning on doing something bigger and I can’t wait to do it all again with y’all next year. 😌

P.S. - Did you spot our refreshed Creator Network page yet? 👀

Home Assistant 2025.6! 🎉

We are already half way through 2025, can you believe it? I personally can’t, as it feels like we just started the year. Not just that, there are so many exciting things to still come this year, and I can’t wait to share them with you!

Anyway, the June release is here! A week later than usual, but it also means we had an extra week to polish and beta test this release. Like the previous release, this release is packed with quality-of-life improvements!

Last release my favorite feature was the new entity picker; this release, we improved ALL other pickers! No surprise that this, again, makes it to my top favorite this release. Although the ability to group media players directly from the media player card is a close second. It is so nice to see how Home Assistant keeps getting better and better, and how our community keeps contributing to it. 😍

If you are leveraging Bluetooth in your Home Assistant setup, you will also love the new Bluetooth connection graph that shows how your Bluetooth devices are connected, including Bluetooth proxies. Troubleshooting Bluetooth has become so much easier now!

Enjoy the release!

../Frenck

PS: We will pick up the regular release schedule again now, so expect the next release on the first Wednesday of July (July 2nd).

• Improving all the “pickers”
• Making sense of Bluetooth
• Iterations of the experimental area dashboard
• Deprecating installation methods and 32-bit architectures
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Farewell to the following
• Other noteworthy changes
• Sidebar improvements
• Join/unjoin groups of media players
• Reset/restore entity IDs
• Patch releases
  • 2025.6.1 - June 13
  • 2025.6.2 - June 23
  • 2025.6.3 - June 24
• Need help? Join the community!
• Backward-incompatible changes
• All changes

Improving all the “pickers”

Pickers are those dropdowns you use to select entities, devices, areas, and more. Pickers are everywhere in Home Assistant, being used in automations, scripts, and configuration options.

Last release, we introduced a new entity picker, which was a big hit! This release takes things further by refining the search experience based on your feedback.

Even better, that same improved search experience now comes to the area, category, floor, label, user, and device pickers too! They are consistent, fast, and easy to use, no matter what you’re selecting.

And the device picker? It now has a fresh look to match, complete with manufacturer logos and styling inspired by the entity picker.

Making sense of Bluetooth

Home Assistant has powerful Bluetooth capabilities, and with the use of something like ESPHome Bluetooth proxies, you can extend your Bluetooth network to cover your entire home. This release brings some improvements to the Bluetooth integration that will help you understand your Bluetooth network better.

The Bluetooth integration now provides a visualization that shows how your Bluetooth devices are connected to your Home Assistant instance, whether that’s directly to your system or through a Bluetooth proxy.

It not only shows the actively connected devices, but also the devices that are in range, but not yet known to Home Assistant. This is a great way to see what devices are around you and where they can be potentially connected.

Oh! And now that the Bluetooth integration has a sleek new visualization, the Zigbee integration, which already has a similar feature, has been given a visual update. This makes visualizations consistent across Home Assistant.

Iterations of the experimental area dashboard

In the April release, we introduced a new experimental Areas dashboard, which automatically generates a ready-to-use dashboard based on the areas you’ve set up in your home. It uses sections and tile cards for a modern, clean, and intuitive look — all built for you in a couple of clicks.

As this is experimental, it is being continuously iterated on. This release brings some nice changes, based on your feedback, to subtly refine the experience.

We added a new “Actions” section that includes scripts, automations, and scenes. We also added number entities (and number helpers), button entities (and button helpers), counters, and timer helpers to the “Others” section. This makes it easier to find and manage your automations and scenes in the context of your areas.

Finally, we renamed the “Entertainment” section to “Media players”. This makes it clearer that this section is specifically for your players, and may not include your DIY arcade machine 👾.

Deprecating installation methods and 32-bit architectures

This release introduces important deprecation announcements, and though they only affect a small percentage of users, it is important that they understand the impacts. We’ve written a detailed blog that explains the rationale, timeline, and tips on how to migrate — which I highly suggest reading if you think you’re affected.

• Installation Methods: The Core and Supervised installation methods are now officially deprecated. These are advanced setups that are only used by a small portion of users, as they involve running Home Assistant in a Python environment or installing the Supervisor on top of your own operating system. Moving forward, we are focusing our support on the more streamlined and maintainable installation methods: Home Assistant OS and Home Assistant Container.

• 32-bit Architectures: Support for legacy 32-bit CPU architectures (i386, armhf, and armv7) is also being deprecated. These architectures are increasingly uncommon and pose challenges for maintaining compatibility and performance.

To assist you during this transition, Home Assistant will now raise a repair issue after upgrading if your system is affected by these deprecations. This notification will appear in the repair dashboard, providing information about the deprecation along with guidance on how to migrate to a supported setup.

It’s important to note that while these methods and architectures are deprecated, they will continue to receive support for the next six months, until the release of Home Assistant 2025.12. You can continue to use them after this point, but we would highly recommend migrating. After this 6-month period, they will become unsupported, meaning they will no longer receive updates or official assistance.

If you don’t receive this repair message, you’re not affected. However, you can double-check using our guide if you’d like. We also have specific information on what becoming deprecated and unsupported means for your installation. Lastly, we have detailed information on how best to migrate to a supported system.

Integrations

Thanks to our community for keeping pace with the new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] and improvements to existing ones! You’re all awesome 🥰

New integrations

We welcome the following new integrations in this release:

• Alexa Devices, added by @chemelli74
  Connect to and control your Amazon devices like Echo, Fire TV, and Alexa-enabled devices.
• Immich, added by @mib1185
  Integrates with Immich App, a self-hosted photo and video backup solution that puts you in control of your personal media.
• Paperless-ngx, added by @fvgarrel
  Connect to your Paperless-ngx system to track and manage your digital documents from Home Assistant.
• Probe Plus, added by @pantherale0
  Integrate wireless Bluetooth meat thermometers compatible with the PROBE PLUS app, bringing real-time temperature monitoring during cooking into Home Assistant.
• Zimi Cloud Connect, added by @mhannon11
  Connect to Zimi Cloud devices to monitor and control your Zimi smart home products.

This release also has new virtual integrations. Virtual integrations are stubs that are handled by other (existing) integrations to help with findability. These ones are new:

• Kaiser Nienhaus, provided by Motionblinds, added by @starkillerOG

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have been added; existing integrations are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• @bdraco added support for updating ESPHome devices that are in deep sleep. A very welcome improvement for battery-powered devices!
• The Homee integration now supports fans and provides alarm control panels. Thanks for expanding its capabilities, @Taraman17!
• Teslemetry keeps getting better—@Bre77 added a hazard lights binary sensor, a valet mode switch, and a credit balance sensor. Nice!
• @bieniu improved the Shelly integration to use sub-devices for multi-channel devices. A notable change for complex setups!
• The SmartThings integration saw a huge round of improvements by @joostlek, including: support for cooktops, hobs, water heaters, hood fan speeds, Steam closet modes, freezer and cooler temperatures, washer spin and soil levels, valve positions, heat pump zone climates, and atmospheric pressure. Amazing!
• Miele keeps on shining with new features from @astrandb, like vacuum support, drying step sensors, washer-dryer program phases, and hob plate sensors. @generically-named added energy and water forecasts too—very cool!
• @agorecki added a Lux sensor to the Airthings Cloud integration—bright idea!
• The Squeezebox integration now includes service update entities, thanks to @pssc!
• @tedvdb added a status sensor to the Whois integration. Simple, but effective.
• @zerzhang added support for SwitchBot vacuums, and new lock models: the Lock Ultra and Lock Lite!
• @danielvandenberg95 updated the Sonos integration to show playlists under favorites. A great UX win!
• The Kostal Plenticore integration now supports installer login. Thanks for that improvement, @Schlauer-Hax!
• @Shulyaka added support for Anthropic Claude 4. Welcome to the future!
• And finally, @chemelli74 added preset mode support to the Comelit climate integration. Another nice quality-of-life addition!

Integration quality scale achievements

One thing we are incredibly proud of in Home Assistant is our integration quality scale. This scale helps us and our contributors to ensure integrations are of high quality, maintainable, and provide the best possible user experience.

This release, we celebrate several integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have improved their quality scale:

• 1 integration reached gold 🥇

  • SwitchBot, thanks to @zerzhang

• 1 integration reached silver 🥈

  • Shelly, thanks to @bieniu

This is a huge achievement for these integrations and their maintainers. The effort and dedication required to reach these quality levels is significant, as it involves extensive testing, documentation, error handling, and often complete rewrites of parts of the integration.

A big thank you to all the contributors involved! 👏

Farewell to the following

The following integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] are also no longer available as of this release:

• RTSPtoWebRTC has been removed as it has been replaced by the go2rtc integration.

Other noteworthy changes

There are many more improvements in this release; here are some of the other noteworthy changes:

• A small but neat one: @balloob made it so discoveries shown on an integration page are now sorted by title. Helpful!
• The Home Assistant Cloud integration will now raise a repair issue when your subscription has expired, helping make sure you’re aware and not caught off guard. Nice one, @ludeeus!
• More backup improvements! 🎉
  • Home Assistant will now raise a repair issue if not all add-ons or folders were successfully backed up. Thanks, @emontnemery!
  • @agners made it so that when an add-on is auto-updated, a backup is now correctly created as an “add-on”-backup. Great!
  • A new automatic backup event entity has been added to track automatic backups made by the system. Great addition by @mib1185!
• @lboue added support for the Matter pump device type. Another one added to the list—awesome!
• The Template integration got a big boost!
  • @Petro31 added modern-style YAML support for template fans, locks, alarm control panels, vacuums, and covers. So clean!
  • You can now create trigger-based template covers. Yep, also by @Petro31!
  • The trigger_variables option is now supported when using for in a trigger. A small but powerful feature. Thanks, @Petro31!
  • New template filters! You can now use from_hex, and base64_encode now supports both bytes and strings. Handy additions from @Petro31!
• New sensor capabilities:
  • @Passific added a new device class and units for reactive energy. Nice!
  • A new unit for energy distance (Wh/km) has been added. Thanks, @frenck!
  • Sensors now support mg/m³ as a concentration unit—another nice addition by @frenck!
  • @Arnie97 added support for liters as a unit for gas sensors. Much appreciated!
• The new recorder.get_statistics action lets you query statistics directly from the recorder. Powerful stuff, @Hypfer!

Sidebar improvements

If you didn’t know yet, you can actually adjust the contents of your Home Assistant sidebar. You can change the order and show/hide items by pressing and holding the “Home Assistant” text at the top of the sidebar, or by going to your user profile page and selecting “Change the order and hide items from the sidebar”.

This release brings a couple of much-needed improvements to this feature. When you customize the sidebar, it will now bring up a nice and clean dialog that allows you to drag and drop items to change their order, or hide them by clicking the eye icon next to them.

The biggest improvement is actually found somewhere else! Previously, the customization of the sidebar was only applied to the device you made the changes on; and even more annoying, sometimes it would lose the changes, or it would magically forget your settings on our [mobile companion apps] when you switched between your home network (and thus the internal URL). 🥲

In this release, this annoyance has been fixed! The sidebar customization is now stored in your user profile, so your personalized layout follows you across all devices you use with Home Assistant!

Join/unjoin groups of media players

Media players in Home Assistant can provide actions for media players to join or unjoin a group of media players. This is a great way to dynamically control your media players and the groups they are in. However, this feature was somewhat limited, as it could only be used as actions within things like automations or scripts.

Now, @AlexGustafsson changed that! 🎉

You can now use the media player card to join or unjoin groups of media players. This is a great way to control your media players and their groups directly from the UI.

Please note that, you can only join or unjoin groups of media players that support this feature. Unfortunately, not all media players support this, so it might not be available for all your media players.

Anyhow, amazing contribution Alex! 👏

Reset/restore entity IDs

You can now restore the ID of an entity to its original value. This is useful if you have renamed an entity and want to revert it back to its original entity ID.

This feature is available in the entity configuration dialog, where you can now find a “Reset” icon on the entity ID field. When clicked, it will restore the entity ID to its original value. Additionally, there is the option called “Recreate entity IDs” in the top right three-dotted menu on the device page, to reset all entity IDs of a device to their original values.

Patch releases

We will also release patch releases for Home Assistant 2025.6 in June. These patch releases only contain bug fixes. Our goal is to release a patch release every Friday.

2025.6.1 - June 13

• Fix palette handling for LIFX Ceiling SKY effect (@Djelibeybi - #146582)
• Fix fan is_on status in xiaomi_miio (@epenet - #146592)
• Drop HostKeyAlgorithms in aruba (@aethrvmn - #146619)
• Update frontend to 20250531.3 (@piitaya - #146638)
• Fix cookies with aiohttp >= 3.12.7 for Vodafone Station (@chemelli74 - #146647)
• Bump wakeonlan to 3.1.0 (@epenet - #146655)
• Bump hdate to 1.1.2 (@tsvi - #146659)
• Bump linkplay to v0.2.12 (@silamon - #146669)
• Filter speak notify entity for WHA devices in Alexa Devices (@chemelli74 - #146688)
• Bump aioamazondevices to 3.1.2 (@chemelli74 - #146690)
• Fix opower to work with aiohttp>=3.12.7 by disabling cookie quoting (@tronikos - #146697)
• Revert scan interval change in local calendar (@allenporter - #146700)
• Partial revert of update to remote calendar to fix issue where calendar does not update (@allenporter - #146702)
• Ignore lingering pycares shutdown thread (@cdce8p - #146733)
• Bump aiodns to 3.5.0 (@bdraco - #146758)
• Fix throttling issue in HomematicIP Cloud (@hahn-th - #146683)

2025.6.2 - June 23

• Remove address info from Rachio calendar events (@brg468 - #145896)
• Bump uiprotect to 7.12.0 (@RaHehl - #146337)
• Bump uiprotect to 7.13.0 (@RaHehl - #146410)
• Bump reolink-aio to 0.14.0 (@starkillerOG - #146566)
• Bump pypck to 0.8.7 (@alengwenus - #146657)
• Update rokuecp to 0.19.5 (@ctalkington - #146788)
• Use Shelly main device area as suggested area for sub-devices (@bieniu - #146810)
• Fix blocking open in Minecraft Server (@elmurato - #146820)
• Bump aioamazondevices to 3.1.3 (@chemelli74 - #146828)
• Bump aiohttp to 3.12.13 (@bdraco - #146830)
• Bump motion blinds to 0.6.28 (@starkillerOG - #146831)
• Bump pypck to 0.8.8 (@alengwenus - #146841)
• Fix missing key for ecosmart in older Wallbox models (@hesselonline - #146847)
• Bump bthome-ble to 3.13.1 (@Ernst79 - #146871)
• Bump reolink-aio to 0.14.1 (@starkillerOG - #146903)
• Add debug log for update in onedrive (@zweckj - #146907)
• Switchbot Cloud: Fix device type filtering in sensor (@SeraphicRav - #146945)
• Bump pySmartThings to 3.2.5 (@joostlek - #146983)
• Bump ical to 10.0.4 (@allenporter - #147005)
• Fix incorrect use of zip in service.async_get_all_descriptions (@emontnemery - #147013)
• Disable Z-Wave indidator CC entities by default (@MartinHjelmare - #147018)
• Fix Shelly entity names for gen1 sleeping devices (@bieniu - #147019)
• Disable Z-Wave idle notification button (@MartinHjelmare - #147026)
• Fix log in onedrive (@zweckj - #147029)
• Bump holidays lib to 0.75 (@gjohansson-ST - #147043)
• Bump aiohomeconnect to 0.18.0 (@Diegorro98 - #147044)
• Bump ZHA to 0.0.60 (@puddly - #147045)
• Bump pylamarzocco to 2.0.9 (@zweckj - #147046)
• Handle missing widget in lamarzocco (@zweckj - #147047)
• Bump aioamazondevices to 3.1.4 (@chemelli74 - #146883)
• Bump aioamazondevices to 3.1.12 (@chemelli74 - #147055)
• Bump uiprotect to version 7.14.0 (@RaHehl - #147102)
• Improve advanced Z-Wave battery discovery (@MartinHjelmare - #147127)
• Fix Charge Cable binary sensor in Teslemetry (@Bre77 - #147136)
• [ci] Bump cache key version (@cdce8p - #147148)
• Bump homematicip to 2.0.6 (@hahn-th - #147151)
• Wallbox fix too many requests by API (@hesselonline - #147197)
• Bump deebot-client to 13.4.0 (@edenhaus - #147221)
• Handle the new JSON payload from traccar clients (@ludeeus - #147254)
• Bump aioamazondevices to 3.1.14 (@chemelli74 - #147257)
• Bump uiprotect to version 7.14.1 (@RaHehl - #147280)
• Bump aioesphomeapi to 32.2.4 (@synesthesiam - #147100)
• Bump aioesphomeapi to 33.0.0 (@bdraco - #147296)
• Fix reload for Shelly devices with no script support (@chemelli74 - #147344)
• Add Matter protocol to Switchbot (@joostlek - #147356)

2025.6.3 - June 24

• Update frontend to 20250531.4 (@bramkragten - #147414)

Need help? Join the community!

Home Assistant has a great community of users who are all more than willing to help each other out. So, join us!

Our very active Discord chat server is an excellent place to be at, and don’t forget to join our amazing forums.

Found a bug or issue? Please report it in our issue tracker, to get it fixed! Or, check our help page for guidance for more places you can go.

Are you more into email? Sign-up for our Building the Open Home Newsletter to get the latest news about features, things happening in our community and other news about building an Open Home; straight into your inbox.

Backward-incompatible changes

We do our best to avoid making changes to existing functionality that might unexpectedly impact your Home Assistant installation. Unfortunately, sometimes, it is inevitable.

We always make sure to document these changes to make the transition as easy as possible for you. This release has the following backward-incompatible changes:

If you are a custom integration developer and want to learn about changes and new features available for your integration: Be sure to follow our developer blog. The following changes are the most notable for this release:

• Icon translations now support ranges
• Sensor device classes now have default display precision

All changes

Of course, there is a lot more in this release. You can find a list of all changes made here: Full changelog for Home Assistant Core 2025.6

We are today officially deprecating two installation methods and three legacy CPU architectures. We always strive to have Home Assistant run on almost anything, but sometimes we must make difficult decisions to keep the project moving forward. Though these changes will only affect a small percentage of Home Assistant users, we want to do everything in our power to make this easy for those who may need to migrate.

Beginning with Home Assistant 2025.6, affected systems will display a notification after updating, indicating that support will end in six months (with release 2025.12) and include a recommendation to migrate to a supported system. In this post, we’ll go into our thinking on these deprecations and our findings after consulting the community on these changes.

We have deprecated the following installation methods:

• Home Assistant Core installation method, where you run your system in a Python environment, not to be confused with Container (for example, running your system in Docker).
• Home Assistant’s Supervised installation method, which involves running your own operating system, then installing the Supervisor and other requirements on top of that.

These are advanced installation methods, with only a small percentage of the community opting to use them. If you are using these methods, you can continue to do so (you can even continue to update your system), but in six months time, you will no longer be supported, which I’ll explain the impacts of in the next section. References to these installation methods will be removed from our documentation after our next release (2025.6). Going forward Home Assistant OS and Home Assistant Container will become the only supported installation methods.

In the future, only the currently supported 64-bit architectures (aarch64 and amd64) will be used. The following legacy architectures are being deprecated:

• i386 (32-bit x86) is an architecture used by Intel and AMD predominantly before 2003, but some later processors still utilized it (e.g., early Intel Atom models).
• armhf (32-bit ARM hard-float) was used by very early single-board computers, notably the original Raspberry Pi.
• armv7 (32-bit ARM) was used by a number of early single-board computers, most notably the Raspberry Pi 2.

If you are one of the few with a system using these architectures, you will receive a notification after updating to 2025.6, and it will describe how to migrate your system. In six months, your system will become unsupported and will no longer receive updates.

Check our guide to see if your current Home Assistant installation is affected.

What does deprecated and unsupported mean

In the simplest terms, deprecation is where you stop recommending a certain feature to users as you intend to remove it soon. As we deprecated the Core and Supervised installations methods today, that means we are now working to remove all references to them from our documentation. The goal is to guide new users towards installation methods we plan to support long term, and discourage the use of those that are being phased out.

Even though they are being deprecated, we are committing to support them for a further six months (until release 2025.12), giving existing users time to migrate to Home Assistant OS or Container. During this time we will ensure these installation types keep functioning as normal during the deprecation period. However, after those six months have elapsed, these methods will become unsupported, which means issue reports will no longer be accepted. As these installation methods are used for the development of Home Assistant, it will still be technically possible to update them. We still would recommend migrating to a supported method, but that’s your choice.

As i386, armhf, and armv7 architectures have also been deprecated, we are currently removing references to them from our documentation. More importantly, they will also be subject to a six-month support window. After that support ends (from release 2025.12 onwards), we will no longer build or release distributions or containers targeting these platforms. This will mean that in six months’ time, there will be no more updates for these systems, and if users encounter issues, they will no longer be able to ask for support from Home Assistant maintainers.

Why we made this decision

Core and Supervised

From our opt-in analytics

The Core and Supervised installation methods are not only complex for users to install and maintain — they’re also challenging for the Home Assistant team to support. In the past, there were compelling reasons, outside Home Assistant development, to run these installation methods, but for most people those reasons are disappearing. Home Assistant OS is very capable with a rich ecosystem of add-ons, while also being easy to run in a virtual machine. Container adoption has become mainstream, now being widely available along with systems having more resources to run them. Steadily, we’ve seen year-on-year reductions in the percentage of Core and Supervised installations (currently standing at 2.5% and 3.3% respectively).

As Core and Supervised are more complex to maintain, they generate more issues that are more difficult to solve. This complexity places a disproportionate burden on our community-driven support system, where volunteers generously give their time to help others. It also takes time away from assisting the vast majority of users who are on the simpler to maintain installation methods. Along with this, new users could sometimes be swayed into running Core or Supervised, and have a bad experience that could cause them to give up on the best way to automate their home. By focusing our support and documentation on OS and Container methods, we can greatly improve the onboarding experience and ensure a smoother start for new users.

Legacy 32-bit architectures

Though Home Assistant is very lean and can run great on older or low-spec hardware, the architectures we’re deprecating are definitely on the leaner side of the spectrum. That probably explains why we see such low usage figures, with i386 and armhf architectures representing less than 0.5% of installations each, and armv7 at only 0.95% of installations. More than half of Home Assistant systems using armv7 have hardware that is capable of running 64-bit operating systems, like Raspberry Pi 3 and 4. This hardware can actually upgrade and migrate to a supported 64-bit version of our Home Assistant Operating System

The broader software and hardware industries have also shifted away from these older 32-bit systems. Most have adopted 64-bit architectures such as amd64 and aarch64, and we are seeing more projects we depend on no longer supporting these 32-bit architectures. There have already been several instances where keeping support for these architectures has held back the development of new features.

Your feedback

For any major change, it is our goal to make sure the community guides this decision-making. When our maintainers initially proposed these deprecations, we shared this plan with the community (in our forum, GitHub, Discord, Reddit, and other social channels), using it to gather feedback. It was a constructive, civil discussion, and we learned a couple of interesting things that have helped us move this decision forward.

First, our current wording is confusing to the community. Core and Supervisor are components of Home Assistant OS, but are also similar—or the same—as the names of installation methods, which is not super clear for new users. We also found these installation methods being used in ways we never expected, and there are a good number of people who were already running Home Assistant in custom and unsupported ways, not even realizing they were unsupported.

Many of those impacted asked for better guidance on how to migrate. A good number were unaware of our expansion of backup and restore features to all installation methods, significantly smoothing their transition to a new platform.

Check if you’re affected

The blue arrow shows your installation type, and the red arrow displays the architecture.

If you are unsure which installation method you are running:

• Select this link OR Navigate to Settings > System > Repairs, select the three-dotted menu in the top right corner, and select System information.
• Check the Installation type field. If you are running Home Assistant OS, or Container, you are fine as the installation method deprecation doesn’t apply to you.

In this same window, you can find the architecture as well:

• The CPU architecture field will tell you exactly which architecture you are using. If you are seeing aarch64 or x86_64 here, you are fine as the architecture deprecation doesn’t apply to you.

How to migrate

Green are staying, and red are deprecated.

If it’s been a while since you’ve migrated Home Assistant systems, a lot has improved over the past several years. Switching systems is as easy as making a backup, downloading it, and restoring it during the initialization of your new system (Home Assistant Cloud subscribers using off-site backups can restore with just their password). Every Home Assistant installation method now has backups, and you can restore backups from any method onto another regardless of the differences in architecture. In many cases, very little needs to be done once the restore is successful (to the dismay of tinkerers online). Our documentation has a full list of guides on how to install Home Assistant on different hardware.

Before you think about migrating to a different installation method, you can always choose to stick with what you have. Just because it becomes unsupported by the Home Assistant project, it doesn’t mean you can’t keep running it like you do today. That choice is up to you.

For Home Assistant Core users, the closest alternative is Home Assistant Container, which is most commonly used with Docker. If you can dedicate a device exclusively to Home Assistant, the recommended installation method is Home Assistant OS, which gives an appliance-like setup.

For Home Assistant Supervised users, we recommend migrating to Home Assistant OS—it supports everything Supervised does, including add-ons. If you want more control over the OS, you can also run Home Assistant OS in a virtual machine, like with Proxmox, or go the Home Assistant Container path alternatively.

For deprecated architectures, there is generally no supported migration path using your existing hardware. You will therefore need to find alternative hardware compatible with Home Assistant OS or Container. Second-hand single-board computers and recycled small-form-factor office machines are affordable and sustainable options. In some cases, your system may be running a 32-bit operating system, but is capable of running a 64-bit one (Raspberry Pi 3 and 4 are examples of systems often running a 32-bit OS despite being capable of running 64-bit). In this case, you will need to install a 64-bit capable operating system and restore Home Assistant on that system.

Frequently asked questions

• If Home Assistant Core is used for development, and part of the developer docs, why not just offer it to end-users?
  This is not just about technical viability, it is also about helping and supporting people with their issues, problems, and questions, in our forums and chat. Having these options available to less technical people leads to support queries, and if they have a bad first experience that reflects poorly on the project. Users are free to continue running their systems the way they would like.

• No support for Core or Supervised—can I still use them?
  You can still use them even if we no longer support them. There are many users running Home Assistant in all kinds of unofficial ways. This change just means we are removing it from our end-user documentation and will no longer recommend using these installation methods from an official standpoint.

• Will the developer documentation on these things remain?
  Yes, those will remain. The developer documentation for running Home Assistant’s Core Python application directly in a Python virtual environment will remain. This is how we develop. This proposal is about removing end-user documentation and support.

• Can I start maintaining these installation methods?
  While maintaining these methods will require effort, the community is free to move documentation and code to new independent projects. Our maintainers will no longer accept issues or provide end-user documentation, but that shouldn’t stop anyone passionate about them from continuing to run them, or helping others to do the same.

• Can I reproduce any of the installations you offer?
  Yes, of course! All our pipelines are open source and transparent, you can always recreate any of our pipelines and release artifacts; either automated or manual.

• Is this the first step towards making Home Assistant closed source/proprietary/commercial?
  No, that is impossible. Home Assistant will always remain open source. Home Assistant is owned by the Open Home Foundation, a Swiss non-profit foundation that is audited and governed, and—by law—bound by its mission. This means it will always be open source and cannot be bought or sold.