|

Troubleshooting Matter Device Won’t Pair Multi Admin

ByAlex Turner

When a Matter device refuses to pair with a second controller in a multi-admin setup, the problem is almost never the device itself. It’s the commissioning flow — specifically, how the second controller tries to add a device that’s already bound to the first platform.

Matter’s multi-admin feature is supposed to make this seamless. In practice, the most common failure point is a stale or incomplete commissioning window left open by the first controller. Here’s how to diagnose and fix it without factory-resetting everything.

What Actually Breaks in Multi-Admin Pairing

Matter devices don’t “broadcast” like Bluetooth speakers. They open a commissioning window — a short, encrypted time slot during which a controller can add the device to its fabric. In a multi-admin setup, each controller (Apple Home, Google Home, Alexa, SmartThings, etc.) maintains its own fabric. The device joins each fabric separately.

The failure mode you’re likely hitting:

1. Controller A (say, Apple Home) pairs the device successfully.

2. You open Controller B (say, Google Home) and tap “Add Matter device.”

3. Controller B sends a commissioning request to the device.

4. The device rejects it because the commissioning window isn’t open — or it’s open on the wrong port.

Matter uses UDP port 5540 for commissioning by default. If your router or the device’s firmware blocks or misroutes that port, the second controller never “sees” the device, even though the first controller works fine.

The commissioning window isn’t a single global state. Each controller opens a window on the device independently, and the device can only honor one active window at a time. If Controller A’s window is still technically open when you try to pair with Controller B, the device may reject the second request. This is why closing the first window before opening a new one matters.

Pre-Flight Checklist (2 Minutes)

Before you reset anything, run through these checks. They resolve about 40% of multi-admin pairing failures:

Check What to Look For Why It Matters
Device firmware Is it updated to the latest version? Early Matter devices (2022–2023) had buggy multi-admin implementations.
Controller firmware Is the second controller’s app updated? Google Home and Alexa shipped multi-admin support in stages.
Phone/tablet Are you using the same phone for both pairings? Some controllers cache device state per-phone.
Network Is the device on the same 2.4 GHz network as the phone? Matter commissioning requires local network access. Guest networks and VLANs block it.
Thread border router If it’s a Thread device, is the border router online? A dead border router makes the device unreachable for re-commissioning.

Early checkpoint: If the device appears in Controller A but not in Controller B’s “nearby devices” list, the commissioning window is almost certainly closed or blocked. Don’t factory-reset yet.

Ordered Fix: Re-Open the Commissioning Window

This is the single most effective fix for multi-admin pairing failures. You don’t need to remove the device from Controller A — you just need to open a fresh commissioning window from the controller that already has the device.

Step 1: Open the Matter Commissioning Window from Controller A

The exact path varies by platform:

  • Apple Home: Open the Home app → tap the device → tap the gear icon → scroll to “Matter Accessories” → tap “Turn On Pairing Mode.” This opens a QR code and a manual pairing code.
  • Google Home: Open the Google Home app → tap the device → tap the gear icon → tap “Matter” → tap “Enable pairing mode.”
  • Alexa: Open the Alexa app → tap Devices → select the device → tap the gear icon → tap “Matter” → tap “Enable pairing mode.”
  • SmartThings: Open the SmartThings app → tap the device → tap the three-dot menu → tap “Matter” → tap “Enable pairing mode.”

Common mistake: Users tap “Remove Device” instead of “Enable Pairing Mode.” That’s a different action — it removes the device from the fabric entirely, which forces a full re-pair.

Step 2: Wait 10–15 Seconds

The commissioning window stays open for about 15 minutes by default, but the device needs a few seconds to broadcast its presence. Don’t rush to the second controller immediately.

Step 3: Pair from Controller B

Open Controller B’s app and start the Matter pairing flow. Use the QR code or manual pairing code displayed in Step 1 — not the original code from the device’s box. The original code may still work, but the freshly generated code is tied to the current commissioning session and is more reliable.

Step 4: Verify Multi-Admin Status

Once paired, check that the device appears in both controllers. Then test control from both platforms. If the device responds from both, you’re done.

Success signal: The device appears in both controllers’ apps and responds to commands from each within 5 seconds.

If the Commissioning Window Fix Fails

If re-opening the window doesn’t work, the problem is likely one of these three things:

1. Port 5540 Is Blocked

Matter commissioning uses UDP port 5540. Some routers, especially those with “AI” or “smart” security features, block this port by default. Check your router’s firewall logs or temporarily disable the security feature to test.

How to detect it early: If Controller A pairs fine but Controller B consistently fails at the “searching for device” stage, and you’ve confirmed the commissioning window is open, suspect port blocking.

Some routers also block mDNS (multicast DNS) traffic, which Matter uses for device discovery during commissioning. If port 5540 is open but discovery still fails, check whether your router has an “IGMP snooping” or “multicast filtering” setting that might be interfering. This is especially common on mesh router systems with band steering enabled.

2. The Device Has a Stale Fabric

If the device was previously paired to a controller that was factory-reset or removed without proper unpairing, it may have a stale fabric entry that confuses new commissioning attempts. This is more common with Thread devices.

Fix: Remove the device from all controllers, then factory-reset the device and pair it fresh to Controller A first. Then add Controller B.

3. The Second Controller Doesn’t Support Multi-Admin for That Device Type

Not all Matter device types are equally supported across platforms. For example, some robot vacuums and air purifiers have limited multi-admin support even though they’re Matter-certified.

Check: Look up the device’s Matter certification details. The CSA (Connectivity Standards Alliance) maintains a certification database. If the device is certified for Matter 1.0 but the second controller requires 1.2 features, you’ll hit a wall.

The Matter 1.2 specification added support for more device types, but controllers must update their software to recognize them. A controller running an older Matter stack may silently reject a device type it doesn’t recognize, rather than showing a clear error message.

When the Second Controller Still Won’t See the Device

You’ve opened the window, waited, and tried pairing — but Controller B still shows “No devices found.” Here’s how to branch your next move based on what you’re seeing:

If Controller B shows “Searching” indefinitely: The commissioning window is likely open, but mDNS discovery is being blocked. Check your router’s multicast settings first. Temporarily disable band steering or “smart connect” features that might be pushing your phone to a different band than the device. If the device is Thread-based, confirm the border router is online and updated — a border router running outdated firmware can advertise the device but fail to route commissioning traffic.

If Controller B shows “Device found but pairing failed”: The device is being discovered, which means mDNS and port 5540 are working. The failure is happening during the secure handshake. This usually points to a stale fabric entry or a controller that doesn’t fully support the device type. Try removing the device from Controller A entirely, then re-pairing it fresh to Controller A, and immediately attempting the multi-admin add from Controller B.

If Controller B shows an error code like “0x2A” or “FAILURE” without context: This is a generic Matter error that often means the device rejected the commissioning request because another window was active. Go back to Controller A, confirm the pairing mode is still on, and try again. If it fails a second time, close the window, wait 30 seconds, and reopen it.

Expert Tips for Multi-Admin Pairing

Tip 1: Always generate a fresh pairing code from the first controller. The code printed on the device is a one-time entry point. Once the device is on a fabric, that code may not work for additional fabrics. Use the in-app “Enable Pairing Mode” option to generate a new code. Mistake to avoid: Scanning the original QR code from the device’s box when the device is already paired — this fails more often than it succeeds.

Tip 2: Pair the second controller within 5 minutes of opening the window. While the window technically stays open for 15 minutes, some devices (especially Thread end devices) go to sleep and become unresponsive after 5–10 minutes. If the device is battery-powered, this is almost always the culprit. Mistake to avoid: Opening the window, getting distracted, and trying to pair 20 minutes later.

Tip 3: Use the same network for the phone and the device during commissioning. Matter commissioning requires the phone to communicate with the device over the local network. If your phone is on 5 GHz and the device is on 2.4 GHz, some routers block the cross-band communication. Mistake to avoid: Assuming “same Wi-Fi network” means “same band” — it doesn’t. Check your router’s settings to confirm both bands are on the same subnet.

Tip 4: If you’re using Home Assistant, specify which integration you’re on. The troubleshooting path differs between ZHA, Zigbee2MQTT, and the Matter server add-on. For Matter specifically, check that the Matter server add-on is running the latest version and that the device isn’t already claimed by another integration. Mistake to avoid: Assuming the Matter server add-on handles multi-admin automatically — it doesn’t. You may need to manually open a commissioning window from the first controller before adding the device to Home Assistant.

When to Factory Reset (Last Resort)

Factory reset is the nuclear option. Only do this if:

  • The device fails to pair with any controller after a fresh commissioning window.
  • The device is stuck in a partial pairing state (shows in one controller but not another, and re-opening the window doesn’t help).
  • You’ve confirmed the network and port are not the issue.

Before you reset: Document which controllers have the device. After the reset, pair it to your primary controller first, then add the secondary. This order matters — pairing to the secondary first can cause the same multi-admin failure to recur.

Some devices require a specific reset sequence (e.g., holding a button for 10 seconds vs. 5 seconds). Check the device’s manual. A partial reset — where the device reboots but doesn’t clear its fabric state — can leave the device in a worse state than before, with stale fabric entries that block all future pairing attempts.

Closing Thoughts on Multi-Admin Pairing

Multi-admin pairing failures are almost always a commissioning-window problem, not a device defect. Re-opening the window from the controller that already has the device resolves the majority of cases. If that fails, check port 5540, verify the second controller’s device-type support, and only then consider a factory reset.

The key habit to build: always generate a fresh pairing code from the first controller when adding a second one. It takes 30 seconds and eliminates the most common failure point. If you’re still stuck after working through these steps, check the CSA certification database for your specific device model and the second controller’s platform documentation for known multi-admin limitations.

<!– cluster-navigation –>

Explore This Topic

Related guides in this cluster:

Similar Posts