Got back ZigbeeStatus here

Zigbee-Operation.md

@@ -8,6 +8,9 @@ Note: Zigbee will automatically boot the CC2530 device, configure it and wait fo
 ### 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.  
 
+
+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>
+
 ### Permit Join
 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:  
 - `ZigbeePermitJoin 1`: enables pairing for 60 seconds