Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.
waidis
User level: Level 1 (5 points)

Apple TV 4K Thread Border Router not advertising service after tvOS 27.2.

Suspected Thread Border Router failure after tvOS 27.2



My Apple TV 4K 2nd generation (A2169) automatically updated to tvOS 27.2. All 10 Matter devices previously worked normally, but I subsequently discovered that all were offline in both Apple Home and Home Assistant.

The Apple TV remains connected as a Home hub, and AirPlay/mDNS services are discoverable.

However, the Thread Border Router service _meshcop._udp.local is no longer discoverable from macOS or Home Assistant.


Troubleshooting already completed:

  • Cold-restarted the Apple TV.
  • Switched from Ethernet to Wi-Fi.
  • Confirmed devices are on the same VLAN.
  • Checked UniFi multicast settings.
  • Confirmed Apple TV's IPv4 and IPv6 mDNS traffic with tcpdump.
  • Confirmed the Matter Server is running.



The Apple TV appears not to be advertising its Thread Border Router service following the update.

Could this be a tvOS 27.2 Thread initialization or network-attachment regression? Is there a way to restart or recover the Thread subsystem without factory-resetting the Apple TV or losing the existing Thread network credentials?

Posted on Oct 29, 2026 1:53 PM

1 reply

heliokanat
User level: Level 2 (354 points)

Nov 7, 2026 10:59 AM in response to waidis

There is no switch to restart just the Thread stack in tvOS, but there are two recoveries short of a reset that specifically rebuild it, and your Thread credentials are not at risk in either: the network dataset for an Apple home lives in iCloud Keychain, not only on this box.


1. Full hub power sequencing. Unplug every home hub in the house (all HomePods and Apple TVs, not just this one) for about two minutes, then power up ONLY this Apple TV and give it a good five minutes alone before plugging the rest back in. A cold restart of the Apple TV while the other hubs stay up lets them hold the home's state; powering everything down forces re-election and a fresh Thread attachment when this one comes up first.


2. iCloud sign out and back in on the Apple TV (Settings > Users and Accounts > your name). This forces the home configuration and Thread credentials to re-sync from iCloud, and it is the known recovery when a hub's Thread stack does not initialize after an OS update. The network dataset re-downloads, so your Matter devices should rejoin the same network rather than needing to be re-commissioned.

One discriminator before you do either, since you run Home Assistant: Settings > Devices and Services > Thread lists the border routers Home Assistant can see and their datasets. If this Apple TV appears there with a dataset, its Thread radio is up and the break is in advertisement toward the rest of the network. If it does not appear at all, Thread never started on the box, which points at step 2.


Also worth one quick check on the UniFi side even with multicast reviewed: the border router advertises its service as _meshcop._udp. If your discovery app sees that service only when the checking device is on the same access point as the Apple TV, the traffic is being dropped between APs and the Apple TV is fine. If _meshcop is absent even on the same AP, the box is not advertising it, and I would file this in Feedback Assistant as a tvOS 27.2 Thread regression with the before and after behavior noted.

Originally posted at discussions.apple.com/thread/256385515