Automation
Command
/unifly-status
Config profile to use (e.g., home, office)
Install
> /plugin marketplace add hyperb1iss/unifly > /plugin install unifly@hyperb1iss
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/unifly-status
Context preview
What this command does when you run it.
Config profile to use (e.g., home, office)
Command definition
unifly-status.mdname: unifly-status
description: Quick health check of UniFi infrastructure. Shows controller health, device status, and alerts
arguments:
- name: profile
description: "Config profile to use (e.g., home, office)"
required: falseUniFi Status Check
Run a comprehensive health check of the UniFi infrastructure.
Execution
1. Verify controller connectivity via `unifly system health` 2. Count online vs offline devices via `unifly devices list --all -o json` 3. Check for active alarms via `unifly alarms list --unarchived -o json` 4. Report findings in a clear summary
Basic Status
unifly system health -p {{profile}} -o jsonFull Status Report
# Controller health
unifly system health -p {{profile}} -o json
# Device summary
unifly devices list --all -p {{profile}} -o json | jq '{
total: length,
online: [.[] | select(.state == "ONLINE")] | length,
offline: [.[] | select(.state == "OFFLINE")] | length,
pending: [.[] | select(.state == "PENDING")] | length
}'
# Active alarms
unifly alarms list --unarchived -p {{profile}} -o json | jq 'length'
# Client count
unifly clients list --all -p {{profile}} -o json | jq 'length'When `-p {{profile}}` is provided, the `-p {{profile}}` flag is already wired into every command above; no further substitution is needed.
Result Reporting
Summarize the health check:
- Controller status (healthy/degraded/unreachable)
- Device counts by state
- Number of active alarms (highlight if > 0)
- Connected client count
- Any offline devices (list names and MACs)
Read more
name: unifly-status
description: Quick health check of UniFi infrastructure. Shows controller health, device status, and alerts
arguments:
- name: profile
description: "Config profile to use (e.g., home, office)"
required: falseUniFi Status Check
Run a comprehensive health check of the UniFi infrastructure.
Execution
1. Verify controller connectivity via `unifly system health` 2. Count online vs offline devices via `unifly devices list --all -o json` 3. Check for active alarms via `unifly alarms list --unarchived -o json` 4. Report findings in a clear summary
Basic Status
unifly system health -p {{profile}} -o jsonFull Status Report
# Controller health
unifly system health -p {{profile}} -o json
# Device summary
unifly devices list --all -p {{profile}} -o json | jq '{
total: length,
online: [.[] | select(.state == "ONLINE")] | length,
offline: [.[] | select(.state == "OFFLINE")] | length,
pending: [.[] | select(.state == "PENDING")] | length
}'
# Active alarms
unifly alarms list --unarchived -p {{profile}} -o json | jq 'length'
# Client count
unifly clients list --all -p {{profile}} -o json | jq 'length'When `-p {{profile}}` is provided, the `-p {{profile}}` flag is already wired into every command above; no further substitution is needed.
Result Reporting
Summarize the health check:
- Controller status (healthy/degraded/unreachable)
- Device counts by state
- Number of active alarms (highlight if > 0)
- Connected client count
- Any offline devices (list names and MACs)
Ships withunifly
๐ Elegant UniFi network management CLI & TUI - for humans and agents
Get the whole plugin
Stats
240
Stars
15
Forks
Active
Maintenance
Rust
Language
Apache-2.0
License
2d ago
Last commit
5mo ago
Created
Repo: hyperb1iss/unifly

