• Wi-Fi
  • Beginner
  • 3 min
  • Serial CLI

Recipe · Beginner · Wi-Fi

How to scan Wi-Fi and find local devices

Wi-Fi mode is useful for the non-invasive side of IoT debugging: see nearby networks, connect, print status, ping and discover devices on your own LAN.

Wi-Fi signal with local network devices.
Use the board as a small network probe after it connects to your own Wi-Fi.
Step 1

Commands

Run the typed commands first. If the command opens an interactive shell, select the named action from the shell menu instead of treating it as another CLI command.

Result

What success looks like

Use scan/status for connectivity, discovery for local visibility, and ping for reachability. Avoid running Wi-Fi reset/disconnect while using Web CLI.

Troubleshooting

  • Changing Wi-Fi state while connected through Web CLI.
  • Scanning or probing networks you do not own or have permission to test.
  • Assuming discovery finds every device; some hosts block ping.
  • Forgetting saved credentials may auto-reconnect later.

Next steps

  • Use webui to print the Web UI URL after connecting.
  • Use ping <host> for reachability.
  • Use nc or http get only against systems you control.

Wi-Fi and LAN discovery FAQ

What is the difference between scan and discovery?

scan lists nearby Wi-Fi networks and radio details. discovery runs after connection and looks for reachable devices on the local network.

What should Wi-Fi discovery results be used for?

Use them as a map of visible hosts and likely next probes, not as a complete inventory. Discovery helps prioritize ping, HTTP, port checks or manual verification.

What does local discovery add after a Wi-Fi scan?

A Wi-Fi scan finds access points. Local discovery goes one step deeper by looking for reachable hosts and services on the connected network, which helps plan HTTP, ping, Modbus or TCP checks.

Go deeper