Why Smart-Home Devices Cannot Find Each Other on the Local Network

A phone and accessory can both reach the internet yet be unable to see each other. Local discovery depends on the home network allowing the relevant devices and discovery messages to meet. Guest networks and client-isolation features commonly prevent device-to-device communication by design.

Do not disable security broadly. First confirm whether the phone, controller, border router, and accessory are intended to share a trusted LAN under the router maker’s documented configuration.

Matter uses IPv6 for operational communication and DNS-based service discovery to locate commissioned nodes. On Wi-Fi and Ethernet, multicast DNS carries local discovery. For Thread devices, the Thread border router advertises discovery information onto the adjacent Wi-Fi or Ethernet network.

You do not need to calculate addresses. The homeowner consequence is simple: blocking IPv6, multicast discovery, or the route between Thread and the LAN can prevent setup or control even when ordinary websites load.

1. Put the setup phone on the intended home Wi-Fi, not cellular or a guest SSID.
2. Confirm the controller or bridge is on the same intended logical LAN.
3. Check router documentation for guest isolation, client/AP isolation, VLAN, or IoT-network discovery rules.
4. Confirm IPv6 and multicast settings have not been disabled as an undocumented troubleshooting shortcut.
5. Retest discovery before resetting the accessory.

Separating IoT devices can be useful, but a segmented design must deliberately permit the exact control and discovery traffic required between trusted controllers and devices. Do not expose devices to the internet, add blanket port forwarding, or remove firewall protection to make discovery work. If your router cannot express a safe rule you understand, use its supported default LAN or seek qualified network help.