Broken Matter Mesh - Apple TV fails in role as gateway

My Matter mesh is broken. No amount of resets will allow my (new) Apple TV to function or show as active on Matter. I have disconnected all Apple TV's and Homepods and deleted my home in the app. Even creating a new home and attempting to use one Apple TV as a gateway has failed. Home sees the device but Matter never shows up at all. I think Apple needs to reset my mesh, but nobody from Apple support can even understand the problem or refer me to the Homekit technical team.

Posted on Jan 13, 2026 10:57 PM

Reply
Question marked as Top-ranking reply

Posted on Jan 22, 2026 8:38 AM

I saw your Apple Support Communities post (“Broken Matter Mesh - Apple TV fails in role as gateway”) and your description sounds very similar to an issue I chased for weeks with Matter over Thread devices and Apple TV acting as the hub/border router.


In my case, the Apple TV would appear in Home as the connected hub, but the Matter/Thread side would either not show up reliably or would flap (devices would go No Response, automations would stop, and sometimes it looked like there was no border router at all). I eventually found the root cause was a VPN on the Apple TV combined with Ethernet. Once I removed that variable, everything immediately stabilized.


Here are a couple concrete tests that were decisive for me and might help you isolate whether something similar is happening:

1. If you have any VPN app or profile on the Apple TV (NordVPN in my case), disable it completely as a test.


• With VPN enabled and Apple TV on Ethernet, my Thread/Matter network would not properly form.

• Turning the VPN off restored the border router role and devices began working again.


2. If you want to keep VPN enabled, try switching the Apple TV from Ethernet to Wi-Fi (same LAN).


• In my setup, Apple TV on Wi-Fi stayed stable even with VPN enabled, while Apple TV on Ethernet did not.

• This suggests some interaction between the Apple TV VPN/tunneling behavior and local LAN discovery/routing (mDNS/Bonjour/multicast), especially on the Ethernet interface.


3. If you have only one hub, consider temporarily making sure the Apple TV is the only candidate hub while testing.


• Unplug other Apple TVs/HomePods during the test window so you can see clearly whether the Apple TV becomes the border router and stays that way.


4. Router-side quick checks that improved stability (not the root cause for me, but worth doing once):


• Disable QoS.

• Use WPA2-only on 2.4 GHz (some IoT devices behave better).

• Fix 2.4 GHz channel/width to 20 MHz and avoid Auto.

• Reserve a stable IP (DHCP reservation) for the Apple TV.


If your symptoms are that Home sees the Apple TV, but Matter never shows a gateway/border router, the VPN/Ethernet variable is a surprisingly common and easy thing to rule out before deeper resets.


If you share whether you run any VPN on the Apple TV (or at the router), and whether your Apple TV is on Ethernet vs Wi-Fi, I can tell you exactly what change fixed it for me and what the expected behavior should look like after.

4 replies
Question marked as Top-ranking reply

Jan 22, 2026 8:38 AM in response to Lemon Sand

I saw your Apple Support Communities post (“Broken Matter Mesh - Apple TV fails in role as gateway”) and your description sounds very similar to an issue I chased for weeks with Matter over Thread devices and Apple TV acting as the hub/border router.


In my case, the Apple TV would appear in Home as the connected hub, but the Matter/Thread side would either not show up reliably or would flap (devices would go No Response, automations would stop, and sometimes it looked like there was no border router at all). I eventually found the root cause was a VPN on the Apple TV combined with Ethernet. Once I removed that variable, everything immediately stabilized.


Here are a couple concrete tests that were decisive for me and might help you isolate whether something similar is happening:

1. If you have any VPN app or profile on the Apple TV (NordVPN in my case), disable it completely as a test.


• With VPN enabled and Apple TV on Ethernet, my Thread/Matter network would not properly form.

• Turning the VPN off restored the border router role and devices began working again.


2. If you want to keep VPN enabled, try switching the Apple TV from Ethernet to Wi-Fi (same LAN).


• In my setup, Apple TV on Wi-Fi stayed stable even with VPN enabled, while Apple TV on Ethernet did not.

• This suggests some interaction between the Apple TV VPN/tunneling behavior and local LAN discovery/routing (mDNS/Bonjour/multicast), especially on the Ethernet interface.


3. If you have only one hub, consider temporarily making sure the Apple TV is the only candidate hub while testing.


• Unplug other Apple TVs/HomePods during the test window so you can see clearly whether the Apple TV becomes the border router and stays that way.


4. Router-side quick checks that improved stability (not the root cause for me, but worth doing once):


• Disable QoS.

• Use WPA2-only on 2.4 GHz (some IoT devices behave better).

• Fix 2.4 GHz channel/width to 20 MHz and avoid Auto.

• Reserve a stable IP (DHCP reservation) for the Apple TV.


If your symptoms are that Home sees the Apple TV, but Matter never shows a gateway/border router, the VPN/Ethernet variable is a surprisingly common and easy thing to rule out before deeper resets.


If you share whether you run any VPN on the Apple TV (or at the router), and whether your Apple TV is on Ethernet vs Wi-Fi, I can tell you exactly what change fixed it for me and what the expected behavior should look like after.

Jan 22, 2026 4:56 PM in response to Lemon Sand

Lemon Sand wrote:

Turns out that if you are relying on an AppleTV as your Thread border router, the Thread network is 100% invisible. But, if you are using a Homepod, the Thread network shows up in the Home app under Home Settings/Hubs and Bridges. I suspect most people would rely on an AppleTV and will never know if Thread is operational until they attempt to pair a Matter/Thread device and then turn Bluetooth off to test the connection. I got an Eve Matter/Thread smart outlet and sure enough it did pair, work, and expose the Thread network including the AppleTV's properly functioning as routers. The Eve for Matter/Homekit app shows you everything.


Log some feedback with Apple: Product Feedback - Apple


It's been an education, but a slightly expensive one (playing with different devices) and a time suck. To make matters (no pun intended) 10x worse, ChatGPT and CoPilot are ignoramuses on the subject. LLM = Large Language Misdirection on this particular topic.


That LLMs are terrible technical reference sources is not unique, unusual, or even unexpected.


Even better, results are likely to degrade further, as updates to the LLM corpora ingest LLM output.


LLM output doubles the work around here, as there’s the answer, and then explaining where the LLM went wrong.


Jan 22, 2026 3:52 PM in response to Lemon Sand

Turns out that if you are relying on an AppleTV as your Thread border router, the Thread network is 100% invisible. But, if you are using a Homepod, the Thread network shows up in the Home app under Home Settings/Hubs and Bridges. I suspect most people would rely on an AppleTV and will never know if Thread is operational until they attempt to pair a Matter/Thread device and then turn Bluetooth off to test the connection. I got an Eve Matter/Thread smart outlet and sure enough it did pair, work, and expose the Thread network including the AppleTV's properly functioning as routers. The Eve for Matter/Homekit app shows you everything.


Why Apple sees fit to treat AppleTV as a poor cousin to Homepod when it comes to Thread support is beyond me. The world of transport (WiFi, Zwave, Zigbee, Thread, etc.) is obscure to most users who get totally confused about Matter over WiFi vs. Matter over Thread, etc. not to mention non-Matter connection protocols. It is a morass made worse by this particular obfuscation by Apple. It's no wonder few vendors have ventured into Thread, and fewer still (one - Aqara) into the UWB support that requires Thread.


It's been an education, but a slightly expensive one (playing with different devices) and a time suck. To make matters (no pun intended) 10x worse, ChatGPT and CoPilot are ignoramuses on the subject. LLM = Large Language Misdirection on this particular topic.

Jan 22, 2026 9:03 AM in response to D_M_G

VPNs are too often privacy-leaking hot garbage, seemingly perfect for metadata collection, with negligible added security, and otherwise just adding overhead badly solving an issue that hasn’t existed for a decade or so.


Need privacy and connection security? Use iCloud+ Private Relay with ODoH. If that’s not already in use.


And yeah, VPNs can and do (and need to) mess with routing, some even when ostensibly disabled.

Broken Matter Mesh - Apple TV fails in role as gateway

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.