# Home Assistant 2026.8 separates devices by integration

Home Assistant 2026.8 now keeps one device entry per integration, so previously merged native-plus-Matter setups may show separate records while most automations keep working.

Canonical page: https://matterhome.io/news/home-assistant-2026-8-device-entries
Markdown page: https://matterhome.io/news/home-assistant-2026-8-device-entries.md
Author: Matterhome Editorial Team
Author profile: https://matterhome.io/authors/matterhome-editorial-team
Editorial lead: JC Martinez
Editor profile: https://matterhome.io/authors/jc-martinez
Published: 2026-08-07T02:08:56.000Z
Category: Platform update
Tags: Home Assistant, Matter, Smart home platforms

## Feature Image

- Origin: sourced
- Image: https://assets.matterhome.io/content/news/2026-08-07-home-assistant-2026-8-device-entries/feature.07ec9367039b8b45f0f0/source.webp
- Alt text: Home Assistant 2026.8 release graphic with integration logos branching from a tree
- Caption: Official Home Assistant 2026.8 release graphic. Matterhome has not tested the device-registry migration.
- Source: https://www.home-assistant.io/images/blog/2026-08/social.png

## Sources

- https://www.home-assistant.io/blog/2026/08/05/release-20268/
- https://developers.home-assistant.io/blog/2026/07/21/device-registry-single-config-entry/
- https://www.home-assistant.io/integrations/matter/

Home Assistant 2026.8, released on August 5, 2026, no longer merges device records across integrations. If the same physical accessory was previously represented by both a manufacturer integration and Matter, the update may now show two device entries, one for each path. Home Assistant does not name Matter as a special case, but a native-plus-Matter setup falls under its documented rule for one physical device connected through multiple integrations.

The old behavior could combine entities from several integrations on one device page while discarding conflicting details such as the model or serial number. Home Assistant now keeps those details separate for each integration. When the device registry loads after the update, it automatically separates previously merged devices and moves their entities to the matching entries.

Home Assistant says most people will not notice a change. Existing automations and scripts should keep working because actions that target the previous combined device are passed to the split entries. An affected setup may instead show what looks like a duplicate device or receive a Repair notification. Automations that store a device ID directly, unusual configurations, and custom integrations that work with the device registry deserve a closer check.

## Two entries can be the correct result

Do not delete or recommission an accessory only because it appears twice after the update. Open both entries and compare their integrations and entities first. Home Assistant's [Matter documentation](https://www.home-assistant.io/integrations/matter/) says a manufacturer integration can expose controls that the standardized Matter path does not. Separating those records does not create a second physical device, add another Matter fabric, or change the accessory's network connection.

Matterhome has not tested the migration. After updating, follow any Repair that Home Assistant presents and test automations tied to important jobs such as locks, heating, leak alerts, or lighting. If a device-ID-based automation behaves differently, rebuild that target against the entry or entities you intend to control. Custom integration developers have compatibility shims until Home Assistant Core 2027.8, but the developer notes describe them as best effort rather than a guarantee.

This is a Home Assistant platform change, not new Matter firmware or a new device feature. If you deliberately keep both a native integration and Matter, check which integration owns each entry and test important automations before removing either path.