Network field notebook

I Found Three Thread Network Names
on My Home Network

Apple, Amazon, and eero advertised three Thread network names. That prompted a closer look at the difference between discovery, shared credentials, and radio paths.

9 min readInteractive field note

Three meshes, one IP network

My capture found separate network names for Apple, Amazon, and eero; it did not expose their credentials. Separate credentials can produce separate radio meshes, but network names alone do not prove credential or radio topology.

When two Thread devices sit on different meshes, their traffic crosses a border router, the home IP network, and another border router. I did not measure enough to claim a specific latency penalty.

Below is a model based on my discovery output, with example network names, hostnames, ports, and devices. It is an illustration, not a live capture. Press play to compare an eero-mesh sensor reaching an Amazon-mesh bulb with a same-mesh route.

What the apps do not show

Each vendor app shows a clean local view. None show the cross-mesh path.

  • Apple Home shows the sensor and TV, but not the border routers or routed IP path.
  • Alexa shows the bulb and Echo, but not the eero side of the route.
  • eero shows Wi-Fi and clients, but not Thread hops at all.

The command nobody runs

Thread border routers announce themselves over mDNS under _meshcop._udp. Grouping by network name revealed three advertised names; it did not by itself establish shared credentials or radio connectivity.

dns-sd -B _meshcop._udp .

example-eero-mesh
example-apple-mesh
example-amazon-mesh

The apps show which ecosystems can control a device. The browse shows advertised network names and border routers, not the path a particular device’s packets took. Those are different questions.

Why I commission via eero first

My capture listed three eero border routers and one Apple border router. I preferred trying eero first, but an address prefix alone does not prove which network commissioned a device, and commissioning there is not a guarantee that another network will never be created.

A Matter fabric controls application trust; a Thread network carries packets. Pairing order can affect the second without making those two layers the same thing.