Home Assistant 2026.8! 🎉

Hi, I’m Ashley, the Technical Program Manager at the Open Home Foundation. With Frenck taking a well-deserved break, Bram and I are teaming up to handle things this time around.

We have been working on a lot over the past few weeks, and I’m excited to share some of what we have done for this release!

If there’s one thread tying this release together, it’s a direction we care about: making Home Assistant something you don’t need to be technical to use. This release is another step along that path.

Enjoy the release!

- Ashley

• Making Home Assistant more approachable
• The same Home Assistant, minus the magic number
  • Your current setup keeps working
  • Want to change the port? We’ve got you covered
  • What this means for YAML
• Less “advanced”, more approachable
  • Describing the feature, not the user
  • Just Tools, no developer required
• Home Assistant Cloud, now easier to explore
• Your entity IDs, your choice
• A cleaner way to handle your devices
• We can’t stop adding triggers and conditions
• 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
  • Tell us how setup went
  • A roomier template editor
  • Taps that land where you mean them
  • A combined battery level you can trust
  • Search your media
  • Find your favorite cards faster
  • Z-Wave lock credentials, properly managed
  • And a few more
• Patch releases
  • 2026.8.1 - August 7
• 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 @frenck and @bramkragten who helped write the release notes this release. Also, @piitaya, @RaHehl, and @farmio for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️

Making Home Assistant more approachable

One of the directions we care about most for Home Assistant is making it simpler to pick up and use, without compromising on capability. It’s something we have been working toward for a long time, and it runs through our roadmap and goals for this year. We cannot do it overnight though, so we keep listening to your feedback to make sure we are fixing the things that actually get in your way. If there is something you would like to see, we would love for you to weigh in. Every comment helps shape what comes next.

This release brings together some of that work. It may never be truly finished, and that is fine, but it is something we hold close: the more people who can use Home Assistant, whatever their technical ability, the better.

The same Home Assistant, minus the magic number

Ever wondered why the address for your own home has a random number stuck on the end? So did we. For years, reaching Home Assistant meant remembering to add :8123 to the address, a little piece of technical trivia that everyone simply had to learn. This release starts to put that right.

New installations of “Home Assistant OS”Home Assistant OS, the Home Assistant Operating System, is an embedded, minimalistic, operating system designed to run the Home Assistant ecosystem on single board computers (like the Raspberry Pi) or Virtual Machines. It includes Home Assistant Core, the Home Assistant Supervisor, and supports apps. Home Assistant Supervisor keeps it up to date, removing the need for you to manage an operating system. Home Assistant Operating System is the recommended installation type for most users. now use a normal web address by default, with no number to add on the end. You reach your home the same way you reach any website. Nothing extra to remember, nothing extra to type.

Your current setup keeps working

If you are already running Home Assistant, nothing changes and there is nothing you need to do. This only affects new installations of Home Assistant OS. Your existing installation is completely unchanged, keeps the exact port it has always used, and keeps working just as before. If everything works today, the simplest thing is to leave it exactly as it is.

Want to change the port? We’ve got you covered

You do not have to change anything, but if you would like the cleaner address, or need to change the port for another reason, you can now do it yourself from the interface. The same screen also holds a few more options, like choosing which network connection Home Assistant listens on and setting trusted proxies, for the setups that need them.

Changing something as fundamental as the port your home lives on can feel nerve-wracking, so we made it hard to get stuck. When you change the web server settings, Home Assistant applies the new configuration and then waits for you to confirm everything still works. If you do not confirm within five minutes, it assumes something went wrong, puts your previous settings back, and restarts. And if the new settings cannot be applied at all, it falls back right away. So if you ever lock yourself out with the wrong setting, you do not have to do anything: wait a few minutes, and Home Assistant returns you to where you were.

What this means for YAML

If you currently set up the web server in YAMLYAML is a human-readable data serialization language. It is used to store and transmit data in a structured format. In Home Assistant, YAML is used for configuration, for example in the configuration.yaml or automations.yaml files. [Learn more], you do not need to change anything. The first time you start Home Assistant after updating, your settings move into the interface for you, and you manage them there from then on. You might also see a repair appear, just to let you know your settings were imported; it can point you to tidying up the old YAML if you like, but nothing breaks either way.

Less “advanced”, more approachable

A word comes up around Home Assistant a lot: advanced. But what does it actually mean, and who gets to decide what counts as advanced and what does not? Too often it is a label that quietly tells people a feature is not for them. We want Home Assistant to be approachable for everyone, so this release removes some of that language.

Describing the feature, not the user

The clearest place to start is the words themselves. Labels like advanced and expert were dotted around Home Assistant. Words like these can be discouraging: they suggest a feature is not for you and steer you away from trying it, even when it is perfectly approachable. This release removes that wording in around 43 places, across the app, its documentation, and the companion apps. None of these features changed. Instead of rating your skill, the wording now simply describes what each one does.

A big thank you to everyone who helped comb through and clean this up! 👏

Just Tools, no developer required

In the same spirit, Developer Tools is now simply Tools. It has always been a useful spot for everyone, whether you are checking the stateThe state holds the information of interest of an entity, for example, if a light is on or off. Each entity has exactly one state and the state only holds one value at a time. However, entities can store attributes related to that state such as brightness, color, or a unit of measurement. [Learn more] of your “devices”A device is a model representing a physical or logical unit that contains entities., testing a templateA template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more], or reloading part of your setup, and you never needed to be a developer to use it. The shorter name matches how people actually use it, and feels a little friendlier to open.

Home Assistant Cloud, now easier to explore

Home Assistant Cloud by Nabu Casa is how many people add remote access, fast and private voice, encrypted backupsHome Assistant has built-in functionality to create files containing a copy of your configuration. This can be used to restore your Home Assistant as well as migrate to a new system. The backup feature is available for all installation types. [Learn more], and more to their home, all while supporting the project at the same time. Until now, everything it offers lived on a single long page of switches and settings. This release gives that page a proper redesign.

The main page is now a clean overview. Each feature (remote access, backups, voice assistants, the companion app, and more) has its own space, so you can see what you have turned on at a glance. The settings for each one move onto their own page, which keeps the overview tidy and makes every feature easier to understand on its own.

The bigger change is for anyone just getting started. There is now a guided setup that walks you through Home Assistant Cloud step by step, instead of leaving you to find your way around a wall of options. If it is not a good moment, you can put it off and pick it up again later.

A big thank you to @klejejs for this redesign!

Your entity IDs, your choice

Behind every deviceA device is a model representing a physical or logical unit that contains entities. and sensorSensors return information about a thing, for instance the level of water in a tank. [Learn more] sits an entity ID, a short name such as light.kitchen_ceiling that your automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more], scriptsScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more], and dashboards use to refer to it. Most of the time they look after themselves. But when you do want them neat and consistent, you should be the one deciding how they read.

Some earlier work looked at building entity IDs automatically from the areaAn area in Home Assistant is a logical grouping of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage. [Learn more] a device belongs to. Your feedback told us this suited some people but not everyone. So this release takes a more flexible route and puts you in charge: you can rename an entity ID yourself, and control how it is ordered, so your 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] follow whatever naming pattern makes sense to you.

Thanks to @arturpragacz and @piitaya for this work.

A cleaner way to handle your devices

Home Assistant is changing how it keeps track of your devices behind the scenes. Until now, if one physical deviceA device is a model representing a physical or logical unit that contains entities. was set up through two different integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more], Home Assistant merged them into a single device. Details that can only hold one value, such as the model or serial number, could then clash. From this release, each integration keeps its own device entry, so nothing gets collapsed together.

When you update, any devices that were merged this way are separated automatically, and their 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] move to the right device for you. Most people will not notice a thing. In the rarer cases where a device was set up through more than one integration, you might see it appear twice, once per integration, and Home Assistant may raise a repair to let you know.

There is nothing you need to do. Your automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] and scriptsScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more] keep working, because Home Assistant still sends actions to the right devices after the split. The only things that might need a second look are automations that point to a device by its ID directly, or the occasional unusual setup. If a repair appears, just follow it.

This is groundwork for more flexible device handling we are building toward over the coming months, so think of it as a step along the way rather than the finished picture.

If you build a custom integrationA custom integration is an integration that has been created by someone from the Home Assistant community and has been published for others to use at their own risk. Custom integrations are not supported by the Home Assistant project. They are not reviewed or tested by the Home Assistant development team and thus may negatively impact the stability of your Home Assistant instance. An example of a custom integration is the Spook integration., most need no changes at all. If yours works with device details directly, the developer blog walks through what changed. There is no rush: the previous approach keeps working for now, so you have plenty of time.

Thanks to @emontnemery for this work.

We can’t stop adding triggers and conditions

Last release, purpose-specific triggers and conditions became the friendlier way to build automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more]: you describe the moment you care about, like when the front door opens, instead of piecing it together from the technical parts underneath. This release adds two more of them.

Vibration now has conditions to match its triggers. On top of reacting the moment vibration starts or stops, you can check whether something is vibrating (or not) as part of a bigger automation, for example, only sending a “laundry is done” message once the washing machine has actually stopped shaking.

Moon gains a trigger and matching conditions. You can start an automation the moment the moon enters a new phase, or check the current phase as part of a bigger automation. Point it at the full moon, the new moon, or any change of phase, and let your home take it from there, whether that is mood lighting, a reminder, or just a bit of fun. 🌙

Thanks, @nielsrowinbik!

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:

• Dyson Infrared, added by @elax46
  Control your Dyson fans through any infrared transmitter you already have set up in Home Assistant. Because the connection only goes one way, Home Assistant shows the last command you sent rather than the fan’s live state.

• Fuelprices.dk, added by @MTrab
  Track current fuel prices from Danish fuel companies in Home Assistant. The integration pulls prices from the Fuelprices.dk service and creates a sensor for each product you select at a station, so you can watch prices and build automations around them.

• Gatus, added by @TN-1, launching at 🥈 silver quality
  Bring the health of your services into Home Assistant from your Gatus monitoring instance. Each monitored endpoint shows up as a binary sensorA binary sensor is an entity that reports one of two mutually exclusive states, on or off. The device class determines how those states are labeled in the UI. For example, open/closed for a door or detected/clear for motion. [Learn more], so you can put service status on a dashboard or trigger automations when something goes down or comes back up.

• GeoSphere Austria Warnings, added by @tklecka
  Bring official weather warnings for Austria into Home Assistant from GeoSphere Austria (formerly ZAMG), the national weather service. Warnings are issued per municipality and cover events like storms, heavy rain, snow, black ice, thunderstorms, heat, and cold, so you can get notified or trigger automations when the warning level rises.

• Google Health, added by @allenporter
  Bring your health and fitness data into Home Assistant from Google Health and the Fitbit Web API. After you connect your Google account, you get sensors such as steps, distance, weight, and resting heart rate, and it can run alongside the existing Fitbit integration.

• Harbor Sleep, added by @Lash-L
  Keep an eye on your Harbor Sleep baby monitor from Home Assistant. The integration connects to the device on your local network and exposes sensors like temperature, Wi-Fi strength, and stream quality.

• Harman Luxury Audio, added by @sbesh91
  Control network streamers built on the Harman Luxury Audio platform, such as the Arcam Radia ST5 and ST60, and equivalent JBL and Mark Levinson streamers. The integration talks to the device directly on your local network, so no cloud account is required.

• Karakeep, added by @sli-cka
  Connect your self-hosted Karakeep bookmarking service to Home Assistant and keep track of your bookmark statistics. Karakeep helps you save, organize, and tag links, notes, and images, and this integration surfaces those numbers as sensors.

• LED Infrared, added by @tr4nt0r
  Control LED lights through any infrared emitter you already have set up in Home Assistant. It supports many branded and unbranded bulbs and strip controllers that use generic infrared remotes. Communication is one-way, so the integration uses assumed states.

• LiteLLM, added by @luismalves
  Use a LiteLLM proxy as a conversation agent in Home Assistant. LiteLLM puts a single OpenAI-compatible API in front of many model providers, so you can reach almost any model through one endpoint, hosted or self-hosted. Home Assistant creates a conversation agent for each model you configure.

• llama.cpp, added by @allenporter
  Use a local llama.cpp server, or any OpenAI-compatible endpoint, as a conversation agent in Home Assistant. You can set up several agents, each with its own model and instructions, and keep everything running on your own hardware.

• Lyngdorf, added by @fishloa, launching at 🥈 silver quality
  Control Lyngdorf audio processors and amplifiers from Home Assistant, including power, volume, source selection, and sound modes. The integration keeps in sync with the device over your local network.

• Midea, added by @chemelli74
  Bring devices that use the Midea protocol, such as air conditioners and air purifiers, into Home Assistant. The integration provides information on the connected devices and lets you control their main features.

• NeoPool, added by @svasek, launching at 🥈 silver quality
  Monitor and manage pool controllers built on the NeoPool system, originally from Sugar Valley and sold under many brands like Hidrolife, Aquarite, and Oxilife. It talks to your controller locally over Modbus TCP, exposing water chemistry, filtration, and hydrolysis data with no cloud needed.

• ScorpionTrack, added by @Herbertmt978, launching at 🥈 silver quality
  Follow vehicles shared through a public ScorpionTrack location-share link on your Home Assistant map. The integration reads the shared vehicle feed and creates a device trackerDevice trackers are used to track the presence, or location, of a device. [Learn more] for each vehicle, without needing your private account credentials.

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 keep getting better too. Here are some of the noteworthy improvements this release:

• Shelly now supports Enhanced Security, the HTTPS-only mode on firmware 2.0 for gen2 and newer devices, and added support for Shelly circuit breakers, with on/off control plus output-state and safety-switch sensors. Thanks, @bieniu and @thecode!
• Reolink gained pre-siren entities and a motion device class on its AI-detection binary sensors. Thanks, @starkillerOG and @abmantis!
• Overkiz added window and tilt binary sensors for contact sensors, boost and drying-duration numbers for the Atlantic electrical towel dryer, and support for the Somfy Thermostat PRO. Thanks, @iMicknl!
• SwitchBot added support for the Candle Warmer Lamp and the RGBIC Neon Rope Light, plus fan and select controls for the Standing Fan. Thanks, @Onero-testdev!
• Roborock got plenty of love for the Q10, with a do-not-disturb switch, switch entities, a map image, and a volume control. Thanks, @lboue and @tubededentifrice!
• Whirlpool added an oven light, an oven cook-mode select, and an oven target-temperature number. Thanks, @matthewdias and @bdlcalvin!
• MQTT gained an infrared platform, so you can send infrared commands over MQTT. Thanks, @jbouwh!
• KNX got a whole set of improvements. Button and notify entities can now be configured from the interface, the KNX panel gained a Send telegram dialog (keyboard shortcut s), plus a datapoint type (DPT) reference and a device view for your project data. On top of that, all KNX entities now restore their state after a reload or restart. Thanks, @farmio!
• Enphase Envoy added ACB battery sensors, along with sleep and wake controls. Thanks, @genestealer!
• MELCloud gained on/off control, an operation-mode select, and a flow-temperature number for air-to-water heat pump zones. Thanks, @imilchev!
• MELCloud Home added energy-consumption reporting and a number platform. Thanks, @erwindouna!
• Portainer added an update platform and container health status. Thanks, @erwindouna!
• Mikrotik gained sensor, button, and update platforms. Thanks, @chemelli74!
• Imou added switch and sensor platforms. Thanks, @Imou-OpenPlatform!
• Fronius added a binary sensor for backup mode. Thanks, @farmio!
• OpenAI Conversation now supports GPT-5.6. Thanks, @Shulyaka!
• WiiM added multi-room grouping and metadata synchronization. Thanks, @Linkplay2020!
• SMLIGHT added Bluetooth proxy support and an infrared receiver for SMLIGHT Ultima devices. Thanks, @tl-sl!
• Vizio added command aliases for its remote. Thanks, @raman325!
• Tesla Wall Connector added an option to switch total power calculation between single-phase / split-phase and three-phase electrical service, along with vehicle current and Wi-Fi signal sensors. Thanks, @sarabveer!
• Teslemetry added control for seat coolers. Thanks, @Bre77!
• Tessie added a navigation-destination text entity. Thanks, @Mattheinrichs!
• Gardena Bluetooth added tank pressure and water temperature sensors. Thanks, @icereed!
• Duco added ventilation temperature sensors. Thanks, @ronaldvdmeer!
• Victron BLE added support for Orion XS and inverter devices. Thanks, @rajlaud!
• OMIE added an action to get prices for a specific date. Thanks, @abmantis!
• Ecowitt added soil conductivity sensor support. Thanks, @GSzabados!
• Steam added an image platform, plus new Last online, Level, and Now playing sensors. Thanks, @tr4nt0r!
• LG Infrared added support for LG air conditioners. Thanks, @Dr-Blank!
• UniFi Protect now supports the USL smart sensors (USL Entry, USL Environmental, and USL GlassBreak) on UniFi Protect 7.2 and newer, and cameras gained Motion detection, Smart detection, and Sound detection event entities that fire for any detection the camera reports, such as a person, a package, or barking, with the detected type as an attribute. Thanks, @RaHehl!

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 🏆

  • Anthropic, thanks to @Shulyaka
  • SMLIGHT SLZB, thanks to @tl-sl

• 1 integration reached gold 🥇

  • Nobø Ecohub, thanks to @oyvindwe

• 5 integrations reached silver 🥈

  • Dropbox, thanks to @bdr99
  • Kiosker, thanks to @Claeysson
  • OpenWrt (luci), thanks to @kristbaum
  • STIEBEL ELTRON, thanks to @ThyMYthOS
  • WattWächter Plus, thanks to @smartcircuits

• 2 integrations reached bronze 🥉

  • Midea ccm15 AC Controller, thanks to @ocalvo
  • Netatmo, thanks to @cgtobi

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:

• AquaLogic, done by @j-mutter
• OpenWrt (luci), done by @kristbaum

Farewell to the following

Time for a little cleaning, and no, we did not wait for spring! The following “integrations”Integrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] are no longer available as of this release:

• Permobil has been removed. Permobil deprecated the API it relied on, so the integration could no longer retrieve any data, and there is no replacement available.
• Volvo On Call has been removed. If you have a supported Volvo, set up the newer Volvo integration instead.

Other noteworthy changes

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

Tell us how setup went

If you have set up Home Assistant recently, you might notice a short, optional survey asking how your first experience went. It is entirely up to you, and every response helps us make getting started smoother for the next person. Thank you to everyone who shares their thoughts! 💛

A roomier template editor

The template tool in Tools is where you try out “templates”A template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] and watch the result update as you type. This release gives it a more comfortable layout: the editor and the result now sit in a split view you can drag to resize, and you can switch between side by side and stacked, whichever suits what you are working on. Your choice is remembered for next time.

Thanks, @maartenla!

Taps that land where you mean them

On the picture elements card, a tap could trigger the element next to the one you meant, or hit nothing at all, and some elements could not be tapped. Taps now go to the nearest icon or label, so every element can be reached, and tapping a label’s text always triggers that label. Thanks, @RaHehl!

A combined battery level you can trust

If you track more than one battery in the energy dashboard, you can now give each one a capacity. The combined state of charge is then weighted by size, so a small full battery and a large empty one no longer average out to a misleading number. Batteries without a capacity set keep using the plain average, so nothing changes unless you want it to. Thanks, @MindFreeze!

Search your media

Browsing for the right song, photo, or film used to mean clicking through folder after folder. Now, integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that provide media can offer search right in the media browser, so you type what you are looking for and jump straight to it.

What you can search depends on the media source. Immich, for example, gained a smart search that finds photos by what is actually in them rather than by their filename, and Overseerr lets you search for and request movies and shows without leaving Home Assistant.

Thanks, @zweckj, @mib1185, and @felixschndr!

Find your favorite cards faster

Your most-used cards are now easier to find. In the card picker’s “By Card” tab, you can now mark the cards you use most as favorites using the icon in the corner of each card. Favorited cards float to the top of the section, so if you reach for the same card again and again while building similar dashboards, it’s always right there waiting for you. Tap the icon again to remove a card from your favorites.

Thanks, @piitaya, @laupalombi, and everyone who suggested this at a Release Party!

Z-Wave lock credentials, properly managed

Managing who can unlock your Z-Wave lock just got a lot more capable. Powered by Z-Wave JS’s new Access Control API, the Z-Wave JS app 1.6.0 brings a heavily revised interface: every supported lock now gets a dedicated Access Control tab. For now, this lives in Z-Wave JS UI rather than in the Z-Wave panel in Home Assistant.

Users, their credentials, and a full audit trail, all in one place.

Depending on what your lock supports, you can now give each user several credentials of more than one type, so the same person can have a PIN and a fingerprint, or multiple of both. New credentials can be learned on the lock itself: start the enrollment from the interface, then present the finger or type the PIN. There is also an audit log of every change, admin code management for locks that use one, and the ability to move credentials between users or delete them in bulk.

Update the Z-Wave JS app to 1.6.0 or later, then open Z-Wave JS UI to find the new tab. Thanks, @AlCalzone!

And a few more

There is even more packed into this release. Here are some of the other changes worth a mention:

• Templates keep getting faster. Another round of “templates”A template is an automation definition that can include variables for the action or data from the trigger values. This allows automations to generate dynamic actions. [Learn more] performance work landed: templates with a numeric result are up to 40% faster, and templates used on dashboards can now be cached. Thanks, @frenck!
• Template entities remember their state. Fan, coverCovers are devices such as blinds, garage doors, etc that can be opened and closed and optionally set to a specific position. [Learn more], and device trackerDevice trackers are used to track the presence, or location, of a device. [Learn more] template entities now restore their previous state after a restart, so they pick up right where they left off. Thanks, @Petro31!
• Search finds more of what is connected. When you search or open a device or entity, Home Assistant now digs deeper into what is related, so scenes, scripts, groups, the people behind a person entity, and anything sharing a label or area all show up where you would expect them. It is a small change that makes it much easier to see how your setup fits together. Thanks, @frenck!
• A reboot heads-up on Home Assistant OS. The system updateAn update entity is an entity that indicates if an update is available for a device or service. [Learn more] entity now lets you know when an update needs a reboot to finish. Thanks, @mdegat01!
• A new radon device class. Sensors and numbers can now be classified as radon, so radon measurements get the right units and display. Thanks, @abmantis!
• Filter entities by manufacturer and model. The entity filter can now narrow entities by manufacturer, model, and model ID. Thanks, @Skaronator!
• Ask Assist from quick search. You can now start an Assist command straight from quick search. Thanks, @timmo001!
• A date on the clock card. The clock card can now show the date alongside the time. Thanks, @timmo001!
• More from the Activity panel. The Activity panel gained a CSV download and a clear-and-reset action. Thanks, @karwosts and @timmo001!

Patch releases

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

2026.8.1 - August 7

• Fixes #173399 Seerr webhook registration (@shtefko - #177201) (overseerr docs)
• Debounce Matter cover state writes to coalesce split attribute updates (@agners - #177540) (matter docs)
• Bump pydaikin to 2.18.4 (@fredrike - #178001) (daikin docs)
• Adapt vicare to set via_device_id in DeviceInfo (@emontnemery - #178229) (vicare docs)
• Adapt mqtt to set via_device_id in DeviceInfo (@emontnemery - #178234) (mqtt docs)
• bump pyenphase to 3.2.1 (@catsmanac - #178273) (enphase_envoy docs)
• Bump lyngdorf to 1.4.3 (@fishloa - #178323) (lyngdorf docs)
• Track shielded service call task in REST API (@arturpragacz - #178377) (api docs)
• Bump aiowebostv to v0.9.1 (@thecode - #178384) (webostv docs)
• chore: update python-picnic-api2 to v2.0.1 (@codesalatdev - #178395) (picnic docs)
• Bump lyngdorf to 1.4.4 (@fishloa - #178401) (lyngdorf docs)
• Use SmartThings cooling setpoint range for air conditioners (@StellarSea - #178430) (smartthings docs)
• Bump solaredge-web to 0.3.1 (@tronikos - #178437) (solaredge docs)
• Bump pytrydan to 1.0.5 (@dgomes - #178447) (v2c docs)
• mikrotik: Don’t reuse a string from Vodafone Station (@reedy - #178455) (mikrotik docs)
• Update frontend to 20260729.6 (@bramkragten - #178470) (frontend docs)

Need help? Join the community

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

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

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

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

If you would like to wear your support: the Open Home Foundation store just added new T-shirts featuring ESPHome, Music Assistant, and a fresh Home Assistant design, all in classic black (or Dark Mode, if you prefer!). They are versatile, built to last, and best of all, every purchase helps fund the foundation’s work. Grab yours from the store.

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:

• Devices are restricted to a single config entry and at most one subentry
• Introducing the Open Home Foundation AI Policy
• Media sources can now be searched
• Modernizing Modbus in Home Assistant
• Standard event types for button event entities

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

Sound the alarm, because Works with Home Assistant just welcomed our newest partner to the program: FireAvert! 🎉 Specialists in fire safety, FireAvert are on a mission to keep you and your home out of harm’s way. They bring the very first gas and electric appliance shutoff devices to the program, and with them, a whole lot of peace of mind.

Where there’s smoke, there’s FireAvert

As ex-firefighter Peter Thorpe knows too well, a moment of forgetfulness is all it takes for a kitchen to end up in flames. And after close to twenty years of service witnessing the same devastating scenario repeat itself, he knew something had to be done. So he founded FireAvert, launching with the Auto Stove Shutoff for electric stovetops.

The device was already gaining momentum before FireAvert’s pitch caught the attention of Shark Tank, and for good reason. They say there’s no smoke without fire, but years on the job taught Thorpe that in the kitchen, that isn’t always the case. Smoke can build well before a flame takes hold – and that’s the window FireAvert’s shutoff works in. By listening for your standard smoke alarm, the device automatically shuts off your stove when the alarm sounds – cutting the heat at the source before a fire can catch.

Since their launch, FireAvert’s range has expanded to include gas stove and small appliance shutoffs (think microwaves, air fryers, hot plates), so whatever’s most likely to be left on in your kitchen, there’s a shutoff for it. And with Z-Wave units now among them, it’s easier than ever to bring that protection straight into your Home Assistant setup.

On the same frequency

The FireAvert shutoffs joining the program run on Z-Wave. For anyone unfamiliar, here’s a quick rundown: Z-Wave is an open smart home protocol that allows your devices to talk to each other regardless of the brand, without locking you into one ecosystem. It’s also a mesh network, where each device relays signals for the others to extend coverage across your home, reinforcing your connection.

While Z-Wave wasn’t a part of FireAvert’s initial product line, since then we’ve been pleased to see the company prioritize local control by producing shutoff devices with the open standard, and certifying them with the Z-Wave Alliance. We first met the FireAvert team at a San Diego alliance meeting back in 2025, and it was clear from the get-go that we were on the same wavelength: driven to build open, interoperable smart home tech that doesn’t require a cloud to keep your home protected.

FireAvert automatic shutoffs for electric and gas stoves

Safe as houses

It’s important to note that FireAvert’s shutoffs don’t rely purely on Z-Wave to do their job, and they’ll keep protecting your kitchen even if your network drops out entirely. That kind of safety net is reassuring for anyone, but even more so for those with caring responsibilities or aging relatives to worry about.

Likewise, FireAvert’s shutoffs don’t depend on a battery to function: just plug your stove or small appliance into the shutoff device, and the device into your wall socket – and you’re all set. As long as your appliance has power, the shutoff is on duty. And FireAvert back up that dependability where it counts: all four devices come with a lifetime warranty, and are independently tested to CSA and UL standards – confirming the hardware meets strict, recognized electrical safety requirements.

Devices

Just like every device certified by the Works with Home Assistant program, FireAvert’s shutoffs have also been rigorously tested by our in-house team to ensure they are up to code with our core requirements of local control and privacy.

Check out the devices that made the grade:

• FireAvert Electric 240V 3 Prong Auto Stove Shutoff
• FireAvert Electric 240V 4 Prong Auto Stove Shutoff
• FireAvert 120V Auto Appliance Shutoff
• FireAvert Gas Shutoff

But it’s not just about adding devices to a list – our community is the engine of everything we do, and by joining it FireAvert commits to providing long-term support to make certain their devices continue to work smoothly within your setup.

Building the brigade

While there are already certified water shutoff devices in the program, stove shutoffs are a first, bringing a brand-new category of safety tech to Home Assistant users. It’s exactly the kind of innovation we love to see: more ways for our community to manage their smart homes, on their own terms.

That expansion is core to what the Open Home Foundation – which operates the Works with Home Assistant program – is about: keeping smart homes local, private, and safe. If you’d like to see more safety-focused partners like FireAvert join the program, consider subscribing to Home Assistant Cloud or buying official hardware like the Home Assistant Connect ZWA-2. Every bit of support helps us expand and maintain the program for all ⚒️.

Geared up and ready to respond

Forged to protect the community, FireAvert are a natural match for ours. We’re thrilled to have them join the ranks, and excited for Home Assistant users to be able to add another line of defense for their smart homes, and the people and pets who live in them. Head to our certified device list to discover the full range of devices to safeguard your 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 the functionality you would expect within Home Assistant, operate locally without the need for the cloud, and that they 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 Home Assistant Connect ZWA-2 as the Z-Wave adapter and with our Z-Wave integration. If you have another hub/adapter/integration that’s not a problem but we test against these as they are the most effective way for our team to certify within our ecosystem.

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

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

The Works with Home Assistant program powers up this month as we welcome our new partner, IoTorero! 🎉 Experts in pre-flashed smart home hardware, IoTorero bring the very first ESPHome-ready smart plugs and relays to the program (and that’s not all).

IoTorero enters the ring

If you’ve spent any time browsing pre-flashed smart home tech online, there’s a good chance you’ve come across IoTorero. And if you haven’t, let us introduce you! Founded in 2020, the company (formerly Athom Technology) was tinkering with ESPHome right out of the gate. Their new name is a nod to the Internet of Things (IoT), but unlike standard IoT gadgets that stop working if your internet drops or a company closes its servers, IoTorero champion open source firmware.

Other smart devices run manufacturer-written software, which is tuned to work well with Home Assistant for certification to the program. IoTorero go a step further to make sure their tech is accessible for all: all seven of their certified devices are pre-flashed with ESPHome, meaning there’s no installation required – the devices will integrate into your Home Assistant setup straight out of the box. And because their devices are genuinely open, you can always tweak and customize them if you want to.

That same spirit of openness carried over to last year’s Community Day, where IoTorero donated a stack of samples for attendees to try – a gesture we loved to see, and one that speaks to how seriously they take supporting our community 💪. It shows up in their approach to code, too: IoTorero maintain a public GitHub repository of configs for all their devices, free for anyone to learn from or build on.

Speaking of community, 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 IoTorero’s devices work locally, if you’re interested in remote access – for example to check your energy use or open the garage door from a distance – check out Home Assistant Cloud.

Right on (Io)Time

For anyone new to it, ESPHome is a powerful platform that allows smart home devices to operate completely locally via the chip inside, with no cloud required. Because IoTorero’s devices arrive pre-flashed, you get all that local power without having to learn how to build or compile firmware yourself. And it just got a major upgrade. The ESPHome team recently released a new UI and Device Builder, swapping the old code editor-inspired dashboard for a visual workspace that can suggest components and layouts as you build.

Since IoTorero’s devices arrive pre-flashed, there’s nothing to set up in advance: just connect them, and they’ll show up in Home Assistant like any other device, ready to control and automate from your normal dashboard. The ESPHome Device Builder is there if you ever want to go further: it allows you to do things like renaming a device or tweaking its config, without needing to touch any code… unless you want to. Whether you’re new to the arena or a seasoned pro, it means a lot less guesswork (and a lot more fun!).

Devices

Every device that earns Works with Home Assistant certification goes through our in-house testing process, checked against our core requirements of local control, privacy, and long-term support – and IoTorero meets that bar across the board. Their devices also carry the Made for ESPHome certification, a separate badging program and prerequisite for any ESPHome devices joining Works with Home Assistant.

Here’s the full list of IoTorero’s certified devices:

• IoTorero ESP32-C3 EU Plug
• IoTorero ESP32-C3 US Plug
• IoTorero ESP32-C3 UK Plug
• IoTorero ESP32-C3 AU Plug
• IoTorero Power Monitoring Mini Relay
• IoTorero Garage Door Opener
• IoTorero EU Wall Socket

Sustainability is one of the Open Home Foundation’s core principles, and IoTorero’s ESP32-C3 plugs are a great example of what that looks like in practice. They turn an ordinary appliance into something smart and measurable, with all four regional variants monitoring voltage, current, power, and total consumption – making it easy to spot energy waste and cut your home’s carbon footprint, as well as your bill.

The Power Monitoring Mini Relay brings that same convenience to hardwired setups. At roughly the size of a matchbox, it’s small enough to tuck behind a wall switch or inside a cabinet, and it’s built for switch control, garage and appliance automation, and other local smart home workflows a standard plug can’t reach.

Proxy points

Another nifty feature across IoTorero’s devices is that they double as Bluetooth proxies. This means they pick up signals from nearby Bluetooth low-energy (BLE) devices and pass them on to Home Assistant, extending your Bluetooth range without having to buy an extra, dedicated device. The Open Home Foundation’s recent blog post, Proxy all the things: no device left behind, explains why this is so important: turning everyday hardware into a “bridge” for other devices means getting more out of what you already own, instead of buying something new for every job. And one less gadget to buy means one less device ending up as e-waste ♻️.

Old friends, new badge

As one of ESPHome’s earliest adopters, IoTorero have well and truly earned our formal badging, and we’re thrilled to bring their devices to the Home Assistant community – tested, certified, and ready to make the path from unboxing to automating that much smoother. Check out the full lineup of IoTorero’s devices, along with the full range of Works with Home Assistant-compatible tech over at our certified device list.

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. We do not certify anything that relies on cloud control.

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

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have the functionality you would expect within Home Assistant, operate locally without the need for cloud and that they 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 as a hub and using the ESPHome integration. If you have a different 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 IoTorero devices to the program?

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

We’re updating which Apple platforms the Home Assistant Companion app supports, and because transparency is core to how we work, we want to be upfront about what’s changing.

Starting with version 2026.8.0 of the Companion app, we will no longer support iOS 15, watchOS 8, or macOS 11. The last supported version for these platforms will be 2026.7.1.

Here’s everything you need to know:

Why we’re making the change

At Home Assistant, we’re committed to helping you use your devices for the long haul. We know your hardware is something you rely on every day, which is why we try to keep the Companion app running on older devices for as long as possible. However, supporting older OS versions indefinitely comes at a cost, limiting our ability to adapt to modern technology.

From September this year, Apple’s developer tools will officially stop supporting watchOS 8 and macOS 11, making it technically difficult for us to keep building for them. With less than 1% of our users currently running these older OS versions, this update allows us to future-proof the Companion app for the vast majority of our community.

By focusing our efforts on current operating system versions, we can keep our codebase maintainable for the long term. This shift removes some long-standing constraints, since older OS versions had been limiting our ability to make UX, stability, and performance improvements, including adding features such as Apple Watch complications and more advanced widgets.

What this means for you

A recap of what’s changing:

• The last Companion app update for these platforms will be version 2026.7.1.
• After version 2026.7.1, the minimum supported versions for the Companion app will be iOS 16.4, watchOS 9, and macOS 12.

Importantly, this doesn’t mean your older iOS devices will become unusable. You can still control your home using the Home Assistant frontend in your device’s web browser, which remains fully supported and receives regular monthly updates.

The last compatible Companion app version (2026.7.1) will also remain available on the App Store, and the source code will stay accessible on GitHub for any users who want to compile the app themselves.

Looking ahead

This update means a stronger, more capable Companion app for everyone going forward, and it’s part of how we keep Home Assistant evolving. We appreciate your understanding and support through this change, and are looking forward to building what’s next.

Home Assistant 2026.7! 🎉

This is one of those releases I’ve been looking forward to for a long time. My favorite by far is what we’ve done with automations. Purpose-specific triggers and conditions graduate from Labs and become the new default for everyone. 🎉

It comes down to something we’ve been chasing for years: more power, less complexity. Instead of starting from Home Assistant’s internals, which entity, which state, which kind of trigger, you start from what you actually want your home to do. When the bedroom drops below 18°C, turn on the heating. That’s it. No technical traps, no quirks to memorize. And because integrations can teach the automation engine their own triggers and conditions, it only gets better from here. All of it right there in our beautiful user interface.

The nice thing is, nothing breaks. All your existing automations keep working, worry-free. We’ve also written tons of great documentation explaining every single trigger, condition, and action, with examples to learn from. And if you’re one of those people who prefers writing automations in YAML instead of the UI, you’re in for an amazing experience too. User experience is not a synonym for “the UI”. YAML users deserve good user experience too.

But honestly? I’ve got a second favorite this release, and that surprised me a little. Activity, what many of you still know as the logbook, has been rebuilt into a slick and clean timeline. 😍 It reads top to bottom like a feed, groups entries by day, and finally speaks the same language as the rest of Home Assistant. I keep opening it just to look at it.

And that’s just the start. There’s a new update-all button, dedicated panels for infrared and radio frequency, an overhauled ZHA Zigbee device management, and 10 new integrations from our community.

One more thing before you dive in: the Open Home Foundation is exhibiting at IFA Berlin for the first time, from September 4 to 8, 2026. We’d love to meet you there, so come say hello. There’s also a community meetup on Sunday, September 6, and everyone’s welcome. You can read all about it here.

Enjoy the release!

../Frenck

• Creating automations just became easier, natural and more powerful
  • Start with what you want, not how it works
  • Built around areas, not one device or entity at a time
  • More than friendlier wording
  • No technical traps
  • Your automations are safe, and YAML isn’t going anywhere
  • Documentation is part of the feature
• Activity logbook
• Update all
• 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
  • Time format selection
  • Dedicated panels for infrared and radio frequency
  • The ZHA Zigbee device management got an overhaul
  • Keeping your Raspberry Pi firmware up to date
• Patch releases
  • 2026.7.1 - July 3
  • 2026.7.2 - July 10
  • 2026.7.3 - July 21
  • 2026.7.4 - July 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 @piitaya, @sairon, and @agners who helped write the release notes this release. Thanks to them, these release notes are in great shape. ❤️

Creating automations just became easier, natural and more powerful

This is, hands down, one of the biggest and best changes we’ve made to the automation editor in years. It has been roughly eight months in the making, built and refined release after release by a lot of people, and shaped by a mountain of your feedback along the way. As of this release, it is here for everyone, and we could not be more excited to finally hand it over.

Why are we this excited? Because automations have always asked you to meet Home Assistant halfway. Some people still talk about it like you need YAML, a coding background, and a free evening just to automate a light. That hasn’t been true for a while, and this release takes the biggest step yet toward closing that gap for good.

Back in Home Assistant 2025.12, we introduced purpose-specific triggers and conditions in Settings > System > Labs. Every release since has added more of them and polished the experience. This release, they graduate: this new way of building automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] is out of Labs and becomes the new default for everyone. 🎉

It is tempting to read this as a nicer set of menu options. It is much more than that. It is a different starting point: you describe what you want your home to react to, rather than starting from the technical building blocks underneath.

Start with what you want, not how it works

An automation engine thinks in primitives. People don’t. You think “when the front door opens”, “when the last person leaves”, or “when a battery runs low”.

The old path started somewhere else, with Home Assistant’s internals. Which entity? Which state? Does it become on, detected, home, or not_home? Do I need a state trigger, a numeric state trigger, a device trigger, or a system event? If you know Home Assistant well, those questions are second nature. If you don’t, they are the wall you hit before you even start. 😤

The new triggers and conditions speak the language of the thing you care about. When the bedroom drops below 18°C, turn on the heating. You don’t think about numeric state triggers, attributes, or units. You pick Temperature crossed threshold and say what matters. Or Battery low: no need to know whether a device reports its battery as a percentage sensor, or what counts as “low”. You build around the moment itself.

Built around areas, not one device or entity at a time

The new building blocks also support targets, and that is a bigger deal than it sounds.

You can build an automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] around motion in the living room, instead of around one specific motion sensor. One sensor in that room, fine. Ten, also fine. Swap one out next year, add another, or remove the one that kept seeing the cat, and the automation keeps describing the same intent: motion in the living room.

When motion is detected outside, turn on the lights outside. The trigger points at the outside areaAn area in Home Assistant is a logical grouping of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage. [Learn more], the action points at the outside lights. Change which sensors or lights live there later, and the automation follows along. It reads like a sentence, and it is one less fragile list of entities to maintain forever.

More than friendlier wording

Here is the part that is easy to miss: this isn’t just a friendly wrapper around the old triggers.

These triggers and conditions can be extended by integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more], including custom and community ones. Integrations have long been able to add their own actions; now they can add their own triggers and conditions too. Picture a washing machine integration offering a plain “laundry is done” trigger, with no need to know which state value or attribute actually means finished. An integration knows things you would otherwise have to figure out yourself: which state changes matter, which to ignore, which edge cases are normal, and what a useful automation moment looks like in its world.

A sensor can tell you the electricity price. The integration can tell you when the price is lowest today. Instead of everyone rebuilding the same template, or learning the quirks of one particular heat pump, EV charger, or alarm panel, the integration can offer the triggers, conditions, and actions that make sense for it. That turns the automation engine into something integrations can teach. It is where “more power, less complexity” stops being a slogan.

No technical traps

There is a quieter benefit too: No technical traps. 💪

With these new triggers, you don’t need to care about unknown or unavailable states. The building block handles those in the way that makes sense for its purpose. The moment you have to decide whether one specific automation should ignore unavailable, wait it out, or treat it as false, we have already made you think about the wrong thing.

Event entities are another classic. Automate around one with a plain state trigger and you may discover it doesn’t fire the second time the same event happens, because the state didn’t change the way you expected. A purpose-specific trigger expresses the event directly, so that whole class of surprise simply goes away.

Your automations are safe, and YAML isn’t going anywhere

Before anyone opens a forum thread in mild panic: no, you don’t need to rewrite anything.

Existing automations keep working. Generic triggers, conditions, templates, and YAML all keep working. The new triggers and conditions are simply the better starting point for the next automation you build, and a nicer option when you decide to improve an old one. It is not a migration tax.

And this isn’t Home Assistant walking away from YAML. We put real effort into making the new building blocks read well in YAML too, the same way we did when automations moved to triggers, conditions, and actions and swapped service for action. If text is your interface, it should feel just as natural. If you use YAML to write automations, we are sure you’ll love the new triggers and conditions just as much!

Documentation is part of the feature

We also did the less flashy work, which on a project like this is often the work that matters most. Every trigger, condition, and action now has its own documentation page over at triggers, conditions, and actions. Each one explains what the building block is, when you would reach for it, how to use it from the automation editor, how it looks in YAML, and includes real examples to learn from.

There is a lot of it, on purpose. Approachability is not only about a friendlier button in the UI. It is also about helping you understand what that button does, and when to use it. Good documentation is product work, even when it does not get its own screenshot.

There is an AI angle here too, and it belongs in the right place: this is for people first. But many of you already use AI to help build automations, and clearer, well-described building blocks give those tools much better material to work with. Their suggestions can become more consistent, because there is less Home Assistant-specific guesswork to invent. It will not happen overnight, since most models are trained on older examples and may keep suggesting the old patterns for a while. The better the documentation, the faster both people and machines pick up the new way.

Haven’t tried building automations this way yet? Open the automation editor and start with what you want to happen. We think you’ll like where it begins. 😎

Activity logbook

Activity, the feature many of you still know as the logbook, has always been there to answer a simple question: what happened, and when? The way it answered, though, was a flat list of full sentences. “Living room lamp turned on.” “Auto lights was triggered by motion.” Every row was a complete sentence, the device name was repeated on every line, and it used its own wording (“turned on”, “changed to”) that didn’t quite match how states are written everywhere else in Home Assistant. Reading back a busy day meant reading every single line.

This release rebuilds it from the ground up into a timeline.

Each entry now sits on a vertical rail: the time on the left, a colored dot with the 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]’s icon, and the text beside it. You read it top to bottom, like a feed. Entries are grouped by day, with Today, Yesterday, and dated headers, so you never lose track of where you are in time. The dot takes on the state color too, so an on and an off are easy to tell apart at a glance, without reading a word.

It also shows only the context you actually need. The timeline trims the name down to where you’re looking: on an entity page you just see the value, on a device page the device name is dropped, and on an area page the area is left out. No more reading the same device name on every row.

A few more touches make it feel right at home:

• The same words as the rest of the app. State text now comes from the backend, the same source the rest of Home Assistant uses, so it reads identically everywhere and in every language. No more logbook-only verbs.
• It shows the cause. When something was set in motion by a person, you see their avatar. An automation shows what triggered it, and an integration shows its brand icon. The “why” sits right next to the “what”.
• Time the way you want it. In the compact views, like the more info dialog, device and area pages, and on cards, select the timestamp to flip between absolute time and a relative “2 hours ago”. A quick glance when you want it, exact precision when you need it.

The same component powers all of this, so the timeline stays consistent whether it’s filling the full Activity page on a wide screen or tucked into a card on your phone. Wide screens get the full timeline with the time column and icons; narrow screens and cards get a compact version with the cause icon and the time trailing the entry.

Update all

We’ve all been there. You open Settings > Updates after being away for a bit, and there it is: a wall of pending updates. A new Home Assistant release, a handful of apps, that one integration, and seven ESPHome devices that all decided to ship new firmware in the same week. Keeping up used to mean working down that list one entry at a time, selecting, waiting, selecting the next, and repeating until your finger got tired.

Not anymore. This release reorganizes the updates page around how you actually think about your system, and adds a single button that does the heavy lifting: Update all.

Instead of one long, flat list, your pending updates are now grouped into clear cards, each covering a part of your setup:

• Home Assistant sits right at the top, with Core, the Operating System, and the Supervisor. These run the core of your system, so they’re kept on their own, without an Update all button. You apply them yourself, on purpose.
• Integrations with several pending updates get a card of their own. Those seven ESPHome devices? Bundled together, so a single selection brings them all up to date. The same goes for a stack of HACS integrations waiting on a new version.
• Integrations gathers the remaining one-off integration updates into one tidy card.
• Apps does the same for your apps (used to be called add-ons).
• Skipped updates show up in their own card once you turn on Show skipped updates. Keeping them separate means they never get swept along by an Update all you didn’t intend for them.

Select Update all on any card, and Home Assistant takes it from there, updating everything in that group in one go. No ticking boxes, no confirmation dialog to step through, just done.

It’s a small change to a page you only visit now and then, but it turns a recurring chore into a couple of taps.

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:

• Aqvify, added by @astrandb, launching at 🏆 platinum quality
  Monitor your Aqvify water well and tank sensors in Home Assistant. The integration connects through Aqvify’s public cloud API and exposes sensors for your well water level, so you can keep an eye on your supply and build automations around it.

• Chef iQ, added by @Invader444
  Read the temperatures from your Chef iQ wireless cooking probes directly over Bluetooth. No cloud account, base station, or hub is needed: the probe broadcasts its readings and Home Assistant listens passively.

• Dropbox, added by @bdr99
  Store your Home Assistant backups straight to your Dropbox account. Setup runs through the Home Assistant Cloud Account Linking service, so you do not need a Home Assistant Cloud subscription or your own application credentials to get started. Once connected, Dropbox shows up as a backup location alongside the rest.

• Edifier Infrared, added by @abmantis
  Control your Edifier speaker with any infrared transmitter you already have set up in Home Assistant. Built on the Infrared entity platform, so you can pair it with an ESPHome device with an IR LED, or any other supported IR emitter. Communication is one-way, so the integration uses assumed states.

• energieleser, added by @AjinkyaGokhale
  Bring real-time energy readings into Home Assistant from energieleser devices, such as stromleser, gasleser, wasserleser, and wärmeleser. The integration reads consumption data over a local HTTP API, so all communication stays on your network.

• Envertech EVT800, added by @daniel-bergmann-00
  Monitor your Envertech EVT800 solar microinverter in Home Assistant. The integration receives data locally over your network, exposing energy and power readings you can track on dashboards and use in automations.

• Greencell, added by @BrzezowskiGC
  Connect your Greencell EV charging devices to Home Assistant over MQTT. It monitors charger status and electrical measurements like voltage, current, and power, and exposes real-time telemetry and charging-session data for dashboards and automations.

• Helty Flow, added by @ebaschiera
  Control your Helty Flow decentralized heat-recovery ventilation units with the smart Wi-Fi interface. The integration talks to each unit directly on your local network, so it keeps working without an internet connection.

• KlikAanKlikUit, added by @Phunkafizer
  Control self-learning KlikAanKlikUit 433.92 MHz RF devices from Home Assistant. Because the integration sends commands over RF without a feedback channel, it uses assumed states.

• MELCloud Home, added by @erwindouna
  Bring your Mitsubishi Electric air conditioning and heat pump products into Home Assistant through MELCloud Home, Mitsubishi Electric’s cloud service. Monitor and control your devices alongside the rest of your home automations.

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:

• Avosdim, provided by Motionblinds, added by @mbo18
• BWT, provided by SEKO PoolDose, added by @lmaertin
• Gitter, provided by Matrix, added by @tr4nt0r
• Nexen, provided by Hypontech Cloud, added by @jcisio

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 keep getting better too. Here are some of the noteworthy improvements this release:

• Alexa Devices gained switches to toggle announcements and communications on your Amazon Echo devices, thanks to @chemelli74. It also added a to-do list platform, so you can manage your Alexa shopping and to-do lists from Home Assistant, thanks to @lonlazer.
• SwitchBot added a button event entity for the Contact Sensor, plus switch controls for the Standing Fan. Thanks, @prmx and @Onero-testdev!
• Overkiz now supports Rexel Energeasy Connect, through both its cloud and local API. Thanks, @iMicknl!
• SwitchBot Cloud can now upload images to the SwitchBot AI Art Frame. Thanks, @XiaoLing-git!
• SMTP gained notify entities, the modern way to send email notifications. Thanks, @tr4nt0r!
• GitHub added entities that track GitHub user accounts. Thanks, @joostlek!
• Environment Canada gained a get_alerts action to fetch active weather alerts on demand. Thanks, @gwww!
• Wallbox added a button to resume the charging schedule, handy alongside EcoSmart solar charging. Thanks, @Rayman223!
• Tesla Powerwall now supports the Powerwall 3, and gained sensors for the operation mode and the maximum charge and discharge power. Thanks, @Bre77 and @BrettLynch123!
• Tedee added a connectivity binary sensor, so you can tell when a lock drops off the network. Thanks, @zweckj!
• BleBox added support for openSensor and drutexSmart devices, including CO2 sensors. Thanks, @bkobus-bbx!
• Droplet now reports leak alerts. Thanks, @sarahseidman!
• Whirlpool Appliances added a button to stop the oven. Thanks, @bdlcalvin!
• Yoto got a lot of attention this release: a media browser, plus new sensors, binary sensors, a time entity, and number controls for display brightness and maximum volume. Thanks, @piitaya!
• Samsung Infrared added buttons for individual remote commands. Thanks, @lmaertin!
• openSenseMap now exposes its environmental measurements as sensors. Thanks, @AlCalzone!
• OpenEVSE added binary sensors for your charger’s status. Thanks, @firstof9!
• Rabbit Air added an air quality sensor. Thanks, @MagikalUnicorn!
• Green Planet Energy gained actions to find the cheapest stretch of energy prices. Thanks, @petschni!
• Duco added a select to set the ventilation state on your Duco box nodes. Thanks, @ronaldvdmeer!
• Hypontech Cloud added load, grid, and battery sensors. Thanks, @jcisio!
• Xthings Cloud added a switch platform. Thanks, @zhangluofeng!
• Kiosker added a button to clear the blackout, plus binary sensors and sensors with blackout details. Thanks, @Claeysson!
• PAJ GPS added battery sensors for your trackers. Thanks, @skipperro!
• Vistapool grew a lot, with new button, number, light, and binary sensor entities for your pool controller. Thanks, @fdebrus!
• Fluss+ now supports covers, like gates and garage doors. Thanks, @Marcello17!
• Imou added live camera streaming. Thanks, @Imou-OpenPlatform!

Integration quality scale achievements

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

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

• 1 integration reached platinum 🏆

  • Yoto, thanks to @piitaya

• 2 integrations reached gold 🥇

  • Anthropic, thanks to @Shulyaka
  • Growatt, thanks to @johanzander

• 3 integrations reached silver 🥈

  • OpenEVSE, thanks to @c00w
  • OVHcloud AI Endpoints, thanks to @Crocmagnon
  • Splunk, thanks to @Bre77

• 1 integration reached bronze 🥉

  • openSenseMap, thanks to @AlCalzone

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:

• SAJ Solar Inverter, done by @edurenye
• SMTP, done by @tr4nt0r
• Swisscom Internet-Box, done by @anatosun
• UniFi AP, done by @PaulVanSchayck

Farewell to the following

Time for a little cleaning, and no, we did not wait for spring. The following integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] are no longer available as of this release. Most had been broken for a while, leaning on libraries or services that went unmaintained or offline years ago:

• Acer projector has been removed. It had been broken since 2019.
• Ampio Smog has been removed. The air quality service it polled is offline and its library has been unmaintained since 2019, so it no longer works.
• ATEN Rack PDU has been removed. It had been broken since 2024 over a dependency conflict, and its maintainer stepped down with no one to take over.
• Avi-on has been removed. It depended on the bluepy library, which Home Assistant dropped back in 2022.7, and which has been unmaintained since 2018.
• BeeWi SmartClim has been removed for the same reason: it relied on the long-unmaintained bluepy library that Home Assistant dropped in 2022.7.
• BlinkStick has been removed. It was disabled in 2024 because it relied on a non-open-source library that has been unmaintained since 2020.
• Clementine has been removed. It had been broken since 2023, and its library has been unmaintained since 2018.
• Dovado has been removed. It was disabled in 2024.7 because it relied on a non-open-source library that has been unmaintained since 2017.
• ELIQ Online has been removed. Its API endpoint no longer exists, and the underlying library has been unmaintained for years.
• Gitter has been removed. Gitter migrated to Matrix back in 2023 and its old API no longer works, so it is now a virtual integration handled by the Matrix integration, which you can use to connect instead.
• Greenwave Reality has been removed. It had been broken since around 2022, because the devices use an outdated encryption key that modern systems reject, and its library has been unmaintained since 2018.
• Logentries has been removed. The service was rebranded to InsightOps years ago and is no longer offered, and its API endpoint no longer responds.
• Microsoft Face has been removed, together with the Microsoft Face Detect and Microsoft Face Identify integrations that built on it. They had been broken since 2022 after a change to Microsoft’s Azure face API.
• MS Teams has been removed. The integration relied on Office 365 Connectors, which Microsoft discontinued on May 22, 2026, so it no longer works.
• Mycroft has been removed. It was disabled in 2023.6 over an unresolvable dependency conflict, and its library has not been updated since.
• SCSGate has been removed. It required obscure DIY hardware that is no longer available, its library has been unmaintained for a decade, and it had effectively no users left.
• ThermoWorks Smoke has been removed. It was disabled in 2024.10 over a dependency conflict, and its library has been unmaintained since 2019.
• Tikteck has been removed.
• UniFi LED has been removed. The hardware is discontinued and the integration had no remaining users.
• Watson TTS has been removed. It was disabled in 2023 over a dependency conflict, and no one stepped up to update it since.

Other noteworthy changes

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

• Edit a running timer’s duration. Change a timer’s duration straight from its dialog, no need to cancel and start over. Thanks, @chli1!
• A faster frontend. A big batch of performance work landed this release, most noticeably across the energy, history, and statistics graphs, so they draw quicker and feel snappier. Thanks, @MindFreeze!
• Device and area pages adapt to your screen. They now use a responsive column layout, and the device page lists its main entities first, so the important controls sit right at the top.
• More context in the scene editor. Entity rows now show their type and the integration they belong to, making large scenes easier to read. Thanks, @pszypowicz!
• Tags in the Apps store. The Apps store now shows tags and marks which apps you already have installed. Thanks, @bramkragten!
• A sub-editor for the statistics graph card. Tune each entity right from the card’s visual editor. Thanks, @ildar170975!
• Live condition testing keeps improving. Conditions now show clearer status icons (addressing the red and green only accessibility concern from last release), the indicator works on mobile in the visibility editor, and live testing now covers conditions inside actions too. Thanks, @silamon and @marcinbauer-ohf!
• Hide columns in Developer tools. The States tab can now hide the Device and Area columns. Thanks, @vingerha!
• Matter soil moisture sensors. Matter-certified soil moisture sensors now show up in Home Assistant. Thanks, @lboue!
• A projector device class for media players. Projectors are now a proper media player device class, surfaced through Google Assistant, HomeKit, and SmartThings too. Thanks, @jtjart!
• Template lights gain xy color. Build template lights with full xy color support. Thanks, @Petro31!
• Clean a specific room from Google Assistant. Ask Google to send your robot vacuum to a particular room. Thanks, @joostlek!
• Snappier templates. Under the hood, a template engine optimization makes templates render up to 40% faster. Thanks, @frenck!
• Clearer automation traces. When you debug an automation or script, its trace now always includes template errors, making it easier to spot what went wrong. Thanks, @emontnemery!

Time format selection

Some 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] tell time. A sensor with the next sunrise, the timestamp of your last backup, a countdown to the next calendar event. How that moment should be shown is a matter of taste: sometimes you want the exact date and time, and sometimes a friendly “in 3 hours” or “2 days ago” is far more useful at a glance.

Until now, picking how a timestamp was displayed meant editing YAML. This release brings that choice into the UI. When you add a timestamp entity to a tile card, the entities card, or as an entity badge, a Time format option shows up in the editor, so you can choose how the time is presented, including a new short or long style for the relative format.

Thanks, @karwosts!

Dedicated panels for infrared and radio frequency

Earlier this year, Home Assistant gained dedicated entity platforms for infrared and radio frequency devices, the building blocks behind integrations that reach your gear through an IR blaster or a 433 MHz transmitter. This release gives them a proper home.

Two new panels show up in the Settings menu, one for infrared and one for radio frequency. Each lists the proxies and transmitters you’ve set up, so you can see your IR blasters and RF bridges at a glance and jump straight to the one you’re looking for, instead of hunting for them among everything else. The panels only appear when you actually have such devices, so they stay out of the way if you don’t.

Thanks, @balloob!

The ZHA Zigbee device management got an overhaul

Managing a Zigbee device through ZHA used to mean squinting at a cramped dialog. The clusters, bindings, signature, and neighbors tools were all there, but crammed into a small popup that left little room to breathe.

This release moves all of that onto a dedicated, full-page device view. The same tools are now laid out across tabbed navigation, with a device summary card up top, and the loading, empty, and error states have been cleaned up throughout. It’s the same powerful Zigbee management, just far easier to work with.

Thanks, @jpbede!

Keeping your Raspberry Pi firmware up to date

Running Home Assistant Operating System on a Raspberry Pi? You are in good company: per our public, opt-in analytics, the Raspberry Pi platform currently powers about a third of all installations. As of this release, there is an “update entity”An update entity is an entity that indicates if an update is available for a device or service. [Learn more] for the Pi’s bootloader firmware, also often referred to as the EEPROM update. You can keep it current right from Settings > Updates, the same place you handle every other update.

This is more than a nice-to-have. Especially on the Raspberry Pi 5 and Compute Module 5, the firmware contains bug fixes, compatibility improvements for NVMe drives, thermal improvements, and much more. Until now, updating that firmware was cumbersome: you had to flash another SD card with a special image, or connect a keyboard and a display and run the rpi-eeprom-update command by hand. Now it takes a single step.

A few things to keep in mind:

• This needs Home Assistant Operating System 18 or newer, which provides the support the update entity builds on. On older versions, the entity simply isn’t there.
• On a Raspberry Pi 4, the firmware can only be updated when the board boots from an SD card. If your Pi 4 boots from USB storage, the update isn’t available. This is a limitation of the update system, and one more reason we recommend using USB only as a data disk while keeping an SD card as the main boot device.
• Not every board can update its firmware this way. Besides a Raspberry Pi 4 booting from USB storage, the Home Assistant Yellow with a Compute Module 4 isn’t supported either. Where an update can’t be applied, the entity doesn’t appear at all, so you don’t see an update that wouldn’t work.
• After the update is applied, Home Assistant prompts you to reboot to complete it.

Thanks, @sairon!

Patch releases

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

2026.7.1 - July 3

• Proximity: Fix/improve matching against trackers with in_zones attributes (@kbuck1 - #172602)
• Fix HomeKit Controller doorbell event entity to use ring event type (@frenck - #173621)
• Retry ecobee setup on transient refresh failure (@frenck - #173720)
• Handle cname records in dnsip (@gjohansson-ST - #175313)
• Bump habluetooth to 6.26.2 (@bdraco - #175317)
• Fix airOS advanced settings migration (@CoMPaTech - #175319)
• Fix SolarEdge energy sensors losing unit of measurement (@frenck - #175335)
• Switchbot_cloud: fixed cloud hook error (@XiaoLing-git - #175336)
• Homee: fix unavailable entities (@Taraman17 - #175367)
• catch SMTPException and TimeoutError in SMTP config flow (@tr4nt0r - #175369)
• Fix Hitachi Yutaki DHW turn-on command in Overkiz (@iMicknl - #175374)
• Homee: fix unavailable entities - FollowUp (@Taraman17 - #175380)
• Bump py-synologydsm-api to 2.10.2 (@mib1185 - #175383)
• Fix KNX telegram history migration for data of 2026.3 and earlier (@martinhoefling - #175396)
• Fall back to PyPI when the extra index is down (@bdraco - #175404)
• Fix Overkiz Rexel gateway setup failing with Local API (@iMicknl - #175409)
• Bump pylamarzocco to 2.4.1 (@zweckj - #175468)
• Redact debug output in FRITZ!Box Tools (@mib1185 - #175469)
• Update frontend to 20260624.4 (@bramkragten - #175490)

2026.7.2 - July 10

• Store recovery HTTP config with the full trusted proxy network (@agners - #176075)
• Trigger reauth on Teslemetry LoginRequired errors (@Bre77 - #174255)
• Bump ical to 13.3.0 (@FuNK3Y - #175090)
• Bump uiprotect to 15.4.0 (@RaHehl - #175347)
• Correct availability check for Huntedouglas Powerview tilt-only shades (@kingy444 - #175350)
• Bump uiprotect to 15.4.1 (@RaHehl - #175540)
• Bump aioamazondevices to 14.1.9 (@chemelli74 - #175563)
• Bump pylamarzocco to 2.4.2 (@zweckj - #175564)
• Homee: fix covers not reacting correctly to commands (@Taraman17 - #175565)
• Add options update listener to Rain Bird integration (@allenporter - #175571)
• Bump habluetooth to 6.26.5 (@bdraco - #175595)
• Include melcloud_home in Mitsubishi brand (@scop - #175635)
• Bump python-roborock to 5.25.0 (@allenporter - #175645)
• Bump python-bsblan to 6.1.5 (@liudger - #175651)
• Fix temperature bound resolution for BSBLAN climate devices (@liudger - #175704)
• Bump python-bsblan to 6.1.6 (@liudger - #175711)
• Bump uiprotect to 15.4.2 (@RaHehl - #175712)
• Bump axis to v73 (@Kane610 - #175717)
• fix typos in KlikAanKlikUit integration (@Phunkafizer - #175720)
• Fix Teslemetry covers reporting a false closed/open state when data is missing (@Bre77 - #175748)
• Ensure http2 stream cleaned up on shudown for Alexa Devices (@jamesonuk - #175766)
• Add debug logging with full exception details to legacy notify action in SMTP integration (@tr4nt0r - #175781)
• Fix for Roborock uninitialized coordinator data (@allenporter - #175789)
• Bump onvif-zeep-async to 4.2.1 (@bdraco - #175795)
• Bump bleak-esphome to 3.9.7 (@bdraco - #175796)
• Don’t restart a Wyoming satellite pipeline if there’s an error (@synesthesiam - #175798)
• Fix missing To headers in SMTP integration (@tr4nt0r - #175803)
• Bump pywmspro to 0.4.2 (@mback2k - #175805)
• Bump holidays to 0.100 (@gjohansson-ST - #175809)
• Fix tesla_fleet media player volume step calculation (@Bre77 - #175813)
• Fix weatherflow_cloud websocket double-connect (@jeeftor - #169573)
• Fix for Atlantic heaters missing regulation mode in Overkiz (@iMicknl - #175817)
• Bump pyoverkiz to 2.0.4 (@iMicknl - #175818)
• Add MIT-0 to OSI approved SPDX licenses (@iMicknl - #175819)
• Bump aioruckus to 0.46.3 (@ms264556 - #175824)
• Fixed YoLink water meter controller valve status showing as “Unknown” (@matrixd2 - #175835)
• Fix RollerShutterUno covers reporting open when closed in Overkiz (@iMicknl - #175837)
• Add missing holiday categories in holiday (@gjohansson-ST - #175841)
• Re-import Rexel client credential in Overkiz config flow (@iMicknl - #175852)
• Bump uiprotect to 15.4.3 (@RaHehl - #175861)
• Bump venstarcolortouch to 0.22 (@hplato - #175867)
• Fix ZHA device trigger cache not resolving quirks (@TheJulianJES - #175895)
• Pin cffi to 2.0.0 in package constraints (@allenporter - #175907)
• Fix Teslemetry insufficient-credits polling storm (@Bre77 - #175913)
• Fix Teslemetry cabin overheat protection restored temperatures (@epenet - #175973)
• Refresh hassio coordinator after OS update install (@agners - #176004)
• Fix Rexel OAuth2 session expiring after a day in Overkiz (@iMicknl - #176010)
• bump py-synologydsm-api to 2.10.3 (@mib1185 - #176012)
• Fix max color temperature in Elgato (@joostlek - #176072)
• Sonos - avoid blocking call to get uid (@PeteRager - #176109)
• Fix rest_command digest auth with templated hosts (@jpbede - #176155)
• Bump reolink_aio to 0.21.4 (@starkillerOG - #176156)
• Skip global ESPHome update lock when dashboard has a build queue (@bdraco - #176162)
• Bump zha-quirks to 2.1.1 (@TheJulianJES - #176173)
• Bump dsmr-parser to 1.11.0 (@balloob - #175639)
• Bump dsmr_parser to 1.11.1 (@jasperslits - #176192)
• Bump tuya-device-handlers to 0.0.25 (@epenet - #176213)
• Update frontend to 20260624.5 (@bramkragten - #176216)
• Add dynamic icon for lightbulb group (@karwosts - #176218)

2026.7.3 - July 21

Apologies for shipping off schedule. This patch release should have shipped last Friday, but we weren’t able due to technical difficulties.

• Fix Hitachi Yutaki second heating zone using zone 1 states in Overkiz (@iMicknl - #176210)
• Filter out grinders during CF in lamarzocco (@zweckj - #176289)
• Bump guntamatic to v1.9.1 (@JensTimmerman - #176301)
• Fix UniFi setup crash on cellular/5G WAN without monitors (@mattsm - #176223)
• Bump python-roborock to 5.26.0 (@allenporter - #175734)
• Bump python-roborock to 5.29.0 (@Lash-L - #176311)
• Fix duplicate Hikvision binary sensor unique IDs (@gunjanjaswal - #176345)
• Bump python-roborock to 5.30.0 (@allenporter - #176373)
• Refresh Lunatone sensor data before update (@MoonDevLT - #176389)
• Bump guntamatic to v1.9.2 (@JensTimmerman - #176416)
• Filter Roborock A01 query protocols by supported schema (@allenporter - #176421)
• Make NS device a service (@joostlek - #176424)
• Bump pyoverkiz to 2.1.0 (@iMicknl - #176481)
• Bump python-swisscom-internet-box to 0.2.0 (@ghouscht - #176519)
• Make repairs not persistent in FRITZ!Box Tools (@mib1185 - #176623)
• Fix open/close for RTSGeneric covers in Overkiz (@iMicknl - #176626)
• Update vizio config entry host on zeroconf rediscovery (@raman325 - #176628)
• Bump ZHA to 2.0.1 (@TheJulianJES - #176643)
• Refresh add-on update entities after store reload through Supervisor API proxy (@balloob - #176648)
• Update Roborock dynamic dock support (@Lash-L - #176686)
• Update frontend to 20260624.6 (@bramkragten - #176711)
• Fix roborock vacuum segment mapping repair issue (@allenporter - #176778)
• Fixes for Plugwise Select (@bouwew - #176787)
• Bump python-roborock to 5.31.1 (@allenporter - #176850)
• Bump gios to 7.1.1 (@bieniu - #176904)
• Exempt certain protocol integrations from entity limit (@emontnemery - #176973)

2026.7.4 - July 24

• Fix for ProxmoxVE compoenent failing authentication with realms containg upper case letters. (@crmason2 - #176742)
• Bump yoto-api to 4.3.2 (@piitaya - #176987)
• Fix Envoy diagnostics fixture download on non-UTF-8 responses (@genestealer - #177008)
• Bump pybravia to 0.5.1 (@Drafteed - #177076)
• Bump yarl to 1.24.5 (@bdraco - #177097)
• Bump aiohttp to 3.14.3 (@bdraco - #177105)
• Bump pylamarzocco to 2.4.3 (@zweckj - #177151)

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:

• Changes to device tracker entity models
• Frontend component updates in 2026.7
• Introducing new unit enumerators
• Deprecation of the home_assistant_start flag of async_initialize_triggers

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

It started as a passion project. Yet in a few years matter.js has grown beyond my wildest expectations, becoming the backbone of the open source Matter ecosystem, and powering everything from Homebridge to openHAB, and even some commercial products.

Ten months ago, I joined forces with the Open Home Foundation to work full time as Lead Developer of Matter. Shortly after, I donated matter.js to the foundation – giving it a new home where it would be safeguarded for the future. Together we announced our plans to take Matter support in Home Assistant in a completely new direction: we set out to rebuild the Open Home Foundation Matter Server – the engine that powers Matter in Home Assistant – on matter.js.

After four months of beta testing, with our community fixing bugs and contributing new features along the way, today we’re thrilled to present the newest version of Matter for Home Assistant! 🎉

The Open Home Foundation invests in important technology to make open alternatives possible, and our work is funded in part by everyone who subscribes to Home Assistant Cloud and buys official hardware from our commercial partners. The launch of a new Matter experience in Home Assistant shows what’s possible with your support. 💪

Presenting the matter.js plans at the Connectivity Standards Alliance (CSA) Member Meeting in November 2025 (right), and returning in March 2026 as an Outstanding Contributor Award recipient (left).

Serving up more with matter.js

For those new to matter.js, it’s an open source TypeScript implementation of the Matter standard. I built it to give developers and power users more speed and flexibility, and to make Matter better suited for open source development across the millions of homes that use Home Assistant. By running Matter in Home Assistant on matter.js, all of those benefits now flow directly into the platform.

This major update brings greater stability for Matter in Home Assistant, fewer bugs, and faster start-up and recovery. It also comes with a brand new visualization feature to help you understand your network (more on that below 👀). And by upgrading to the Matter 1.5.1 specification (1.6 coming soon!), we’re better equipped to improve support for all new Matter device types, such as cameras, doorbells, and closures.

Coupled with an updated OpenThread Border Router (OTBR) app to support Thread 1.4 in Home Assistant, these changes mark important steps in making Matter work more reliably within your setup, now and into the future. But don’t just take our word for it – here’s what our beta testers are saying:

It was just a matter of time

When Matter emerged a few years ago, we immediately saw its potential to shape the industry for the better. As an open standard that lets smart devices from different brands speak the same language, it represents the kind of interoperable tech the Open Home Foundation exists to champion. So we set out to build on it.

Just weeks after Matter’s official launch in 2022, we added the Matter integration to Home Assistant, and in 2025 both Home Assistant and the Open Home Foundation Matter Server were officially certified by the Connectivity Standards Alliance. That server was built with Python and the official C++ Matter SDK – a solid starting point, but one that couldn’t keep pace with our open source ambitions.

Matter now runs in 38% of Home Assistant instances, and ranks twelfth among all integrations – a clear sign of where the smart home world is heading. We want that future to have fewer compatibility headaches, more device choice, and a smart home that just works. This update to Matter support in Home Assistant takes a huge step toward that vision.

An easy switch

The new Matter experience in Home Assistant is delivered through the “Matter Server app 9.0” – a fully compatible drop-in replacement for the previous Python-based server. After you’ve updated the app, it will automatically migrate your data on the first start, and work in exactly the same way that the previous server did.

Faster, smarter, and more secure

The real benefits kick in with every subsequent server start and device reconnection. Thanks to a range of optimizations, devices now come back online much faster, networks are more responsive, and over-the-air updates are more reliable.

Beyond performance, the new server also tightens security. When commissioning new devices, uncertified devices with an official development/test certificate can no longer be added out of the box, ensuring no malicious devices are added to your Matter network without your knowledge. Additionally, the new server checks certificate revocation data during commissioning, adding another layer of protection.

A clearer view

While the Matter Server’s web UI received a range of new and improved features, the ability to visualize your Thread or Wi-Fi networks steals the show.

Your whole network, at a glance.

The visualization feature draws details from your commissioned Matter devices to map the network and offer insights into connection quality. Each device appears as a node, with small icons indicating its role in the network – whether it’s a leader (crown), a router (arrows), a sleepy, or another end device. The color of the connections between nodes reflects connection quality: green is strong, orange medium, red weak, and gray no signal (for those that want a deeper dive, check out our GitHub documentation).

This is especially helpful for Thread networks, where there can be multiple “hops” between a device and the border router, and the devices themselves decide how data is routed. Where possible, border routers are also discovered and displayed, giving you a fuller picture of how your network is structured. The visualization also helps with Wi-Fi devices, making it easier to see which device is connected to which access point, and at what signal quality.

A foundation for what’s next

Graduating Home Assistant to matter.js wouldn’t have been possible without our community, who’ve helped grow Home Assistant into one of the biggest smart home platforms in the world.

With these new changes, we’re better placed than ever to make Matter in Home Assistant more approachable for all. Head to the Open Home Foundation roadmap to add your voice to what comes next. We can’t wait to keep building together ⚒️.

Home Assistant 2026.6! 🎉

I’m going to put my hand up right away: ✋ I am not a dashboard person. Not because I don’t like them; I love seeing what you all build. But designing a beautiful one is a kind of visual creativity I just don’t have. That’s a big part of why I love the built-in Home dashboard so much, it does the designing for me. But when I do build a custom dashboard, I usually stare at that “add a card” dialog for way too long, picking cards almost at random just to see if they look good with the data I have.

So you can imagine my excitement for my personal favorite of this release: the new card picker. Instead of asking “which card type do I want?”, it now asks “which thing in your home do you want to show?”, and then suggests cards that actually make sense for it, with live previews using your own data. For someone like me, that’s not just easier; it’s genuinely inspiring. It nudges me towards combinations I would not have thought of on my own. 💡

This fits into a bigger direction I keep getting more excited about: Home Assistant getting better at starting from the thing you want to do, instead of asking you to first learn the building blocks. The same idea is what makes purpose-specific triggers and conditions in Home Assistant Labs feel so right, and this release brings them a big step closer to graduating out of Labs with brand new zone triggers and conditions. 📍

A close second favorite for me this release is everything happening around that in the automation editor: live test indicators on your conditions, target counts on every device, area, floor, and label, and proper notes you can attach to any step. Individually they are small quality-of-life touches; together, they make building automations feel a whole lot more transparent. ✨

And there is plenty more to love in this release: new tile card features, Z-Wave smart locks catching up with their Matter siblings, a friendlier Apps page, and another big batch of new integrations from our community. 🚀

Enjoy the release!

../Frenck

• A friendlier way to add cards to your dashboard
• Infrared now also listens
• Polishing the automation editor
  • Purpose-specific triggers and conditions
  • See exactly how many things an automation targets
  • See at a glance which conditions pass
  • Add notes to any step in your automation
• Tile card features
  • Your forecast, right where you check the weather
  • Turning the media player tile into a real remote
• Z-Wave smart lock credential management
• A fresh look for the Apps page
• 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
  • A clearer view of your home’s energy
  • Quick links between everything you care about
  • YAML linting inside the UI editors
• Patch releases
  • 2026.6.1 - June 5
  • 2026.6.2 - June 9
  • 2026.6.3 - June 12
  • 2026.6.4 - June 19
• 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 @piitaya who helped write the release notes this release. Also, @karwosts, @lexpostma, and @Petro31 for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️

A friendlier way to add cards to your dashboard

Adding a card to a dashboard is one of those moments where Home Assistant has historically asked a lot of you. The old dialog opened on a wall of card types, all named after the building blocks we use under the hood: tile, entities, button, gauge, glance, picture, markdown, and so on. Lovely if you already know what each one does. A lot less lovely if you came in thinking “I just want my living room light on this dashboard.” 💡

User research kept telling us the same thing: people open the editor with a deviceA device is a model representing a physical or logical unit that contains entities. or 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] in mind, not a card type. So we flipped the dialog around.

When you add a card now, the dialog opens on a new By entity tab. On the left, your home: a tree of 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], areasAn area in Home Assistant is a logical grouping of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage. [Learn more], devices, and entities, the same shape some of you may recognize from the new purpose-specific triggers and conditions currently in Settings > System > Labs. Anything that doesn’t fit cleanly into your areas shows up under Unassigned, so nothing gets lost. Search jumps straight to a flat result list.

Pick an entity, and the right side fills with live previews of cards that actually fit it, not a generic list:

• For a light, you get a plain tile, a tile with a brightness slider, a toggle tile, color temperature, and favorite colors.
• For a cover, open/close, a position slider, and tilt.
• For a media player, a tile with playback controls or with the volume slider.
• For a numeric sensor like temperature, humidity, or power, a trend graph tile so you can see history at a glance.
• For a calendar or to-do list, the matching dedicated card.
• And a Browse all cards option in case none of those is what you wanted; the familiar By card tab is still there too, unchanged.

Every suggestion renders as a real preview of how the card will look on your dashboard, with your data, before you pick it. No more “add it, see how it looks, delete it, try the next one.”

Custom cards can join the party too. If a custom card you have installed has opted in to the new picker, its suggestions show up under a separate Community section, right below the built-in ones. Support depends on the custom card’s author adding it.

On mobile, the same dialog turns into a two-step flow: pick your entity, then pick your card.

This is the first visible step of a broader effort on the Open Home Foundation roadmap to make building a dashboard feel as natural as building an automation: start from what you want to control, and let Home Assistant suggest the rest. Expect more in this direction in the releases to come.

Infrared now also listens

Two releases ago, infrared became a first-class citizen of Home Assistant, but as a one-way street: Home Assistant could send commands to your TV or air conditioner, but it had no way to hear what the device, or its original remote, was doing. The most asked-for follow-up was simple: “can Home Assistant also listen?” 📡

In this release, it does.

The Infrared platform gains a new receiver event entityEvents are signals that are emitted when something happens, for example, when a user presses a physical button like a doorbell or when a button on a remote control is pressed. [Learn more]. Any transmitter integration that supports it can expose the IR commands it picks up as events in Home Assistant, ready to drive automations just like any other event trigger. ESPHome is the first transmitter integration on board, so any ESPHome device with an IR receiver wired up can now act as an IR listener for your whole house. On the device side, LG Infrared is the first device integration to use it, exposing the commands its receiver sees as events you can react to.

This means you can keep Home Assistant in sync with the original remote: use the remote that came with the device, and Home Assistant sees it happen instead of being left in the dark with stale state. It also opens the door for future integrations to do more with what they hear, like turning a spare IR remote into a Home Assistant controller.

This is the second half of the infrared story we started two releases ago, making infrared a true two-way platform in Home Assistant. It also closes out the Open Home Foundation roadmap opportunity that set out to make infrared a two-way platform in Home Assistant.

Polishing the automation editor

Ever since Home Assistant 2025.12 introduced purpose-specific triggers and conditions, every release has nudged the automation editor a little closer to how you actually think about your home. The work in Labs is ongoing, and feedback keeps pouring in. While we keep iterating there, the rest of the automation editor has been getting some love too. ✨

Purpose-specific triggers and conditions

The Labs preview keeps growing, both in capabilities and polish. This release picks up where last month left off: the cross-domain successors to the old Person and Device Tracker home triggers and conditions have landed, this time built around zones. 📍

Four new zone triggers and four new zone conditions cover the same ground the removed entered_home, left_home, is_home, and is_not_home building blocks did, but in a more flexible way:

• Triggers to react when a person or device trackerDevice trackers are used to track the presence, or location, of a device. [Learn more] enters or leaves a zoneZones allow you to specify certain regions on a map. They enable zone presence-detection and can be used in automations. For example, to start the vacuum after you left home or start the heating at home when you leave the office. [Learn more], and when a zone becomes occupied or empty.
• Conditions to check whether a person or device tracker is in or not in a zone, or whether a zone is currently occupied or not.

You’re no longer limited to your home zone: any zone you’ve defined works, so reacting to someone arriving at work, school, or the gym is just as straightforward. Both triggers and conditions support the for duration field added last release, so you can wait until someone has actually settled in (or out) before doing anything.

We’ve also been busy giving the existing triggers and conditions the documentation they deserve. About half of the purpose-specific triggers and conditions now have their own dedicated reference page over at triggers and conditions, with examples, options, and the small details that make a real difference when you are wiring things up. The rest are on their way.

Haven’t tried them yet? Now is a great time. Enable the feature at Settings > System > Labs, give it a spin, and let us know what you think. The more feedback we collect, the sooner we can graduate this out of Labs.

See exactly how many things an automation targets

When you build an automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] that acts on a 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], an areaAn area in Home Assistant is a logical grouping of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage. [Learn more], a labelLabels 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], or a device, the editor used to just show the name of that target. So “Bedrooms” could mean three lights, or thirty, with no way to tell at a glance.

Now every floor, area, device, and label pill in your automation rows shows the number of entities it expands to, right next to its name. If your target selector also filters by domain or device class, the count reflects that filter, so what you see is what the action will actually touch. Select the pill for a quick peek at exactly which entities are included.

It is the kind of small detail that turns “I hope this only hits the right lights” into “yep, twelve, that’s correct”, especially handy as your home grows or you start using labels across rooms.

See at a glance which conditions pass

Conditions are the gatekeepers of your automations. They decide whether something runs or not, and when an automation doesn’t fire the way you expected, the first question is usually: “which condition was actually blocking it?” Until now, finding out meant testing each condition one by one, or waiting for the next run and digging through the trace afterwards.

The automation editor now tells you right there, while you are editing. Every condition row shows a small live test indicator as a badge on its icon that updates in real time as your home changes:

• A green check when the condition currently passes
• A red circle when it doesn’t
• A neutral state when the condition is incomplete or can’t be evaluated yet
• A clear error indicator, with the full message in a tooltip, when the configuration is invalid

Hover the icon to see exactly what the condition is reporting. Edit the condition, and the badge updates immediately, so you can dial in thresholds, zones, or state matches and see the result without leaving the editor. The same indicators also show up on dashboard visibility conditions, so the cards you hide or show conditionally tell you the same story.

This is part of a broader roadmap effort to bring home context into the automation editor: surfacing the information you need to build and debug automations right where you are working on them.

Add notes to any step in your automation

Aliases are great for renaming a trigger or action, but they have always been a single line, and they double as the label you see in the row. So if you wanted to explain why a step exists (“the porch sensor sometimes triggers on its own in winter, so this waits a few seconds to make sure”), you were out of luck without dropping into YAML.

Every triggerA trigger is a set of values or conditions of a platform that are defined to cause an automation to run. [Learn more], conditionConditions are an optional part of an automation that will prevent an action from firing if they are not met. [Learn more], actionActions 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], option, and scriptScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more] field now has a dedicated Notes field, separate from its name. Open the step’s sidebar, jot down whatever future-you needs to know, and it stays with that step forever. We deliberately called it notes and not comments to keep it clear from YAML comments, which are a different thing entirely.

Notes travel with the automation when you duplicate, export, or share it as a blueprintA blueprint is a script, automation, or template entity configuration with certain parts marked as configurable. This allows you to create multiple scripts, automations, or template entities based on the same blueprint, with each having its own configuration-specific settings. Blueprints are shared by the community on the blueprints exchange in the forum. [Learn more], so the reasoning behind a setup is no longer something only the original author remembers.

Tile card features

The tile card keeps growing into one of the most capable building blocks in your dashboards. This release adds two brand-new card features for weather entities and a generous round of additions to the media player tile.

Your forecast, right where you check the weather

Most of us already have a weather tile sitting somewhere on a dashboard. Up until now, the moment you wanted to know what tomorrow looks like, you had to open the more info dialog, jump to a different card, or build a whole forecast section just for that. No more.

Two new tile card features put the forecast directly onto your existing weather tile:

• Temperature forecast draws a bar chart of high and low temperatures for the days ahead, colored from cool cyan to deep red so you can read the week at a glance. In the hourly view, it renders as a smooth filled curve.
• Precipitation forecast shows how much rain (or snow) is expected for each slot, or, when your weather service only provides it, the chance of precipitation.

Both features automatically pick the best forecast resolution your weather service offers (daily, twice-daily, or hourly), and you can pin a specific resolution or toggle the day and hour labels from the card editor. One small change, big difference: your dashboard now answers the next question before you ask it.

Turning the media player tile into a real remote

Last release was a big step for the media player tile: a proper source picker, a sound mode picker, and playback buttons you could finally pick and reorder. Lots of you ran with it and built beautiful, focused media controls on your dashboards, and some of you immediately came back with: “this is great, but can it also…” 🎶

This release fills in those last gaps. Across the media player tile card features, you now have:

• A Mute button on both the Volume slider and Volume buttons features, so you can silence the room straight from the tile.
• Shuffle, Repeat, Volume up, Volume down, and Mute as extra controls you can mix into the Playback feature, alongside the existing transport buttons.
• A filter for the Source and Sound mode dropdowns, so a receiver that reports two dozen inputs only shows the three you actually use.

The result: a single tile that looks like, and acts like, a remote built specifically for that device. No more “almost right” tiles, no more falling back to the more info dialog for that one button you really need. Your Music Assistant setup is going to feel right at home. Thanks, @pcan08 and @MindFreeze!

Z-Wave smart lock credential management

Two releases ago, we added credential management for MatterMatter is an open-source standard that defines how to control smart home devices on a Wi-Fi or Thread network. [Learn more] smart locks: a friendly dialog to add, edit, and remove the users (and the PIN codes that go with them) that your lock accepts, without ever opening the lock’s own app. This release, Z-Wave smart locks get the same treatment. 🔐

Open your lock from the device page and select Manage access from the menu to get an overview of every user the lock has, and the credentials assigned to them. From there, you can add a new user, give existing ones extra credentials, edit them, or remove them. If you try to reuse a PIN that is already in use on the lock, the dialog will warn you instead of silently overwriting it. Everything happens directly between Home Assistant and your lock over Z-Wave; no cloud account, no vendor app, no internet connection required.

There is one small difference with the Matter version that plays to Z-Wave’s strengths: both PIN codes and passwords are supported, where the lock supports them. PIN codes are limited to digits (the familiar keypad experience), while passwords accept the full character set for locks with an alphanumeric keypad.

Just like the Matter equivalent, every action behind the dialog is also available as a regular Home Assistant actionActions 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]. That means you can hand out a one-time PIN to a guest from an automation, rotate codes on a schedule, or wipe a lost user with a single button press on your dashboard.

A fresh look for the Apps page

Apps (previously known as add-ons) are how you extend the system that Home Assistant runs on with extra software, like a media server, an MQTT broker, a VPN, or a code editor, all running right next to Home Assistant on the same device.

This release gives the Apps page a friendlier, more modern look. Every installed app is shown as its own card with its icon, name, a short description, and a clear indicator of whether it is running, so you can spot the state of your apps at a glance.

Installed apps can now also carry small tags that highlight what they are, making it easier to scan your list and find what you are looking for. The app detail page got the same care, with a cleaner layout that also works well on a tablet.

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:

• AiDot, added by @s1eedz
  Control your AiDot Wi-Fi smart lights, including A19 and BR30 bulbs, directly from Home Assistant. Communication happens locally over your network, so no cloud connection is required.

• CentriConnect/MyPropane, added by @gresrun
  Keep an eye on your propane tank from Home Assistant. The integration connects to the centriconnect.com cloud service to expose the level and status of tanks equipped with a MyPropane monitor, perfect for getting a notification before you run out.

• Cielo Home, added by @ihsan-cielo
  Control your Cielo smart air conditioner and heat pump controllers from Home Assistant, contributed by Cielo themselves. Connects through the Cielo Connect cloud API and exposes each device as a climate entity, so you can adjust modes and temperatures alongside the rest of your home automations.

• Data Grand Lyon, added by @Crocmagnon — launching at 🏆 platinum quality
  Bring open data from the city of Lyon, France, into Home Assistant. Track upcoming departure times at TCL public transit stops, and monitor real-time bike and dock availability at Vélo’v bike-sharing stations.

• Guntamatic, added by @JensTimmerman — launching at 🥈 silver quality
  Monitor your Guntamatic wood or pellet heater locally from Home Assistant. The integration reads sensor data directly from the heater’s web interface over your local network, with no cloud account needed.

• LG TV via Serial, added by @balloob — launching at 🥈 silver quality
  Control your LG TV locally from Home Assistant over its built-in RS-232 serial port. Works through a direct serial cable, a USB-to-serial adapter, or an ESPHome-based serial proxy, giving you a reliable connection that even works while the TV is in standby. Great for older sets without smart features and for commercial signage displays.

• Marantz Infrared, added by @balloob — launching at 🥈 silver quality
  Control your Marantz amplifier with any infrared transmitter you already have set up in Home Assistant. Built on top of the Infrared entity platform, so you can pair it with an ESPHome device with an IR LED, or any other supported IR emitter, and operate your amplifier without depending on the network or cloud.

• Mitsubishi Comfort, added by @nikolairahimi
  Bring Mitsubishi Electric ductless minisplit heat pump and air conditioning systems into Home Assistant. The integration talks directly to each indoor unit over your local network for low-latency control, and only uses the Kumo Cloud account for the initial device discovery and credential retrieval. Kumo Station outdoor units are supported for temperature monitoring.

• Ouman EH-800, added by @Markus98
  Connect your Ouman EH-800 heating controller to Home Assistant. Monitor and control your heating system locally with climate, number, select, sensor, and valve entities, perfect for automating your home’s heat distribution.

• OVHcloud AI Endpoints, added by @Crocmagnon Add a conversation agent powered by OVHcloud AI Endpoints to Home Assistant. Pick from a curated catalog of open-weight large language models hosted in Europe, and use them with Assist to control your home and answer questions.

• PAJ GPS, added by @skipperro
  Track the location of your PAJ GPS devices on the map in Home Assistant. The integration creates a device tracker entity for each tracker in your PAJ account, so you can build automations around their location, like notifications when a tracker arrives home or leaves a zone.

• PTDevices, added by @frogman85978
  Monitor your PTLevel water level sensors in Home Assistant. Get notifications when tanks run low or are being used unexpectedly, and build automations to turn off pumps when levels drop or run appliances once water has been delivered.

• Samsung Infrared, added by @lmaertin
  Control your Samsung TV with any infrared transmitter you already have set up in Home Assistant. Like the Marantz Infrared integration, it builds on the Infrared entity platform, so you can use an ESPHome device with an IR LED, or any other supported IR emitter, to operate your TV.

• Vistapool, added by @fdebrus Monitor and control your Hayward-branded pool controllers from Home Assistant, including AquaRite, Vistapool, Sugar Valley, Poolwatch, Kripsol, and Dagen devices. The integration uses the official Hayward cloud API with real-time push updates, so changes show up instantly without polling.

• Xthings Cloud, added by @zhangluofeng
  Control your Xthings smart home devices, starting with the U-tec Bright A19 Color smart light bulb, through the Xthings Cloud service. Contributed by Xthings themselves, with real-time status updates delivered over WebSocket push, so the state in Home Assistant stays in sync with what’s happening on your devices.

• Yoto, added by @piitaya
  Control your Yoto audio players from Home Assistant. Play and pause cards, change the volume, skip and seek tracks, and see what is currently playing. The integration connects to your Yoto account and receives live playback updates, so changes that happen on the player show up in Home Assistant almost immediately.

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:

• MQTT picked up two improvements: a new message expiry interval option, and subentry support extended to the date, datetime, and time entity platforms. Thanks, @jbouwh!
• Shelly now exposes an occupancy binary sensor. Thanks, @bieniu!
• Sonos got search, so you can now find tracks, albums, and artists across your music services straight from Home Assistant. Thanks, @PeteRager!
• Reolink battery cameras can now connect directly to Home Assistant, without needing a Reolink Home Hub or NVR as a bridge. Not all models and features are supported yet; using a Home Hub or NVR remains the preferred method. A battery camera cannot be connected both ways at the same time. Thanks, @starkillerOG!
• Tuya received a wave of device-specific improvements: number entities and fault codes for the Pro Breeze OmniDr dehumidifier, water-timer data points and a countdown number for the sfkzq single-valve timers, additional entities for cameras, a number entity for the WG2 alarm panel (Duosmart C30), total production sensor support for SPM02 devices, and support for the InverGo inverter pool heat pump. Thanks, @peterlang-p, @mik-laj, @davidXire, @tbouron, @ChayoteJarocho, and @focabr!
• SwitchBot had a great release with broad device support: the Permanent Outdoor Light, Weather Station, and Lock Vision (Pro) / Lock Pro Wifi are now supported, the Meter CO2 gained a display time offset number entity, and the Air Purifier now exposes its LED settings. Thanks, @elgris, @Onero-testdev, and @zerzhang!
• SmartThings TVs now let you select the input source, and Copper water meters expose their sensors. Thanks, @felipecrs and @joostlek!
• Alexa Devices got two big additions: a new media player platform that exposes your Echo devices as media players, with playback, volume, and mute controls, and a new event entity that surfaces the voice commands your Echo hears so you can react to them in automations. Thanks, @jamesonuk and @chemelli74!
• Anthropic Claude conversations now support the web fetch tool, allowing the model to retrieve and reason about live web content. Thanks, @Shulyaka!
• Google Nest added a nest.set_fan_timer action, so you can script your thermostat’s fan timer right from Home Assistant. Thanks, @tronikos!
• HomeWizard updated charging strategies with support for their new smart charging feature, and two new battery group sensors: target power and group power. Thanks, @DCSBL!
• UniFi Protect added an alarm profile select entity, letting you switch between alarm profiles directly from Home Assistant. Thanks, @RaHehl!
• FRITZ!SmartHome now ships data descriptions for all configuration fields, making setup easier to understand. Thanks, @mib1185!
• Viessmann ViCare RadiatorActuator devices now expose a target temperature sensor. Thanks, @lackas!
• Cambridge Audio receivers now expose a volume limit, so you can prevent overly loud playback. Thanks, @noahhusby!
• Nord Pool picked up a binary sensor for price-based automations. Thanks, @gjohansson-ST!
• YouTube channels now expose a video count sensor. Thanks, @nathan-osman!
• OneDrive added a delete action so you can clean up files from your automations. Thanks, @leodrivera!
• WeatherFlow Cloud stations now expose dedicated station-level sensors. Thanks, @jeeftor!
• Portainer continues to grow: new system health and disk space coordinators, and recreate-container service actions. Thanks, @erwindouna!
• Ohme EV chargers got two new controls: a state of charge input number and a solar boost switch. Thanks, @dan-r!
• Jewish Calendar now exposes a calendar entity, perfect for tracking Jewish holidays and Shabbat in your dashboards and automations. Thanks, @tsvi!
• BleBox picked up several improvements: a new update platform that exposes installed and latest firmware versions and lets you trigger firmware updates straight from Home Assistant, plus tilt-only mode and 180-degree tilt support for cover and shutter entities. Thanks, @bkobus-bbx!
• PrusaLink 3D printers gained more sensors: X/Y axis position, location, minimum extrusion temperature, plus SD ready, farm mode, and connection status binary sensors. Thanks, @heikkih!
• System Bridge gained a notify entity, so you can send desktop notifications from your automations. Thanks, @tr4nt0r!
• Indevolt battery support expanded significantly with new battery temperature, MOS temperature, main MOS temperature, cycle count, transformer temperature, and real-time control sensors. Thanks, @Xirt and @karlbeecken!
• Qube heat pump added a water heater entity for domestic hot water control (with a boost mode for using surplus energy), plus switches for summer mode, anti-legionella cycle, heating curve, and heating demand. Thanks, @MattieGit!
• Eurotronic Comet Blue thermostats added a number platform exposing the eco and comfort setpoints and the temperature offset, so you can fine-tune your schedule without leaving the dashboard. Thanks, @rikroe!
• Elk-M1 Control picked up dedicated number entities for the Elk’s configurable settings (such as timers), previously buried inside a single sensor. Thanks, @gwww!
• Control4 now supports motorized window treatments through a new cover platform. Thanks, @nayfield!
• IMGW-PIB added river vegetation cover sensors for emergent, floating, and submerged vegetation. Disabled by default, so you can enable just the ones you need. Thanks, @bieniu!
• Watts Vision + received HVAC action and preset mode support, plus a new timer mode service. Thanks, @theobld-ww!
• Kiosker gained a switch to disable the screensaver, plus a set of buttons for common kiosk actions: navigate forward, backward, and home; clear cache and cookies; print; ping; and interact with the screensaver. Thanks, @Claeysson!
• V2C EV chargers now expose their LED lights. Thanks, @dgomes!
• Lunatone DALI lighting controllers now expose their device status as sensors. Thanks, @MoonDevLT!
• Satel Integra alarm zones now expose temperature sensors. Thanks, @Tommatheussen!
• Template entities now support the device tracker platform, giving you a modern replacement for the device_tracker.see action that was deprecated last release. Thanks, @Petro31!

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:

• 4 integrations reached platinum 🏆

  • Casper Glow, thanks to @mikeodr
  • Indevolt, thanks to @Xirt
  • Tailwind, thanks to @frenck
  • UptimeRobot, thanks to @chemelli74

• 1 integration reached gold 🥇

  • Novy Cooker Hood, thanks to @piitaya

• 1 integration reached silver 🥈

  • Jandy iAquaLink, thanks to @flz

• 2 integrations reached bronze 🥉

  • Nobø Ecohub, thanks to @oyvindwe
  • Zeversolar, thanks to @mhuiskes

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:

• Elgato Avea, done by @pattyland
• openSenseMap, done by @AlCalzone
• OPNsense, done by @HarlemSquirrel

Farewell to the following

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

• Konnected has been removed. The legacy Konnected.io integration was deprecated in Home Assistant 2025.10 and is now removed. To keep using your Konnected hardware, follow the migration guide from Konnected to flash your device with ESPHome firmware.

Other noteworthy changes

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

• A friendlier setup for MatterMatter is an open-source standard that defines how to control smart home devices on a Wi-Fi or Thread network. [Learn more] devices. When you add any Matter device, Home Assistant now asks you to name it and assign it to an area right away, so it is ready to use the way you intend from the first moment. For contact sensors and covers, you can also pick what the device is attached to (a door, window, garage door, or something else). On iOS, the pre-filled name and device class selection require an upcoming iOS app update; until then, the previous behavior is used.
• OpenThread Border Router 1.4 is out of beta. The OpenThread Border Router app now ships ThreadThread is a low-power mesh networking standard that is specifically designed for smart home applications. It is a protocol that defines how devices communicate. [Learn more] 1.4 by default, no beta toggle required. For now, this is mostly about bug fixes and stability, including the new built-in mDNS implementation from OpenThread, which should help resolve a class of stubborn Thread connectivity issues that previously traced back to mDNS quirks in some home routers. It also lays the groundwork for bringing the new Thread 1.4 features to Home Assistant in the near future.
• Sirens join the Matter integration. Matter sirens (like Heiman-style smoke detectors that double as a loud alarm) are now exposed as proper siren 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] you can switch on and off from automations and dashboards. Thanks, @lboue! 🚨
• Bluetooth proxies are now much friendlier to battery-powered devices. Until now, every Bluetooth scanner ran in active mode, constantly polling devices and waking up your battery-powered Bluetooth sensors and trackers more often than they need to. Starting this release, the default for both the Bluetooth integration and ESPHome Bluetooth proxies is the new Auto mode, which switches to active scanning only when an integration actually needs it, and only on one scanner at a time. The result: around 95–96% less battery used for Bluetooth scanning, while everything keeps working the way it did. The Bluetooth UI catches up too, labeling each adapter as Auto (active) or Auto (passive), and the device info dialog gained a Raw advertisement field for debugging. More on the default change in the backward-incompatible changes section.
• Firmware version in the devices table. The Devices page gets a hidden-by-default Firmware column you can switch on from the table options, making it easy to check whether a firmware update actually landed without changing the default layout. Thanks, @markvp!
• A friendlier ZHA group page. The ZHA group create and edit screens have been rebuilt around a compact, card-based layout that keeps your devices and group settings visible together, instead of one long table you had to scroll through. Thanks, @jpbede!
• Search by label in more places. The data tables for helpersA helper is a virtual entity you create inside Home Assistant. It is not backed by a physical device. Helpers store values, track state, or do calculations that your automations and dashboards need. [Learn more], automations, scenes, and scripts now let you filter by labelLabels 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], matching the search bar that devices and entities already had. Thanks, @ildar170975!
• The backup encryption key is harder to miss. Home Assistant already creates a backupHome Assistant has built-in functionality to create files containing a copy of your configuration. This can be used to restore your Home Assistant as well as migrate to a new system. The backup feature is available for all installation types. [Learn more] automatically before every update, but that backup is only useful if you can still decrypt it. The Backup settings page has been reorganized to put your encryption key front and center, with a clear reminder to save it somewhere safe. Losing that key is one of the most painful ways to lose access to a backup, so we want to make sure you don’t.
• Color customization for graph cards. The statistics graph card and history graph card now let you pick a custom color per entity, both from the visual editor and in YAML. Thanks, @ildar170975!
• Advanced mode is gone. The Advanced mode toggle on your user profile, and every feature that used to hide behind it, is now retired. We have been peeling away its gates release by release; this release finishes the job. A single toggle was never a great fit: it bundled unrelated features together and quietly suggested some parts of Home Assistant were only for “advanced” users. Neither is true. Everything that used to live behind it is now simply available to everyone by default. More background in the Open Home Foundation roadmap.

A clearer view of your home’s energy

Two quality-of-life upgrades land in the energy dashboard this release. ⚡

If you have a home battery, you can now hook up its state-of-charge sensor (the percentage one) right from Settings > Dashboards > Energy. Once it is set, the Battery node on the energy distribution card shows the current charge level alongside the energy flowing in and out, and a matching battery badge appears at the top of the energy panel so you can see at a glance how full your battery is, without leaving the dashboard. Thanks, @MindFreeze!

The other addition is small but long-requested: you can now give your grid, solar, battery, gas, and water sources a custom name in the energy configuration. So instead of “Grid consumption” and “Grid return”, you can call them “Main meter” and “Solar export”, or whatever makes sense for your home. The names flow through to the cards, charts, and statistics, making multi-source setups (like a separate EV meter or a second water tap) far easier to tell apart. Thanks, @karwosts!

Quick links between everything you care about

Home Assistant is full of things that are related to each other: a device has entities, those entities show up in automations and scripts, automations live in areas, areas have labels, and so on. Getting from one to the next used to mean a lot of back-and-forth between settings pages.

This release threads a generous set of quick links through those views so you can jump straight to the related thing, or create a new one without losing your place:

• Device pages now bundle related automations, scriptsScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more], and scenesScenes capture the states you want certain entities to be. For example, a scene can specify that light A should be turned on and light B should be bright red. [Learn more] into a single Related card (instead of three separate ones), and the existing quick links section gains shortcuts to all the other places that reference the device.
• Area pages got the same treatment, with quick links into the tables and dashboards that already filter by that area in a single step.
• From an entity, device, or area, you can now create a new automation or script with that target already wired into a trigger, condition, or action, no copy-pasting entity IDs required. (This piece rides on top of the purpose-specific triggers and conditions Labs preview, so enable it at Settings > System > Labs to see the option.)
• Label navigation actions now include scenes and scripts alongside automations, so a label like “morning routine” surfaces everything tagged with it, not just a subset.

Individually these are small. Together they make Home Assistant feel even more connected than it already was, with fewer detours between the pages. Thanks, @timmo001!

YAML linting inside the UI editors

A small quality-of-life improvement that should not go unnoticed. You don’t need to know or use YAML to use Home Assistant, but if you like it, or want to dive into more specific use cases, we give you the power to do so.

The YAML code editors throughout the UI now show inline linting: missing colons, unmatched quotes, and yes, that one space too many or too few in your indentation (we know, we know 😅), are all highlighted as you type, right next to the line that causes them. No more saving, hitting an obscure error, and scrolling back to find the cause.

Patch releases

We also release patch releases for Home Assistant Core. These patch releases are released on a weekly basis (on Fridays) and contain bug fixes and small improvements.

2026.6.1 - June 5

• Fix Lyric sensor crash when next_period_time is None (@bk86a - #167831)
• Fix SleepIQ 401 storm by isolating client session cookies (@Stormalong - #172276)
• Upgrade HomeLink package, set integration type (@rjones-gentex - #172371)
• Bump actron-neo-api to 0.5.12 (@kclif9 - #172902)
• Switchbot Cloud: Fixed an issue where condition filtering for enabled Webhooks was abnormal (@XiaoLing-git - #172903)
• Bump aioautomower to 2.7.6 (@Thomas55555 - #172937)
• Add more Reolink diagnostic info (@starkillerOG - #172945)
• Fix Mitsubishi Comfort devices skipped due to unresolved local address (@nikolairahimi - #172959)
• Bump idasen-ha to 2.7.0 (@abmantis - #172962)
• Fix value template in MQTT Fan and Siren subentry setup (@jbouwh - #172980)
• Improve person tests (@emontnemery - #172997)
• Bump imgw_pib to 2.2.2 (@bieniu - #172999)
• Fix person in_zones propagation from scanner in home zone (@emontnemery - #173007)
• Bump holidays to 0.98 (@gjohansson-ST - #173029)
• Portainer extend timeout for disk space coordinator (@erwindouna - #173032)
• Convert LinkPlay configuration_url to string for device registry (@frenck - #173034)
• Fix Duco mode end time sensor name (@ronaldvdmeer - #173045)
• Unify query token auth in http views (@edenhaus - #173082)
• Create certificate files before trying to migrate the MQTT config entry (@jbouwh - #173087)
• Bump wheels to 2026.06.0 (@edenhaus - #173089)
• Bump pySmartThings to 4.0.1 (@joostlek - #173092)
• Bump yoto-api to 3.1.6 (@piitaya - #173104)
• Bump aiostreammagic to 2.13.2 (@noahhusby - #173114)
• Fix process advertisement for active scans (@elupus - #173116)

2026.6.2 - June 9

• Update PARALLEL_UPDATES to 0 for Squeezebox platforms (@peteS-UK - #172906)
• Bump pyyardian to 1.4.0 (@aeon-matrix - #173020)
• Bump pytrydan to v1.0.1 (@dgomes - #173047)
• Improve and complete exception handling for Alexa Devices (@chemelli74 - #173053)
• Switch to active scanner for gardena (@elupus - #173062)
• Bump opower to 0.18.3 (@tronikos - #173141)
• Bump plugwise to v1.11.4 (@bouwew - #173147)
• Ensure opentherm_gw boiler and thermostat manufacturers are strings (@mvn23 - #173162)
• Wait for ESPHome bluetooth proxy connection at startup (@bdraco - #173164)
• Wait for Shelly bluetooth proxy connection at startup (@bdraco - #173165)
• Have Plugwise handle unavailable temperature measurements (@joostlek - #173173)
• Fix Shelly virtual component unit retrieval (@thecode - #173183)
• Adjust ONVIF event fallbacks for battery cameras (@starkillerOG - #173214)
• Update frontend to 20260527.5 (@bramkragten - #173236)
• Bump pydaikin to 2.18.1 (@purcell-lab - #173249)
• Fix homeassistant hardware unique id migration (@MartinHjelmare - #173258)
• Bump renault-api to 0.5.12 (@chemelli74 - #173289)
• Mitigate TTS ResultStream leak in pipeline (@synesthesiam - #173290)
• Ensure we provide strings to vol.In for philips js (@elupus - #173313)
• Bump opower to 0.18.4 (@tronikos - #173323)
• Fix reload fails when MQTT entry is not set up (@jbouwh - #173335)
• Handle unavailable Zinvolt devices better (@joostlek - #173359)
• Bump mitsubishi-comfort to 0.3.1 (@nikolairahimi - #173362)
• Set Zinvolt max output to 2kW if unlocked (@joostlek - #173367)
• Only allow specific protocols with ffmpeg in Wyoming satellite announce (@synesthesiam - #173381)

2026.6.3 - June 12

• Add debug logging for Mitsubishi Comfort polling failures (@nikolairahimi - #173364)
• Do not enable MQTT entities though discovery that were disabled by user (@jbouwh - #173404)
• Change update interval for UptimeRobot (@chemelli74 - #173435)
• Redact more fields in diagnostics for Alexa devices (@chemelli74 - #173446)
• Fix UniFi Protect ufp_set debug log printing UndefinedType for translation-key entities (@heytcass - #173460)
• Revert “Unify query token auth in http views” (@edenhaus - #173466)
• Bump reolink_aio to 0.21.0 (@starkillerOG - #173477)
• Bump aioamazondevices to 14.0.3 (@chemelli74 - #173478)
• Bump pytrydan to 1.0.2 (@dgomes - #173479)
• Bump hassil to 3.6.0 (@synesthesiam - #173031)
• Update hassil to 3.7.0 (#173484)
• Refresh preferred Thread border agent address on OTBR reconnect (@agners - #173508)
• Update frontend to 20260527.6 (@bramkragten - #173522)
• Bump bthome-ble to 3.23.4 (@Ernst79 - #173526)
• Fix Hue light level sensor crash on None value (@frenck - #173532)
• Fix Hue grouped light icon by adding translation_key (@frenck - #173536)
• Fix iCloud RuntimeError on unload by running cancel in executor (@frenck - #173537)
• Convert JPEG-incompatible image modes to RGB in image upload thumbnail generation (@frenck - #173538)
• Convert RainMachine hw_version to string for device registry (@frenck - #173545)
• Convert OpenGarage sw_version to string for device registry (@frenck - #173546)
• Fix Yale Smart Living panic button unique_id for multiple hubs (@frenck - #173547)
• Suppress InsecureKeyLengthWarning in HTML5 push notifications (@frenck - #173551)
• Fix Rituals Perfume Genie sw_version dict passed to device registry (@frenck - #173552)
• Return enum values from config_entry_attr template function (@frenck - #173554)
• Sort aliases in LLM prompts for stable prefix caching (@frenck - #173558)
• Disambiguate duplicate channel names in LG Netcast source list (@frenck - #173560)

2026.6.4 - June 19

• Fix Growatt total_output_power 1000x too low with V1 API (@johanzander - #172474)
• Solve issue with double slash in url when writing data to InfluxDB (@RobBie1221 - #173395)
• Avoid leaking Immich API key in error logs (@frenck - #173541)
• Stop validating # of slots in zwave_js.set_credential action (@raman325 - #173644)
• Add missing Miele dishwasher codes (@astrandb - #173662)
• Bump aiodiscover to 3.3.1 (@bdraco - #172882)
• Bump aiodiscover to 3.3.2 (@bdraco - #173705)
• Skip Miele fan set_percentage when already at the target step (@frenck - #173725)
• Add missing flow form field translation in tuya (@frenck - #173745)
• Add missing flow form field translation in flux_led (@frenck - #173746)
• Add missing flow form field translation in hue (@frenck - #173747)
• Bump lxml to 6.1.1 (@gjohansson-ST - #173748)
• Add missing flow form field translations in islamic_prayer_times (@frenck - #173749)
• Add missing flow form field translation in lacrosse_view (@frenck - #173750)
• Fix flow form field translation key in lookin (@frenck - #173751)
• Add missing flow form field translation in melnor (@frenck - #173752)
• Add missing flow form field translation in gogogate2 (@frenck - #173753)
• Fix flow form field translation key in meteoclimatic (@frenck - #173754)
• Fix options flow form field translation key in plaato (@frenck - #173755)
• Add missing flow form field translation in blink (@frenck - #173756)
• Add missing flow form field translation in motionblinds_ble (@frenck - #173758)
• Add missing flow form field translation in snooz (@frenck - #173760)
• Bump aioamazondevices to 14.0.4 (@frenck - #173761)
• Bump pyrainbird to 6.3.1 (@frenck - #173786)
• Bump pyituran to 0.1.6 (@shmuelzon - #173833)
• Add API_GEN_4 support to Subaru integration (@jpettitt - #173956)
• Fix flow form field translation keys in here_travel_time (@frenck - #173992)
• Fix flow form field translations in hlk_sw16 (@frenck - #173993)
• Add missing flow form field translation in otp (@frenck - #173994)
• Add missing flow form field translation in honeywell (@frenck - #173996)
• Fix flow form field translations in local_calendar (@frenck - #173997)
• Fix flow form field translation key in sia (@frenck - #173998)
• Fix flow form field translations in modem_callerid (@frenck - #173999)
• Add missing flow form field translation in airvisual (@frenck - #174000)
• Add missing flow form field translations in ecobee (@frenck - #174002)
• Add missing flow form field translation in iskra (@frenck - #174004)
• Add missing flow form field translations in tractive (@frenck - #174005)
• Add missing subentry flow translations in scrape (@frenck - #174006)
• Fix MQTT discovery option unjustly added to entry data (@jbouwh - #174073)
• Cast numeric firmware to string for squeezebox hw_version (@frenck - #174076)
• Retry webdav setup on connection errors (@frenck - #174077)
• Bump opower to 0.18.5 (@frenck - #174080)
• Cast system version to string for simplisafe device model (@frenck - #174081)
• Filter out closed sites in Amber Electric config flow (@frenck - #174084)
• Bump aioamazondevices to 14.1.2 (@chemelli74 - #174114)
• Fix stale routine entities removal for Alexa Devices (@chemelli74 - #174138)
• Bump aioamazondevices to 14.1.3 (@chemelli74 - #174158)
• Cast SwitchBot Cloud device sw_version to string (@gaborbernat - #174167)
• Bump aiocomelit to 2.0.5 (@frenck - #173800)
• Bump aiocomelit to 2.0.7 (@chemelli74 - #174183)
• Update max prebrew numbers in lamarzocco (@zweckj - #174204)
• Fix Elk-M1 reconfigure failing when entry has no unique_id (@frenck - #174230)
• Include Sonos favorites in source list and gate SELECT_SOURCE dynamically (@frenck - #174231)
• Skip fill sensor for Rituals diffusers without fill data (@frenck - #174232)
• Handle Weheat API errors during config flow entry creation (@frenck - #174234)
• Re-raise non-401 HTTP errors in Tank Utility setup (@frenck - #174272)
• Fix econet fan mode select returning int instead of str (@frenck - #174274)
• Update frontend to 20260527.7 (@bramkragten - #174285)
• Cast Xiaomi Gateway sub-device firmware version to string (@frenck - #174294)
• Remove event entities from virtual groups for Alexa Devices (@chemelli74 - #174303)
• Bump pyroute2 to 0.9.6 (@bdraco - #172521)
• Bump aioimmich to 0.15.0 (@mib1185 - #174305)
• Bump dsmr-parser to 1.9.0 (@TheJulianJES - #174307)

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:

• BrowseMediaSource: domain is now required
• Changes to the condition and script APIs
• Custom card suggestions in the card picker
• Deprecating config entry listener with reloading methods in config flow
• Deprecation of advanced mode in data entry flow
• Format entity names in custom cards
• Frontend component updates in 2026.6
• MQTT publish API changes
• MQTT publish API supports message expiry interval

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

We’re sensing a change in the air this month as we welcome Sensereo to the Works with Home Assistant program 🎉. Specialists in environmental sensing, Sensereo brings Matter smoke and carbon monoxide (CO) alarms into the Home Assistant ecosystem – meaning more ways to keep your home open, safe, and sound.

Built from a burning question…

What happens if your smoke alarm goes off, but you’re not there to hear it? It’s an unsettling question, and one that led Roy Chen to found Sensereo in 2024. Driven to create safety devices that were equal parts reliable and resilient, Sensereo built the Matter-based MS-1 Smoke Alarm and MSC-1 Smoke and Carbon Monoxide Alarm, because as they put it: “every home deserves a system that will not fall silent when it matters most.”

It’s just good sense

For anyone unfamiliar, Matter is an open standard that lets smart home devices from different brands work together, regardless of who made them – no lock-in, no closed ecosystems. It’s exactly the kind of open, interoperable technology the Open Home Foundation exists to champion. Thread operates on the same principle: it’s an energy-efficient, wireless mesh network that connects devices directly to one another and can automatically reroute around disruptions. And for battery-powered alarms like Sensereo’s, Thread’s low-power design means fewer battery changes for devices that are always on duty.

While we’re talking about safety, it’s important to note that if your Thread network did for any reason drop out, Sensereo’s smoke and CO alarms will keep working as a “regular” alarm would – no smart home required.

That peace of mind is central to how Sensereo thinks about their products, and having caught up with the team at CES 2026 earlier this year, we can tell you it’s just the beginning. Air quality sensors and more are on the horizon, all building toward the same vision: to build an environmental intelligence system for the home that helps users understand and respond to their surroundings.

Devices

Most of us want our smoke alarms to be “reasonably annoying,” and Sensereo clearly agrees, because they printed this very description on the MS-1’s packaging. Which, as we love to see, has been designed sustainably – signaling the company’s commitment to one of the Open Home Foundation’s three core principles before you’ve even opened the box.

Sensereo MSC-1 smoke and carbon monoxide detector

The MSC-1 goes a step further with a nifty, built-in digital display showing real-time carbon monoxide levels. Since CO is odorless and invisible, being able to accurately check levels at a glance lets you know if there is a rise and act before it becomes an emergency – not just after an alarm sounds.

And with local integration, that kind of proactive awareness extends further still – allowing you to build around the people in your home, not just the devices. A smoke detection event could flash smart bulbs for a family member who’s hard of hearing, or send a separate alert to a caregiver. Your alarm does its job – and so does everything else around it. It’s this kind of thoughtful design that shows us Sensereo are here for all the right reasons.

• Sensereo MS-1 Smoke Alarm
• Sensereo MSC-1 Carbon Monoxide Alarm

Like all partners of the Works with Home Assistant program, Sensereo commits to providing long-term support and firmware updates, as well as staying connected to the community they’re helping protect 💪. As always, the MS-1 and MSC-1 have been rigorously tested and certified by our in-house team to meet our core requirements of local control, privacy, and long-term sustainability. The program’s operated by the Open Home Foundation, which is funded with the support of Home Assistant Cloud subscribers. With each new partner like Sensereo that expands the program, we’re able to give more choice, support, and peace of mind to Home Assistant users.

Breathe easy

No smoke and mirrors – just reliable home safety devices and a team that clearly gets what this community is about. Sensereo’s commitment to building open, locally controlled tech is fundamental to the Works with Home Assistant program, and why we’re so thrilled to have them on board. Check out our certified device list to see what else is there!

FAQs

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

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

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

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have the functionality you would expect within Home Assistant, operate locally without the need for cloud and that they 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 Home Assistant Connect ZBT-2 as the Thread Border Router and with our certified Matter integration. If you have another hub / border router set-up / integration that’s not a problem but we test against these as they are the most effective way for our team to certify within our ecosystem.

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

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

We are often asked if we prioritize “Big Tech” firms in the Works with program, but we’ve always been clear that newer companies are just as important to our certification as household names. Start-ups are innovators, and have their fingers on the pulse of community needs much more than brands that are only at the mercy of their investors.

That’s just one reason we’re thrilled to welcome zunzunbee to the program! They really stood out from the crowd at CES 2026 this January with their new product, the Slate Switch. This battery-powered smart scene controller simply snaps over existing switches – ideal if you rent your home, or don’t fancy working with wiring. We’re always on the lookout for devices that make setting up your smart home easier, so we’re delighted to have zunzunbee on board!

A clean slate for switches

While zunzunbee are newcomers to the market, founder Harish Raman has more than 18 years’ experience in lighting and connected systems – including senior engineering roles at Leviton and Philips. Harish designed the Slate Switch to cut the complexity sometimes found in smart homes, by bringing back simple, tactile control without any installation headaches. And because it builds on top of your existing switches rather than replacing them, it means less waste and more value from the things you already own.

Not just for newbies

The Slate Switch isn’t just a low-barrier entry point for beginners. It also tackles an issue that can crop up in more complex smart home setups: someone flipping a wall switch that controls your smart bulbs so all your carefully configured automations stop working 😩. Slate Switch keeps those bulbs permanently powered, while giving everyone in the household a familiar, physical button right where they expect it. If you prefer, you can also make use of the snap-on snap-off magnetic function to pick up the switch and take it with you. You can use it as a remote, and each of the zones can support both a tap or long-press action, making it a perfect partner to have in a pocket.

A cost-effective device is also a low-risk way to experiment, with plenty of possibilities to explore without a big outlay. And once you’re hooked, multipacks of two or four are available so you can roll them out across your home.

The right buzz

Two bs and a lot of zs: it’s no coincidence that zunzunbee uses Zigbee for the Slate Switch. If you’ve not heard of Zigbee before, it’s an open wireless standard built for low-power smart home devices – which describes the Slate Switch to a tee, since it runs on a single CR2450 coin cell with up to two years of battery life.

Zigbee works entirely locally with no dependency on the cloud, so your smart home stays in your hands and the Slate Switch keeps working even if you lose internet connection. If you want that same security and control when you’re away, Home Assistant Cloud offers fully encrypted remote access – and as an added bonus 😉 subscribing directly funds the Open Home Foundation’s fight for privacy, choice and sustainability for smart homes (and this very program too!).

By choosing Zigbee, zunzunbee support that fight… and they’ve been proactive contributors to our community as well. They’ve published official Home Assistant blueprints to make setup as smooth as possible, and contributed code to Zigbee2MQTT (another popular community-maintained open source project) on GitHub. It’s exactly what we love to see from our partners!

The Slate Switch simply snaps over your existing wall switches.

Devices

As with every device in the Works with Home Assistant program, the Slate Switch has been through our full certification process: tested for performance, reliability, and compatibility with our principles. By joining the program, zunzunbee also commits to providing long-term support and firmware updates, so you can purchase with confidence.

• zunzunbee Slate Switch

It may be just one small device, but it gives you mighty choice! 💪The Slate Switch arrives as a blank canvas, with two sheets of stickers so you can label and arrange up to eight tappable zones exactly how you want them, and reconfigure just as easily if your needs change. And it’s not only about switching scenes or triggers: there’s a built-in ambient temperature sensor in the switch too, opening up even more automation possibilities straight out of the box.

Jimmy over at the Automated House YouTube channel has a great hands-on walkthrough if you want to see it all in action.

Ready to make the switch?

We love it when a fresh idea from a new face lands in our orbit (and passes muster!) – and we have a feeling the Home Assistant community is going to have a lot of fun with this one. Whether you’re just dipping your toe into smart home control, or looking for new ways to push your existing setup further, the Slate Switch has you covered. Check out our certified device list to see what else is out there!

FAQs

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

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

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

A: It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have the functionality you would expect within Home Assistant, operate locally without the need for cloud, and that they 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 as a hub with the Home Assistant Connect ZBT-2, and with ZHA, our Zigbee integration. If you have another hub/adapter set-up/integration that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.

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

A: Why not! We’re thrilled to foster a close relationship with the team at zunzunbee and we’re excited to see how they grow their product line in the future. We’re looking forward to working together on any upcoming releases or adding in further products that are not yet listed here.

Home Assistant 2026.5! 🎉

What a few weeks it has been! Earlier this month, we hosted State of the Open Home 2026 live in Utrecht, the Netherlands. A big chunk of that day was dedicated to something we deeply care about: building in the open, and how we’re going to take that even further from here on out. 💙

Building in the open isn’t just about source code on GitHub. It’s about doing the planning, the decision-making, and the prioritizing out where everyone can see it, follow along, and join in. And “joining in” doesn’t mean you have to write a single line of code or even consider yourself technical. Sharing how you use Home Assistant, telling us what frustrates you, what you wish existed, voting on ideas, helping a fellow user on the forums or Discord, translating, writing documentation, or simply leaving a thoughtful comment on a roadmap item: it all counts, and it all shapes where this project goes next. 🤝

A great first step in that direction also went live this month: our roadmap is now public. You can go browse it, see what we’re working on, what’s next, and (most importantly) comment on it, share your thoughts, and help shape it. We talked about all of this, and a lot more, on stage. So if you weren’t able to join us live, please go watch the recording. It is genuinely worth your time, and it’s the best invitation I can give you to come build the Open Home with us. 🗺️

Now, on to this release. My personal favorite this month is maybe a bit unexpected, considering it sits all the way at the end of this post: the completely reworked templating documentation. I know, I know, “documentation” doesn’t exactly scream headline feature. But hear me out: making Home Assistant more approachable is one of our biggest missions this year, and darn good documentation is a big part of that. We’ve expanded our documentation team and are investing heavily in this, and the new templating docs are the very first taste of what’s to come. I’m really proud of where this is heading. 📚

That said, I’d be lying if I said I wasn’t also super stoked about radio frequency (RF) support landing this release. Just like last month’s infrared (IR) release, this brings a massive category of devices into Home Assistant natively: blinds, garage doors, ceiling fans, RF outlets, doorbells… you name it. Sure, there have always been clever workarounds and custom integrations to bridge some of these, but having it built right into the platform changes the game completely. There is so much cool stuff going on around this, and we’re only getting started. 📡

And there’s plenty more: a new Maintenance dashboard for your batteries, serial ports proxied over the network with ESPHome, new tile card features for media players, durations for purpose-specific automation triggers and conditions, redesigned more-info dialogs for vacuums and lawn mowers, autocomplete in the code editors, and 12 new integrations! 🚀

Enjoy the release!

../Frenck

• Radio frequency joins infrared as a first-class citizen
  • Meet the Radio frequency platform
  • Why this is a big deal
  • A sneak peek at what’s coming
• Serial ports over the network with ESPHome
  • Where this comes in handy
  • Under the hood
  • A first step, not the finish line
• More from your built-in dashboards
  • Stay on top of your batteries with the new Maintenance dashboard
  • Activity log on the Security dashboard
• More for the dashboards you build yourself
  • Introducing the shortcut card
  • New tile card features for media players
• Purpose-specific automation triggers & conditions
  • Automations that finally understand “for a while”
  • A few more triggers and conditions to play with
  • Changes to existing triggers and conditions
  • Try it out!
• 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
  • A modern more-info dialog for vacuums and lawn mowers
  • New styling for toggles
  • The templating documentation you’ve always wanted
  • Smarter code editors with autocomplete
• Need help? Join the community
• Backward-incompatible changes
• Patch releases
  • 2026.5.1 - May 8
  • 2026.5.2 - May 15
  • 2026.5.3 - May 19
  • 2026.5.4 - May 22
• All changes

A huge thank you to all the contributors who made this release possible! And a special shout-out to @piitaya who helped write the release notes this release. Also, @RaHehl, @balloob, @Tommatheussen, and @mib1185 for putting effort into improving its contents. Thanks to them, these release notes are in great shape. ❤️

Radio frequency joins infrared as a first-class citizen

Last release, we welcomed infrared as a first-class citizen of Home Assistant, opening the door to all those TVs, air conditioners, and other appliances still controlled by their little IR remote. This release continues that story with another old-school protocol: radio frequency (RF). 📡

Think about all the RF-controlled devices already living in your home: motorized blinds and curtains, garage door openers, ceiling fans, wireless wall switches, RF outlets, doorbells, and yes, those holiday string lights. Most of them haven’t had a great way into your smart home, because they don’t speak Wi-Fi, Bluetooth, Zigbee, Z-Wave, or Matter. They speak RF, and only RF. There have always been workarounds and custom integrations to bridge some of them, but with this release, Home Assistant speaks RF natively.

Meet the Radio frequency platform

The new Radio frequency integration follows the exact same pattern as last release’s infrared platform. It’s an entity type that represents an RF transmitter, like an ESPHome-powered device with a sub-GHz transmitter attached. You don’t set it up directly. Instead, other integrations use it to send RF commands on your behalf, and you simply pick which transmitter they should use.

Two transmitter integrations support this from day one:

• ESPHome, so any ESPHome device with a compatible sub-GHz transmitter can act as your home’s RF bridge. Most modules cover all common sub-GHz bands (315, 433, 868, and 915 MHz), so a single transmitter can talk to a wide range of devices. For DIY, we recommend the inexpensive CC1101 module (around $10), which you wire up to an ESP32 yourself. There’s a step-by-step guide on how to build one in the ESPHome documentation.
• Broadlink, so any Broadlink RM4 Pro you may already own can be reused as an RF transmitter for the new integrations. The RM4 Pro is the only model in the RM4 line with RF support, and it’s limited to the 433 MHz band.

On the other side, device-specific integrations use the platform to actually do something useful. Two are shipping in this release:

• Honeywell String Lights, to turn your RF remote-controlled Honeywell string lights on and off from Home Assistant, with all the automation magic that brings. 🎄
• Novy Cooker Hood, to control the light and the extractor fan on your Novy cooker hood. These are typically ceiling-mounted, so an RF remote (and now Home Assistant) is the only practical way to reach them. 💨

Why this is a big deal

Like infrared, this is about more than a single new feature. A large chunk of perfectly good RF-controlled hardware out there has no smart home story at all. By giving Home Assistant a standard way to talk to RF devices, every new consumer integration built on top instantly works with every transmitter integration. Add a new ESPHome RF proxy somewhere in the house, and your blinds, your fan, and your string lights all just work. ✨

This is a great fit with the values of the Open Home Foundation, and especially sustainability. 🌱 Instead of throwing out a working motorized blind because it’s “dumb”, you can integrate it. Instead of replacing your RF outlets with new Wi-Fi ones, you can keep using them. It’s another way to extend the life of devices you already own, and to reduce electronic waste. ♻️

A sneak peek at what’s coming

You may have caught a glimpse of where this is heading at the State of the Open Home 2026. Nabu Casa is a commercial partner of the Open Home Foundation, running Home Assistant Cloud and producing devices like the Home Assistant Green and the Home Assistant Voice Preview Edition. They’ve been working on a new device, currently going by the codename Project Blast, that brings infrared and radio frequency capabilities together in a single, polished package. The new Radio frequency platform in this release is part of the foundation that makes products like that possible. Stay tuned. 👀

If this tickles your interest, watch Carl from Nabu Casa explain what’s coming in this segment of the State of the Open Home 2026. 📺

We’re excited to see where the community takes this. The Radio frequency platform is designed to grow: more transmitter integrations, more device integrations, and more protocols over time.

This work is part of an Open Home Foundation roadmap opportunity to make radio frequency a first-class citizen of Home Assistant. Mission accomplished. 🎉

Serial ports over the network with ESPHome

We have a bit of a theme going on. Last release, infrared became a first-class citizen of Home Assistant. This release, radio frequency joined the party. And now, there’s another way you can put an ESPHome device somewhere in your home and let Home Assistant talk to things through it: serial ports. 🔌

If you’ve ever set up a Bluetooth proxy, the idea will feel familiar. Plenty of smart home gear talks over a serial connection, like energy meters with a P1 port, or that classic Denon receiver with the new Denon RS-232 integration shipping in this release. Until now, the device producing those serial signals had to be physically plugged into the same machine running Home Assistant, or wired up over a long, unwieldy cable. Not anymore. ✨

With the new serial proxy support in ESPHome, any serial port plugged into (or built into) an ESPHome device can now be exposed over your network and used by Home Assistant as if it were sitting right next to it. Drop an ESP somewhere convenient, plug your serial device into it, and Home Assistant takes care of the rest. 🪄

Where this comes in handy

This is great news if you’ve ever struggled to put a serial-connected device exactly where you wanted it. A few practical examples:

• Connect to receivers, projectors, or other AV gear over RS-232 from anywhere on your network.
• Read your smart meter’s P1 port from the meter cabinet, even if your Home Assistant server lives upstairs in a closet. ⚡

Like our existing Bluetooth, infrared, and radio frequency proxies, this is also a sustainability win. ♻️ Instead of replacing perfectly good serial-only equipment with newer Wi-Fi versions, you can keep using what you already have. That energy meter, that older AV receiver, that industrial sensor: they all just work, over the network. 🌱

Under the hood

Behind the scenes, this release rewires Home Assistant’s serial-port handling top to bottom to make serial proxies a natural part of the system. Some highlights for the curious:

• All of Home Assistant has been migrated to a modern, async-first serial driver called serialx, replacing the older pyserial library that Home Assistant has used for years. It’s designed for the way Home Assistant works today and adds support for new connection types, including ESPHome serial proxies, transparently.
• Integrations that need a serial port now get a new, polished serial port selector in the UI. It lists local USB serial ports and remote ESPHome serial proxies side by side, with friendly names. The list even updates live, so a USB device you plug in while the dropdown is open shows up right away.
• Common integrations that talk over serial pick up serial proxies for free. The new Denon RS-232 integration uses it from day one, and the existing Russound RIO integration has been migrated to serialx as well, so it can now talk to your multi-room audio gear over an ESPHome serial proxy too.

If you’re an integration developer (or maintain a custom component) talking over serial, head over to the migrating from pyserial to serialx developer blog post to read all about how to take advantage of this. 🛠️

A first step, not the finish line

Let’s be upfront about one thing: getting a serial proxy up and running today is not a one-tap experience yet. To use this in your home, you’ll need to build your own ESPHome device with the serial_proxy component configured for the UART your serial device is wired to. That means writing an ESPHome YAML configuration, flashing the firmware, and connecting the hardware. It’s very doable, but it is on the technical side. 🤓

We think that’s okay, because this release is the foundational milestone that makes everything else possible. The plumbing is now in place across Home Assistant, ESPHome, and the integrations that need it. From here, we (and the broader community) can build on top of this with friendlier setup flows, ready-made hardware, and pre-built ESPHome configurations. Just like Bluetooth and infrared proxies before it, the experience will get more approachable release after release. 🚀

This work is part of an Open Home Foundation roadmap opportunity to make serial proxying a first-class citizen of Home Assistant. Another roadmap milestone, checked off the list. ✅

More from your built-in dashboards

Over the past few releases, Home Assistant has been quietly growing a family of built-in dashboards that you don’t have to build yourself. It started with the Home dashboard back in 2025.9, and grew with dedicated Lights, Climate, and Security dashboards in 2025.11. This release adds a new one and upgrades an existing one. 🏠

Stay on top of your batteries with the new Maintenance dashboard

Keeping your smart home running smoothly is a side of home automation that doesn’t always get the spotlight. We’ve all been there: that motion sensor in the hallway that suddenly stops triggering the lights one evening, only to discover days later that its battery had died. 🪫 Wouldn’t it be nice to spot that before it becomes a problem? The new built-in Maintenance dashboard gives questions like that a home of their own. 🧰

The dashboard focuses on what is probably the most-requested view of all: your batteries. It automatically discovers every battery 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] in your home and lays them out grouped by area, with low ones highlighted so you can spot the ones that need swapping at a glance. No more digging through entity lists or building your own dashboard for it. 🔋

This is a community contribution from @Brookke, who built it from the ground up. Big thanks for adding such a useful new dashboard to Home Assistant! 👏

Activity log on the Security dashboard

The built-in Security dashboard also gets a nice upgrade this release: a new Activity sidebar that shows you a live, 24-hour log of everything happening with your security-related entities. Cameras, locks, alarm panels, motorized covers, door and window sensors, and the comings and goings of the people in your home, all in one place. 🔓

It’s a quiet upgrade you’ll feel every day: at a glance, you can see if a door was opened, if someone arrived home, or if the front camera spotted motion, without having to dig through the logbook or build a dashboard for it yourself. The sidebar appears automatically on wider screens whenever the Logbook integration is enabled (it is, by default).

More for the dashboards you build yourself

Building your own dashboard is one of the most rewarding parts of Home Assistant. The best part: you can build the entire thing right in the UI, by dragging and dropping cards into place. You don’t need to be technical, you don’t need to know YAML, and you don’t need to touch a single line of code to make something that looks great and works exactly the way you want.

Of course, the dashboards you craft yourself get plenty of love this release too. A new card for one-tap shortcuts and fresh tile card features for your media players. 🎨

Introducing the shortcut card

Dashboards are the front door to your smart home, and sometimes the most useful thing you can put on them isn’t an entity, but a quick way to get somewhere. Jump to your energy dashboard. Open the camera view. Launch Assist. Open the manual in a new tab. The new shortcut card makes building those one-tap launchers a breeze. ⚡

It looks and feels like a tile card, but instead of representing an entity, it triggers an action when you select it. You can pick from:

• Navigate to another dashboard, view, area, or device page.
• Open a URL in a new tab, perfect for linking out to your router, NAS, or documentation.
• Launch Assist, so your voice assistant is always one tap away.
• Perform an action, like turning off all the lights when you head out the door. 🌙

The card is smart about defaults: pick a navigation target and it picks up the title, icon, and color of that destination automatically. Pick Launch Assist and it suggests a microphone icon. You can override any of it, of course; set your own label, description, icon, and color, and pick between a horizontal or vertical layout.

The shortcut also comes as a badge, so you can drop the same one-tap actions into the badge row at the top of any view. Same options, same smart defaults, just in a more compact form.

New tile card features for media players

The tile card is one of the most flexible building blocks in Home Assistant dashboards, and this release expands what it can do for media players. Two new card features and a more flexible playback feature give you a lot more choice in how your media player tiles look and behave. 🎶

The first new feature is select source: a dropdown right on the tile that lets you switch the input or source on your media player. HDMI 1, the Spotify input on your receiver, that one obscure radio station you actually like; it’s all one tap away. The second is select sound mode, with the same dropdown experience for picking modes like Movie, Music, or Night on receivers and AV gear that support it.

And the existing playback card feature got a long-requested upgrade: you can now pick exactly which buttons appear and in what order. Mix and match from on/off, play, pause, play/pause, stop, previous track, and next track to build a remote that fits your media player perfectly. No more turn-on button on a TV that doesn’t need one, no more missing the next-track button on your speaker. 🎚️

Purpose-specific automation triggers & conditions

The journey to make automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] building feel natural continues. Ever since Home Assistant 2025.12 introduced purpose-specific triggers and conditions, every release has chipped away at the gap between how you describe your home in your head (“when a light turns on”, “if the climate is heating”) and what you actually had to type into an automation. Last release added a whole batch of cross-domain triggers and conditions. This release adds something the entire community has been asking for: time. ⏱️

Automations that finally understand “for a while”

Reading back the feedback we’ve received in the months this has been in Home Assistant Labs, one request stood out above all others: durations. Almost every “when motion is detected” automation in the wild secretly wishes it could say “when motion has not been detected for the last 5 minutes”. And almost every “if a door is open” condition really wants to be “if a door has been open for at least 10 minutes”. 🚪

Now they can. On the trigger side, a new for field has landed across a wide range of state-based purpose-specific triggers, from motion and occupancy to doors, windows, lights, switches, climate, covers, and many more. Pick a trigger, set how long the situation has to hold, and you’re done. No more wrestling with template helpers or YAML for: keys hidden in code views to express something this fundamental.

On the condition side, duration is now available across the entire family of entity conditions in Labs. Whether you’re checking on motion, a door, a light, a switch, a climate, a media player, or anything else, you can now ask for the state to have held for a given amount of time before the condition is considered true. Same story: no template helpers, no YAML detour.

A few examples of what this unlocks:

• “When the front door has been open for more than 2 minutes” → close-the-door reminder. 🔔
• “When motion has not been detected in the office for 15 minutes” → turn off the lights. 💡
• “If the bedroom window has been closed for at least an hour” → only then start the air purifier. 🌬️
• “When a garage door has been open for more than 30 minutes after sunset” → send a notification. 🌙

It’s a small-looking addition with an outsized impact: a whole category of “almost possible” automations just became easy to put together.

A few more triggers and conditions to play with

Beyond the new sense of time, this release sprinkles a few more handy purpose-specific building blocks across your house.

If you keep an eye on updates waiting to be installed, two new conditionsConditions are an optional part of an automation that will prevent an action from firing if they are not met. [Learn more], is available and is not available, let an automation branch on whether something is pending, without templating the answer yourself.

Your media players got chatty: triggers fire when something starts playing, pauses, turns on, or turns off, and now also when a player is muted or unmuted, when its volume changes, or when the volume crosses a threshold you set. Conditions follow the same beat with is muted, is unmuted, and a numeric volume check. Perfect fuel for “dim the lights when the movie starts”, “pause the music when the doorbell rings”, or “only send the loud TTSTTS (text-to-speech) allows Home Assistant to talk to you. [Learn more] announcement if the speaker is below 30%”. 🎬🔇

Your remotes picked up matching is on and is off conditions, finishing what last release’s triggers started. And your to-do lists can now answer two questions an automation might have: are all items completed, or are there still incomplete items on the list? Great for end-of-day check-ins or those “did I forget to feed the cat” moments. 🐱

Your timers got a whole lifecycle of new triggersA trigger is a set of values or conditions of a platform that are defined to cause an automation to run. [Learn more]: started, paused, restarted, cancelled, and finished. So that 20-minute “tea is ready” timer can now actually tell your kitchen lights to flash, and your “kids screen time” timer can announce when it’s running, paused, or up. There’s also a new time remaining trigger that fires when a running timer reaches a remaining duration you pick: think a gentle “five minutes left” warning before the screen time timer runs out. ⏲️

And finally, a new doorbell rang trigger. Doorbell event entities now speak a shared language, so a single trigger lights up regardless of which brand sits at your front door. 🔔

Changes to existing triggers and conditions

As some of the very first, we’ve added purpose-specific triggers and conditions for Person entities and Device Tracker entities separately. More recently, we’ve decided we want to go for a more ergonomic cross-domain approach. Thus, the triggers entered_home and left_home and also the conditions is_home and is_not_home got removed from the Person and Device Tracker. They will get successors in one of the upcoming releases.

Try it out!

Purpose-specific triggers and conditions are still a preview feature in Home Assistant Labs, but with each release the rough edges get smoother, and we’re closing in on having it feature complete. If you haven’t given it a spin yet, head over to Settings > System > Labs, switch it on, and let us know what you think. Your feedback is genuinely shaping where this lands; building in the open at work. 💚

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:

• Denon RS-232, added by @balloob
  Control your Denon receiver locally over its RS-232 serial port. Connect your receiver using a serial cable or a USB-to-serial adapter for push-based state updates, without depending on the network or the cloud.

• Duco, added by @ronaldvdmeer — launching at 🏆 platinum quality
  Monitor and control your Duco demand-controlled ventilation system locally from Home Assistant. Track CO₂, humidity, and other sensor data, and adjust ventilation, all over your local network.

• EARN-E P1 Meter, added by @Miggets7
  Connect your EARN-E energy monitor to Home Assistant for real-time insights into your smart meter’s energy and gas data. The device pushes its readings over your local network, so no cloud or polling is involved.

• Eurotronic Comet Blue, added by @rikroe
  Integrate your Eurotronic Comet Blue (and similar) Bluetooth radiator thermostats with Home Assistant. Read thermostat status and adjust temperatures locally, without a hub or cloud connection. Compatible thermostats include Sygonix HT100 BT, Xavax Hama, and Lidl Silvercrest RT2000BT.

• Fumis, added by @frenck — launching at 🏆 platinum quality
  Bring your Fumis-based pellet stove into Home Assistant through the Fumis online service. Monitor your room temperature, set a comfortable target temperature, and turn your stove on or off. Pellet stoves, pellet boilers, and hybrid wood and pellet stoves equipped with a Fumis WiRCU Wi-Fi module are sold under many different brands, including Austroflamm, Eco Spar, HAAS+SOHN, and Heta.

• Honeywell String Lights, added by @balloob
  Control your Honeywell radio frequency (RF) remote-controlled string lights from Home Assistant. Uses the new Radio frequency entity platform, so you’ll need a compatible sub-GHz RF transmitter (for example, an ESPHome device) to send commands.

• Kiosker, added by @Claeysson
  Monitor your Kiosker web kiosks running on iPad or iPhone from Home Assistant. Kiosker turns your iOS device into a powerful, easy-to-use web kiosk, perfect for dashboards on the wall.

• Novy Cooker Hood, added by @piitaya
  Control the light and the extractor fan on your Novy cooker hood from Home Assistant. Novy hoods are typically ceiling-mounted, with no buttons within reach, so an RF remote (and now Home Assistant) is the only practical way to control them. Uses the new Radio frequency entity platform, so you’ll need a compatible sub-GHz RF transmitter (for example, a Broadlink RM4 Pro or an ESPHome device) to send commands.

• OMIE, added by @luuuis — launching at 🥈 silver quality
  Bring Iberian Peninsula day-ahead electricity spot prices from OMIE into Home Assistant. Sensors expose the current and next-hour prices for both Spain and Portugal, perfect for smarter automations around when to run your dishwasher, charge your EV, or heat your water.

• Radio frequency, added by @balloob
  A new entity type that represents a sub-GHz radio frequency (RF) transmitter, like an ESPHome device with a CC1101 module attached. You don’t set this integration up directly; instead, other integrations use it to send RF commands to devices such as remote outlets, garage doors, and string lights. The new Honeywell String Lights and Novy Cooker Hood integrations are the first to make use of it. Read more about it in the Radio frequency joins infrared as a first-class citizen section above.

• Teleinfo, added by @esciara — launching at 🥈 silver quality
  Read electricity consumption data from French Linky smart meters and older electronic meters using the Télé-Information Client (TIC) protocol. Connect a Teleinfo USB adapter to your meter’s TIC output to monitor real-time energy indexes, apparent power, instantaneous current, and tariff information, all locally.

• Victron GX, added by @tomer-w — launching at 🏆 platinum quality
  Connect your Victron Energy GX devices, like the Cerbo GX, Venus GX, and Color Control GX, to Home Assistant over MQTT. Get real-time monitoring and control of your Victron system, including inverters, solar chargers, battery systems, grid meters, and EV chargers.

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:

• MQTT picked up three new platforms this release: time, datetime, and date entities, giving you even more building blocks for your MQTT-based devices and automations. Thanks, @jbouwh!
• Matter added support for Matter radon sensors, so radon-monitoring devices that speak Matter now show up natively in Home Assistant. Thanks, @dnicoara!
• ESPHome water heater entities now support away mode, matching what physical and smart water heaters in your home offer. Thanks, @tronikos!
• Shelly added tilt and rotation binary sensors for the Shelly Cury, and the Shelly Wall Display now exposes a media player entity for built-in audio playback. Thanks, @bieniu!
• Sonos got two new switches for TV Autoplay and Ungroup on Autoplay, giving you fine-grained control over how home theater speakers behave when the TV turns on. Thanks, @arsenicks!
• Apple TV now supports keyboard text input services, so you can send text to your Apple TV right from Home Assistant. No more hunting for letters on the on-screen keyboard. Thanks, @kroehre!
• Music Assistant received a big batch of player options: number, text, switch, and select entities are now exposed for everything Music Assistant players make configurable. On top of that, sound mode support has landed too. Thanks, @fmunkes!
• Roborock owners with a Q10 S5+ now get dedicated sensor and select entities for their vacuum, and Q7 vacuums gained cleaning route control. Thanks, @lboue and @Lash-L!
• WLED now supports per-segment freezing, letting you pause effects on individual LED segments. Thanks, @tgechev!
• Broadlink can now act as an infrared emitter on the new infrared platform that landed last release, so your Broadlink RM-series devices can be reused as native IR transmitters for other integrations. Thanks, @YuvalWS!
• Home Connect added microwaves to the related appliance types for several sensors, expanding coverage of supported devices. Thanks, @Diegorro98!
• OpenAI Conversation added support for OpenAI’s new GPT-5.5 conversation model and the gpt-image-2 image generation model, which is now the recommended default for image generation. Thanks, @Shulyaka!
• SMLIGHT SLZB devices now expose an infrared platform, so they can be used as IR transmitters with the new infrared entity platform. Thanks, @tl-sl!
• SwitchBot Air Purifier devices gained fan speed percentage control and a button to toggle the built-in light sensor. Thanks, @zerzhang!
• Tado now uses a dynamic update interval, automatically adjusting how often it polls based on activity to give you fresher data when something is happening. Thanks, @erwindouna!
• SolarEdge got a whole set of new battery storage sensors. There are aggregate sensors for the total daily charge and discharge energy across your batteries, and per-battery sensors for daily charge and discharge energy, state of charge, and current power. All new sensors are disabled by default, so you can enable just the ones you need. Thanks, @it-rec!
• HTML5 Push Notifications got a major upgrade: a new event platform, a new html5.send_message entity action, and the integration is now correctly classified as a notification service. Thanks, @tr4nt0r!
• Anthropic added support for Anthropic’s new Claude Opus 4.7 model. Thanks, @Shulyaka!
• Immich media source now exposes your favorite collection, making it easy to pull starred photos straight into your dashboards. Thanks, @mib1185!
• Transmission gained an event entity for torrent events, perfect for triggering automations when downloads finish. Thanks, @andrew-codechimp!
• Portainer continues its rapid expansion: new buttons for pruning volumes, killing containers, recreating containers, and full volume management. Thanks, @erwindouna!
• LG Netcast got a new action to send remote control commands, letting you script TV navigation and input. Thanks, @mithomas!
• Subaru vehicles that support remote start now have a dedicated start/stop button entity. Thanks, @masterkoppa!
• London Underground expanded beyond the tube: it now reports status for the Trams and the IFS Cloud Cable Car as well. Thanks, @prpr19xx!
• UniFi Access picked up several improvements: a select entity for temporary door lock rules, UA-HUB-Door support, entry/exit direction on access events, automatic console discovery via UniFi Discovery, and a warning when a UniFi Protect API key is used during setup. Thanks, @imhotep and @RaHehl!
• UniFi Protect is turning into your alarm hub: it gains an alarm control panel, UniFi PoE Siren / UniFi SuperLink Siren sirens, and switches for the new UniFi SuperLink Relay — a device that reaches up to 2 km over LoRa. All of these new features require UniFi Protect 7.1 or later. Thanks to Ubiquiti for the public API improvements, and to @RaHehl for bringing it all to Home Assistant!
• WaterFurnace geothermal systems now expose a climate entity, alongside new energy statistics so you can track your system’s energy use over time. Thanks, @masterkoppa!
• OpenDisplay Flex e-paper devices now expose new diagnostic sensors driven by passive Bluetooth Low Energy advertisements: a battery percentage and battery voltage sensor for battery- and solar-powered devices, and a chip temperature sensor. Thanks, @g4bri3lDev!
• Satel Integra now supports encrypted connections, keeping your alarm panel communications secure over the network. Thanks, @Tommatheussen!

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:

• 6 integrations reached platinum 🏆

  • Elgato, thanks to @frenck
  • freshR, thanks to @SierraNL
  • Google Weather, thanks to @tronikos
  • Liebherr, thanks to @mettolen
  • Twente Milieu, thanks to @frenck
  • UniFi Access, thanks to @imhotep and @RaHehl

• 2 integrations reached gold 🥇

  • FRITZ!Box Tools, thanks to @AaronDavidSchneider, @chemelli74, and @mib1185
  • Samsung Smart TV, thanks to @chemelli74 and @epenet

• 3 integrations reached silver 🥈

  • Anthropic, thanks to @Shulyaka
  • Huum, thanks to @frwickst and @vincentwolsink
  • UniFi Network, thanks to @RaHehl and @Kane610

• 2 integrations reached bronze 🥉

  • iAquaLink, thanks to @flz
  • WaterFurnace, thanks to @sdague and @masterkoppa

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:

• PJLink, done by @jtjart
• Pico TTS, done by @rrooggiieerr

Farewell to the following

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

• LANnouncer has been removed. The companion Android app is no longer available, which made the integration impossible to install or use. It was deprecated in Home Assistant 2025.10 and is now removed. If you were still using it, you’ll need to look for an alternative notification integration.

Other noteworthy changes

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

• Mobile app notifications are now entities. The Mobile app integration now exposes a notificationYou can use notifications to send messages, pictures, and more, to devices. [Learn more] entity for each of your devices, on top of the existing notify actions. That means you can group your phones and tablets together using the regular group helper right from the user interface, and send a single notification to all of them at once. No YAML, no scripting, no scrolling through a list of targets. Thanks, @tr4nt0r! 📱
• A search bar on the integration detail page. Integrations with a lot of devices and entries (think Z-Wave, Zigbee, or your sprawling pile of ESPHome devices) now have a search bar at the top, matching across entry titles, device names, manufacturers, models, and areas. 🔍
• Dashboard visibility conditions can now refer to the card’s own entity. State and numeric state visibility conditions get a new Current entity option that automatically follows whichever entity the card is bound to. No more re-typing entity IDs, and your card stays reusable.
• Dashboard visibility conditions now support attributes. State and numeric state visibility conditions on cards can now check an entity attribute instead of just the state, catching up with their automation counterparts.
• Reload your shell commands without restarting. A new reload action lets you re-read your Shell command YAML configuration on the fly. One less reason to restart Home Assistant. Thanks, @potelux!
• Template vacuums learned about rooms. Vacuums you build with the Template integration can now expose their segments (rooms) and a clean_segment action, plugging straight into the new Clean by area view. 🧹 Thanks, @gustavakerstrom!
• More unit love for sensors. Frequency sensors now support millihertz (mHz) through gigahertz (GHz) with automatic conversion between them, and electric current sensors gained microamperes (µA). Thanks, @32u-nd, @Lamarqe, and @Phunkafizer!

A modern more-info dialog for vacuums and lawn mowers

When you tap on an entity in your dashboard, the more-info dialog that pops up is one of the most-used surfaces in Home Assistant. This release, two of them get a fresh new look: vacuums and lawn mowers. 🧹🌱

The redesigned vacuum dialog leads with a friendly new illustration of your vacuum that comes to life with state-driven animations: it spins while cleaning, glides home while returning, sits quietly when docked, and shakes when something’s wrong. Battery moved up into the header where you can spot it at a glance, and the action buttons (start, pause, return to dock) are now lined up in a single, consistent row.

The biggest functional addition is a brand new Clean by area view. Many modern robot vacuums let you ask them to clean a specific room, but until now, there was no built-in way to do that from the dialog. You can now map your Home Assistant areasAn area in Home Assistant is a logical grouping of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage. [Learn more] to the rooms your vacuum knows about, and start a cleaning job for one or more areas right from the dialog. If you haven’t set up a mapping yet, the dialog walks you through it with a friendly empty state.

Lawn mowers got the same love. The redesigned lawn mower dialog brings the same fresh illustration with state-driven animations (mowing, returning, docked, error), the same battery-in-the-header layout, and the same unified action button row. Whether your robot is busy on the carpet or busy on the lawn, the experience now feels the same.

This work delivers on two Open Home Foundation roadmap opportunities: refined more info screen for vacuum cleaners and refining the more info screen for lawn mowers. Two roadmap items, one redesign. ✅

New styling for toggles

Toggles across Home Assistant got a small but lovely makeover this release. Every toggle in the app has been updated with a fresh new design. 🎨

The refreshed toggles on an entities card.

It’s not just a fresh coat of paint either: the new toggle is fully keyboard-friendly. Tab to it, then use the arrow keys to flip it on or off without ever touching the mouse. Small change, big quality-of-life upgrade. ⌨️

The templating documentation you’ve always wanted

First, the most important thing to say up front: you do not need to write code or touch a single template to use Home Assistant. Everything from setting up your devices, to building automations and crafting beautiful dashboards, can be done entirely through the user interface, and it gets better every release. If the interface does what you need, you’re done. 💚

That said, templating is one of the most powerful corners of Home Assistant for the people who do want to go a step further: dynamic notifications that read the actual temperature, automations that decide based on a calculation across several entities, template entities whose value is computed from other entities. And it has long been one of the most intimidating corners too. So we shipped a top-to-bottom rework of the templating documentation, with one goal: if you have ever felt that templates were “not for you”, we want to change that. 📚✨

If you decide to learn templating, we are now confident we have everything in place to take you all the way:

• 14 brand new learning pages walk you through templating step by step, from what is a template? and where to use templates, through syntax, loops and conditions, working with states, types and conversion, dates and times, common patterns, and debugging, all the way to writing your own custom templates and macros.
• Two full tutorials build something real you can use: a daily low-battery notification, and an average home temperature sensor you can drop straight onto your dashboard.
• Every one of the 200+ “template functions”A template function is called by name with parentheses, like states(“sensor.temperature”) or now(). It takes input values as arguments and returns a result. [Learn more], “filters”A template filter transforms a value using the pipe (|) operator. It takes the value on the left and returns a modified result. For example, states(“sensor.temperature”) | float converts the state to a number. [Learn more], and “tests”A template test checks a condition using the “is” keyword and returns true or false. For example, value is number checks if a value is a number. [Learn more] has its own page, with a plain-language intro, parameters, examples that show the exact output they produce, common gotchas, and links to related functions. All searchable through a single template functions reference that lists them all.
• A dedicated error messages page lists common template errors verbatim, so when something breaks late at night you can paste the error into a search engine and land somewhere that actually helps.

There’s a quality-of-life upgrade across the entire website too: templates in code blocks are now interactive. Hover over a function name to see its description, select it to jump to the reference page, hover over a parameter for a quick reminder of what it does. Examples render with the input on top and the actual output right below, so you never have to guess what a template will produce.

Skip it, skim it, or master it. Either way, we’ve got your back. And this is just the beginning: we’ve expanded our documentation team and are investing heavily in making all of our documentation more approachable. So expect more reworks, more tutorials, and more friendly-but-thorough guides in releases to come. 💪

Smarter code editors with autocomplete

The rework didn’t stop at the documentation. While building it, it became painfully clear that even with great docs, writing a template still meant flipping back and forth between tabs. So the code editors you find throughout Home Assistant, the ones you use to write a template or fine-tune an automation, got a serious upgrade this release too. They now offer rich, context-aware autocomplete for both YAML and Jinja2 templates. ✨

Start typing inside a {{ ... }} or {% ... %} block, and the editor now suggests Home Assistant’s template functions, filters, tests, and globals. Each suggestion comes with a short signature, a description, and tab-stops for the arguments, so you can fly through writing a template without keeping the template documentation open in another tab.

It gets even better inside the string arguments of those functions. The editor knows what kind of ID a function expects and offers matching suggestions:

• Entity IDs for functions like states(), is_state(), and state_attr(), including the states["..."] shorthand.
• Device IDs for device_entities(), device_name(), and device_attr(), showing the device’s friendly name with the raw ID as the inserted value.
• Area IDs for area_entities(), area_devices(), and area_name().
• Floor IDs for floor_areas(), floor_entities(), and floor_name().
• Label IDs for label_areas(), label_devices(), and label_entities().

No more copy-pasting entity IDs from the developer tools, and no more typos sneaking into your templates. Less friction, fewer mistakes. 🎯

And it’s not just autocomplete. Hover over anything in your template and the editor has something useful to say. Functions, filters, and tests get a small tooltip with their signature, what they do, and a direct link to the full documentation page. Entity IDs and attributes show their current value right where you’re typing, so you instantly see whether your template is reading what you think it is. 🔍

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:

• Deprecation of legacy device tracker platform API
• Entity IDs with mismatched domains are deprecated
• Frontend component updates in 2026.5
• Frontend context groups, new context decorators and deprecated contexts
• Migrating app builds to Docker BuildKit
• New radio frequency entity platform for RF device integrations
• Registering custom dashboard strategies
• Serious about serial: migrating from pyserial to serialx
• Standard event type for doorbell event entities

Patch releases

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

2026.5.1 - May 8

• Added wfsens as a occupancy source in wiz (@th3spis - #166799)
• Fix WiZ Light config flow timeout by properly closing UDP connections (@robwasripped - #168456)
• Fix IntelliFire setup recovery (@jeeftor - #169739)
• Fix hassio auth IndexError on Supervisor Unix socket requests (@agners - #169911)
• Update gardena ble to 2.8.1 (@elupus - #169914)
• Bump serialx to 1.7.1 (@puddly - #169928)
• Bump holidays to 0.96 (@gjohansson-ST - #169939)
• Add support for options to todo triggers (@emontnemery - #169947)
• Bump pyTibber to 0.37.5 (@Danielhiversen - #169981)
• Bump python-duco-client to 0.4.0 (@ronaldvdmeer - #169776)
• Bump python-duco-client to 0.4.1 (@ronaldvdmeer - #169991)
• Proper handling of malformed data during FRITZ!Box Tools setup (@mib1185 - #170030)
• Fix websocket certificate verification Bump axis to v70 (@Kane610 - #170038)
• Fix is_closed state for DynamicGarageDoor in Overkiz (@iMicknl - #170052)
• Fix tilt controls for TiltOnlyVenetianBlind in Overkiz (@iMicknl - #170055)
• Fix cover controls for UpDownBioclimaticPergola in Overkiz (@iMicknl - #170058)
• Bump pyOverkiz to 1.20.3 (@iMicknl - #170060)
• Bump deebot-client to 18.3.0 (@edenhaus - #170066)
• Set is_closed state to None when a cover state returns “unknown” in Overkiz (@iMicknl - #170081)
• Fix sensors getting wrong unit from MeasuredValueType attribute in Overkiz (@iMicknl - #170088)
• Fix Z-Wave discovery crash with unknown node firmware version (@TheJulianJES - #170090)
• Bump ZHA to 1.3.1 (@TheJulianJES - #170095)
• Bump python-bsblan to 5.2.1 (@liudger - #170100)
• Bump blebox_uniapi to v2.5.3 (@bkobus-bbx - #170115)
• Fix is_closed state for DynamicGate covers in Overkiz (@iMicknl - #170130)
• Fix tilt support for UpDownVenetianBlind (rts:VenetianBlindRTSComponent) in Overkiz (@iMicknl - #170047)

2026.5.2 - May 15

• Fix ValueError for non-numeric value in LG ThinQ (@LG-ThinQ-Integration - #166300)
• Only use SmartThings switch for light if it should (@r2xj - #166424)
• Fix non unique_id for Comelit (@chemelli74 - #169756)
• Migrate ZBT-1 and ZBT-2 to use serial number for unique_id (@puddly - #169879)
• Update afsapi to 1.0.1 (@wlcrs - #170073)
• Fix local API incorrectly marking devices as unavailable in Overkiz (@iMicknl - #170118)
• Fix homematicip_cloud config entry setup crash after migration to 2026.5.0 (@lackas - #170156)
• homematicip_cloud: fix HmIP-FLC lock state polarity (@lackas - #170159)
• Set serial port description from description, not product (@puddly - #170160)
• Reinit API on stale session for Vodafone Station (@chemelli74 - #170190)
• Fix MQTT device discovery not using shared QoS and encoding options (@jbouwh - #170195)
• Fix entities refresh for UptimeRobot (@chemelli74 - #170217)
• Add target flow level and mode end time sensors to Duco integration (@ronaldvdmeer - #169298)
• Add system health platform for Duco integration (@ronaldvdmeer - #169517)
• Add API version to Duco diagnostics for support triage (@ronaldvdmeer - #169802)
• Bump python-duco-client to 0.4.2 (@ronaldvdmeer - #170027)
• Bump python-duco-client to 0.5.0 (@ronaldvdmeer - #170065)
• Handle empty BSB-LAN heating circuits (@liudger - #170249)
• Fix: Do not forget segments from state when a new config arrives (@Hypfer - #170265)
• Bump imgw-pib to 2.1.2 (@bieniu - #170274)
• iaqualink: set system specific polling interval (@flz - #170279)
• Bump renault-api to 0.5.8 (@thargy - #170309)
• Fix hassio.backup_partial AttributeError when folders are specified (@agners - #170312)
• Fix Shelly media player availability (@bieniu - #170319)
• Cancel previous Debouncer timer handle in _schedule_timer (@raman325 - #170339)
• Bump axis to v71 (@Kane610 - #170347)
• Fix duplicate doorbell events when entity becomes unavailable (@jbouwh - #170354)
• Bump serialx to 1.7.2 (@PBrunot - #170272)
• Bump serialx to 1.7.3 (@puddly - #170368)
• Bump pyintesishome to 1.8.7 (@jnimmo - #170382)
• Apply unit_of_measurement to energy combined power sensor (@MindFreeze - #170404)
• Bump pymiele version to 0.6.2 (@astrandb - #170419)
• Bump aioesphomeapi to 44.24.1 (@bdraco - #170428)
• Fix fractional setpoints in Matter climate not rounded (@TheJulianJES - #170442)
• Fix influxdb reconfigure for v1 configuration (@RobBie1221 - #170448)
• Bump aioharmony to 1.0.3 (@bdraco - #170459)
• Increase WebDAV client timeout from 10 to 30 seconds (@Croydon - #170476)
• Fix MQTT settings in device subentry device settings are not recalled when reconfiguring the device (@jbouwh - #170484)
• Add missing optional category strings in workday (@gjohansson-ST - #170505)
• Update frontend to 20260429.4 (@bramkragten - #170567)
• Migrate Duco to python-duco-connectivity and remove temperature sensors (@ronaldvdmeer - #170237)
• Bump python-duco-connectivity to 0.4.0 (@ronaldvdmeer - #170661)

2026.5.3 - May 19

• Bump qbittorrent-api to 2026.5.1 (@lumatijev - #170181)
• Improve iaqualink 429 handling (@flz - #170231)
• Fix Apple TV keyboard focus binary_sensor missing on cold start (@kroehre - #170360)
• Add tilt controls for UpDownSheerScreen in Overkiz (@dankarization - #170563)
• Fix blebox light temperature scaling (@bkobus-bbx - #170573)
• Fix ValueError when turning on blebox light with brightness set to 0 (@bkobus-bbx - #170769)
• Bump aiodns to 4.0.3 (@bdraco - #170865)
• Populate uid and recurrence_id in CalDAV calendar events (@frenck - #170910)
• Fix is_closed state for SlidingDiscreteGateWithPedestrianPosition covers in Overkiz (@iMicknl - #170913)
• Disable USB discovery for teleinfo (@puddly - #170933)
• Fix utility meter next_reset shifting forward on entity rename (@frenck - #170957)
• Use correct state_class for utility meters with device classes that don’t support total_increasing (@frenck - #170962)
• Reduce GoodWe connect retries to avoid blocking startup (@frenck - #170964)
• Fix is_closed state for DiscretePositionableGarageDoor in Overkiz (@iMicknl - #170981)
• Fix controls for OpenCloseGate4T (rts:GateOpenerRTS4TComponent) in Overkiz (@iMicknl - #170987)
• Prevent Google Assistant entity sync from blocking startup (@frenck - #170991)
• Load template extensions by class to prevent import deadlock (@frenck - #170995)
• Use asyncio.get_running_loop() in emulated_hue UPnP responder (@frenck - #171000)
• Fix Netatmo valve KeyError when hvac_action state is unavailable in Overkiz (@frenck - #171004)
• Fix time trigger crash when using entity_id dict format without offset (@frenck - #171006)
• Fix threshold preview crash when hysteresis is not provided (@frenck - #171009)
• Fix Growatt mix device IndexError when chart data is empty (@frenck - #171012)
• Fix SleepIQ timer units: seconds should be minutes for core climate and foot warmer (@frenck - #171013)
• Fix Control4 climate crash when humidity is ‘Undefined’ (@frenck - #171015)
• Fix manual alarm panel crash on restore with invalid state (@frenck - #171016)
• Handle Daikin connection errors gracefully in coordinator (@frenck - #171017)
• Fix shorthand template conditions in choose blocks crashing all automations (@frenck - #171018)
• Add additional overrides to cover entity in Overkiz (@iMicknl - #171019)
• Fix Verisure alarm crash when cloud rejects arm/disarm command (@frenck - #171024)
• Add stop command to Overkiz pergola horizontal awning covers (@frenck - #171034)
• Fix WeatherFlow websocket crash when data payload is None (@frenck - #171037)
• Bump pyIntesishome to 1.8.8 (@jnimmo - #171041)
• Return media_content_id as string in forked_daapd (@frenck - #171059)
• Bump aioimmich to 0.14.1 (@mib1185 - #171138)
• Fix controls for UpDownGarageDoor4T and additional 4T covers in Overkiz (@iMicknl - #171144)
• Fix ZHA config entries using a URI without a port (@puddly - #171164)
• Fix is_closed state and position for DynamicPergola covers in Overkiz (@iMicknl - #170983)
• Fix tilt and position support for VenetianBlind covers in Overkiz (@iMicknl - #170974)

2026.5.4 - May 22

• Apply web search citation stripping for GPT-5.x models in OpenAI conversation (@frenck - #170956)
• Bump aiolyric to 2.1.0 (@yonib05 - #171007)
• Bump python-roborock to 5.12.0 (@Lash-L - #171112)
• Add missing Miele Dishwasher codes (@astrandb - #171175)
• Bump aiolyric to 2.1.1, Update OAuth URL for lyric (@timmo001 - #171181)
• Fix ZHA blocking minor version downgrades (@TheJulianJES - #171319)
• Bump aiodns to 4.0.4 (@bdraco - #171420)
• Bump renault-api to 0.5.9 (@epenet - #171428)
• Fix SmartThings crash when timestamp attribute is None (@frenck - #171467)
• Fix habitica ignoring zero values for interval and streak (@frenck - #171468)
• Fix PowerView cover crash when shade position is unavailable (@frenck - #171471)
• Fix Wyoming satellite crash when TTS is not configured (@frenck - #171513)
• Fix string ref for tedee (@zweckj - #171548)
• Fix media_image_hash and validate the MIME type in the Shelly media player (@bieniu - #171585)
• Fix update error message key in solarlog (@dontinelli - #171611)
• Bump wled to 0.23.0 and remove backoff exception (@mik-laj - #171622)
• Bump renault-api to 0.5.10 (@epenet - #171692)
• Fix exception translation placeholder mismatches in comelit (@chemelli74 - #171748)
• Add missing exception translation keys in alexa_devices (@chemelli74 - #171749)
• Fix ZBT-2 hardware page crash when entry data is missing VID (@frenck - #171828)
• Fix Lutron Caseta battery sensor crash on unsupported devices (@frenck - #171829)
• Fix invalid MDI icon references (@frenck - #171831)
• Register Insteon modem device before platform setup (@frenck - #171839)
• Fix OpenHome config flow crash when UDN is a list (@frenck - #171841)
• Fix Hue device trigger crash for devices removed from bridge (@frenck - #171844)
• Fix dead link in System Bridge service action (@tr4nt0r - #171855)

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

How do you more or less double the number of Works with Home Assistant-certified devices available to our community? Have BEGA join the program! This German firm has spent more than 75 years designing a wide range of architectural lighting that sets the industry standard: and now they’re bringing that expertise to your smart home.

Bright BEGA-nnings

If you haven’t heard of BEGA before, you may have admired their work without realizing it. That’s because they produce the kind of beautifully engineered fixtures you see gracing the facades of fancy hotels, elegant public buildings, and stylish modern homes worldwide. They’re probably better known for this kind of work than for smart home tech, which is precisely what makes their joining the Works with Home Assistant program so exciting.

Because BEGA aren’t just dipping a toe in: they’re bringing what’s almost certainly the largest single addition of certified devices we’ve ever had in one go: enough to very nearly double the number of certified products in the program! And it’s not just the volume that impresses. BEGA Smart – their Zigbee-powered smart lighting system – is flexible, expandable, and designed to work entirely offline, with no internet connection required.

BEGA: putting the smart into smart home lighting.

Beyond beautiful design

BEGA’s premium positioning isn’t only about aesthetics. Their commitment to repairability also aligns well with the Open Home Foundation’s sustainability principles. Rather than treating a luminaire as a disposable unit, BEGA designs the majority of their components to be replaceable. Crack a glass panel? You can order that specific spare via their website’s search function and replace it, rather than throwing out the whole fixture.

This also makes BEGA an interesting choice if you’re thinking about illuminating your outdoor spaces. We have relatively few outdoor lighting options in the program, and BEGA fills that gap in style – just in time if you’re looking to get your garden or terrace ready for summer 😎.

Let there (Zig)bee light

We mentioned BEGA Smart runs on Zigbee, but if that’s new to you, here’s what it means. Zigbee is basically a short-range wireless communication standard: like Wi-Fi, but designed specifically for smart home devices. Unlike Wi-Fi however, it’s an open standard, so isn’t run by one specific company, and connects directly to Home Assistant without needing a router or internet connection. It’s also a mesh protocol, which means the more devices you add to your network, the stronger and more reliable it gets – handy for lighting that’s spread across your home and garden.

And on that subject, if you want to dim the patio lights from your sofa, or check they’re off while you’re away, Home Assistant Cloud can help – providing secure remote access wherever you are (your subscription helps fund the Works with Home Assistant program too!).

The path to enlightenment, with BEGA devices.

Devices

As with every Works with Home Assistant partner, our in-house team has thoroughly tested BEGA’s devices to make sure they meet our core requirements: local control, privacy, and long-term sustainability.

Because the list of certified BEGA devices is so long, we’ve included a condensed list below (there’s not enough room for them all here without subjecting you to a loooonnnnnng scroll! 😄). Bear in mind, when you browse BEGA’s website, look for devices marked as BEGA Smart. This tells you the item is Zigbee enabled and Works with Home Assistant certified. Worth knowing, since each luminaire also comes in other variants, such as DALI or non-smart versions, which are not certified under the program.

BEGA Smart covers a swathe of indoor and outdoor luminaires, with wall or ceiling mounted options, as well as freestanding garden path lighting to illuminate those balmy summer evenings.

• BEGA Smart Outdoor Ceiling luminaire (two variants)
• BEGA Smart Indoor Ceiling luminaire (nine variants)
• BEGA Smart Wall Outdoor Luminaire (10 variants)
• BEGA Smart Outdoor Garden and pathway luminaire (79 variants)
• BEGA Smart Indoor Ceiling and wall luminaire (two variants)
• BEGA Smart Indoor table lamp (three variants)
• BEGA Smart Outdoor Ceiling and wall luminaire (35 variants)
• BEGA Smart Outdoor PRIMA wall luminaire (eight variants)
• BEGA Smart Outdoor PRIMA ceiling and wall luminaire (eight variants)
• BEGA Smart Outdoor PRIMA ceiling mounted downlight (eight variants)

For the full list of certified BEGA devices, see our filtered device list.

Dazzled by choice

With BEGA on board, Home Assistant users have more choice than ever when it comes to quality lighting, inside and out. Ready to explore the full range? Head over to our certified device list to be illuminated about everything that’s been approved from BEGA and beyond. The future of your smart home is looking bright 💡.

FAQs

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 later down the road, 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 the functionality you would expect within Home Assistant, operate locally without the need for cloud and that they 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 Hub with the Home Assistant Connect ZBT-2 and with our Zigbee integration (ZHA). If you have another hub/antenna setup/integration that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.

Will you be adding more BEGA devices to the program?

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

We’re thrilled to welcome ubisys to Works with Home Assistant! This German company has been dedicated to smart home automation for more than 20 years, and offers a range of Zigbee devices designed to help you retrofit your home. If retrofitting is conjuring up images of avocado bathrooms 🥑 and artexed ceilings, fear not – it just means upgrading what you already have, rather than ripping it out and starting again. Better for your home, and the planet 🌍.

Here today, here tomorrow

Founded in Düsseldorf in 2005, ubisys build devices that last. They back their hardware with a five-year warranty and software updates for the long term, meaning the device you buy today won’t end up obsolete in a few years’ time – in fact, they’re still shipping feature updates for hardware designed in 2010! That kind of longevity aligns closely with the Open Home Foundation’s own sustainability principle, and is just one reason why they’re such a great (retro)fit for the program! Zigbee is another…

Zigbee to the bone

If you’re scratching your head at the mention of Zigbee, allow me to explain: it’s a wireless standard that lets smart home devices communicate with each other, regardless of who made them. Unlike WiFi, it’s a mesh network, meaning Zigbee devices “talk” to each other, as well as to a central hub (like your Home Assistant setup), strengthening the connection across your whole home. It runs entirely locally, with no cloud dependency, and is optimized for long battery life.

For retrofit devices that need to just get on with their jobs in the background, these qualities really count, and explains why ubisys refer to Zigbee as the backbone of everything they build. And they don’t just use the standard, they help shape it: ubisys are active members of the Connectivity Standards Alliance (the organization responsible for maintaining and developing Zigbee), sitting on working groups and committees at the highest level – helping improve the standard for the benefit of the whole community. This commitment to open standards runs through everything ubisys do:

Devices

Every device in the Works with Home Assistant program is put through its paces by our in-house team before it earns certification, so when you see the badge, you know it works. But that’s not all: every partner must also commit to providing long-term support and firmware updates, and engaging with our community – all things we’re confident ubisys will deliver, for the reasons outlined above! 👆

These are the first Works with Home Assistant-certified Zigbee devices designed to fit behind your existing wall fixtures. Together they cover switch and scene control, energy monitoring, and heating:

• ubisys Control Unit C4 (Series 2)
• ubisys Heating Regulator H1
• ubisys Switching Actuator S1
• ubisys Switching Actuator S1-R (Series 2)
• ubisys Switching Actuator S2

It’s important to note that the actuators and control unit involve mains electricity, so must be installed by a qualified electrician: check the ubisys website for guidance. The H1 is more straightforward, since it simply clips onto your existing radiator valve and runs on AA batteries.

Ready to retrofit?

To use these devices with Home Assistant, you need a Zigbee adapter (a USB dongle that allows everything to communicate), and to enable Home Assistant’s built-in Zigbee Home Automation (ZHA) integration, which takes care of the rest. ZHA is supported by the Open Home Foundation, with full-time developers dedicated to working on it and helping certify new Works with Home Assistant Zigbee devices.

If you’d like to support this work, a Home Assistant Cloud subscription helps fund ZHA and the wider Open Home Foundation mission – all while giving you secure, remote access to your smart home.

We hope ubisys’s inclusion in the program means more Home Assistant users can upgrade their smart homes without starting from scratch – and with our certified device list growing all the time, there’s never been more ways to build the way you want. We look forward to seeing what you get up to! 👀

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 later down the road, 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 the functionality you would expect within Home Assistant, operate locally without the need for cloud, and that they 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 as a hub with the Home Assistant Connect ZBT-2, and with ZHA, our Zigbee integration. If you have another hub/adapter set-up/integration that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.

Will you be adding more ubisys devices to the program?

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

Where can I see what other devices have been certified?

You can find every Works with Home Assistant device on our certified device list. All products included have been rigorously tested by our team, and are built with privacy and local control at their core by partners committed to long-term support. We also flag which regions they are available in, and any known limitations on the list so you can make a fully informed decision before you buy.

Home Assistant 2026.4! 🎉

I’ll be honest: when I first heard the pitch for infrared support in Home Assistant, I wasn’t exactly jumping out of my chair. Infrared? That’s old tech! But that’s exactly the point. Think about how many TVs, air conditioners, and other appliances sitting in your home right now have an infrared receiver but no smart features whatsoever. With this release, all of those devices can get a smart future, showing up as actual, controllable devices in Home Assistant. Turns out, old tech can learn some very new tricks. 📡

Our purpose-specific automation triggers and conditions are back with a whole metric ton of new triggers and conditions! This effort, currently available through Home Assistant Labs, is now almost feature complete. If you haven’t tried it yet, please give it a shot; I’m really looking forward to your feedback. 🧠

There’s also plenty of fun stuff: background colors for dashboard sections, favorites on your dashboard cards, full Matter lock management with PIN codes, and you can now see what your AI-powered Assist is thinking while it processes your requests. Plus 14 new integrations! 🚀

Oh! And don’t forget: State of the Open Home 2026 is happening on April 8 in Utrecht, the Netherlands! Come celebrate everything we’ve built together in person. Tickets are limited, so grab yours while you can! 🎟️

Enjoy the release!

../Frenck

• Infrared becoming a first-class citizen of Home Assistant
  • Get started in just a few steps
  • Why this matters
• Purpose-specific automation triggers & conditions
  • Thinking in real-world concepts, not technical domains
  • New cross-domain triggers and conditions
  • More triggers and conditions for existing domains
  • Try it out!
• Background color for your dashboard sections
• Matter lock manager
• 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
  • Favorites on your dashboard
  • Gauge card redesign
  • Auto height for cards
  • What is an AI-powered Assist thinking?
• Need help? Join the community
• Disclosed security advisories
• Backward-incompatible changes
• Patch releases
  • 2026.4.1 - April 3
  • 2026.4.2 - April 11
  • 2026.4.3 - April 17
  • 2026.4.4 - April 24
• All changes

A huge thank you to all the contributors who made this release possible! And a special shout-out to @arturpragacz and @piitaya who helped write the release notes this release. Also, @mib1185, @missyquarry, @RaHehl, @CoMPaTech, @mikeodr, @silamon, and @tronikos for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️

Infrared becoming a first-class citizen of Home Assistant

This release introduces native infrared support in Home Assistant, opening the door to controlling a massive range of devices that were previously out of reach. Think about all those TVs, air conditioners, fans, sound bars, and other appliances sitting in your home that still rely on their little infrared remote. With this update, Home Assistant can now talk to them. 📡

You might already be familiar with how Bluetooth proxies transformed Bluetooth in Home Assistant, making it possible to reach Bluetooth devices anywhere in your home through relatively inexpensive ESPHome devices. We’re doing the same thing for infrared. With the new Infrared integration, Home Assistant now supports infrared proxies: small ESPHome-powered devices with an IR transmitter that can send infrared commands on behalf of Home Assistant. This means Home Assistant can now control any device that responds to an infrared remote, as long as there’s an integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that knows how to speak that device’s protocol.

The first integration to take advantage of this is the LG Infrared integration, which lets you control LG TVs from Home Assistant. It creates a media player entity with support for power, volume, channel control, and playback commands, plus button entities for all the common remote functions like input selection and navigation. Since infrared is one-way by nature, the integration uses assumed states for now, but it works remarkably well for day-to-day use.

Get started in just a few steps

Want to try it out? The quickest way to get started is with the Seeed Studio XIAO IR Mate. Head over to the ESPHome Ready-Made Projects page, connect the device to your computer, and flash it right from your browser. Once it’s set up and added to Home Assistant, you’ll have a working infrared proxy ready to go. Point it at your LG TV, set up the LG Infrared integration, and you’re controlling your TV from Home Assistant! 🎉

Why this matters

This is more than just a fun new feature. Bringing infrared support to Home Assistant aligns with the values of the Open Home Foundation, and especially sustainability. 🌱 There are millions of perfectly good appliances out there that aren’t “smart” but do have an infrared receiver. Instead of replacing them with newer connected versions, you can now integrate them into your smart home using a simple, relatively inexpensive IR transmitter. It’s a great way to extend the life of existing devices and reduce electronic waste. ♻️

We’re excited to see where this goes. The infrared support is designed to work with any IR protocol, and we’re looking forward to seeing integrations for more brands and device types. This is just the beginning!

Purpose-specific automation triggers & conditions

Since Home Assistant 2025.12, we’ve been working on making automationAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] building more natural. Instead of thinking in technical terms like 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] states and numeric thresholds, you can now pick things like “When a light turns on” or “If the climate is heating”. Each release since has added more, and this release brings the biggest batch yet.

But this release also brings something fundamentally new to the table: cross-domain triggers and conditions.

And yes, while this is still a Home Assistant Labs feature, we encourage you to give it a spin.

Thinking in real-world concepts, not technical domains

Up until now, every triggerA trigger is a set of values or conditions of a platform that are defined to cause an automation to run. [Learn more] and conditionConditions are an optional part of an automation that will prevent an action from firing if they are not met. [Learn more] was tied to a specific entity type. Want to know if a door opened? That used to depend on whether your door was represented as a magnetic contact sensor (a binary sensorA binary sensor is an entity that reports one of two mutually exclusive states, on or off. The device class determines how those states are labeled in the UI. For example, open/closed for a door or detected/clear for motion. [Learn more]), a motorized door such as a garage door (a coverCovers are devices such as blinds, garage doors, etc that can be opened and closed and optionally set to a specific position. [Learn more] entity), or something else entirely. You had to know the technical difference and pick the right one.

But that’s not how we think about our homes. We think in terms of doors, windows, motion, temperature, and humidity. These are real-world concepts that can be represented by different entity types in Home Assistant.

This release introduces 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] that work across entity types and are organized by what they mean, not where they live technically. A “door opened” trigger now responds to any door entity, whether it’s a contact sensor or a motorized cover. A “temperature changed” trigger picks up readings from temperature sensors, climateThe Climate entity allows you to control and monitor HVAC (heating, ventilating, and air conditioning) devices and thermostats. [Learn more] devicesA device is a model representing a physical or logical unit that contains entities., and water heaters alike. You no longer need to know the technical details behind the scenes.

And just like the purpose-specific triggers you already know, these new cross-domain triggers and conditions fully support targeting by areaAn area in Home Assistant is a logical grouping of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage. [Learn more], 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], or labelLabels 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]. That means you can create a trigger like “When a window on the upstairs floor is opened” without listing every single window. Add a new window sensor up there, and it’s automatically included.

New cross-domain triggers and conditions

The following new triggers and conditions now work across entity types. For each of these, you get both a trigger (“when” something happened) and a condition (“if” something is true), so you can use the same natural concepts throughout your automation:

• Door, garage door, gate, and window: trigger when they open or close, and check if they are currently open or closed (from both binary sensors and covers).
• Motion: trigger when motion is detected or cleared (across binary sensorA binary sensor is an entity that reports one of two mutually exclusive states, on or off. The device class determines how those states are labeled in the UI. For example, open/closed for a door or detected/clear for motion. [Learn more] and “event entities”Events are signals that are emitted when something happens, for example, when a user presses a physical button like a doorbell or when a button on a remote control is pressed. [Learn more]).
• Occupancy: trigger when occupancy is detected or cleared, and check if a space is occupied.
• Temperature: trigger when the temperature changes or crosses a threshold (from temperature sensors, climate devices, and more).
• Humidity: trigger when humidity changes or crosses a threshold, and check if it’s above or below a value (from humidity sensors, climate devices, humidifiers, and weather entities).
• Illuminance: trigger when the light level changes or crosses a threshold, and check if it’s above or below a value.
• Power: trigger when power consumption changes or crosses a threshold, and check current values.
• Battery: trigger when the battery level is low or not low, when charging starts or stops, when the level changes, or when it crosses a threshold. Check if the battery level is above or below a threshold.
• Air quality: check for detected pollutants like CO, CO2, smoke, and more.
• Climate: check if the current or target temperature is above or below a threshold.

More triggers and conditions for existing domains

On top of the cross-domain additions, a lot of existing 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. also gained new triggers and conditions:

• Counter gained triggers for when the counter is incremented, decremented, reset, or reaches its maximum or minimum value.
• Cover now has triggers and conditions for all cover types (blinds, shutters, shades, curtains, and awnings).
• Event entities now have a generic trigger that fires when any event is received.
• Humidifier now has a condition to check if the target humidity is above or below a threshold.
• Input boolean now works with switch triggers (and vice versa), because they behave identically.
• Input text now works with text triggers, just like text entities.
• Moisture now has triggers and conditions for when moisture is detected or cleared, when moisture values change, or when they cross a threshold.
• Remote gained turned on and turned off triggers.
• Schedule now has conditions to check if a schedule is active.
• Select gained triggers for when a selection changes and conditions to check if an option is selected.
• Text now has conditions.
• Temperature now has conditions to check if a temperature value is above or below a threshold.
• To-do list gained triggers for when an item is added, completed, or removed.
• Valve gained triggers for when a valve is opened or closed.
• Water heater gained both triggers and conditions, including an operation mode changed trigger.

Try it out!

Purpose-specific triggers and conditions are available as a preview feature in Home Assistant Labs. We’ve been building and refining this for over four releases now, and it’s getting really close to being feature complete. If you haven’t tried it yet, head over to Settings > System > Labs to enable it. We’d love your feedback!

Background color for your dashboard sections

Your dashboard sections can now have a background color! This is a great way to visually group related cards together, make certain sections stand out, or add a personal touch to your dashboard. 🤩

To add a background color to a section, open the section settings and turn on the Background toggle. From there, you can pick a color from a list of predefined options, or enter a custom hex color code. You can also adjust the opacity to get just the right look.

If you have sections side by side on the same row, sections without a background will automatically align with those that have one, keeping everything looking clean and tidy.

Matter lock manager

If you have a Matter-compatible smart lock, you can now manage your lock users and PIN codes directly from Home Assistant! 🔐

On the device page of your Matter lock, you’ll find a new Manage lock option. It opens a dialog where you can see all configured users, add new ones, edit existing ones, or remove them. When adding a new user, you give them a name, set a PIN code, and choose an access type: full access (can lock and unlock anytime) or one-time access (the code works once and is then automatically deleted by the lock).

Under the hood, this is powered by a new set of MatterMatter is an open-source standard that defines how to control smart home devices on a Wi-Fi or Thread network. [Learn more] lock 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] that are also available for use in your automationsAutomations in Home Assistant allow you to automatically respond to things that happen in and around your home. [Learn more] and scriptsScripts are components that allow you to specify a sequence of actions to be executed by Home Assistant when turned on. [Learn more]. You can, for example, create a one-time PIN code for a guest and send it in a notification, all from an automation! The available actions include creating and removing users, setting and clearing credentials (like PIN codes and RFID tags), and querying the lock’s capabilities.

Thanks, @Ahbrown41, for this awesome contribution! 🙌

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:

• Autoskope, added by @mcisk
  Integrate your Autoskope vehicle tracking devices with Home Assistant. Track the GPS location of your vehicles and other assets through Autoskope’s cloud services.

• Casper Glow, added by @mikeodr - launching at 🥈 silver quality
  Control your Casper Glow portable sleep light from Home Assistant over Bluetooth. Adjust brightness levels and incorporate this gentle-dimming sleep aid into your bedtime automations.

• Chess.com, added by @joostlek
  Monitor your Chess.com chess statistics in Home Assistant, including your ratings and game data.

• Fresh-r, added by @SierraNL - launching at 🥈 silver quality
  Monitor your Fresh-r ventilation devices in Home Assistant. Track indoor air quality, CO2 levels, and ventilation performance through the Fresh-r cloud dashboard.

• Infrared, added by @abmantis
  A new entity platform that provides an abstraction layer for infrared transmitter devices, allowing integrations to send IR commands to control TVs, air conditioners, and other IR-controlled appliances.

• LG Infrared, added by @abmantis - launching at 🥈 silver quality
  Control your LG TV using any infrared proxy configured in Home Assistant. Send commands over IR to manage power, volume, input sources, and more, using assumed states.

• Lichess, added by @aryanhasgithub
  Monitor your Lichess chess statistics in Home Assistant.

• LoJack, added by @devinslick - launching at 🥈 silver quality
  Connect your LoJack by Spireon vehicle tracking account to track the GPS location of your enrolled vehicles on the Home Assistant map.

• OpenDisplay, added by @g4bri3lDev
  Control your OpenDisplay BLE e-paper displays from Home Assistant. Devices are automatically discovered via Bluetooth, and you can send images to the display.

• Qube Heat Pump, added by @MattieGit
  Monitor your Qube heat pump in Home Assistant via Modbus TCP. Track energy performance and operational data from your heat pump on the local network.

• Solarman, added by @solarmanpv
  Integrate your Solarman smart energy devices with Home Assistant over the local network. Monitor energy production, consumption, and control devices like smart plugs and meter readers in real time.

• TRMNL, added by @joostlek - launching at 🏆 platinum quality
  Monitor your TRMNL e-paper (e-ink) displays in Home Assistant. Track battery levels and manage the display sleep schedule of your low-power e-ink devices.

• UniFi Access, added by @imhotep and @RaHehl - launching at 🥈 silver quality
  Control and monitor your Ubiquiti UniFi Access system locally from Home Assistant. Manage locks, doors, and access readers with real-time status updates over the local network.

• WiiM, added by @Linkplay2020
  Integrate your WiiM streamer devices with Home Assistant. Control playback, volume, and input sources on devices like the WiiM Pro and WiiM Amp, with automatic discovery via Zeroconf.

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:

• SmartThings received a massive wave of improvements this release. Robot vacuums gained fan speed control, select entities for driving mode and cleaning type, water spray and sound mode options, a sound detection switch with sensitivity control, a full dust-bag sensor, a HEPA filter reset button, and a time entity for Do Not Disturb schedules. Stick cleaner devices are now supported as well. Thanks, @joostlek! Dishwashers also picked up new start, pause, resume, cancel, and drain actions. Thanks, @edu-tsen!
• Roborock owners with a Q10 can now integrate their vacuum, thanks to @allenporter!
• OpenAI Conversation added GPT-5.4 and GPT-5.4-pro model support, including reasoning effort options. Thanks, @Shulyaka!
• SwitchBot picked up Keypad Vision support, bringing doorbell events, tamper alarms, and charging sensors to your setup. Thanks, @zerzhang!
• Govee BLE added the H5140 CO2 monitor, providing CO2 readings right in Home Assistant. Thanks, @funkadelic!
• SwitchBot Cloud can now control Standing Fan devices. Thanks, @XiaoLing-git!
• Jellyfin gained shuffle and enqueue support for its media player, giving you more playback control. Thanks, @ch604!
• GitHub picked up a merged pull requests count sensor for your repositories. Thanks, @abmantis!
• Proxmox VE expanded with uptime duration, memory usage, storage, network, and backup sensors, runtime entity discovery for nodes, VMs, and containers, a suspend all button at the node level, a snapshot button, and token-based authentication support. Thanks, @erwindouna!
• Renault exposes a charging settings mode sensor and battery charge limit controls to set your minimum and target state of charge. Thanks, @reneboer and @yoda-jm!
• Schlage gained actions for managing door lock access codes: add, delete, and retrieve codes directly from Home Assistant. Thanks, @tykeal!
• Kostal Plenticore added an active power limit control, letting you adjust your solar inverter’s output power. Thanks, @erikbadman!
• Portainer has new pause and resume buttons for container management. Thanks, @erwindouna!
• Teslemetry introduced an energy price calendar that shows your buy and sell tariff schedules, including time-of-use pricing periods. Thanks, @Bre77!
• Cambridge Audio devices gained an equalizer switch. Thanks, @Solmath!
• Gardena Bluetooth expanded to cover the Aqua Contour and Precise product line devices. Thanks, @elupus!
• HDFury picked up audio unmute offset controls for fine-tuning audio delay. Thanks, @glenndehaan!
• ToGrill lets you set ambient temperature range limits for alarms. Thanks, @pandanz!
• Smarla added a spring status sensor showing the spring constellation status. Thanks, @rlint-explicatis!

Integration quality scale achievements

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

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

• 5 integrations reached platinum 🏆

  • Opower, thanks to @tronikos
  • Portainer, thanks to @erwindouna
  • System Nexa 2, thanks to @konsulten
  • Teslemetry, thanks to @Bre77
  • Whisker (Litter-Robot), thanks to @natekspencer

• 5 integrations reached gold 🥇

  • Ghost, thanks to @JohnONolan
  • Liebherr, thanks to @mettolen
  • Mastodon, thanks to @andrew-codechimp
  • Samsung Smart TV, thanks to @chemelli74
  • Telegram bot, thanks to @hanwg

• 7 integrations reached silver 🥈

  • Actron Air, thanks to @kclif9 and @JagadishDhanamjayam
  • devolo Home Control, thanks to @2Fake and @Shutgun
  • FRITZ!Box Tools, thanks to @AaronDavidSchneider, @chemelli74, and @mib1185
  • Growatt Server, thanks to @johanzander
  • Smarla, thanks to @rlint-explicatis
  • Tessie, thanks to @Bre77
  • uhoo, thanks to @joshsmonta

• 3 integrations reached bronze 🥉

  • WaterFurnace, thanks to @masterkoppa
  • MyNeomitis, thanks to @l-pr
  • Satel Integra, thanks to @Tommatheussen

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:

• Leviton Decora Wi-Fi, done by @joostlek
• Orvibo, done by @peteS-UK

Farewell to the following

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

• BMW Connected Drive / Mini Connected has been removed. On September 29, 2025, BMW added additional security measures that block third parties from accessing BMW servers. For EU-registered cars, BMW now provides the CarData API, for which a custom integration has been developed.
• Duke Energy has been removed. Duke Energy changed authentication providers back in November 2025, and the integration has not worked since.
• Tfiac has been removed because a valid wheel cannot be created for its dependencies. It has been disabled since Home Assistant 2024.10.

Other noteworthy changes

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

• Voice: “Clean the kitchen”: In 2026.3, we added the ability to send your vacuum to clean specific areas. Back then, we mentioned that voice support wasn’t available just yet. Well, now it is! You can ask your voice assistant to clean a specific area, and your vacuum will head there. Thanks, @arturpragacz!
• Backup upload progress: When uploading a backup, you can now see the upload progress for each backup location. The backup page shows which step is active (creating the backup or uploading it), and for locations that support it, you’ll see a per-location upload percentage. This is supported by Home Assistant Cloud (by Nabu Casa), WebDAV, Google Drive, OneDrive, OneDrive for Business, and the S3-compatible integrations (AWS S3, iDrive e2, Cloudflare R2), as well as the built-in Home Assistant Supervisor backup. Thanks, @zweckj, @jpbede, @ludeeus, and @tronikos!
• Markdown card actions: The Markdown card now supports tap, hold, and double-tap actions. This means you can turn your Markdown cards into interactive elements that navigate, open URLs, or call actions when you interact with them. Thanks, @ildar170975 and @piitaya!
• Map card editor improvements: The map card visual editor now exposes all card-level and per-entity options, including label mode, color, and attribute selection. No more switching to YAML to customize your map. Thanks, @ildar170975!
• New template function: state_attr_translated: A new template function lets you retrieve translated attribute values for entities, like fan modes, HVAC actions, and preset modes. Works just like the existing state_translated, but for attributes. Thanks, @piitaya!
• New template function: entity_name: A new template function retrieves the name of an entity, making it easy to combine it with device and area names in your templates however you prefer. It is recommended to use this function instead of referencing the friendly_name attribute. Thanks, @arturpragacz!
• Network visualization search: Finding specific devices in the network visualization graph for ZHA, Z-Wave, and Bluetooth is now much simpler with the addition of a search box. Thanks, @abmantis!

Favorites on your dashboard

@karwosts is well known for contributing quality-of-life improvements, and this release is no exception. You could already save your favorite colors for lights in the more-information dialog, and now those favorites can be added as a card feature on your tile and light cards, bringing those one-tap color buttons directly onto your dashboard. 🌈

The card feature automatically shows as many of your saved favorites as can fit in the available space, giving you quick access to your preferred colors and color temperatures without opening the light’s more-information dialog.

@timmo001 extended the favorites concept to covers and valves! You can now save your favorite positions, like fully open, half open, or closed, from the more-information dialog and add them as a card feature too, just like with light colors.

@karwosts also made it possible to copy your favorites from one entity to others that support the same modes, so you don’t have to set them up from scratch for every light or cover. Nice!

Gauge card redesign

The gauge card got a fresh new look! @silamon gave it a visual overhaul, bringing a more modern and polished design that fits right in with the rest of your dashboard.

The new design keeps all the functionality you’re used to, including needle mode and severity segments, while giving the card a cleaner, more refined appearance. A well-deserved refresh!

Auto height for cards

Cards can automatically adjust their height based on their content, instead of occupying a fixed number of grid rows. While this was previously only available through manual YAML configuration, the card layout editor now has an Auto height option, making it accessible for everyone.

Some cards, like the entities card and vertical stack card, already default to auto height. For other cards, you can now enable it yourself in the card’s layout settings. This is especially handy for cards with variable content, so they no longer leave empty space or cut off content.

What is an AI-powered Assist thinking?

If you use an LLM-powered conversation agent with Assist, you may have wondered what’s going on behind the scenes when it’s processing your request. Now you can find out! The Assist dialog now shows you the thinking steps and tool calls your AI agent makes while working on your request.

Each response from the AI agent now has a collapsible Show details section. Expand it to see the agent’s reasoning process, which tools it called, what arguments it passed, and what results it got back. This is great for understanding how your AI agent arrives at its answers, and super helpful when debugging automations or tweaking your agent’s behavior.

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.

Disclosed security advisories

This month, we published the following security advisories for vulnerabilities that have been found and fixed. We always disclose security issues with a delay, giving everyone time to update their systems first. This is why keeping your Home Assistant installation up to date is so important.

For more information on our security policy and past advisories, visit our security page.

• 2026-03-27: Stored XSS in map card through malicious device name
  Severity: Moderate
  Detailed information: Security advisory
  Assigned CVE: CVE-2026-33044
  Discovered by: @pwnpanda
  Fixed in: Home Assistant Core 2026.1.2

• 2026-03-27: Stored XSS in history graph card
  Severity: Moderate
  Detailed information: Security advisory
  Assigned CVE: CVE-2026-33045
  Discovered by: @pwnpanda
  Fixed in: Home Assistant Core 2026.1.2

• 2026-03-27: Unauthenticated app (add-on) endpoints exposed to local network via host network mode
  Severity: Critical (CVSS: 9.7)
  Detailed information: Security advisory
  Assigned CVE: CVE-2026-34205
  Discovered by: @arturpragacz
  Fixed in: Home Assistant Supervisor 2026.03.2

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:

• Backup agents can now report upload progress
• Frontend component updates 2026.4
• Frontend lazy context
• Frontend new way of dialogs
• New infrared entity platform for IR device integrations

Patch releases

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

2026.4.1 - April 3

• Fix tuya energy sensor units (@jbouwh - #160392)
• Fix Ring snapshots (@Ltek - #164337)
• Fix Tesla Fleet charge current scope handling (@Bre77 - #166919)
• Fix Tesla Fleet OAuth scope refresh during reauth (@Bre77 - #166920)
• Fix select condition state selector (@bramkragten - #167064)
• Fix websocket calling async_release_notes in update component although unavailable (@tr4nt0r - #167067)
• Fix Proxmox VE backup status sensor false positive due to case mismatch (@irishpadres - #167069)
• Bump pySmartThings to 3.7.3 (@joostlek - #167075)
• Wrap hassio import in is_hassio check in get_system_info helper (@mdegat01 - #167111)
• Remove not implemented supported feature from Wiim (@joostlek - #167205)
• Migrate image unique_id for Fritz (@chemelli74 - #167209)
• Fix SMHI (@gjohansson-ST - #167212)
• Bump holiday library to 0.93 (@gjohansson-ST - #167217)
• Fix Sonos reporting wrong state when media title is whitespace (@PeteRager - #167223)
• Improve Recorder action naming consistency (@NoRi2909 - #167244)
• Update arcam to 1.8.3 (@elupus - #167249)
• Bump psutil to 7.2.2 (@dotlambda - #167263)
• Remove Transmission port forward sensor (@andrew-codechimp - #167269)
• Improve Media player action naming consistency (@NoRi2909 - #167274)
• Bump zinvolt to 0.4.0 (@joostlek - #167276)
• Improve Assist satellite action naming consistency (@NoRi2909 - #167278)
• Fix to allow Matter Fan percent setting to be null when FanMode is Auto (@lboue - #167279)
• Update frontend to 20260325.6 (@bramkragten - #167285)
• Fix Matter water heater off mode (@lboue - #167286)
• Make sure we take all Zinvolt battery units in account (@joostlek - #167294)
• Bump Zinvolt to 0.4.1 (@joostlek - #167296)
• Bump soco to 0.30.15 (@PeteRager - #167299)
• Sonos alarm switch entities may not be created when speaker offline initially (@PeteRager - #167303)

2026.4.2 - April 11

• Improve handling of disconnected meters with Rainforest Automation Eagle-200 (@SkySrfr - #161185)
• Prevent the intellifire client from polling independently of its coordinator (@jeeftor - #165341)
• Switchbot Cloud: Enable Webhook for Bot (@XiaoLing-git - #165647)
• Include port in BSB-LAN configuration URL when non-default (@liudger - #166480)
• Fix incorrect state for some LG Soundbar models (@alexmerkel - #167094)
• Bump aiopvpc to 4.3.1 (@marcomsousa - #167189)
• Bump starlink-grpc-core to 1.2.5 (@patcfly - #167195)
• Allow force alarm actions for Comelit (@chemelli74 - #167202)
• Add Hisense AC to Matter dry and fan mode device lists (@lboue - #167282)
• Bump pyTibber to 0.37.0 (@Danielhiversen - #167283)
• Fix victron ble reauth flow title (@rajlaud - #167307)
• Update to tplink-omada-client 1.5.7 (@MarkGodwin - #167313)
• Bump afsapi to 0.3.1 (@007hacky007 - #167321)
• Bump pylutron to 0.4.1 (@cdheiser - #167324)
• Bump cryptography to 46.0.6 (@pantherale0 - #167330)
• Align and cleanup tests data for Fritz (@chemelli74 - #167363)
• Bump aiohue to 4.8.1 (@joostlek - #167369)
• Improve ProxmoxVE permissions handling (@CoMPaTech - #167370)
• Bump axis to v68 to improve MQTT event resiliance (@Kane610 - #167373)
• Use dedicated session for seventeentrack to preserve login cookies (@shaiu - #167394)
• Bump aiocomelit to 2.0.2 (@chemelli74 - #167414)
• Fix setup without dhw (@liudger - #167423)
• Fix handling of missing period statistics in Anglian Water coordinator (@pantherale0 - #167427)
• Fix missing color_mode initialization in MQTT JSON light schema (@noerstad - #167429)
• Bump jvcprojector dependency to pyjvcprojector 2.0.5 (@SteveEasley - #167450)
• Fix nzbget positional argument mismatch in NZBGetAPI calls (@JamieMagee - #167456)
• Update roborock services to raise ServiceNotSupported for new devices that don’t yet support it (@allenporter - #167470)
• Miele - fix core temperature reading (@aturri - #167476)
• Bump b2sdk to 2.10.4 (@ElCruncharino - #167481)
• Handle BadRequest exception in Backblaze B2 config flow and setup (@ElCruncharino - #167482)
• Bump pynintendoparental to 2.3.4 (@pantherale0 - #167510)
• Add missing Miele dishwasher program ID 201 (@runningcode - #167536)
• Bump python-picnic-api2 to 1.3.4 (@xZise - #167539)
• Bump incomfort-client to v0.7.0 (@jbouwh - #167546)
• Remove homeassistant/actions/helpers/info from builder workflow (@sairon - #167573)
• Set up condition and trigger helpers in check config script (@arturpragacz - #167589)
• Fix EWS deviceType problem (@l-pr - #167597)
• Fix Tractive switch availability (@bieniu - #167599)
• Bump securetar to 2026.4.0 (@emontnemery - #167600)
• Fix securetar size calculation when encrypting backup (@emontnemery - #167602)
• Bump holidays to 0.94 (@gjohansson-ST - #167604)
• Fix ProxmoxVE migration causing reauthentication (@CoMPaTech - #167624)
• Improve error logging for Backblaze B2 upload failures (@ElCruncharino - #167721)
• Bump pyvlx to 0.2.33 (@wollew - #167764)
• Set proper state for the internet_access switches in FRITZ!Box Tools (@mib1185 - #167767)
• Bump aiotractive to 1.0.2 (@bieniu - #167783)
• Revert “Fix Ring snapshots” (@bhudgens - #167790)
• Fix Victron BLE false reauth triggered by unknown enum bitmask combinations (@rajlaud - #167809)
• Fix Victron BLE storage errors caused by non-serializable value_fn callable in sensor entity description (@rajlaud - #167819)
• Support Chess.com accounts with no name (@joostlek - #167824)
• Fix stale devices removal for Alexa devices (@chemelli74 - #167837)
• Fix service.yaml values for Home Connect (@Diegorro98 - #167847)
• Bump ZHA to 1.1.2 (@TheJulianJES - #167849)
• Bump velbusaio to 2026.4.0 (@cereal2nd - #167868)
• Bump zinvolt to 0.4.3 (@joostlek - #167908)
• Bump qbusmqttapi to 1.4.3 (@thomasddn - #167909)
• Bump oasatelematics to 0.4 (@panosmz - #167911)
• Fix light on action for qbus integration (@thomasddn - #167917)
• Bump pylitterbot to 2025.2.1 (@natekspencer - #167921)
• Update frontend to 20260325.7 (@bramkragten - #167922)
• Bump pyrisco to 0.6.8 (@OnFreund - #167924)
• Improve Tibber price coordinator (@Danielhiversen - #166175)
• Fix tibber price sensor first state update (@MartinHjelmare - #167938)
• Update cryptography to 46.0.7 (@frenck - #167960)
• Fix spelling of “Shut down” button label in proxmoxve (@NoRi2909 - #167059)
• Bump opower to 0.18.1 (@tronikos - #167967)
• Portainer fix fetching swarm stacks (@erwindouna - #167979)
• Bump python-bsblan to version 5.1.4 (@liudger - #167987)

2026.4.3 - April 17

• Fix Proxmox VE storage usage percentage crash on missing used_fraction (@irishpadres - #167136)
• Fix device_class removal in template binary sensors (@timmo001 - #167775)
• Fix openevse charging_current and charging_power units (@c00w - #167863)
• Don’t create cpu temperature sensor when not supported in FRITZ!Box Tools (@mib1185 - #167905)
• Fix ESPHome cold/warm white color temperature read-back (@bdraco - #167972)
• Fix missing kWh unit for dlq ADD_ELE energy sensor (@gerculanum - #168026)
• Bump PySwitchbot to 2.0.1 (@zerzhang - #168090)
• Bump satel_integra to 1.1.0 (@Tommatheussen - #167353)
• Bump satel-integra to 1.1.1 (@Tommatheussen - #168091)
• Update Z-Wave cover moving state based on current position and cover capabilities (@AlCalzone - #168096)
• Fix Switchbot Keypad Vision doorbell detection (@zerzhang - #168098)
• Bump aioamazondevices to 13.4.0 (@chemelli74 - #167984)
• Bump aioamazondevices to 13.4.1 (@chemelli74 - #168121)
• Bump pylitterbot to 2025.3.2 (@natekspencer - #168146)
• Fix Wyoming satellite memory leak on disconnect (@marcelveldt - #168152)
• Bump pyenphase from 2.4.6 to 2.4.8 (@catsmanac - #168190)
• Handle Tibber async_get_client failing (@Danielhiversen - #168207)
• Bump pyTibber to 0.37.1 (@Danielhiversen - #168208)
• Update Pillow to 12.2.0 (#168234)
• Update uv to 0.11.6 (#168237)
• Fix unit of measurement for SPH power sensors in growatt_server (@johanzander - #168251)
• Bump PyViCare to v2.59.0 (@CFenner - #168254)
• Bump imgw-pib to 2.1.0 (@bieniu - #168319)
• Fix VOIP blocking call in event loop (@jaminh - #168331)
• Fix disabled discovered MQTT entities cleaned up (@jbouwh - #168382)
• Update satel-integra to 1.2.1 (@Tommatheussen - #168416)
• Add cleaning codes for Miele steam oven combo (@astrandb - #168418)

2026.4.4 - April 24

• Fixed Kodi Media Browsing (@albaintor - #165819)
• Fix Victron BLE false reauth on unrecognised advertisement mode bytes (@rajlaud - #168209)
• Fix case-sensitive MIME type check in Google Generative AI TTS (@MohamedBarrak3 - #168458)
• Hive - Bump pyhive-integration to 1.0.9 (@KJonline - #168489)
• Bump aioamazondevices to 13.4.3 (@chemelli74 - #168536)
• Fix MQTT JSON light restoring None color_mode on startup (@noerstad - #168608)
• Add Roborock fan speed validation and error handling (@allenporter - #168623)
• Correct state/device class for water in gardena (@elupus - #168637)
• Cancel and await idle_start future if the task was canceled after an IMAP connection was lost (@jbouwh - #168662)
• Validate local_only user property during ws auth phase (@edenhaus - #168812)
• Update Tibber library, 0.37.2 (@Danielhiversen - #169027)
• Slow down Tractive API polling to avoid 429 too many requests (@bieniu - #169057)
• Bump aiotractive to 1.0.3 (@bieniu - #169059)
• Validate local_only user for signed requests (@edenhaus - #169066)
• Update frontend to 20260325.8 (@bramkragten - #169076)

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

Backups are one of those quiet, powerful features: when they work, you don’t notice them, but when you need them, they’re everything. We’ve evolved Home Assistant’s built-in backup format over the years to keep it safe and secure, especially when backing up to remote locations. As modern cryptography has advanced, we needed to build a system to match. SecureTar v3 is a purpose-built library for creating and reading password-protected Home Assistant backups with modern cryptography and safer, stronger defaults.

To help us get this right, we commissioned Trail of Bits, a leading security engineering firm, to independently audit our work. Their review found that SecureTar v3 follows best-in-class practices for core security algorithms, such as hashing and encryption. They also identified three areas for improvement, which they confirmed were resolved in their follow-up review. This audit was paid for by the Open Home Foundation so we could invest in improvements that protect users’ privacy, security, and control.

Your backups will start using this new encryption automatically, beginning with the release of version 2026.4 on April 1, 2026. Please note old backups will still work and be readable after this change (see Recommended next steps below). For more technical details, please read on…

A bit of history

Home Assistant backups have always been encrypted by default, and use a high entropy key, to help ensure your data is safe. When we introduced backups, early formats (v1 and v2) used the same AES-128 encryption variant, along with a simple key derivation (the code that turns your passphrase into the actual key used for encryption). Sam Gleske brought to our attention that the key-derivation step was no longer up to modern standards.

It’s worth stressing an important point: Home Assistant’s passphrase generator already produces long, high-entropy passphrases. This means that backups created previously were difficult to break if using this feature. To demonstrate this, we calculated that a brute force passphrase attack (where attackers try many passwords rapidly) on the backups would take more time than the average lifespan of a person to be successful.

Still, because it was possible to manually generate an insecure passphrase for advanced users, and the library’s internal cryptographic primitives could be improved, we decided to overhaul SecureTar to use best-in-class algorithms, and to have that work validated by an external audit.

What we changed and why

The goals were simple: choose modern, well-studied algorithms, avoid design mistakes that could weaken confidentiality or integrity, and make v3 the secure default.

Highlights of the SecureTar v3 design:

• Modern key derivation: SecureTar v3 uses Argon2id for password-based key derivation. Argon2id is a memory-hard algorithm that makes brute-force attacks much more costly.
• Modern encryption and authentication: Encryption is provided by the libsodium secretstream API (exposed in Python via PyNaCl), which implements a robust streaming authenticated-encryption construction using XChaCha20-Poly1305. That combination gives both confidentiality (nobody can read your data) and integrity/authentication (nobody can tamper with it without detection).
• Safer defaults and parsing: We set safer defaults so new backups use v3, and we fixed parsing logic to avoid silently treating corrupt data as valid legacy backups.

We made these choices to ensure that SecureTar is resilient to modern attacks and easier to reason about from a security perspective.

Independent audit by Trail of Bits

After implementing SecureTar v3, we commissioned Trail of Bits to perform the focused security assessment and fix review. Here is what the review found:

1. Timing side-channel in a validation comparison (informational): The audit pointed out a minor coding issue in how we checked a validation key. It wasn’t a security risk (the value is stored openly in the file header), but we updated the check to a safer form so security tools stop flagging it.
2. Insecure fallback to legacy protocol version (informational): Header parsing logic could be confused by corrupted data; we updated the logic so corrupted headers raise an error instead of silently falling back.
3. Supply-chain risk in GitHub Actions workflow (medium): Workflow steps were not pinned to specific commit hashes and used broad permissions, opening the build process to possible supply-chain attacks. We pinned actions to specific commit hashes and tightened permissions.

Crucially, Trail of Bits’ post-fix review confirmed all three findings were resolved. This shows we have not only adopted modern cryptography, but also closed the gaps the audit exposed.

You can read more about the audit and the fixes in the Trail of Bits report.

How you help support this work

Security work (especially external audits and specialist engineering) costs money. The Open Home Foundation provides the structure and finances that let us do this work. That money comes, in part, from people who buy official Home Assistant or ESPHome products from the foundation’s commercial partners, and merchandise from the Open Home Foundation Store: we really appreciate your support!

Because of this, we were able to commission experts, invest engineering time, and validate the fixes. That investment protects users’ backups (which often contain configurations, passwords and API keys, integrations, and automations) and keeps Home Assistant a trustworthy, secure platform for everyone.

Recommended next steps

• Ensure Home Assistant is updated to the latest version. The 2026.4 release includes SecureTar v3.
• Any encrypted backup created after updating to 2026.4 will use v3’s improved format.
• Existing backups are still secure, as Home Assistant’s generated passphrase is strong. That said, for extra security, you can regenerate the encryption key in your backup settings (use the Change encryption key option at the bottom of the backup settings page).
• If you use the ha backup CLI command, or the hassio.backup_full or hassio.backup_partial actions to create backups, and you’ve used a short/low entropy password, you should choose a new password.

For the curious: technical summary

• Key derivation: Argon2id (memory-hard), using separate sub-keys for each backup part.
• Encryption / AEAD: XChaCha20-Poly1305 via libsodium secretstream (PyNaCl) with 256-bit key size. AEAD means your data is not only encrypted, but also authenticated (validating the data is unchanged/not tampered with).
• Audit: Trail of Bits: 3 findings (2 informational, 1 medium), all resolved.
• Build hardening: GitHub Actions pinned to commit SHAs and narrower permissions to reduce supply-chain risk.

Looking for more? Check out the SecureTar repository on GitHub.

Final note

Security is iterative, and this latest work has helped build a stronger foundation for Home Assistant backups, and a clearer path forward for maintaining that security over time.

If you want to read about similar past efforts, see some of our other posts:

• One of our past security audits
• The upcoming release notes for Home Assistant 2026.4

By keeping Home Assistant secure, we make the platform safer, more trusted, and more enjoyable for the whole community. Thank you.