QS-Zigbee-D02-TRIAC-LN_1 - no more dimming

[chrischn82]

describe the changes between the device operation problem in Detail. What is the curernt state, what is the desired state ?

"Modell QS-Zigbee-D02-TRIAC-LN_1 (4 baugleiche Geräte) nimmt ab v3.4.10 oder früher keine Dimmbefehle mehr an (Error: Send command... failed with no error code (undefined)). Ein Downgrade auf v3.3.5 behebt das Problem sofort.

Device information (Type of the device, including the Z2M link to the device description page)

https://www.zigbee2mqtt.io/devices/QS-Zigbee-D02-TRIAC-LN_1.html

Coordinator firmware version

0-0.2.6.102.

Coordinator

ConBee2/RaspBee2

Setup

Raspberry PI4 8GB - 64GB SDHC

Current adapter version

3.5.5 (3.3.5 works without this error)

Protocol of the error (as text, encapsulated in multiline code tags <>). Logs which are too big to be shown in the issue MUST be trimmed so that they fit, e.g. by removing duplicate warning messages.

Error: Send command... failed with no error code (undefined)

Previous adapter version

3.3.5

Protocol of the error (as text, encapsulated in multiline code tags <>). Logs which are too big to be shown in the issue MUST be trimmed so that they fit, e.g. by removing duplicate warning messages.

no error

[asgothian]

Please read this document: https://github.com/ioBroker/ioBroker.zigbee/wiki/Device-messaging-debug , then use the info contained to do the following :

• set the device to device debug.
• try to dim the device
• check the debug tab for the corresponding messages
• post the message details here (as text - as described in the document)

A.

[chrischn82]

`Messages from 20:10:54 for device 0xa4c138d2f0b8f499

O01: User state change of state zigbee.0.a4c138d2f0b8f499.brightness with value 38 (ack: false) from system.adapter.lovelace.0
O02: Change state 'brightness' at device 'Bad_Deckenspots (0xa4c138d2f0b8f499)' type 'QS-Zigbee-D02-TRIAC-LN_1'
O03: Publishing to 'Bad_Deckenspots (0xa4c138d2f0b8f499)' of model QS-Zigbee-D02-TRIAC-LN_1 with brightness
Os4.0: Setting' converter to converter with key(s)'["state","brightness"]}
O04: convert brightness with value 96 and options {"state":"ON","brightness":96} for device 'Bad_Deckenspots (0xa4c138d2f0b8f499)' without Endpoint
O05: Attempt 1 at converting data for brightness with preparedValue 96, meta.state {"state":"ON"}, meta.message {"brightness":96}
EXSET: caught error Cannot read properties of undefined (reading 'toString') when setting value for device 'Bad_Deckenspots (0xa4c138d2f0b8f499)' (TypeError: Cannot read properties of undefined (reading 'toString') at Object.toNumber (/opt/iobroker/node_modules/zigbee-herdsman-converters/dist/lib/utils.js:621:112) at Object.convertSet (/opt/iobroker/node_modules/zigbee-herdsman-converters/dist/lib/tuya.js:2763:111) at ZigbeeController.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1688:54)).

[asgothian]

Please add the option meta_state with the value brightness to the device or model (see the documentation on how to set device / model options.

This should fix the problem without adapter restart for either model or device option.

A.

[chrischn82]

I did. It worked.

Setting Model Options via the UIOpen the ioBroker Admin interface and go to Instances. Click the settings (wrench/gear) icon on your Zigbee instance. Switch to the Local Data tab. Find your target model or device in the list. Click the edit/options button (green icon on the right) for that specific model to open the configuration dialog. Adjust advanced options (most advanced settings mirrored from Zigbee2MQTT), default names, or icons, then save. Note: Changes here do not auto-restart the adapter, and state-affecting changes may require a manual adapter restart.

[asgothian]

Reopened so that other users can find the fix until the option is present as default option in the next version