Zigbee2mqtt: Can't add Remote Trust/KlikAanKlikUit ZYCT-202

Created on 26 Nov 2018  路  63Comments  路  Source: Koenkk/zigbee2mqtt

I have bought a Trust ZYCT-202 remote control.
Trust zyct-202
this is the same as:
KAKU zyct-202

As coordinator I use a CC2531 with FW version 20181024
After pairing, I see the following notifications in zigbee2mqtt:

zigbee2mqtt:debug 2018-11-26 11:22:44 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-26 11:22:44 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-26 11:22:45 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-26 11:22:51 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-26 11:22:58 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-26 11:23:05 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-26 11:23:12 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-26 11:23:12 Received zigbee message of type 'devIncoming' with data '"0x00158d0001ee2aa1"' of device '' (0x00158d0001ee2aa1) zigbee2mqtt:info 2018-11-26 11:23:12 Device incoming... zigbee2mqtt:info 2018-11-26 11:23:12 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}' zigbee2mqtt:warn 2018-11-26 11:23:12 Device with modelID '' is not supported. zigbee2mqtt:warn 2018-11-26 11:23:12 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices zigbee2mqtt:debug 2018-11-26 11:23:12 Received zigbee message of type 'devStatus' with data '"online"' of device '' (0x00158d0001ee2aa1) zigbee2mqtt:warn 2018-11-26 11:23:12 Device with modelID '' is not supported. zigbee2mqtt:warn 2018-11-26 11:23:12 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices

Do I ever get this device working without a modelID?

I have created an object in node_modules/zigbee-shepherd-converters/devices.js :

// Trust { zigbeeModel: ['ZYCT-202'], model: 'ZYCT-202', vendor: 'Trust', description: 'Remote Controle ', supports: 'switch', fromZigbee: [], toZigbee: [], },

after restarting zigbee2mqtt is see:

zigbee2mqtt:info 2018-11-26 12:12:51 0x00158d0001ee2aa1 (0x00158d0001ee2aa1): unkown - undefined unknown (EndDevice)

if I now press a random button from the remote control, I can not see anything coming in...
Does anyone have an idea how I get this working?

picture hwijers

Most helpful comment

@Koenkk , thank you (and other zigbee2mqtt addicts) very much for this beautiful project and all the time and energy you put into it. I have learned a lot from this again!

picture hwijers on 23 Feb 2019
👍2

All 63 comments

Hi ,
according to the process adding a device you have to add a log line in node_modules/zigbee-shepherd-converters/devices.js, see the proc
cheers

khzd picture khzd on 26 Nov 2018

Can you post the contents of your database.db?

Koenkk picture Koenkk on 26 Nov 2018

Can you post the contents of your database.db?

{"$$indexCreated":{"fieldName":"id","unique":true,"sparse":false}} {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018ed22ee","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1543256425,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"2":{"profId":257,"epId":2,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"3":{"profId":261,"epId":3,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"4":{"profId":263,"epId":4,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"5":{"profId":264,"epId":5,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"6":{"profId":265,"epId":6,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}}},"_id":"PVokl7hv6Y5PTVzl"} {"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0001ee2aa1","nwkAddr":38738,"manufId":4151,"epList":[1,2],"status":"online","joinTime":1543256658,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,3,4,6,8,4096],"outClusterList":[0,3,4,6,8,4096],"clusters":{}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{}}},"_id":"w5iBvCxD94EDRQIP"} {"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0001ee2aa1","nwkAddr":38738,"manufId":4151,"manufName":"\u0000\u0000\u0000","powerSource":"Battery","modelId":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","epList":[1,2],"status":"online","joinTime":1543256658,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,3,4,6,8,4096],"outClusterList":[0,3,4,6,8,4096],"clusters":{}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{}}},"_id":"w5iBvCxD94EDRQIP"} {"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0001ee2aa1","nwkAddr":38738,"manufId":4151,"manufName":"\u0000\u0000\u0000","powerSource":"Battery","modelId":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","epList":[1,2],"status":"online","joinTime":1543256658,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,3,4,6,8,4096],"outClusterList":[0,3,4,6,8,4096],"clusters":{"genBasic":{"dir":{"value":3},"attrs":{}},"genIdentify":{"dir":{"value":3},"attrs":{}},"genGroups":{"dir":{"value":3},"attrs":{}},"genOnOff":{"dir":{"value":3},"attrs":{}},"genLevelCtrl":{"dir":{"value":3},"attrs":{}},"lightLink":{"dir":{"value":3},"attrs":{}}}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{"lightLink":{"dir":{"value":3},"attrs":{}}}}},"_id":"w5iBvCxD94EDRQIP"}

hwijers picture hwijers on 26 Nov 2018

Hi ,
according to the process adding a device you have to add a log line in node_modules/zigbee-shepherd-converters/devices.js, see the proc
cheers

add a log line?
I have followed the procedure How-to-support-new-devices but get stuck in step 2:

restart zigbee2mqtt and trigger some actions on the device

Nothing happens...

hwijers picture hwijers on 26 Nov 2018

Let's start with the on/off buttons.

In devices.js add:

{
        zigbeeModel: ['\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000'],
        model: 'Zigbee remote control',
        vendor: 'Trust',
        description: 'TODO',
        supports: 'TODO',
        fromZigbee: [],
        toZigbee: [],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const cfg = {direction: 0, attrId: 0, dataType: 16, minRepIntval: 0, maxRepIntval: 1000, repChange: 0};
            const actions = [
                (cb) => device.bind('genOnOff', coordinator, cb),
                (cb) => device.foundation('genOnOff', 'configReport', [cfg], foundationCfg, cb),
            ];

            execute(device, actions, callback);
        },
    },
Koenkk picture Koenkk on 27 Nov 2018

I started again with a clean installation (zigbee2mqtt version 0.2.0 (commit # b0d3c2f)).

First pairing without adjustment in node_modules/zigbee-shepherd-converters/devices.js

Log:
zigbee2mqtt:debug 2018-11-28 09:47:39 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:47:39 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:47:39 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:47:40 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:47:40 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:47:40 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:48:10 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:48:10 Received zigbee message of type 'devIncoming' with data '"0x00158d0001ee2aa1"' of device '' (0x00158d0001ee2aa1) zigbee2mqtt:info 2018-11-28 09:48:10 Device incoming... zigbee2mqtt:info 2018-11-28 09:48:10 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}' zigbee2mqtt:warn 2018-11-28 09:48:10 Device with modelID '' is not supported. zigbee2mqtt:warn 2018-11-28 09:48:10 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices zigbee2mqtt:debug 2018-11-28 09:48:10 Received zigbee message of type 'devStatus' with data '"online"' of device '' (0x00158d0001ee2aa1) zigbee2mqtt:warn 2018-11-28 09:48:10 Device with modelID '' is not supported. zigbee2mqtt:warn 2018-11-28 09:48:10 Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices

Database:

{"$$indexCreated":{"fieldName":"id","unique":true,"sparse":false}} {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018ed22ee","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1543394823,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"2":{"profId":257,"epId":2,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"3":{"profId":261,"epId":3,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"4":{"profId":263,"epId":4,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"5":{"profId":264,"epId":5,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"6":{"profId":265,"epId":6,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}}},"_id":"utKG2qzCoAVW01U0"} {"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0001ee2aa1","nwkAddr":4132,"manufId":4151,"epList":[1,2],"status":"online","joinTime":1543394858,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,3,4,6,8,4096],"outClusterList":[0,3,4,6,8,4096],"clusters":{}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{}}},"_id":"yZinE0H0eJFtnYRn"} {"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0001ee2aa1","nwkAddr":4132,"manufId":4151,"manufName":"\u0000\u0000\u0000","powerSource":"Battery","modelId":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","epList":[1,2],"status":"online","joinTime":1543394858,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,3,4,6,8,4096],"outClusterList":[0,3,4,6,8,4096],"clusters":{}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{}}},"_id":"yZinE0H0eJFtnYRn"} {"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0001ee2aa1","nwkAddr":4132,"manufId":4151,"manufName":"\u0000\u0000\u0000","powerSource":"Battery","modelId":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","epList":[1,2],"status":"online","joinTime":1543394858,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,3,4,6,8,4096],"outClusterList":[0,3,4,6,8,4096],"clusters":{"genBasic":{"dir":{"value":3},"attrs":{}},"genIdentify":{"dir":{"value":3},"attrs":{}},"genGroups":{"dir":{"value":3},"attrs":{}},"genOnOff":{"dir":{"value":3},"attrs":{}},"genLevelCtrl":{"dir":{"value":3},"attrs":{}},"lightLink":{"dir":{"value":3},"attrs":{}}}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{"lightLink":{"dir":{"value":3},"attrs":{}}}}},"_id":"yZinE0H0eJFtnYRn"}

Now I have changed the devices.js and removed the database and re-paired the remote.

Log:

zigbee2mqtt:debug 2018-11-28 09:58:59 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:59:00 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:59:00 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:59:00 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:59:01 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:59:01 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:59:31 Received zigbee message of type 'devInterview' with data '"0x00158d0001ee2aa1"' zigbee2mqtt:debug 2018-11-28 09:59:31 Received zigbee message of type 'devIncoming' with data '"0x00158d0001ee2aa1"' of device '' (0x00158d0001ee2aa1) zigbee2mqtt:info 2018-11-28 09:59:31 Device incoming... zigbee2mqtt:info 2018-11-28 09:59:31 MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}' zigbee2mqtt:debug 2018-11-28 09:59:31 Received zigbee message of type 'devStatus' with data '"online"' of device '' (0x00158d0001ee2aa1)

Database:

{"$$indexCreated":{"fieldName":"id","unique":true,"sparse":false}} {"id":1,"type":"Coordinator","ieeeAddr":"0x00124b0018ed22ee","nwkAddr":0,"manufId":0,"epList":[1,2,3,4,5,6],"status":"online","joinTime":1543395509,"endpoints":{"1":{"profId":260,"epId":1,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"2":{"profId":257,"epId":2,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"3":{"profId":261,"epId":3,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"4":{"profId":263,"epId":4,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"5":{"profId":264,"epId":5,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}},"6":{"profId":265,"epId":6,"devId":5,"inClusterList":[],"outClusterList":[],"clusters":{}}},"_id":"Filk6aHf1mZshed2"} {"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0001ee2aa1","nwkAddr":38945,"manufId":4151,"epList":[1,2],"status":"online","joinTime":1543395539,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,3,4,6,8,4096],"outClusterList":[0,3,4,6,8,4096],"clusters":{}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{}}},"_id":"c0VeWWRfYzZWxGgj"} {"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0001ee2aa1","nwkAddr":38945,"manufId":4151,"manufName":"\u0000\u0000\u0000","powerSource":"Battery","modelId":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","epList":[1,2],"status":"online","joinTime":1543395539,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,3,4,6,8,4096],"outClusterList":[0,3,4,6,8,4096],"clusters":{}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{}}},"_id":"c0VeWWRfYzZWxGgj"} {"id":2,"type":"EndDevice","ieeeAddr":"0x00158d0001ee2aa1","nwkAddr":38945,"manufId":4151,"manufName":"\u0000\u0000\u0000","powerSource":"Battery","modelId":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","epList":[1,2],"status":"online","joinTime":1543395539,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2080,"inClusterList":[0,3,4,6,8,4096],"outClusterList":[0,3,4,6,8,4096],"clusters":{"genBasic":{"dir":{"value":3},"attrs":{}},"genIdentify":{"dir":{"value":3},"attrs":{}},"genGroups":{"dir":{"value":3},"attrs":{}},"genOnOff":{"dir":{"value":3},"attrs":{}},"genLevelCtrl":{"dir":{"value":3},"attrs":{}},"lightLink":{"dir":{"value":3},"attrs":{}}}},"2":{"profId":49246,"epId":2,"devId":1010,"inClusterList":[4096],"outClusterList":[4096],"clusters":{"lightLink":{"dir":{"value":3},"attrs":{}}}}},"_id":"c0VeWWRfYzZWxGgj"}

data/configuration.yaml:

devices: '0x00158d0001ee2aa1': friendly_name: TrustRC01 retain: false

You can see that the message "is not supported" is no longer displayed.
So, the remote control is now recognized in the config ...?
But unfortunately, zigbee2mqtt does not respond to buttons...
After a short time:

zigbee2mqtt:error 2018-11-28 10:00:21 Failed to configure TrustRC01 0x00158d0001ee2aa1

I now purchased also a Philips Hue wireless dimmerset Philips Products and this works well.
So the software and coordinator work properly.

The Trust remote control is still preferable to the Philips Hue dimmer because the Trust has more features such as 5 lamp channels and a group button.

After second restart of zigbee2mqtt:

zigbee2mqtt:info 2018-11-28 10:32:37 TrustRC01 (0x00158d0001ee2aa1): Zigbee remote control - Trust TODO (EndDevice)

But unfortunately, zigbee2mqtt does not respond to buttons...

hwijers picture hwijers on 28 Nov 2018

Can you provide the log with DEBUG=* npm start (we need to find out why configuration failed (zigbee2mqtt:error 2018-11-28 10:00:21 Failed to configure TrustRC01 0x00158d0001ee2aa1)?

Koenkk picture Koenkk on 28 Nov 2018

Here is the debug log:
logfile

hwijers picture hwijers on 28 Nov 2018

As far as I understand the log, the bind process goes wrong
I then looked at issue 36 https://github.com/Koenkk/zigbee2mqtt/issues/36.

add this to lib/zigbee.js handleReady function:

    // TEMP: Trust remote to coordinator.
    let trustremote = '0x00158d0001ee2aa1';
    trustremote = this.shepherd.find(trustremote, 1);
    let coordinator = this.shepherd.list().find((d) => d.type === 'Coordinator');
    coordinator = this.shepherd.find(coordinator.ieeeAddr, 1);

    trustremote.bind('genOnOff', coordinator, (err) => {
        if (err) {
            console.log('FAILED TO BIND :(');
        } else {
            console.log('GOOD!');
        }
    });

In the log is see:
FAILED TO BIND :(

hwijers picture hwijers on 28 Nov 2018

can you try with:

{
        zigbeeModel: ['\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000'],
        model: 'Zigbee remote control',
        vendor: 'Trust',
        description: 'TODO',
        supports: 'TODO',
        fromZigbee: [],
        toZigbee: [],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const cfg = {direction: 0, attrId: 0, dataType: 16, minRepIntval: 0, maxRepIntval: 1000, repChange: 0};
            const actions = [
                (cb) => device.foundation('genOnOff', 'configReport', [cfg], foundationCfg, cb),
            ];

            execute(device, actions, callback);
        },
    },
Koenkk picture Koenkk on 29 Nov 2018

unfortunately, no effect...

logfile

hwijers picture hwijers on 29 Nov 2018

AF data request fails, status code: 240. MAC transaction expired.' +0ms -> the device is probably sleeping when the configure commands are executed.

Try repairing, this makes sure that the device is online.

Koenkk picture Koenkk on 29 Nov 2018

I started again with an empty database. Here the whole unpair and repair process.

logfile

hwijers picture hwijers on 29 Nov 2018

It looks like the behaviour of this device is similar to the Ikea Tradfri button. It controls lights directly instead of sending commands to the coordinator. I will give the tradfri remote another try..

Koenkk picture Koenkk on 30 Nov 2018

Remote Manual:
https://www.klikaanklikuit.nl/media/wysiwyg/manuals/71171_1.pdf

Trust/klikaanklikuit Z1 Zigbee Control Station manual:
https://www.klikaanklikuit.nl/media/wysiwyg/manuals/71168-2.pdf

Check page 11. Pairing the remote with the station
The remote control seems to be made to communicate with a central controller.

Thank you for the time you have already invested. I hope you find the solution to get it working.

hwijers picture hwijers on 30 Nov 2018

I repeated the pairing process again and saved the output as HTML. Maybe easier debugging with color codes. I still learn every day to make my posts better ...

logfile in HTML format

maybe you / someone can do something with it...

hwijers picture hwijers on 30 Nov 2018

The picture and 3. CONNECT REMOTE WITH BULB explains that the remote is connected directly to the bulb, which is the same as the TRADFRI remote.

Koenkk picture Koenkk on 1 Dec 2018

Yes, but you can choose.
A. pairing with the bulb: select the channel and hold the ON button. (1st manual)
B. pairing with the controller: hold down the BULBGROUP button. (2nd manual)

hwijers picture hwijers on 1 Dec 2018

Did you pair using the B method?

Koenkk picture Koenkk on 1 Dec 2018

Yes, method B. To be sure, I also tried option A but that does not work.

hwijers picture hwijers on 1 Dec 2018

Any ideas for testing?

hwijers picture hwijers on 8 Dec 2018

Not yet, I still assume it is the same as the tradfri remote.

Koenkk picture Koenkk on 9 Dec 2018

I look forward to an improvement.

ysoyipek picture ysoyipek on 11 Jan 2019

The tradfri remote is now supported, with that knowledge in mind, can you try sniffing the traffic of the remote: https://github.com/Koenkk/zigbee2mqtt/blob/dev/docs/how_tos/how_to_sniff_zigbee_traffic.md ?

Koenkk picture Koenkk on 11 Jan 2019

Nice, I finally got my order from China. I can finally continue. I see traffic in Wireshark and see the group and have added this as coordinator_group to the config but it has no influence. Do i need to capture the whole pair process, or what do you need?

hwijers picture hwijers on 11 Feb 2019

@hwijers only the button presses are interesting.

Koenkk picture Koenkk on 12 Feb 2019

Ok here the capture output file:
On
Dimm Up
Dimm Down
Off

trust zyct-202 pcapng
(Rename back to trust_zyct-202.pcapng)

hwijers picture hwijers on 12 Feb 2019

It's the same as the TRADFRI 5 button remote control. In your case the group is 0xb2bb.

You should add the device here: https://github.com/Koenkk/zigbee2mqtt/blob/dev/lib/extension/coordinatorGroup.js#L8 and then add coordinator_group: 0xb2bb for this device.

Koenkk picture Koenkk on 13 Feb 2019

I already added that "coordinator_group: 0xb2bb".
During the pairing I already get the message "Device with modelID ' ' is not supported".
So, the remote control does not send / has no modelID.

Unfortunately, it does not work.
Any ideas?

hwijers picture hwijers on 13 Feb 2019

@hwijers did you have: https://github.com/Koenkk/zigbee2mqtt/issues/635#issuecomment-442834106 in devices.js?

Koenkk picture Koenkk on 14 Feb 2019

Thanks Koen, I'm a lot closer.

replaced the Ikea remote in /opt/zigbee2mqtt/lib/extension/coordinatorGroup.js :

// Trust remote control
const ZYCT202 = zigbeeShepherdConvertersDevices.find((d) => d.model === 'ZYCT202');
const devices = [ZYCT202];

added a new device to /opt/zigbee2mqtt/node_modules/zigbee-shepherd-converters/devices.js under section _const devices_ :

// Trust Remote
{
    zigbeeModel: ['\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000'],
    model: 'ZYCT202',
    vendor: 'Trust',
    description: 'Remote control',
    supports: 'on, off, stop, up-press, down-press',
    fromZigbee: [
        fz.ZYCT202_on, fz.ZYCT202_off, fz.ZYCT202_stop, fz.ZYCT202_up_down,
    ],
    toZigbee: [],
    configure: (ieeeAddr, shepherd, coordinator, callback) => {
        const device = shepherd.find(ieeeAddr, 1);
        const cfg = {direction: 0, attrId: 0, dataType: 16, minRepIntval: 0, maxRepIntval: 1000, repChange: 0};
        const actions = [
            (cb) => device.foundation('genOnOff', 'configReport', [cfg], foundationCfg, cb),
        ];

        execute(device, actions, callback);
    },
},

added new converters to /opt/zigbee2mqtt/node_modules/zigbee-shepherd-converters/converters/fromZigbee.js under section _const converters_ : 

ZYCT202_on: {
    cid: 'genOnOff',
    type: 'cmdOn',
    convert: (model, msg, publish, options) => {
        return {action: 'on'};
    },
},
ZYCT202_off: {
    cid: 'genOnOff',
    type: 'cmdOffWithEffect',
    convert: (model, msg, publish, options) => {
        return {action: 'off'};
    },
},
ZYCT202_stop: {
    cid: 'genLevelCtrl',
    type: 'cmdStop',
    convert: (model, msg, publish, options) => {
        return {action: 'stop'};
    },
},
ZYCT202_up_down: {
    cid: 'genLevelCtrl',
    type: 'cmdMove',
    convert: (model, msg, publish, options) => {
        const value = msg.data.data['movemode'];
        let action = null;

        if (value === 0) action = {'action': 'up-press'};
        else if (value === 1) action = {'action': 'down-press'};

        return action ? action : null;

   },
},

With the remote control you can operate 5 lamps and 1 group of lamps. 1 remote control has 5 coordinator groups:
1 = 0xb2bb
2 = 0xb2bc
3 = 0xb2bd
4 = 0xb2be
5 = 0xb2bf
Group = 0xbc0

The problem now is that I can only add the remote control 1x to /opt/zigbee2mqtt/data/configuration.yaml and not 2x with a different friendly_name and coordinator_group

Do you have a solution for this?

hwijers picture hwijers on 16 Feb 2019

@hwijers I've took another look at the firmware to check if we cannot just forward all messages (even when the coordinator is not in the group). I managed to workaround this, meaning coordinator_group is not needed anymore.

This should also solve your problems with the multiple groups.

Please check with this firmware: https://github.com/Koenkk/Z-Stack-firmware/tree/dev/coordinator/CC2531/bin (another cool thing about this firmware is that it doesn't require re-pairing of all your devices)

Koenkk picture Koenkk on 17 Feb 2019

I have tested the new firmware and it does work. Regardless of which mode the remote control is set (1,2,3,4,5, or Group) the button on, off, up-press, down-press now work but, I can't use the remote now to control 5 different lamps. That was actually the idea behind this remote control.

So, it would be nice if you can make converters linked to GroupIDs or that a zigbee device is created for each GroupID.

hwijers picture hwijers on 17 Feb 2019

I don't know if this groupID is included, perhaps some changes in zigbee-shepherd are required. You could start with logging the msg here: https://github.com/Koenkk/zigbee-shepherd/blob/master/lib/components/af.js#L581 to check if this is included.

Koenkk picture Koenkk on 18 Feb 2019

Yes, its included. Here the output when I press "on". Here I can see the group ID: Debug output
The GroupID changes when I change the lamp selector as it should.

hwijers picture hwijers on 20 Feb 2019

@hwijers what is logged with

ZYCT202_on: {
    cid: 'genOnOff',
    type: 'cmdOn',
    convert: (model, msg, publish, options) => {
        console.log(msg);
        return {action: 'on'};
    },
},
Koenkk picture Koenkk on 20 Feb 2019

debug output after adding the console.log(msg); to the ZYCT202_on converter.

hwijers picture hwijers on 20 Feb 2019

Can you change https://github.com/Koenkk/zigbee-shepherd/blob/master/lib/shepherd.js#L134 to 

        self.emit('ind', { type: type, endpoints: [ ep ], data: notifData, linkquality: msg.linkquality, groupid: msg.groupid });

and check if the groupid is available in the converter now?

Koenkk picture Koenkk on 20 Feb 2019

Yes:

{ type: 'cmdOn',
endpoints:
[ Endpoint {
isLocal: [Function],
device: [Device],
profId: 49246,
epId: 1,
devId: 2080,
inClusterList: [Array],
outClusterList: [Array],
clusters: [Ziee],
onAfDataConfirm: null,
onAfReflectError: null,
onAfIncomingMsg: null,
onAfIncomingMsgExt: null,
onZclFoundation: null,
onZclFunctional: null,
foundation: [Function],
functional: [Function],
bind: [Function],
unbind: [Function],
read: [Function],
write: [Function],
report: [Function] } ],
data: { cid: 'genOnOff', data: {} },
linkquality: 131,
groupid: 45755 }

hwijers picture hwijers on 20 Feb 2019

Good, so now the groupID can be added to the payload, please put it under the key named: action_group and make a PR to update zigbee-shepherd.

Koenkk picture Koenkk on 20 Feb 2019

Sorry Koen, I've lost you ... Can you give me an example?

Also a PR (Pull Request I assume) is new to me. I like to learn every day .. ;-)

hwijers picture hwijers on 20 Feb 2019

no problem, example:

ZYCT202_on: {
    cid: 'genOnOff',
    type: 'cmdOn',
    convert: (model, msg, publish, options) => {
        return {action: 'on', action_group: msg.groupid};
    },
},
Koenkk picture Koenkk on 21 Feb 2019

Are there more people with such a Trust ZYCT-202 remote?
Does anyone want to sniff his remote traffic: "how to sniff zigbee traffic"
I would like to know if each remote uses the same GroupID's like:
selector position 1 = 0xb2bb
selector position 2 = 0xb2bc
selector position 3 = 0xb2bd
selector position 4 = 0xb2be
selector position 5 = 0xb2bf
Group Button = 0xbc0

hwijers picture hwijers on 21 Feb 2019

@Koenkk:
Nice, now we have the remote control working with lamp selector (GroupID) and action.
This can then be used again in HomeAssistant.

I hope that we will receive a response to the above message.
If the selector always has the same GroupID then a fixed converter can be made for this.
For example, If you then press the ON button with the selector in position 1 can give output "action: 1_on"

hwijers picture hwijers on 21 Feb 2019

@hwijers nice, could you make a pull request for this? In this way we can officially support it (https://help.github.com/en/articles/creating-a-pull-request).

Koenkk picture Koenkk on 21 Feb 2019

Merged, thanks!

Koenkk picture Koenkk on 23 Feb 2019

@Koenkk , thank you (and other zigbee2mqtt addicts) very much for this beautiful project and all the time and energy you put into it. I have learned a lot from this again!

hwijers picture hwijers on 23 Feb 2019
👍2

@hwijers Just to be sure, you paired the remote by holding the group button? Probably this info should be added in the pairing_devices page.

RyuzakiKK picture RyuzakiKK on 17 Mar 2019

@RyuzakiKK , You must have the latest version of zigbee2mqtt and the latest firmware version. Otherwise it doesn't work ..
To be sure, first reset your remote by holding the 0 (off) key for a while (20sec?)

Take the following steps on the ZYCT-202 Remote
a. Hold the remote within 2 meters of the Hue bridge
b. Press & hold the Smart Group button (button with 2 bulbs).
First the LEDs of channels 1, 3 and 5 will blink

hwijers picture hwijers on 18 Mar 2019

Thanks, I created a PR to add the instruction in the pairing section https://github.com/Koenkk/zigbee2mqtt.io/pull/49

RyuzakiKK picture RyuzakiKK on 18 Mar 2019

I have ZYCT-202 and now trying to pair it with zigbee2mqtt:

info: Starting zigbee2mqtt version 1.2.1 (commit #4048cb8)
info: Coordinator firmware version: '20190223'

Following the instructions above I get the following messages into log:

Mar 28 21:25:51 pi3 npm[1862]:   zigbee2mqtt:info 2019-3-28 21:25:51 New device '
Mar 28 21:25:51 pi3 npm[1862]:   zigbee2mqtt:info 2019-3-28 21:25:51 MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":"0x00158d0001314232","meta":{"modelID":"\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000"}}'
Mar 28 21:25:51 pi3 npm[1862]:   zigbee2mqtt:info 2019-3-28 21:25:51 MQTT publish: topic 'homeassistant/sensor/0x00158d0001314232/action/config', payload '{"icon":"mdi:gesture-double-tap","value_template":"{{ value_json.action }}","expire_after":1,"state_topic":"zigbee2mqtt/0x00158d0001314232","json_attributes_topic":"zigbee2mqtt/0x00158d0001314232","name":"0x00158d0001314232_action","unique_id":"0x00158d0001314232_action_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x00158d0001314232","name":"0x00158d0001314232","sw_version":"Zigbee2mqtt 1.2.1","model":"Remote control (ZYCT-202)","manufacturer":"Trust"},"availability_topic":"zigbee2mqtt/bridge/state"}'
Mar 28 21:25:51 pi3 npm[1862]:   zigbee2mqtt:info 2019-3-28 21:25:51 MQTT publish: topic 'homeassistant/sensor/0x00158d0001314232/linkquality/config', payload '{"unit_of_measurement":"-","value_template":"{{ value_json.linkquality }}","state_topic":"zigbee2mqtt/0x00158d0001314232","json_attributes_topic":"zigbee2mqtt/0x00158d0001314232","name":"0x00158d0001314232_linkquality","unique_id":"0x00158d0001314232_linkquality_zigbee2mqtt","device":{"identifiers":"zigbee2mqtt_0x00158d0001314232","name":"0x00158d0001314232","sw_version":"Zigbee2mqtt 1.2.1","model":"Remote control (ZYCT-202)","manufacturer":"Trust"},"availability_topic":"zigbee2mqtt/bridge/state"}'
Mar 28 21:25:52 pi3 npm[1862]:   zigbee2mqtt:warn 2019-3-28 21:25:52 Failed to configure 0x00158d0001314232 (0x00158d0001314232) ('Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.') (attempt #2)
Mar 28 21:25:52 pi3 npm[1862]:   zigbee2mqtt:warn 2019-3-28 21:25:52 This can be ignored if the device is working properly

The device is registered, but clicking buttons will do nothing (according to log). After playing around, I saw the following message

Mar 28 21:28:29 pi3 npm[1862]:   zigbee2mqtt:warn 2019-3-28 21:28:29 Failed to configure 0x00158d0001314232 (0x00158d0001314232) ('Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.') (attempt #3)
Mar 28 21:28:29 pi3 npm[1862]:   zigbee2mqtt:warn 2019-3-28 21:28:29 This can be ignored if the device is working properly

I have not connected any bulbs and would like to connect the remote only to the controller. Is this possibe?

willew picture willew on 28 Mar 2019

@willew I don't know why it is not working for you but I can answer your last question: yes it is possible to pair the remote only with the coordinator. This is how I currently set mine.

Have you tried to remove it, reset the remote and do the pairing again?

RyuzakiKK picture RyuzakiKK on 29 Mar 2019

Yes, I've done this several times (stop server, remove the lines from the configuration, factory reset remote, start server, pair). The remote appears in the configuration always. I've also tried to keep the service awake during the pairingn by clicking the buttons.

But when i click the buttons, no events are shown in the log. I've several xiaomi remotes working ok.

willew picture willew on 29 Mar 2019

I did the whole process once more and now it started working! I think the only difference was that the server was running when I reset the remote. I still see error messages in the log
Mar 30 07:09:55 pi3 npm[1826]: zigbee2mqtt:warn 2019-3-30 07:09:55 Failed to configure tv_trust (0x00158d0001314232) ('Error: AF data request fails, status code: 240. MAC transaction expired.') (attempt #1) Mar 30 07:09:55 pi3 npm[1826]: zigbee2mqtt:warn 2019-3-30 07:09:55 This can be ignored if the device is working properl y

willew picture willew on 30 Mar 2019

Hi @hwijers

Previously you said:

Nice, now we have the remote control working with lamp selector (GroupID) and action.
This can then be used again in HomeAssistant.

I hope that we will receive a response to the above message.
If the selector always has the same GroupID then a fixed converter can be made for this.
For example, If you then press the ON button with the selector in position 1 can give output "action: 1_on"

I'm guessing you didnt get enough responses, as I can see that currently the group is sent in payload to HA, but as far as I can tell there is no way to use it:

e.g.

publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":10,"action":"on","action_group":145}'

"action_group" is not a sensor in HA, and I cant see it in payload of events in node red.
I think a work around is to use the event direct from mqtt topic in node red though... will try it.

So here is me capturing the "On" button for each of the 5 groups:

zigbee2mqtt:info 8/30/2019, 9:46:26 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":"on","action_group":145}'
zigbee2mqtt:info 8/30/2019, 9:46:26 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":""}'
zigbee2mqtt:info 8/30/2019, 9:46:28 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":"on","action_group":146}'
zigbee2mqtt:info 8/30/2019, 9:46:28 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":""}'
zigbee2mqtt:info 8/30/2019, 9:46:29 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":"on","action_group":147}'
zigbee2mqtt:info 8/30/2019, 9:46:29 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":""}'
zigbee2mqtt:info 8/30/2019, 9:46:29 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":"on","action_group":148}'
zigbee2mqtt:info 8/30/2019, 9:46:29 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":""}'
zigbee2mqtt:info 8/30/2019, 9:46:30 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":"on","action_group":149}'
zigbee2mqtt:info 8/30/2019, 9:46:30 PM MQTT publish: topic 'zigbee2mqtt/Trust remote', payload '{"linkquality":104,"action":""}'

So groups 145, 146, 147, 148 and 149
Not sure if this is the same is you or not...? (def not the same as the hex numbers you posted if I convert e.g. 145 to hex).

Also is there a reason why every press sends a second message with a null action after the 1st message?

james-fry picture james-fry on 30 Aug 2019

Just in case anyone sees this, I got groups working in node red with a flow like this:

image

[{"id":"871af3aa.f2eef","type":"switch","z":"3da2c349.0ebdcc","name":"On, off, up, down","property":"payload.action","propertyType":"msg","rules":[{"t":"eq","v":"on","vt":"str"},{"t":"eq","v":"off","vt":"str"},{"t":"eq","v":"up-press","vt":"str"},{"t":"eq","v":"down-press","vt":"str"}],"checkall":"true","repair":true,"outputs":4,"x":870,"y":1240,"wires":[["4ee0c9c1.0fd358"],["f202f877.ff4ae8"],[],[]]},{"id":"4ee0c9c1.0fd358","type":"api-call-service","z":"3da2c349.0ebdcc","name":"Turn On James Bedside Light","server":"b8197728.8ac978","service_domain":"light","service":"turn_on","data":"{\"entity_id\":\"light.bedside_james\"}","mergecontext":"","output_location":"","output_location_type":"none","x":1290,"y":1180,"wires":[[]]},{"id":"f202f877.ff4ae8","type":"api-call-service","z":"3da2c349.0ebdcc","name":"Turn Off James Bedside Lights","server":"b8197728.8ac978","service_domain":"light","service":"turn_off","data":"{\"entity_id\":\"light.bedside_james\"}","mergecontext":"","output_location":"","output_location_type":"none","x":1290,"y":1240,"wires":[[]]},{"id":"35c42d05.81b5e2","type":"mqtt in","z":"3da2c349.0ebdcc","name":"","topic":"zigbee2mqtt/Trust remote","qos":"2","datatype":"auto","broker":"a9c1a622.a79798","x":190,"y":1380,"wires":[["2090a197.5d9bae"]]},{"id":"2090a197.5d9bae","type":"json","z":"3da2c349.0ebdcc","name":"","property":"payload","action":"","pretty":false,"x":430,"y":1380,"wires":[["9a1a1a7c.393cc8"]]},{"id":"9a1a1a7c.393cc8","type":"switch","z":"3da2c349.0ebdcc","name":"Action Group","property":"payload.action_group","propertyType":"msg","rules":[{"t":"eq","v":"145","vt":"str"},{"t":"eq","v":"146","vt":"str"},{"t":"eq","v":"147","vt":"str"},{"t":"eq","v":"148","vt":"str"},{"t":"eq","v":"149","vt":"str"}],"checkall":"true","repair":false,"outputs":5,"x":630,"y":1380,"wires":[["871af3aa.f2eef"],["5625935.1b3176c"],[],[],["2751481a.365828"]]},{"id":"bd59907f.b0f92","type":"api-call-service","z":"3da2c349.0ebdcc","name":"Turn On SmartMi Fan","server":"b8197728.8ac978","version":1,"service_domain":"fan","service":"turn_on","entityId":"fan.xiaomi_smart_fan_2","data":"","dataType":"json","mergecontext":"","output_location":"","output_location_type":"none","mustacheAltTags":false,"x":1260,"y":1300,"wires":[[]]},{"id":"b756e137.6a91c","type":"api-call-service","z":"3da2c349.0ebdcc","name":"Turn Off SmartMi Fan","server":"b8197728.8ac978","version":1,"service_domain":"fan","service":"turn_off","entityId":"fan.xiaomi_smart_fan_2","data":"","dataType":"json","mergecontext":"","output_location":"","output_location_type":"none","mustacheAltTags":false,"x":1260,"y":1360,"wires":[[]]},{"id":"5625935.1b3176c","type":"switch","z":"3da2c349.0ebdcc","name":"On, off, up, down","property":"payload.action","propertyType":"msg","rules":[{"t":"eq","v":"on","vt":"str"},{"t":"eq","v":"off","vt":"str"},{"t":"eq","v":"up-press","vt":"str"},{"t":"eq","v":"down-press","vt":"str"}],"checkall":"true","repair":true,"outputs":4,"x":870,"y":1360,"wires":[["bd59907f.b0f92"],["b756e137.6a91c"],[],[]]},{"id":"2751481a.365828","type":"switch","z":"3da2c349.0ebdcc","name":"On, off, up, down","property":"payload.action","propertyType":"msg","rules":[{"t":"eq","v":"on","vt":"str"},{"t":"eq","v":"off","vt":"str"},{"t":"eq","v":"up-press","vt":"str"},{"t":"eq","v":"down-press","vt":"str"}],"checkall":"true","repair":true,"outputs":4,"x":870,"y":1480,"wires":[["df5ea696.b4e068"],["b345bb23.3a3078"],[],[]]},{"id":"b345bb23.3a3078","type":"api-call-service","z":"3da2c349.0ebdcc","name":"Turn Off Kate Bedside Lights","server":"b8197728.8ac978","version":"1","service_domain":"light","service":"turn_off","entityId":"light.bedside_kate","data":"","dataType":"json","mergecontext":"","output_location":"","output_location_type":"none","mustacheAltTags":false,"x":1280,"y":1480,"wires":[[]]},{"id":"df5ea696.b4e068","type":"api-call-service","z":"3da2c349.0ebdcc","name":"Turn On Kate Bedside Light","server":"b8197728.8ac978","version":"1","service_domain":"light","service":"turn_on","entityId":"light.bedside_kate","data":"","dataType":"json","mergecontext":"","output_location":"","output_location_type":"none","mustacheAltTags":false,"x":1280,"y":1420,"wires":[[]]},{"id":"b8197728.8ac978","type":"server","z":"","name":"Home Assistant instance","legacy":false,"hassio":true,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open","connectionDelay":true},{"id":"a9c1a622.a79798","type":"mqtt-broker","z":"","name":"Mosquitto","broker":"192.168.1.2","port":"1883","tls":"","clientid":"NodeRed","usetls":false,"compatmode":false,"keepalive":"300","cleansession":true,"birthTopic":"","birthQos":"0","birthPayload":"","closeTopic":"","closeQos":"0","closePayload":"","willTopic":"/unxpected_disconnect","willQos":"0","willPayload":""}]

james-fry picture james-fry on 31 Aug 2019
👍1

Thanks for this!
Just received the remote and got it working!
Found out there is another action from the remote called "stop"
This gets triggered when you hold down the dimming up or down function

My groups where different btw, but that's no surprise ;)

{"linkquality":21,"action":"stop","action_group":8785}

MrMennens picture MrMennens on 19 Nov 2019
👍1

I have the same remote, but my modelId shows 'ZLL-NonColorController'. I modified devices.js and changed the original model for this device to ZLL-NonColorController, the remote is recognized but I get this error: Failed to configure '0x00158d00038e6094', attempt 1

Any idea how to fix this?

SilvanLaroo picture SilvanLaroo on 23 Jan 2020

Trying to get this Trust ZYCT-202 working too.
After modifying the devices.js it seems to work somehow, however the configuring failed somehow.
Can someone provide me any clue how to get this working with the the Group-ID

Mar 01 19:18:54 openHABianPi npm[7330]: zigbee2mqtt:info 2020-03-01 19:18:54: MQTT publish: topic 'Home/0x00158d00038e5b58', payload '{"linkquality":94,"action":"off","action_group":23386}'
Mar 01 19:18:54 openHABianPi npm[7330]: zigbee2mqtt:info 2020-03-01 19:18:54: Configuring '0x00158d00038e5b58'
Mar 01 19:19:01 openHABianPi npm[7330]: zigbee2mqtt:info 2020-03-01 19:19:01: MQTT publish: topic 'Home/0x00158d00038e5b58', payload '{"linkquality":92,"action":"on","action_group":23386}'
Mar 01 19:19:04 openHABianPi npm[7330]: zigbee2mqtt:error 2020-03-01 19:19:04: Failed to configure '0x00158d00038e5b58', attempt 2 (Error: Bind 0x00158d00038e5b58/1 genOnOff from '0x00124b0019367ceb/1' failed (Error: AREQ - ZDO - bindRsp after 10000ms)
Mar 01 19:19:04 openHABianPi npm[7330]: at Endpoint. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:235:23)
Mar 01 19:19:04 openHABianPi npm[7330]: at Generator.throw ()
Mar 01 19:19:04 openHABianPi npm[7330]: at rejected (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))
Mar 01 19:19:12 openHABianPi npm[7330]: zigbee2mqtt:info 2020-03-01 19:19:12: MQTT publish: topic 'Home/0x00158d00038e5b58', payload '{"linkquality":92,"action":"off","action_group":23386}'
Mar 01 19:19:12 openHABianPi npm[7330]: zigbee2mqtt:info 2020-03-01 19:19:12: Configuring '0x00158d00038e5b58'
Mar 01 19:19:15 openHABianPi npm[7330]: zigbee2mqtt:info 2020-03-01 19:19:15: MQTT publish: topic 'Home/0x00158d00038e5b58', payload '{"linkquality":94,"action":"on","action_group":23386}'
Mar 01 19:19:22 openHABianPi npm[7330]: zigbee2mqtt:error 2020-03-01 19:19:22: Failed to configure '0x00158d00038e5b58', attempt 3 (Error: Bind 0x00158d00038e5b58/1 genOnOff from '0x00124b0019367ceb/1' failed (Error: AREQ - ZDO - bindRsp after 10000ms)
Mar 01 19:19:22 openHABianPi npm[7330]: at Endpoint. (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:235:23)
Mar 01 19:19:22 openHABianPi npm[7330]: at Generator.throw ()
Mar 01 19:19:22 openHABianPi npm[7330]: at rejected (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65))

janlinders picture janlinders on 1 Mar 2020

Sorry forgot to mention the env.

zigbee2mqtt:info 2020-03-01 17:45:29: Starting zigbee2mqtt version 1.8.0-dev (commit #6245c72)
zigbee2mqtt:info 2020-03-01 17:45:29: Starting zigbee-herdsman...
zigbee2mqtt:debug 2020-03-01 17:45:29: Using zigbee-herdsman with settings: '{"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[20],"networkKey":"HIDDEN"},"databasePath":"/opt/zigbee2mqtt/data/database.db","databaseBackupPath":"/opt/zigbee2mqtt/data/database.db.backup","backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json","serialPort":{"baudRate":115200,"rtscts":true,"path":"/dev/ttyACM0"}}'
zigbee2mqtt:info 2020-03-01 17:45:30: zigbee-herdsman started
zigbee2mqtt:info 2020-03-01 17:45:30: Coordinator firmware version: '{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}}'
zigbee2mqtt:debug 2020-03-01 17:45:30: Zigbee network parameters: {"panID":6754,"extendedPanID":"0xdddddddddddddddd","channel":20}

janlinders picture janlinders on 1 Mar 2020

Trust ZYCT-202 is working now. After a few removals from the network and re-joining it started to work. The on/off and up/down/'stop per selected group-id are working. The part that does not seem to work is the GroupFunction (Double Lamp knob). Nothing is captured in the log.
Would be great if this could be implemented too.

janlinders picture janlinders on 2 Mar 2020

Trust ZYCT-202 fully operational.

Forget my remark about the GroupFunction. The knob with the double lamps is not supposed to send any code. It switches the RC to send another action_group code to indicate to take action (on/off/up-press/down-presss) to ALL the devices.

janlinders picture janlinders on 3 Mar 2020

I recently updated firmware version zStack12 20190608 and zigbee2mqtt version 1.11.0 and the device will no longer pair. Could any one shed some light on why it's unsupported?

Previously running zigbee2mqtt version 1.6.0 - not sure of previous firmware version.

zigbee2mqtt:info 2020-03-07 10:14:54: Device '0x00158d0001314742' joined zigbee2mqtt:info 2020-03-07 10:14:54: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":{"friendly_name":"0x00158d0001314742"}}' zigbee2mqtt:info 2020-03-07 10:14:54: Starting interview of '0x00158d0001314742' zigbee2mqtt:info 2020-03-07 10:14:54: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"0x00158d0001314742"}}' zigbee2mqtt:warn 2020-03-07 10:14:57: Received message from unsupported device with Zigbee model 'undefined' zigbee2mqtt:warn 2020-03-07 10:14:57: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. zigbee2mqtt:warn 2020-03-07 10:14:58: Received message from unsupported device with Zigbee model 'undefined' zigbee2mqtt:warn 2020-03-07 10:14:58: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. zigbee2mqtt:warn 2020-03-07 10:15:00: Received message from unsupported device with Zigbee model 'undefined' zigbee2mqtt:warn 2020-03-07 10:15:00: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. zigbee2mqtt:warn 2020-03-07 10:15:01: Received message from unsupported device with Zigbee model 'undefined' zigbee2mqtt:warn 2020-03-07 10:15:01: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. zigbee2mqtt:warn 2020-03-07 10:15:02: Received message from unsupported device with Zigbee model 'undefined' zigbee2mqtt:warn 2020-03-07 10:15:02: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. zigbee2mqtt:warn 2020-03-07 10:15:02: Received message from unsupported device with Zigbee model 'undefined' zigbee2mqtt:warn 2020-03-07 10:15:02: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. zigbee2mqtt:warn 2020-03-07 10:15:05: Received message from unsupported device with Zigbee model 'undefined' zigbee2mqtt:warn 2020-03-07 10:15:05: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. zigbee2mqtt:error 2020-03-07 10:15:25: Failed to interview '0x00158d0001314742', device has not successfully been paired zigbee2mqtt:info 2020-03-07 10:15:25: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_failed","meta":{"friendly_name":"0x00158d0001314742"}}'

mousemat86 picture mousemat86 on 7 Mar 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

CodeFinder2 picture CodeFinder2  路  4Comments
Koenkk picture Koenkk  路  3Comments
tb-killa picture tb-killa  路  3Comments
andreasbrett picture andreasbrett  路  3Comments
mpuff picture mpuff  路  4Comments