Network control path
A command is a path, not a single connection
When a light, sensor, or thermostat appears “offline,” the accessory may still be healthy. A command can pass through a phone or automation engine, an account, the home’s Wi-Fi or Ethernet LAN, a Matter controller, a bridge, or a Thread border router before it reaches the device.
Write that path from left to right. The exact path differs by device, but the diagnostic rule is stable: test each layer separately and stop at the first transition that fails.
Network control path
Match symptoms to layers
| What still works | What it suggests | Check next |
|---|---|---|
| Physical control only | Power may be present while network control is absent. | Device connection and manufacturer app. |
| Manufacturer app on home Wi-Fi | The immediate device path probably works. | Receiving platform, account link, controller, or bridge. |
| Manual platform control | The control path works outside the rule. | Automation starter, condition, action, and owner. |
| Local control but not remote control | The LAN may be healthy while internet, cloud, or authorization is not. | Internet service and platform status. |
Network control path
Keep Wi-Fi, Thread, and application roles separate
Wi-Fi and Ethernet place devices directly on the home IP network. Thread is also IP-based, but uses a low-power mesh connected to the adjacent Wi-Fi or Ethernet network by a Thread border router. Matter operational discovery uses DNS-based service discovery; Thread devices rely on border-router proxying for that discovery.
A controller decides how a platform administers Matter devices. A Thread border router moves network traffic. One product may do both jobs, but successful control requires every required role and the paths between them.
Network control path
Build a control-path record
- Name the device and its connection method.
- Name the direct app and primary control platform.
- Record the controller, bridge, or border router the path requires.
- Mark which steps need local discovery, internet access, or a cloud account.
- Record one physical or direct-app fallback.
This small map is more useful during an outage than a list of Wi-Fi signal bars.
Evidence boundary
Network behavior depends on the exact setup
Router, mesh, platform, model, software, and region behavior can change. Confirm current documentation before changing network security or resetting a device. Never expose devices directly to the internet merely to restore discovery.
Primary sources
Official documentation behind the network boundaries
Continue the diagnosis