You’ve been asking all year, and the wait is over… Mark your calendars, because Community Day 2026 will be held on Saturday, November 7! 🎉

Back in April during State of the Open Home 2026, we gave you a sneak peek of ESPHome’s very first official product… And after months of hard work alongside the community, the ESPHome Starter Kit is here! 🎉

Home Assistant 2026.8! 🎉

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

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

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

Enjoy the release!

- Ashley

• Making Home Assistant more approachable
• The same Home Assistant, minus the magic number
  • Your current setup keeps working
  • Want to change the port? We’ve got you covered
  • What this means for YAML
• Less “advanced”, more approachable
  • Describing the feature, not the user
  • Just Tools, no developer required
• Home Assistant Cloud, now easier to explore
• Your entity IDs, your choice
• A cleaner way to handle your devices
• We can’t stop adding triggers and conditions
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
  • Farewell to the following
• Other noteworthy changes
  • Tell us how setup went
  • A roomier template editor
  • Taps that land where you mean them
  • A combined battery level you can trust
  • Search your media
  • Find your favorite cards faster
  • Z-Wave lock credentials, properly managed
  • And a few more
• Patch releases
  • 2026.8.1 - August 7
  • 2026.8.2 - August 14
  • 2026.8.3 - August 21
• Need help? Join the community
• Backward-incompatible changes
• All changes

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

Making Home Assistant more approachable

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

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

The same Home Assistant, minus the magic number

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

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

Your current setup keeps working

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

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

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

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

What this means for YAML

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

Less “advanced”, more approachable

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

Describing the feature, not the user

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

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

Just Tools, no developer required

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

Home Assistant Cloud, now easier to explore

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

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

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

A big thank you to @klejejs for this redesign!

Your entity IDs, your choice

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

Some earlier work looked at building entity IDs automatically from the areaAn area in Home Assistant is a logical grouping of devices and entities that represents a room or space in your home, such as the living room, kitchen, or garage. [Learn more] a device belongs to. Your feedback told us this suited some people but not everyone. So this release takes a more flexible route and puts you in charge: you can rename an entity ID yourself, and control how it is ordered, so your entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] follow whatever naming pattern makes sense to you.

Thanks to @arturpragacz and @piitaya for this work.

A cleaner way to handle your devices

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

When you update, any devices that were merged this way are separated automatically, and their entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] move to the right device for you. Most people will not notice a thing. In the rarer cases where a device was set up through more than one integration, you might see it appear twice, once per integration, and Home Assistant may raise a repair to let you know.

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

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

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

Thanks to @emontnemery for this work.

We can’t stop adding triggers and conditions

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

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

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

Thanks, @nielsrowinbik!

Integrations

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

New integrations

We welcome the following new integrations in this release:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have been added; existing ones keep getting better too. Here are some of the noteworthy improvements this release:

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

Integration quality scale achievements

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

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

• 2 integrations reached platinum 🏆

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

• 1 integration reached gold 🥇

  • Nobø Ecohub, thanks to @oyvindwe

• 5 integrations reached silver 🥈

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

• 2 integrations reached bronze 🥉

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

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

A big thank you to all the contributors involved! 👏

Now available to set up from the UI

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

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

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

Farewell to the following

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

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

Other noteworthy changes

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

Tell us how setup went

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

A roomier template editor

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

Thanks, @maartenla!

Taps that land where you mean them

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

A combined battery level you can trust

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

Search your media

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

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

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

Find your favorite cards faster

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

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

Z-Wave lock credentials, properly managed

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

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

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

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

And a few more

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

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

Patch releases

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

2026.8.1 - August 7

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

2026.8.2 - August 14

• Teslemetry: convert streamed tyre pressure and isolation resistance to their declared units (@Bre77 - #177541)
• Handle inconsistence api response in Husqvarna Automower (@Thomas55555 - #178200)
• Scope hassfest Docker manifest.json discovery to documented locations (@jabone - #178265)
• Fix/tplink omada switch port refresh (@rubempoli - #178270)
• Unload legacy notify actions in SMTP integration (@tr4nt0r - #176747)
• Fix potential race condition in SMTP integration (@tr4nt0r - #178416)
• Fix adaptive update interval Tado (@erwindouna - #178515)
• Bump midea-local to 7.0.0 (@chemelli74 - #178535)
• Bump python-bsblan to 6.1.8 (@liudger - #178561)
• Victron GX: Fix regression in SSDP rediscovery with missing host (@tomer-w - #178585)
• Bump evohome-async to v2.1.0 (@zxdavb - #178588)
• Fix Reolink time import (@starkillerOG - #178597)
• Add handle_safe_area opt-out to panel_custom and fix KNX panel (@farmio - #178598)
• Use common logger in Mikrotik (@chemelli74 - #178602)
• Fix sensors for Mikrotik (@chemelli74 - #178604)
• Bump ical to 14.1.0 (@allenporter - #178626)
• Update xknx to 3.19.0 (@farmio - #178652)
• Bump aiolyric to 2.1.2 (@timmo001 - #178670)
• Create hassio config entry during setup instead of deferring to started (@agners - #178677)
• Handle Wyoming error events (@synesthesiam - #178696)
• Bump homematicip to 2.14.1 (@lackas - #178701)
• Report a refused alarm activation in homematicip_cloud (@lackas - #179139)
• Fix missing optional gameserverip field in Steam Online dataclass (@tr4nt0r - #178751)
• Fix delayed trains being dropped from Israel Rail departures (@mikomgk - #178773)
• Bump lyngdorf to 1.4.9 (@fishloa - #178784)
• Bump aiopvapi to 3.4.1 for hunterdouglas_powerview (@kingy444 - #178792)
• Make tedee unknown during calibration and updates (@zweckj - #179048)
• Bump blebox-uniapi to v2.5.7 (@bkobus-bbx - #179050)
• Fix composed devices behind Matter bridge losing “via device” (@TheJulianJES - #179118)
• Electric Kiwi: bugfix connections empty not checked (@mikey0000 - #179119)
• Separate energy endpoint MELCloud Home (@erwindouna - #179124)
• Update frontend to 20260729.7 (@bramkragten - #179131)
• Bump incomfort-client to v0.7.1 (@jbouwh - #179134)
• Bump py-nymta to 0.4.1 (@OnFreund - #179136)
• Bump homematicip to 2.15.0 (@lackas - #179153)

2026.8.3 - August 21

• Show artwork and a play button when opening a Sonos music library album (@bharat - #177510)
• Pass config entry explicitly in Supla coordinator (@Fistacho - #178347)
• Bump holidays to 0.102 (@gjohansson-ST - #179170)
• errors could be None in Shelly Wall Display status (@bieniu - #179207)
• Bump google-health-api to 0.9.0 (@allenporter - #179323)
• Bump ical to 14.1.1 (@allenporter - #179325)
• Fix Signal Messenger self notifications (@brozikcz - #179351)
• Remove use of default_ device info in device_tracker (@emontnemery - #179380)
• Remove use of default_ device info in dlna_dmr (@emontnemery - #179381)
• Remove use of default_ device info in fritz (@emontnemery - #179382)
• Remove use of default_ device info in netgear (@emontnemery - #179383)
• Remove use of default_ device info in unifi (@emontnemery - #179384)
• Remove use of default_ device info in wake_on_lan (@emontnemery - #179385)
• Use dedicated translation on sensor entities if it’s Ecovacs mower (@edenhaus - #179416)
• Revert host update on Overkiz local gateway rediscovery (@iMicknl - #179422)
• Fix Vizio media player crash when volume is missing from audio settings (@raman325 - #179431)
• Fix KeyError in Shelly integration for LinkedGo ST802 in floor heating mode (@bieniu - #179435)
• Invalidate conversation slot-list cache on device registry changes (@emontnemery - #179486)
• Log warning when event triggers filter on composite device (@emontnemery - #179490)
• Bump holidays to 0.103 (@gjohansson-ST - #179500)
• Remove just go2rtc sessions of the failing camera (@edenhaus - #179534)
• Bump reolink-aio to 0.21.9 (@starkillerOG - #179625)
• bump pyenphase to 4.0 and add required None handling and tests (@catsmanac - #179673)
• Bump volvocarsapi to v0.4.4 for the Volvo integration (@thomasddn - #179712)
• Bump aiowebostv to 0.9.2 (@thecode - #179757)

Need help? Join the community

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

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

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

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

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

Backward-incompatible changes

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

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

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

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

All changes

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

Something big just happened. As the Open Home Foundation’s Android developer for Home Assistant, I was invited by the European Commission to consult on Android interoperability. On July 16, 2026, the Commission adopted a decision requiring Alphabet to open up eleven Android features — including always-on wake word detection, ambient sensor access, and screen automation — to all assistants, on equal terms.

The Open Home Foundation fights for privacy, choice, and sustainability. These principles are at the heart of everything we do, including how we handle website analytics. Our position is clear: we reject tools that track individuals across the web to monetize their data. Instead, we want aggregated, anonymized analytics that show how our websites are performing overall — without identifying who our visitors are, or compromising their privacy.

• [Halo: Campaign Evolved]: Resolved game crashes observed on RTX 50 Series GPUs with R610 drivers. [6259837]
• Path of Exile 2: Fixed intermittent long pauses that could occur after extended gameplay sessions in DX12 mode [5090018]
• Silent Hill F: Gaming stability improvements [6432954]
• [Strange Brigade/Zombie Army 4:Dead War]: Game may crash when exiting if NVIDIA App In-Game Overlay is enabled [6392324]
• Improves frame pacing in certain DX11 games when Smooth Motion is used while G-SYNC is enabled [6300603]

• RTX Dynamic Vibrance is incorrectly applied to Wallpaper Engine [6244021]
• Paint.NET may crash during launch when NVIDIA Surround is enabled [5366537]

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

Where there’s smoke, there’s FireAvert

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

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

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

On the same frequency

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

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

FireAvert automatic shutoffs for electric and gas stoves

Safe as houses

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

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

Devices

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

Check out the devices that made the grade:

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

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

Building the brigade

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

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

Geared up and ready to respond

Forged to protect the community, FireAvert are a natural match for ours. We’re thrilled to have them join the ranks, and excited for Home Assistant users to be able to add another line of defense for their smart homes, and the people and pets who live in them. Head to our certified device list to discover the full range of devices to safeguard your home.

FAQs

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

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

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

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

Q: How were these devices tested?

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

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

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

Hi,

The OpenWrt community is proud to announce the newest stable release of the OpenWrt 24.10 stable series.

This release fixes many security issues, several of them remotely triggerable in network services that are enabled by default. We strongly recommend everyone to upgrade.

The OpenWrt 24.10 series is in security maintenance (only security problems are fixed), with end of life (EoL) projected for September 2026. We recommend migrating to OpenWrt 25.12 before then.

Download firmware images using the OpenWrt Firmware Selector:

• https://firmware-selector.openwrt.org/?version=24.10.8

Download firmware images directly from our download servers:

• https://downloads.openwrt.org/releases/24.10.8/targets/

Main changes between OpenWrt 24.10.7 and OpenWrt 24.10.8

Only the main changes are listed below. See changelog-24.10.8 for the full changelog.

Security fixes

This release fixes several remotely triggerable vulnerabilities in core network
services that are enabled by default. Updating is strongly recommended.

• odhcpd (DHCPv6/DHCPv4/RA server, enabled by default): multiple vulnerabilities reachable by a network-adjacent, unauthenticated attacker were fixed:
  • CVE-2026-53921 (Critical): stack buffer overflow in the DHCPv6 IA reply serialization, triggerable with crafted DHCPv6 REQUEST packets.
    GHSA-7fwx-hhrg-3496
  • Reconfigure-Accept stack buffer overflow (High, no CVE assigned): the Reconfigure-Accept reply block wrote 36 bytes into the response buffer without checking the remaining space, leading to a pre-auth out-of-bounds write.
    https://github.com/openwrt/openwrt/security/advisories/GHSA-q6wx-p68j-chp9
  • CVE-2026-53918 (High): use-after-free through a dangling first-lease pointer in the DHCPv6 IA handler.
    GHSA-44ff-jcwh-wgc2
  • CVE-2026-53920 (High): stack memory disclosure via a truncated DHCPv6 IA_NA/IA_PD option.
    GHSA-p769-5v73-pc4f
  • CVE-2026-53922 (Moderate): pre-auth denial of service via a size_t underflow in DHCPv6 IA handling.
    GHSA-7hcw-g2jh-pqv5
  • Zero-length CLIENT_ARCH option (Moderate, no CVE assigned): stack buffer over-read, and an unaligned read that crashes on strict-alignment targets.
    https://github.com/openwrt/odhcpd/security/advisories/GHSA-7x9h-5mxm-jg3f
  • NDP hop-limit spoofing (Moderate, CVSS 5.4, no CVE assigned): the NDP relay accepted IPv6 Neighbor Solicitations with a hop limit other than 255 (RFC 4861 violation), letting an off-link attacker spoof NS packets through the relay. Only relevant when the NDP relay is enabled.
    https://github.com/openwrt/odhcpd/security/advisories/GHSA-qvg7-9jf5-wgjc
• odhcpd / LuCI stored XSS: CVE-2026-62948 (Critical): an unauthenticated DHCPv6 client could inject lease-file lines through a crafted FQDN hostname, resulting in stored cross-site scripting on the LuCI DHCPv6 leases status page. Fixed by escaping client hostnames in the lease state file.
  GHSA-hhmc-92hw-535f
• uhttpd (web server, serves LuCI): three HTTP request smuggling issues on keep-alive connections were fixed:
  • CVE-2026-55614 (High): case-sensitive Transfer-Encoding matching.
    GHSA-mcfg-c4r7-pjpf
  • CVE-2026-55612 (High): invalid chunk-length state reset.
    GHSA-p55c-rmhc-qfm5
  • CVE-2026-55613 (Moderate): ubus POST body parse-error desync.
    GHSA-wgwp-64hh-f52p
  • In addition uhttpd received hardening without an assigned CVE: a one-byte overflow in uh_urldecode(), an off-by-one out-of-bounds read in uh_b64decode(), constant-time password comparison and stricter handling of $p$ crypt-hash entries in the authentication realm.
• rpcd: ACL bypass through symlinks (High): the file plugin matched ACL grants against the textual path but then followed symlinks unchecked, so a symlink inside an ACL-covered directory let a limited account read or write arbitrary root-owned files. The path is now re-resolved and re-authorized for every operation that dereferences the final component.
  https://github.com/openwrt/openwrt/security/advisories/GHSA-q5gr-86pq-vvwr
• cgi-io (file upload/download helper used by LuCI, installed by default with LuCI):
  • CVE-2026-62947 (Moderate): ACL bypass and arbitrary root file read — the download and exec paths were checked against the ACL before being canonicalized, so path traversal let an authenticated user with wildcard read permission read any root-readable file (e.g. /etc/shadow).
    GHSA-jw5r-xhf5-2xcq
  • Use-after-free (Moderate, no CVE assigned): decoding malformed percent-encoded POST field data could use freed memory.
    https://github.com/openwrt/openwrt/security/advisories/GHSA-wvhq-qmwj-grj2
• LuCI (web interface): several issues in LuCI modules and applications were fixed. The privilege-escalation issues only apply if the affected app is installed and a limited (delegated) account with the relevant ACL exists:
  • luci-app-ddns (High): the ucode status backend passed DDNS UCI values such as lookup_host, dns_server and the section name to system() as an unquoted shell string, so anyone able to write DDNS configuration could execute commands as root. The invocations now use the array form of system().
    https://github.com/openwrt/openwrt/security/advisories/GHSA-32r4-3wh2-qvq3
  • luci-app-samba4 (High): the read ACL granted exec permission for smbd in general rather than only smbd -V, allowing read-only accounts to run arbitrary commands as root.
    GHSA-vx64-mmp7-h36c
  • luci-app-upnp (High): stored XSS — an unauthenticated LAN client can inject JavaScript through a UPnP port-mapping description, which the underlying daemon does not sanitize. The description is now HTML-escaped.
    GHSA-8v49-6387-7f89
  • luci-mod-status (High): stored XSS via a DHCP/DHCPv6 lease hostname shown in the lease status tables. Together with the odhcpd fix above this closes the injection path from an unauthenticated DHCP client into the LuCI admin UI.
    GHSA-686p-p8p9-x6fh
  • luci-base: the dispatcher now escapes the URL path and user name when logging, so crafted login requests can no longer pollute the system log.
  • The LuCI rpcd ACL files were adjusted for the symlink-aware rpcd ACL check mentioned above, so that /proc paths that are symlinks (such as /proc/mounts) keep working.
• umdns (mDNS responder): CVE-2026-55492 (Moderate, CVSS 6.5): an unauthenticated attacker on the local network segment could flood the daemon with unique mDNS records; the unbounded cache exhausted the heap and took the whole device into out-of-memory. Fixed by bounding the cache size and clamping hostile TTLs.
  GHSA-jg8f-fhfw-jg46
• ead (Emergency Access Daemon): CVE-2026-55490 (Moderate): an integer underflow in handle_send_a() allowed an unauthenticated attacker on the local segment to crash the daemon with a single crafted packet.
  GHSA-9558-77jp-g3fw
• hostapd / wpa_supplicant: the fixes from upstream hostap security advisory 2026-1 were applied. Missing validation of multi-link (MLO / IEEE 802.11be) information in received Management frames could terminate the process or corrupt a small amount of memory; the frames need neither authentication nor user interaction.
  https://w1.fi/security/2026-1/missing-ml-parsing-validation.txt
  https://github.com/openwrt/openwrt/security/advisories/GHSA-3hj7-gj5w-h68m
• dropbear (SSH): security fixes from upstream 2026.90 were backported:
  • CVE-2019-6111: a malicious server could make the scp client overwrite unexpected local files (missing OpenSSH patch). Note the accompanying upstream behaviour change: scp -r is now rejected when the target directory already exists.
  • CVE-2026-35385: scp did not clear setuid/setgid bits on received files.
  • An authenticated user could bypass an authorized_keys forced_command option when dropbear runs with -t; authorized_keys is now opened non-blocking (local denial of service via special files); and a close() on a file descriptor obtained from an out-of-bounds read was fixed.
• musl libc: backport of the upstream fixes for CVE-2026-6042 (algorithmic-complexity denial of service in iconv) and CVE-2026-40200 (stack corruption in qsort with sufficiently large inputs).
• OpenSSL: update to 3.0.21, fixing multiple security vulnerabilities (CVE-2026-45447, CVE-2026-34182, CVE-2026-45445, CVE-2026-7383, CVE-2026-9076, CVE-2026-34180, CVE-2026-42766, CVE-2026-42770, CVE-2026-45446).
• Linux kernel: update to 6.6.144, pulling in the upstream 6.6.142, 6.6.143 and 6.6.144 stable releases, which fix multiple security vulnerabilities.
• dnsmasq: update to 2.93, which carries the security fixes that were backported into 2.90 in the previous release (CVE-2026-2291, CVE-2026-4890, CVE-2026-4891, CVE-2026-4892, CVE-2026-4893 and CVE-2026-5172) plus further upstream fixes.

In addition, the packages feed shipped with this release moved a number of
optional packages to newer upstream versions that contain security fixes, among
them curl (8.12.1 to 8.19.0), expat (2.7.4 to 2.8.2), BIND (9.20.23 to 9.20.26),
PHP 8 (8.3.29 to 8.3.32), Tor (0.4.8.22 to 0.4.9.10), unbound (1.24.2 to 1.25.1),
lighttpd (1.4.82 to 1.4.85), haproxy (3.0.19 to 3.0.25) and rsync (3.4.2 to 3.4.3).
collectd also received a fix for a use-after-free in the ping plugin. These
packages are not part of the default images — you have to update the installed
packages on your device to receive them.

Beyond the issues listed above, this release fixes a number of further security
and robustness problems in odhcpd, odhcp6c, rpcd and uhttpd for which no CVE
number or dedicated advisory was assigned. We strongly recommend upgrading to
the latest OpenWrt release and installing all available package updates.

Device support

No new devices were added in this security maintenance release.

Device fixes:

• airoha: update the PCS driver to a newer proposed upstream version (EN7581 Ethernet SerDes)
• ipq806x: Extreme Networks AP3935 - disable PHY hibernation on LAN1, which otherwise stayed dead when no cable was connected at power-on

WiFi fixes and improvements

• mac80211: update the backported wireless stack and drivers from 6.12.61 to 6.12.96, containing many upstream fixes for ath10k, ath11k, rtw88, rtlwifi and iwlwifi, among them:
  • ath10k: skip WMI and beacon transmission when the device is wedged
  • ath11k: fix a warning on unbind and fix peer resolution on the RX path
  • rtw88: fix memory leaks on USB write failures
  • mac80211/nl80211: reject oversized EMA RNR lists and fix multi-link element defragmentation
• hostapd / wpa_supplicant: multi-link (MLO) parsing validation fixes, see the security section above
• wireless-regdb: update to 2026.05.30

Network and service improvements

• odhcpd received many DHCPv6/DHCPv4 correctness and robustness fixes on top of the security fixes listed above, among them bounded nested relay recursion, correct handling of DHCPv4 Pad/End option encoding, fixed reallocation error handling and a memory leak on reload
• odhcp6c: several fixes to DHCPv6 option parsing, RFC 6603 prefix-exclude handling, Reconfigure message validation and script invocation
• rpcd: fixes for a use-after-free in the async exec reply path, a double close of exec pipe descriptors, an integer overflow in the UCI apply timeout and several memory leaks
• umdns: update to a current version with the cache limits mentioned above

Other changes

• busybox: the shell command history is now saved again. To avoid flash wear, it is written only when a shell session exits and it is stored in /tmp, so it is lost on reboot. The location can be changed in /etc/profile.d/busybox-history-file.sh.

Core components update

• Linux kernel: update from 6.6.141 to 6.6.144
• OpenSSL: update from 3.0.20 to 3.0.21 (multiple security fixes, see above)
• dnsmasq: update from 2.90 to 2.93
• mac80211: update from 6.12.61 to 6.12.96
• wireless-regdb: update from 2026.03.18 to 2026.05.30
• ca-certificates: update from 20260223 to 20260601 (refreshed root CA bundle)

Upgrading to 24.10

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.

• Users of scp from the dropbear package: recursive copies (scp -r) into an already existing target directory are now rejected. This is an intentional upstream change that comes with the fix for CVE-2019-6111. Use rsync or copy into a non-existing directory instead.

Known issues

• LEDs for Airoha AN8855 are not yet supported. Devices like the Xiaomi AX3000T with an Airoha switch will have their switch LEDs powered off. This will not be addressed in the OpenWrt 24.10 series any more, it is fixed in OpenWrt 25.12.
• 5GHz WiFi is non-functional on certain devices with ath10k chipsets. Affected models include the Phicomm K2T, TP-Link Archer C60 v3 and possibly others. For details, see issue #14541.

Full release notes and upgrade instructions are available at
https://openwrt.org/releases/24.10/notes-24.10.8

In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/24.10/notes-24.10.8#known_issues

For a detailed list of all changes since 24.10.7, refer to
https://openwrt.org/releases/24.10/changelog-24.10.8

To download the 24.10.8 images, navigate to:
https://downloads.openwrt.org/releases/24.10.8/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=24.10.8

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

Ever since we introduced the idea of a community-powered device database at State of the Open Home 2025, our goal has been clear: create a “Wikipedia of smart home devices” based on real-world usage. In February, we took the first step by inviting Home Assistant users to voluntarily share anonymized device data to help us build it.

• N/A

• Tencent Meeting: Flickering may be observed when Smooth Motion is enabled globally [6329207]

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

IoTorero enters the ring

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

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

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

Speaking of community, the development of projects like ESPHome from the Open Home Foundation is supported by Home Assistant Cloud subscribers and anyone who purchases Home Assistant hardware. While all of IoTorero’s devices work locally, if you’re interested in remote access – for example to check your energy use or open the garage door from a distance – check out Home Assistant Cloud.

Right on (Io)Time

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

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

Devices

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

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

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

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

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

Proxy points

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

Old friends, new badge

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

FAQs

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

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

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

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

Q: How were these devices tested?

A: All devices in this list were tested using a standard Home Assistant Green as a hub and using the ESPHome integration. If you have a different set-up that’s not a problem, but we test against these as they are the most effective way for our team to certify within our ecosystem.

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

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

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

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

Here’s everything you need to know:

Why we’re making the change

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

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

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

What this means for you

A recap of what’s changing:

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

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

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

Looking ahead

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

Home Assistant 2026.7! 🎉

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

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

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

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

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

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

Enjoy the release!

../Frenck

• Creating automations just became easier, natural and more powerful
  • Start with what you want, not how it works
  • Built around areas, not one device or entity at a time
  • More than friendlier wording
  • No technical traps
  • Your automations are safe, and YAML isn’t going anywhere
  • Documentation is part of the feature
• Activity logbook
• Update all
• Integrations
  • New integrations
  • Noteworthy improvements to existing integrations
  • Integration quality scale achievements
  • Now available to set up from the UI
  • Farewell to the following
• Other noteworthy changes
  • Time format selection
  • Dedicated panels for infrared and radio frequency
  • The ZHA Zigbee device management got an overhaul
  • Keeping your Raspberry Pi firmware up to date
• Patch releases
  • 2026.7.1 - July 3
  • 2026.7.2 - July 10
  • 2026.7.3 - July 21
  • 2026.7.4 - July 24
• Need help? Join the community
• Backward-incompatible changes
• All changes

A huge thank you to all the contributors who made this release possible! And a special shout-out to @piitaya, @sairon, and @agners who helped write the release notes this release. Thanks to them, these release notes are in great shape. ❤️

Creating automations just became easier, natural and more powerful

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

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

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

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

Start with what you want, not how it works

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

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

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

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

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

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

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

More than friendlier wording

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

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

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

No technical traps

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

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

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

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

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

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

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

Documentation is part of the feature

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

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

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

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

Activity logbook

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

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

Each entry now sits on a vertical rail: the time on the left, a colored dot with the entityAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more]’s icon, and the text beside it. You read it top to bottom, like a feed. Entries are grouped by day, with Today, Yesterday, and dated headers, so you never lose track of where you are in time. The dot takes on the state color too, so an on and an off are easy to tell apart at a glance, without reading a word.

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

A few more touches make it feel right at home:

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

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

Update all

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

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

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

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

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

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

Integrations

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

New integrations

We welcome the following new integrations in this release:

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

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

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

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

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

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

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

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

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

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

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

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

Noteworthy improvements to existing integrations

It is not just new integrationsIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] that have been added; existing ones keep getting better too. Here are some of the noteworthy improvements this release:

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

Integration quality scale achievements

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

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

• 1 integration reached platinum 🏆

  • Yoto, thanks to @piitaya

• 2 integrations reached gold 🥇

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

• 3 integrations reached silver 🥈

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

• 1 integration reached bronze 🥉

  • openSenseMap, thanks to @AlCalzone

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

A big thank you to all the contributors involved! 👏

Now available to set up from the UI

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

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

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

Farewell to the following

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

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

Other noteworthy changes

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

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

Time format selection

Some entitiesAn entity represents a sensor, actor, or function in Home Assistant. Entities are used to monitor physical properties or to control other entities. An entity is usually part of a device or a service. [Learn more] tell time. A sensor with the next sunrise, the timestamp of your last backup, a countdown to the next calendar event. How that moment should be shown is a matter of taste: sometimes you want the exact date and time, and sometimes a friendly “in 3 hours” or “2 days ago” is far more useful at a glance.

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

Thanks, @karwosts!

Dedicated panels for infrared and radio frequency

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

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

Thanks, @balloob!

The ZHA Zigbee device management got an overhaul

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

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

Thanks, @jpbede!

Keeping your Raspberry Pi firmware up to date

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

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

A few things to keep in mind:

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

Thanks, @sairon!

Patch releases

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

2026.7.1 - July 3

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

2026.7.2 - July 10

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

2026.7.3 - July 21

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

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

2026.7.4 - July 24

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

Need help? Join the community

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

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

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

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

Backward-incompatible changes

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

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

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

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

All changes

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

Hi,

The OpenWrt community is proud to announce the fifth service release of the OpenWrt 25.12 stable series.

Download firmware images using the OpenWrt Firmware Selector:

• https://firmware-selector.openwrt.org/?version=25.12.5

Download firmware images directly from our download servers:

• https://downloads.openwrt.org/releases/25.12.5/targets/

Main changes between OpenWrt 25.12.4 and OpenWrt 25.12.5

Only the main changes are listed below. See the full changelog for details.

Security fixes

This release fixes several remotely triggerable vulnerabilities in core network services that are enabled by default. Updating is strongly recommended.

• odhcpd (DHCPv6/DHCPv4/RA server, enabled by default): multiple vulnerabilities reachable by a network-adjacent attacker were fixed by updating odhcpd:
  • CVE-2026-53921 (Critical): stack buffer overflow in the DHCPv6 IA reply serialization, triggerable with crafted DHCPv6 REQUEST packets. GHSA-7fwx-hhrg-3496
  • CVE-2026-53918 (High): use-after-free in the DHCPv6 IA handler. GHSA-44ff-jcwh-wgc2
  • CVE-2026-53920 (High): stack memory disclosure via a truncated DHCPv6 IA_NA/IA_PD option. GHSA-p769-5v73-pc4f
  • CVE-2026-53922 (Moderate): pre-auth denial of service via a size_t underflow in DHCPv6 IA handling. GHSA-7hcw-g2jh-pqv5
  • CVE-2026-55606 (Moderate): stack buffer overread caused by a DUID length endianness mismatch. GHSA-x8x4-7gvf-gp45
  • No CVE assigned (Moderate, CVSS 5.4): the NDP relay accepted IPv6 Neighbor Solicitations with a hop limit other than 255 (RFC 4861 violation), letting an off-link attacker spoof NS packets through the relay (neighbor-cache poisoning, traffic redirection or DoS). Only relevant when the NDP relay is enabled. https://github.com/openwrt/odhcpd/security/advisories/GHSA-qvg7-9jf5-wgjc
• odhcpd / LuCI stored XSS (Critical): an unauthenticated DHCPv6 client could inject lease-file lines through a crafted FQDN hostname, resulting in stored cross-site scripting on the LuCI DHCPv6 leases status page. Fixed by escaping client hostnames in the lease state file. GHSA-hhmc-92hw-535f
• uhttpd (web server): three HTTP request smuggling issues on keep-alive connections were fixed:
  • CVE-2026-55612 (High): invalid chunk-length state reset. GHSA-p55c-rmhc-qfm5
  • CVE-2026-55614 (High): case-sensitive Transfer-Encoding matching. GHSA-mcfg-c4r7-pjpf
  • CVE-2026-55613 (Moderate): ubus POST body parse-error desync. GHSA-wgwp-64hh-f52p
• cgi-io: ACL bypass / arbitrary file read (Moderate): a path-traversal flaw in the cgi-download handler let an authenticated user with wildcard read permission read any root-readable file (e.g. /etc/shadow). GHSA-jw5r-xhf5-2xcq
• LuCI (web interface): a set of issues in LuCI core modules and applications were fixed. Most let a logged-in user with limited (delegated) permissions escalate to root command execution; a few are stored XSS issues reachable by clients on the network. The privilege-escalation issues only apply if the affected app is installed and the account/ACL in question exists:
  • luci-app-tailscale-community (Critical, CVSS 9.9): command injection allowing delegated users to run commands as root via tailscale.do_login. GHSA-xwc5-mx58-rh35
  • luci-app-advanced-reboot (High): CVE-2026-55897 — a read ACL exposes /bin/sh via file.exec, allowing delegated users to run commands as root. GHSA-vj96-f37g-37f6
  • luci-app-adblock-fast (High): CVE-2026-55159 — delegated users can reach root command execution via newline-separated cron entries. GHSA-ggpf-xrph-wg5v
  • luci-app-samba4 (High): a read ACL allows authenticated root command execution via the smbd file.exec permission. GHSA-vx64-mmp7-h36c
  • luci-app-travelmate (High): a delegated UCI write can execute the travelmate auto-login command as root. GHSA-p35r-3323-6g7g
  • luci-app-upnp (High): stored XSS — an unauthenticated LAN client can inject JavaScript via a UPnP port-mapping description. GHSA-8v49-6387-7f89
  • luci-mod-network / luci-mod-status (High): stored XSS via a DHCPv6 lease hostname (FQDN) shown in the status tables. GHSA-686p-p8p9-x6fh
  • luci-app-banip (High): a crafted LuCI login username can inject an arbitrary IP into banIP's log parser, causing the wrong address to be blocked. GHSA-r6hx-4f83-vp8m
• ead (Emergency Access Daemon): CVE-2026-55490 (Moderate): an integer underflow in handle_send_a() allowed a pre-auth denial of service. GHSA-9558-77jp-g3fw
• Linux kernel: update to 6.12.94, pulling in the upstream 6.12.88 through 6.12.94 stable releases, which fix multiple security vulnerabilities, such as CVE-2026-43500.
• OpenSSL: update to 3.5.7, fixing multiple security vulnerabilities (CVE-2026-7383, CVE-2026-9076, CVE-2026-34180, CVE-2026-34181, CVE-2026-34182, CVE-2026-34183, CVE-2026-42764, CVE-2026-42766, CVE-2026-42767, CVE-2026-42768, CVE-2026-42769, CVE-2026-42770, CVE-2026-45445, CVE-2026-45446, CVE-2026-45447).
• musl libc: backport upstream fixes for CVE-2026-6042 and CVE-2026-40200.
• dropbear (SSH): backport security fixes from upstream 2026.90 and 2026.91, including CVE-2019-6111 (a malicious server could trick the scp client into overwriting arbitrary local files) and CVE-2026-35385.

Beyond the issues listed above, this release fixes a number of further security problems for which no CVE number or dedicated advisory was assigned. We strongly recommend upgrading to the latest OpenWrt release and installing all available package updates.

Device support

New devices supported in 25.12.5:

• ipq40xx: Linksys MR9000
• mediatek (filogic): GL.iNET GL-MT3600BE
• mediatek (filogic): Huasifei WH3000R (NAND)
• mediatek (filogic): JioRouter AX6000 (JIDU6101)
• mediatek (filogic): netis EAP930 V1
• mediatek (filogic): netis MEX605
• mediatek (filogic): TP-Link F65 v1
• mediatek (filogic): Zbtlink ZBT-Z8106AX-S
• mvebu: Zyxel NAS326
• ramips (mt76x8): Cudy WR300 v1
• ramips (mt7621): I-O DATA WN-AX2033GR2

New image variants for already supported devices:

• mediatek (filogic): Qihoo 360T7 - add UBI layout image
• mediatek (filogic): Creatlentem CLT-R30B1 - add all-in-UBI layout image
• mediatek (filogic): Bazis AX3000WM - also recognized under its alternative name WD-R3000N-G2A

Device fixes:

• ath79: MikroTik - build AG71XX_LEGACY as a module, fixing AR8216/AR8236/AR8316 switch bring-up on boot on some MikroTik devices (#23739)
• mediatek: do not let devfreq power off the CPU (stability fix)
• mediatek (filogic): Wavlink WL-WN536AX6 rev A - several fixes (correct 5 GHz MAC address, MAC-address nvmem layout, NAND bad-block management, SPI drive strength, network LED)
• mediatek (filogic): Qihoo 360T7 - fix DDR3 rate
• mediatek: Acer Predator W6X - add LED boot status support
• ramips: PAX1800 Lite - fix label MAC device and avoid attaching both UBI partitions on boot
• ramips (mt76x8): Cudy LT300 v3 - fix backup partition offset
• rtl8367b: fix RTL8367S-VB VLAN multicast memory handling
• mvebu: uDPU / eDPU - convert to dual (A/B) firmware
• ipq806x: AP3935 - disable hibernation on LAN1
• airoha (an7581): platform improvements and upstream networking fixes

WiFi fixes and improvements

• wifi-scripts: fix a null dereference on 6 GHz-only radios
• wifi-scripts: fix EAP (802.1X) station mode in the wpa_supplicant configuration generator
• wifi-scripts: fix tracking of disabled virtual interfaces
• hostapd: fix a misplaced radar-detected (DFS) ubus notification

Network and service improvements

• New "network" LED trigger (lan/wan/wlan) for link and activity indication on supported devices
• odhcpd and odhcp6c received many DHCPv6/DHCPv4 and IPv6 prefix-delegation correctness and robustness fixes, on top of the security fixes listed above, including more stable DHCPv6 IAID handling
• More robust handling of invalid DHCP / DHCPv6 client identifiers
• ubus, rpcd, uhttpd, umdns, uclient and fstools updated with stability and hardening fixes

Other changes

• kmod-nf-nathelper-extra was split into individual per-protocol packages, so only the needed NAT helper modules have to be installed.
• Matching the linker max-page-size to the target page size removes unnecessary padding, which can make many binaries - and thus the images - a bit smaller.
• OpenWrt builds are now more reproducible.

Core component updates

• Linux kernel: update from 6.12.87 to 6.12.94
• OpenSSL: update from 3.5.6 to 3.5.7 (multiple security fixes, see above)
• wireless-regdb: update from 2026.03.18 to 2026.05.30
• dnsmasq: update from 2.91 to 2.93
• ca-certificates: update from 20260223 to 20260601 (refreshed root CA bundle)
• util-linux: update from 2.41.3 to 2.41.5

Upgrading to 25.12.5

Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.

• Sysupgrade from 23.05 or earlier to 25.12 is not officially supported.

• Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed. fc0c518

• Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4, and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe

• TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).

• Meraki MX60: Direct sysupgrade to 25.12.5 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.

• Sitecom WLR-7100 (X7 AC1200): This device was moved from the ath79/generic target to the ath79/tiny target in OpenWrt 25.12.4. Users upgrading from 25.12.3 or earlier need to flash the new image from the ath79/tiny target (use sysupgrade -F).

Known issues

• Zyxel EX5601-T0: the WAN interface was renamed from eth1 to wan — check and update your network configuration after upgrading.
• Pixel 10 phones have problems connecting to WPA3-protected WiFi 6 APs. #21486
• 802.11r Fast Transition (FT) causes connection problems with some WiFi clients when WPA3 is used. #22200
• SQM CAKE MQ (cake_mq): throughput may be unexpectedly low on some configurations after the scheduler fixes in this release. #22344

Full release notes and upgrade instructions are available at
https://openwrt.org/releases/25.12/notes-25.12.5

In particular, make sure to read the known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.5#known_issues

For a detailed list of all changes, refer to
https://openwrt.org/releases/25.12/changelog-25.12.5

To download the 25.12.5 images, navigate to:
https://downloads.openwrt.org/releases/25.12.5/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.5

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

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

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

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

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

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

Serving up more with matter.js

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

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

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

It was just a matter of time

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

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

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

An easy switch

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

Faster, smarter, and more secure

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

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

A clearer view

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

Your whole network, at a glance.

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

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

A foundation for what’s next

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

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

Every smart home has them: the older devices that still work perfectly well but no longer fit neatly into a modern setup. Instead of letting them gather dust in a drawer, the Open Home Foundation’s projects can help you bring them back into the fold. Here’s how a little proxying can give your beloved old gear a new lease of life, and keep your smart home that bit more sustainable.

• World of Warcraft: Gaming stability improvements [5563205]
• Apex Legends: Occasional visual corruption after extended gameplay [6239327]
• Users may observe DLSS settings being grayed out in certain games after updating to display driver 615.47 [6262805]
• Improved gaming stability in multi-monitor configurations when using V-SYNC with DLSS Frame Generation [6158481]
• Resolved an issue that could cause jittering or ghosting in some DirectX 11 games when Smooth Motion is enabled [5937897]
• Resolved an issue that could cause some games to crash when launched with Smooth Motion enabled [5466398]

• [Ada] Resolves a frame pacing issue on certain monitors when G-SYNC is enabled [6226972]
• Resolved an issue that prevented the EDID from being read on certain monitors causing them to be identified as "NVIDIA NV-Failsafe” [6005508]
• Resolved an issue where certain monitors would not wake from sleep mode [5806798/5635230]
• General stability improvements when the system fails to create a new allocation [5449920]