Zigbee by @ivangdavila
Deploy and troubleshoot Zigbee mesh networks for home automation.
clawhub install zigbeeCopy
π About This Skill
name: Zigbee
description: Deploy and troubleshoot Zigbee mesh networks for home automation.
metadata: {"clawdbot":{"emoji":"π","os":["linux","darwin","win32"]}}
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