A Matter accessory that suddenly looks standalone in Home Assistant 2026.8.0 or 2026.8.1 should not be deleted as cleanup. Core 2026.8.2, released on August 14, 2026, fixes the regression that removed some devices' Connected via link and hid them from their Matter bridge's device page, even though the Matter Server could still show the correct endpoint tree.
The problem started with Core 2026.8.0 and was limited to composed bridged devices. These accessories expose several Matter endpoints but appear as one device in Home Assistant. The fix uses a Philips Hue motion sensor behind a Hue hub as its code example; the original report also showed a Venetian blind and thermostat variants. Bridged accessories represented by a single endpoint were not affected.
The missing relationship was more than an organization problem. Home Assistant normally prevents a bridged child from being deleted on its own. According to the merged fix, losing the bridge link bypassed that protection, so deleting an affected child from the interface could remove the whole bridge from the Matter fabric.
Update before removing a bridged device
If a bridged accessory became a standalone-looking device after Core 2026.8.0 or 2026.8.1, update to 2026.8.2 before deleting or recommissioning anything. Restart Home Assistant, open the bridge's device page, and check that the child has returned under Connected devices and again names the bridge under Connected via.
No migration or accessory firmware update is required for this repair. Home Assistant recalculates the relationship during setup, so the first restart on 2026.8.2 should restore it. If the child still appears detached after that restart, leave it in place and report the bridge model, child model, Core version, Matter Server version, and diagnostics to Home Assistant rather than removing the device as a cleanup step.
Content feedback
Spot a mistake or missing context?
Send a quick note so it can be checked against the source material.