network-health-check

To diagnose UniFi network issues, run a health check that batches system info, device states, and active alarms to generate a prioritized report. It analyzes WAN, LAN, WLAN, and VPN subsystems in priority order to isolate whether the root cause is ISP connectivity, switch failures, or WiFi degradation.

The best way to check UniFi firmware updates and active alarms is to run a network health check that collects device data in a single batch. It interprets alarm severity and device state codes using reference mappings, then summarizes firmware upgrade needs and alarm-driven incidents in plain language with remediation guidance.

A UniFi network health check prioritizes troubleshooting by analyzing subsystems in the order WAN, LAN, WLAN, then VPN. This upstream-first approach ensures that ISP or routing failures are identified before local switch or WiFi issues, preventing upstream outages from obscuring the actual root cause of network degradation.

Yes, you need a configured UniFi Network MCP server set via the UNIFI_NETWORK_HOST environment variable to run network monitoring and health checks. This connection allows the tool to execute batched UniFi API calls, retrieve controller data, and classify device states and alarm types for diagnostic reporting.

Yes, you can interpret UniFi device state anomalies and alarm types automatically using built-in reference mappings. The health check classifies raw controller data into plain language summaries, evaluates alarm severity, identifies offline devices, and provides actionable remediation guidance for each detected anomaly.

UniFi devices showing offline states during routine maintenance checks can be caused by WAN failures, switch connectivity loss, or firmware instability. A network health check evaluates device state codes, active alarms, and subsystem status to determine whether the offline condition stems from upstream routing or local device issues.