mirrors
/
Tasmota
mirror of https://github.com/arendst/Tasmota.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Zigbee Operation (markdown)

Michael Ingraham 2019-11-07 23:09:20 -05:00
parent 1bef3a210f
commit 6dc444e680
1 changed files with 22 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
Zigbee-Operation.md

@ -6,10 +6,30 @@ Refer to the [Zigbee Commands](Commands#zigbee)
Note: Zigbee will automatically boot the CC2530 device, configure it and wait for Zigbee messages.
### Z2T Status
You can inspect the log output to determine whether Z2T started correctly. Z2T sends several [`ZigbeeStatus`](Commands#zigbee) messages to inform the MQTT host about initialization.
You can inspect the log output to determine whether Z2T started correctly. Z2T sends several [`ZigbeeStatus`](Commands#zigbeestatus) messages to inform the MQTT host about initialization.
Ex: ```{"ZigbeeStatus":{"Status":1,"Message":"CC2530 booted","RestartReason":"Watchdog","MajorRel":2,"MinorRel":6}}```
- `Status` contains a numeric code about the status message
- `0`: initialization complete, **Z2T is running normally**
- `1`: booting
- `2`: resetting CC2530 configuration
- `3`: starting Zigbee coordinator
- `20`: disabling Permit Join
- `21`: allowing Permit Join for 60 seconds
- `22`: allowing Permit Join until next boot
- `30`: Zigbee device connects or reconnects
- `31`: Received Node Descriptor information for a Zigbee device
- `32`: Received the list of active endpoints for a Zigbee device
- `33`: Received the simple Descriptor with active ZCL clusters for a Zigbee device
- `50`: reporting CC2530 firmware version
- `51`: reporting CC2530 device information and associated devices
- `98`: error, unsupported CC2530 firmware
- `99`: general error, **Z2T was unable to start**
- `Message` (optional) a human-readable message
- other fields depending on the message (e.g., Status=`50` or Status=`51`)
Ex: ```{"ZigbeeStatus":{"Status":1,"Message":"CC2530 booted","RestartReason":"Watchdog","MajorRel":2,"MinorRel":6}}```<BR><li>`Status` contains a numeric code about the status message<ul><li>`0`: initialization complete, **Z2T is running normally**</li><li>`1`: booting</li><li>`2`: resetting CC2530 configuration</li><li>`3`: starting Zigbee coordinator</li><li>`20`: disabling Permit Join</li><li>`21`: allowing Permit Join for 60 seconds</li><li>`22`: allowing Permit Join until next boot</li><li>`30`: Zigbee device connects or reconnects</li><li>`31`: Received Node Descriptor information for a Zigbee device</li><li>`32`: Received the list of active endpoints for a Zigbee device</li><li>`33`: Received the simple Descriptor with active ZCL clusters for a Zigbee device</li><li>`50`: reporting CC2530 firmware version</li><li>`51`: reporting CC2530 device information and associated devices</li><li>`98`: error, unsupported CC2530 firmware</li><li>`99`: general error, **Z2T was unable to start**</li></ul></li><li>`Message` (optional) a human-readable message</li><li>other fields depending on the message (e.g., Status=`50` or Status=`51`)</li>
### ZigbeePermitJoin
By default, and for security reasons, the Zigbee coordinator does not automatically accept new devices. To pair new devices, use one of the following commands: