Discover first, then verify
Select the intended network and interface or bridge before running discovery. Neighbor information is useful initial evidence, but does not by itself prove current reachability or a wireless parent relationship. Distinguish online, offline and unverified states instead of treating missing observations as confirmed outages.
Inspect one access point
Open a device card and run its check. Supported devices, including some Ubiquiti models, can expose wireless role and connection information through available services with valid credentials. Results depend on model, firmware, permissions and network access. A timeout alone does not prove the device has stopped operating.
Build relationships from evidence
Parent-child discovery requires usable information from access points or their connected stations. A transmitter's client count is not always the number of cards the map can resolve: some addresses may be undiscovered, unreachable or incomplete. Review the scan result before treating the drawing as a complete inventory.
Read AP, STA and signal correctly
AP commonly indicates an access-point role; STA indicates a station connected to another point. Signal readings describe the measured wireless link, not internet speed or the quality of the entire network. Missing signal data should not be read as zero, and an unknown role should not be assumed to be AP.
Wired links and manual placement
A transmitter can be wired behind a receiving station, so wireless role alone is not enough to infer physical topology. If you assign a parent manually, choose the actual upstream device and avoid cycles. Distinguish a manually assigned relationship from one observed by a device to make future troubleshooting clearer.
Check the finished map
Review interface placement, parents, children and the most recent check status. Search for a specific card and compare it with direct device observations if its placement looks wrong. The map becomes more useful as discovery coverage and device access information improve.