Trust ZYCT-202 Failed to configure #5928

Mr-Groch · 2021-01-27T07:07:15Z

What happened

Each Zigbee2MQTT restart i see in logs:

Zigbee2MQTT:error 2021-01-26 17:00:47: Failed to configure 'Pilot do świateł 1', attempt 1 (Error: Bind 0x00158d00038e48fa/1 genOnOff from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))
Zigbee2MQTT:error 2021-01-26 17:01:05: Failed to configure 'Pilot do świateł 1', attempt 2 (Error: Bind 0x00158d00038e48fa/1 genOnOff from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))
Zigbee2MQTT:error 2021-01-26 17:01:20: Failed to configure 'Pilot do świateł 1', attempt 3 (Error: Bind 0x00158d00038e48fa/1 genOnOff from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))

The same happens when I click "reconfigure" button from frontend for this device. I'm waking it up before that. Device is working - all button presses are handled by zigbee2mqtt, just no battery level (I'm using this device about 2 months now and still no battery property).

What did you expect to happen

There should be no error in logs for this device and reconfiguration should success. Also battery level should work

How to reproduce it (minimal and precise)

Force delete ZYCT-202 device from zigbee2mqtt
Reset ZYCT-202 device by holding Off button for 10 seconds
Enable pairing mode in zigbee2mqtt
Pair ZYCT-202 with zigbee2mqtt by holding "two bulbs" button for 5 seconds until leds flashes
Observe in zigbee2mqtt logs that configuration of device fails
Restart zigbee2mqtt and failed to reconfigure still fails

Debug info

Zigbee2MQTT version: 1.17.0
Adapter hardware: CC26X2R1 zzh!
Adapter firmware version: 20201113

The text was updated successfully, but these errors were encountered:

Tyrian81 · 2021-01-28T11:42:45Z

I have the exact same problem, hope theres a solution
tried resetting device, repairing like 10 x
interview 100% , gets added in HA , but then no actions or lqi

Koenkk · 2021-01-28T16:59:11Z

Battery isn't supported indeed. Can you update the definition in devices.js to below and see if it works after a repair? (if it works configure error should also be fixed)

{
    zigbeeModel: ['\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000'+
                    '\u0000\u0000\u0000\u0000\u0000', 'ZLL-NonColorController'],
    model: 'ZYCT-202',
    vendor: 'Trust',
    description: 'Remote control',
    fromZigbee: [fz.command_on, fz.command_off_with_effect, fz.legacy.ZYCT202_stop, fz.legacy.ZYCT202_up_down, fz.battery],
    exposes: [e.action(['on', 'off', 'stop', 'brightness_stop', 'brightness_move_up', 'brightness_move_down']), e.battery()],
    toZigbee: [],
    meta: {configureKey: 2},
    configure: async (device, coordinatorEndpoint, logger) => {
        const endpoint = device.getEndpoint(1);
        await reporting.bind(endpoint, coordinatorEndpoint, ['genPowerCfg']);
        await reporting.batteryPercentageRemaining(endpoint);
    },
},

Mr-Groch · 2021-01-28T21:07:27Z

I had some trouble with pairing (but with this device there were always problems during pairing - no all attempts were succesfull). At the end I paired it successfully with no error message, battery is exposed now, but without value for now... I will wait some time if it will appear or not...

EDIT: After next Zigbee2mqtt restart I see that configuring also fails:

Zigbee2MQTT:error 2021-01-28 22:21:45: Failed to configure 'Pilot do świateł 1', attempt 1 (Error: Bind 0x00158d00038e48fa/1 genPowerCfg from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))
Zigbee2MQTT:error 2021-01-28 22:22:09: Failed to configure 'Pilot do świateł 1', attempt 2 (Error: Bind 0x00158d00038e48fa/1 genPowerCfg from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))
Zigbee2MQTT:error 2021-01-28 22:22:26: Failed to configure 'Pilot do świateł 1', attempt 3 (Error: Bind 0x00158d00038e48fa/1 genPowerCfg from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))

Tyrian81 · 2021-01-29T07:58:22Z

I'm running zigbee2mqtt in docker container , where can i find the devices.js only have 3 files in its config folder ?
configuration.yaml, database.db, state.json, log folder

Mr-Groch · 2021-01-30T10:54:46Z

After 2 days still no battery value, and still:

Zigbee2MQTT:error 2021-01-28 22:22:26: Failed to configure 'Pilot do świateł 1', attempt 3 (Error: Bind 0x00158d00038e48fa/1 genPowerCfg from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))

Tyrian81 · 2021-01-30T11:56:18Z

After 2 days still no battery value, and still:

Zigbee2MQTT:error 2021-01-28 22:22:26: Failed to configure 'Pilot do świateł 1', attempt 3 (Error: Bind 0x00158d00038e48fa/1 genPowerCfg from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))

Do your buttons work ?¿

Tyrian81 · 2021-01-30T11:57:14Z

can i packet sniff with zigbee2mqtt ? maybe i can sniff something out ... :)

Mr-Groch · 2021-01-30T12:40:36Z

After 2 days still no battery value, and still:

Zigbee2MQTT:error 2021-01-28 22:22:26: Failed to configure 'Pilot do świateł 1', attempt 3 (Error: Bind 0x00158d00038e48fa/1 genPowerCfg from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))

Do your buttons work ?¿

Yes, buttons are working, action and action_group

Koenkk · 2021-01-30T12:55:16Z

@Mr-Groch instead of repairing force a reconfigure via: https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgerequestdeviceconfigure . Right before doing wakeup the device so by clicking on it and check the logs if OK.

If that doesn't help share the data/database.db entry of this device.

Mr-Groch · 2021-01-30T13:20:55Z

@Mr-Groch instead of repairing force a reconfigure via: https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgerequestdeviceconfigure . Right before doing wakeup the device so by clicking on it and check the logs if OK.

If that doesn't help share the data/database.db entry of this device.

First, response was:

{
  "data": {
    "id": "Pilot do świateł 1"
  },
  "error": "Failed to configure (Bind 0x00158d00038e48fa/1 genPowerCfg from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms))",
  "status": "error"
}

But next each time I repeat configure request, I'm getting instand response:

{
  "data": {
    "id": "Pilot do świateł 1"
  },
  "status": "ok"
}

Weird thing that this device announce itself always after wakeup:

Info MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"Pilot do świateł 1","ieee_address":"0x00158d00038e48fa"},"type":"device_announce"}'
Info MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"Pilot do świateł 1"},"type":"device_announced"}'

Now this device in database.db looks like that:

{"id":18,"type":"EndDevice","ieeeAddr":"0x00158d00038e48fa","nwkAddr":2584,"manufId":4653,"manufName":"Trust International B.V.","powerSource":"Battery","modelId":"ZLL-NonColorController","epList":[1,2],"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,4,3,6,8,4096],"outClusterList":[0,4,3,6,8,4096],"clusters":{"genBasic":{"attributes":{"modelId":"ZLL-NonColorController","manufacturerName":"Trust International B.V.","powerSource":3,"zclVersion":1,"appVersion":3,"stackVersion":1,"hwVersion":1,"dateCode":"20150212","swBuildId":"2000-0003"}}},"binds":[],"configuredReportings":[],"meta":{}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":3,"stackVersion":1,"hwVersion":1,"dateCode":"20150212","swBuildId":"2000-0003","zclVersion":1,"interviewCompleted":true,"meta":{},"lastSeen":1612000432947}

Koenkk · 2021-01-30T14:48:10Z

The database explains a lot, the device does not support the power cluster (ID: 1 is not in the inClusterList) so therefore it cannot provide battery measurements. I removed the configure() entirely so issue will be fixed.

Tyrian81 · 2021-01-30T15:30:34Z

so you made a fix in db file , do i need to update zigbee2mqtt ? or edit file devices.js ?

Koenkk · 2021-01-30T15:41:31Z

Changes will be available in the latest dev branch in a few hours (https://www.zigbee2mqtt.io/how_tos/how-to-switch-to-dev-branch.html)

Tyrian81 · 2021-01-30T15:50:05Z

https://imgur.com/a/HUMjWq1

Have 2 folders with devices.js ? which should be edited ? running in docker

Mr-Groch · 2021-01-30T16:02:38Z

https://imgur.com/a/HUMjWq1

Have 2 folders with devices.js ? which should be edited ? running in docker

Open bash console in docker container (docker exec -it container_name bash) and there find devices.js (find / -name devices.js), next edit it with vi (vi /app/node_modules/zigbee-herdsman-converters/devices.js). If you don't know vi - / to search in file, i for edit mode, esc to exit edit mode, :w to save, to exit :q! )

Tyrian81 · 2021-01-30T16:19:02Z

just deleting those 6 lines should fix it ?

Tyrian81 · 2021-01-30T16:37:18Z

removed the six lines and its not erroring in logs any more , but HA doesn't show actions

Zigbee2MQTT:info 2021-01-30 17:31:05: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x00158d00038e5ff4"},"type":"device_announced"}' ,Zigbee2MQTT:info 2021-01-30 17:30:54: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00158d00038e5ff4","ieee_address":"0x00158d00038e5ff4"},"type":"device_announce"}' ,Zigbee2MQTT:info 2021-01-30 17:30:55: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00158d00038e5ff4","ieee_address":"0x00158d00038e5ff4"},"type":"device_announce"}' ,Zigbee2MQTT:info 2021-01-30 17:30:54: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x00158d00038e5ff4"},"type":"device_announced"}' ,Zigbee2MQTT:info 2021-01-30 17:30:55: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x00158d00038e5ff4"},"type":"device_announced"}' ,Zigbee2MQTT:info 2021-01-30 17:31:05: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00158d00038e5ff4","ieee_address":"0x00158d00038e5ff4"},"type":"device_announce"}'

It does not register button clicks .¿

ramming multiple buttons(phun intended) at the same time gives ;

(node:18) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. ,(node:18) UnhandledPromiseRejectionWarning: Error: SREQ '--> AF - dataRequestExt - {"dstaddrmode":2,"dstaddr":"0x000000000000fffd","destendpoint":242,"dstpanid":0,"srcendpoint":242,"clusterid":33,"transid":2,"options":0,"radius":30,"len":6,"data":{"type":"Buffer","data":[25,3,2,11,254,0]}}' failed with status '(0x11: BUFFER_FULL)' (expected '(0x00: SUCCESS)') , at Znp.<anonymous> (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27) , at Generator.next (<anonymous>) , at fulfilled (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58) ,(node:18) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

Tyrian81 · 2021-01-30T17:47:00Z

`Zigbee2MQTT:info 2021-01-30 18:44:32: Device '0x00158d00038e5ff4' joined
,Zigbee2MQTT:info 2021-01-30 18:44:32: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00158d00038e5ff4","ieee_address":"0x00158d00038e5ff4"},"type":"device_joined"}'
,Zigbee2MQTT:info 2021-01-30 18:44:32: Starting interview of '0x00158d00038e5ff4'
,Zigbee2MQTT:info 2021-01-30 18:44:32: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x00158d00038e5ff4"},"type":"pairing"}'
,Zigbee2MQTT:info 2021-01-30 18:44:32: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00158d00038e5ff4","ieee_address":"0x00158d00038e5ff4","status":"started"},"type":"device_interview"}'
,Zigbee2MQTT:info 2021-01-30 18:44:32: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x00158d00038e5ff4"},"type":"device_connected"}'
,Zigbee2MQTT:info 2021-01-30 18:44:33: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x00158d00038e5ff4","ieee_address":"0x00158d00038e5ff4"},"type":"device_announce"}'
,Zigbee2MQTT:info 2021-01-30 18:44:33: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x00158d00038e5ff4"},"type":"device_announced"}'
,Zigbee2MQTT:info 2021-01-30 18:44:37: Successfully interviewed '0x00158d00038e5ff4', device has successfully been paired
,Zigbee2MQTT:info 2021-01-30 18:44:37: Device '0x00158d00038e5ff4' is supported, identified as: Trust Remote control (ZYCT-202)
,Zigbee2MQTT:info 2021-01-30 18:44:37: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"Remote control","exposes":[{"access":1,"description":"Triggered action (e.g. a button click)","name":"action","property":"action","type":"enum","values":["on","off","stop","up-press","down-press"]},{"access":1,"description":"Link quality (signal strength)","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"ZYCT-202","vendor":"Trust"},"friendly_name":"0x00158d00038e5ff4","ieee_address":"0x00158d00038e5ff4","status":"successful","supported":true},"type":"device_interview"}'
,Zigbee2MQTT:info 2021-01-30 18:44:37: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"description":"Remote control","friendly_name":"0x00158d00038e5ff4","model":"ZYCT-202","supported":true,"vendor":"Trust"},"type":"pairing"}'
,Zigbee2MQTT:info 2021-01-30 18:44:37: MQTT publish: topic 'zigbee2mqtt/bridge/devices', payload '[{"definition":null,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce"],"output":["ssIasZone","ssIasWd"]},"configured_reportings":[]},"110":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"12":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"13":{"bindings":[],"clusters":{"input":["genOta"],"output":[]},"configured_reportings":[]},"2":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"242":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"3":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"4":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"47":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"5":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"6":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[]},"8":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":

Gets added correctly no errors ?

Tyrian81 · 2021-01-30T22:45:08Z

After 2 days still no battery value, and still:

Zigbee2MQTT:error 2021-01-28 22:22:26: Failed to configure 'Pilot do świateł 1', attempt 3 (Error: Bind 0x00158d00038e48fa/1 genPowerCfg from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))

Do your buttons work ?¿

Yes, buttons are working, action and action_group

how did you get the buttons to register , because mine does neatly pair in zigbee2mqtt and gets added in HA , but no buttonpresses, lqi are reported ? i dont have zigbee bulbs so i dont want to pair it directly with the bulbs. just want the button presses to show up in HA zigbee2mqtt

Mr-Groch · 2021-01-31T09:37:46Z

After 2 days still no battery value, and still:
Zigbee2MQTT:error 2021-01-28 22:22:26: Failed to configure 'Pilot do świateł 1', attempt 3 (Error: Bind 0x00158d00038e48fa/1 genPowerCfg from '0x00124b00215fff6e/1' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7))
Do your buttons work ?¿
Yes, buttons are working, action and action_group
how did you get the buttons to register , because mine does neatly pair in zigbee2mqtt and gets added in HA , but no buttonpresses, lqi are reported ? i dont have zigbee bulbs so i dont want to pair it directly with the bulbs. just want the button presses to show up in HA zigbee2mqtt

Do you see in mqtt state topic action and action_group after wakeup and press? If yes, restart HA, autodiscovery sometimes is buggy, and entities are added but not visible until restart

Tyrian81 · 2021-01-31T09:40:35Z

no in the logs of zigbee2mqtt it doesnt register any button presses, it does get interviewed/paired(without errors) and then added in HA with only action and linkquality...?

Mr-Groch · 2021-01-31T09:45:42Z

Try to reset remote (press OFF for about 0 seconds), and pair again (press TWO BULBS button for about 5 seconds) - keep close to coordinator during pairing.. I've also had one time such situation - paired but without button presses, but only once... This device have some trouble with pairing...

Tyrian81 · 2021-02-01T18:13:09Z

Tried everything repairing 10x close distance and 2m but no presses are registered ? did remove the 6 lines which gives the error , but its just not responding to clicks ?
see debug log when pairing , which seems to be ok ...
https://pastebin.ubuntu.com/p/RrffKfVkKH/

except for (no converter available) ?

Received Zigbee message from '0x00158d00038e5ff4', type 'readResponse', cluster 'genBasic', data '{"hwVersion":1}' from endpoint 1 with groupID 0
,Zigbee2MQTT:debug 2021-02-01 18:37:42: No converter available for 'ZYCT-202' with cluster 'genBasic' and type 'readResponse' and data '{"stackVersion":1}'

Koenkk · 2021-02-01T19:05:38Z

@Tyrian81 can you try updating the definition to below and repair it?

{
    zigbeeModel: ['\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000'+
                    '\u0000\u0000\u0000\u0000\u0000', 'ZLL-NonColorController'],
    model: 'ZYCT-202',
    vendor: 'Trust',
    description: 'Remote control',
    fromZigbee: [fz.command_on, fz.command_off_with_effect, fz.legacy.ZYCT202_stop, fz.legacy.ZYCT202_up_down],
    exposes: [e.action(['on', 'off', 'stop', 'brightness_stop', 'brightness_move_up', 'brightness_move_down'])],
    toZigbee: [],
    meta: {configureKey: 2},
    configure: async (device, coordinatorEndpoint, logger) => {
        // Device does not support battery: https://github.com/Koenkk/zigbee2mqtt/issues/5928
        const endpoint = device.getEndpoint(1);
        await reporting.bind(endpoint, coordinatorEndpoint, ['genOnOff']);
        await reporting.onOff(endpoint);
    },
},

See https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html on how to modify devices.js

Tyrian81 · 2021-02-01T19:58:13Z

@Koenkk
looks identical

  {                                                                                                  
        zigbeeModel: ['\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000'+
                      '\u0000\u0000\u0000\u0000\u0000', 'ZLL-NonColorController'],                            
        model: 'ZYCT-202',                   
        vendor: 'Trust',                
        description: 'Remote control',  
        fromZigbee: [fz.command_on, fz.command_off_with_effect, fz.legacy.ZYCT202_stop, fz.legacy.ZYCT202_up_down],
        exposes: [e.action(['on', 'off', 'stop', 'up-press', 'down-press'])],
        toZigbee: [],                                                            
        meta: {configureKey: 2},                                            
        configure: async (device, coordinatorEndpoint, logger) => {
            const endpoint = device.getEndpoint(1);                                   
            await reporting.bind(endpoint, coordinatorEndpoint, ['genOnOff']);    
            await reporting.onOff(endpoint);
        },

Tyrian81 · 2021-02-01T20:01:34Z

@Koenkk
ah i see add , brightness
/app/node_modules/zigbee-herdsman-converters /devices.js is the right one ?

Tyrian81 · 2021-02-01T20:12:42Z

@Koenkk
hmm, added the brightness actions and now i get this error again ?

Zigbee2MQTT:error 2021-02-01 21:10:17: Failed to configure '0x00158d00038e5ff4', attempt 1 (Error: Bind 0x00158d00038e5ff4/1 genOnOff from '0x00124b0018e299ec/1' failed (AREQ - ZDO - bindRsp after 10000ms)
, at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
, at listOnTimeout (internal/timers.js:554:17)
, at processTimers (internal/timers.js:497:7))
,Zigbee2MQTT:info 2021-02-01 21:10:08: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x00158d00038e5ff4"},"type":"device_announced"}'

Koenkk · 2021-02-02T17:57:11Z

@Tyrian81 make sure to wakeup the device and then directly after that configure it via: https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgerequestdeviceconfigure

Mr-Groch · 2021-02-02T18:06:02Z

@Koenkk But this is the same config as initially - and with this config configure will fail

Koenkk · 2021-02-02T19:14:34Z

@Mr-Groch I know, some may require it some don't (it seems?) so if it works I will surround it with a try/catch

Tyrian81 · 2021-02-02T19:36:18Z

{"id": "0x00158d00038e5ff4"} where do i input this ?

Tyrian81 · 2021-02-02T19:41:52Z

docker container /bash ?

Mr-Groch · 2021-02-02T19:44:31Z

MQTT Explorer (you will easly see answer there) or Home Assistant (dev tools, call service mqtt.publish with data):

topic: 'zigbee2mqtt/bridge/request/device/configure'
payload: '{"id": "0x00158d00038e5ff4"}'

Tyrian81 · 2021-02-02T19:57:53Z

hmm now it doesnt even get added in HA, configure gives error ?
Zigbee2MQTT:info 2021-02-02 20:55:23: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure', payload '{"data":{"id":"0x00158d00038e5ff4"},"error":"Device '0x00158d00038e5ff4' cannot be configured","status":"error"}'

Tyrian81 · 2021-02-02T20:10:55Z

@Koenkk @Mr-Groch

This should be done after pairing , and then right after waking (pressing some buttons) right ?

Tyrian81 · 2021-02-02T20:18:40Z

Hmm paired it again with success, got added in HA check, manual configure fails ?

https://pastebin.ubuntu.com/p/5SnnntCphW/

Tyrian81 · 2021-02-02T20:24:23Z

It did do some device_announced

https://pastebin.ubuntu.com/p/zB7DpZXDMR/

Tyrian81 · 2021-02-02T20:33:53Z

https://imgur.com/a/wDgKryY

Koenkk · 2021-02-02T21:10:46Z

What changed between #5928 (comment) and now? In #5928 (comment) you still had the configuring stuff. If you updated to Zigbe2MQTT 1.17.1 make sure to apply the changes as suggested in #5928 (comment).

Also what coordinator are you using?

Tyrian81 · 2021-02-02T21:29:33Z

Coordinator;
https://pastebin.ubuntu.com/p/q4J2RkGhhY/

Re-edited devices.js ;
https://imgur.com/a/qmYbfwt

updated today to new docker image

Tyrian81 · 2021-02-02T21:33:16Z

just repaired it with error , will try and configure it manually now
https://pastebin.ubuntu.com/p/KBs2p9w6g2/

Tyrian81 · 2021-02-02T21:37:21Z

configuring it tries , but alas;
https://pastebin.ubuntu.com/p/r2xYsyRSzT/

Tyrian81 · 2021-02-02T21:42:04Z

after pressing 2 bulbs it seemed to give an device_announced, after that a manual configure gave status "OK"

https://pastebin.ubuntu.com/p/cHN6g8fnMz/

,Zigbee2MQTT:info 2021-02-02 22:43:30: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure', payload '{"data":{"id":"0x00158d00038e5ff4"},"status":"ok"}'
,Zigbee2MQTT:info 2021-02-02 22:44:49: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure', payload '{"data":{"id":"0x00158d00038e5ff4"},"status":"ok"}'

Koenkk · 2021-02-02T21:49:27Z

I see you are running a very old firmware (20180507), updating to https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_Home_1.2/bin/default probably fixes it (no changes are required to the code)

Tyrian81 · 2021-02-02T21:54:56Z

Ah ok, updating firmware via USB possible ? Or would i need UART/serial device ?

Koenkk · 2021-02-03T08:11:30Z

https://www.zigbee2mqtt.io/information/flashing_the_cc2531.html

Mr-Groch added the problem Something isn't working label Jan 27, 2021

Koenkk closed this as completed Jan 30, 2021

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Jan 30, 2021

Fix configure for ZYCT-202 failing. Koenkk/zigbee2mqtt#5928

54b76d4

Trust ZYCT-202 Failed to configure #5928

Trust ZYCT-202 Failed to configure #5928

Comments

Mr-Groch commented Jan 27, 2021

What happened

What did you expect to happen

How to reproduce it (minimal and precise)

Debug info

Tyrian81 commented Jan 28, 2021 • edited Loading

Koenkk commented Jan 28, 2021 • edited Loading

Mr-Groch commented Jan 28, 2021 • edited Loading

Tyrian81 commented Jan 29, 2021 • edited Loading

Mr-Groch commented Jan 30, 2021

Tyrian81 commented Jan 30, 2021

Tyrian81 commented Jan 30, 2021

Mr-Groch commented Jan 30, 2021

Koenkk commented Jan 30, 2021

Mr-Groch commented Jan 30, 2021 • edited Loading

Koenkk commented Jan 30, 2021

Tyrian81 commented Jan 30, 2021

Koenkk commented Jan 30, 2021

Tyrian81 commented Jan 30, 2021 • edited Loading

Mr-Groch commented Jan 30, 2021 • edited Loading

Tyrian81 commented Jan 30, 2021

Tyrian81 commented Jan 30, 2021 • edited Loading

Tyrian81 commented Jan 30, 2021 • edited Loading

Tyrian81 commented Jan 30, 2021 • edited Loading

Mr-Groch commented Jan 31, 2021 • edited Loading

Tyrian81 commented Jan 31, 2021

Mr-Groch commented Jan 31, 2021

Tyrian81 commented Feb 1, 2021 • edited Loading

Koenkk commented Feb 1, 2021

Tyrian81 commented Feb 1, 2021 • edited Loading

Tyrian81 commented Feb 1, 2021

Tyrian81 commented Feb 1, 2021 • edited Loading

Koenkk commented Feb 2, 2021

Mr-Groch commented Feb 2, 2021

Koenkk commented Feb 2, 2021

Tyrian81 commented Feb 2, 2021

Tyrian81 commented Feb 2, 2021

Mr-Groch commented Feb 2, 2021 • edited Loading

Tyrian81 commented Feb 2, 2021

Tyrian81 commented Feb 2, 2021

Tyrian81 commented Feb 2, 2021 • edited Loading

Tyrian81 commented Feb 2, 2021 • edited Loading

Tyrian81 commented Feb 2, 2021

Koenkk commented Feb 2, 2021

Tyrian81 commented Feb 2, 2021 • edited Loading

Tyrian81 commented Feb 2, 2021 • edited Loading

Tyrian81 commented Feb 2, 2021

Tyrian81 commented Feb 2, 2021 • edited Loading

Koenkk commented Feb 2, 2021

Tyrian81 commented Feb 2, 2021 • edited Loading

Koenkk commented Feb 3, 2021

Tyrian81 commented Jan 28, 2021 •

edited

Loading

Koenkk commented Jan 28, 2021 •

edited

Loading

Mr-Groch commented Jan 28, 2021 •

edited

Loading

Tyrian81 commented Jan 29, 2021 •

edited

Loading

Mr-Groch commented Jan 30, 2021 •

edited

Loading

Tyrian81 commented Jan 30, 2021 •

edited

Loading

Mr-Groch commented Jan 30, 2021 •

edited

Loading

Tyrian81 commented Jan 30, 2021 •

edited

Loading

Tyrian81 commented Jan 30, 2021 •

edited

Loading

Tyrian81 commented Jan 30, 2021 •

edited

Loading

Mr-Groch commented Jan 31, 2021 •

edited

Loading

Tyrian81 commented Feb 1, 2021 •

edited

Loading

Tyrian81 commented Feb 1, 2021 •

edited

Loading

Tyrian81 commented Feb 1, 2021 •

edited

Loading

Mr-Groch commented Feb 2, 2021 •

edited

Loading

Tyrian81 commented Feb 2, 2021 •

edited

Loading

Tyrian81 commented Feb 2, 2021 •

edited

Loading

Tyrian81 commented Feb 2, 2021 •

edited

Loading

Tyrian81 commented Feb 2, 2021 •

edited

Loading

Tyrian81 commented Feb 2, 2021 •

edited

Loading

Tyrian81 commented Feb 2, 2021 •

edited

Loading