Device messaging debug

You can check the communication with any device without setting the entire adapter into debug mode.

Add the ieee number in to zigbee.0.info.debugmessages (for example a4c138af98263863. Multiple ieee can be entered if separated by a ; Starting with the Adapter 2.0.1, the debug can be activated device specific by using the bug icon on the device tile (leftmost icon. Black: Debug is off. Green: Debug is on, Orange: Debug is on due to a pattern match). The adapter does not need to run in Debug mode or be restarted when activating this feature.

The iobroker Log will contain ELEVATED warn messages for the device with active debug. The messages fall into 2 separate 'chains': ELEVATED I00 to I06 (possibly) signal events generated when the device sends a message to the Adapter. They offer the option to track the flow of the event through the internal structure, and show a link between the device payload generated by the zigbee-herdsman and the state changes in ioBroker.

Example:

2025-02-26 14:44:57.896  - �[33mwarn�[39m: zigbee.0 (1289) ELEVATED I00: Zigbee Event of Type commandMove from device "0x28dba7fffe85ca78", incoming event: {"type":"commandMove","device":"0x28dba7fffe85ca78","endpoint":1,"data":{"movemode":1,"rate":255},"linkquality":168,"groupID":0,"cluster":"genLevelCtrl"}
2025-02-26 14:44:57.901  - �[33mwarn�[39m: zigbee.0 (1289) ELEVATED I01: message received '{"linkquality":168}' from device 28dba7fffe85ca78 type 'E2123'
2025-02-26 14:44:57.902  - �[33mwarn�[39m: zigbee.0 (1289) ELEVATED I02: value generated '168' from device 28dba7fffe85ca78 for 'Link quality'

• I00: incoming message with cluster, type and content, sent to the converter.
• I01: message after processing from the converter, identifying payload for the adapter
• I03: message after modifying the iobroker State, with state ID and new Value

ELEVATED O00 to O06 These messages are generated when the user modifies a state and track the passage of the change to the device, again generating a link between the state change and the payload sent to the adapter due to this.

Example:

2025-02-26 21:10:34.060  - warn: zigbee.2 (1149) ELEVATED O01: User state change of state zigbee.2.ccccccfffee3ef17.state with value true (ack: false) from system.adapter.zigbee.2
2025-02-26 21:10:34.062  - warn: zigbee.2 (1149) ELEVATED O02: Change state 'state' at device 0xccccccfffee3ef17 type '07048L'
2025-02-26 21:10:34.062  - warn: zigbee.2 (1149) ELEVATED O03: Publishing to 0xccccccfffee3ef17 of model 07048L 
2025-02-26 21:10:34.064  - warn: zigbee.2 (1149) ELEVATED O04.0: Setting' converter to converter with key(s)'["state","on_time","off_wait_time"]}
2025-02-26 21:10:34.064  - warn: zigbee.2 (1149) ELEVATED O04: convert state, "ON", {} for device 0xccccccfffee3ef17 with Endpoint state
2025-02-26 21:10:34.171  - warn: zigbee.2 (1149) ELEVATED O05: convert result {"state":{"state":"ON"}} for device 0xccccccfffee3ef17

O01: State change detected, includes new value, ack flag, state ID and source of the change O02: Link: state -> device and Model O03: Publish to Converter triggered O04, O04.0: Converter selection plus value conversion for sending data to the device O05: Payload sent to the device.