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:
Log instate_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)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.
Yes, the day has finally arrived: the Open Home Foundation merch store is up and running! ๐ฅณ While some of you have tracked it down already (and are wearing the T-shirts to prove it!), we wanted to share it officially with the whole community so no one misses the chance to get involved.
In case you didnโt know, there are already several ways to support our fight for the principles of privacy, choice, and sustainability for smart homes: you can subscribe to Home Assistant Cloud, buy official hardware from our commercial partners, or contribute to an open source project.
The merch store adds another choice to the mix thatโs fun and easy to access. Whether youโve been with us from the beginning, or have only recently discovered our mission and like what we stand for, the merch store is open to everyone!
We have offered merch before through on-demand services, but those platforms didnโt give us the control we wanted. Now we have our own store, we can select every item ourselves, check the quality (weโve particularly enjoyed getting cozy in the hoodies this winter), and work with ethical manufacturers who share our commitment to sustainability.
And hereโs the important part: after covering costs like production and fulfillment, your purchase contributes directly to our mission. You can see the breakdown of where your money goes on every product page.
Weโre starting with the essentials: hoodies, tees, polos, and accessories in a range of classic styles, colors, and designs โ with exciting plans to expand both our products and categories over time. But for now there should be something for everyone: from understated logos to bold patterns that declare your advocacy loud and clear. One of our favorites is the โOpen Homesโ tee, where our in-house designer has captured our communityโs strength โ one foundation, many homes.
Weโve put a lot of thought and care into creating this first collection, and we canโt wait for you to check it out! You can browse our European or North American store depending on where youโre based: both have the full selection of swag, with local shipping for speed and convenience (and a lower carbon impact).
And rememberโฆ this is just the beginning. We already have lots of ideas for whatโs next. But we want to hear from you too: what designs would you wear? What products or materials are you missing? Let us know and help us build a store the community really loves โ in the open, of course.
The OpenWrt community is proud to announce the fifth release candidate of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
OpenWrt 25.12.0-rc5 incorporates over 4600 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-rc5 for the full changelog.
The hardware requirements did not change significantly, most devices supported by OpenWrt 24.10 should also work with 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.
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 wifi scripts were rewritten in ucode.
OpenWrt 25.12 supports over 2240 devices. Support for over 220 new devices was added in addition to the device support by OpenWrt 24.10.
Core components have the following versions in 25.12.0-rc5:
In addition to the listed applications, many others were also updated.
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 the 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 should be fairly self explanatory. Since you have fairly limited options there that should be pretty obvious, but if anything is unclear or you're unsure about something, go to the LuCI Attended Sysupgrade support thread and ask.
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-rc5
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.0-rc5#known_issues
For a detailed list of all changes since 25.12.0-rc4, refer to
https://openwrt.org/releases/25.12/changelog-25.12.0-rc5
To download the 25.12.0-rc5 images, navigate to:
https://downloads.openwrt.org/releases/25.12.0-rc5/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.0-rc5
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.2! ๐
February is the month of love, and this release is here to share it!
The new Home Dashboard is now the official default for all new installations. If youโve been using Home Assistant for a while and never customized your default view, youโll get a suggestion to switch; give it a try!
I also need your help! The Open Home Foundation device database is being built as a community-powered resource to help everyone make informed decisions about smart home devices. Head to Home Assistant Labs to opt in and contribute your anonymized device data. ๐
Add-ons are now called Apps! After a lot of community discussion, it was time to use terminology that everyone understands. Your TV has apps, your phone has apps, and now Home Assistant has apps too.
My personal favorite this release? The completely redesigned Quick search! If youโre like me and navigate Home Assistant using your keyboard, youโre going to love this one. Press โ + K (or Ctrl + K on Windows/Linux) and you have instant access to everything. ๐คฉ
Enjoy the release!
../Frenck
A huge thank you to all the contributors who made this release possible! And a special shout-out to @laupalombi and @mkerstner who helped write the release notes this release. Also, @wollew, @Diegorro98, and @MindFreeze for putting effort into tweaking its contents. Thanks to them, these release notes are in great shape. โค๏ธ
The Home Dashboard is now Overview as it becomes the official default standard, replacing the old โOverviewโ for all new instances. If youโre a long-time user who never customized your default view, weโll suggest the switch to you; otherwise, you can find it in Settings > Dashboards to try it out whenever youโre ready.
Liked the old Overview as a way to build your custom dashboards? You can still do it. Go to Settings > Dashboards, select Create, and pick the Overview (legacy) template.
Check out the new card in the For You section! It instantly displays any new devices your Home Assistant has discovered, allowing you to add them on the spot or jump straight to device management without digging through menus.
In the last release, we added a dedicated Devices area within the Home Dashboard to catch everything currently unassigned. Now this section provides quick prompts to help you categorize your devices into the right rooms, keeping your setup organized with minimal effort.
Need to swap the area temperature sensor? Area pages now feature a shortcut in the Edit button. This lets you jump straight to the areaโs configuration to update primary sensors like humidity or temperature in seconds.
Weโve also tidied up the interface by removing awkward empty spaces and fixing issues with some back arrows. Navigating through your sub-menus should now feel as smooth and predictable as youโd expect.
Modern look in the default theme: Weโve retired the old blue top bar in favor of a clean, consistent theme that matches our Settings page. This distraction-free design lets your cards and data take center stage.
Personalized themes per user: Themes have moved! You can now find and toggle your favorite looks directly within your User profile, making it easier to set up a theme that works for you in any device you are logged in.
Finding reliable information about smart home devices before you buy them can be challenging. Thatโs why weโre building the Open Home Foundation device database: a community-powered resource that helps you make informed decisions based on real-world data.
Weโve been working with early contributors to lay the groundwork, and the results are already impressive: over 10,000 unique devices across more than 260 integrations have been submitted by Home Assistant users who opted in to share their anonymized data.
Since weโre still in the early stages, the device database lives in Home Assistant Labs, where you can opt in to share anonymized information about the devices in your home.
We have also added a new section called Device analytics to Home Assistant Analytics, which shows up when you enable it in Home Assistant Labs. If you opt in, you are, of course, able to opt out at any time.
Privacy is our foundation. We collect zero personal data, period. Only aggregated, anonymized device information is shared if someone chooses to opt in, providing valuable insights while keeping your privacy intact. You can preview what is being sent using the Preview device analytics option available in the top-right corner on the Analytics page. Read our Data Use Statement for complete details.
Weโve launched an initial public dashboard where you can explore aggregated statistics as it grows. This is just our first step. We want to build what comes next together with you.
Head to Settings > System > Labs to enable device analytics and start contributing your real-world anonymized device data to help others make better choices.
Read our blog post for more details and join the conversation in our Discord project channel; weโd love to hear your ideas, feedback, and questions as we shape this resource together.
Starting with this release, add-ons are now called apps! ๐
You might be wondering: why change the name? The answer comes down to making Home Assistant more approachable for everyone, especially newcomers.
When you first open Home Assistant, you see two sections that sound very similar: โAdd-onsโ and โIntegrations.โ Both names imply something you add to extend Home Assistant, but they serve fundamentally different purposes. For those of us whoโve been in the ecosystem for a while, this distinction is second nature. But we keep seeing new users getting confused, attempting to install add-ons when they need integrations, or vice versa.
This is where the rename helps: use terminology that people already understand. Most people know what an โappโ is. You open your phoneโs app store, you pick an app, you install it. Your TV has an app store. Your NAS has apps. Heck, even some fridges have apps these days. Itโs a concept everyone understands. The same mental model now applies to Home Assistant:
Apps are separate software managed by your Home Assistant Operating System, running next to Home Assistant itself. They can be things like code editors, media servers, MQTT brokers, or database tools. Some apps even pair with integrations: for example, the Mosquitto MQTT broker app provides the service, while the MQTT integration connects Home Assistant to it.
Existing documentation, community posts, and tutorials will continue to reference โadd-onsโ for some time. Search engines and AI assistants will also need time to catch up. Weโve put redirects in place to ensure that searching for โadd-onsโ will still get you where you need to go.
Thank you to everyone who participated in the community discussion and architecture proposal. Whether you supported the idea, pushed back, or landed somewhere in between, your feedback was invaluable.
Besides the rename, we did a major refactoring under the hood of the Apps panel (formerly known as the Add-ons panel) in this release. Previously, this panel was served by a separate process (the Supervisor), but it has now been fully integrated into the Home Assistant frontend.
You shouldnโt notice much of a difference visually, but the panel is now much faster and snappier to use. More importantly, this change makes future development on Apps significantly easier, paving the way for more improvements down the road.
In Home Assistant 2025.12, we introduced purpose-specific triggers and conditions. Instead of thinking in technical state changes, you can simply pick things like โWhen a light turns onโ or โIf the climate is heatingโ when building your automations. In Home Assistant 2026.1, we added more triggers and laid the groundwork for conditions.
This feature is still being refined in Home Assistant Labs, but we continue to expand it with every release. This release brings a mix of new triggers and, for the first time, a whole set of purpose-specific conditions!
The following new triggers have been added in this release:
Purpose-specific conditions are expanding! In the previous release, we introduced the first purpose-specific condition for lights. This release adds a whole set of new conditions across many more entity types.
Just like triggers, conditions now allow you to express your intent in a more natural way. Instead of checking if the state of an entity equals a specific value, you can now simply ask โIf the climate is heatingโ or โIf the lock is lockedโ.
The following purpose-specific conditions are now available:
Head over to Settings > System > Labs to enable purpose-specific triggers and conditions and give them a try!
Meet the distribution card, a brand new dashboard card that visualizes how values are distributed across multiple entities. It displays your data as a proportional horizontal bar chart with an interactive legend, perfect for seeing at a glance where your power, storage, or any other measurable quantity is going.
The card is fully interactive: select legend items to hide or show entities (the percentages recalculate dynamically), and select bar segments to open the more-info dialog for that entity. When you have many entities, the legend shows the first items with a More button to expand the rest.
The distribution card is smart about what you can combine. It validates that all entities share the same domain and device class, so you wonโt accidentally mix power sensors with battery sensors. It even handles related units gracefully: mixing watts and kilowatts works just fine.
Some ideas for how you might use it:
Thanks to @jlpouffier for building this card! ๐
We continue to make it easier to access and find things in Home Assistant. The quick bar has been completely redesigned and is now simply called Quick search. Think of it as the command center for your entire Home Assistant: navigate anywhere, run commands, find entities, devices, or areas, all from a single, unified search.
Open Quick search from anywhere by pressing โ + K on macOS or Ctrl + K on Windows and Linux. The new design features category filters at the top: Navigate, Commands, Entities, Devices, and Areas. Select a filter to instantly narrow your results, or just start typing to search across everything.
Full keyboard navigation makes Quick search a power userโs friend. Use the arrow keys to move through results, Enter to select, and Esc to close. On mobile, you can assign Quick search to a gesture for one-tap access.
If youโve been using the single-key shortcuts from the old quick bar, they still work! The difference is that they now open Quick search with the corresponding filter already selected:
This means your muscle memory is preserved while you get access to all the new capabilities.
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:
Cloudflare R2, added by @corrreia
Back up your Home Assistant to Cloudflare R2. R2 offers generous free tier storage with no egress fees, making it an affordable option for keeping your backups safe in the cloud.
Green Planet Energy, added by @petschni
Get real-time dynamic electricity pricing data from German renewable energy provider Green Planet Energy. Monitor hourly prices and optimize your energy consumption by shifting it to cheaper hours.
HDFury, added by @glenndehaan
Control and monitor your HDFury HDMI video processing devices, like the VRROOM and Diva. Manage HDMI port selection, operation modes, audio muting, and monitor input/output signal status.
NRGkick, added by @andijakl
Monitor your NRGkick Gen2 mobile EV charger locally. Track charging status, energy consumption, power flow across all phases, and device temperatures without requiring a cloud connection.
Prana, added by @prana-dev-official
Integrate your Prana heat recovery ventilation systems. Prana HRV units provide balanced mechanical ventilation with energy-efficient heat exchange, and you can now control and monitor them directly from Home Assistant.
uHoo, added by @getuhoo and @joshsmonta
Integrate your uHoo indoor air quality monitors to track temperature, humidity, CO2, PM2.5, and other air quality metrics. Also includes proprietary health indices for virus and mold risk.
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:
3 integrations reached platinum ๐
4 integrations reached silver ๐ฅ
1 integration 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:
The heading card now supports button badges, giving you a new way to add quick actions right alongside your section headings. Display an icon, text, or both, pick a custom color, and configure tap, hold, or double-tap actions to trigger anything you want.
You can also set visibility conditions to show or hide buttons based on entity states. Combined with the existing entity badges, this makes the heading card a versatile anchor for your dashboard sections, whether you want to display status information, provide quick controls, or both.
Thanks to @piitaya for this addition! ๐
The area card now lets you select individual entities as control buttons, not just entire types of entities like all lights or all switches in the area. Previously, adding a light control meant showing all lights in the area. Now you can pick exactly which entities appear.
Great job, @MindFreeze! ๐
We will also release patch releases for Home Assistant 2026.2 in February. These patch releases only contain bug fixes. Our goal is to release a patch release once a week, aiming for Friday.
off preset in Tuya climate (@epenet - #161040)stopped state to denonavr media player (@ol-iver - #162283)google_cloud (@NoRi2909 - #162534)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 behavior of sensor groups has changed:
ignore_non_numeric is set to False (the default), the group state is calculated according to the configured type only if all group members are in the state machine and have a numeric state. If not, the group state will be unknown.Self-hosted Sentry users only: This upgrade requires Sentry server version 20.6.0 or later (released June 2020) due to the SDKโs use of the /envelope API endpoint. Users running older self-hosted Sentry instances must upgrade their server before updating Home Assistant.
Home Assistant users using sentry.io are not affected.
The following sensors have been removed because they are no longer supported by the Tractive API:
activitycalories burnedsleepIf you use these entities in your automations or scripts, you must update them.
Duplicate HVACMode have been converted to presets. You may need to adjust service calls from set_hvac_mode to set_preset_mode in your automations or scripts.
(@epenet - #160918) (tuya documentation)
The advanced_sleep preset mode is now replaced by sleep. If you have been using advanced_sleep, in your automations or scripts, you must update them to use sleep instead.
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.2.
Imagine knowing how a smart device will actually perform in your home before you buy itโฆ not from a spec sheet, but from anonymized data that people running setups just like yours have opted to share. Having answers to questions like: will this sensor work without the cloud? Is that smart plug actually being reported by users as reliable? Does โlocal controlโ mean local always, or just sometimes? Will these devices work well across protocols? What this device looks like in other usersโ homes?
Thatโs the idea behind the Open Home Foundation Device Database: a community-powered resource built from anonymized data shared voluntarily by Home Assistant users around the world. The aim: to give people the information they need to benefit from privacy, choice, and sustainability in their smart homes.
Having easy access to this wealth of data changes everything. With the device database at your fingertips, youโll know upfront that there are 1000+ Home Assistant users running that smart plug fully locally, and it includes those voltage and wattage sensors you were looking for. Or if you see a sensor everyoneโs raving about requires Bluetooth when your protocol of choice is Zigbee, the database could save you the hassle of buying it in the first place.
Of course, there are some excellent device databases and compatibility lists already available. Our own Works with Home Assistant (WWHA) program puts products through their paces in home settings, which has taught us how vital real-world testing is. But to really understand how devices perform across the incredibly diverse range of setups out there (different integrations, hardware combinations, network connections, and protocols) we need data at a much larger scale. Thatโs what makes the device database different: itโs thousands of real homes opting in to contribute real anonymized data. And thatโs only possible with your help.
Creating the device database is a big job, and weโre going to need your help to do it. Before we build a shiny new website or complex search engine, the first step is to make sure the data you opt to share with us is accurate, anonymized, and meaningful, so weโre prioritizing:
Like everything we do, the Device database initiative follows a steady, iterative approach, which takes time. We want to be honest: nothing happens overnight. We donโt believe in hiding away for years behind closed doors just to launch our vision of a โperfectโ finished product (spoiler: thereโs no such thing as perfect!). Instead, in the true open source fashion, we build in the open, release early experiments, and refine them based on how our community actually uses them.
Right now, in these early stages, our focus is on planting the seeds and gathering the first shoots of real-world information, as well as your feedback. This way, the tools we build later can grow and evolve alongside your needs.
Following our iterative philosophy, we have a roadmap of small, manageable milestones designed to gather feedback at every step:
We are introducing the Open Home Foundation device database as a Labs feature in the 2026.2 release of Home Assistant. The idea is to broaden visibility and reach a wider audience (hello, that means you ๐) willing to contribute by opting in to share their device data and providing valuable feedback.
Building on the further insights and feedback we gather, weโre planning to launch the first public device database web interface in the first half of 2026. The plan is to make it easier for you to explore and interact with the information, beyond simple statistical dashboards.
While this initial version will be far from the final version (if there ever is one!). By getting it into your hands as early as possible, we can better understand where to go next, and make sure our future work is focused on the most valuable features for you.
Right from the start, weโre establishing simple flows to enable you to contribute more easily, allowing you to enrich the device database by adding real-world insights, all under the watch of our community. The result: an authentic and unbiased source of truth that helps everyone make informed decisions when it comes to privacy, choice, and sustainability in the smart home.
Because this project belongs to the community, we need your perspective early and often to help shape what comes next.
This is a marathon, not a sprint. The device database will only become a definitive resource through consistent, collective effort over the coming months and years, but bit by bit, device by device, we can make something great together! Hereโs how you can be part of it:
Together weโll build a transparent, open, and community-driven map of the real-world smart home ecosystem: one that gets better with every contribution. We hope youโll be part of it.
Hi,
The OpenWrt community is proud to announce the fourth release candidate of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
OpenWrt 25.12.0-rc4 incorporates over 4300 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-rc4 for the full changelog.
The hardware requirements did not change significantly, most devices supported by OpenWrt 24.10 should also work with 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.
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 wifi scripts were rewritten in ucode.
OpenWrt 25.12 supports over 2180 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 24.10.
Core components have the following versions in 25.12.0-rc4:
In addition to the listed applications, many others were also updated.
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 the 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 should be fairly self explanatory. Since you have fairly limited options there that should be pretty obvious, but if anything is unclear or you're unsure about something, go to the LuCI Attended Sysupgrade support thread and ask.
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-rc4
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.0-rc4#known_issues
For a detailed list of all changes since 25.12.0-rc3, refer to
https://openwrt.org/releases/25.12/changelog-25.12.0-rc4
To download the 25.12.0-rc4 images, navigate to:
https://downloads.openwrt.org/releases/25.12.0-rc4/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.0-rc4
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
