Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Deploy and troubleshoot Zigbee mesh networks for home automation.
Deploy and troubleshoot Zigbee mesh networks for home automation.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
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
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
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
"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 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: 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 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
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
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.