A HomePod Mini, by default, acts as a Thread border router for your HomeKit setup. This means Thread accessories (like the Eve Energy or Nanoleaf Essentials over Thread) can route their traffic through the HomePod to reach your network. When this works, it is invisible. When it does not work, your Thread devices appear in HomeKit but respond slowly or intermittently, and you have no clear indicator that Thread border routing is the actual problem.
Confirm the HomePod is meant to be a Thread router
Only the HomePod Mini and the second-generation HomePod include Thread radios. The original HomePod (full-size, first generation) does not. If you only have a first-gen HomePod, you do not have a Thread border router from Apple at all, and your Thread devices need a different border router source (Apple TV 4K from 2022 onward, Eero, or Google Nest Hub second generation).
To verify your specific device, open the Home app, go to Home Settings, then Hubs & Bridges. Each Thread-capable device shows a Thread status. If your HomePod Mini is listed and shows “Connected” under Thread, it is supposed to be advertising as a border router. If it shows “Not Connected” or is missing the Thread field entirely, you have your first symptom.
The three common reasons the HomePod does not advertise
- The HomePod is not on the same network segment as the rest of your HomeKit devices
- The HomePod’s HomeKit residence is set to a different home
- The HomePod is part of a stereo pair, and only one of the two acts as the router (sometimes neither, due to a quirk)
Same network segment
Thread border router advertisements use mDNS, which does not cross VLANs without explicit configuration. If your HomePod is on the main Wi-Fi network and your iPhone (where you check HomeKit) is on a guest network, you may see the HomePod in HomeKit but the Thread advertisement may not reach the rest of your Thread devices.
The fix is to make sure all your HomeKit devices share the same network segment. If you maintain a separate IoT VLAN, the HomePod should be on the IoT VLAN with your other Thread accessories, and mDNS reflection or repetition should be enabled between the main LAN and the IoT VLAN.
HomeKit residence
If you have multiple HomeKit homes (a primary home and a vacation home, for example) and your HomePod is set up in the wrong home, it will not act as a border router for the home you are looking at. Verify in the Home app under Home Settings, People, that the HomePod is assigned to the right home and not duplicated across both.
If you find a duplicate, remove the HomePod from the wrong home through the Home app on the HomePod’s owner account. This is one of those weird scenarios that often only the original setup user can fix.
Stereo pairs
When two HomePod Minis are paired as a stereo pair, only one of them is supposed to be the active Thread border router. The other is on standby. Sometimes the standby HomePod is selected as the active border router and then loses its routing because of the stereo pair’s playback prioritization. Symptom: Thread devices that worked yesterday are slow today, even though both HomePods are healthy.
The cleanest fix is to temporarily unpair the stereo pair, confirm one HomePod is acting as the router, and only then re-pair them. After re-pairing, that HomePod usually remains the active border router for the long term. Unpairing is done in the Home app on the HomePod’s settings page.
Restart the HomePod
If the basic configuration looks right and the HomePod still does not advertise, an Apple-style restart often works. Unplug the HomePod for thirty seconds, then plug it back in. The Thread radio re-initializes during boot and re-advertises. Allow about five minutes after restart for Thread devices to find the new advertisement and re-bind.
Check for competing border routers
If you have an Eero router that supports Thread, an Apple TV 4K (2022 or later), or a Google Nest Hub (2nd gen) all on the same network, you have multiple border routers competing for advertisement. Thread is designed to support multiple border routers, but practical behavior varies. The active border router can shift between devices in ways that confuse weakly-implemented Thread accessories.
If you have multiple potential border routers, the cleanest setup is to keep them all online and accept some routing variability. Disabling the border router function on individual devices is possible on Eero (disable Thread in settings) and on Google Nest Hub (no Thread toggle, but its border router is only used for Google Home Thread devices, not for HomeKit). On Apple devices, there is no way to disable the border router; it is always on when present.
When the HomePod itself has failed
A small number of HomePod Minis have had hardware Thread radio failures, usually presenting as: HomePod is online, plays audio normally, appears in HomeKit, but the Thread status is permanently “Not Connected”. A factory reset of the HomePod sometimes resolves this. If it does not, Apple replacement is the only path.
To factory reset the HomePod Mini: long-press the top of the HomePod, follow the audible prompts, and confirm the reset. After reset, set it up fresh in your home.
Realistic expectations for Thread
Thread is newer than Wi-Fi or Zigbee and the ecosystem is still maturing. Some Thread devices are flaky regardless of border router quality. If a single Thread accessory is unreliable but others on the same network are fine, the accessory is probably the issue, not the border router.
The diagnostic that takes 60 seconds
When a Thread accessory is misbehaving, the fastest test of whether your border router is the issue is to physically move the accessory next to the HomePod for thirty seconds. If it suddenly becomes responsive, your accessory’s location is too far from any Thread router, not just the border router. If it stays unresponsive even at three feet from the HomePod, the border router pairing is the issue.
This 60-second test saves hours of router-side diagnostics. For the broader picture of how Thread interacts with the rest of your smart home, our Thread pairing guide covers the commissioning path that creates these issues in the first place.
