How to Fix a Duplicate Matter Device Without Breaking the Working One
Start in Home Assistant's Matter device list, not with the factory-reset button. Go to Settings → Matter → Devices, open the accessory, and note its name, serial information, online state, and connected controllers under Manage fabrics. A fabric is the private relationship between one Matter controller—such as Home Assistant or Apple Home—and the accessory. The same physical accessory can correctly belong to several fabrics.
Next open the official Matter Server app's web interface and compare its nodes. A node is simply one accessory entry commissioned into that server. If it shows one online node but Home Assistant or Apple Home shows two tiles, the extra copy probably comes from another integration, HomeKit Bridge, or an orphaned entity. An entity is one Home Assistant control, such as a switch or battery reading. Deleting the physical device will not fix the source of that duplication.
If the server shows two nodes for the same physical accessory and one is offline, remove only the obsolete node through the current Matter device controls. If Apple Home alone shows two tiles, keep either its native Matter fabric or the copy exported by HomeKit Bridge—not both. Back up Home Assistant and photograph the device's setup code before changing any controller relationship.
First Identify Which Kind of Duplicate You Have
“Duplicate device” describes several different failures. The safe fix depends on where the extra copy exists.
| What you see | Most likely cause | Safest first action | Do not do yet |
|---|---|---|---|
| Two Apple Home tiles, one Matter node in Home Assistant | Apple has the native Matter accessory and a second copy exported by Home Assistant's HomeKit Bridge | Choose the Apple path you want, then exclude or remove only the other path | Do not reset the accessory |
| Two Home Assistant devices from different integrations | The same hardware is connected through Matter and a native vendor integration | Open each device and check the integration name; keep the path with the features and local behavior you want | Do not delete both integrations |
| Two Matter Server nodes with the same product or serial information; one is offline | The device was reset or re-added before its old node was removed | Confirm which node is online, move automations off the offline copy, then delete only the obsolete node | Do not remove the online node |
One Matter node but repeated entities, often ending in _2 or _3 | An entity-registry or integration issue, not two commissioned accessories | Update Home Assistant and Matter Server, restart once, then download diagnostics if the entries remain | Do not remove controller fabrics |
| An unavailable device returns after the Matter integration is reloaded | The old node still exists in Matter Server, so the integration recreates its Home Assistant record | Use the Matter Server node view to verify and remove the failed node through the supported UI | Do not edit .storage or the database |
| One device, but an automation runs twice | Two automations, triggers, or platform routines may be acting on the same entity | Trace the automation before removing hardware | Do not assume the Matter device is duplicated |
Clean Up Duplicate Matter Devices in This Order
1. Back Up and Record the Working Copy
Create a current backup at Settings → System → Backups. Store the backup emergency kit somewhere you can reach if the Home Assistant host fails. Then take screenshots of the working device page, its entities, area, and the automations that use it.
Photograph the Matter QR code or numeric setup code on the device or its paperwork. Home Assistant's official Matter documentation warns that you need that code if the accessory must be commissioned again. This matters most for installed switches, shades, thermostats, and locks whose labels may be hard to reach later.
2. Update the Supported Matter Path
Install the current stable Home Assistant Core, Companion app, and official Matter Server app before cleanup. Home Assistant moved the supported Matter path to Matter Server 9 and matter.js in June 2026, bringing faster recovery and a clearer device and network view. Home Assistant OS with the official Matter Server app remains the supported installation.
Do not use a duplicate as a reason to jump to a beta or paste storage-file cleanup commands. If the current stable version still creates repeat entities after one controlled restart, preserve the evidence and download diagnostics instead.
3. Compare the Device, Fabric, and Node Views
- In Home Assistant, open Settings → Matter → Devices and select the accessory.
- Next to Share device, open the three-dot menu and select Manage fabrics. Record the controller names.
- Open Settings → Apps → Matter Server → Open Web UI and compare the node list. Look for one online node and any offline node with matching product or serial information.
- On an iPhone or iPad, open Settings → General → Matter Accessories. Apple shows the serial number and connected services for each saved accessory.
- In Google Home, open the device and check Linked Matter apps & services when Google is one of the controllers.
Thread is not another copy of the device. Thread is the low-power network used by some Matter accessories. A Thread border router carries their local IPv6 traffic; it does not create a second Home Assistant entity by itself.
4. If the Extra Copy Is a Controller Fabric
Use the accessory's Manage fabrics view and remove only the controller you no longer want. If you want to remove Home Assistant's own Matter copy, the official Matter instructions direct you to the device's three-dot menu and Delete. Then confirm the accessory still works from the controller you intended to keep before cleaning anything else.
Apple provides three different removal scopes: Keychain only, one connected service, or every connected service. Choose the individual service when that is your target. Remove From All Services removes control from every associated app on the iPhone or iPad and is the wrong first response to one duplicate tile.
5. If Apple Home Has a Native and a Bridged Copy
Native Matter multi-admin and Home Assistant's HomeKit Bridge are separate paths. Native Matter gives Apple Home its own controller relationship with the accessory. HomeKit Bridge exports a Home Assistant entity to Apple Home over the local network. If you enable both, Apple can display the same physical plug, light, or thermostat twice.
- Keep native Matter in Apple Home when you want Apple to control the accessory independently of Home Assistant. Exclude that Home Assistant entity from the HomeKit Bridge filter.
- Keep the HomeKit Bridge copy when Home Assistant is the one automation brain and Apple is mainly a front end. Remove only Apple's native Matter service for that accessory. The bridged tile then depends on Home Assistant remaining online.
Do not delete the entire HomeKit Bridge just to remove one ordinary accessory. Home Assistant supports include and exclude filters so one entity can be left out while the rest of the bridge remains paired.
6. If Home Assistant Has Matter and a Native Integration
Open both device pages and look under Device info for the integration name. A vendor's native integration and Matter can each create a valid Home Assistant representation of the same hardware. That is not multi-admin; it is two Home Assistant integrations.
Prefer a well-supported local native integration when it exposes useful features Matter omits. Home Assistant's Matter documentation uses Philips Hue as the example: the native local Hue integration provides richer scenes and entertainment features than the bridge's basic Matter controls. Prefer Matter when its common local controls and cross-platform sharing are the better fit. If the native integration depends on a vendor cloud, decide whether its extra features justify that internet and account dependency before removing the local Matter path.
7. If Matter Server Shows an Old Offline Node
An offline node can remain when a device is factory-reset and commissioned again before the old entry is removed. A Home Assistant Community troubleshooting thread documents this stale-node pattern: the new copy works while the old one returns as an unavailable device.
Match the product and serial information, verify the current node responds, and remove only the offline obsolete node through the current Matter UI. After cleanup, restart the Matter Server app once and recheck entity names and automations. If the UI will not offer a supported delete action, stop there. Download device and integration diagnostics from the Matter integration and file a current issue; do not manually delete database or .storage records.
8. If There Is One Node but Several Entities
Leave the device and its fabrics alone. A Home Assistant entity is a software control, not another commissioned Matter accessory. Update, restart once, and check whether the extra entity is now unavailable and removable. If it is still actively supplied by the integration, deleting its registry entry will not solve the source—it can return on the next reload.
Download diagnostics before renaming or disabling the repeats. They contain the device's cluster and network information with sensitive data redacted. Include the exact Home Assistant and Matter Server versions when reporting the problem.
9. Repair Automations Before Removing the Last Reference
Move dashboards, scenes, and automations to the working entity before deleting the duplicate. If the old entity is switch.lamp and the working copy is switch.lamp_2, decide which name you want to keep and update every reference deliberately. A cleanup that leaves the room dark at sunset is not finished.
If there is only one Matter device and one set of entities, use Home Assistant's automation traces instead. The separate guide to an automation that runs twice covers duplicate triggers and overlapping routines.
10. Factory-Reset Only as the Last Step
Reset only when the accessory itself is stuck, the supported removal controls cannot repair it, and you are ready to commission it again. Remove obsolete controller entries first when possible, keep the setup code nearby, then follow the manufacturer's exact reset procedure. Add the accessory to one chosen Matter controller and share it to other platforms with fresh temporary codes.
For locks, garage doors, alarms, thermostats, hardwired controls, and motorized shades, keep a manual control path and physical access throughout the repair. Never make a working access or HVAC controller the first test device.
Which Control Path Should You Keep?
| Control path | Official support | Local control | Cloud or account dependency | Matter or HomeKit role | Main caveat |
|---|---|---|---|---|---|
| Home Assistant OS + official Matter Server | Home Assistant's supported Matter installation | Normal device commands stay inside the home and can work without internet | No vendor cloud is required for normal Matter control | Home Assistant is a native Matter controller with its own fabric | Matter may expose fewer brand-specific features than a native integration |
| Apple Home as another Matter controller | Apple-supported Matter multi-admin path | In-home Matter control is local through compatible Apple or third-party infrastructure | Apple Account, iCloud Keychain, Siri, remote access, and some setup features use Apple services | Apple owns a separate Matter fabric; this is not HomeKit Bridge | Apple can show two tiles if Home Assistant also exports the entity through HomeKit Bridge |
| Home Assistant HomeKit Bridge | Official Home Assistant integration | Home Assistant exports supported entities to Apple Home across the local network | The bridge path needs Home Assistant online; Apple remote and voice services have their own account and hub requirements | HomeKit bridge, not Matter multi-admin | A bridged entity can duplicate the same accessory's native Apple Matter tile |
| Native vendor integration in Home Assistant | Varies by integration; check its Home Assistant documentation | May be fully local, locally polled, or cloud-polled | Varies; some require a vendor login or internet | Not automatically a Matter fabric or HomeKit path | Often richer features, but it can create a second Home Assistant device beside Matter |
What Not to Do
- Do not remove every Matter service when only one controller or bridge path is unwanted.
- Do not factory-reset first. That can leave the old controller node behind and create the very duplicate you are trying to remove.
- Do not delete
.storage, registry, or database files by hand. Preserve diagnostics and use supported controls. - Do not assume two tiles mean two Thread networks. Check nodes, fabrics, and integrations separately.
- Do not remove a lock, thermostat, or shade controller without a manual fallback and a plan to restore its automations.
Tara's Practical Recommendation
Give every important accessory one documented source of truth inside Home Assistant. If Apple Home is also needed, choose either native Matter multi-admin for independent Apple control or HomeKit Bridge for a Home-Assistant-first design. Do not expose the same accessory both ways without a specific reason.
Label the chosen integration, controller, Thread border router when relevant, setup-code location, and automation owner during handoff. That small record turns a future “ghost device” from a whole-house reset into a five-minute cleanup.
FAQ
Will deleting a Matter device from Home Assistant remove it from Apple Home?
Matter controllers normally use separate fabrics. Confirm them under Manage fabrics, remove only the unwanted controller, and test the Apple Home copy before doing more. Avoid Apple's Remove From All Services option unless removing every connected service is truly the goal.
Why does the duplicate return after Home Assistant restarts?
An old offline Matter node, a second integration, or HomeKit Bridge may recreate the visible copy. Compare the Matter Server node list with Home Assistant's devices. One node with two Home Assistant entries points to an entity or integration problem; two nodes for the same physical accessory point to an obsolete node.
Can Home Assistant merge duplicate Matter devices?
There is no general merge action that safely removes an extra Matter fabric, node, or integration. Move automations to the working entities, then remove the narrow duplicate at its source. Combining names in the dashboard would only hide the underlying second path.
Why is the device duplicated only in Apple Home?
The common cause is one native Matter tile plus the same Home Assistant entity exported through HomeKit Bridge. Keep native Matter and exclude the bridged entity, or keep the bridge copy and remove only Apple's native Matter service for that accessory.
Can a Thread border router create duplicate devices?
Not by itself. A Thread border router routes local IPv6 traffic between a Thread mesh and the home network. Duplicate tiles usually come from two controller fabrics, two integrations, a bridge, or stale Home Assistant records.
Should I factory-reset a duplicate Matter device?
Reset last. Back up Home Assistant, save the setup code, identify the online node and connected fabrics, remove only the obsolete copy, and retest. Reset only if the physical accessory remains stuck and you are ready to commission it again.
Related Tara Reading
- Share one Matter device across several platforms correctly
- Choose HomeKit Device or HomeKit Bridge in Home Assistant
- Clear a stale Matter fabric when a device will not re-add
- Choose which Matter controller should pair first
- Back up and restore Home Assistant safely
- Trace a Home Assistant automation that runs twice