Home Assistant 2026.7 releases publicly on Wednesday, July 1, 2026 — two days from now — and brings the most consequential set of changes to the platform's automation engine and Matter implementation in years. The release, currently in its second beta build, moves purpose-specific automation triggers out of opt-in testing and makes them the default experience for all users, while simultaneously replacing the Python-based Matter server with a TypeScript implementation called matter.js that brings Matter 1.5.1 compliance, faster device reconnection, and a new Thread network visualization tool. New Matter diagnostic sensors will also surface device health data that was previously buried in JSON exports, and the platform's Activity feed is being rebuilt from a raw event log into a navigable timeline.

The update is available now in beta through the standard Home Assistant update channel. A release party livestream is scheduled for July 1, 2026 at 4:00 PM ET (20:00 GMT) on the Home Assistant YouTube channel.

Matter's Engine Gets Rebuilt: matter.js Takes Over

The single largest change in 2026.7 is one the draft article did not mention at all: the Matter server that powers all Matter device communication in Home Assistant has been rebuilt from the ground up. The previous server ran on Python using the official C++ Matter SDK. As of the 2026.7 release, it runs on matter.js — an open-source TypeScript implementation of the Matter standard originally created by Ingo Fischer, who joined the Open Home Foundation in 2025 as Lead Developer of Matter and subsequently donated the project to the foundation.

The switch from Python to TypeScript is not primarily a programming language preference. The matter.js architecture enables Home Assistant to track the Matter specification more closely — version 1.5.1 is now supported, with 1.6 in active development — and delivers concrete operational improvements: devices come back online faster after a server restart, over-the-air firmware updates are more reliable, and the commissioning pipeline now checks certificate revocation data, blocking uncertified devices from joining the network without user confirmation. The prior Python server could not easily enforce this security boundary.

The new server ships as Matter Server app 9.0 and migrates existing device data automatically on first boot. Users who have been running Home Assistant's Matter integration will not need to recommission devices; the switch is a drop-in replacement that starts delivering performance benefits with every subsequent startup.

Matter 1.5.1 and New Diagnostic Sensors Surface Hidden Device Health

The upgrade to Matter 1.5.1 — the most recent published version of the standard — directly enables support for new device categories including cameras, doorbells, and closures. It also unlocks a set of diagnostic entities that 2026.7 now exposes natively in the Home Assistant dashboard for the first time.

These diagnostic entities pull health data directly from Matter devices rather than requiring users to download and parse raw JSON diagnostic files. The new sensors include Reboot Count, Uptime, and Boot Reason — enough to answer the question every Matter user has encountered when a smart plug unexpectedly disappears from the network: was it a power interruption, a firmware crash, or something else? Binary sensors for Hardware Faults, Radio Faults, and Network Faults provide additional granularity, making it possible to spot a struggling device before it goes fully offline. Thread and Wi-Fi network diagnostic data from Matter devices is also now exposed as optional entities.

All diagnostic entities are disabled by default. Users who want them must enable them per-device through the Home Assistant interface. This prevents the dashboard from becoming cluttered with health metrics for installations that are already stable; the entities are there when needed and invisible otherwise.

Also new in 2026.7: support for the Matter soil moisture sensor device type, introduced in the Matter 1.5 specification alongside garden and irrigation features. No commercial Matter soil moisture sensors are currently available, but the addition means users running Zigbee or other protocol sensors through Matterbridge can expose their existing soil moisture hardware to any Matter-compatible controller.

Automations That Describe What You Want, Not How the Platform Works

The other headlining change in 2026.7 is the graduation of purpose-specific triggers and conditions from Home Assistant Labs — where they have been an opt-in experiment since early 2026 — to the default experience for every user. Lead developer Franck Nijhof, writing on his developer blog about the underlying design philosophy, described it as "more power, less complexity."

The practical difference for a user building an automation is significant. The previous editor required knowing which entity — a specific named sensor with a specific entity ID — governed the condition you wanted to monitor, then selecting whether you wanted a state trigger, a numeric state trigger, a device trigger, or one of several other trigger types, then specifying the comparison value and any edge-case handling for unknown or unavailable states. That sequence is sensible once you understand Home Assistant's entity model; it is genuinely opaque to someone who does not.

The new triggers work in reverse. A user who wants an automation to run when a motion sensor detects movement in the office types "Motion," selects the office area, and Home Assistant watches every motion sensor in that space automatically. A user who wants to know when a door has been open for ten minutes selects "Door Open" as the trigger type and sets the duration — no entity IDs, no state comparisons. Integrations can now also teach the automation engine their own purpose-specific triggers and conditions, meaning that a heat pump integration can expose "when heating demand exceeds threshold" as a named trigger rather than requiring users to construct that logic manually from raw sensor states.

The old building blocks have not been removed. Existing automations using generic triggers, raw entity states, templates, and YAML continue to work without changes. The new triggers are the better starting point for the next automation you build and a cleaner option for improving an old one — not a migration requirement.

How Do Purpose-Specific Triggers Work in Home Assistant?

Under the surface, purpose-specific triggers introduce a new architectural layer between the user-facing automation editor and the Home Assistant entity and state model. Rather than requiring users to understand which entity type corresponds to the condition they want — a motion sensor is a binary sensor with a "motion" device class; triggering on it previously required knowing that distinction — the new trigger model is organized around outcome concepts: "motion detected," "battery low," "temperature threshold." The automation engine maps these to the underlying entity classes and state conditions internally.

The engineering tradeoff is intentional: complexity that previously lived in the user interface now lives in the trigger implementation. Edge cases like unavailable states, undefined values, and attribute access are handled by the trigger's built-in logic rather than by the user. According to the official 2026.7 beta release notes, this means users no longer need to decide how each individual automation should handle unavailable sensors — the purpose-specific trigger handles those in the way that makes sense for its purpose by design.

This extensibility is also why integrations can now register their own triggers at the trigger-type level, not just at the entity level. An EV charger integration can expose "when charging complete" as a first-class trigger; a home energy monitor can expose "when electricity price is at today's lowest" as a condition. Neither was buildable in the previous model without custom templates.

Activity Feed Becomes a Timeline

Home Assistant's Activity page — previously called the Logbook — receives one of its biggest redesigns since the feature was introduced. The prior interface presented events as a flat chronological list of text entries that was accurate but required users to mentally reconstruct context: which automation caused this device state to change, and why did it fire at that time?

The 2026.7 redesign presents the same data as a vertical timeline with icons, color-coded state changes, and automatic context trimming. Device names and area labels are removed from individual entries when viewing an entity-specific timeline, because that information is already implied by the page the user is on. The more meaningful addition is causal attribution: user avatars appear next to manual actions, automations display the trigger that fired them, and integrations show their brand icon. A door that opened at 3:00 AM now shows whether it was opened manually, triggered by an automation, or reported by an integration — without requiring a separate click to find out.

What You Get on July 1

Home Assistant 2026.7 goes stable on Wednesday, July 1, 2026 at 4:00 PM ET. Users running Home Assistant OS, Supervised, or Container installations can update through Settings → Updates. The matter.js migration from the Python server happens automatically; no user action is required beyond the update itself.

A release party livestream will go live on the Home Assistant YouTube channel at 4:00 PM ET (20:00 GMT), featuring a walkthrough of the major changes and community Q&A. The beta is available now at rc.home-assistant.io for users who want to test ahead of the public release.

Beyond the headlining features, 2026.7 adds ten new integrations — including Dropbox for cloud backup storage — Raspberry Pi firmware updates from within Home Assistant, a faster frontend template engine, and a dedicated section in Settings for infrared and RF devices. The ZHA (Zigbee Home Automation) interface also received a visual overhaul. Several outdated integrations have been removed, including MS Teams (whose underlying Office 365 Connectors were discontinued by Microsoft on May 22, 2026) and UniFi LED (discontinued hardware with no remaining users).

Home Assistant 2026.7 is a project of the Open Home Foundation, an open-source organization that develops and stewards the Home Assistant platform. Nabu Casa, the commercial entity behind the Home Assistant Cloud subscription service, funds a substantial portion of core development.

Frequently Asked Questions

What is new in Home Assistant 2026.7?

Home Assistant 2026.7, releasing July 1, 2026, replaces the Python-based Matter server with matter.js (a TypeScript implementation that brings Matter 1.5.1 support and faster device reconnection), graduates purpose-specific automation triggers from opt-in Labs testing to the default experience for all users, adds Matter diagnostic sensors for device health monitoring, and rebuilds the Activity page as a navigable timeline. Ten new integrations, including Dropbox backup support, are also included.

How do the new purpose-specific automation triggers work, and do they break existing automations?

The new triggers let users describe automations in outcome terms — "when the back door opens," "when the office motion sensor detects movement" — rather than selecting entity IDs and state comparison types. Home Assistant handles the underlying entity model internally. Existing automations using generic triggers, templates, or YAML continue to work without changes; no migration is required. The new triggers are the new starting point for future automations, not a replacement for existing ones.

What does the matter.js migration mean for my Matter devices?

Matter Server app 9.0 replaces the previous Python server automatically when you update. Existing device pairings are migrated on first startup. The change brings faster device reconnection after server restarts, Matter 1.5.1 specification compliance, and a new security feature that checks certificate revocation during commissioning, preventing uncertified devices from joining your Matter network without explicit user approval. You do not need to recommission devices.

What are Matter diagnostic entities and how do I enable them?

Matter diagnostic entities expose device health data — Reboot Count, Uptime, Boot Reason, Hardware Faults, Radio Faults, and Network Faults — that was previously only available through downloaded JSON diagnostic files. They are disabled by default and must be enabled per-device through the Home Assistant Matter device settings. Once enabled, they appear on the dashboard and can be used in automations to alert you when a device is behaving unusually.