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
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. ❤️
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.
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:
On the other side, device-specific integrations use the platform to actually do something useful. Two are shipping in this release:
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. ♻️
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. 🎉
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. 🪄
This is great news if you’ve ever struggled to put a serial-connected device exactly where you wanted it. A few practical examples:
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. 🌱
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:
Log inpyserial 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.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. 🛠️
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. ✅
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. 🏠
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! 👏
Tip
Are you a developer? Each one of these built-in dashboards is powered by a dashboard strategy: a piece of code that generates a complete dashboard on the fly, tailored to your home. Starting with this release, you can register your own custom dashboard strategies from a custom integration or frontend module, and share them with the community.
Imagine a strategy that builds the perfect dashboard for your plants, your 3D printers, your home lab, or your aquarium, automatically, for anyone who installs it. We can’t wait to see what you create. 🌱
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).
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. 🎨
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:
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.
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. 🎚️
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. ⏱️
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:
It’s a small-looking addition with an outsized impact: a whole category of “almost possible” automations just became easy to put together.
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. 🔔
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. Those the triggers entered_home and left_home as also the conditions is_home and is_not_home got removed from the Person and Device Tracker. They will get successor in one of the upcoming releases.
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. 💚
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 🥰
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.
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:
html5.send_message entity action, and the integration is now correctly classified as a notification service. Thanks, @tr4nt0r!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 🏆
2 integrations reached gold 🥇
3 integrations reached silver 🥈
2 integrations reached bronze 🥉
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! 👏
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:
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:
There are many more improvements in this release; here are some of the other noteworthy changes:
clean_segment action, plugging straight into the new Clean by area view. 🧹 Thanks, @gustavakerstrom!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 are meant to match areas (or rooms) in the physical world: your home. For example, the living room area groups devices and entities in your living room. [Learn more] 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. ✅
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. ⌨️
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:
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. 💪
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:
states(), is_state(), and state_attr(), including the states["..."] shorthand.device_entities(), device_name(), and device_attr(), showing the device’s friendly name with the raw ID as the inserted value.area_entities(), area_devices(), and area_name().floor_areas(), floor_entities(), and floor_name().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. 🔍
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.
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:
When we first introduced purpose-specific triggers and conditions, we added separate ones for Person entities and Device Tracker entities. Since then, we’ve decided to take a more ergonomic, cross-domain approach instead.
As a result, the entered home and left home triggers, and the is home and is not home conditions, have been removed from Person and Device Tracker. Replacements that work across both will land in an upcoming release.
If you have automations that use these triggers or conditions on a person or device tracker, switch them back to a regular state trigger or state condition (for example, state changed to home) until the cross-domain replacements arrive.
(@emontnemery - #168406)
The “finish watering” value in the Gardena Bluetooth integration has been moved from a binary sensor to a regular sensor that exposes the timestamp of when watering is expected to finish. This makes the value far more useful in dashboards and automations.
If you have automations, scripts, or dashboards that reference the previous binary sensor entity, update them to use the new sensor entity instead.
The pilight integration has been disabled because the underlying pilight library relies on setuptools.pkg_resources, which is no longer available in setuptools 82.0.0 and later.
If the library is updated to remove the setuptools.pkg_resources dependency, or replaced with a maintained alternative that does so, the integration can be activated again. Community contributions to make this happen are very welcome.
The Ring doorbell event entity now emits the standardized ring event type instead of the legacy ding. This change aligns Ring with the new doorbell event standard, so the entity can be used seamlessly with the new purpose-specific automation triggers and conditions.
If you have automations that listen for the ding event type from your Ring doorbell, update them to use ring instead.
Previously, all actions registered by the Supervisor integration (such as hassio.addon_start, hassio.backup_partial, and hassio.host_reboot) only logged an error on failure, and your script or automation would continue running regardless of whether the action succeeded.
These actions now properly raise on failure, which means your automation or script will stop unless continue_on_error is set to true. If you rely on the previous behavior, add continue_on_error: true to those action steps.
The local_only option on webhooks must now be a proper boolean (true or false). Previously, other truthy values like 1 or "yes" were silently accepted. This brings the option in line with the rest of Home Assistant.
If you have webhooks configured in YAML with non-boolean local_only values, update them to use true or false.
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:
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.
is_closed state for DynamicGarageDoor in Overkiz (@iMicknl - #170052)is_closed state to None when a cover state returns “unknown” in Overkiz (@iMicknl - #170081)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.
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.
"With BEGA Smart, we aim to combine high-quality architectural lighting with intelligent control. Integrating with Home Assistant allows us to bring our lighting solutions into an open and flexible smart home ecosystem that many of our customers already value. By doing so, we enhance comfort, safety, and energy efficiency while enabling new ways to experience light. We're excited to support the community and be part of this ecosystem."
- Heinrich Gantenbrink, Managing Partner at BEGABEGA’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 😎.
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.
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.
For the full list of certified BEGA devices, see our filtered device list.
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 💡.
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.
Hi,
The OpenWrt community is proud to announce the third service release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See the full changelog for details.
New devices supported in 25.12.3:
Device fixes:
erp_domain and fils_cache_id values generated by the ucode-based config script (#21768)bridge_isolate and network_vlan fields to the ucode schema (#22620)iface and other fields to the ucode station/vlan schema (#22165)set_fixed_freq-u option (skip default configuration) which was broken with apk-f (custom backup) when the path contains spacesDISKSEQ instead of MAJOR/MINOR for stable disk identification (MAJOR/MINOR are not sequential)devpath option for selecting cellular modems by USB device pathkmod-vsock and kmod-vsock-virtio for VM guests (vsock communication)Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.
Sysupgrade from 23.05 or earlier to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed. fc0c518
Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4, and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe
TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).
Meraki MX60: Direct sysupgrade to 25.12.3 is not possible without manual preparation — meraki_loadaddr must be changed before upgrading, as the default value is insufficient to boot OpenWrt 25.12+. See the device wiki page for instructions.
eth1 to wan — check and update your network configuration after upgrading.cake_mq): throughput may be unexpectedly low on some configurations after the scheduler fixes in this release. #22344Full release notes and upgrade instructions are available at
https://openwrt.org/releases/25.12/notes-25.12.3
In particular, make sure to read the known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.3#known_issues
For a detailed list of all changes, refer to
https://openwrt.org/releases/25.12/changelog-25.12.3
To download the 25.12.3 images, navigate to:
https://downloads.openwrt.org/releases/25.12.3/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.3
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
Have fun!
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in
the future, they will be listed at https://openwrt.org/contact
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 🌍.
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…
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:
"We are convinced the future of smart homes lies in openness and robust interoperability. This partnership is a testament to that shared vision, and represents a significant step in deepening our integration with Home Assistant -- helping empower the most vibrant, tight-knit community in the smart home space. This community is the true engine of innovation. By achieving this certification, we're ensuring our devices integrate more seamlessly than ever into Home Assistant's robust ecosystem, providing the reliability and performance this community expects and deserves. We look forward to supporting the brilliant, custom solutions they will build."
- Dr.-Ing Arasch Honarbacht, Founder & Engineering LeadEvery 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:
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.
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! 👀
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/antennae 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
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. ❤️
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.
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! 🎉
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!
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.
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 returns information about things that only have two states - such as on or off. [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 are meant to match areas (or rooms) in the physical world: your home. For example, the living room area groups devices and entities in your living room. [Learn more], 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.
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:
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:
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!
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.
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! 🙌
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 🥰
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.
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:
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 🏆
5 integrations reached gold 🥇
7 integrations reached silver 🥈
3 integrations reached bronze 🥉
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! 👏
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:
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:
There are many more improvements in this release; here are some of the other noteworthy changes:
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!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!@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!
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!
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.
Note
As part of this change, heading cards now default to auto height as well, making them shorter (about half a grid row). This is only visible for heading cards placed between other cards; headings at the top of a section are unaffected. The default row gap between sections also increased from 8 pixels to 24 pixels, giving sections a bit more breathing room. To restore the previous compact layout, set the ha-view-sections-row-gap theme variable to 8px in your theme.
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.
Note
This feature is currently available on the desktop web interface only, and not yet in the Home Assistant mobile companion apps.
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.
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
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:
The Picture Mode and HDR Processing entities have been migrated from the sensor domain to the select domain, because they represent selectable settings rather than read-only values.
New entities:
select.jvc_projector_picture_modeselect.jvc_projector_hdr_processingThe legacy sensor entities are now deprecated. If a deprecated sensor is disabled and not referenced by automations or scripts, Home Assistant will remove it from the entity registry. If usage is detected, Home Assistant keeps it and shows a repair issue to help you migrate. Update your automations, scripts, dashboards, and templates to use the new select entities.
The deprecated night light mode switch entity for Litter-Robot 4 devices has been removed. This switch was replaced by a select entity in Home Assistant 2025.10. If you still use the old switch entity in your automations or scripts, update them to use the select entity instead.
On devices that support tilt but do not report a tilt position, the tilt open and tilt close operations now send jog up and jog down commands instead of setting the tilt angle to 0° or 180°. Setting an absolute tilt position usually didn’t work on these devices anyway, and jog commands provide a meaningful small step in the intended direction.
If you have automations that rely on the previous tilt behavior for these devices, you may need to adjust them.
Support for the object_id option has been removed after 6 months of deprecation. This option was used to suggest the entity ID for an MQTT entity and has been replaced by the default_entity_id configuration option.
If you used object_id in your MQTT YAML configuration, you were previously asked via a repair flow to update your configuration. If object_id is still part of a discovery message, the option will simply be ignored and will not break discovery.
(@jbouwh - #164460) (MQTT documentation)
pyLoad 0.4.x is now deprecated, and you should switch to pyLoad-ng 0.5.0. pyLoad-ng introduced a new API, and support for the old API has been dropped.
The preset mode names for the Roth Touchline climate entities have been updated to use standard Home Assistant preset names, making them translatable. If you have automations or scripts that reference the old preset mode names, update them to use the new names:
Normal → noneNight → sleepHoliday → awayPro 1 → program_1Pro 2 → program_2Pro 3 → program_3Previously deprecated switch entities used to control valves have been removed. Use the valve entities instead. If you have automations or scripts that reference these switch entities, update them to use the corresponding valve entities.
(@epenet - #164657) (Tuya documentation)
The Z-Wave Installer panel has been removed. This panel was hidden and required an undocumented YAML configuration to enable. The same functionality is now natively available through Z-Wave JS UI in the Z-Wave app.
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:
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.
async_release_notes in update component although unavailable (@tr4nt0r - #167067)proxmoxve (@NoRi2909 - #167059)imgw-pib to 2.1.0 (@bieniu - #168319)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.
Hi,
The OpenWrt community is proud to announce the second service release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See the full changelog for details.
kmod-pwm-an7581 to kmod-pwm-airoha — users with this module explicitly installed need to reinstall under the new nameUpgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.
Sysupgrade from 23.05 or earlier to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed. fc0c518
Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4, and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe
TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).
Meraki MX60: Direct sysupgrade to 25.12.2 is not possible without manual preparation — meraki_loadaddr must be changed before upgrading, as the default value is insufficient to boot OpenWrt 25.12+. See the device wiki page for instructions.
eth1 to wan — check and update your network configuration after upgrading.cake_mq): throughput may be unexpectedly low on some configurations after the scheduler fixes in this release. #22344Full release notes and upgrade instructions are available at
https://openwrt.org/releases/25.12/notes-25.12.2
In particular, make sure to read the known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.2#known_issues
For a detailed list of all changes, refer to
https://openwrt.org/releases/25.12/changelog-25.12.2
To download the 25.12.2 images, navigate to:
https://downloads.openwrt.org/releases/25.12.2/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.2
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
Have fun!
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact
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…
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.
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:
We made these choices to ensure that SecureTar is resilient to modern attacks and easier to reason about from a security perspective.
After implementing SecureTar v3, we commissioned Trail of Bits to perform the focused security assessment and fix review. Here is what the review found:
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.
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.
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.Looking for more? Check out the SecureTar repository on GitHub.
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:
By keeping Home Assistant secure, we make the platform safer, more trusted, and more enjoyable for the whole community. Thank you.
We’re thrilled to extend a very warm (ahem) Works with Home Assistant welcome to Heatit! As the name suggests, Heatit are all about keeping you, and your home, warm. They specialize in smart climate and heating control, which might have something to do with the fact they’re based in Norway, where energy management is a big reason people turn to Home Assistant, as winter temperatures can dip to below -20°C!
Formerly known as Thermofloor, Heatit has spent more than 30 years building a rock-solid reputation across Scandinavia and Northern Europe for thermostats and controllers designed to handle harsh conditions, so they’re certainly robust enough for milder climes. But they don’t just stop at heating: the range extends to home safety, with the Heatit Z-Smoke 2 being the first Z-Wave smoke detector we’ve certified.
In fact, all of Heatit’s certified devices connect via Z-Wave, which is what makes them integrate so well with Home Assistant. Crucially, the Z-Smoke 2 will always function regardless of network status. The smart features are there when you need them, but the fundamentals never depend on them.
If you’ve not heard of Z-Wave before, here’s a quick explainer: it’s a low-power wireless protocol built specifically for smart homes. Unlike WiFi, it operates on a dedicated frequency that means less interference and more reliable communication. It’s also a mesh network, where mains-powered devices help pass signals along to each other, strengthening the connection. Battery-powered devices can also benefit from this, since the mesh helps preserve their charge.
For heating and safety devices, those enhancements really count. Long battery life means a thermostat or smoke detector that should keep working without constant attention. Reliable range means your devices can stay connected even through thick walls or across a large home. And because everything runs locally, your heating responds quickly: no routing through a third-party server, no unnecessary delays.
Heatit are also serious about the impact they have beyond their products, with sustainability and reducing environmental impact being central to their company philosophy, which aligns with the Open Home Foundation’s principles of privacy, choice, and sustainability. What’s more, for Heatit, one of the most exciting things about joining the program is the chance to connect with the passionate, knowledgeable people who make up our community (yes, that’s you!).
"We're excited to join the Home Assistant program because of the strong community and the shared focus on open, local-first smart home solutions. This integration allows us to work more closely with both enthusiasts and professionals, and to deliver products that are flexible, reliable, and built for long-term use."
- Pål Aksel Forberg, CEO at HeatitWorks with Home Assistant isn’t just a badge: every certified product is rigorously tested by our in-house team to make sure it works seamlessly with Home Assistant out of the box. Brands joining the program also commit to long-term support and firmware updates, and to being an active, positive part of our community. Here’s what’s made the cut from Heatit:
Professionally built and designed to last, these devices cover both sides of a smart heating setup: the thermostats handle the actual temperature control, while the wall controller gives you a physical way to manage it all without reaching for your phone.
It’s worth noting that in-wall devices will require installation by a qualified electrician in many regions, so if you’re not confident with electrics, it’s worth checking Heatit’s website for guidance and to find a local installer. The standalone devices are more straightforward to set up, and include SmartStart, making adding them to your Z-Wave network as simple as scanning a QR code.
To use Z-Wave with Home Assistant, you’ll need a Z-Wave adapter and the Z-Wave integration. This will help everything run locally, keeping your data private and your smart home responsive. Of course, if you want to turn the heat up before you get home, or check on things while you’re away, Home Assistant Cloud gives you secure remote access, and by subscribing you’ll help fund the Open Home Foundation’s work, including the Works with Home Assistant program!
We hope this is just the beginning of Heatit’s involvement with the program, and we’re excited to see where things go, both with these devices and whatever comes next. In the meantime, there’s plenty here to get started with. Time to turn up the heat.
If I have a device that is not listed under Works with Home Assistant, does this mean it’s not supported?
No! It just means that it hasn’t gone through a testing schedule with our team, or doesn’t fit the requirements of the program. It might function perfectly well but be added to the testing schedule in the future, or it might work under a different connectivity type that we don’t currently test under the program.
OK, so what’s the point of the Works with program?
It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that the devices must have full functionality within Home Assistant, operate locally without the need for cloud, and will continue to do so long-term.
How were these devices tested?
All devices in this list were tested using a standard Home Assistant Green with the Home Assistant Connect ZWA-2 as the Z-Wave adapter and with our Z-Wave integration. If you have another hub or setup, that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.
Will you be adding more Heatit devices to the program?
Why not! We’re thrilled to foster a close relationship with the team at Heatit to work together on any upcoming releases or add in further products that are not yet listed here. They have also been working on integrating their WiFi products further in Home Assistant, so we’re excited to see their progress.
Hi,
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 24.10 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See changelog-24.10.6 for the full changelog.
OpenWrt components (Trail of Bits audit, February 2026):
LuCI:
OpenSSL:
With the release of OpenWrt 25.12 stable series, the OpenWrt 24.10 stable series will go end of life in 6 months. We will not provide security updates for OpenWrt 24.10 after September 2026. We encourage everyone to upgrade to OpenWrt 25.12 before September 2026.
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA. You have to upgrade without saving the configuration.
''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki. This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible. After upgrading, the config file /etc/config/system should not be restored from a backup, as this will overwrite the new compat_version value.
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.6
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.6#known_issues
For a detailed list of all changes since 24.10.5, refer to
https://openwrt.org/releases/24.10/changelog-24.10.6
To download the 24.10.6 images, navigate to:
https://downloads.openwrt.org/releases/24.10.6/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=24.10.6
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
Have fun!
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact
Hi,
The OpenWrt community is proud to announce the first service release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See the full changelog for details.
OpenWrt components (Trail of Bits audit, February 2026):
LuCI:
Additional hardening from the same Trail of Bits audit (no CVE assigned):
--force-reinstall option to reinstall already-installed packages without requiring a version changeUpgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.
Sysupgrade from 23.05 or earlier to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed. fc0c518
Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4, and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe
TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).
eth1 to wan — check and update your network configuration after upgrading.cake_mq): throughput may be unexpectedly low on some configurations after the scheduler fixes in this release. #22344Full release notes and upgrade instructions are available at
https://openwrt.org/releases/25.12/notes-25.12.1
In particular, make sure to read the known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.1#known_issues
For a detailed list of all changes, refer to
https://openwrt.org/releases/25.12/changelog-25.12.1
To download the 25.12.1 images, navigate to:
https://downloads.openwrt.org/releases/25.12.1/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.1
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
Have fun!
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact
Home Assistant 2026.3! 🎉
After last month’s massive release, this one is a nice and relaxed one. We took a step back from the big headline features and fully focused on something equally important: getting the amazing contributions from our community reviewed, polished, and merged. 💚
And did our community deliver! This release is packed with tons of new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more], lots of noteworthy improvements to the ones you already use, boatloads of bug fixes, and a really nice list of integrations that climbed up the integration quality scale. 📈
It’s releases like these that really show the strength of our open-source community. Every single contribution matters, and this month that shows more than ever. Thank you all! 🙏
My personal favorite this month? The automation editor change: Continue on error has finally landed in the UI. I actually wrote this feature years ago, but it was only available through YAML. Seeing it now land in the visual editor (making it accessible to everyone) is just awesome. It’s one of those small things that make a big difference in everyday use. 🤩
Oh, and before I forget: have you seen our brand new merch store? The Open Home Foundation store is live! I have to be honest: the quality is really great. The hoodie is so darn comfy it’s ridiculous. I’ve been wearing mine non-stop. Go check it out! 🏃
Also, mark your calendars: State of the Open Home 2026 is happening on April 8 in Utrecht, the Netherlands! Join us live in the audience for a celebration of everything we’ve built together, a look at what’s ahead, and your chance to help shape the future of the Open Home. Tickets are limited, so grab yours while you can! 🎟️
Enjoy the release!
../Frenck
A huge thank you to all the contributors who made this release possible! And a special shout-out to @TimoPtr, @arturpragacz, and @MindFreeze who helped write the release notes this release. Also, @CoMPaTech, @balloob, @OnFreund, and @silamon for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. ❤️
Got a robot vacuum? You can now tell it exactly which areas to clean! This release introduces the clean area action, which lets you send your vacuum to clean one or more specific areas on demand, right from Home Assistant. In this release, it’s supported by Matter, Ecovacs, and Roborock.
The best part? The action uses your existing Home Assistant areas, not some obscure vendor-specific identifiers. You simply map the segments your vacuum knows about to the areas you’ve already set up in Home Assistant, and that’s all there is to it.
When your vacuum supports area cleaning, you can set up the mapping through the vacuum’s entity settings. Open the vacuum entity, select the settings icon, and look for the Map vacuum segments to areas section. From there, you can match the segments your vacuum has detected to your Home Assistant areas.
If your vacuum’s internal segment layout ever changes (for example, after remapping in the manufacturer’s app or the vacuum rediscovering its environment), Home Assistant will notice. A repair issue will alert you that the segments have changed, so you can update your mapping and make sure everything stays in sync.
Because the mapping uses native Home Assistant areas, this feature lays the groundwork for future voice assistant support. Imagine simply saying “clean the kitchen” and having your vacuum head to the right area. That’s not available just yet, but the foundation is now in place to make it happen.
The Energy dashboard received a nice batch of improvements this release.
The Now view gained badges that show real-time power consumption, gas flow rate, and water flow rate at a glance. Water also gets its own Sankey chart in the Now view, giving you a visual breakdown of water usage across your home, just like the existing power Sankey chart.
To reduce ambiguity, the second tab on the Energy dashboard has been renamed from Energy to Electricity, since the dashboard covers electricity, gas, and water. On the configuration side, the energy settings page is now split into three tabs: Electricity, Gas, and Water, making it easier to find and manage your energy sources.
Finally, energy bar chart tooltips now include the day of the week, helping you quickly spot usage patterns.
Thanks, @MindFreeze, @NoRi2909, and @gpoitch! 🎉
The automation editor now has a Continue on error option for actions, directly accessible from the visual editor. Previously, this setting was only available through YAML.
You can find it in the three-dots menu of any action. When enabled, a visual indicator appears on the action row, so you can quickly see which actions will continue running even if they encounter an error.
This is especially handy for automations where a single failing action shouldn’t stop the rest from running. For example, if one of several notification actions fails, the remaining ones will still be sent.
Thanks, @wendevlin! 🎉
Your phone just became a voice satellite! The Home Assistant Companion app for Android now supports on-device wake word detection, allowing you to open Assist from anywhere; even when your phone is locked.
Inspired from the great work from @brownard in Ava.
This feature uses microWakeWord, the same lightweight wake word engine that powers the Home Assistant Voice Preview Edition. All processing happens locally on your device, no audio is sent to the cloud, and no server-side processing is needed. Your voice stays on your phone.
You can choose between three wake words:
To enable wake word detection, open your Android device’s Settings > Companion App > Assist for Android, and enable the Enable wake word detection toggle. Once enabled, simply say your chosen wake word and the Assist pipeline will open, ready to take your command.
Watch the video to see wake word detection in action on an Android device.
It already integrates with your voice equipment at home, and if another satellite is nearby, only the fastest one will respond. This also applies to multiple Android devices.
Because wake word detection requires continuous microphone access and CPU usage, this feature does have a noticeable impact on battery life. To help manage this, you can use automations to start and stop wake word detection based on your context, for example, only enabling it when you’re connected to your home Wi-Fi or within a specific zone. This way, you get hands-free voice control when it matters most, without draining your battery all day.
Note
Battery usage could be drastically reduced if Google opened their API for hardware hotword detection. Unfortunately, this is hidden behind a system API that only phone manufacturers have access to. Maybe one day they will open it up to improve the experience.
Thanks, @TimoPtr! 🎉
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 🥰
We welcome the following new integrations in this release:
Ghost, added by @JohnONolan
Monitor your Ghost publication metrics, including member counts, revenue, post statistics, and email newsletter performance, right from your Home Assistant dashboard.
Hegel Amplifier, added by @boazca - launching at 🥈 silver quality
Control your Hegel Music Systems amplifiers locally over your network. Manage power, volume, input selection, and mute with real-time push updates for instant feedback.
Homevolt, added by @Danielhiversen - launching at 🥈 silver quality
Read local data from your Homevolt battery over your network, no cloud required. Monitor power, energy, voltage, temperature, and battery status.
Hypontech Cloud, added by @jcisio
Monitor your Hypontech solar inverter system through the Hypontech Cloud platform. Track power production, energy yields, and system status.
IDrive e2, added by @patrickvorgers
Back up your Home Assistant to an IDrive e2 bucket. IDrive e2 offers affordable S3-compatible cloud storage with flexible access controls for keeping your backups safe.
Indevolt, added by @Xirt
Communicate directly with your Indevolt energy storage devices over the local network. Monitor energy production, consumption, and battery status.
IntelliClima, added by @dvdinth
Integrate your Fantini Cosmi Ecocomfort 2.0 ventilation devices. Control fan modes and speeds of your mechanical ventilation with heat recovery system.
Liebherr, added by @mettolen - launching at 🥈 silver quality
Control and monitor your Liebherr SmartDevice refrigerators and freezers via the cloud. Monitor temperatures, adjust cooling settings, and automate food safety alerts.
MTA New York City Transit, added by @OnFreund - launching at 🥈 silver quality
Get real-time arrival predictions for all NYC subway and bus lines using data from the Metropolitan Transportation Authority (MTA).
MyNeomitis, added by @l-pr
Connect your Axenco MyNeomitis heating and energy management devices, such as electric radiators, towel rails, and underfloor heating, to Home Assistant.
OneDrive for Business, added by @zweckj - launching at 🏆 platinum quality
Use OneDrive for Business as a backup location for your Home Assistant backups. Great for users with a Microsoft 365 business subscription.
Powerfox Local, added by @klaasnicolaas - launching at 🏆 platinum quality
Gather data from your Powerfox Poweropti device directly over your local network, offering faster updates with no cloud dependency.
Redgtech, added by @Jonhsady
Connect your Redgtech smart switches to Home Assistant. Control and monitor your cloud-connected switches and relays from this Brazilian smart home brand.
System Nexa 2, added by @konsulten - launching at 🥈 silver quality
Integrate your System Nexa 2 smart home devices locally. Control lights, switches, and smart plugs with support for dimmers and outdoor plugs.
Teltonika, added by @karlbeecken - launching at 🥈 silver quality
Monitor your Teltonika Networks routers running RutOS. Track cellular signal quality, modem temperature, and network connectivity.
Trane Local, added by @bdraco
Locally control Trane and American Standard thermostats over your network using a direct mTLS connection. No cloud required.
Zinvolt, added by @joostlek
Monitor your Zinvolt batteries in Home Assistant, including state of charge and other battery metrics.
This release also has new virtual integrations. Virtual integrations are stubs that are handled by other (existing) integrations to help with findability. These ones are new:
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:
gpt-image-1.5 image generation model for AI Tasks, offering cheaper and faster image generation. Thanks, @Shulyaka!ptz_goto_preset action for triggering presets and a PTZ patrol select entity with live state updates. Thanks, @RaHehl!aionanoleaf2, fixing authorization errors that prevented newer Nanoleaf Essentials devices from connecting. Thanks, @loebi-ch!radarr.get_movies and radarr.get_queue, returning detailed information about movies in your library and the current download queue. Thanks, @Liquidmasl!get_shopping_list_items action that returns structured shopping list data, useful for automations that need more detail than the to-do entity provides. Thanks, @andrew-codechimp!prune_images action to clean up unused Docker images. Thanks, @erwindouna!start_session action, letting you start a sauna session with custom duration, target temperature, and fan duration in a single call. Thanks, @mettolen!One thing we are incredibly proud of in Home Assistant is our integration quality scale. This scale helps us and our contributors to ensure integrations are of high quality, maintainable, and provide the best possible user experience.
This release, we celebrate several integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have improved their quality scale:
9 integrations reached platinum 🏆
1 integration reached gold 🥇
6 integrations reached silver 🥈
7 integrations reached bronze 🥉
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! 👏
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:
There are many more improvements in this release; here are some of the other noteworthy changes:
This release ships running on Python 3.14! In case you are wondering what that means: Python is the programming language Home Assistant is built with.
So, why does it matter to you? Python 3.14 brings performance improvements to the foundation that Home Assistant is built on. The new version includes a faster interpreter, improved startup times, and better memory usage, all of which contribute to a snappier Home Assistant experience. 🚀
Don’t worry! We handle the upgrade to Python 3.14 automatically for you on all officially supported installation methods. Just upgrade Home Assistant as you normally would, and you are good to go! 😎
We will also release patch releases for Home Assistant 2026.3 in March. These patch releases only contain bug fixes. Our goal is to release a patch release once a week, aiming for Friday.
async_join_players (@mill1000 - #165020)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.
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:
The water heater operation mode state on has been changed to performance for the BSB-Lan water heater. If you use this state in your automations or scripts, you will need to update them to use the new state value.
Home Assistant container images are now compressed with zstd instead of gzip. This change is supported on Docker 23.0.0 and later, and containerd 1.5.0 and later, so it is not expected to break installations that meet these minimum versions. If your environment uses an older Docker or containerd version, make sure your container runtime supports zstd before updating.
Passing the color_temp parameter (in mireds) to the lifx.effect_pulse action is no longer allowed. Use the color_temp_kelvin parameter instead.
Using color_temp (in mireds) to set a light’s color temperature is no longer supported. Use color_temp_kelvin instead.
Additionally, the color_temp, kelvin, min_mireds, and max_mireds light entity state attributes have been removed. Use color_temp_kelvin, min_color_temp_kelvin, and max_color_temp_kelvin instead.
Binary sensors and switches now have an initial state of unknown while the alarm panel is still reporting all states during startup. Previously, the default state was off, which was incorrect, as no data had been received from the panel yet.
The chance that you are impacted is low, as most states are reported before Home Assistant fully finishes setup; but this might occur on larger installations and slower connections.
Media player entities for Snapcast groups have been removed. Additionally, the Snapcast-specific grouping actions have been removed. If you use these entities or actions in your automations or scripts, you will need to update them.
The ignition and autostart state attributes of the engine switch have been removed. Two new binary sensors have been introduced to replace them. If you reference these attributes in your automations or scripts, update them to use the new binary sensor entities instead.
Mobile device tracking has been removed from the Tado integration. Mobile devices and their associated device tracker entities are no longer available. This change resolves re-authentication issues and reduces unnecessary load on the Tado API.
The behavior of template fans has changed:
unavailable if the state template encounters a syntax error. Previously, a template error would show the fan’s state as off.percentage attribute will be None if the percentage template encounters a syntax error. Previously, it would be 0.unknown state. A state template that returns None will render the entity as unknown instead of off.Percentage speeds reported by Z-Wave fans have been corrected to align with other integrations. As a result, values may differ slightly. For example, a value previously reported as 67% may now appear as 66%. If you have automations that trigger on exact percentage values, you may need to adjust them.
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:
Of course, there is a lot more in this release. You can find a list of all changes made here: Full changelog for Home Assistant Core 2026.3.
Hi,
The OpenWrt community is proud to announce the first stable release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
OpenWrt 25.12.0 incorporates over 4700 commits since branching the previous OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0 for the full changelog.
OpenWrt 25.12 is named Dave's Guitar to honor Dave Täht, who sadly passed away on April 1, 2025.
Dave played a key role in reducing bufferbloat and improving network latency in OpenWrt and across the wider internet. His work made networks faster, more responsive, and more reliable for millions of users.
This release is dedicated to his memory and lasting impact on the networking community.
The hardware requirements did not change significantly. Most devices supported by OpenWrt 24.10 are also supported in OpenWrt 25.12.
OpenWrt has transitioned from the traditional opkg package manager to apk (Alpine Package Keeper).
This change brings several advantages:
apk supports most features of opkg. Only very few package names changed. The command line arguments of apk are different from the command line arguments of opkg.
For users migrating existing systems, an official opkg to apk cheatsheet is available to ease the transition and map common workflows.
The attended sysupgrade LuCI application is now installed by default.
owut is included by default in images for devices with larger flash storage.
ASU allows devices to:
This dramatically simplifies upgrades: with just a few clicks in LuCI and a short wait, a custom firmware image is built and installed without manual intervention.
Shell command history is now preserved across sessions by storing it in a RAM-backed filesystem.
Benefits:
For users who prefer persistent history storage, this behavior can be changed by editing: ''/etc/profile.d/busybox-history-file.sh''
⚠️ Note: Storing history on flash will increase write cycles and may impact flash endurance over time.
The OpenWrt video feed with Qt5 and UI applications is integrated by default.
The Wi-Fi scripts were rewritten in ucode.
This is part of the rewrite of the management scripts from shell scripts to ucode.
uCode is used for system scripts because it is faster and safer than shell scripts, and integrates directly with ubus and UCI.
Wi-Fi and network management scripts rewritten in uCode run faster, have fewer errors, and are easier to maintain.
OpenWrt 25.12 supports over 2200 devices. Support for over 180 new devices was added in addition to the devices already supported in OpenWrt 24.10.
Most devices already supported by OpenWrt 24.10 are still supported.
Core components have the following versions in 25.12.0:
In addition to the listed applications, many others were also updated.
With the release of OpenWrt 25.12 stable series, the OpenWrt 24.10 stable series will go end of life in 6 months. We will not provide security updates for OpenWrt 24.10 after September 2026. We encourage everyone to upgrade to OpenWrt 25.12 before September 2026.
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
Sysupgrade from 23.05 to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed.
Bananapi BPI-R4: Interfaces ''eth1'' was renamed to ''sfp-lan'' or ''lan4'', and interface ''eth2'' was renamed to ''sfp-wan'' to match the labels. You have to upgrade without saving the configuration.
If you wish to start from scratch (always the safest, but also the most work), simply download the pre-built image from the downloads site or from the Firmware Selector to your device. Make sure to create and save a backup, then install the image using sysupgrade -n /tmp/firmware.bin or the LuCI Backup/Flash Firmware, being sure to set "Keep settings and retain the current configuration" to its off position. Restore or reconstruct your configuration using the contents of the backup as a template.
Attended Sysupgrade (ASU) allows you to build a custom image that retains all of your installed packages and their configuration transparently. You need to use one of the three ASU clients that interface with the ASU server to produce this custom image:
Both the LuCI ASU app and owut are optional packages in 24.10, so if you have not installed them, they won't be there by default. Use either the LuCI Package Manager to install them, or you can do it from the command line with opkg:
$ opkg update
$ opkg install luci-app-attendedsysupgrade
$ opkg install owut
Note that you can install one or the other, or both together, they are completely independent packages.
The Firmware Selector does an excellent job of searching through the thousands of available device configurations and getting you to the right place. But, some devices have several variants and possibly different image formats, so if you're unsure about which one you need or which device you're dealing with or anything else, go to the |Firmware Selector support thread and ask away.
The LuCI web interface is fairly self-explanatory. If anything is unclear, please refer to the LuCI Attended Sysupgrade support thread for guidance.
If you choose to use owut, the fact that it's a command line program means you'll need a little more explanation regarding best practices. In any situation, it's always safe to do a check to see what's going on.
$ owut check --verbose --version-to 25.12
... a lot of output ...
This check should show you all the details of what this upgrade entails with regards to the packages available, and will point out any issues with package versions and so on.
Assuming the results of the check look good, you can simply do an upgrade next.
$ owut upgrade --verbose --version-to 25.12
... even more output ...
If you are unsure of anything you see in the check, during the upgrade, or simply have questions, jump on over to the owut support thread on the forum and ask.
eth1 to wan.Full release notes and upgrade instructions are available at
https://openwrt.org/releases/25.12/notes-25.12.0
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.0#known_issues
For a detailed list of all changes since branching of 24.10, refer to
https://openwrt.org/releases/25.12/changelog-25.12.0
To download the 25.12.0 images, navigate to:
https://downloads.openwrt.org/releases/25.12.0/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.0
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
Have fun!
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact
After an amazing 2025 that saw 12 new Works with Home Assistant partners join the program, it’s now time to say “Hei” to the first partner joining us this year: Heiman.
Founded back in 2005, Heiman specialize in smart home security devices, and are bringing an impressive selection of safety-focused sensors and alarms to the program: including the first Matter carbon monoxide alarms to be certified, along with smoke alarms designed for international markets.
If you’re new to the Works with Home Assistant program, it’s designed to help you identify devices that work brilliantly with Home Assistant, and support the Open Home Foundation’s principles of privacy, choice, and sustainability.
These values all pivot around local control, something that’s essential when it comes to home safety. Your smoke and CO alarms need to work when you need them most, regardless of your internet connection or cloud service status (though if you want to check in on your devices while away from home, Home Assistant Cloud provides secure remote access, and your subscription helps fund this very program, among other things!).
Our in-house team has thoroughly tested Heiman’s devices to ensure they meet this key requirement, and we’re happy to report they did! But Heiman has gone further still by using the Matter open connectivity standard…
Matter was launched to be a unifying connectivity type with interoperability at its heart. Instead of being locked into one company’s ecosystem, Matter devices work across Home Assistant, as well as other platforms like Google Home.
Heiman’s Matter devices work over Thread, which adds another layer of benefits. Thread is a low-power wireless mesh network protocol that creates resilient connectivity throughout your home, perfect for battery-powered sensors that need reliable communication while staying energy efficient. This is ideal for battery-powered sensors like Heiman’s that need to be energy efficient while maintaining reliable communication.
So why does all this matter for safety devices specifically? Well firstly, it’s important to know these smart devices will still work as “dumb” ones, so there’s always a failsafe if you decide to rebuild your Thread network, or start making tweaks. If your sensors integrate locally, it means you can automate basic checks, such as reminders to test an alarm once a month, or notifications of hardware faults. If you want to go even further, your smoke alarm could trigger emergency lighting, your CO detector could shut off your gas fireplace, or your leak sensor could close water valves, all without sending your private data through a third-party server. And this is just the sort of complete, interoperable ecosystem Heiman aims to provide.
"Our core goal has always been to enable every family to enjoy a safe and intelligent living experience. Home Assistant, as a world-leading open source smart home platform, has an open and inclusive ecological philosophy and strong compatibility with multi-brand and multi-protocol devices, which are highly consistent with the direction of our product research and development. We deeply understand that only by integrating into an open ecosystem can we break down device barriers and provide users with a truly seamless whole-house smart solution."
- Leo Xie, Software Engineer Manager at HeimanHeiman is showing they’re true to these ambitions. Beyond getting certified, they’re planning to take an active role in the Home Assistant community by participating in discussions, listening to real-world feedback, and continuously optimizing their products based on what users actually need. They’re also sharing their technical expertise in smart home security, collaborating with developers to explore innovative safety scenarios that benefit everyone.
Heiman’s commitment to openness and community is also reflected in the devices we’ve certified, which also meet strict safety regulations across the US, Europe, Asia and beyond. Before Heiman joined, we had one Zigbee smoke alarm in the program. Now there are Matter options for multiple regions, plus the first certified carbon monoxide alarms: more choice, more coverage.
What devices have been certified?
Also worth noting: Heiman’s global presence allows them to deliver quality devices at prices that won’t break the bank. Safety sensors and alarms shouldn’t be a luxury, and Heiman’s approach means they don’t have to be.
Accessible pricing is just one way Heiman expands choice for users. We’ve found they also deliver on the other core principles behind the Works with Home Assistant program: local control protects privacy, and open standards ensure sustainability. And that’s the whole point of our certification process: to make it easier for you to spot manufacturers who genuinely commit to these values, taking the guesswork out of building your open home. For full details of all Works with Home Assistant partners, check out our certified device list.
Welcome to the program, Heiman, we’re excited to see what the community builds with these devices!
If I have a device that is not listed under Works with Home Assistant, does this mean it’s not supported?
No! It just means that it hasn’t gone through a testing schedule with our team, or doesn’t fit the requirements of the program. It might function perfectly well but be added to the testing schedule in the future.
OK, so what’s the point of the Works with program?
It highlights the devices we know work well with Home Assistant and the brands that make a long-term commitment to keeping support for these devices going. The certification agreement specifies that brands must continue to support the devices in the program.
How were these devices tested?
All devices in this list were tested using a standard Home Assistant Green Hub with the Home Assistant Connect ZBT-2 as the Thread Border Router and with our certified Matter integration.
Will you be adding more Heiman devices to the program?
Why not! We’re thrilled to foster a close relationship with the team at Heiman to work together on any upcoming releases or add in further products that are not yet listed here. We are also chatting with them about some exciting future plans.
