Home Assistant 2026.5 Release: What It Means for You

The Home Assistant 2026.5 release dropped on 6 May 2026, and it is one of the more consumer-friendly updates in recent memory. If you have been running Home Assistant on a Raspberry Pi or a Green box and mostly ignore the developer-flavoured release notes, this guide pulls out the changes that genuinely matter for the way you use the system day to day — plus the breaking changes that might bite if you upgrade without checking.

The four changes that will affect everyday users

Skip the developer internals — here is what actually changes day to day

Home Assistant releases tend to bundle dozens of small improvements with a handful of headline features. The release notes for 2026.5 are no different. For non-developer users, four changes stand out.

1. The new maintenance dashboard

Home Assistant now ships with a dedicated maintenance dashboard that auto-discovers every battery-powered device in your home and groups them by room. Low batteries are highlighted at the top. For anyone managing a couple of dozen Zigbee or Matter sensors, this replaces a fiddly custom template helper or a third-party card that you had to install and maintain yourself.

If you have ever had a motion sensor silently die in the middle of the night because you missed a low-battery notification two weeks earlier, this is the feature for you. It is enabled by default after the update — look for the new "Maintenance" entry in your sidebar.

2. Duration triggers and conditions

This one is a quiet revolution for anyone who writes automations. You can now express time-based logic naturally without templates or YAML workarounds. Triggers like "when no motion has been detected for 15 minutes" or conditions like "if the front door has been open for more than 2 minutes" are now first-class building blocks in the visual automation editor.

If you have been on Home Assistant for a while, you will remember stitching this together with last_changed templates and waiting-for-trigger blocks. That whole pattern goes away. New users get a much smoother on-ramp, and existing automations can be simplified during their next refactor.

3. Native RF device support

Home Assistant 2026.5 adds proper native support for radio frequency (RF) controlled devices — motorised blinds, garage doors, ceiling fans, and the wireless mains-plug remotes you find at the back of an electrics drawer. You still need a bridge device (a Broadlink RM4 Pro, or an ESPHome board with a sub-GHz transmitter for about £10), but the integration is now built in rather than a community add-on.

Two new integrations ship alongside this: Honeywell String Lights and Novy Cooker Hood. The bigger win is for the older equipment that has been gathering dust because it was "not smart enough" — bringing it into Home Assistant means it can finally join your automations.

4. Vacuum and lawn mower "clean by area"

Robot vacuum users get a redesigned info dialog with state-driven animations and, more usefully, a "clean by area" feature that maps Home Assistant rooms to the segmented zones your vacuum already understands. You can finally write an automation that says "clean the kitchen and hallway when everyone leaves the house" without poking at the vacuum app's own scripting layer. The same machinery now extends to lawn mowers, which is a nice touch for the small but growing set of robot mower owners.

Smaller wins worth knowing about

✓

Security dashboard activity log: a 24-hour live feed of door openings, motion events, lock activity and household arrivals in one sidebar.

✓

Shortcut card and badge: one-tap dashboard tiles that can open a URL, launch voice assist, or trigger "turn off all lights" without dropping into the more menu.

✓

Media player tile improvements: reorder playback controls, pick exactly which buttons appear, and switch sound modes like Movie / Music / Night from the tile itself.

✓

Serial port proxying over ESPHome: any serial device on your network can now talk to Home Assistant. Useful for Denon receivers, smart-meter P1 ports, and old kit you used to need a USB cable for.

✓

Twelve new integrations in total, including Duco ventilation systems, Victron Energy solar, and OMIE electricity pricing for Spain and Portugal.

✓

Refreshed toggle switches with proper keyboard navigation: tab to a toggle and use the arrow keys, which matters for accessibility and for power users.

✓

Context-aware autocomplete in the template and YAML editors, with hover tooltips showing the current value of any entity ID you mention.

Breaking changes to read before you click update

Home Assistant has been moving towards fewer surprise breakages, and 2026.5 is mostly clean. But a few of the changes will bite specific setups, so it is worth scanning this list before you press the button.

Person and device tracker: the "entered home" / "left home" triggers and the "is home" / "is not home" conditions have been removed. If any of your automations use these, you will need to switch to state-based triggers (<code>state from not_home to home</code>) until the planned replacements arrive.

Ring doorbell: the event type changed from <code>ding</code> to <code>ring</code> for standardisation. Any automation listening for the old event needs the name updated.

Gardena Bluetooth: the watering-finish entity moved from a binary sensor to a timestamp sensor — minor, but it will break templates that read it as a true/false value.

Supervisor actions now properly raise errors on failure instead of silently continuing. If you relied on the old behaviour (rare, but possible), add <code>continue_on_error: true</code> to those steps.

Webhook configuration: the <code>local_only</code> parameter must now be a boolean (<code>true</code> or <code>false</code>). Old configs that used <code>1</code> or other truthy values will need editing.

pilight integration: disabled outright in 2026.5 due to a broken dependency on the deprecated setuptools library. If you use pilight, hold off on the upgrade or migrate first.

The plain-English upgrade checklist

Take a snapshot first

Settings → System → Backups → Create backup. Even on a clean release, do not skip this. If anything misbehaves, you are one restore away from your old setup.

Scan the breaking changes list above

Search your automations for is_home / not_home, ring doorbell ding events, and any pilight references. Note the ones that need a manual touch.

Update from the UI

Settings → System → Updates → Update. On a Raspberry Pi 4 with Home Assistant OS, the update typically takes 5 to 10 minutes and the UI reconnects automatically.

Check the repair issues panel

After the reboot, head to Settings → Repairs. Home Assistant flags anything it detected during the upgrade — deprecation warnings, removed integrations, configuration that needs attention.

Spot-check your headline automations

Run the three or four automations you use every day (lights at sunset, presence-based heating, the morning routine). If they fire as expected, you are done. If not, the most likely culprit is one of the breaking changes from step 2.

Where this release fits in the bigger picture

The 2026.5 release continues a clear pattern in the Home Assistant project: pull more functionality out of community add-ons and into the core product, and round off the rough edges that put off non-developer users. Maintenance dashboards, duration triggers and built-in RF support are exactly the kind of things that used to require a HACS install, a custom card, and an evening of YAML tinkering.

Combined with the steady drumbeat of Matter improvements through the year, Home Assistant is quietly becoming the platform you can recommend to a less-technical friend without a long list of caveats. If you have not looked at it for a while, the gap between Home Assistant and the major commercial hubs has narrowed considerably in the last 12 months.

Frequently asked questions

How big is the 2026.5 update on a Raspberry Pi?

On Home Assistant OS, the core update is typically 200–400 MB and takes 5 to 10 minutes on a Pi 4 with a decent SD card or SSD. Restore-from-backup if anything goes wrong adds another 5 to 10 minutes.

Do I need new hardware to use the RF integration?

Yes — you need a bridge that can transmit on sub-GHz RF frequencies. The cheapest route is an ESPHome board with a sub-GHz transmitter (about £10 in parts). A Broadlink RM4 Pro is the easier plug-and-play option at around £40.

Will my existing automations still work after the upgrade?

For most users, yes. The biggest risk is the removal of the "is home" / "is not home" conditions and the renaming of the Ring doorbell event from ding to ring. Search your automations for those before you upgrade.

Should I upgrade if I run pilight?

No — pilight is disabled in 2026.5 due to a dependency issue. Wait for an update from the integration maintainer, or migrate your pilight devices to the new native RF integration first.

Is the maintenance dashboard switched on by default?

Yes. After the upgrade, the Maintenance entry appears in the sidebar automatically and starts populating with every battery-powered device Home Assistant already knows about.

New to Home Assistant?

If the release notes are over your head, start with our beginner guide before upgrading anything.

Getting started with Home Assistant