Zigbee

Deploy and troubleshoot Zigbee mesh networks for home automation.

Security Scan

This is an instruction-only troubleshooting guide for Zigbee meshes; its content, lack of required credentials, and lack of install steps are consistent with its stated purpose.

Purpose & Capability

The name and description (deploy and troubleshoot Zigbee mesh networks) match the SKILL.md content. The skill requests no binaries, env vars, or config paths — nothing unrelated to Zigbee troubleshooting is asked for.

Instruction Scope

SKILL.md is purely informational troubleshooting guidance (pairing tips, routing, coordinator placement, interference, etc.). It contains no shell commands, file or path references, environment-variable access, or instructions to transmit data to external endpoints.

Install Mechanism

There is no install spec and no code files — this is instruction-only, so nothing will be downloaded or written to disk by the skill itself.

Credentials

The skill requires no credentials, environment variables, or config paths — the requested access is minimal and proportional to a guidance-only skill.

Persistence & Privilege

always is false and the skill does not request persistent or elevated privileges. The skill being user-invocable and allowed to be invoked by the agent is the platform default and is appropriate for an informational skill.

Assessment

This skill is low-risk: it's an offline troubleshooting guide with no code, no installs, and no credential access. Two practical cautions: (1) provenance is unknown (no homepage/source), so treat the advice as general guidance — verify device- or vendor-specific instructions before flashing firmware or making irreversible changes; (2) this skill will not perform hardware actions for you (it's informational only). If you need an automated tool that talks to a coordinator device, prefer a skill that explicitly declares the required hardware access, credentials, and a trusted source.

Mesh Network Traps

• Battery devices don't route — only mains-powered devices extend mesh
• Mesh needs routers every 10-15m — one coordinator alone has limited range
• Adding routers requires rebuilding routes — devices don't automatically find new paths
• First devices paired become mesh backbone — pair routers before sensors

Coordinator Issues

• Only one coordinator per network — two coordinators create two separate networks
• Coordinator stick placement matters — USB extension away from computer reduces interference
• Coordinator migration loses all pairings — backup before switching hardware
• Some sticks need firmware flash — Sonoff, CC2531 don't work out of box

WiFi Interference

• Zigbee shares 2.4GHz spectrum — WiFi channels overlap with Zigbee channels
• Zigbee channel 11 = WiFi channel 1, Zigbee 25 = WiFi 11 — pick non-overlapping
• Default Zigbee channel 11 often worst — conflicts with common WiFi defaults
• Changing Zigbee channel requires re-pairing all devices — choose carefully initially

Compatibility Issues

• "Zigbee compatible" doesn't mean interoperable — some devices only work with their hub
• Xiaomi/Aqara devices drop off generic coordinators — need specific handling
• Tuya Zigbee often requires their gateway — may not pair with Zigbee2MQTT
• Check device compatibility list before buying — not all Zigbee is equal

Pairing Problems

• Pairing mode timeout is short — be ready before enabling
• Factory reset required if previously paired — hold button 5-10 seconds
• Distance during pairing matters — pair close to coordinator, move after
• Some devices need multiple reset attempts — keep trying

Groups vs Binding

• Groups: coordinator sends one command to all — requires coordinator online
• Binding: direct device-to-device — works without coordinator, lower latency
• Binding a switch to bulbs survives coordinator reboot — groups don't
• Not all devices support binding — check before planning automation

Battery Devices

• Battery sensors sleep aggressively — commands only received on wake
• Check-in intervals vary by device — some wake every hour, others every few seconds
• Reporting thresholds affect battery life — frequent updates drain faster
• Replacing battery sometimes requires re-pairing — device forgets network

Common Failures

• Device shows online but doesn't respond — try power cycle, check routing
• Intermittent responses — mesh too sparse, add routers
• Delayed commands — routing through many hops, add closer router
• New device won't pair — network in wrong mode, coordinator issue, or device not reset