Home Assistant 2026.9, titled “There’s room on this bus,” was released on September 2, 2026. The release includes practical changes around Modbus setup, voice processing, dashboards, device management, and network visibility.
These changes affect local device setup, automation troubleshooting, voice-workflow choices, and day-to-day management as a Home Assistant installation grows.
What Changed in Home Assistant 2026.9?
The changes most relevant to everyday administration include the following. Full technical details are available in the official Home Assistant 2026.9 release notes:
- Modbus device setup is becoming easier for integrations that already know how a device communicates, including more configuration through the user interface.
- Home Assistant Cloud is testing a new speech-to-text engine through Labs for Cloud subscribers; the feature is experimental and may not become permanent.
- Security, History, and Activity improvements make it easier to see device state and understand why a change occurred.
- A Matter network map provides a clearer view of the Matter side of a smart-home installation.
- Additional integrations and interface improvements continue to reduce the amount of manual administration required as a Home Assistant installation grows.
Why the Modbus Changes Matter for Local Automation
Modbus is common in energy meters, solar equipment, heat pumps, building controls, and other local devices. The difficult part is often not the automation itself. It is describing registers, connections, and device behavior accurately enough for Home Assistant to use them reliably.
The 2026.9 direction makes that setup more approachable for supported integrations. It can reduce the amount of hand-written configuration required before a local device becomes useful in dashboards and automations.
This does not mean that every Modbus device becomes plug-and-play. Users still need the correct device documentation, network access, register definitions, and a safe way to validate readings before using them in an automation.
What the Voice Updates Mean for Local Smart Homes
Home Assistant 2026.9 is testing a new speech-to-text engine for Home Assistant Cloud through Labs. This is a Cloud subscriber feature being evaluated through the Labs program, rather than a new generally available local speech-processing engine. Home Assistant also notes that Labs features are experimental and may change or may not become permanent features.
For users evaluating voice workflows, the update is useful as a sign of continued experimentation around speech processing, but it should not yet be treated as a permanent architectural change. Before enabling a cloud path, consider whether voice data leaves the home, what happens when the internet is unavailable, and which actions are allowed after a voice request.
For privacy-conscious households, the useful question is not simply whether voice control is available. The better question is which parts of the workflow remain local, which services are involved, and whether the resulting behavior is understandable and controllable.
Device Management and Dashboard Improvements
As a Home Assistant installation grows, reliability depends on observability as much as on the number of integrations. A dashboard should help a user see the current state, while the Activity and History views should help explain what happened.
The new Matter network map is useful for users who need to reason about Matter devices, network relationships, and the role of Thread infrastructure. It should be treated as a troubleshooting and orientation tool, not as proof that every device has the same protocol or control path.
These changes are especially useful in homes that combine sensors, dashboards, MQTT devices, local automations, and more than one smart-home protocol.
What This Means for LinknLink Users
Home Assistant 2026.9 did not introduce special LinknLink-specific support. LinknLink devices should continue to be evaluated through their documented integration path and the configuration already used in the home.
For example, an existing Home Assistant workflow may use:
- eMotion Air, eMotion Pro, or eMotion Ultra for supported presence and environmental sensing workflows.
- eRemote HA for supported IR control workflows.
- eHome HA for supported RF control workflows.
- The LinknLink App feature workflow when the configured devices and services are supported by the user’s setup.
The release is therefore best understood as a Home Assistant platform update around an existing device architecture. It does not remove the need to verify MQTT topics, entity availability, permissions, network paths, or product-specific capabilities.
When comparing related device paths, use the local AI gateway guide, the mmWave presence sensor guide, and the IR and RF remote-control guide to check the configuration path that fits your installation.
Should You Upgrade Immediately?
There is no single answer for every installation. A sensible upgrade decision depends on how critical the home is, how many integrations are installed, and whether the system has a recovery plan.
Before upgrading:
- Create and verify a recent backup.
- Read the official release notes and check the integrations used by the home.
- Record important automation behavior and dashboard views.
- Choose a maintenance window if the system controls heating, access, energy, or other important routines.
What to Check After Updating
- Confirm that critical integrations load without errors.
- Check that automations, scenes, and scripts still run as expected.
- Verify dashboard cards, device availability, and recent state history.
- Check MQTT devices and confirm that expected entities remain available.
- Confirm local device control before relying on an automation.
- Review voice workflows and the network services they use.
- Look at Activity and History when a device behaves differently than expected.
Frequently Asked Questions
What is new in Home Assistant 2026.9?
Home Assistant 2026.9 focuses on practical platform improvements, including easier setup for supported Modbus integrations, testing of a new speech-to-text engine for Home Assistant Cloud through Labs, dashboard and activity improvements, and a Matter network map.
The voice engine is an experimental Cloud subscriber feature being evaluated through Labs. It may change or may not become a permanent feature, so it should not be treated as a generally available local voice engine.
Does Home Assistant 2026.9 improve local control?
Some changes can make local device administration easier, but there is no universal local-control switch. The result still depends on the integration, network path, device, and automation configuration.
Do I need to reconfigure MQTT devices after upgrading?
There is no blanket requirement to reconfigure every MQTT device. Confirm that the integration loads, expected entities are available, and important automations still receive the correct state changes.
Should I update Home Assistant immediately?
Update after creating a verified backup and checking the integrations that matter to your home. A maintenance window is sensible when Home Assistant controls important routines.
Does Home Assistant 2026.9 add a special LinknLink integration?
No special LinknLink-specific integration was introduced solely by this release. Use the documented Home Assistant, MQTT, IR, RF, and App paths that apply to the configured product and installation.
Final Thoughts
The most useful part of Home Assistant 2026.9 is not simply the number of changes. It is the continued improvement of the local smart-home workflow: configuring devices, understanding state changes, navigating multiple protocols, and keeping everyday automations manageable.
That makes the release worth evaluating for existing Home Assistant users, while still leaving the final upgrade decision with the person responsible for the home.