We’re thrilled to extend a very warm (ahem) Works with Home Assistant welcome to Heatit! As the name suggests, Heatit are all about keeping you, and your home, warm. They specialize in smart climate and heating control, which might have something to do with the fact they’re based in Norway, where energy management is a big reason people turn to Home Assistant, as winter temperatures can dip to below -20°C!

Home is where the heat is

Formerly known as Thermofloor, Heatit has spent more than 30 years building a rock-solid reputation across Scandinavia and Northern Europe for thermostats and controllers designed to handle harsh conditions, so they’re certainly robust enough for milder climes. But they don’t just stop at heating: the range extends to home safety, with the Heatit Z-Smoke 2 being the first Z-Wave smoke detector we’ve certified.

In fact, all of Heatit’s certified devices connect via Z-Wave, which is what makes them integrate so well with Home Assistant. Crucially, the Z-Smoke 2 will always function regardless of network status. The smart features are there when you need them, but the fundamentals never depend on them.

Z-Wave, and then some

If you’ve not heard of Z-Wave before, here’s a quick explainer: it’s a low-power wireless protocol built specifically for smart homes. Unlike WiFi, it operates on a dedicated frequency that means less interference and more reliable communication. It’s also a mesh network, where mains-powered devices help pass signals along to each other, strengthening the connection. Battery-powered devices can also benefit from this, since the mesh helps preserve their charge.

For heating and safety devices, those enhancements really count. Long battery life means a thermostat or smoke detector that should keep working without constant attention. Reliable range means your devices can stay connected even through thick walls or across a large home. And because everything runs locally, your heating responds quickly: no routing through a third-party server, no unnecessary delays.

Connecting with the community

Heatit are also serious about the impact they have beyond their products, with sustainability and reducing environmental impact being central to their company philosophy, which aligns with the Open Home Foundation’s principles of privacy, choice, and sustainability. What’s more, for Heatit, one of the most exciting things about joining the program is the chance to connect with the passionate, knowledgeable people who make up our community (yes, that’s you!).

Devices

Works with Home Assistant isn’t just a badge: every certified product is rigorously tested by our in-house team to make sure it works seamlessly with Home Assistant out of the box. Brands joining the program also commit to long-term support and firmware updates, and to being an active, positive part of our community. Here’s what’s made the cut from Heatit:

• Heatit Z-Push Wall Controller
• Heatit Z-Temp3
• Heatit Z-TRM6 DC
• Heatit Z-Smoke 2
• Heatit ZM Thermostat 16A
• Heatit Z-HAN2

Professionally built and designed to last, these devices cover both sides of a smart heating setup: the thermostats handle the actual temperature control, while the wall controller gives you a physical way to manage it all without reaching for your phone.

How to get started

It’s worth noting that in-wall devices will require installation by a qualified electrician in many regions, so if you’re not confident with electrics, it’s worth checking Heatit’s website for guidance and to find a local installer. The standalone devices are more straightforward to set up, and include SmartStart, making adding them to your Z-Wave network as simple as scanning a QR code.

To use Z-Wave with Home Assistant, you’ll need a Z-Wave adapter and the Z-Wave integration. This will help everything run locally, keeping your data private and your smart home responsive. Of course, if you want to turn the heat up before you get home, or check on things while you’re away, Home Assistant Cloud gives you secure remote access, and by subscribing you’ll help fund the Open Home Foundation’s work, including the Works with Home Assistant program!

Wrapping up warmly

We hope this is just the beginning of Heatit’s involvement with the program, and we’re excited to see where things go, both with these devices and whatever comes next. In the meantime, there’s plenty here to get started with. Time to turn up the heat.

Frequently asked questions

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

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 in the future, or it might work under a different connectivity type that we don’t currently test under the program.

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

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.

How were these devices tested?

All devices in this list were tested using a standard Home Assistant Green with the Home Assistant Connect ZWA-2 as the Z-Wave adapter and with our Z-Wave integration. If you have another hub or 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.

Will you be adding more Heatit devices to the program?

Why not! We’re thrilled to foster a close relationship with the team at Heatit to work together on any upcoming releases or add in further products that are not yet listed here. They have also been working on integrating their WiFi products further in Home Assistant, so we’re excited to see their progress.

Home Assistant 2026.3! 🎉

After last month’s massive release, this one is a nice and relaxed one. We took a step back from the big headline features and fully focused on something equally important: getting the amazing contributions from our community reviewed, polished, and merged. 💚

And did our community deliver! This release is packed with tons of new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more], lots of noteworthy improvements to the ones you already use, boatloads of bug fixes, and a really nice list of integrations that climbed up the integration quality scale. 📈

It’s releases like these that really show the strength of our open-source community. Every single contribution matters, and this month that shows more than ever. Thank you all! 🙏

My personal favorite this month? The automation editor change: Continue on error has finally landed in the UI. I actually wrote this feature years ago, but it was only available through YAML. Seeing it now land in the visual editor (making it accessible to everyone) is just awesome. It’s one of those small things that make a big difference in everyday use. 🤩

Oh, and before I forget: have you seen our brand new merch store? The Open Home Foundation store is live! I have to be honest: the quality is really great. The hoodie is so darn comfy it’s ridiculous. I’ve been wearing mine non-stop. Go check it out! 🏃

Also, mark your calendars: State of the Open Home 2026 is happening on April 8 in Utrecht, the Netherlands! Join us live in the audience for a celebration of everything we’ve built together, a look at what’s ahead, and your chance to help shape the future of the Open Home. Tickets are limited, so grab yours while you can! 🎟️

Enjoy the release!

../Frenck

• Send your vacuum to clean specific areas
  • Getting started
  • Paving the way for voice
• Energy dashboard improvements
• Continue on error in the automation editor
• Wake word detection on your Android phone (experimental)
  • Battery usage
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
• Other noteworthy changes
  • Running on Python 3.14 🚀
• Patch releases
  • 2026.3.1 - March 6
  • 2026.3.2 - March 16
  • 2026.3.3 - March 20
  • 2026.3.4 - March 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 @TimoPtr, @arturpragacz, and @MindFreeze who helped write the release notes this release. Also, @CoMPaTech, @balloob, @OnFreund, and @silamon for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️

Send your vacuum to clean specific areas

Got a robot vacuum? You can now tell it exactly which areas to clean! This release introduces the clean area action, which lets you send your vacuum to clean one or more specific areas on demand, right from Home Assistant. In this release, it’s supported by Matter, Ecovacs, and Roborock.

The best part? The action uses your existing Home Assistant areas, not some obscure vendor-specific identifiers. You simply map the segments your vacuum knows about to the areas you’ve already set up in Home Assistant, and that’s all there is to it.

Getting started

When your vacuum supports area cleaning, you can set up the mapping through the vacuum’s entity settings. Open the vacuum entity, select the settings icon, and look for the Map vacuum segments to areas section. From there, you can match the segments your vacuum has detected to your Home Assistant areas.

If your vacuum’s internal segment layout ever changes (for example, after remapping in the manufacturer’s app or the vacuum rediscovering its environment), Home Assistant will notice. A repair issue will alert you that the segments have changed, so you can update your mapping and make sure everything stays in sync.

Paving the way for voice

Because the mapping uses native Home Assistant areas, this feature lays the groundwork for future voice assistant support. Imagine simply saying “clean the kitchen” and having your vacuum head to the right area. That’s not available just yet, but the foundation is now in place to make it happen.

Energy dashboard improvements

The Energy dashboard received a nice batch of improvements this release.

The Now view gained badges that show real-time power consumption, gas flow rate, and water flow rate at a glance. Water also gets its own Sankey chart in the Now view, giving you a visual breakdown of water usage across your home, just like the existing power Sankey chart.

To reduce ambiguity, the second tab on the Energy dashboard has been renamed from Energy to Electricity, since the dashboard covers electricity, gas, and water. On the configuration side, the energy settings page is now split into three tabs: Electricity, Gas, and Water, making it easier to find and manage your energy sources.

Finally, energy bar chart tooltips now include the day of the week, helping you quickly spot usage patterns.

Thanks, @MindFreeze, @NoRi2909, and @gpoitch! 🎉

Continue on error in the automation editor

The automation editor now has a Continue on error option for actions, directly accessible from the visual editor. Previously, this setting was only available through YAML.

You can find it in the three-dots menu of any action. When enabled, a visual indicator appears on the action row, so you can quickly see which actions will continue running even if they encounter an error.

This is especially handy for automations where a single failing action shouldn’t stop the rest from running. For example, if one of several notification actions fails, the remaining ones will still be sent.

Thanks, @wendevlin! 🎉

Wake word detection on your Android phone (experimental)

Your phone just became a voice satellite! The Home Assistant Companion app for Android now supports on-device wake word detection, allowing you to open Assist from anywhere; even when your phone is locked.

Inspired from the great work from @brownard in Ava.

This feature uses microWakeWord, the same lightweight wake word engine that powers the Home Assistant Voice Preview Edition. All processing happens locally on your device, no audio is sent to the cloud, and no server-side processing is needed. Your voice stays on your phone.

You can choose between three wake words:

• Okay Nabu
• Hey Jarvis
• Hey Mycroft

To enable wake word detection, open your Android device’s Settings > Companion App > Assist for Android, and enable the Enable wake word detection toggle. Once enabled, simply say your chosen wake word and the Assist pipeline will open, ready to take your command.

Watch the video to see wake word detection in action on an Android device.

It already integrates with your voice equipment at home, and if another satellite is nearby, only the fastest one will respond. This also applies to multiple Android devices.

Battery usage

Because wake word detection requires continuous microphone access and CPU usage, this feature does have a noticeable impact on battery life. To help manage this, you can use automations to start and stop wake word detection based on your context, for example, only enabling it when you’re connected to your home Wi-Fi or within a specific zone. This way, you get hands-free voice control when it matters most, without draining your battery all day.

Thanks, @TimoPtr! 🎉

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:

• Ghost, added by @JohnONolan
  Monitor your Ghost publication metrics, including member counts, revenue, post statistics, and email newsletter performance, right from your Home Assistant dashboard.

• Hegel Amplifier, added by @boazca - launching at 🥈 silver quality
  Control your Hegel Music Systems amplifiers locally over your network. Manage power, volume, input selection, and mute with real-time push updates for instant feedback.

• Homevolt, added by @Danielhiversen - launching at 🥈 silver quality
  Read local data from your Homevolt battery over your network, no cloud required. Monitor power, energy, voltage, temperature, and battery status.

• Hypontech Cloud, added by @jcisio
  Monitor your Hypontech solar inverter system through the Hypontech Cloud platform. Track power production, energy yields, and system status.

• IDrive e2, added by @patrickvorgers
  Back up your Home Assistant to an IDrive e2 bucket. IDrive e2 offers affordable S3-compatible cloud storage with flexible access controls for keeping your backups safe.

• Indevolt, added by @Xirt
  Communicate directly with your Indevolt energy storage devices over the local network. Monitor energy production, consumption, and battery status.

• IntelliClima, added by @dvdinth
  Integrate your Fantini Cosmi Ecocomfort 2.0 ventilation devices. Control fan modes and speeds of your mechanical ventilation with heat recovery system.

• Liebherr, added by @mettolen - launching at 🥈 silver quality
  Control and monitor your Liebherr SmartDevice refrigerators and freezers via the cloud. Monitor temperatures, adjust cooling settings, and automate food safety alerts.

• MTA New York City Transit, added by @OnFreund - launching at 🥈 silver quality
  Get real-time arrival predictions for all NYC subway and bus lines using data from the Metropolitan Transportation Authority (MTA).

• MyNeomitis, added by @l-pr
  Connect your Axenco MyNeomitis heating and energy management devices, such as electric radiators, towel rails, and underfloor heating, to Home Assistant.

• OneDrive for Business, added by @zweckj - launching at 🏆 platinum quality
  Use OneDrive for Business as a backup location for your Home Assistant backups. Great for users with a Microsoft 365 business subscription.

• Powerfox Local, added by @klaasnicolaas - launching at 🏆 platinum quality
  Gather data from your Powerfox Poweropti device directly over your local network, offering faster updates with no cloud dependency.

• Redgtech, added by @Jonhsady
  Connect your Redgtech smart switches to Home Assistant. Control and monitor your cloud-connected switches and relays from this Brazilian smart home brand.

• System Nexa 2, added by @konsulten - launching at 🥈 silver quality
  Integrate your System Nexa 2 smart home devices locally. Control lights, switches, and smart plugs with support for dimmers and outdoor plugs.

• Teltonika, added by @karlbeecken - launching at 🥈 silver quality
  Monitor your Teltonika Networks routers running RutOS. Track cellular signal quality, modem temperature, and network connectivity.

• Trane Local, added by @bdraco
  Locally control Trane and American Standard thermostats over your network using a direct mTLS connection. No cloud required.

• Zinvolt, added by @joostlek
  Monitor your Zinvolt batteries in Home Assistant, including state of charge and other battery metrics.

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:

• Ubisys, provided by ZHA, added by @abmantis

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 ones are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• Matter now supports carbon monoxide alarm states and TVOC air quality level sensors. If you have Matter-certified CO sensors or air quality devices, they now show up in Home Assistant. Thanks, @Leo2442926161 and @lboue!
• HomeKit Controller now exposes water level sensors, so devices like the Smartmi Humidifier Rainforest will show their current water level in Home Assistant. Thanks, @romanlytvyn!
• Reolink cameras gained five new diagonal and continuous rotation PTZ buttons, plus the PTZ patrol switch now correctly reports its real-time status. Thanks, @starkillerOG!
• SmartThings now supports dual-cavity Samsung ovens, with separate entities for each chamber. It also gained switch and select controls for Samsung dishwasher washing options like sanitize, heated dry, and speed booster. Thanks, @mik-laj and @edu-tsen!
• Roborock now fully supports Zeo washing and drying machines with program selection, temperature control, drying modes, and detergent status sensors. Thanks, @yangqian!
• OpenAI Conversation now supports the gpt-image-1.5 image generation model for AI Tasks, offering cheaper and faster image generation. Thanks, @Shulyaka!
• UniFi Protect cameras now have PTZ support with a ptz_goto_preset action for triggering presets and a PTZ patrol select entity with live state updates. Thanks, @RaHehl!
• SwitchBot now lets you add passwords to Keypad Vision devices programmatically. It also gained a slow mode setting for curtain devices, which can reduce noise and improve reliability with heavier curtains. Thanks, @zerzhang and @ljmerza!
• Alexa Devices now supports Amazon Air Quality Monitor devices, exposing sensors for air quality index, VOC index, humidity, temperature, and particulate matter. Thanks, @jamesonuk!
• VeSync humidifiers now have a switch to enable or disable auto-drying mode for humidifier pads. Thanks, @cdnninja!
• SwitchBot Cloud now supports the SwitchBot AI Art Frame with battery level, next/previous picture buttons, and a display image entity showing the current picture. Thanks, @XiaoLing-git!
• KNX now allows configuring number entities and sending the current time directly from the UI. Additionally, expose gained a new periodic send option to periodically re-send entity states to the bus. Thanks, @farmio!
• MELCloud air-to-water devices now have additional sensors for RSSI signal strength, condensing temperature, fan frequency, and estimated energy produced. Thanks, @ffourcot!
• Nanoleaf replaced its underlying library with aionanoleaf2, fixing authorization errors that prevented newer Nanoleaf Essentials devices from connecting. Thanks, @loebi-ch!
• Uptime Kuma monitors now have uptime ratio and average response time sensors for 1-day, 30-day, and 365-day periods. Thanks, @tr4nt0r!
• Radarr gained two new actions: radarr.get_movies and radarr.get_queue, returning detailed information about movies in your library and the current download queue. Thanks, @Liquidmasl!
• Renault vehicles now have buttons to remotely sound the horn or flash the lights. Thanks, @sebastiaanspeck!
• Proxmox VE gained a sensor platform with CPU usage, memory usage, disk usage, and status sensors for nodes, virtual machines, and containers. Thanks, @erwindouna!
• Mealie now has a get_shopping_list_items action that returns structured shopping list data, useful for automations that need more detail than the to-do entity provides. Thanks, @andrew-codechimp!
• Ambient Weather Station now exposes sensors for the AQIN indoor air quality monitor, including PM2.5, PM10, CO2, temperature, humidity, and AQI measurements. Thanks, @n-6!
• WeatherFlow Tempest stations now show battery level as a percentage for consistency with other integrations. Thanks, @pkolbus!
• SleepIQ now provides five new sleep health sensors per sleeper: sleep score, sleep duration, heart rate average, respiratory rate average, and heart rate variability. Thanks, @rhcp011235!
• Anthropic now supports the Claude Opus 4.6 model with adaptive thinking effort levels, and gained native structured outputs for more accurate tool calls on models 4.5 and newer. Thanks, @Shulyaka!
• Tessie received several enhancements: an energy remaining sensor for vehicles, battery health diagnostics, island and grid status sensors for energy sites, and full energy history support for the Home Assistant Energy Dashboard. Thanks, @jrhillery and @Bre77!
• Portainer now supports Docker stack monitoring and control with status sensors, container counts, and start/stop switches. It also gained a prune_images action to clean up unused Docker images. Thanks, @erwindouna!
• Nintendo Parental Controls now has a bedtime end time entity, complementing the existing bedtime start time for a complete bedtime schedule. Thanks, @pantherale0!
• LG Soundbar now supports play/pause media control, shows track title, artist, and album art, and reports playing/paused state. Thanks, @alexmerkel!
• Velux now supports on/off switches connected to the KLF 200 gateway. Thanks, @wollew!
• Switcher now supports Switcher heater devices for monitoring and control. Thanks, @YogevBokobza!
• Cambridge Audio devices now have a room correction switch for compatible models. Thanks, @noahhusby!
• Vera metered switches now expose power and energy sensors, bringing energy monitoring to your Vera devices. Thanks, @jronnols!
• Control4 thermostats now support fan mode control with Auto, Circulate, and On modes. Thanks, @davidrecordon!
• BSB-Lan now shows the current HVAC action (heating, cooling, idle) on the climate entity and gained a button to synchronize your heating system’s clock. Thanks, @liudger!
• JVC Projector gained a wide range of new sensors and controls: source, color depth, HDR status, picture mode, installation mode, light power, and switches for E-Shift and Low Latency Mode. Thanks, @SteveEasley!
• NRGkick EV chargers now have a switch to enable or pause car charging directly from Home Assistant. Thanks, @andijakl!
• Green Planet Energy now shows timestamp sensors for the highest and lowest energy price times of the day, helping you time your energy usage. Thanks, @petschni!
• Compit expanded significantly with new water heater, number, and binary sensor platforms for controlling hot water, adjusting temperature settings, and monitoring device states across their HVAC product range. Thanks, @Przemko92!
• Saunum now has a start_session action, letting you start a sauna session with custom duration, target temperature, and fan duration in a single call. Thanks, @mettolen!
• Watts Vision + now supports controlling smart switches alongside the existing thermostat support. Thanks, @theobld-ww!
• Sunricher DALI now tracks energy consumption for DALI light devices connected through a Sunricher gateway. Thanks, @niracler!

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:

• 9 integrations reached platinum 🏆

  • GIOŚ, thanks to @mik-laj
  • HDFury, thanks to @glenndehaan
  • Immich, thanks to @mib1185
  • Namecheap DynamicDNS, thanks to @tr4nt0r
  • Portainer, thanks to @erwindouna
  • Ubiquiti airOS, thanks to @CoMPaTech
  • Watts Vision +, thanks to @theobld-ww
  • WLED, thanks to @mik-laj
  • Xbox, thanks to @tr4nt0r

• 1 integration reached gold 🥇

  • UptimeRobot, thanks to @chemelli74

• 6 integrations reached silver 🥈

  • BSB-Lan, thanks to @liudger
  • devolo Home Control, thanks to @Shutgun
  • Mastodon, thanks to @andrew-codechimp
  • NRGkick, thanks to @andijakl
  • Teslemetry, thanks to @Bre77
  • Velux, thanks to @wollew

• 7 integrations reached bronze 🥉

  • Aladdin Connect, thanks to @JamieMagee
  • Anthropic, thanks to @Shulyaka
  • OpenAI, thanks to @zweckj
  • OpenEVSE, thanks to @c00w
  • Prana, thanks to @prana-dev-official
  • Splunk, thanks to @Bre77
  • VeSync, thanks to @cdnninja

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:

• InfluxDB, done by @RobBie1221
• Ness Alarm, done by @Poshy163
• Splunk, done by @Bre77

Other noteworthy changes

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

• The settings pages for Matter, Z-Wave, Zigbee, and Bluetooth have been reorganized for better clarity and discoverability. Thanks, @matthiasdebaat!
• You can now ask your Assist to remove items from a to-do list! The new remove item intent complements the existing complete item intent, so managing your lists by voice just got even easier. Thanks, @mistic100!
• The statistics graph card editor now offers “Year” as a selectable period, making it easy to view annual trends right from the UI. Thanks, @karwosts!
• The Security dashboard now also shows window-type covers (automated windows), so they appear alongside your other window and door sensors. Thanks, @jhenkens!
• The sections view now supports footer cards, giving you a sticky card at the bottom of the viewport, similar to the existing view header. Thanks, @MindFreeze!

Running on Python 3.14 🚀

This release ships running on Python 3.14! In case you are wondering what that means: Python is the programming language Home Assistant is built with.

So, why does it matter to you? Python 3.14 brings performance improvements to the foundation that Home Assistant is built on. The new version includes a faster interpreter, improved startup times, and better memory usage, all of which contribute to a snappier Home Assistant experience. 🚀

Don’t worry! We handle the upgrade to Python 3.14 automatically for you on all officially supported installation methods. Just upgrade Home Assistant as you normally would, and you are good to go! 😎

Patch releases

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

2026.3.1 - March 6

• Fix Rain Bird controllers updated by Rain Bird 2.x (@rblakemesser - #163915)
• Bump spotifyaio to 2.0.2 (@joostlek - #164114)
• Hunter Douglas Powerview: Fix missing class in hierarchy. (@gwww - #164264)
• Ensure Snapcast client has a valid current group before accessing group attributes. (@mill1000 - #164683)
• Fix button entity creation for devices with more than two radios (@tl-sl - #164699)
• Fix IntesisHome outdoor_temp not reported when value is 0.0 (@antonio-mello-ai - #164703)
• Update keyboard_remote dependencies (@lanrat - #164755)
• more programs for Miele steam ovens (@sean797 - #164768)
• Enforce SSRF redirect protection only for connector allowed_protocol_schema_set (@RaHehl - #164769)
• Remove caio from licenses exception list (@epenet - #164806)
• Add device class to active_liter_lpm sensor (@glenndehaan - #164809)
• Update ness_alarm scan interval to 5 secs (@Poshy163 - #164835)
• Fix Ghost config flow using wrong field name for site UUID (@JohnONolan - #164836)
• Fix KNX sensor default attributes for energy and volume DPTs (@farmio - #164838)
• Fix volvo test RuntimeWarning (@cdce8p - #164845)
• Fix ‘this’ variable in template options flow (@Petro31 - #164866)
• Bump onedrive-personal-sdk to 0.1.5 (@zweckj - #164880)
• Pass in Base Url during Roborock reauth (@Lash-L - #164903)
• Bump aiovodafone to 3.1.3 (@chemelli74 - #164955)
• Fix energy unit in Homevolt (@Danielhiversen - #164959)
• Bump python-bsblan to 5.1.1 (@liudger - #164591)
• Bump python-bsblan to 5.1.2 (@liudger - #164963)
• Change setpoint step size in IronOS integration (@tr4nt0r - #164979)
• Bump aioswitcher to 6.1.1 (@thecode - #164981)
• Bump teltasync to 0.2.0 (@karlbeecken - #164995)

2026.3.2 - March 16

• Fix wifi switch status and add 100% coverage for Fritz (@chemelli74 - #164696)
• Fix dnd switch status for Alexa Devices (@chemelli74 - #164953)
• Fix cover state updates for legacy Multilevel Switch based Z-Wave covers (@AlCalzone - #165003)
• Bump yalexs-ble to 3.2.8 (@bdraco - #165018)
• Update pychromecast to 14.0.10 (@elupus - #165069)
• Fix forced VERIFY_SSL in Portainer (@erwindouna - #165079)
• Bump pyportainer 1.0.32 (@erwindouna - #164803)
• Bump pyportainer to 1.0.33 (@erwindouna - #165080)
• Make restore state resilient to extra_restore_state_data errors (@arturpragacz - #165086)
• Bump pyanglianwater to 3.1.1 (@pantherale0 - #165097)
• Bump jvc_projector dependency to 2.0.2 (@SteveEasley - #165099)
• Add missing code for Miele dryer (@astrandb - #165122)
• Add reorder support to area selector (@bramkragten - #165211)
• Bump onedrive-personal-sdk to 0.1.6 (@zweckj - #165219)
• Fix switch set for Vodafone Station (@chemelli74 - #165273)
• Bump python-otbr-api to 2.9.0 (@TheJulianJES - #165298)
• Bump ohme to 1.7.0 (@dan-r - #165318)
• Bump pyjvcprojector to 2.0.3 (@SteveEasley - #165327)
• August oauth2 exception migration (@zachfeldman - #165397)
• Bump onedrive-personal-sdk to 0.1.7 (@zweckj - #165401)
• Remove stateclass from timestamp entity in Intellifire (@joostlek - #165403)
• Update govee local api to 2.4.0 (@Galorhallen - #165418)
• Update frontend to 20260312.0 (@bramkragten - #165420)
• Bump ZHA to 1.0.2 (@TheJulianJES - #165423)
• Handle OAuth token request exceptions in Yale setup (@bdraco - #165430)
• Bump orjson to 3.11.7 (@edenhaus - #165443)
• Bump pySmartThings to 3.7.0 (@joostlek - #165468)
• Bump aioamazondevices to 13.0.1 (@chemelli74 - #165476)
• Fix victron_ble warning sensor using duplicate alarm translation key (@rajlaud - #165502)
• Fix MQTT device tracker overrides via JSON state attributes without reset (@jbouwh - #165529)
• Upgrade ical dependency to 13.2.2. (@allenporter - #165642)
• Bump aiocomelit to 2.0.1 (@chemelli74 - #165663)

2026.3.3 - March 20

• Fix Tibber update token (@Danielhiversen - #164295)
• Add correct speed fan mapping for Z-Wave GE/Jasco Enbrighten ZWA4013 (@martinecker - #164500)
• Improve ProxmoxVE permissions validation (@CoMPaTech - #164770)
• Start orphaned entries in normal mode only (@erwindouna - #164815)
• Skip unmapped and watchdog event types in Hikvision NVR event injection (@ptarjan - #165009)
• Snapcast: Fix incorrect identifier extraction in async_join_players (@mill1000 - #165020)
• Hive: Fix bug in config flow for authentication and device registration (@KJonline - #165061)
• LG Soundbar: Fix incorrect state and outdated track information (@alexmerkel - #165148)
• Fix optional static values in bsblan (@liudger - #165488)
• Fix SmartLithium 8-cell support in victron_ble (@rajlaud - #165496)
• Fix Matter firmware update detection when version strings are identical (@lboue - #165509)
• Bump pyOpenSSL to 26.0.0 (@edenhaus - #165770)
• Bump pySmartThings to 3.7.2 (@joostlek - #165810)
• Bump axis to v67 (@Kane610 - #165840)
• Fix Abort exception caught by wrong handler in backup encrypt/decrypt (@agners - #165852)
• Proxmox fix restart/reboot action (@erwindouna - #165901)
• Do not use moving states for Multilevel Switch CC v1-3 Z-Wave covers (@AlCalzone - #165909)
• Fix unit when plant power is above 1000W in Hypontech (@jcisio - #165959)
• Bump hyponcloud from 0.3.0 to 0.9.0 (@jcisio - #166005)
• Don’t create fridge setpoint if no range in SmartThings (@joostlek - #166018)
• Fix enable/disable device tracking feature during setup of FRITZ!Box Tools (@mib1185 - #166027)
• Bump opower to 0.17.1 (@tronikos - #166044)
• Properly handle buttons of SMLIGHT SLZB-MRxU devices (@tl-sl - #166058)
• Bump Pysmlight to 0.3.0 (@tl-sl - #165658)
• Bump Pysmlight 0.3.1 (@tl-sl - #166060)

2026.3.4 - March 24

• Correct validation of scripts in template entities (@Petro31 - #165226)
• Update starlink-grpc-core to 1.2.4 (@boswelja - #165882)
• Bump python-google-weather-api to 0.0.6 (@tronikos - #166085)
• Bump xiaomi-ble to 1.10.0 (@xuejuhui - #166099)
• Add additional miele oven programs (@sean797 - #166100)
• Bump aiotedee to 0.2.27 (@zweckj - #166101)
• Fix reload of FRITZ!Box Tools in case of connection issues (@mib1185 - #166111)
• Bump wolf_comm to 0.0.48 (@EnjoyingM - #166144)
• Bump oralb-ble to 1.1.0 (@bdraco - #166165)
• Fix zwave_js fan speed mapping for GE/Jasco Enbrighten 55258 / ZW4002 (@airdrummingfool - #166169)
• Bump tplink-omada-client to fix breaking changes in Omada API (@MarkGodwin - #166206)
• Bump greenplanet-energy-api from 0.1.4 to 0.1.10 (@petschni - #166217)
• Bump yolink-api to 0.6.3 (@matrixd2 - #166232)
• Update frontend to 20260312.1 (@bramkragten - #166251)
• Update template light test framework (@Petro31 - #164688)

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:

• async_listen in Labs is deprecated
• Changes in OAuth 2.0 helper error handling
• Custom integrations can now ship their own brand images
• Reconfiguration support for webhook helper
• Remove deprecated light features

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 2026.3.

After an amazing 2025 that saw 12 new Works with Home Assistant partners join the program, it’s now time to say “Hei” to the first partner joining us this year: Heiman.

Founded back in 2005, Heiman specialize in smart home security devices, and are bringing an impressive selection of safety-focused sensors and alarms to the program: including the first Matter carbon monoxide alarms to be certified, along with smoke alarms designed for international markets.

Keep it local, keep it safe

If you’re new to the Works with Home Assistant program, it’s designed to help you identify devices that work brilliantly with Home Assistant, and support the Open Home Foundation’s principles of privacy, choice, and sustainability.

These values all pivot around local control, something that’s essential when it comes to home safety. Your smoke and CO alarms need to work when you need them most, regardless of your internet connection or cloud service status (though if you want to check in on your devices while away from home, Home Assistant Cloud provides secure remote access, and your subscription helps fund this very program, among other things!).

Our in-house team has thoroughly tested Heiman’s devices to ensure they meet this key requirement, and we’re happy to report they did! But Heiman has gone further still by using the Matter open connectivity standard…

Why this matters

Matter was launched to be a unifying connectivity type with interoperability at its heart. Instead of being locked into one company’s ecosystem, Matter devices work across Home Assistant, as well as other platforms like Google Home.

Heiman’s Matter devices work over Thread, which adds another layer of benefits. Thread is a low-power wireless mesh network protocol that creates resilient connectivity throughout your home, perfect for battery-powered sensors that need reliable communication while staying energy efficient. This is ideal for battery-powered sensors like Heiman’s that need to be energy efficient while maintaining reliable communication.

So why does all this matter for safety devices specifically? Well firstly, it’s important to know these smart devices will still work as “dumb” ones, so there’s always a failsafe if you decide to rebuild your Thread network, or start making tweaks. If your sensors integrate locally, it means you can automate basic checks, such as reminders to test an alarm once a month, or notifications of hardware faults. If you want to go even further, your smoke alarm could trigger emergency lighting, your CO detector could shut off your gas fireplace, or your leak sensor could close water valves, all without sending your private data through a third-party server. And this is just the sort of complete, interoperable ecosystem Heiman aims to provide.

Working with the community

Heiman is showing they’re true to these ambitions. Beyond getting certified, they’re planning to take an active role in the Home Assistant community by participating in discussions, listening to real-world feedback, and continuously optimizing their products based on what users actually need. They’re also sharing their technical expertise in smart home security, collaborating with developers to explore innovative safety scenarios that benefit everyone.

Devices

Heiman’s commitment to openness and community is also reflected in the devices we’ve certified, which also meet strict safety regulations across the US, Europe, Asia and beyond. Before Heiman joined, we had one Zigbee smoke alarm in the program. Now there are Matter options for multiple regions, plus the first certified carbon monoxide alarms: more choice, more coverage.

What devices have been certified?

• Heiman Smart Smoke Alarm (USA)
• Heiman Smart Smoke Alarm (EU and China)
• Heiman Smart Carbon Monoxide Alarm (USA)
• Heiman Smart Carbon Monoxide Alarm (EU and China)
• Heiman Motion Sensor
• Heiman Water Leak Sensor
• Heiman Humidity and Temperature Sensor

Also worth noting: Heiman’s global presence allows them to deliver quality devices at prices that won’t break the bank. Safety sensors and alarms shouldn’t be a luxury, and Heiman’s approach means they don’t have to be.

No more guessing games!

Accessible pricing is just one way Heiman expands choice for users. We’ve found they also deliver on the other core principles behind the Works with Home Assistant program: local control protects privacy, and open standards ensure sustainability. And that’s the whole point of our certification process: to make it easier for you to spot manufacturers who genuinely commit to these values, taking the guesswork out of building your open home. For full details of all Works with Home Assistant partners, check out our certified device list.

Welcome to the program, Heiman, we’re excited to see what the community builds with these devices!

Frequently asked questions

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

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 in the future.

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

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 brands must continue to support the devices in the program.

How were these devices tested?

All devices in this list were tested using a standard Home Assistant Green Hub with the Home Assistant Connect ZBT-2 as the Thread Border Router and with our certified Matter integration.

Will you be adding more Heiman devices to the program?

Why not! We’re thrilled to foster a close relationship with the team at Heiman to work together on any upcoming releases or add in further products that are not yet listed here. We are also chatting with them about some exciting future plans.

Yes, the day has finally arrived: the Open Home Foundation merch store is up and running! 🥳 While some of you have tracked it down already (and are wearing the T-shirts to prove it!), we wanted to share it officially with the whole community so no one misses the chance to get involved.

Show your support

In case you didn’t know, there are already several ways to support our fight for the principles of privacy, choice, and sustainability for smart homes: you can subscribe to Home Assistant Cloud, buy official hardware from our commercial partners, or contribute to an open source project.

The merch store adds another choice to the mix that’s fun and easy to access. Whether you’ve been with us from the beginning, or have only recently discovered our mission and like what we stand for, the merch store is open to everyone!

Taking care of quality

We have offered merch before through on-demand services, but those platforms didn’t give us the control we wanted. Now we have our own store, we can select every item ourselves, check the quality (we’ve particularly enjoyed getting cozy in the hoodies this winter), and work with ethical manufacturers who share our commitment to sustainability.

And here’s the important part: after covering costs like production and fulfillment, your purchase contributes directly to our mission. You can see the breakdown of where your money goes on every product page.

What’s in store?

We’re starting with the essentials: hoodies, tees, polos, and accessories in a range of classic styles, colors, and designs – with exciting plans to expand both our products and categories over time. But for now there should be something for everyone: from understated logos to bold patterns that declare your advocacy loud and clear. One of our favorites is the “Open Homes” tee, where our in-house designer has captured our community’s strength – one foundation, many homes.

Over to you!

We’ve put a lot of thought and care into creating this first collection, and we can’t wait for you to check it out! You can browse our European or North American store depending on where you’re based: both have the full selection of swag, with local shipping for speed and convenience (and a lower carbon impact).

And remember… this is just the beginning. We already have lots of ideas for what’s next. But we want to hear from you too: what designs would you wear? What products or materials are you missing? Let us know and help us build a store the community really loves – in the open, of course.

Home Assistant 2026.2! 💝

February is the month of love, and this release is here to share it!

The new Home Dashboard is now the official default for all new installations. If you’ve been using Home Assistant for a while and never customized your default view, you’ll get a suggestion to switch; give it a try!

I also need your help! The Open Home Foundation device database is being built as a community-powered resource to help everyone make informed decisions about smart home devices. Head to Home Assistant Labs to opt in and contribute your anonymized device data. 📈

Add-ons are now called Apps! After a lot of community discussion, it was time to use terminology that everyone understands. Your TV has apps, your phone has apps, and now Home Assistant has apps too.

My personal favorite this release? The completely redesigned Quick search! If you’re like me and navigate Home Assistant using your keyboard, you’re going to love this one. Press ⌘ + K (or Ctrl + K on Windows/Linux) and you have instant access to everything. 🤩

Enjoy the release!

../Frenck

• A new way to view your home
  • Discovered devices at a glance
  • Area assignments made easy
  • Faster area edits
  • UX and visual upgrades
• Device database: We need your help!
  • Help us out and share your devices
  • See the data in action
  • Join us in building something meaningful
• Add-ons are now called Apps
  • A faster, snappier Apps panel
• Purpose-specific triggers and conditions progress
  • New triggers
  • New conditions
• A brand new card: The distribution card
• Quick search: The fastest way to anything
  • Your favorite shortcuts still work
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
• Other noteworthy changes
  • Add buttons to your heading card
  • Pick specific entities in your area card
• Patch releases
  • 2026.2.1 - February 6
  • 2026.2.2 - February 13
  • 2026.2.3 - February 20
• 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 @laupalombi and @mkerstner who helped write the release notes this release. Also, @wollew, @Diegorro98, and @MindFreeze for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️

A new way to view your home

The Home Dashboard is now Overview as it becomes the official default standard, replacing the old “Overview” for all new instances. If you’re a long-time user who never customized your default view, we’ll suggest the switch to you; otherwise, you can find it in Settings > Dashboards to try it out whenever you’re ready.

Liked the old Overview as a way to build your custom dashboards? You can still do it. Go to Settings > Dashboards, select Create, and pick the Overview (legacy) template.

Discovered devices at a glance

Check out the new card in the For You section! It instantly displays any new devices your Home Assistant has discovered, allowing you to add them on the spot or jump straight to device management without digging through menus.

Area assignments made easy

In the last release, we added a dedicated Devices area within the Home Dashboard to catch everything currently unassigned. Now this section provides quick prompts to help you categorize your devices into the right rooms, keeping your setup organized with minimal effort.

Faster area edits

Need to swap the area temperature sensor? Area pages now feature a shortcut in the Edit button. This lets you jump straight to the area’s configuration to update primary sensors like humidity or temperature in seconds.

We’ve also tidied up the interface by removing awkward empty spaces and fixing issues with some back arrows. Navigating through your sub-menus should now feel as smooth and predictable as you’d expect.

UX and visual upgrades

Modern look in the default theme: We’ve retired the old blue top bar in favor of a clean, consistent theme that matches our Settings page. This distraction-free design lets your cards and data take center stage.

Personalized themes per user: Themes have moved! You can now find and toggle your favorite looks directly within your User profile, making it easier to set up a theme that works for you in any device you are logged in.

Device database: We need your help!

Finding reliable information about smart home devices before you buy them can be challenging. That’s why we’re building the Open Home Foundation device database: a community-powered resource that helps you make informed decisions based on real-world data.

We’ve been working with early contributors to lay the groundwork, and the results are already impressive: over 10,000 unique devices across more than 260 integrations have been submitted by Home Assistant users who opted in to share their anonymized data.

Help us out and share your devices

Since we’re still in the early stages, the device database lives in Home Assistant Labs, where you can opt in to share anonymized information about the devices in your home.

We have also added a new section called Device analytics to Home Assistant Analytics, which shows up when you enable it in Home Assistant Labs. If you opt in, you are, of course, able to opt out at any time.

Privacy is our foundation. We collect zero personal data, period. Only aggregated, anonymized device information is shared if someone chooses to opt in, providing valuable insights while keeping your privacy intact. You can preview what is being sent using the Preview device analytics option available in the top-right corner on the Analytics page. Read our Data Use Statement for complete details.

See the data in action

We’ve launched an initial public dashboard where you can explore aggregated statistics as it grows. This is just our first step. We want to build what comes next together with you.

Join us in building something meaningful

Head to Settings > System > Labs to enable device analytics and start contributing your real-world anonymized device data to help others make better choices.

Read our blog post for more details and join the conversation in our Discord project channel; we’d love to hear your ideas, feedback, and questions as we shape this resource together.

Add-ons are now called Apps

Starting with this release, add-ons are now called apps! 🎉

You might be wondering: why change the name? The answer comes down to making Home Assistant more approachable for everyone, especially newcomers.

When you first open Home Assistant, you see two sections that sound very similar: “Add-ons” and “Integrations.” Both names imply something you add to extend Home Assistant, but they serve fundamentally different purposes. For those of us who’ve been in the ecosystem for a while, this distinction is second nature. But we keep seeing new users getting confused, attempting to install add-ons when they need integrations, or vice versa.

This is where the rename helps: use terminology that people already understand. Most people know what an “app” is. You open your phone’s app store, you pick an app, you install it. Your TV has an app store. Your NAS has apps. Heck, even some fridges have apps these days. It’s a concept everyone understands. The same mental model now applies to Home Assistant:

• Apps are standalone applications that run alongside Home Assistant.
• Integrations are connections that connect Home Assistant to your devices and services.

Apps are separate software managed by your Home Assistant Operating System, running next to Home Assistant itself. They can be things like code editors, media servers, MQTT brokers, or database tools. Some apps even pair with integrations: for example, the Mosquitto MQTT broker app provides the service, while the MQTT integration connects Home Assistant to it.

Existing documentation, community posts, and tutorials will continue to reference “add-ons” for some time. Search engines and AI assistants will also need time to catch up. We’ve put redirects in place to ensure that searching for “add-ons” will still get you where you need to go.

Thank you to everyone who participated in the community discussion and architecture proposal. Whether you supported the idea, pushed back, or landed somewhere in between, your feedback was invaluable.

A faster, snappier Apps panel

Besides the rename, we did a major refactoring under the hood of the Apps panel (formerly known as the Add-ons panel) in this release. Previously, this panel was served by a separate process (the Supervisor), but it has now been fully integrated into the Home Assistant frontend.

You shouldn’t notice much of a difference visually, but the panel is now much faster and snappier to use. More importantly, this change makes future development on Apps significantly easier, paving the way for more improvements down the road.

Purpose-specific triggers and conditions progress

In Home Assistant 2025.12, we introduced purpose-specific triggers and conditions. Instead of thinking in technical state changes, you can simply pick things like “When a light turns on” or “If the climate is heating” when building your automations. In Home Assistant 2026.1, we added more triggers and laid the groundwork for conditions.

This feature is still being refined in Home Assistant Labs, but we continue to expand it with every release. This release brings a mix of new triggers and, for the first time, a whole set of purpose-specific conditions!

New triggers

The following new triggers have been added in this release:

• Calendar triggers fire when a calendar event starts or ends.
• Person triggers now cover when a person arrives home or leaves home.
• Vacuum triggers fire when a vacuum cleaner returns to its dock.

New conditions

Purpose-specific conditions are expanding! In the previous release, we introduced the first purpose-specific condition for lights. This release adds a whole set of new conditions across many more entity types.

Just like triggers, conditions now allow you to express your intent in a more natural way. Instead of checking if the state of an entity equals a specific value, you can now simply ask “If the climate is heating” or “If the lock is locked”.

The following purpose-specific conditions are now available:

• Alarm control panel conditions check if the alarm is armed (home, away, night, or vacation), disarmed, or triggered.
• Assist satellite conditions check if your voice assistant satellites are idle, listening, processing, or responding.
• Climate conditions check if the climate device is on, off, heating, cooling, or drying.
• Device tracker conditions check if a device is home or not home.
• Fan conditions check if a fan is on or off.
• Humidifier conditions check if a humidifier is on, off, humidifying, or drying.
• Lawn mower conditions check if your lawn mower is mowing, docked, paused, returning, or encountering an error.
• Lock conditions check if a lock is locked, unlocked, open, or jammed.
• Media player conditions check if a media player is on, off, playing, paused, or not playing.
• Person conditions check if a person is home or not home.
• Siren conditions check if a siren is on or off.
• Switch conditions check if a switch is on or off.
• Vacuum conditions check if a vacuum is cleaning, docked, paused, returning, or encountering an error.

Head over to Settings > System > Labs to enable purpose-specific triggers and conditions and give them a try!

A brand new card: The distribution card

Meet the distribution card, a brand new dashboard card that visualizes how values are distributed across multiple entities. It displays your data as a proportional horizontal bar chart with an interactive legend, perfect for seeing at a glance where your power, storage, or any other measurable quantity is going.

The card is fully interactive: select legend items to hide or show entities (the percentages recalculate dynamically), and select bar segments to open the more-info dialog for that entity. When you have many entities, the legend shows the first items with a More button to expand the rest.

The distribution card is smart about what you can combine. It validates that all entities share the same domain and device class, so you won’t accidentally mix power sensors with battery sensors. It even handles related units gracefully: mixing watts and kilowatts works just fine.

Some ideas for how you might use it:

• Power monitoring: See which circuits or appliances are consuming the most electricity right now.
• Storage usage: Visualize how storage is distributed across drives or folders.
• Any proportional data: Compare any group of entities with the same unit.

Thanks to @jlpouffier for building this card! 🎉

Quick search: The fastest way to anything

We continue to make it easier to access and find things in Home Assistant. The quick bar has been completely redesigned and is now simply called Quick search. Think of it as the command center for your entire Home Assistant: navigate anywhere, run commands, find entities, devices, or areas, all from a single, unified search.

Open Quick search from anywhere by pressing ⌘ + K on macOS or Ctrl + K on Windows and Linux. The new design features category filters at the top: Navigate, Commands, Entities, Devices, and Areas. Select a filter to instantly narrow your results, or just start typing to search across everything.

Full keyboard navigation makes Quick search a power user’s friend. Use the arrow keys to move through results, Enter to select, and Esc to close. On mobile, you can assign Quick search to a gesture for one-tap access.

Your favorite shortcuts still work

If you’ve been using the single-key shortcuts from the old quick bar, they still work! The difference is that they now open Quick search with the corresponding filter already selected:

• e opens Quick search with the Entities filter
• d opens Quick search with the Devices filter
• c opens Quick search with the Commands filter
• a still opens Assist directly
• m still creates a My link for the current page (unrelated but still useful mention! 😉)

This means your muscle memory is preserved while you get access to all the new capabilities.

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:

• Cloudflare R2, added by @corrreia
  Back up your Home Assistant to Cloudflare R2. R2 offers generous free tier storage with no egress fees, making it an affordable option for keeping your backups safe in the cloud.

• Green Planet Energy, added by @petschni
  Get real-time dynamic electricity pricing data from German renewable energy provider Green Planet Energy. Monitor hourly prices and optimize your energy consumption by shifting it to cheaper hours.

• HDFury, added by @glenndehaan
  Control and monitor your HDFury HDMI video processing devices, like the VRROOM and Diva. Manage HDMI port selection, operation modes, audio muting, and monitor input/output signal status.

• NRGkick, added by @andijakl
  Monitor your NRGkick Gen2 mobile EV charger locally. Track charging status, energy consumption, power flow across all phases, and device temperatures without requiring a cloud connection.

• Prana, added by @prana-dev-official
  Integrate your Prana heat recovery ventilation systems. Prana HRV units provide balanced mechanical ventilation with energy-efficient heat exchange, and you can now control and monitor them directly from Home Assistant.

• uHoo, added by @getuhoo and @joshsmonta
  Integrate your uHoo indoor air quality monitors to track temperature, humidity, CO2, PM2.5, and other air quality metrics. Also includes proprietary health indices for virus and mold risk.

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 ones are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• ESPHome integration now supports water heater devices! Thanks, @dhoeben, for adding this!
• Music Assistant integration now supports pre-announce URLs, thanks to @arturpragacz. Use your custom announcement sounds before your text-to-speech message plays!
• @fr33mang made it possible to play your “Liked Songs” collection directly in the Spotify integration. No more searching for that special playlist. 😁
• The Sonos integration now shows your podcast favorites in the media browser, thanks to @divers33. May we recommend the Home Assistant Podcast? 🎤
• @starkillerOG added a new pet chime option to the Reolink integration. Now you can trigger a special chime when your furry friends are at the door! 🐶
• The SmartThings integration now supports audio notifications, thanks to @vmonkey.
• @Lash-L improved the Roborock integration by adding sensors for the dock water box status. Nice!
• The Tibber integration received several enhancements from @Danielhiversen: new binary sensors for EV charger status, additional temperature and grid sensors, and more EV settings to fine-tune your charging experience. ⚡️
• @LG-ThinQ-Integration added support for controlling humidifiers and dehumidifiers in the LG ThinQ integration. Thanks!
• Thanks to @ptarjan, the Hikvision integration now has camera support! You can view snapshots and streams from your Hikvision cameras and NVRs directly in Home Assistant.
• @cdnninja added PM1 and PM10 air quality sensors to the VeSync integration. Nice!
• The Bang & Olufsen integration received battery support from @mj23000. You can now monitor battery levels and charging status for your portable Beosound speakers and Beoremote One remotes.
• @erwindouna enhanced the Portainer integration with a new prune images button and a state sensor. Awesome!
• Thanks to @klaasnicolaas, the Powerfox integration now supports gas meters alongside electricity meters.
• @terop added an Indoor Air Quality Score (IAQS) sensor to the Ruuvi integration. Great!
• @pandanz added an ambient temperature sensor to the ToGrill integration. Keep an eye on the temperature around your grill 🍗, not just inside it!
• @tr4nt0r added support for sequence IDs to the ntfy integration, allowing notifications to be updated, and added two new actions to dismiss and delete notifications.

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 🏆

  • Airobot, thanks to @mettolen
  • Duck DNS, thanks to @tr4nt0r
  • Saunum, thanks to @mettolen

• 4 integrations reached silver 🥈

  • Feedreader, thanks to @mib1185
  • NINA, thanks to @DeerMaximum
  • Velbus, thanks to @cereal2nd
  • Velux, thanks to @wollew

• 1 integration reached bronze 🥉

  • TP-Link Omada, thanks to @MarkGodwin

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:

• Namecheap DynamicDNS, done by @tr4nt0r
• OpenEVSE, done by @c00w
• Proxmox VE, done by @erwindouna
• WaterFurnace, done by @masterkoppa

Other noteworthy changes

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

• The Developer tools have been moved to the Settings area. This change keeps all administrative and system tools in one central location, making the interface cleaner and more consistent. We understand this might take some getting used to, and we hear you! We’re actively exploring adding full sidebar menu customization capabilities in the future, giving you the flexibility to organize your navigation exactly the way you want it.
• Dashboards now support calendar colors! Pick a color for each calendar, and it will show up in your calendar cards. The Google Calendar integration already supports this feature, thanks to @Misiu.
• @karwosts added live inline template previews to the template editor. As you type, you can instantly see the result of your template without needing to manually refresh.
• The sidebar now features a subtle scroll fade effect and keeps Settings always visible at the bottom, so you never have to scroll to find it. Thanks, @ildar170975!
• @MindFreeze added tap action and image tap action options to the area card, giving you more control over what happens when you interact with your areas.
• The entity card now supports actions, thanks to @ildar170975. Configure tap, hold, or double-tap actions to trigger anything you want directly from the card.
• @Thomas55555 added parts per billion (ppb) as a valid unit of measurement for sulfur dioxide sensors and number entities.
• The Energy dashboard now supports power sensors in other formats without the need for a template sensor thanks to @MindFreeze. You can now use a single sensor with an inverted polarity for grid or battery. You can also configure two separte positive sensors for charge and discharge (or import/export).

Add buttons to your heading card

The heading card now supports button badges, giving you a new way to add quick actions right alongside your section headings. Display an icon, text, or both, pick a custom color, and configure tap, hold, or double-tap actions to trigger anything you want.

You can also set visibility conditions to show or hide buttons based on entity states. Combined with the existing entity badges, this makes the heading card a versatile anchor for your dashboard sections, whether you want to display status information, provide quick controls, or both.

Thanks to @piitaya for this addition! 🎉

Pick specific entities in your area card

The area card now lets you select individual entities as control buttons, not just entire types of entities like all lights or all switches in the area. Previously, adding a light control meant showing all lights in the area. Now you can pick exactly which entities appear.

Great job, @MindFreeze! 🎉

Patch releases

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

2026.2.1 - February 6

• Fix redundant off preset in Tuya climate (@epenet - #161040)
• Fix device_class of backup reserve sensor (@jonootto - #161178)
• Bump evohome-async to 1.1.3 (@zxdavb - #162232)
• Bump google_air_quality_api to 3.0.1 (@Thomas55555 - #162233)
• Bump denonavr to 1.3.2 (@ol-iver - #162271)
• Fix multipart upload to use consistent part sizes for R2/S3 (@corrreia - #162278)
• Add mapping for stopped state to denonavr media player (@ol-iver - #162283)
• Fix unicode escaping in MCP server tool response (@luochen1990 - #162319)
• Bump pyenphase to 2.4.5 (@catsmanac - #162324)
• Fix Shelly Linkedgo Thermostat status update (@thecode - #162339)
• Update pynintendoparental requirement to version 2.3.2.1 (@pantherale0 - #162362)
• Fix conversion of data for todo.* actions (@boralyl - #162366)
• Bump python-smarttub to 0.0.47 (@mdz - #162367)
• Add missing config flow strings to SmartTub (@mdz - #162375)
• Remove entity id overwrite for ambient station (@joostlek - #162403)
• Bump librehardwaremonitor-api to version 1.9.1 (@Sab44 - #162409)
• Remove double unit of measurement for yardian (@joostlek - #162412)
• Fix invalid yardian snapshots (@epenet - #162422)
• Make bad entity ID detection more lenient (@arturpragacz - #162425)
• Bump aioamazondevices to 11.1.3 (@jamesonuk - #162437)

2026.2.2 - February 13

• Bump essent-dynamic-pricing to 0.3.1 (@jaapp - #160958)
• Fix AsyncIteratorReader blocking after stream exhaustion (@ElCruncharino - #161731)
• Fix absolute humidity sensor on HmIP-WGT glass thermostats (@lackas - #162455)
• Fix device_class of backup reserve sensor in teslemetry (@Bre77 - #162458)
• Fix device_class of backup reserve sensor in Tessie (@Bre77 - #162459)
• Fix JSON serialization of time objects in OpenAI tool results (@Shulyaka - #162490)
• Fix JSON serialization of datetime objects in Google Generative AI tool results (@Shulyaka - #162495)
• Fix JSON serialization of time objects in Ollama tool results (@Shulyaka - #162502)
• Fix JSON serialization of time objects in Open Router tool results (@Shulyaka - #162505)
• Fix JSON serialization of time objects in Cloud conversation tool results (@Shulyaka - #162506)
• Fix Green Planet Energy price unit conversion (@petschni - #162511)
• Bump grpc to 1.78.0 (@allenporter - #162520)
• Fix Tesla Fleet partner registration to use all regions (@Bre77 - #162525)
• Sentence-case “speech-to-text” in google_cloud (@NoRi2909 - #162534)
• Add new Miele mappings (@aturri - #162544)
• Fix config flow bug for Telegram bot (@hanwg - #162555)
• Add timeout to B2 metadata downloads to prevent backup hang (@ElCruncharino - #162562)
• migrate velbus config entries (@cereal2nd - #162565)
• Bump aioimmich to 0.12.0 (@mib1185 - #162573)
• Bump aioautomower to 2.7.3 (@Thomas55555 - #162583)
• Increase max tasks retrieved per page to prevent timeout (@boralyl - #162587)
• Pin setuptools to 81.0.0 (@joostlek - #162589)
• Improve MCP SSE fallback error handling (@allenporter - #162655)
• Bump intellifire4py to 4.3.1 (@jeeftor - #162659)
• Bump reolink-aio to 0.19.0 (@starkillerOG - #162672)
• Fix handling when FRITZ!Box reboots in FRITZ!Smarthome (@mib1185 - #162676)
• fix to cloudflare r2 setup screen info (@corrreia - #162677)
• Fix handling when FRITZ!Box reboots in FRITZ!Box Tools (@mib1185 - #162679)
• Bump onedrive-personal-sdk to 0.1.2 (@zweckj - #162689)
• Fix unavailable status in Tuya (@epenet - #162709)
• Fix alarm refresh warning for Comelit SimpleHome (@chemelli74 - #162710)
• Fix image platform state for Vodafone Station (@chemelli74 - #162747)
• Fix bug in edit_message_media action for Telegram bot (@hanwg - #162762)
• Bump cryptography to 46.0.5 (@edenhaus - #162783)
• Bump pySmartThings to 3.5.2 (@joostlek - #162809)
• Filter out transient zero values from qBittorrent alltime stats (@Xitee1 - #162821)
• Bump slixmpp to 1.13.2 (@Lyokovic - #162837)
• Bump pydaikin to 2.17.2 (@YoshiWalsh - #162846)
• Bump pytouchlinesl to 0.6.0 (@jnsgruk - #162856)
• Add Miele TQ1000WP tumble dryer programs and program phases (@andrei-marinache - #162871)
• Bump ZHA to 0.0.90 (@puddly - #162894)
• Log remaining token duration in onedrive (@zweckj - #162933)

2026.2.3 - February 20

• Add the ability to select region for Roborock (@Lash-L - #160898)
• Fix dynamic entity creation in eheimdigital (@autinerd - #161155)
• Fix HomematicIP entity recovery after access point cloud reconnect (@lackas - #162575)
• Show progress indicator during backup stage of Core/App update (@hbludworth - #162683)
• Fix Z-Wave climate set preset (@MartinHjelmare - #162728)
• Block redirect to localhost (@edenhaus - #162941)
• Bump pypck to 0.9.10 (@alengwenus - #162333)
• Bump pypck to 0.9.11 (@alengwenus - #163043)
• Fix blocking call in Xbox config flow (@tr4nt0r - #163122)
• Bump ical to 13.2.0 (@allenporter - #163123)
• Add Lux to homee units (@Taraman17 - #163180)
• Fix remote calendar event handling of events within the same update period (@allenporter - #163186)
• Fix Control4 HVAC action mapping for multi-stage and idle states (@davidrecordon - #163222)
• NRGkick: do not update vehicle connected timestamp when vehicle is not connected (@andijakl - #163292)
• Add Miele dishwasher program code (@astrandb - #163308)
• Bump pyrainbird to 6.0.5 (@allenporter - #163333)
• Fix touchline_sl zone availability when alarm state is set (@molsmadsen - #163338)
• Bump pySmartThings to 3.5.3 (@joostlek - #163375)
• Fix hassfest requirements check (@cdce8p - #163681)
• Bump eheimdigital to 1.6.0 (@autinerd - #161961)

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:

• Replacing pre-commit with prek
• Solving pyserial-asyncio blocking the event loop

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 2026.2.

Imagine knowing how a smart device will actually perform in your home before you buy it… not from a spec sheet, but from anonymized data that people running setups just like yours have opted to share. Having answers to questions like: will this sensor work without the cloud? Is that smart plug actually being reported by users as reliable? Does “local control” mean local always, or just sometimes? Will these devices work well across protocols? What this device looks like in other users’ homes?

That’s the idea behind the Open Home Foundation Device Database: a community-powered resource built from anonymized data shared voluntarily by Home Assistant users around the world. The aim: to give people the information they need to benefit from privacy, choice, and sustainability in their smart homes.

Having easy access to this wealth of data changes everything. With the device database at your fingertips, you’ll know upfront that there are 1000+ Home Assistant users running that smart plug fully locally, and it includes those voltage and wattage sensors you were looking for. Or if you see a sensor everyone’s raving about requires Bluetooth when your protocol of choice is Zigbee, the database could save you the hassle of buying it in the first place.

Of course, there are some excellent device databases and compatibility lists already available. Our own Works with Home Assistant (WWHA) program puts products through their paces in home settings, which has taught us how vital real-world testing is. But to really understand how devices perform across the incredibly diverse range of setups out there (different integrations, hardware combinations, network connections, and protocols) we need data at a much larger scale. That’s what makes the device database different: it’s thousands of real homes opting in to contribute real anonymized data. And that’s only possible with your help.

Building together

Creating the device database is a big job, and we’re going to need your help to do it. Before we build a shiny new website or complex search engine, the first step is to make sure the data you opt to share with us is accurate, anonymized, and meaningful, so we’re prioritizing:

• Privacy first: The information we collect strictly follows our privacy principles: we don’t collect any personal data, period. Instead, we only share aggregated versions of device data, ensuring our community gets the insights they need without compromising anyone’s privacy. Check out our Data Use Statement for details.
• Real-world context: Our device database is centered around anonymized device data from Home Assistant instances of users who choose to participate through this new Labs feature.
• Laying the groundwork: To prepare the first stage of this initiative, we invited members of the Open Home Foundation, our commercial partners, and a range of Home Assistant users, to opt into sharing their device data with us. This collaborative start has helped us aggregate more than 2,000 unique devices across more than 160 integrations, with lots more to come.
• Transparency: We’ve launched an initial public dashboard for aggregated statistics and data downloads, giving you a first look at the insights as they grow. Of course, we won’t stop there, as we’re approaching this step-by-step…

Nothing happens overnight

Like everything we do, the Device database initiative follows a steady, iterative approach, which takes time. We want to be honest: nothing happens overnight. We don’t believe in hiding away for years behind closed doors just to launch our vision of a “perfect” finished product (spoiler: there’s no such thing as perfect!). Instead, in the true open source fashion, we build in the open, release early experiments, and refine them based on how our community actually uses them.

Right now, in these early stages, our focus is on planting the seeds and gathering the first shoots of real-world information, as well as your feedback. This way, the tools we build later can grow and evolve alongside your needs.

The next steps

Following our iterative philosophy, we have a roadmap of small, manageable milestones designed to gather feedback at every step:

1. Launching in Home Assistant Labs

We are introducing the Open Home Foundation device database as a Labs feature in the 2026.2 release of Home Assistant. The idea is to broaden visibility and reach a wider audience (hello, that means you 👋) willing to contribute by opting in to share their device data and providing valuable feedback.

2. Putting the data in your hands

Building on the further insights and feedback we gather, we’re planning to launch the first public device database web interface in the first half of 2026. The plan is to make it easier for you to explore and interact with the information, beyond simple statistical dashboards.

While this initial version will be far from the final version (if there ever is one!). By getting it into your hands as early as possible, we can better understand where to go next, and make sure our future work is focused on the most valuable features for you.

3. Encouraging community contributions

Right from the start, we’re establishing simple flows to enable you to contribute more easily, allowing you to enrich the device database by adding real-world insights, all under the watch of our community. The result: an authentic and unbiased source of truth that helps everyone make informed decisions when it comes to privacy, choice, and sustainability in the smart home.

Now it’s over to you!

Because this project belongs to the community, we need your perspective early and often to help shape what comes next.

This is a marathon, not a sprint. The device database will only become a definitive resource through consistent, collective effort over the coming months and years, but bit by bit, device by device, we can make something great together! Here’s how you can be part of it:

• Enable Device Analytics: If you use Home Assistant, opting into Device Analytics in the Labs menu is the direct way to contribute to the device database.
• Provide feedback: We’ve created a simple survey form so you can let us know what you think of the initiative, and why you’d like to contribute (or not!).
• Join the discussion: We also have a dedicated Discord channel and want to hear what matters most to you: how can we make the device database a flourishing resource the community can trust for years to come?

Together we’ll build a transparent, open, and community-driven map of the real-world smart home ecosystem: one that gets better with every contribution. We hope you’ll be part of it.

It’s time to celebrate what we’ve built together, and get excited about what’s coming next – at State of the Open Home, our annual look at how we’re championing privacy, choice, and sustainability in the smart home. And this year, we’re doing something new: inviting you to be part of the action in our audience! 🎉

That’s right, you don’t have to watch from home – you can join us live in Utrecht, the Netherlands, on Wednesday, April 8.

This year’s theme: Building in the open

Building in the open has always been at the heart of what the Open Home Foundation does, across Home Assistant and other projects. This year, we’re taking it to the next level – shining a spotlight on the transparency and collaboration that sets this community apart.

We’re talking open roadmaps, honest conversations about the way we work and the challenges we face, and how we solve them together. Plus, we’ll be showcasing what our community achieved in 2025, giving you a look at what’s ahead – and asking you to help shape it.

What to expect

We’re putting the final touches on the program (watch this space!) – but here’s a taste of what’s in store:

• Celebrate all we’ve achieved together in 2025
• See what’s ahead for Home Assistant and the wider ecosystem
• Connect with fellow Open Home advocates and contributors in person
• Have your say in the discussions guiding the future of the Open Home

And that’s just the start. Expect special guests, a few surprises, and the kind of positive energy you only get when this community gathers in one room ⚡.

Tickets available soon!

Limited spots will be available for our live audience in Utrecht, the Netherlands. Tickets will be available from early February – and they’ll go fast, so stay tuned for details! We’ll also be livestreaming globally for those who can’t make it in person.

Visit our new State of the Open Home website to learn more, and be sure to follow us on Fosstodon, Bluesky, Instagram or Facebook so you don’t miss the ticket drop!

📅 Mark your calendars now: Wednesday, April 8, Utrecht, the Netherlands.

Last month – and indeed last year! – we published a blog recapping the highlights from the Works with Home Assistant program in 2025. As with any certification program, our partnerships evolve: some start anew, some grow bigger and stronger, and some naturally run their course. In the interest of visibility for our community, we want to share an update about one such change. When a partner leaves the program, we believe it’s important to document this openly so you get the full picture.

Why we’re making a change

Despite reaching out to HELTUN multiple times during 2025 to discuss renewing their Works with Home Assistant contract with the Open Home Foundation, we haven’t been able to connect. As their previous contract has now lapsed, we’re formally removing HELTUN from the Works with Home Assistant program.

We have no specific issues with the HELTUN devices, and hope they will continue to be compatible with Home Assistant – as Z-Wave devices operate on an open standard, they should continue to function. However, without a contract, HELTUN has no formal obligation to provide ongoing support, such as firmware updates via Z-Wave JS.

This is an example of why the contract is more than just paperwork. It’s intrinsic to the badging as it outlines, in a legal and binding document, our partners’ commitment to the community, keeping devices working long-term, and the values we all care about. Without it, we can’t maintain certification.

What happens now

HELTUN’s integration page will now be removed from the partner filter, and an update has been published on our original HELTUN launch blog stating that the information is no longer applicable. They are now also prohibited from using the Works with badge on relevant marketing materials.

As we have no problems with the devices themselves, we will be happy to welcome HELTUN back into the program should they wish to re-engage in the future.

Looking ahead

In more positive news, don’t forget we’ve introduced an up-to-date list of all certified devices from our current Works with partners to help guide your purchasing decisions – and watch this space for details of more brands joining us in 2026!

Happy New Year! 🥂

I hope you had a wonderful holiday, spending time with your loved ones. We’re kicking off 2026 with a smaller release, as our contributors and maintainers have been enjoying some well-deserved time off as well. But don’t worry, there’s still plenty of good stuff in this release!

Home Assistant 2026.1 brings a refreshed Home dashboard experience on mobile, with summary cards right at your fingertips without extra taps. We’ve also made it easier than ever to navigate to the protocol connecting your devices, such as Zigbee, Z-Wave, Thread and more.

For automation enthusiasts, we’re continuing our work on our even more “human-friendly” triggers, which can be enabled via Home Assistant Labs, so you can build automations using easy-to-understand language instead of technical state changes, like initiating automations if a button is pressed or someone arrives home.

On the integrations front, we welcome eight new integrations to the family, including pet tracking with Fressnapf, energy monitoring with eGauge, and smart heating control with Watts Vision +. Plus, improvements to existing integrations from our amazing community contributors.

I wish you a happy and healthy 2026! Enjoy the release!

../Frenck

• Home dashboard improvements
  • Streamlined mobile navigation
  • New devices page
• Purpose-specific triggers and conditions progress
• Easier navigation to protocol dashboards
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
• Other noteworthy changes
  • Energy dashboard date picker
  • ESPHome action responses
• Patch releases
  • 2026.1.1 - January 12
  • 2026.1.2 - January 16
  • 2026.1.3 - January 23
• 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 @bramkragten, @piitaya, and @abmantis who helped write the release notes for this release. ❤️

Home dashboard improvements

The Home dashboard continues to evolve! In the previous release, we introduced a brand-new sidebar layout, weather tiles, and energy distribution summaries. This release takes it even further with a streamlined mobile experience and better device management.

Streamlined mobile navigation

On mobile devices, the Home dashboard now displays summary cards (like lights, climate, security, media players, weather, and energy) directly at the top of the view, followed by your favorites and areas. This replaces the previous tab-based navigation, giving you instant access to everything that matters without any extra taps.

The desktop experience remains unchanged, with summaries displayed in the sidebar under the For you heading.

New devices page

Ever wondered where your devices went after you removed them from an area? A new Devices page now appears on the Home dashboard, showing all devices that aren’t currently assigned to a specific area. This makes it easy to find and control those “orphaned” devices without hunting through the settings.

The new Devices page shows devices not assigned to any area.

Purpose-specific triggers and conditions progress

In the previous release, we introduced purpose-specific triggers and conditions. Instead of thinking in technical state changes, you can now simply pick things like “When a light turns on” or “If the climate is heating” when building your automations.

This feature is still being refined in Home Assistant Labs, but this release adds a lot more trigger types, making this new approach even more useful. Here is an overview of all the new triggers added in this release:

• Button triggers fire when a button entity has been pressed.
• Climate triggers now cover all common scenarios. You can trigger on HVAC mode changes, target temperature changes, or when the target temperature crosses a threshold. There are also triggers for current temperature and humidity changes, and even target humidity changes.
• Device tracker triggers let you automate based on when a device entered or left home, with support for the first device arriving, last device leaving, or any change. Don’t worry, person-specific triggers are coming soon, the device tracker ones were simply available sooner.
• Humidifier triggers will fire when a humidifier turns on or off, starts humidifying, or starts drying. You can also trigger on humidity changes or when humidity crosses a threshold.
• Light triggers let you automate based on brightness changes or when brightness crosses a specific threshold.
• Lock triggers can now fire when a lock is locked, unlocked, opened, or jammed.
• Scene triggers fire when a scene is activated.
• Siren triggers fire when sirens are turned on or off.
• Update trigger fires when an update becomes available.

As the new purpose-specific triggers and conditions all support targeting something bigger than a simple entity (an area, a floor, or even a label), we also redesigned how the target gets displayed on the automation flow.

The goal of this change is to allow you to quickly glance at your automation, and understand its purpose.

Head over to Settings > System > Labs to enable purpose-specific triggers and conditions and give them a try!

Easier navigation to protocol dashboards

For an organization that loves the open standards that seamlessly connect our devices, we sure didn’t promote them enough! Most people didn’t even know that Home Assistant has dedicated dashboards for protocols like Zigbee, Z-Wave, and more.

This release reorganizes the Settings page to give these open protocols a more prominent spot. The protocols section now appears right after the core settings, making it much easier to find all the different ways you’re connecting your devices and quickly access some very useful protocol-specific configurations.

The menu items only appear when you have the corresponding integration set up, so you’ll only see what’s relevant to your setup.

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:

• AirPatrol, added by @antondalgren
  Control your air conditioning units through AirPatrol Wi-Fi devices directly from Home Assistant.
• eGauge, added by @neggert
  Integrate eGauge energy monitors for residential and commercial applications, commonly used with solar energy installations.
• Fluss+, added by @Marcello17
  Connect your Fluss+ Button to Home Assistant for quick and easy control of your smart home.
• Fish Audio, added by @noambav
  Use Fish Audio’s text-to-speech service to generate natural-sounding speech in Home Assistant.
• Fressnapf Tracker, added by @eifinger
  Track the location of your pets and monitor their activity using Fressnapf GPS Trackers.
• HomeLink, added by @ryanjones-gentex
  Integrate your HomeLink devices to trigger smart home routines from the comfort of your vehicle.
• Watts Vision +, added by @theobld-ww
  Control your Watts Vision + smart heating system, allowing remote control of individual home heating zones.
• WebRTC, added by @balloob
  An internal integration providing WebRTC functionality for camera streaming in Home Assistant.

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:

• Levoit, provided by VeSync, added by @timmo001

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 ones are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• The Matter integration gained three new diagnostic binary sensors for thermostat remote sensing status from @lboue, helping you keep an eye on your climate system.
• @joostlek added lots of new sensors to the SmartThings integration, including air quality sensors for PM1, PM2.5, and PM10, hood filter usage tracking, fridge temperature sensors for One Door refrigerators, and fan speed control for range hoods.
• Roborock owners with Q7 devices can now integrate them thanks to @Lash-L, who added basic read-only support with sensors for battery, status, and cleaning data.
• @mib1185 improved the FRITZ!SmartHome integration by adding switch entities that let you enable or disable FRITZ! Smart Home routines (triggers) directly from Home Assistant.
• The Ping integration now tracks packet loss, thanks to @mib1185. The new sensor shows packet loss as a percentage and is disabled by default.
• @Shulyaka added support for GPT-5.2 and GPT-5.2-pro models to the OpenAI integration, including a new “xhigh” reasoning effort level.
• The HomeWizard integration gained two new battery charge modes from @DCSBL: zero charge only and zero discharge only, giving you more control over your energy storage.
• @Abestanis expanded the KNX UI configuration to support time, date, and datetime entities, while @farmio added sensor, scene, text, and fan entities, making it easier than ever to set up your KNX installation.
• The Squeezebox integration now offers alarm monitoring, thanks to @wollew: you get binary sensors to track if an alarm is upcoming, active, or snoozed, plus a timestamp sensor showing when the next alarm is scheduled.
• @andrew-codechimp added support for new meal plan types in Mealie 3.7, including dessert, drink, and snack plans, giving you more flexibility in your meal planning.
• The Hikvision integration gained NVR support from @ptarjan, including extended event detection and automatic discovery of video channels.
• @FredericMa added a set_time action to the Risco integration, allowing you to sync your local alarm panel’s clock and fix those pesky clock drift issues.
• The Nederlandse Spoorwegen integration got a major overhaul from @heindrichpaul, splitting the monolithic sensor into over 15 individual sensors, one for each train route, making it much easier to track specific journeys.
• @zweckj added a beautiful entity picture of your coffee machine to the La Marzocco integration’s main switch entity.
• The Actron Air integration gained a new switch platform from @kclif9, exposing Away Mode, Continuous Fan, Quiet Mode, and Turbo Mode controls.
• @Djelibeybi gave the Pooldose integration a massive upgrade: you now get water meter sensors for monitoring levels, number entities for configuring dosing targets, and select entities for controlling your pool’s operating mode.
• The AirPatrol integration now lets you monitor temperature and humidity, thanks to new sensor entities added by @antondalgren.
• @mettolen added sensor and number platforms to the Airobot integration, letting you monitor air quality data and control hysteresis band settings.

A huge thank you to all the contributors who improved these integrations, and to everyone else who contributed improvements that aren’t listed here. Your work makes Home Assistant better for everyone! ❤️

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 🏆

  • KNX, thanks to @farmio
  • UniFi Protect, thanks to @RaHehl

• 4 integrations reached silver 🥈

  • Autarco, thanks to @klaasnicolaas
  • SFR Box, thanks to @epenet
  • Squeezebox, thanks to @peteS-UK, @pssc and @rajlaud
  • Watergate, thanks to @adam-the-hero

• 2 integrations reached bronze 🥉

  • Growatt Server, thanks to @johanzander
  • TP-Link Omada, thanks to @MarkGodwin

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:

• Hikvision, done by @ptarjan
• VIVOTEK, done by @HarlemSquirrel

Other noteworthy changes

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

• If you monitor your home’s oil tank or other slow flow rates, you might appreciate the new gallons per day unit of volume flow rate added by @StaleLoafOfBread. This unit is particularly useful for tracking daily consumption rates of heating oil or similar resources.
• Got a Matter speaker? @lboue added volume control support to the Matter integration, exposing a volume slider entity for Matter speakers using the LevelControl cluster.
• The statistics graph card now includes a link to the history panel in its header, just like the history graph card already had. Selecting the link takes you directly to the history with the same entities and time range pre-selected, thanks to @joepio.
• When using the state badge element in your picture elements card, you can now set a custom name option, giving you more flexibility in your dashboard designs, thanks to @ildar170975.
• In 2025.11 we improved the logging efficiency by disabling the duplicated log file. This release adds a new configuration option to re-enable it if needed. If you are using the official Terminal & SSH add-on, make sure it is updated to 9.22.0 or higher to be able to use that option. The Advanced SSH & Web Terminal add-on has not been updated yet, but will be soon.
• For integration developers: @bramkragten added a new choose selector, allowing users to select between different input types in the UI. You’ll start seeing this pop up in various places where flexible input is needed.

Energy dashboard date picker

In the previous release, the Energy dashboard received a big update with real-time power monitoring and downstream water tracking. However, some of you noticed that navigating between periods required scrolling back up, making it harder to compare data while looking at graphs further down the page.

This release fixes that! The date picker is now sticky at the bottom of the screen, so you can easily switch between days, weeks, or months without losing sight of the graph you’re viewing. This also makes it much easier to access on mobile devices.

ESPHome action responses

ESPHome 2025.12 introduced a powerful new feature called API action responses, enabling true bidirectional communication between your ESPHome devices and Home Assistant. With this release, Home Assistant now fully supports receiving these responses!

Previously, when calling an action on an ESPHome device, communication was one-way: you could send a command, but the device couldn’t send structured data back. Now, your ESPHome devices can return JSON data in response to actions, unlocking new possibilities like querying device configuration, reading sensor values on demand, or retrieving diagnostic information.

This is particularly useful for actions that answer questions rather than perform tasks. For example, you could create an action that returns your device’s current Wi-Fi signal strength, firmware version, or any custom sensor readings, all as structured data you can use in your automations.

To get started, check out the ESPHome documentation on action responses for configuration examples.

Patch releases

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

2026.1.1 - January 12

• Fix Hikvision NVR binary sensors not being detected (@ptarjan - #160254)
• Bump eheimdigital to 1.5.0 (@autinerd - #160312)
• Bump ZHA to 0.0.84 (@TheJulianJES - #160440)
• Bump pyOverkiz to 1.19.4 (@iMicknl - #160457)
• Fix JSON serialization of time objects in anthropic tool results (@dcermak - #160459)
• Add asyncio-level timeout to Backblaze B2 uploads (@ElCruncharino - #160468)
• Fix Requirement parsing in RequirementsManager (@epenet - #160485)
• Add Nettleie optimization option (@osohotwateriot - #160494)
• Bump python-otbr-api to 2.7.1 (@emontnemery - #160496)
• fix rain sensor for some rare velux windows (@wollew - #160504)
• Fix trigger selectors (@bramkragten - #160519)
• Bump Intergas Incomfort-client to v0.6.11 (@jbouwh - #160520)
• Revert “Update voluptuous and voluptuous-openapi” (@synesthesiam - #160530)
• Bump serialx to v0.6.2 (@puddly - #160545)
• Catch any migration failures in Teslemetry (@Bre77 - #160549)
• Fix AttributeError for missing/incomplete health data in Tractive (@bieniu - #160553)
• Bump pysilero-vad to 3.1.0 (@synesthesiam - #160554)
• Fix for older Fritzbox models which do not support smarthome triggers (@mib1185 - #160555)
• Bump google-air-quality-api to 2.1.2 (@Thomas55555 - #160561)
• Fix Climate signal in Teslemetry (@Bre77 - #160571)
• Bump pysma to 1.1.0 (@kellerza - #160583)
• Bump opower to 0.16.1 (@tronikos - #160588)
• Fix config flow bug in Tesla Fleet (@Bre77 - #160591)
• Add missing segment speed icons for WLED (@Tommatheussen - #160597)
• Better handling of ratelimiting from Tibber (@Danielhiversen - #160599)
• Change device class to energy_storage for some enphase_envoy battery entities (@catsmanac - #160603)
• Fix Z-Wave creating notification binary sensor for idle state (@MartinHjelmare - #160604)
• Bump pynintendoparental to 2.3.2 (@pantherale0 - #160626)
• Update frontend to 20260107.1 (@bramkragten - #160644)
• Bump pyhik to 0.4.0 (@ptarjan - #160654)
• Bump greeclimate to 2.1.1 (@cmroche - #160683)
• Bump pysilero-vad to 3.2.0 (@synesthesiam - #160691)
• Revert bthome-ble back to 3.16.0 to fix missing data (@Ernst79 - #160694)
• Fix missing key for brew by weight in lamarzocco (@zweckj - #160722)
• Bump pytado 0.18.16 (@erwindouna - #160724)
• Bump python-homewizard-energy to 10.0.1 (@DCSBL - #160736)
• Fix fitbit icon (@joostlek - #160750)

2026.1.2 - January 16

• Fix Airzone Q-Adapt select entities (@Noltari - #160695)
• Revert back to microVAD (@synesthesiam - #160821)
• Bump opower to 0.16.2 (@tronikos - #160822)
• accept leading zeros in sms_code for fressnapf_tracker (@eifinger - #160834)
• Add support for packaging version >= 26 on the version bump script (@edenhaus - #160858)
• Update PyNaCl to 1.6.2 (@cdce8p - #160909)
• Bump pyenphase from 2.4.2 to 2.4.3 (@catsmanac - #160912)
• Decrease Essent update interval to 1 hour (@jaapp - #160959)
• Bump opower to 0.16.3 (@tronikos - #160961)
• Bump PySrDaliGateway from 0.18.0 to 0.19.3 (@niracler - #160972)
• Add descriptions to openai_conversation (@zweckj - #160979)
• Clean up unnecessary Z-Wave “device config changed” repairs (@AlCalzone - #161000)
• Update knx-frontend to 2026.1.15.112308 (@farmio - #161004)
• Require admin for blueprint ws commands (@edenhaus - #161008)
• Bump aiomealie to 1.2.0 (@andrew-codechimp - #161058)
• Update frontend to 20260107.2 (@bramkragten - #161061)
• Update aioairzone to v1.0.5 (@Noltari - #160688)

2026.1.3 - January 23

• Bump uiprotect to 8.1.1 (@RaHehl - #160816)
• Update list of supported locations for London Air (@allanlewis - #160884)
• Bump onedrive-personal-sdk to 0.1.0 (@zweckj - #160976)
• Adjust battery voltage sensor display precision for Matter devices (@lboue - #161088)
• Fix color temperature attributes in wiz (@arturpragacz - #161125)
• Bump xiaomi-ble to 1.4.3 (@terop - #161132)
• Bump opower to 0.16.4 (@tronikos - #161153)
• Fix detection of multiple smart object types in single event (@RaHehl - #161189)
• Fix icons for ‘moving’ state (@stickpin - #161194)
• Bump onedrive-personal-sdk to 0.1.1 (@zweckj - #161337)
• Bump uiprotect to 10.0.0 (@RaHehl - #161350)
• Migrate config entries to string unique id (@edenhaus - #161370)
• Bump uiprotect to 10.0.1 (@RaHehl - #161397)
• Bump Insteon panel to 0.6.1 (@teharris1 - #161411)
• Bump music-assistant-client to 1.3.3 (@arturpragacz - #161438)
• Revert deprecation of server_host for container installations (@emontnemery - #161443)
• Bump opower to 0.16.5 (@tronikos - #161450)

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 2026.1.

It’s been a busy few months composing behind the scenes, building up to a massive crescendo. Today, the beat finally drops on Music Assistant’s biggest update yet. With version 2.7, Music Assistant is getting all jazzed up with a visual overhaul, a chart-topping lineup of new features and providers, along with a brand-new streaming protocol we’re spinning up ourselves.

Of course, you can always update and experience all the great new stuff without reading the rest of this, but you might miss a deep cut. In fact, we can’t even cover everything in this blog (there really is that much), so go sing your praises for anything we missed in the comments!

Table of contents

• Marvin joins the team
• A visual overhaul
• Users and logins
• Remote music streaming
• Introducing Sendspin
• AirPlay additions
• Lyrics support
• Smart fading
• And much more
• Join the audio revolution

“With a Little Help from My Friends”

Marvin joins the team

Music Assistant has gained its first full-time employee at the Open Home Foundation. No, not me! My day job is leading the Ecosystems department at the foundation (which comprises all the software projects the Foundation has that are not Home Assistant itself). Marvin will be joining the foundation in the new year to work full-time on Music Assistant, leading the project’s day-to-day operations. Marvin has been contributing to the project for three years now, working on all sorts of parts of the project, and specifically with the Apple Music and YouTube providers.

Not to worry, I’m pretty obsessed with my audio setup and will still be tinkering on my little pet project 😁.

“Everything in Its Right Place”

A visual overhaul

A well deserved visual refresh

Music Assistant joining the foundation has given us a lot more than a nice open home; it’s given the project clearer direction and some expert help. One area some people felt Music Assistant fell short was its UI and UX, and in version 2.7, we’re starting the process of giving it a major overhaul, making it look as good as your music sounds!

This is just the beginning of a big process, so expect every update to bring more polish. The first thing you’ll probably notice is the collapsible navbar on the left of the screen, which looks pretty familiar to another Assistant 😉. Now it’s much more intuitive, especially for new users. The settings page has also been made much easier to navigate with breadcrumbs.

The biggest star of the show is the new Built-in Player, which lets you listen to music on the browser you’re using to hunt for your next track. Great for double-checking if the next song is family-friendly before sending it to every speaker in the home.

“Bulletproof”

Users and logins

User profiles for the whole family!

A lot of new features we’ve implemented wouldn’t be possible without some form of login and authentication. It was a much-requested feature, as security even within your home shouldn’t be ignored. We know logging in every once in a while can be a minor inconvenience, but we’ve tried to make it as unobtrusive as possible, even implementing a way to use your Home Assistant login as a “Single Sign-On”.

You can now have different user profiles with their own music providers. No more having four Tidal accounts all sitting next to each other, cluttering up the Playlists tab. You can even assign who has access to each speaker; say goodbye to the kids playing Demon Hunters on your office speaker during your performance review 😅. In Settings, just head to the User Management section, where you can add and edit your new users.

“Around the world”

Remote music streaming

No matter where, no matter when

One feature made possible with our new login interface is remote music streaming – yes, that’s correct, Music Assistant anywhere you can connect to the internet. We’ve created a new web app that allows for remote connections while you’re out and about.

It uses Home Assistant Cloud’s built-in multimedia streaming capabilities (WebRTC) to help route the audio from your Music Assistant server to wherever you are. A Home Assistant Cloud subscription is not required to use this feature; a big shoutout to Nabu Casa for providing their infrastructure for free to our users. Home Assistant Cloud subscribers get access to even more powerful routing, which improves streaming in more places. This subscription also supports the full-time development of Music Assistant 🙏.

This connection is peer-to-peer and end-to-end encrypted, meaning no one will know if you’re listening to ABBA 😊. I wouldn’t say it’s ready to replace your current music streaming service, but it’s a great way to get your FLACs playing at a friend’s house. You could even open two instances of the web app and stream it to two devices, and they’ll be synchronized… but how is that even possible?

“Spin me right round”

Introducing Sendspin

For some time, the Music Assistant team has been looking for the best way to stream audio, album art, and other music visualizations to the devices we have around our homes. There are a couple of projects out there doing cool stuff with streaming audio, but not any that fit our needs. So, when it doesn’t exist, it’s time to start building.

Introducing Sendspin, a new multimedia streaming and synchronizing protocol. It’s fully open source and free to use. Sendspin can stream high-fidelity audio, album art, and visualizer data, automatically adapting to each device’s capabilities. Imagine an e-paper display showcasing the album cover, while multiple speakers play in sync, and smart lights pulse to the rhythm.

The best way to use it right now is either via your browser or a Home Assistant Voice Preview Edition running beta firmware. We’ve built the experimental ability to use Sendspin on Google Cast-capable speakers (we’re also looking to do the same with AirPlay-capable speakers), which will allow Sendspin to work with a lot of different hardware.

A big thanks to Maxim and Kevin at the Open Home Foundation, who have been instrumental in making Sendspin a reality. Even though it can do some impressive stuff today, it’s very much a tech preview, and this announcement is our call to all developers and DIY audio hobbyists – we need your help building and testing this. This is the spec, start building with it!

All the best things in life are meant to be shared, and your music should be as free and open as the software we love. So spin that record 💿, drop the needle, and send that music across your entire home.

“Aeroplane”

AirPlay additions

We recently added support for external audio sources, the first being Spotify Connect. This allows you to stream audio from the Spotify app to your Music Assistant server, which could send it across all your speakers, even if they don’t support Spotify Connect. We’ve now added the ability to send AirPlay audio to Music Assistant, which you can then send anywhere in your home.

We also now support AirPlay 2 speakers as a player provider, which means perfectly synced audio across all your AirPlay 2-capable speakers, like HomePods. We recommend reading the limitations in the documentation, as not all AirPlay 2 devices are made equal 🤦‍♂️.

“Sing”

Lyrics support

It's time for karaoke!

Never again be left guessing what Kurt is saying in Smells Like Teen Spirit. As of Music Assistant 2.6, you can now see the lyrics of the song you’re playing. If the lyrics provider supports it, there is the ability to have these words time-synced, making it more like karaoke. Lyrics can be found when you open the queue menu and it will be in the “lyrics” tab (this tab will only appear if the track name, artist and album are matched to the lyrics providers). We started with support of LRCLIB, but have since added Tidal lyric syncing, Genius lyrics, and local LRC files.

“Smooth operator”

Smart fading

Making your playlists seamless

Music Assistant is now your personal in-house DJ, perfectly blending one song into the next, and unlike a DJ it always takes your requests 😎. This latest update adds Smart fading, which takes into account the BPM of each song, to make crossfading between songs sound more natural. To turn it on, go to your player of choice, scroll down to the Audio section, and choose “Enable Smart Fades”.

“All the small things”

And much more

None of these updates are small things, but I’m running out of space, so here is the rest of the hot 100:

• There are now DSP presets that allow you to quickly save and apply custom configurations.
• Track and share your listening history, with the addition of scrobbling, with support for LastFM, ListenBrainz, and Subsonic.
• Several new player providers have been added, including Yamaha MusicCast, and Roku devices running Media Assistant.
• Added VBAN as a new input provider.
• New radio and podcast providers include Radio Paradise, Podcast Index, BBC Sounds, gPodder, iTunes Podcasts, Dl.fm, and ARD Audiothek.
• Can’t follow Phish on tour? Luckily, the new Phish.in provider has you covered. There’s also Nugs.net if you’re looking for more live music.
• Another cool hodgepodge of audio is the Internet Archive, which can now be added as a provider.
• One of Japan’s biggest streaming platforms Niconico has been added as an audio provider ㊗️.

“Rebel yell”

Join the audio revolution

Music Assistant is also cast compatible!

Your music, your players – it’s time to take back control of your music and the devices you want to play it on. If you’re new to Music Assistant, check how to get started here. While we’re excited about these new features, we’re not hitting pause anytime soon. We’d love to hear your feedback in the comments or on Discord.

If you’re ever in need of a device that works great with Home Assistant, well, I have just the program for you. Works with Home Assistant is our certification program that ensures devices work seamlessly and locally, all with brands that back them up.

Did you know that this year the Works with Home Assistant program has certified 12 partners across 12 months? That’s more than were certified in the two years since the program launched in 2022! The full list of devices is insanely long now (luckily, we made it searchable). To make all this happen over just one year, a lot of important things have been happening behind the scenes.

Moving to a non-profit foundation

In August 2024, the Open Home Foundation took over Works with Home Assistant. This helped reinforce that this program is not a commercial venture: it exists solely to connect our users with brands that support the foundation’s core values of privacy, choice, and sustainability.

When we moved it over to the foundation, we also took that chance to beef-up our processes, with robust legal contracts that ensure every partner who joins the program formally commits to things like offering users long-term support and easy updates.

It’s all about the devices

When we started the program we certified brands, but now we certify devices. This means you know exactly which sensors, switches, or other gadgets have been rigorously tested by us to ensure the best experience with Home Assistant. Each certified device has to work locally, without the need for cloud subscriptions or control.

We can now certify in phases, rather than overwhelming our testers with a truckload of devices in order to launch one partner. Also, if a manufacturer has one device that is cloud-controlled, it doesn’t blacklist any remaining items they have that could operate perfectly well locally. It sometimes means that sometimes your favorite devices aren’t part of the first wave of certification but, trust us, the partners check the comments 😉.

Making it easy to find certified devices

Here’s a conundrum: the more products that are certified, the harder it is for you to see and find them. The good news is I think we’ve cracked it!

Last week, we published the first version of our new searchable certified device list. Previously, you’d have to hunt around for info by checking the integration page or digging through launch blogs to see if a device was certified. Now, certified devices are kept up to date in one central, easy-to-use location, with extra information on the region they’re available in, the protocol we’ve certified them under, and notes about any secondary functionality we’re still working on.

So many (useful) columns!

The badge had a makeover

Every certified device earns the right to display our badge on its packaging, proudly announcing it Works with Home Assistant. If you’re not part of the program, you’re not allowed to use the Home Assistant logo. We used to have different versions of the badges depending on whether the device used Matter, Zigbee, or Z-Wave, and so on, but – let’s be honest – they were overcomplicated and impossible to actually read on a box!

Since the badge is such an important signal when you’re browsing products, we decided to simplify it and focus purely on that mark of quality. Now we have just two versions: a color badge and a monochrome design that are easier to read on any packaging.

We love to see the new badge being used IRL!

Companies of all sizes

For 2025, our goal was simple: we wanted both the big names and passionate community projects to be able to join. Yes, we’re thrilled to have major smart home players such as Shelly and Reolink committing to the program, but it’s equally important for us to connect with smaller, community-built projects – the start-ups or developers who keep open source at the heart of everything they do, like AirGradient and Apollo Automation.

This commitment to inclusivity is a big reason why we keep the annual fee for joining the program deliberately low, at only 500 CHF (per partner, not device) per year. We want to ensure being part of Works with Home Assistant is achievable for everyone who shares our vision.

Some of our team visiting the Apollo booth at IFA Berlin in September.

Improving testing

Testing hasn’t always been perfect – we knew we needed to make improvements, and the community has been amazing in helping us find things we need to look at. Like everything we do, we learn as we go, we iterate, and we improve. Previously, everyone was testing in their own way, but now we’ve standardized the way we test and give feedback to partners. This means testing is more consistent, exacting, and able to handle higher volumes – one of the reasons why we’ve been able to increase the number of devices we’ve certified so radically!

A lot of devices that come across our desks don’t pass certification, and it’s often due to organizations not fully understanding the requirements of joining. While this can vary greatly depending on the device and protocol, it was clear we needed to be more transparent. So as well as publishing our Works with Home Assistant Working Group Resolution, we’re also publishing further testing information: this sample testing report for a simple smart plug shows you the process we follow.

Keeping Home Assistant on the bleeding edge

Because we get to see and test new devices in advance, and receive feedback from our certified partners as part of the process, we have a sneak peek into what vendors have in mind for 2026 and beyond. This allows us to look at our product roadmap and see where we need to realign with innovations in the market. By testing today’s devices, we’re guiding tomorrow’s Home Assistant features!

Spot one of the certified cameras in our State of the Open Home segment

What can be controlled in Home Assistant

A core aim of the program is to ensure all certified devices have their “key functionality” available within Home Assistant. So how do we decide what aspects are controllable in Home Assistant and what doesn’t make the cut?

1. Key: First, we look at the functionality as a whole. Let’s use a door lock for example. The door should lock and unlock from within Home Assistant. That’s key functionality, get it? 😉
2. Secondary: If the lock also chimes when it locks or unlocks, we think of that as “secondary” functionality. We recommend that the manufacturer has it as an “exposed feature” in Home Assistant, so you can turn it off during quiet hours for example, but it wouldn’t block certification.
3. We have to look at what’s actually supported by the open standard that we’re testing against too. If a feature is not currently supported by the specification, there’s no way for the manufacturer to actually implement it. This is one of the major challenges in certifying against ‘younger’ specifications such as Matter.

We use our best judgment on this, but we also want your feedback, because everyone has a slightly different point of view, even within our team and testers – so look out for our user research requests, or please share your thoughts in our comments below!

Connecting with our community

For all this talk of testing, Works with Home Assistant is primarily about people and partnerships! As a foundation, we’re focused on making sure the program stays deeply connected with the community it serves, both online and in person.

We’ve been stepping up our presence at meetups and events around the world, so we can share the latest developments and gather your valuable feedback. From gigantic trade shows like CES in Las Vegas to small, local get-togethers, you can expect to see us there! We also want to do this online, so you can ask partners questions on streams, or in comments – keep an eye out for more of this in future.

San Diego Meetup

On to 2026

So that was 2025 in a (big) nutshell. As for 2026, we want to kick it off with some wonderful Zigbee partners we’ve been working really hard on – particularly after the awesome launch of Connect ZBT-2. Even though Zigbee is one of the longest-established protocols, it’s actually one of the hardest for us to test and certify because so many devices operate outside the official specification. This means our team and partners do a lot of prep to get them to a testable state – but in doing so we’re driving big improvements in functionality for everyone!

We also want to improve coverage globally, so, regardless of region, everyone who uses Home Assistant has a good range of certified options to choose from. This means we’re actively seeking partners who will cover regions outside of Europe and North America for everyday essentials like smart plugs and lighting.

As ever, everything coming up will be covered right here – so stay tuned for updates… and here’s to certifying many more devices in 2026! 🎉🥳🎊

Home Assistant 2025.12! 🎄

As the year winds down and the holidays approach, we’re closing out 2025 with a release that’s all about giving you more control and a little bit of magic. ✨

This month, we’re unveiling Home Assistant Labs, a brand-new space where you can preview features before they go mainstream. And what better way to kick it off than with Winter mode? ❄️ Enable it and watch snowflakes drift across your dashboard. It’s completely unnecessary, utterly delightful, and exactly the kind of thing we love to build. ❄️

But that’s just the beginning. We’ve been working on making automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] more intuitive over the past releases, and this release finally delivers purpose-specific triggers and conditions. Instead of thinking in (numeric) states, you can now simply say “When a light turns on” or “If the climate is heating”. It’s automation building the way our mind works, as it should be. 🧠

Oh, and if you’re looking to level up your Zigbee or Thread network, check out the Home Assistant Connect ZBT-2 we released last month. It’s four times faster and has a gorgeous new antenna design that you’ll actually want to display on your desk. 📡

From all of us working on Home Assistant:

Thank you for an amazing 2025! ❤️

Happy holidays, and enjoy the release!

../Frenck

• Home Assistant Labs 🧪
• Purpose-specific triggers and conditions
• More dashboard improvements!
  • Set a system-wide default dashboard
  • Reorder areas and floors
  • Experimental dashboards have graduated
  • Home dashboard improvements
  • Undo and redo in the dashboard editor
• Power and water in the Energy dashboard
  • Real-time power monitoring
  • Downstream water meters
  • New energy layout
• 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
  • Get insight into your AI conversations
  • Add entities to Android widgets and favorites
• Patch releases
  • 2025.12.1 - December 5
  • 2025.12.2 - December 8
  • 2025.12.3 - December 12
  • 2025.12.4 - December 19
  • 2025.12.5 - December 29
• 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 @TimoPtr, @laupalombi, @jlpouffier, and @MindFreeze who helped write these release notes. Also, @edenhaus, @tr4nt0r, @jpbede, @RaHehl, @bieniu, @arturpragacz, and @piitaya for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️

Home Assistant Labs 🧪

When we develop new features for Home Assistant, we often find ourselves in a tricky spot. A feature might be fully built and tested, but we’re not entirely sure if it’s the right fit for everyone just yet. Maybe we want to gather some real-world feedback first, or perhaps we want to see how the community uses it before committing to keeping it around forever.

That’s where Home Assistant Labs comes in! 🧪

Labs is a brand-new place in Home Assistant that gives you a sneak peek at features we’re working on. These are not unfinished experiments or unstable beta features. They are fully functional and tested, but they might change or even disappear based on feedback. We are committed to building in the open, and we want to give more people the choice to hop into the lab with us. By joining us, your feedback will directly help refine these features for the entire community.

The very first preview feature available in Labs is Winter mode ❄️, inspired by a community post on Reddit originally created by u/Possible-Week-5815. Enable it, and watch your Home Assistant interface transform into a winter wonderland with falling snow. A fun way to get into the holiday spirit!

When you enable a preview feature, you can also choose to create a backup first, just to be safe. And if you change your mind? Simply disable it again. No restart required!

Preview features are off by default, and enabling them won’t affect your existing setup. It’s completely optional, so if you prefer to stick with the battle-proven experience, that’s totally fine. But if you’re curious and want to explore what’s coming next, Labs is the place to be.

But what was the first Labs preview feature we put in there? Well, it’s a big one…

Purpose-specific triggers and conditions

Almost two years ago, we released a new automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] editor that unwrapped all our actionsActions are used in several places in Home Assistant. As part of a script or automation, actions define what is going to happen once a trigger is activated. In scripts, an action is called sequence. [Learn more] and made them easier to understand. Instead of a single, obscure “Call service” action, you now see clear options like “Light: Turn on” or “Media Player: Set Volume”.

Ever since, we’ve been wondering: could we do the same for triggersA trigger is a set of values or conditions of a platform that are defined to cause an automation to run. [Learn more] and conditionsConditions are an optional part of an automation that will prevent an action from firing if they are not met. [Learn more]? Instead of relying on technical, state-based options, what if we could offer intuitive alternatives that just make sense? Options like “When a light turns on” or “If a light is on”.

That idea set a two-year plan in motion, and today it’s finally becoming a reality.

Along the way, we discovered something interesting: many of you take a “target-first” approach when building automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]. You think about what you want to automate (a deviceA device is a model representing a physical or logical unit that contains entities., an 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], or 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]) before thinking about how to automate it (which action to perform or which trigger to use). This release embraces that mindset with a completely new way to build automations.

Purpose-specific triggers and conditions are now provided directly by domainsEach integration in Home Assistant has a unique identifier: The domain. It is often shown as the first part (before the dot) of entity IDs. like Light, Climate, Fan, and others, covering the most common automation use cases.

These new triggers and conditions fully support targeting. This means you can trigger an automation when any light in your living room turns on, without having to list them one by one or create a group beforehand. Targeting an area keeps things simple: it’s always aligned with how your home is organized, and you don’t have to update anything when you add or remove devices.

LabelsLabels in Home Assistant allow grouping elements irrespective of their physical location or type. Labels can be assigned to areas, devices, entities, automations, scenes, scripts, and helpers. Labels can be used in automations and scripts as a target for actions. Labels can also be used to filter data. [Learn more] are supported too! You can now check if any of your Christmas lights are on. Perfect timing for the holidays! 🎄

We’ve also introduced a new way to pick triggers, conditions, and actions that fits this target-first approach. You can navigate your home by floorA floor in Home Assistant is a logical grouping of areas that are meant to match the physical floors in your home. Devices & entities are not assigned to floors but to areas. Floors can be used in automations and scripts as a target for actions. For example, to turn off all the lights on the downstairs floor when you go to bed. [Learn more], then area, then device, and see exactly which options are available for each target. It’s a much more intuitive way to build automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more].

This feature is still being refined, so we’ve made it available as a preview feature in Labs. Head over to Settings > System > Labs to enable it and help us shape the future of automation building!

More dashboard improvements!

We have a lot of dashboard improvements to share in this release! From better default dashboard management to an improved Home dashboard, we have been busy making your Home Assistant experience even better.

Set a system-wide default dashboard

Picking a default dashboard is now a system-level setting that takes effect instantly for all users on your Home Assistant installation. The dashboard you choose will appear at the top of the sidebar, replacing the current default.

But don’t worry, personal preferences still matter! We added a new setting in your User profile where you can override the system default and set your own preferred dashboard.

If you set your phone to one dashboard and your wall tablet to another, they’ll now both revert to the default dashboard. If you want your wall tablet to use a different dashboard than your other devices, we recommend giving it a separate user profile that you can customize however you want.

Reorder areas and floors

When using the built-in dashboard experiences (Home, Lights, Security, and others), one of the main pain points was the strict ordering of areasAn 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] (alphabetically) and floorsA floor in Home Assistant is a logical grouping of areas that are meant to match the physical floors in your home. Devices & entities are not assigned to floors but to areas. Floors can be used in automations and scripts as a target for actions. For example, to turn off all the lights on the downstairs floor when you go to bed. [Learn more] (numerically by level). This often didn’t make sense in a real home, where your guest bathroom shouldn’t appear before your living room, and the attic is rarely more relevant than the main floor.

Now you can go to Settings > Areas, labels & zones and use the new Reorder floors and areas menu to manually drag and drop any area or floor to reorder them. Your changes will instantly apply to all built-in dashboards that show areas and floors.

Experimental dashboards have graduated

With the launch of Labs, we retired the experimental flag from the dashboard creation list. The Home dashboard can now be found in the dashboard list (still not visible by default), and the Areas dashboard has evolved into Home, so we’ve removed it for now. If you’re using the Areas dashboard, it will continue to work; you just won’t be able to create another.

Home dashboard improvements

We added a new sidebar to the Home dashboard that gathers quick access links we think are useful for you. There’s also a nicer area and floor layout that uses space more efficiently. On a more technical level, the Home dashboard is now a proper built-in dashboard and shows up in the dashboard list.

Undo and redo in the dashboard editor

The dashboard editor now includes the undo and redo feature that we added in 2025.10 to the automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] and scriptScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more] editor. This allows you to experiment safely while editing your dashboards. You can undo up to 75 changes or restore them with a single click, making editing dashboards faster and less stressful.

Thanks to @jpbede for implementing this handy feature!

Power and water in the Energy dashboard

The Energy dashboard has been helping you track your energy and gas usage for years now, and this release brings two great additions: real-time power monitoring and downstream water tracking.

Real-time power monitoring

Until now, the Energy dashboard was all about energy: the cumulative kWh you’ve consumed or produced over time. But sometimes you want to know what’s happening right now. How much power is that appliance actually drawing? Is your solar system producing at this very moment?

With this release, you can now configure power sensors alongside your energy sensors. Track your real-time grid consumption, see how much you’re exporting back to the grid, and watch those watts flow in real-time. The power configuration options now appear alongside energy settings for each source or device, and new power graphs let you see your power consumption throughout the day.

Downstream water meters

The Energy dashboard has been tracking your water consumption for a while now, but it was missing something: the ability to see where all that water is actually going. Just like you can track individual devices for energy consumption, you can now add downstream water meters to break down your water usage.

Got a smart irrigation controller? A water softener with a flow meter? A separate meter for your pool? Now you can track them all and see exactly how your water consumption is distributed across different uses.

There’s also a brand-new water sankey card that visualizes your water flow, just like the energy sankey diagram you already know. It’s a great way to see where your water is going at a glance.

The new water sankey card shows where your water is going at a glance.

New energy layout

To make room for this new functionality, the Energy dashboard has been reorganized. Don’t worry: if you only have energy configured, you’ll still see the same dashboard. But if you add water, gas, or power, the dashboard will be split into several tabs.

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:

• Airobot, added by @mettolen
  Control and monitor your Airobot smart thermostats for intelligent floor heating control via the local REST API.
• Anglian Water, added by @pantherale0
  Integrate your Anglian Water smart water meter to track water usage and consumption costs.
• Backblaze B2, added by @ElCruncharino
  Use a Backblaze B2 cloud storage bucket as a backup location for your Home Assistant backups.
• EnergyID, added by @Molier
  Sync anything from your home directly to EnergyID for advanced analytics, performance tracking and benchmarking.
• Essent, added by @jaapp
  Monitor dynamic electricity and gas prices for Essent customers in the Netherlands with variable pricing contracts.
• Google Air Quality, added by @Thomas55555
  Get real-time air quality data for your location using Google’s Air Quality API.
• Google Weather, added by @tronikos
  Use Google Weather as a source for weather data, providing current conditions, hourly forecasts for the next 24 hours, and daily forecasts for the next 10 days.
• Hanna, added by @bestycame
  Fetch pool water quality data from your Hanna Pool Controller device, including pH, chlorine levels, ORP values, and water temperature.
• Home Assistant Labs, added by @frenck
  A dedicated panel where you can preview and test new features before they become standard in Home Assistant.
• Philips Hue BLE, added by @flip-dots
  Control your Philips Hue Bluetooth lights directly with Home Assistant, without the need for a Hue Bridge.
• Saunum, added by @mettolen
  Integrate your Saunum Leil sauna control unit to precisely control temperature and monitor your sauna’s operation.
• Victron BLE, added by @rajlaud
  Integrate Victron Energy devices that support the Bluetooth Low Energy protocol for real-time monitoring.

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:

• Cosori, provided by VeSync, added by @joostlek
• VÁGNER POOL, provided by SEKO PoolDose, added by @lmaertin

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 ones are also being constantly improved. Here are some of the noteworthy changes to existing integrations:

• @piitaya updated the ESPHome integration to let Home Assistant generate entity IDs using its standard rules, aligning it with how other integrations work.
• Thanks to @bdraco, you can configure Wi-Fi on Shelly generation 2+ devices directly from Home Assistant via Bluetooth.
• Shelly now supports control modes for upcoming Shelly Cury devices. Nice work, @bieniu!
• Thanks to @gjohansson-ST, System Monitor now exposes fan sensors and battery sensors for your system.
• The Tuya integration received a lot of love! Cat litter boxes now expose switches, buttons, lights, and sensors for controlling your pet’s automated litter box. On top of that, doorbell events are now supported too. Thanks, @heindrichpaul!
• @starkillerOG expanded the Reolink integration with an exposure mode select and audio noise reduction controls for supported cameras.
• The OpenAI Conversation integration now supports GPT-5.1 models. Great work, @Shulyaka!
• Air conditioner and microwave support has landed in the Home Connect integration, expanding the range of supported BSH appliances. Thanks, @Diegorro98!
• @zerzhang added support for the SwitchBot smart thermostat radiator to the SwitchBot integration. Nice!
• The Xbox integration got some love from @tr4nt0r! You can now link multiple Xbox accounts, track how many friends you (and your friends) have, see if they’re in a party, and control more remote functions. The media browser also gained a new category showcasing official game art and screenshots.
• Got an Ecovacs robot? The Ecovacs integration now has a border spin switch (to reach those tricky edges while mopping) and an auto-empty select entity. Thanks, @aronnebrivio!
• The VeSync integration gained a child lock switch, giving you control over this safety feature for your devices. Thanks, @cdnninja!
• @XiaoLing-git added support for the SwitchBot smart radiator thermostat to the SwitchBot Cloud integration.
• The SQL integration now supports using templates in your queries, giving you more flexibility when querying your databases. Great addition, @gjohansson-ST!
• @tomwilkie expanded the Prometheus integration to export metrics for the water_heater domain.
• The Anthropic integration now supports AI task entities. Thanks, @Shulyaka!
• Portainer can now show you resource usage of your containers. Nice work, @erwindouna!
• @thomasddn added a button to enable reduced guard mode for compatible vehicles to the Volvo integration.
• The Plugwise integration now supports the new Anna P1 device and gained a select entity for zone profiles on Adam devices. Thanks, @bouwew!
• Bang & Olufsen users can now use their Beoremote One with Home Assistant. The remote’s buttons are exposed as event entities. Awesome, @mj23000!
• @VandeurenGlenn added the climate platform to Niko Home Control, letting you control your Niko heating zones.
• The Saunum integration now supports fan control, giving you control over your sauna ventilation. Thanks, @mettolen!
• @nasWebio added alarm control panel support to the NASweb integration, allowing you to arm and disarm your security system.
• The Nederlandse Spoorwegen integration received a refactor to improve reliability and maintainability. Thanks, @heindrichpaul!

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 🏆

  • Brother Printer, thanks to @bieniu
  • Shelly, thanks to @davidrapan

• 1 integration reached gold 🥇

  • Google Assistant SDK, thanks to @tronikos

• 2 integrations reached silver 🥈

  • LCN, thanks to @alengwenus
  • Telegram bot, thanks to @hanwg

• 2 integrations reached bronze 🥉

  • Music Assistant, thanks to @OzGav
  • Transmission, 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:

• DuckDNS, done by @tr4nt0r

Farewell to the following

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

• Dominos Pizza: The Dominos Pizza integration has been removed. The integration no longer functions and its underlying source has been unmaintained since 2019.
• Flick Electric: The Flick Electric integration has been removed. All customers of the Flick Electric company have already been moved to Meridian Energy. The service this integration used is already non-functional.
• The following integrations have been removed as they are incompatible with the currently supported installation methods:
  • Bluetooth Tracker
  • CUPS
  • Decora
  • dlib Face Detect
  • dlib Face Identify
  • Eddystone Temperature
  • GStreamer
  • Keyboard
  • LIRC
  • Pandora
  • Raspberry Pi Camera
  • SMS
  • Snips
  • TensorFlow

Other noteworthy changes

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

• New template math functions! @akx added clamp, wrap, and remap to manipulate numbers in your templates. Awesome!
• The activity card now supports filtering by state, making it easier to see specific events. Nice one, @karwosts!
• @MindFreeze added min and max options to the bar gauge feature for tile cards, giving you more control over the gauge range.
• You can now delete helpers directly from the helpers panel, without having to open them first. Thanks, @frenck!
• The blueprints panel now shows how many automations and scripts use each blueprint. Great for keeping track, @EarMaster!
• @timmo001 added a handy trick: double-click the automation editor sidebar to reset its width.
• Labels now show up on the device information card, making it easier to see how your devices are organized. Thanks again, @timmo001!

Get insight into your AI conversations

Ever played around with AI in Home Assistant and wondered what data is actually being sent?

@balloob upgraded the voice assistant debug interface, and you can now inspect the system prompt that tells the AI how to behave, along with any tool calls it made to generate your answer.

This makes it much easier to figure out why the AI decided to skip over that one 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], or why it called a specific tool. You can find the debug interface in the voice assistant configuration panel.

Add entities to Android widgets and favorites

If you’re using the Home Assistant Companion app for Android, there’s a handy new feature waiting for you! Starting with app version 2025.11, you can now add 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] to widgets and Android Auto favorites directly from the entity’s more info dialog.

With just a few taps, you can:

• Add widgets for quick control of entities right from your home screen
• Set entities as Android Auto favorites, making them quickly accessible in your car

No more deep-diving into app settings! The Add to option appears in the more info dialog with options tailored to the entity you’re viewing. For example, adding a media player widget is only available for media players.

This is a first step in integrating native mobile features directly into the Home Assistant interface. Future releases will expand this with support for creating shortcuts, tiles, and watch favorites.

Thanks for this great addition, @TimoPtr! 🙏

Patch releases

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

2025.12.1 - December 5

• Fix Rituals Perfume Genie ([@quebulm] - #151537)
• Move telegram-bot URLs out of strings.json ([@maxmichels] - #155130)
• Fix Starlink’s ever updating uptime (@davidrapan - #155574)
• Display error when forming new ZHA network fails ([@TheJulianJES] - #157863)
• Move teslemetry time-of-use URL out of strings.json (@jbouwh - #157874)
• Correctly pass MopParserConfig for Roborock (@Lash-L - #157891)
• Fix VeSync binary sensor discovery (@cdnninja - #157898)
• Bump reolink_aio to 0.17.1 (@starkillerOG - #157929)
• Move out URL of Xiaomy_aquara from strings.json (@jbouwh - #157937)
• Set account number as required for Anglian Water config entry (@pantherale0 - #157939)
• Move translatable URL from rainmachine push_weather_data action description (@jbouwh - #157941)
• Convert image URLs to secure URLs in Xbox integration (@tr4nt0r - #157945)
• Add pyanglianwater to Anglian Water loggers (@pantherale0 - #157947)
• Fix template migration errors (@Petro31 - #157949)
• Move Yeelight URLs out of translatable strings for action descriptions (@jbouwh - #157957)
• Move out zwave_js api docs url from strings.json (@jbouwh - #157959)
• Fix unit parsing in Tuya climate entities (@epenet - #157964)
• Update template deprecation to be more explicit (@Petro31 - #157965)
• Move pilight URL out of strings.json (@jbouwh - #157967)
• Move out example URL and IP of strings.json for reolink (@jbouwh - #157970)
• Add subscribe preview feature endpoint to labs (@piitaya - #157976)
• Bump python-Roborock to 3.10.0 (@Lash-L - #157980)
• Bump oralb-ble to 1.0.2 ([@abmantis] - #157992)
• Bump evohome-async to 1.0.6 ([@zxdavb] - #158005)
• Fix doorbird duplicate unique ID generation (@ptarjan - #158013)
• SharkIQ dep upgrade v1.5.0 ([@funkybunch] - #158015)
• Bump python-roborock to 3.10.2 (@allenporter - #158020)
• Change ZHA strings for incorrect adapter state ([@TheJulianJES] - #158021)
• Improve action descriptions for Telegram bot (@hanwg - #158022)
• Fix missing template key in deprecation repair (@Petro31 - #158033)
• Prevent entsoe from loading (@joostlek - #158036)
• Do not create restart button for sleeping gen2+ Shelly devices (@bieniu - #158047)
• Replace deprecated preview image model (@Shulyaka - #158048)
• Move lametric URLs out of strings.json (@jbouwh - #158051)
• Move example image path out of translatable strings (@jbouwh - #158053)
• Fix inverted kelvin issue (@Petro31 - #158054)
• Bump uiprotect to 7.33.2 (@RaHehl - #158057)
• Update frontend to 20251203.1 (@piitaya - #158069)

2025.12.2 - December 8

• fix Lutron Caseta smart away subscription (@omrishiv - #158082)
• Fix legacy template entity_id field in migration (@Petro31 - #158105)
• Revert “Remove Shelly redundant device entry check for sleepy devices” (@thecode - #158108)
• Ensure Roborock disconnects mqtt on unload/stop (@allenporter - #158144)
• Fix secure URLs for promotional game media in Xbox integration (@tr4nt0r - #158162)
• Add program id codes for Miele WQ1000 (@astrandb - #158175)
• Bump pymiele dependency to 0.6.1 (@astrandb - #158177)
• Bump asusrouter to 1.21.1 (@Vaskivskyi - #158192)
• Bump HueBLE to 2.1.0 (@flip-dots - #158197)
• Bump python-roborock to 3.10.10 (@allenporter - #158212)
• Be more specific about winter mode in the description (@piitaya - #158230)
• Fix description placeholders for system_bridge (@jbouwh - #158232)
• Bump google air quality api to 2.0.0 (@Thomas55555 - #158234)
• Fix zwave_js service description placeholders (@epenet - #158236)
• Fix yeelight service description placeholders (@epenet - #158239)
• Fix teslemetry service description placeholders (@epenet - #158240)
• Fix multiple top-level support for template integration (@Petro31 - #158244)
• Bump yt-dlp to 2025.12.08 (@andreimoraru - #158253)
• Update frontend to 20251203.2 (@piitaya - #158259)
• Skip check for onboarding done in Music Assistant integration (@marcelveldt - #158270)

2025.12.3 - December 12

• Fix Tuya BitmapTypeInformation parsing (@epenet - #158475)
• Move translatable URL out of strings.json for knx integration (@jbouwh - #155244)
• Improve Tuya HVACMode handling (@epenet - #158042)
• Bump pypck to 0.9.7 (@alengwenus - #158089)
• Bump blinkpy to 0.25.1 (@KiraPC - #158135)
• Fix webhook exception when empty json data is sent (@mikedast - #158254)
• Fix roborock off peak electricity timer (@allenporter - #158292)
• Switchbot Cloud: Fixed binary sensors didn’t update automatically (@XiaoLing-git - #158434)
• Add Tuya local_strategy to Tuya diagnostic (@epenet - #158450)
• Improve Roborock exception logging behavior for Zeo/Dyad devices (@allenporter - #158465)
• Fix Matter Door Lock Operating Mode select entity (@lboue - #158468)
• Bump asusrouter to 1.21.3 (@Vaskivskyi - #158492)
• Bump hanna-cloud to version 0.0.7 (@bestycame - #158536)
• Add measurement state class to ohme sensors (@andrew-codechimp - #158541)
• Bump python-roborock to 3.12.2 (@allenporter - #158572)
• Pin pycares to 4.11.0 (@bdraco - #158695)
• Add state_class to Growatt power and energy sensors (@johanzander - #158705)
• Update advanced_options display text for MQTT (@ndrwrbgs - #158728)
• Bump google air quality api to 2.0.2 (@Thomas55555 - #158742)
• Migrate Blink component to use hardware_id instead of device_id (@cdutr - #158765)
• Bump ical to 12.1.1 (@allenporter - #158770)
• Bump pylamarzocco to 2.2.3 (@zweckj - #158104)
• Bump pylamarzocco to 2.2.4 (@zweckj - #158774)
• Increase Xbox update interval to 15 seconds and refactor title data handling (@tr4nt0r - #158780)
• Bump pySmartThings to 3.5.1 (@joostlek - #158795)
• Bump aioasuswrt to 1.5.2 (@kennedyshead - #158727)

2025.12.4 - December 19

• Prevent empty aliases in registries (@FI-153 - #156061)
• Do not check Reolink firmware at start (@starkillerOG - #158275)
• Update pynintendoparental to 2.0.0 (@pantherale0 - #158285)
• Enable volvo engine status for all engine types (@thomasddn - #158437)
• Update pynintendoparental to 2.1.0 (@pantherale0 - #158487)
• Suppress roborock failures under some unavailability threshold (@allenporter - #158673)
• Suppress verbose UPnP subscription error logs (@ptarjan - #158677)
• Fix Sonos speaker async_offline assertion failure (@ptarjan - #158764)
• Bump pynintendoparental to 2.1.1 (@pantherale0 - #158779)
• Bump aioasuswrt 1.5.3 (@kennedyshead - #158882)
• Revert adding entity_category to Plugwise thermostat schedule select (@bouwew - #158901)
• Bump aiomealie to 1.1.1 and statically define mealplan entry types (@andrew-codechimp - #158907)
• Update systembridgeconnector to 5.2.4, fix media source (@timmo001 - #158917)
• Assume cover or valve is always “running” in google assistant when the state is assumed or the position is reported to allow it to be be stopped (@jbouwh - #158919)
• Bump ical to 12.1.2 (@allenporter - #158965)
• Update unnecessary error logging of unknown and unavailable source states from mold indicator (@Petro31 - #158979)
• Add exception handling for rate limited or unauthorized MQTT requests (@allenporter - #158997)
• Bump aioasuswrt to 1.5.4 (@upsuper - #159038)
• Bump blinkpy to 0.25.2 (@fronzbot - #159049)
• Fix slow event state updates for remote calendar (@allenporter - #159058)
• Bump aiodns to 3.6.1 (@mithomas - #159073)
• Bump pysmlight to v0.2.13 (@tl-sl - #159075)
• Improve icloud reauth flow (@PaulCavill - #159081)
• Sonos fix media player join to avoid race condition (@PeteRager - #159106)
• Sonos increase wait for groups timeout (@PeteRager - #159108)
• Bump pynintendoparental 2.1.3 (@pantherale0 - #159120)
• Bump soco to 0.30.13 for Sonos (@PeteRager - #159123)
• Handle missing Miele status codes gracefully (@astrandb - #159124)
• Bump ekey-bionyxpy to version 1.0.1 (@richardpolzer - #159196)
• Fix incorrect status updates for lcn (@alengwenus - #159251)
• Bump python-roborock to 3.18.0 (@Lash-L - #159271)
• Bump pypck to 0.9.8 (@alengwenus - #159277)
• Fix AttributeError in Roborock Empty Mode entity (@allenporter - #159278)
• Add missing strings for Shelly voltmeter sensor (@chemelli74 - #159332)
• Do not trigger reauth for addon in Music Assistant (@arturpragacz - #159372)
• Align format of voltmeter strings for Shelly (@chemelli74 - #159394)
• Bump ZHA to 0.0.81 (@puddly - #159396)
• Bump python-roborock to 3.19.0 (@allenporter - #159404)
• Remove users refresh tokens when the user get’s deactivated (@edenhaus - #159443)
• Update frontend to 20251203.3 (@bramkragten - #159451)

2025.12.5 - December 29

• Disable quoted cookies for compatibility with older SolarLog devices (@dontinelli - #157839)
• Normalize unique ID in WLED (@mik-laj - #157901)
• Change Samsung TV WoL turn_on log from warning to debug (@ptarjan - #158676)
• Fix ZeroDivisionError for inverse unit conversions (@ReneNulschDE - #159161)
• Add openid scope and update OAuth2 url:s in senz integration (@astrandb - #159265)
• Create issue for Sonos when Sonos system does not have UPnP enabled (@PeteRager - #159330)
• Bump insteon panel to 0.6.0 to fix dialog button issues (@teharris1 - #159449)
• Bump yalexs-ble to 3.2.2 (@bdraco - #158124)
• Bump yalexs-ble to 3.2.4 (@bdraco - #159476)
• Improve date handling in UniFi Protect media source (@RaHehl - #159491)
• Redact additional unnecessary diagnostic fields (@allenporter - #159546)
• Bump melissa to 3.0.3 (@kennedyshead - #159557)
• Bump valbusaio to 2025.12.0 (@cereal2nd - #159578)
• Bump uiprotect to 7.33.3 (@RaHehl - #159593)
• Fix Ecoforest unknown alarm translation key (@maylikenoother - #159594)
• Bump axis to v66 fixing an issue with latest xmltodict (@Kane610 - #159604)
• Bump python-roborock to 3.20.1 (@allenporter - #159621)
• Bump python-roborock to 3.21.1 (@allenporter - #159660)
• Fix Roborock repair issue behavior (@allenporter - #159718)
• Start reauth when roborock notices the MQTT session is unauthorized (@allenporter - #159719)
• Add state_class to Nuki battery sensor (@victor-gurbani - #159756)

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:

• Add a status callback for MQTT subscriptions
• Data Update Coordinator now supports Retry After
• Device identification buttons are now classified as diagnostic
• Improved error handling for oauth2 configuration without internet
• Introducing description placeholders for service action translations
• Introducing Labs: Preview features before they become standard
• Serialization of Store data in worker thread is now opt-in
• The capability_attributes field removed from CalculatedState

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.12.

The easiest way to start with Zigbee or Thread just got even better, with Home Assistant Connect ZBT-2. This USB adapter plugs into your Home Assistant system and opens up a world of smart device options. Between its precisely tuned antenna and next-generation chip, it’s a big step up for anyone looking to connect Zigbee, Thread, or Matter devices directly to Home Assistant.

For all our Zigbee fans, this might be the best upgrade you’ll make all year. We’ve squeezed every inch out of this technology, giving it the best range, speed, and stability possible. The same can be said for our Thread-heads out there (yeah, I just came up with that cool nickname 😎), making Matter or ESPHome Thread connections rock-solid. Pick whether to dedicate your Connect ZBT-2 to run a Zigbee or Thread network, and it’ll provide the best experience for that protocol (and if all these names just sound like new streaming services to you, check out our explainer below).

If you’re one of those people still rocking three different hubs, what are you waiting for… another giant server outage to take down your smart home? Ditch those cloud hubs and take back your privacy today. As an added bonus, your devices will likely get more controls, range, and resilience.

Available today starting at $49 and €45 (that’s the MSRP, and pricing will vary by retailer). Designed and built by Nabu Casa and the Open Home Foundation, every purchase helps fund the development of Home Assistant. For quick specs, details, and where to buy, visit our beautiful Home Assistant Connect ZBT-2 page.

Standing on the shoulders of giants

In 2022, we released Home Assistant Connect ZBT-1 (originally called SkyConnect), our first product in the Connect line and first USB adapter. Connect ZBT-1 was designed to be the easiest, most stable way to connect Zigbee devices to Home Assistant. It also came with Thread connectivity support, which was very new at the time. All these years later, it continues to receive software support and is a community favorite.

Sales of Connect ZBT-1 helped fund Home Assistant’s development, and we learned so much that has influenced its next iteration. Alas, as much as we love our little Connect ZBT-1, today we’re saying goodbye. We have now ended production of Connect ZBT-1, but software support will continue. If you’re still using Connect ZBT-1, expect it to keep working far into the future.

If you are looking to upgrade your Zigbee network with a Connect ZBT-2, don’t forget you can continue to use your Connect ZBT-1 as a way to dip your toes into the world of Thread – it’s very easy to switch operating modes.

Upgrading everything

Compared to its predecessor, this version has upgraded everything. First off, we’ve doubled the product number from ZBT-1 to ZBT-2… that’s 2x better already! But there’s definitely more.

Stick with an antenna

First off, to achieve peak performance, we moved away from the small “stick” form factor. Small USB sticks are convenient, but USB ports and nearby electronics can create interference that weakens the signal. With Connect ZBT-1, we recommended using a USB extension cable to keep the adapter away from noise.

The antenna has gone from safety pin-sized 🧷, to tablespoon-sized 🥄

With Connect ZBT-2, we’ve designed away this issue. It’s much easier to properly position as it’s now a free-standing antenna and base, which is perfectly tuned for Zigbee and Thread. The larger antenna is not only good at broadcasting to further away devices, but is also good at listening out for faint signals from far away devices. We even optimized the base, which acts as a “ground plane”, boosting the antenna’s performance. It includes a 1.5 m (4.9 ft) USB cable that lets you place it in a good spot to avoid any interference.

Four times the speed

Inside Connect ZBT-2 is the Silicon Labs MG24, an advanced Zigbee/Thread system-on-chip. Compared to the MG21 used in Connect ZBT-1, it brings higher processing power and better sensitivity to weak signals.

More baud, the better 😜

We also took the opportunity to quadruple the internal communications speed of the chip – taking the baud rate from 115,200 bps to 460,800 bps. In our testing, we saw consistent improvements in device responsiveness. Don’t expect your devices to turn on four times faster, but you’ll feel the difference when turning on several devices simultaneously.

Built for Home Assistant

It is really easy to take advantage of all this performance, as we always work to make Home Assistant hardware super easy to start with. Just plug in the device via the included cable into a spare USB port on your Home Assistant system, and the setup wizard will guide you through everything. This all works so well because the same people who built Zigbee and Thread into Home Assistant also helped build Connect ZBT-2.

You can start a new Zigbee or Thread network in minutes, or use our improved migration tools to move an existing network over. It’s a very easy upgrade, and most adapters migrate with just a few clicks. Best of all, every Home Assistant user upgrading to new adapters will benefit from these new migration tools. Just another example of how hardware sales help level up our software development.

Compatibility and flexibility

Home Assistant Connect ZBT-2 supports Zigbee 3.0 (and yes, we’re looking at Zigbee 4.0 support as well) and is keeping pace with Thread’s rapid development. We’ve tested it working great with ZHA, zigpy-cli, Zigbee2MQTT, matter.js, and OpenThread Border Router, giving you the flexibility to choose how you manage your network.

If it’s a Zigbee-certified device or Matter-certified device that uses Thread, it should work out of the box. Home Assistant already has one of the widest compatibility lists in the world, and our community continuously expands it with every new release. For brands that support the functionality, there are also Over-the-Air (OTA) firmware updates for devices.

Just note: Connect ZBT-2 can only use one protocol at a time, meaning you must choose either Zigbee or Thread. We’ve done extensive testing in the past on running both at the same time, and found it just doesn’t work well for a whole list of reasons.

Second-generation power

Our second-generation Connect line products are all about being open and performant, and one addition that fulfills this promise is our inclusion of the ESP32 chip. Connect ZBT-2 includes an ESP32-S3 as its USB controller, which is a little overkill for this job, but opens up a world of possibilities.

ESP32 devices are well understood by our team, but also the community. It means that anyone can change the firmware on this chip and possibly unlock cool new abilities. For instance, our recently released Connect ZWA-2 uses this same chip to support experimental firmware that adds new functionality. This isn’t to say we’ll do the exact same thing with Connect ZBT-2; it’s more to say the sky’s the limit with our second-gen products. The firmware it ships with is just the start, and we have some cool ideas cooking on what we can do next.

Open design

Look at all those exposed pins and pads 🤤

When we say open, we mean it. In the physical sense, it’s easy to open Connect ZBT-2 as there are no clips or glue, just some lovely standard Phillips head screws. The board has a gorgeous silkscreen, which explains all the chips, exposed pins, and pads.

The bootloader is unlocked, and all the firmware we build is open source and available to modify. We’ve also built a new website that makes it easy to flash the stock firmware, and in the future, experiment with new firmware. We’ll also be providing the PCB and outer casing files if you want to tinker with those. Openness makes our products better… literally, since our community helps us find and fix bugs.

Why USB?

Before you get in the comments asking about Power-over-Ethernet (PoE)… we totally agree it’s cool, but on this occasion, it’s not the direction we took. Yes, PoE has become easier to use and its performance, if implemented correctly, can be quite good (our testing with Connect ZWA-2 shows a pretty minor speed hit). Connect ZBT-2 is focused solely on ease-of-use and pure performance. That said, there are a lot of PoE fans at the foundation, and product sales help fund development, so who knows, maybe we’ll find a way to please everyone.

Don’t hide it

Most other USB adapters are designed to be hidden away, dangling behind a server cabinet. For one thing, antenna orientation is pretty important, but also cool tech should be on show! We’ve designed Connect ZBT-2 to be proudly displayed, and the top even lights up like a candle – perfect timing for the holidays 🕯️.

It all adds up

Not science, but an interesting before-and-after of just one network, about a 60% increase in direct connections 🤩

Nabu Casa, the commercial partner building all official Home Assistant hardware, has knocked the build of this device out of the park. When you combine every small improvement made to Connect ZBT-2, it adds up to a nice performance improvement, while maintaining its predecessor’s reputation for rock-solid stability. What’s more, every purchase helps support the Open Home Foundation and funds the development of Home Assistant. Upgrading your smart home has never felt so good!

What are you waiting for?

Get the most out of your smart home with an adapter that’s open source at its core, delivers maximum performance, and looks good doing it. Home Assistant Connect ZBT-2 is available today for purchase, and as always, thanks for supporting Home Assistant!

Home Assistant 2025.11! 🎉

November is here, and we’ve been hard at work refining some of the main experiences that you interact with every day, and I think you’re going to love what we’ve built.

My personal favorite this release? The brand new target picker. 🎯

It’s one of those changes that seems simple on the surface, but makes such a huge difference in how you build automations. You can finally see exactly what you’re targeting, with full context about which device an entity belongs to and which area it’s in. No more guessing whether you’re controlling the right ceiling light when you have three of them!

But that’s just the beginning. We’re continuing with the automation editor improvements, this time with a completely redesigned dialog for adding triggers, conditions, and actions. It’s cleaner, easier to read, and sets the foundation for some really exciting stuff coming in future releases. 🤫

And speaking of making things clearer, you can now control exactly how entity names appear on your dashboard cards. Want to show just the entity name? The device name? The area? Or combine them? Even if you rename things, your dashboards will stay perfectly in sync. No more manual updates needed!

Oh, and energy dashboard fans will appreciate the new pie chart view for device energy, complete with totals displayed in the corner of every energy card. 🥧

Enjoy the release!

../Frenck

PS: Oh, and pssst… Don’t tell anyone 🤫, but there might be something exciting being released on November 19th. Hit the bell on this announced YouTube stream to not miss it. Stay tuned! 😀

• A brand new target picker
• A brand new way to add triggers, conditions, and actions in your automations
• Naming entities on your dashboard
• Energy pie
• Progress for Home Assistant and Add-on updates
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Now available to set up from the UI
  • Integration quality scale achievements
  • Farewell to the following
• Other noteworthy changes
  • Improved logging efficiency
  • The new Home Dashboard keeps getting smarter
• Patch releases
  • 2025.11.1 - November 7
  • 2025.11.2 - November 14
  • 2025.11.3 - November 21
• 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 @bramkragten, @JLo, @MindFreeze, @agners, and @piitaya who helped write the release notes this release. Also, @silamon and @GemPolisher for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️

A brand new target picker

Have you ever been building an automation and wondered, “Wait, which ceiling light is this?” when you see three entities all named “Ceiling light”? Or tried to figure out how many lights you’re actually controlling when you target an entire floor or area?

We’ve all been there. Until now, the target picker didn’t show you the full picture. You couldn’t see which device an entity belonged to or which area it was assigned to. And when you selected a floor or area as your target, you had no idea how many entities you were actually affecting. This uncertainty meant many of you stuck with targeting individual entities, even though larger targets (like areas and floors) can make your automations much more flexible.

The new target picker changes all that. Now you get full context for everything you’re targeting, and you can see exactly how many entities will be affected by your action.

Want to dig deeper? You can expand any floor, area, or device to see exactly which entities are included and where they’re coming from.

This makes it so much easier to build automations that scale with your home. When you target an area or floor, your automation automatically adapts as you add or remove devices. No more updating your automations every time you add a new light or sensor. Your automations just work, which is exactly how it should be.

A brand new way to add triggers, conditions, and actions in your automations

It’s no secret that we’re currently working hard on making automations easier to create. After the release of the automation sidebar two releases ago, we are now introducing a new dialog to add triggers, conditions, and actions.

The changes are purely cosmetic: the dialog is bigger, so the description of each block is simpler to read, with a two-pane layout to ease both navigation and block selection.

The building blocks (which are used to perform more complex conditions or sequences of actions, such as repeating actions or branching out your sequence into multiple paths) have been moved into the main dialog on a second tab. There is now a single entry point to add something to an automation instead of two, greatly reducing the number of buttons in complex automations.

As mentioned above, these changes are purely cosmetic, for now! But this new dialog is the foundation of what’s coming next, and we cannot wait to present that to you once it finally lands.

Naming entities on your dashboard

A few releases ago, we gave the entity picker a big upgrade by adding more context so you could easily see where each entity belongs (May 2025 release). In this release, we’re bringing that same flexibility to your dashboards.

You can now choose how names appear on your cards: show the entity, device, area, floor, or even combine them. This gives you full control over how your dashboards look and feel. For example, in a dedicated section for a specific device, you might choose to display only the entity name to avoid repeating the device name on every card.

Of course, you can still set a custom name if you want complete control over the text shown.

And the best part? If you rename an entity or device, your dashboards will automatically stay in sync. No more manual edits needed; everything just updates itself.

Energy pie

We’ve added a new layout to the devices energy graph: “pie” 🥧. You can toggle between the regular bar chart and the new pie chart by clicking the icon in the top-right corner.

Doing this made the top-right corner of the other energy cards feel empty, so we used that space to display the total energy for the selected period. For example, if the date picker is set to today, the total solar energy for today will be displayed in the corner of the solar production graph card.

Progress for Home Assistant and Add-on updates

With this release, you can now track the progress of updates to Home Assistant and Add-ons (managed by the Supervisor)! The progress includes the stages of downloading and unpacking, so the time required will vary based on your internet speed, CPU performance, and system load. As a result, the progress is not reflected as perfectly linear, but it does still provide a good estimate of how far along the update is.

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:

• Actron Air, added by @kclif9
  The Actron Air integration allows you to control Actron Air air conditioning controllers in Home Assistant.

• Sunricher DALI, added by @niracler
  Integrate with Sunricher DALI, a platform for managing and monitoring DALI-based lighting systems.

• Fing, added by @Lorenzo-Gasparini
  The Fing integration provides network scanning, device detection, and presence monitoring capabilities using the Fing platform.

• Firefly III, added by @erwindouna
  Integrate with the Firefly III project, a free open source personal finance manager with full transaction management, budgets, categories, and reports.

• iNELS, added by @epdevlab
  Integrate with the iNELS smart home system to manage lighting, heating, and automation components for enhanced home control.

• Lunatone Gateway, added by @MoonDevLT
  Integrate with Lunatone Gateway, enabling control and monitoring of DALI lighting systems through Lunatone’s DALI gateway interface.

• Meteo.lt, added by @xE1H
  The Meteo.lt integration uses meteorological data from the Lithuanian Hydrometeorological Service (LHMT) to provide regional weather forecasts for locations in Lithuania.

• Nintendo Parental Controls, added by @pantherale0
  The Nintendo Parental Controls integration connects with Nintendo’s parental management service, allowing you to monitor and manage device usage and restrictions.

• OpenRGB, added by @felipecrs
  The OpenRGB integration allows unified control of RGB lighting across various hardware brands and devices through the OpenRGB project.

Noteworthy improvements to existing integrations

It’s 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:

• The SwitchBot integration now supports garage door openers. Thanks @zerzhang!
• @tr4nt0r added support for notifications to the Habitica integration. Nice work!
• The VegeHub integration now has support for switches to control actuators. Cool @Thulrus!
• The Portainer integration gained support for switches, buttons, and sensors, so you can control and monitor all your containers! Well done @erwindouna!
• The Volvo integration can now show the location of your car and has buttons to control it. We got @thomasddn to thank for that!
• ElevenLabs can now be used for speech-to-text. Thanks @ehendrix23!
• You can now control the LEDs of supported UniFi network devices! Thanks @Sese-Schneider!
• @barneyonline added binary sensors to the Yardian integration. Nice!
• You can now set the temperature of your 3D printer’s tool and bed with the OctoPrint integration. Thanks @AmadeusW!
• The Niko Home Control integration now also adds your scenes into Home Assistant! Thanks @VandeurenGlenn!
• Your Control4 climate devices (for example, thermostats) are now supported in Home Assistant. Thanks @davidrecordon!
• Support for controlling Growatt MIN/TLX inverters was added, and you can now enable grid charge! Thanks @johanzander!
• @hanwg added event entities to the Telegram bot integration. You can use these entities to more easily automate when you get a message, for example! Cool!
• The Xbox integration now has support for images! It shows an image of the game you are currently playing, the avatar, and the Gamerpic for yourself and your friends. Thanks @tr4nt0r!
• @AndyTempel added support for solar production forecasting to Victron Remote Monitoring, so you can now use it in the energy dashboard to see a forecast of how much solar energy you will produce today!
• The Shelly integration now supports climate and valve entities. Thanks @thecode!
• @starkillerOG improved the Reolink integration; it can now report bicycles and the type of person, vehicle, and animal. So you now know if a man or a woman is detected on your cameras. Great work!

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 a 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:

• London Underground by @HarvsG

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:

• Seven integrations reached platinum 🏆

  • APC UPS Daemon, thanks to @yuxincs
  • IMGW-PIB, thanks to @bieniu
  • LG WebOS TV, thanks to @thecode
  • Mealie, thanks to @andrew-codechimp
  • NextDNS, thanks to @bieniu
  • ntfy, thanks to @tr4nt0r
  • Volvo, thanks to @thomasddn

• Four integrations reached silver 🥈

  • 1-wire, thanks to @epenet
  • Ubiquiti airOS, thanks to @CoMPaTech
  • LetPot, thanks to @jpelgrom
  • Switcher, thanks to @thecode

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 no longer available as of this release:

• Vultr has been removed. The integration has not been working since the API v1 that it used was taken offline in September 2023.
• IBM Watson IoT Platform has been removed. On September 8, 2020, IBM announced the withdrawal of its support for the IBM Watson IoT Platform and successively discontinued all versions until September 30, 2022.
• Plum Lightpad has been removed. Their servers have been shut down, which made the integration non-functional.

Other noteworthy changes

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

• @thecode added group support for valves, so you can group multiple valves into one.
• Searching in data tables got a lot better; you can now search over multiple columns at once. Thanks @wendevlin!
• Energy graphs now show the total of the period in the top-right corner. Great addition, @MindFreeze!
• Thanks to @karwosts, you can now use images from any integration providing images for your dashboard background.

Improved logging efficiency

If you’re using the Home Assistant Operating System, we have some great news for you! We’ve made our logging system way more efficient. 🚀

You might not realize it, but all those Home Assistant logs you can find in Settings > System > Logs were actually being stored on your disk twice. 🙈

Home Assistant OS keeps all logs for everything, including Home Assistant itself, in a very efficient way, even across restarts! But on top of that, we were also writing them to a log file in your Home Assistant configuration folder.

That’s not ideal. It takes twice the disk space, but more importantly, it causes unnecessary wear on your storage medium, which means it will fail sooner. This is especially concerning if you’re using an SD card in, for example, a Raspberry Pi.

As of this release, we’ve stopped writing logs to the configuration folder. You can still view and download all logs from the Home Assistant settings page, just like before. We’ve adapted that page to read the logs from the OS directly instead.

The new Home Dashboard keeps getting smarter

Following the improvements introduced in the latest releases, this release makes the experience even smoother and more intuitive.

We’ve simplified and reorganized things:

• Suggested entities and favorites are now combined into a single, smart section, showing you what’s most relevant in one place.
• Areas are now grouped by floor, making it easier to browse and understand your home’s layout at a glance.
• The Lights, Climate, and Security views have been moved to their own dedicated dashboards, so you can access them directly under Settings > Dashboards. These dashboards now also include devices that aren’t assigned to any specific area, ensuring nothing is overlooked.

These improvements bring everything together more naturally, helping your Home Dashboard feel less like a setup and more like a true reflection of your home.

Patch releases

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

2025.11.1 - November 7

• Improve scan interval for Airthings Corentium Home 2 (@LaStrada - #155694)
• Remove @progress_step decorator from ZHA and Hardware integration (@puddly - #155867)
• Fix KNX Climate humidity DPT (@farmio - #155942)
• Truncate password before sending it to bcrypt (@cdce8p - #155950)
• Fix for corrupt restored state in miele consumption sensors (@astrandb - #155966)
• Handle empty fields in SolarEdge config flow (@tronikos - #155978)
• Fix SolarEdge unload failing when there are no sensors (@tronikos - #155979)
• Bump aioamazondevices to 8.0.1 (@chemelli74 - #155989)
• Fix Growatt integration authentication error for legacy config entries (@johanzander - #155993)
• Bump tuya-device-sharing-sdk to 0.2.5 (@epenet - #156014)
• Bump onedrive-personal-sdk to 0.0.16 (@zweckj - #156021)
• Fix the exception caused by the missing Foscam integration key (@Foscam-wangzhengyu - #156022)
• Bump intents to 2025.11.7 (@synesthesiam - #156063)

2025.11.2 - November 14

• Bump cronsim to 2.7 (@dgomes - #155648)
• Avoid firing discovery events when flows immediately create a config entry (@puddly - #155753)
• Remove arbitrary forecast limit for meteo_lt (@xE1H - #155877)
• Fix progress step bugs (@emontnemery - #155923)
• Make sure to clean register callbacks when mobile_app reloads (@TimoPtr - #156028)
• Bump pyportainer 1.0.13 (@erwindouna - #155783)
• Bump pyportainter 1.0.14 (@erwindouna - #156072)
• Log HomeAssistantErrors in ZHA config flow (@TheJulianJES - #156075)
• Bump aio-ownet to 0.0.5 (@jrieger - #156157)
• Fix MFA Notify setup flow schema (@abmantis - #156158)
• Update xknx to 3.10.1 (@farmio - #156177)
• Forbid to choose state in Ukraine Alarm integration (@PaulAnnekov - #156183)
• Fix set_absolute_position angle (@starkillerOG - #156185)
• Fix config flow reconfigure for Comelit (@chemelli74 - #156193)
• Bump pyvesync to 3.2.1 (@cdnninja - #156195)
• Fix Climate state reproduction when target temperature is None (@mib1185 - #156220)
• Foscam Integration with Legacy Model Compatibility (@Foscam-wangzhengyu - #156226)
• Bump pypalazzetti lib from 0.1.19 to 0.1.20 (@dotvav - #156249)
• Bump pySmartThings to 3.3.2 (@joostlek - #156250)
• Correct migration to recorder schema 51 (@emontnemery - #156267)
• Improve logging of failing miele action commands (@astrandb - #156275)
• Ituran: Don’t cache properties (@shmuelzon - #156281)
• tplink: handle repeated, unknown thermostat modes gracefully (@rytilahti - #156310)
• Check collation of statistics_meta DB table (@emontnemery - #156327)
• Fix support for Hyperion 2.1.1 (@antoniocifu - #156343)
• Update pyMill to 0.14.1 (@Danielhiversen - #156396)
• Prevent sensor updates caused by fluctuating “last seen” timestamps in Xbox integration (@tr4nt0r - #156419)
• Fix update progress in Teslemetry (@Bre77 - #156422)
• Bump pyvesync to 3.2.2 (@cdnninja - #156423)
• Fix lamarzocco update status (@zweckj - #156442)
• Add firmware flashing debug loggers to hardware integrations (@puddly - #156480)
• URL-encode the RTSP URL in the Foscam integration (@Foscam-wangzhengyu - #156488)
• Update Home Assistant base image to 2025.11.0 (@sairon - #156517)
• Bump pySmartThings to 3.3.3 (@joostlek - #156528)
• Update bsblan to python-bsblan version 3.1.1 (@liudger - #156536)
• Bump reolink-aio to 0.16.5 (@starkillerOG - #156553)
• Bump python-open-router to 0.3.3 (@joostlek - #156563)
• Bump ZHA to 0.0.78 (@TheJulianJES - #155937)
• Bump ZHA to 0.0.79 (@TheJulianJES - #156571)
• Fix sfr_box entry reload (@epenet - #156593)
• Fix model_id in Husqvarna Automower (@Thomas55555 - #156608)
• Add debounce to Alexa Devices coordinator (@chemelli74 - #156609)

2025.11.3 - November 21

• Cache token info in Wallbox (@hesselonline - #154147)
• Bump version of python_awair to 0.2.5 (@averybiteydinosaur - #155798)
• Fix args passed to check_config script (@tmonck - #155885)
• update methods to non deprecated methods in vesync (@cdnninja - #155887)
• Fix wrong BrowseError module in Kode (@charrus - #155971)
• Bump universal-silabs-flasher to v0.1.0 (@puddly - #156291)
• Reset state on error during VOIP announcement (@jaminh - #156384)
• Bump pyiCloud to 2.2.0 (@PaulCavill - #156485)
• Fix is_matching in samsungtv config flow (@FredrikM97 - #156594)
• Bump async-upnp-client to 0.46.0 (@edenhaus - #156622)
• Bump tplink-omada-api to 1.5.3 (@MarkGodwin - #156645)
• Fix missing description placeholders in MQTT subentry flow (@jbouwh - #156684)
• Fix missing temperature_delta device class translations (@jbouwh - #156685)
• Bump ohmepy and remove advanced_settings_coordinator (@dan-r - #156764)
• Fix blocking call in cync (@epenet - #156782)
• Lamarzocco fix websocket reconnect issue (@zweckj - #156786)
• Fix hvv_departures to pass config_entry explicitly to DataUpdateCoordinator (@Copilot - #156794)
• Bump aioautomower to 2.7.1 (@Thomas55555 - #156826)
• Bump pySmartThings to 3.3.4 (@joostlek - #156830)
• Bump universal-silabs-flasher to 0.1.2 (@puddly - #156849)
• Bump onedrive-personal-sdk to 0.0.17 (@zweckj - #156865)
• Bump aiounifi to 88 (@Sese-Schneider - #156867)
• Rework CloudhookURL setup for mobile app (@TimoPtr - #156940)
• Bump go2rtc to 1.9.12 and go2rtc-client to 0.3.0 (@edenhaus - #156948)
• Update frontend to 20251105.1 (@bramkragten - #156992)
• Throttle Decora wifi updates (@joostlek - #156994)

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 on 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:

• Changes to the recorder statistics API
• Device filter has been removed from target selector
• Service translations removed from WebSocket get_services and REST /api/services
• TemperatureConverter.convert_interval deprecation
• Update coordinator now allows retriggering

All changes

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

We’re delighted to welcome ELTAKO to the Works with Home Assistant program! ELTAKO’s robust relay switches have formed the blueprint for smart building and smart home control across Europe for decades – and happen to be the first Matter relays to join the program.

You may never have seen one of ELTAKO’s little blue devices before, and that’s the point. They usually sit quietly behind walls, furniture and in distribution boards, doing their jobs without interfering with interiors. Now, thanks to their joining the Works with Home Assistant program, you can bring these professional-level installations to your own smart set-up.

Out of the blue and into the open home

ELTAKO has been a well-known name in the German building trade and throughout Europe for more than 75 years. In fact, the name itself derives from ‘ELektrischer TAst-KOntakt’ (electrical push-button contact) in a nod to ELTAKO’s first impulse switch innovation that started it all back in 1949.

For those of us who haven’t been around quite that long, an impulse switch (also known as a latching or step relay) toggles a circuit on or off each time it receives an electrical pulse. Instead of requiring constant power, it ‘remembers’ its state until the next signal. As well as using less energy, this means it’s possible to control a single light or system from multiple switches without complex wiring – with obvious advantages for the smart home. So synonymous is the brand with this type of device that impulse switches are still referred to as ‘ELTAKOS’ by the professional electricians and engineers who use them.

Because of this innovative spirit, it’s perhaps no surprise that over the years ELTAKO has broadened its range to a full ecosystem of sensors, dimmers, and energy meters – all based on wired or wireless technologies, such as RS485, EnOcean, Modbus or DALI, which are built for longevity and local control, rather than cloud dependency.

True to that philosophy, ELTAKO has embraced open standards such as Matter, ensuring its products speak the same languages that support our mission to keep homes open, private, and locally controlled.

Devices

ELTAKO’s integration with Home Assistant starts with items from the 64 series, which was awarded the SmartHome Germany Award this year. This is the brand’s line that uses Matter over Wi-Fi, showing just how serious they are about interoperability moving forward.

We were also lucky enough to see the ELTAKO team at ISE Barcelona this year, and we’ll be catching up with them again at the Connectivity Standards Alliance (CSA) meeting in November, also in Barca. Since CSA certification is a must for brands joining the program, it’s great to see ELTAKO so engaged.

As always, all the devices below have gone through our rigorous certification process to ensure they meet our standards for performance, reliability and open-home compatibility.

What devices have been certified?

• ELTAKO Universal Dimming Actuator EUD64NPN-IPM (and the previous version here)
• ELTAKO Impulse Switch ESR64PF-IPM
• ELTAKO Impulse Switch ESR64NP-IPM
• ELTAKO Shading Actuator ESB64NP-IPM

These Matter devices that work over Wi-Fi are all about giving you freedom to control your current hardware – switch lights on and off and dim them automatically – without replacing it all. The shading actuator is particularly useful in continental Europe, where shutters are more common. It has a good energy-saving use case to reduce the need for air conditioning, since automatic shutters help keep your home cool in summer and warm in winter, potentially reducing utility bills. This also reflects ELTAKO’s wider focus on sustainability – from low-power devices to recyclable packaging and shipping materials.

In case you didn’t know, when using Matter devices with Home Assistant you have local control with no need for external internet for day-to-day operation. If you do want to access your dashboard while you’re away from home, using Home Assistant Cloud is a simple, secure, way to do this (and help fund Home Assistant’s development in the process!).

Professional quality, support for all

Like all brands within the Works with Home Assistant program, ELTAKO isn’t just adding our little blue logo to their little blue products – they’re joining our community. That means active engagement and shared expertise to help everyone get the best from their devices. Because ELTAKO’s products are built to professional standards, installation can sometimes require a qualified electrician – especially for wired set-ups. That’s where ELTAKO’s directory of system partners and specialists in many regions, as well as a tech support hotline, can help you find the installation advice you need, whether you’re a complete novice or electrical enthusiast.

With ELTAKO on board, we hope Home Assistant users will have further flexibility to explore new devices and experiment with different set-ups, as well as open up more ways to mix and match products to build a professional-standard smart home.

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 key 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 and with our certified Matter Integration. If you have another set-up 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 ELTAKO devices to the program?

A: Why not! We’re thrilled to foster a close relationship with the team at ELTAKO to work together on any upcoming releases, or add in further products that are not yet listed here. We’re really excited about what ELTAKO are doing with EnOcean and green power generally, but we haven’t tested or certified any of these products yet. We don’t have this protocol as part of the Works with Home Assistant certification (even if people are already using EnOcean in Home Assistant), and could explore how we certify these kinds of products.

Welcome to Voice Chapter 11 🎉, our long-running series where we share all the key developments in Open Voice. In this chapter, we will tell you how our assistant can now control more things in the home, in multiple languages at the same time, all while not talking your ear off. What’s more, our list of supported languages has grown again with several languages that big tech’s voice assistants won’t support. Join us for a deeper look at this voice chapter in our livestream on Wednesday, October 29. It’s been a couple of months, we’ve been building up our voice, and now have a lot to say, so let’s get to it!

Multilingual assistants

Our original goal for the Year of Voice back in 2023 was to “let users control Home Assistant in their own language”. We’ve come a long way towards that goal, and really broadened our language support. We’ve also provided options that allow users to customize voice assistant pipelines with the services that best support their language, whether run locally or in the cloud of their choice. But what if you speak two languages within your home?

For some time, users have been able to create Assist voice assistant pipelines for different languages in Home Assistant, but interacting with the different pipelines has either required multiple voice satellite devices (one per language) or some kind of automation trigger to switch languages.

Since even the tiniest voice satellite hardware we support is capable of running multiple wake words now, we’ve added support in 2025.10 for configuring up to two wake words and voice assistant pipelines on each Assist satellite! This makes it straightforward to support dual language households by assigning different wake words to different languages. For example, “Okay Nabu” could run an English voice assistant pipeline while “Hey Jarvis” is used for French.

Multiple wake words and pipelines can be used for other purposes as well. Want to keep your local and cloud-based voice assistants separate? Easy! Assign a wake word like “Okay Nabu” to a fully local pipeline using our own Speech-to-Phrase and Piper. This pipeline would be limited to basic voice commands, but would not require anything to run outside of your Home Assistant server. Alongside this, “Hey Jarvis” could be assigned to a different pipeline that uses external services like Home Assistant Cloud and an LLM to answer questions or perform complex actions.

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

Voice without AI

The whole world is engulfed in hype about AI and adding it to all the things — we’re not exactly quiet about the cool stuff we’re doing with AI. While powering your voice assistants with AI/LLMs makes them much more flexible and powerful, it comes at a cost: paying to use cloud-based services like OpenAI and Google, or pricey hardware and energy to run local models via systems like Ollama. We started building our voice assistant before AI was a thing, and thus it was designed without requiring it. We continue to make great progress towards delivering a solid voice experience to users who want to keep their home AI free — keeping AI opt-in only and not required are guidelines we follow.

Assist, our built-in voice assistant, can do a lot of cool things without the need for AI! This includes a ton of voice commands in dozens of languages for:

• Turning lights and other devices on/off
• Opening/closing and locking/unlocking doors, windows, shades, etc
• Adjusting the brightness and color of lights
• Running scripts and activating scenes
• Controlling media players and adjusting their volume
• Playing music on supported media players via Music Assistant
• Starting/stopping/pausing multiple timers, optionally with names
• Adding/completing items on to-do lists
• Delaying a command for later (“turn off lights in 5 minutes”)…
• …and more!

Want to include your own voice commands? You can quickly add custom sentences to an automation, allowing you to take any action and tailor the response.

The easiest way to get started is with Home Assistant Voice Preview Edition, our small and easy-to-start with Voice Assistant hardware. This, combined with a Home Assistant Cloud subscription, allows any Home Assistant system to quickly handle voice commands, as our privacy-focused cloud processes the speech-to-text (turning your voice into text for Home Assistant) and text-to-speech (turning Home Assistant’s response back into voice). This is all without the use of LLMs, and supports the development of Home Assistant 😎.

For users wanting to keep all voice processing local, we offer add-ons for both speech-to-text and text-to-speech:

• Whisper is a powerful speech-to-text system that comes in different sizes with varying hardware requirements
• Speech-to-Phrase is our speech-to-text system that trades flexibility for speed
• Piper is our fast neural text-to-speech system with broad language support

All of this together shows just how much can be done without needing to include AI, even though it can do some pretty amazing things. And we’re continuing to close the gap with the features highlighted in this blog post, including multilingual assistants, improved sentence matching, and the ability to ask questions from automations.

More intents

Intents are what connect a voice command to the right actions in Home Assistant to get something done. While the end result is often simple, such as turning on a light, intents are designed as a “do what I mean” layer above the level of basic actions. In the previous section, we listed the sorts of voice commands that intents enable, from turning on lights to adding items to your to-do list. Over the last three years, we’ve been progressively adding new and more complex intents.

Recently, we’ve added three new intents to make Assist even better. To control media players, you can now set the relative volume with voice commands like “turn up the volume” or “decrease TV volume by 25%”. This adds to the existing volume intent, which allows you to set the absolute volume level like “set TV volume to 50%”.

Next, it’s now possible to set the speed of a fan by percentage. For example, “set desk fan speed to 50%” or even “set fans to 50%” to target all fans in the current area. Make sure you expose the fans you want Assist to be able to control.

Lastly, you can now tell the kids to “get off your lawn” because your robot is going to mow it! Making use of the lawn_mower integration, your voice assistant can now understand commands like “mow the lawn” and “stop the mower”. Paired with the existing smart vacuum commands, you may never need to lift a finger again to keep things clean and tidy.

Ask question

Picture this: you come home from work and, as you enter the living room, your voice assistant asks what type of music you’d like to hear while preparing dinner. As the music starts to play, it mentions you left the garage door open and wants to know if you’d like it closed. After dinner, as you’re hanging out on the couch, your voice assistant informs you that the temperature outside is lower than your AC setting and asks for confirmation to turn it off and open the windows.

Surely you’d need a powerful LLM to perform such wizardry, right? With the Ask Question action, this can all be done locally using Assist and a few automations!

Within an automation, the Ask Question action allows you to announce a message on a voice satellite, match the response against a list of possible answers, and take an action depending on the user’s answer. While answers can be open-ended, such as a musical artist or genre, limiting the possible answers allows you to use the fully local Speech-to-Phrase for recognizing speech without an internet connection.

Improved sentence matching

Assist was designed to run fast and fully offline on hardware like the Raspberry Pi 4 for many different languages. It works by matching the text of your voice commands against sentence templates, such as “turn on the {name}” or “turn off lights in the {area}”. While this is very fast and straightforward to translate to many languages, it can also be inflexible, resulting in the dreaded “Sorry, I couldn’t understand that” or other errors.

Starting in Home Assistant 2025.9, we’ve included an improved “fuzzy matcher” that is much better at handling extra words or alternative phrasings of our supported voice commands.

The fuzzy matcher is pre-trained on the existing sentence templates, so we will be able to use it for all of our supported languages. However, this is initially only available for the English language and we’re working to determine the best way to enable this for other languages.

Non-verbal confirmations

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

Starting with Home Assistant 2025.10, Assist will detect if the 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 reminder that your voice command only affected the current area.

Non-verbal confirmations will not be used in voice assistant pipelines with LLMs, since the user may have specific instructions in their prompt, such as “respond like a pirate”, and we wouldn’t want to deprive you of a fun response, me mateys 🏴‍☠️.

Text-to-speech streaming

Large language models (LLMs) can be especially verbose in their responses, and we quickly realized that this exposed a weakness in Home Assistant’s text-to-speech (TTS) implementation. For most of its life, TTS in Home Assistant has required the full response to be generated before any audio can be played. This meant a lot of waiting for multi-paragraph LLM responses, especially with local TTS systems like Piper.

Fixing this required an overhaul of the TTS architecture to allow for streaming. Instead of waiting for the entire audio message to be synthesized before playing, we enabled TTS services within Home Assistant to work with chunks of text (input) and audio (output). As chunks of text are streamed in from an LLM, the TTS service can synthesize audio chunks and send them out to be played immediately.

To demonstrate the benefit of streaming, we asked an LLM to “tell me a long story about a frog” and timed how long it took to start speaking the (multi-paragraph) response. Without streaming, both Home Assistant Cloud and Piper took more than five seconds to respond! This is long enough to make you wonder if your voice assistant heard you 😄 With streaming enabled, both TTS services took about half a second to start talking back. A 10x improvement in latency!

New Piper voices

Piper, our homegrown text-to-speech tool, continues to grow with support for several new languages! These new voices were trained from publicly available voice datasets, and are available now in the Piper add-on:

• Daniela (Argentinian Spanish)
• Pratham, Priyamvada, Rohan (Hindi)
• News TTS (Indonesian)
• Maya, Padmavathi, Venkatesh (Telugu)

Want to know what the new voices sound like? You can listen to samples of every available Piper voice or even run Piper entirely within your web browser for free.

If your language is missing from Piper, or you don’t like the existing voices for your language, we’re always looking for volunteers to contribute their voices! Please contact us at voice@openhomefoundation.org

Conclusion

In the past three years, we’ve made great strides with Home Assistant Voice on both the hardware and software fronts. Users today have a wide variety of choices when it comes to voice: from fully local to using the latest and greatest AI to power their smart homes. The great thing about our experimentation with AI is that there are no investors looking for returns, fake money, or “rug-pulls”. We do everything for you, our community. We’re in this for the long haul, and want this all to be your choice, keeping you in full control of whether you want to use this technology or avoid the hype completely.

Much of the advanced work done on voice is only possible with the support of our community, especially those who subscribe to Home Assistant Cloud or anyone who has purchased our Home Assistant Voice Preview Edition (both great ways to get started with voice).

Today, we’re announcing that we will no longer be producing Home Assistant Yellow. Rest assured, it will continue to receive software support far into the future.

I’m Carl, Vice President of Commercial at Nabu Casa, the organization that builds and sells official hardware for the Open Home Foundation. I couldn’t be more proud of our hardware achievements over the past 12 months, including Voice Preview Edition and Connect ZWA-2 (including its cool new Wi-Fi and PoE experimental firmware).

Home Assistant Yellow was similarly groundbreaking at launch and helped fund Home Assistant’s development. However, for reasons I’ll explain below, the time has come to end production. This means that if you were considering buying a Home Assistant Yellow, you’ll need to act fast, as stock will not be replenished (check the Order Now button on the Home Assistant Yellow page to see if your local retailer still has stock).

Nabu Casa is now exploring what hardware could replace Home Assistant Yellow, so if you have any suggestions on what we should do next, please tell us in the comments! In the meantime, the good news is that there are already plenty of other great ways to run Home Assistant. For example, if you’re looking for hardware that’s both easy to start with and supports the Open Home Foundation, we’d recommend the Home Assistant Green.

A golden era

There is a long yellow brick road that brought us to today. All the way back in 2021, we announced Home Assistant Yellow (originally called Amber). It included some pretty unique features, including its built-in Zigbee or Thread adapter, optional PoE, and overall expandable approach. As it used the Raspberry Pi Compute Module platform, included GPIO, and had an NVMe slot, there were a lot of different ways you could upgrade it over time (including people being able to upgrade from CM4 to CM5, which was quite the speed bump 🏎️).

It wasn’t all smooth sailing with Home Assistant Yellow. We essentially launched the device in the middle of the great Pi shortage. It definitely complicated things for a time, but it all eventually stabilized. In late 2023, we launched Home Assistant Green, which became the easiest way to get started with Home Assistant. This new product led us to end the sale of Home Assistant Yellow devices that shipped with a CM4 already installed (called the Home Assistant Yellow Standard), which allowed us to focus the product line on the kit versions.

Small, but so much room for activities

Home Assistant Green continues to have strong sales, but Home Assistant Yellow sales have been naturally slowing down, as happens a couple of years into any product’s life. This month, it finally reached the point where it no longer made sense to have another production run, which ultimately pushed us to discontinue Home Assistant Yellow.

Technology changes, and small-form-factor computing has always moved fast. For instance, in the early days of Home Assistant, the community’s de facto recommendation was always the most recent Raspberry Pi device, but we’re seeing more people gravitate towards Mini PCs. We’re now exploring what we could build next for our power users, but we’re still some way off, so don’t wait if you need something today.

Software support continues

As long as it’s possible to run Home Assistant on Yellow, we will continue to provide builds. If you want living proof of this commitment, take our first hardware device: Home Assistant Blue. It ended production in 2022, but still receives new builds of Home Assistant, something that shows no signs of changing for a long time. We continue to streamline and make Home Assistant more efficient, as it’s our goal for you to run it on the hardware you have.

Say ‘ellow to the future

I’d just like to take a moment to thank everyone who bought a Home Assistant Yellow over the years, and for all the great feedback you shared with us. We’re sad to say goodbye to our trusty little expandable powerhouse, but it’s had a good run and we’re super proud of how far we’ve come. Also, we’ll soon be announcing the date of our next hardware product (not a computing device… but something very cool nonetheless), so stay tuned!

Last month, we launched the Home Assistant Connect ZWA-2, our take on the best possible Z-Wave adapter. Based on the reviews, it sounds like we hit the mark 😎. Today, we’re announcing a new, experimental firmware that allows you to do even more with the ultimate Z-Wave adapter.

I’m Keith, a Senior Hardware and Software Engineer at Nabu Casa, but you also might know me from my work on the ESPHome project. If you weren’t aware, Nabu Casa is the commercial partner of the Open Home Foundation, and the organization that helps build official Home Assistant hardware.

During the launch, one piece of feedback we often received was that people wanted more flexibility in where they could place Connect ZWA-2 in their home — often far away from their Home Assistant system. It was no easy feat (more on that below), but we were able to build a solution that allows you to put it anywhere you have a network connection.

This experimental firmware will allow you to not only leverage the Wi-Fi chip inside the Connect ZWA-2, but also use it with other hardware to facilitate the use of the much-requested PoE. 🎉 This new firmware is only possible because of the second-generation platform we built Connect ZWA-2 on, which is open by design, allowing you to tinker and extend the device you own. Every piece of Home Assistant hardware reflects Nabu Casa and the foundation’s philosophy of constant evolution, and the software it launches with is just the beginning. Whenever we think of a cool new capability, we will work together to add it.

If you want to start using your Connect ZWA-2 with Portable Z-Wave today, visit the brand new home for all the foundation’s web-based tools. Just be aware that this is experimental, and we recommend you read through this blog to understand how it works and its limitations. You can also watch the upcoming ESPHome livestream, where we’ll discuss this new tech in depth.

Getting started

Home Assistant Connect ZWA-2 connected to a Waveshare ESP32-S3-ETH

To get started using your Connect ZWA-2 over your local network, you can use one of the two following configurations:

• Wi-Fi - the new firmware will be installed on the Connect ZWA-2 and use its built-in Wi-Fi chip to communicate over your network.
• PoE - the new firmware will be installed on an external development board that supports Power-over-Ethernet (PoE); Connect ZWA-2 will use its stock firmware and will plug into this new device via USB.

First, before installing this new firmware, make sure to back up your Z-Wave network and ensure your Home Assistant instance is running version 2025.10.2 or later. Only after those steps should you use the toolkit website for Portable Z-Wave. The toolkit’s wizard will walk you through the whole process of installing and connecting your device to your network. When the installation is complete, it should join your network and be discovered by both the ESPHome and Z-Wave integrations in Home Assistant.

This firmware has proven to work well in our lab and home environments, but the real world is a different place; your local network and Z-Wave network might behave differently. For this reason, we’re seeking your feedback. If you try it out, please let us know about your experience – good or bad, brief or long-winded – by leaving a comment below. We’re eager to know how and where we can improve it!

The Portable Z-Wave experiment

Before we launch any of our hardware products, we try to get our pre-production batch to as many testers as possible – most are hobbyists and tinkerers from the community, and of course, the first thing they tend to do is get out the screwdriver and open it up (to be fair, it’s designed to be easy to open — no glue, no clips). When looking at the insides of Connect ZWA-2, they were instantly greeted with an ESP32 chip, and were equally excited and confused. It was initially included just as a USB controller, and yes, an ESP32-S3 is a bit overkill for this specific task, but we wanted to give the device room to grow. This brings us to the experiment we are sharing with you today…

Making things mesh

When you use a Z-Wave adapter with Home Assistant, which relies on the Z-Wave JS add-on, they use USB to communicate via a specialized Z-Wave serial protocol. And yes, it is technically possible to run this Z-Wave serial protocol over your network (serial-over-IP), but our testing reveals that it’s not as reliable or as easy as we’d like. Some parts of the Z-Wave serial protocol are latency (delay) sensitive, specifically the acknowledgment of Z-Wave packets. If your network is busy and decides to take its sweet time with one of those critical packets, your Z-Wave device’s connection can time out and fail. This can stall Z-Wave device communication, or even completely break it.

For Z-Wave to work over a network, we need to address the latency-sensitive parts on the actual device; everything else can be forwarded over the network. This is where ESPHome steps in: it’s the open source software for network-capable microcontrollers that runs on ESP32 devices. We built an ESP32 into the Connect ZWA-2, and it has the horsepower (and Wi-Fi antenna) to handle this task.

To help make this all possible, we added Z-Wave support to ESPHome, allowing it to talk to Z-Wave chips. We then added the ability for Home Assistant and Z-Wave JS to communicate with Z-Wave adapters via ESPHome. As this work is open source, it shouldn’t be limited just to our Connect ZWA-2. Theoretically, it should be able to work with any certified Z-Wave adapter connected to an ESP32. However, before we look at supporting other adapters, we want to ensure that it’s stable when running on the Connect ZWA-2.

Home Assistant connected to the ZWA-2 via its integrated Wi-Fi chip.

Home Assistant connected to the ZWA-2 via the PoE module.

ESPHome handles serial message acknowledgments internally, then leverages its API (specifically its Protobuf implementation) to send the messages over the network more reliably than serial-over-IP. Even if your home network is bogged down by some spikes in traffic, ESPHome will have you covered, keeping your Z-Wave network stable. That’s not to say this has no impact on performance, but it may be less than you think – or can even notice!

Performance

Wi-Fi is very convenient, but the million-dollar question is: how will it impact your Z-Wave network? To find out, we ran some benchmarks to see how Portable Z-Wave stacks up to its USB counterpart.

Compared to a direct serial (USB) connection, a data packet will take longer to travel between Home Assistant/Z-Wave JS and your Z-Wave network when routed through your local network. On a network with only a low to moderate workload, the additional delay is very small and is generally not noticeable. That said, if your network is heavily stressed or the Wi-Fi signal is poor, you should expect packets to take longer to move around, which can lead to a perceivable delay. It can still control your lights and other devices, but it may be a bit slower. Here are some numbers illustrating the typical latency that we were able to achieve across our test environments:

Your results will likely differ somewhat, especially in less ideal conditions and environments. For instance, if you place your Connect ZWA-2 in a spot with really poor Wi-Fi connectivity, you might notice devices not reflecting their actual state or other buggy behavior. Avoid using VPNs or other complex network routing or configuration, as that will add latency. Also, don’t worry about Wi-Fi interfering with your Z-Wave network, as they operate on totally different radio frequencies that don’t interact. I think with a healthy dose of common sense, you can find a great spot that gets both great Wi-Fi connectivity while nicely optimizing your Z-Wave network.

Thanks

This project was brought to you by a collaboration between Nabu Casa and the people below from the Open Home Foundation. None of this would be possible without the support of Home Assistant Cloud subscribers and those who care about Z-Wave and have purchased the Home Assistant Connect ZWA-2. Thank you!

Thanks to Dominic, founder of Z-Wave JS, for quickly jumping in on this project, adding support to Z-Wave JS, and building the browser installation tooling.

Thanks to Nick and Jesse for their support with the ESPHome implementation.

Thanks to Steven for making the new Open Home Foundation toolbox website to allow easy installation of the experiment.

FAQs

Q: Is the Portable Z-Wave experiment limited to the Home Assistant Connect ZWA-2?

A: Theoretically, it should work with other Z-Wave adapters, but thus far we have only tested it with the ZWA-2. The code is part of ESPHome 2025.10, Home Assistant 2025.10.2, and Z-Wave JS v15.15.0. We chose Home Assistant Connect ZWA-2 as the first device with support since it already contains an ESP32-S3. If you’d like to try it out with your favorite Z-Wave adapter, you should start by taking a look at our ESPHome configuration for the ZWA-2 (all that should need changing are the vendor and product IDs to match the Z-Wave adapter).

Q: Is the Portable Z-Wave experiment limited to Home Assistant?

A: No. It is made to work directly with Z-Wave JS. If you use Z-Wave JS v15.15.0, either standalone or with another smart home platform, you are able to use it, too! Configure Z-Wave JS to connect to esphome://<IP OF THE ZWA-2>.

Q: Can I use Ethernet instead of Power-over-Ethernet?

A: Yes. Use a Power-over-Ethernet injector in combination with the Waveshare ESP32-S3-ETH board.

Works with Home Assistant is opening its doors to another new partner who is bringing the first Garage Door Openers and Alarm Panel to the program, all of which are using ESPHome under the hood. Konnected are well known for their devices that let you retrofit new smarts into the devices you already have, allowing you to use them in Home Assistant and keep them working longer.

Getting Konnected

Konnected have been well-known in the Home Assistant community, as they’ve been active members for years. As members of the community, they know how hard it can be to connect the devices that are already built into your home, whether they’re smart or not. That’s why Konnected’s first product was their drop-in replacement alarm panel boards, which allow you to take decades-old wired alarm systems and add them into Home Assistant.

Another challenge the community was facing was garage door openers (GDOs), especially cloud-based openers. In the early days of Home Assistant, the community figured out the APIs for these providers and controlled them that way. Some manufacturers noticed this and put barriers up blocking people from controlling the devices they own, claiming it as “unauthorized usage” 🙄.

The community was naturally incensed, and did what tinkerers tend to do when a cloud gets in their way — they began tinkering with hardware. A community emerged to take back control of these devices, starting with projects like ratgdo, which Konnected used as a base for their work. Today, because of these projects, there are multiple great open source tools to control a large number of these GDOs, ranging from DIY schematics to finished controllers. Konnected has an open source solution which works locally, as well as having the form factor and safety standards to match. Even better, Konnected devices are available in over 60 countries.

For anyone who has used Konnected for quite some time, you’ll notice that they had their own integration, which has now been deprecated in favor of the ESPHome firmware, so that it’s always straightforward to find (or build) the firmware you need. They even publish all their code on GitHub 👏, which allows the community to help them fix issues and add features.

Konnected is another example of ESPHome (a project from the Open Home Foundation) fostering an entirely new ecosystem of Open Home projects. It works fully locally, and it’s perfect for tinkerers, allowing you to build DIY smart home devices yourself (get started with one of our ready-made projects). Konnected also have a thriving community of their own if you have questions or comments.

Creators can also use it to make pre-built, plug-and-play products that give users a really seamless experience. Devices are easily discovered and added to your Wi-Fi network and Home Assistant, along with a one-click update within Home Assistant. To learn more about how Konnected uses ESPHome, look out for Nate on the next ESPHome live stream on October 14!

Remember, the development of projects like ESPHome from the Open Home Foundation is supported by Home Assistant Cloud subscribers and anyone who purchases Home Assistant hardware. While all of Konnected’s devices work locally, if you’re interested in remote access, allowing you to keep tabs on your home’s security when you’re out and about, check out Home Assistant Cloud.

Devices

The Konnected Smart Garage Door Opener blaQ

For anyone new to the Works With Home Assistant program, it’s a way for us to formally certify devices that have been tested by our team, and help you know what works great out of the box with Home Assistant. Any company joining also commits to providing long-term support and firmware updates. Works With Home Assistant is operated by the Open Home Foundation, and the support of Home Assistant Cloud subscribers funds this work. These items were all tested by members of the ESPHome team to see exactly how they function in their own homes.

The Konnected certified devices are listed below:

• Konnected Smart Garage Door Opener blaQ
• Konnected Smart Garage Door Opener White (v2)
• Konnected Alarm Panel Pro

Let’s Konnect

A nice benefit of retrofitting your old wired security system is not needing to maintain loads of battery-powered sensors 🪫. The Alarm Panel Pro has the ability to connect 12 zones (security speak for individual or joined up sensors), it also allows you to connect keypads and sirens, and includes 12V power for the devices that need that. It’s highly customizable, and there’s also plenty of support available if you need help with installation. You can power it using 12V or Power-over-Ethernet, or both! The Alarm Panel Pro is designed to be always-on, and they’ve designed it to consume very little power. This also allows it to easily run for hours on their backup battery.

You’ll also probably be wondering why there are two different variants of the garage door openers, and that’s because each supports a different set of manufacturers. There is a wizard to help you figure out which variant will work with your opener. Between the Konnected GDO blaQ and White, you get support for some of the biggest manufacturers out there, including Chamberlain, LiftMaster, Craftsman, Merlin, Genie, Stanley, and more.

Even with the Konnected controlling your garage door opener, you’re still able to use the included remote or the original manufacturer’s app (if you like that kind of torture). The GDO White features a built-in optical laser sensor that detects whether your garage door is open or closed. The GDO blaQ offers control over the opener’s light and lock, and can even partially open the door (for openers that support these features).

As we mentioned at the top, it’s great to have more products added to the program that help people get the most out of the things they already own. A big part of the Open Home Foundation’s mission is sustainability in the smart home, and Konnected are helping our community get longer lasting use of their existing security and garage door systems.

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 has not yet been added to the testing schedule, 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 Home Assistant Green Hub with the ESPHome integration. If you have another set-up 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 Konnected devices to the program?

A: Why not! Konnected are also looking to do some exciting things with Matter soon, so we’re excited to work together on any upcoming releases or add in further products that are not yet listed here.

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