Duplicate Smart-Home Devices: Remove the Extra Integration Path, Not the Physical Device

One physical device can have several software identities

Duplicate smart-home devices can appear when bridge and native integrations expose the same hardware. Trace the direction of each route and its automation references before deleting entities, then verify state feedback and real triggers through the retained path.

A Reddit Google Home user reported duplicate devices after pairing Matter equipment while manufacturer apps were also linked. That is a concrete example of one device arriving through two routes. It does not mean every pair of similar tiles is redundant: a device can legitimately expose several different functions.

Distinguish duplicate representations, intentionally separate capabilities, and stale records from replaced hardware. A temperature sensor and a thermostat control may legitimately appear as different functions. Deleting by friendly name alone can remove something an automation still needs.

Source: Google Home owner sees duplicate Matter devices through linked manufacturer apps

Map the direction of each bridge

Home Assistant’s HomeKit Device integration brings a HomeKit accessory into Home Assistant. HomeKit Bridge exposes selected Home Assistant entities to Apple Home. These directions are different. Record the source of each representation before changing either path.

Choose a primary representation for ordinary control and document any deliberate secondary integration needed for extra features. Use supported filtering and configuration rather than editing internal databases or repeatedly resetting the accessory.

Source: HomeKit Bridge - Home Assistant · HomeKit Device - Home Assistant

Check a linked service alongside Matter

Google documents deduplication between a manufacturer’s cloud integration and Matter using matching identifiers supplied by the integration. If those identities are not properly associated, the owner can encounter separate representations. A Matter device added directly and the same hardware exposed through a linked app should therefore be traced before either is removed.

On October 4, 2026, Google’s deduplication page still listed an iOS issue and Android-only deduplication support. The page’s last-updated stamp is April 18, 2023, so check the limitation against the installed app version. Compare the view on a supported Android device before deleting a tile; the warning concerns deduplication, not all Matter functions on iOS.

Use the platform’s supported controls to inspect the integration or linked service for each tile. An equivalent inventory question applies in Alexa: whether a manufacturer skill and a Matter connection both expose the device. Do not assume unlinking a manufacturer account removes only the unwanted tile; review the other devices and routines that depend on that account.

Source: Google Home Developers: Cloud-to-Cloud and Matter Device Deduplication

Illustrative scenario: one lamp, two tiles

Imagine a lamp reaches Apple Home directly and also arrives through an automation bridge. Both tiles operate the same lamp, but routines reference different copies. Removing one tile without tracing those references can leave a bedtime scene partly broken.

Inventory scenes, automations, dashboards, and voice names first. Move required references to the retained path, test them, then remove or hide the redundant exposure using supported controls. Keep a rollback record until the household’s normal routines have been exercised.

Source: HomeKit Bridge - Home Assistant · HomeKit Device - Home Assistant

Verify identity through normal operation

Test a physical change at the device and confirm the retained representation updates correctly. Then test commands from the intended control surfaces and a controller restart. A clean tile count does not establish that state feedback or automations survived.

Record the integration path beside the device inventory. That small piece of documentation prevents future troubleshooting from re-adding the same accessory through another route and recreating the confusion.

Source: HomeKit Bridge - Home Assistant · HomeKit Device - Home Assistant

Put it into practice

A decision table to keep handy