unifi-wifi

Solid

Use when UniFi Wi-Fi is slow, unstable, or being tuned: "my wifi is slow but speedtest on the router is fast", "great signal, terrible speed", "should I use 80MHz or 40MHz", "channel planning", "co-channel interference", "DFS channels", "my APs keep picking the same channel", "audit my SSIDs", "hidden SSID", or diagnosing throughput that collapses under load. Covers the diagnostic ladder for slow Wi-Fi, channel width and DFS tradeoffs, safe radio writes, SSID hygiene, and the in-wall AP port trap. Assumes unifi-connect. Not for firewall policy between networks (unifi-firewall), wired port and client operations (unifi-clients).

AI & Automation 29 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
49
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# UniFi Wi-Fi Most "slow Wi-Fi" is not slow Wi-Fi. It is a WAN problem, a backhaul problem, a client problem, or a bandwidth cap somebody set two years ago. The diagnostic ladder below exists to find that out cheaply, in that order, before touching radios. Radio changes are the most disruptive and the most often wrong. ## The diagnostic ladder Run it top to bottom. Each rung eliminates a layer, and the failure that motivated this skill was only visible at the last rung. **1. Rule out the WAN.** Trigger a gateway-side speedtest, which measures the gateway to the internet with no Wi-Fi involved: ```bash udm raw POST /proxy/network/api/s/default/cmd/devmgr '{"cmd":"speedtest"}' # wait, then read the RESULT from stat/device, not stat/health udm devices --json | python3 -c ' import json,sys for d in json.load(sys.stdin): s = d.get("speedtest-status") if s: print(d.get("name"), s.get("xput_download"), s.get("xput_upload"), "status_summary=", s.get("status_summary"))' ``` The result lands on the **gateway's** device object, under the hyphenated key `speedtest-status` (not `speedtest_status`), with throughput in the nested `xput_download` and `xput_upload` fields. `status_summary` tells you whether the run finished; a fresh gateway that has never run one reports zeros. `stat/health` is a different number entirely and will send you in circles. **2. Check the AP's uplink.** An AP on a 100 Mbps link, or meshed rather than wired, caps every client behind it...

Details

Author
t3chnaztea
Repository
t3chnaztea/unifi-skills
Created
2 days ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Solid

unifi-clients

Use when operating on UniFi clients, devices, switch ports, or DHCP: "block a device", "kick a client off wifi", "restart an access point", "power cycle a PoE port", "move a device to a different VLAN", "my device is on the wrong subnet after I changed the port", "set a DHCP reservation", "change DHCP DNS servers", "forget an old client", "why did my PUT reset all the other ports", or reading UniFi events and alarms. Covers full-object PUT discipline, the wired VLAN migration trap, and where events moved. Assumes unifi-connect. Not for firewall policy between zones (unifi-firewall), radios and SSIDs (unifi-wifi).

29 Updated yesterday
t3chnaztea
AI & Automation Solid

unifi-yourskill

Use when [the specific situations, symptoms, and phrases someone would actually type when they hit this problem]. Include the error strings and the wrong-conclusion phrasings, not just the correct terminology: people search for "my wifi is slow", not "co-channel contention". Describe ONLY when to use it, never summarize the workflow inside. Keep the whole frontmatter under 1024 characters. End by naming what this skill is NOT for, pointing at the sibling skill that covers it.

29 Updated yesterday
t3chnaztea
AI & Automation Solid

unifi-firewall

Use when working on UniFi firewall rules, zones, or network segmentation: "my firewall rules are empty", "rest/firewallrule returns nothing", "isolate my IoT devices", "block cameras from the internet", "create a firewall zone", "VLAN isolation", "zone-based firewall", "my IoT devices lost DNS after I segmented them", or auditing what a zone actually permits. Covers the zone-based firewall model, where policies live, the block-by-default trap on new zones, and lockout safety. Assumes unifi-connect. Not for assigning devices to VLANs or switch ports (unifi-clients), Wi-Fi and SSID-to-network mapping (unifi-wifi).

29 Updated yesterday
t3chnaztea