Release update Ecosystems
Home Assistant 2026.7: what's new, what breaks
The July release lets you build automations in plain language, redesigns the logbook, and retires twenty integrations. Here's the 20-second version, and the detail when you want it.
Part of Home Assistant updates, our monthly release series
Every release
2026.7 Released 1 July 2026
Update, after one check The headline: purpose-specific triggers and conditions are now the default. You describe what you want the automation to do, rather than wiring technical triggers by hand. Existing automations keep running.
In this release 6 smaller wins · 10 integrations added · 20 removed · 5 breaking changes
Check first Renamed triggers · Z-Wave JS · Reolink · Battery attributes · Presence scanners
Affected only if you use one of these. None in your setup? You're clear to update.
The headline feature: automations that speak your language
The automation editor has always asked you to think like the machine. You picked a technical state change, typed in an entity ID, and assembled the outcome you wanted out of primitives. 2026.7 turns that around. Purpose-specific triggers and conditions have graduated out of Labs to become the default, so "when the back door has been open for five minutes" or "when nobody's home" are now first-class building blocks you choose directly.
Two things matter for existing setups. First, this is an editor change, not a format change, so every automation you have keeps running and YAML mode is untouched. Second, integrations can now teach Home Assistant their own triggers and conditions, which means the list gets better as the integrations you use catch up. The one catch is a handful of renamed trigger keys, covered in the breaking changes below.
Six smaller wins
The changes most people will notice day to day. Scan the tags for the areas you use.
Logbook
A redesigned activity logbook
A vertical timeline grouped by day, showing what changed and why: a person, an automation or an integration. The fix for working out what turned the lights on at 2am.
Updates
Update everything in one go
Pending updates are grouped by category (Home Assistant, integrations, apps) so you apply them together instead of one at a time.
Infrared
Dedicated infrared and RF panels
Settings panels for managing IR blasters and radio-frequency bridges, building on the infrared and RF support added earlier in 2026.
Zigbee
A rebuilt Zigbee device manager
ZHA device management moves to a full-page view with tabbed navigation, which makes a large Zigbee network far easier to work through.
Hardware
Raspberry Pi firmware updates
Bootloader and EEPROM updates now appear under Settings, then Updates, alongside everything else.
Core
A faster template engine
Templates evaluate about 40 per cent quicker, and the interface is snappier across the energy, history and statistics graphs.
Integrations: 10 in, 20 out
Removals matter more than additions, because a removal can break an automation or dashboard that references it. They're listed first, with what to do about each.
Removed in 2026.7 20 integrations
| Integration | Why | What to do |
|---|---|---|
| Microsoft Teams | Service closed | Microsoft discontinued the Office 365 Connectors it relied on in May. Remove the integration; there's no drop-in replacement. |
| Mycroft | Service closed | The upstream project wound down. If you use Mycroft for voice, stay put until you've moved to Assist. |
| Watson TTS | Service closed | Removed with the service. Any automation calling it for speech will fail silently, so swap the TTS engine first. |
| UniFi LED | Discontinued | The hardware has been discontinued for years. Nothing carries over. |
| SCSGate | Discontinued | Long-discontinued hardware with no maintainer. Remove the integration before updating. |
| ThermoWorks Smoke | Discontinued | Superseded upstream. Your probe entities disappear on update. |
The other 14 removals, all long-discontinued hardware
Acer projectorAmpio SmogATEN Rack PDUAvi-onBeeWi SmartClimBlinkStickClementineDovadoELIQ OnlineGitterGreenwave RealityLogentriesMicrosoft FaceTikteck
Added in 2026.7 10 integrations
AqvifyChef iQDropboxEdifier InfraredenergieleserEnvertech EVT800GreencellHelty FlowKlikAanKlikUitMELCloud Home
Breaking changes
5 this month, all narrow. If the summary at the top already cleared you, nothing below applies to your setup.
Breaking changes · check before you update Most setups are unaffected
Renamed triggers
Several entity trigger keys were renamed for consistency, so battery "low" became battery "became low". Automations using an old key stop working until updated.
What to do: re-save each affected automation in the editor and it migrates itself. YAML users edit the key by hand.
Z-Wave JS
The integration now requires zwave-js-server 3.9.0 or later (schema 49), the app at 1.4.0 or later, and the UI container at 11.19.1 or later.
What to do: update the Z-Wave JS add-on or container alongside Home Assistant, not after it.
Reolink
Dual-lens cameras now expose a sub-device per lens, and the entities lose their lens suffixes.
What to do: expect entity IDs to change. Check any automation or dashboard card that names a specific lens.
Battery attributes
iCloud, StarLine and Tractive no longer report battery_level as an attribute on the tracker.
What to do: point templates and automations at the dedicated battery sensor each integration already provides.
Presence scanners
The Person integration no longer reports home-zone coordinates the way presence-scanner setups relied on, and zone counting changed.
What to do: use the new in_zones attribute. Device trackers now return the smallest matching zone.
Should you update?
Our verdict Update, after one check
Yes, once you've checked the list above. The plain-language automation editor is the most approachable this part of Home Assistant has ever been, and it fixes the steepest part of the learning curve for anyone you're trying to bring along. The checks that matter: Z-Wave users should update the add-on in the same sitting, and anyone with a Reolink dual-lens camera should expect entity names to change.
If you'd rather let others find the bugs, patch releases now land most Fridays. Waiting a week costs you nothing.
Source: home-assistant.io
Frequently asked questions
When was Home Assistant 2026.7 released?
On 1 July 2026, following the usual first-Wednesday-of-the-month schedule. Patch releases follow most Fridays through the month.
What's the headline feature in 2026.7?
Purpose-specific triggers and conditions. Instead of choosing a technical state change and typing entity IDs, you describe the outcome you want, and integrations can teach Home Assistant their own triggers. It's the biggest change to the automation editor in years.
Will 2026.7 break my automations?
Existing automations keep running and YAML is unaffected in format. The one catch is that a few entity trigger keys were renamed, so an automation using an old key stops working until you re-save it. Take a backup before updating and check the breaking-changes list above.
Which integrations were removed in 2026.7?
Twenty in total. The ones most likely to affect a working setup are Microsoft Teams, Mycroft, Watson TTS, UniFi LED, SCSGate and ThermoWorks Smoke. Most of the rest are long-discontinued hardware.
Still need a hand?
We answer most messages within one business day. If your question is about an existing order, have your order number ready. It speeds things up.
Contact us