Mixed-vendor smart homes are normal: Apple TV and HomePod minis on Thread, a Nest Wi-Fi Pro doing the same, maybe Home Assistant with a SkyConnect stick in the closet. Thread can unite them — until partition IDs split and you effectively run two invisible meshes that refuse to exchange routes.
Partition ID splits show up as brand-specific success. Nanoleaf works in Apple Home while an Eve plug on the same shelf answers only Google Home. Power-cycling random devices temporarily “merges” the house until the next hub reboot.
Understand what split means
Thread networks carry a partition identifier. Border routers that share credentials should align on that ID. When they do not — after partial resets, firmware mismatches, or importing the wrong dataset — routers politely ignore each other’s children.
This is not Wi-Fi SSID confusion. Your phone can be on perfect Wi-Fi while Thread children sit on the wrong partition.
Map your border routers
List every device that advertises Thread border routing: Apple hubs, Google hubs, Nest Wi-Fi, Home Assistant OTBR, select Echo models, etc. Note firmware versions and which app commissioned each Thread accessory.
Draw a rough floor plan and mark which hub is physically closest to failing devices. Split partitions often correlate with geography: each vendor’s hub became parent to nearby gear but never bridged datasets.
Healing without flattening the whole home
One maintenance window. Pick a quiet hour. Inform household members automations may flap.
Stop creating new partitions. Pause new commissioning until existing IDs align. Every new device during a split can anchor to the wrong side.
Sequential hub reboot. Router first, then border routers from the ecosystem that owns the most devices, then the others one at a time. Wait fifteen minutes between classes.
Dataset discipline. If you manually imported a Thread dataset into Home Assistant or another OTBR, verify it matches the Apple or Google operational data — not an old backup from a previous apartment.
Re-home edge devices only. Factory reset and recommission accessories that stay on the wrong partition, standing next to the hub you want as canonical. Mass-resetting every bulb is rarely necessary.
Ethernet where possible. Apple TV and Nest Wi-Fi Pro nodes with wired backhaul stabilize border router adjacency that wireless hops frustrate.
Mixed-vendor traps to avoid
Running beta OS on one hub and release on another sometimes splits partitions until all align.
Guest networks and AP client isolation prevent border routers from seeing each other even when Thread children look fine locally.
Chasing “Thread channel change” hacks without reading vendor docs can create a new partition instead of fixing the old one.
When to simplify architecture
If splits return monthly despite careful healing, designate one vendor as Thread owner and disable border routing on others if the platform allows. A simpler topology beats endless partition surgery.
Renters with ISP all-in-one routers may be unable to host multiple border router families — plan device brands accordingly.
Confirm partitions merged
Use manufacturer Thread diagnostics where available (Eve, Nanoleaf, and others expose parent info). After healing, accessories on opposite sides of the house should show parents on different hubs but remain reachable from a single primary app. Run cross-floor automations for forty-eight hours without No Response spikes.