Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hue dimmer switch #36

Closed
Trakkasure opened this issue May 11, 2018 · 132 comments
Closed

Hue dimmer switch #36

Trakkasure opened this issue May 11, 2018 · 132 comments
Labels
new device support New device support request

Comments

@Trakkasure
Copy link

I hit the setup button on the back of the switch, and successfully paired the switch.
Pressing any button on the switch does nothing.
Interestingly, no light shows in the upper left corner on the device (like it usually does) when a button is pressed.

Is there additional support required in the sniffer firmware required to support this device? It would be great to be able to drop the hue hub all together and use my own home grown solution.

Below is the addition to the devices.js file:

{
'RWL020': {
        model: '324131092621',
	vendor: 'Philips',
	description: 'Hue Dimmer Switch',
        supports: 'single, double, triple, quadruple, many and long click',
        homeassistant: [homeassistant.sensor_click]
    }
}
@ciotlosm
Copy link
Contributor

@Trakkasure can you check the logs and post some messages from there? Are there any WARN?

@Koenkk
Copy link
Owner

Koenkk commented May 11, 2018

This device is not supported yet, so you have to follow: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices

@Koenkk Koenkk added the new device support New device support request label May 11, 2018
@Trakkasure
Copy link
Author

So, i did that.
However, when clicking the switch button to send a signal, nothing happens. typically Hue switches illuminate an LED in the upper right corner when pressing a button.

This does not happen.
Nothing happens in the software when I do press a button.
Below is a debug log:

$ DEBUG=zigbee-shepherd* npm start

> zigbee2mqtt@0.1.0 start /Volumes/SSD/Build/CC2531/zigbee2mqtt
> node index.js

2018-5-15 21:37:23 INFO Starting zigbee-shepherd
  zigbee-shepherd:init zigbee-shepherd booting... +0ms
  zigbee-shepherd:request REQ --> SYS:osalNvRead +18ms
  zigbee-shepherd:request RSP <-- SYS:osalNvRead, status: 0 +23ms
  zigbee-shepherd:request REQ --> SAPI:readConfiguration +13ms
  zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +24ms
  zigbee-shepherd:request REQ --> SAPI:readConfiguration +11ms
  zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +9ms
  zigbee-shepherd:request REQ --> SAPI:readConfiguration +12ms
  zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +19ms
  zigbee-shepherd:request REQ --> SAPI:readConfiguration +11ms
  zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +13ms
  zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +12ms
  zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +4ms
  zigbee-shepherd:init Start the ZNP as a coordinator... +0ms
  zigbee-shepherd:request REQ --> ZDO:startupFromApp +0ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:stateChangeInd +1s
  zigbee-shepherd:init Now the ZNP is a coordinator. +1ms
  zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +0ms
  zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +4ms
  zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +0ms
  zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +3ms
  zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +1ms
  zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +3ms
  zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +0ms
  zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +4ms
  zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +0ms
  zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +3ms
  zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +1ms
  zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +3ms
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +12ms
  zigbee-shepherd:request REQ --> ZDO:activeEpReq +1ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +11ms
  zigbee-shepherd:request REQ --> AF:register +1ms
  zigbee-shepherd:request RSP <-- AF:register, status: 0 +4ms
  zigbee-shepherd:init Register delegator, epId: 1, profId: 260  +12ms
  zigbee-shepherd:request REQ --> AF:register +1ms
  zigbee-shepherd:request RSP <-- AF:register, status: 0 +3ms
  zigbee-shepherd:init Register delegator, epId: 2, profId: 257  +12ms
  zigbee-shepherd:request REQ --> AF:register +1ms
  zigbee-shepherd:request RSP <-- AF:register, status: 0 +4ms
  zigbee-shepherd:init Register delegator, epId: 3, profId: 261  +11ms
  zigbee-shepherd:request REQ --> AF:register +1ms
  zigbee-shepherd:request RSP <-- AF:register, status: 0 +4ms
  zigbee-shepherd:init Register delegator, epId: 4, profId: 263  +11ms
  zigbee-shepherd:request REQ --> AF:register +0ms
  zigbee-shepherd:request RSP <-- AF:register, status: 0 +5ms
  zigbee-shepherd:init Register delegator, epId: 5, profId: 264  +11ms
  zigbee-shepherd:request REQ --> AF:register +0ms
  zigbee-shepherd:request RSP <-- AF:register, status: 0 +5ms
  zigbee-shepherd:init Register delegator, epId: 6, profId: 265  +12ms
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +12ms
  zigbee-shepherd:request REQ --> ZDO:activeEpReq +0ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +13ms
  zigbee-shepherd:request REQ --> ZDO:mgmtPermitJoinReq +1ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:permitJoinInd +10ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:mgmtPermitJoinRsp +2ms
  zigbee-shepherd:init Loading devices from database done. +9ms
  zigbee-shepherd:init zigbee-shepherd is up and ready. +0ms
  zigbee-shepherd:init Network information: +0ms
  zigbee-shepherd:init  >> State:      Coordinator +0ms
  zigbee-shepherd:init  >> Channel:    11 +1ms
  zigbee-shepherd:init  >> PanId:      0x1a62 +0ms
  zigbee-shepherd:init  >> Nwk Addr:   0 +0ms
  zigbee-shepherd:init  >> Ieee Addr:  0x00124b000e896f18 +0ms
  zigbee-shepherd:init  >> Ext. PanId: 0xdddddddddddddddd +0ms
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +0ms
2018-5-15 21:37:24 INFO zigbee-shepherd started
2018-5-15 21:37:24 INFO Connecting to MQTT server at mqtt://10.10.10.83:1883
2018-5-15 21:37:24 INFO zigbee-shepherd ready
2018-5-15 21:37:24 INFO Currently 1 devices are joined:
2018-5-15 21:37:24 INFO 0x00178801020e690e (0x00178801020e690e): 324131092621 - Philips Hue Dimmer Switch
2018-5-15 21:37:25 INFO Connected to MQTT server
2018-5-15 21:37:25 INFO MQTT publish, topic: 'zigbee/bridge/state', payload: 'online'
2018-5-15 21:37:25 WARN `permit_join` set to  `true` in configuration.yaml.
2018-5-15 21:37:25 WARN Allowing new devices to join.
2018-5-15 21:37:25 WARN Set `permit_join` to `false` once you joined all devices.
2018-5-15 21:37:25 INFO Zigbee: allowing new devices to join.
  zigbee-shepherd:request REQ --> ZDO:mgmtPermitJoinReq +366ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:permitJoinInd +19ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:mgmtPermitJoinRsp +4ms

  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +5s

@ghost
Copy link

ghost commented May 16, 2018

Zigate has a list of parameters available for a number of devices that are not supported by zigbee2mqtt yet including the dimmer switch. Is it possible to port them over?
For example, the Hue dimmer
http://zigate.fr/philips-hue-telecommande-compatible-zigate-clusters/

@Koenkk
Copy link
Owner

Koenkk commented May 16, 2018

This looks like the same problem as with the TRADFRI remote control: #14

@dabont
Copy link

dabont commented May 16, 2018

@Koenkk Yes, you are correct. The Hue Dimmer Switch can also directly control the bulbs. Same issue as the Ikea remote.

@Koenkk
Copy link
Owner

Koenkk commented May 16, 2018

We need to find a way to send commands to the coordinator (CC2531): https://github.com/ebaauw/homebridge-hue/wiki/ZigBee-Devices#hue-dimmer-switch

@tb-killa
Copy link
Contributor

Do you mean this type of Switch ?
https://youtu.be/QXBZDUR4QN0?t=44s

@Koenkk
Copy link
Owner

Koenkk commented May 16, 2018

I do

@jasonmhite
Copy link

jasonmhite commented May 26, 2018

I was playing around with this today because I would also like to be able to use the Hue remotes. Obviously it doesn't work, I get the same behavior.

I'm a little fuzzy on what's going on, you're saying that it's because the remote sends commands directly to a bulb, not through the hub even when it's paired? I know the dimmers support standalone operation where it directly controls a bulb without a hub, but I thought it also supported passing events through the hub.

If you can point me in the right direction I can hack on this.

@Koenkk
Copy link
Owner

Koenkk commented May 26, 2018

Reading https://github.com/ebaauw/homebridge-hue/wiki/ZigBee-Devices#hue-dimmer-switch.

'The Hue dimmer switch uses standard ZigBee attribute reporting for the FC00 cluster, to send button events to the Hue bridge. In addition, it sends commands from the 0006 and 0008 clusters, to interact directly with lights.'

Can you check if anything happens when running with DEBUG=* npm start while pressing some buttons on the remote?

@Koenkk
Copy link
Owner

Koenkk commented May 26, 2018

Found this, looks promising! rogro82/com.hue.zigbee@4e2c8ae

@jasonmhite
Copy link

jasonmhite commented May 26, 2018

There's still no output even with debug when pressing buttons. If I hold down the setup button on the remote to pair it I get a message that it has paired. Shortly after, if I press a button it gives me the standard device connecting message, but subsequent button presses have no effect. If you let it sit for a bit and then press a button again you get the connecting message, so it's obviously waking from sleep, but there's no actual actions triggered otherwise. If you I can post a log of this if you want, but I don't see much useful in there.

@Koenkk
Copy link
Owner

Koenkk commented May 27, 2018

Then we need to dive a little bit more in the athom implementation as they are also using zigbee-shepherd (a modified version).

@jasonmhite
Copy link

jasonmhite commented May 27, 2018

I'll have a look and try and learn up too, I'm still pretty new to Zigbee on a technical level, if you have recommended reading I'm keen to know more. The Hue remotes are perfect for what I want to do and I already have a couple, so getting them working would be very nice, plus it's something fun to hack on.

What I'm not really understanding is why there aren't any events triggered when pressing buttons. From looking at the code in the project you linked, it doesn't look like they are doing anything special or different to parse. It kinda makes me think that the remotes are using a different underlying protocol that zigbee-shepherd is ignoring. On the bright side, it does seem to be at least possible to get them working.

@tb-killa
Copy link
Contributor

tb-killa commented Jun 1, 2018

Hi i got my dimmer device today:

Pairing bringout this log entry:

6/1/2018, 6:15:04 PM �[33mWARN�[39m Device with modelID 'RWL021' is not supported.
6/1/2018, 6:15:04 PM �[33mWARN�[39m Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices
6/1/2018, 6:15:04 PM �[33mWARN�[39m Device with modelID 'RWL021' is not supported.
6/1/2018, 6:15:04 PM �[33mWARN�[39m Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices

My ModelID is another one as the original author post by opening!

And my database.db contain this two entrys:

{"id":5,"type":"EndDevice","ieeeAddr":"0x0017880103caab06","nwkAddr":14408,"manufId":4107,"manufName":"Philips","powerSource":"Battery","modelId":"RWL021","epList":[1,2],"status":"online","joinTime":1527869694,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2096,"inClusterList":[0],"outClusterList":[0,3,4,5,6,8],"clusters":{}},"2":{"profId":260,"epId":2,"devId":12,"inClusterList":[0,1,3,15,64512],"outClusterList":[25],"clusters":{}}},"_id":"fotpP5FUoTPffL9h"}
{"id":5,"type":"EndDevice","ieeeAddr":"0x0017880103caab06","nwkAddr":14408,"manufId":4107,"manufName":"Philips","powerSource":"Battery","modelId":"RWL021","epList":[1,2],"status":"online","joinTime":1527869694,"endpoints":{"1":{"profId":49246,"epId":1,"devId":2096,"inClusterList":[0],"outClusterList":[0,3,4,5,6,8],"clusters":{"genBasic":{"dir":{"value":3},"attrs":{"zclVersion":1,"appVersion":2,"stackVersion":1,"hwVersion":1,"manufacturerName":"Philips","modelId":"RWL021","dateCode":"20160302","powerSource":3,"swBuildId":"5.45.1.17846"}},"genIdentify":{"dir":{"value":2},"attrs":{}},"genGroups":{"dir":{"value":2},"attrs":{}},"genScenes":{"dir":{"value":2},"attrs":{}},"genOnOff":{"dir":{"value":2},"attrs":{}},"genLevelCtrl":{"dir":{"value":2},"attrs":{}}}},"2":{"profId":260,"epId":2,"devId":12,"inClusterList":[0,1,3,15,64512],"outClusterList":[25],"clusters":{"64512":{"dir":{"value":1},"attrs":{}},"genBasic":{"dir":{"value":1},"attrs":{"zclVersion":1,"appVersion":2,"stackVersion":1,"hwVersion":1,"manufacturerName":"Philips","modelId":"RWL021","dateCode":"20160302","powerSource":3,"swBuildId":"5.45.1.17846"}},"genPowerCfg":{"dir":{"value":1},"attrs":{"batteryVoltage":30,"batteryPercentageRemaining":200}},"genIdentify":{"dir":{"value":1},"attrs":{}},"genBinaryInput":{"dir":{"value":1},"attrs":{}},"genOta":{"dir":{"value":2},"attrs":{}}}}},"_id":"fotpP5FUoTPffL9h"}

@Koenkk: Do you could use this info ? If I could help you could give me some hints and maybe some code to test and debug :)

@jasonmhite
Copy link

@tb-killa That's better than what I get, I don't even get the "device not supported" message. I wonder if they have changed how the dimmer's work in the later models.

Do you get any messages when pressing buttons on the remote?

@tb-killa
Copy link
Contributor

tb-killa commented Jun 1, 2018

@jasonmhite At this time No because i have to modifiy the "converter" first.

@ciotlosm
Copy link
Contributor

ciotlosm commented Jun 1, 2018

@tb-killa if you have access to your host I can help you hot-patch your container to modify the converter. Just ping me on discord.

@tb-killa
Copy link
Contributor

tb-killa commented Jun 1, 2018

@ciotlosm I follow the guide from the wiki but after insert the needing Code Segment

'RWL021': {
        model: '324131137411',
        vendor: 'Philips',
        description: 'Hue dimmer switch',
        supports: 'on/off, brightness',
        fromZigbee: [],
        toZigbee: [],
    },

nothing return.... like the author of the issue get.
Now we have to digging deeper.

@tb-killa
Copy link
Contributor

tb-killa commented Jun 1, 2018

@Koenkk :
I start my zigbee2mqtt with DEBUG=* npm start

My configuration.yaml file contain "permit_join: false" on startup.
The following Code contain the 4 Button Simultaneous Press on the Remote Control to get this Device into Pairing-Mode:

cc-znp:AREQ <-- ZDO:tcDeviceInd, { nwkaddr: 14408, extaddr: '0x0017880103caab06', parentaddr: 0 } +21s
  zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +21s
  cc-znp:AREQ <-- ZDO:endDeviceAnnceInd, { srcaddr: 14408, nwkaddr: 14408, ieeeaddr: '0x0017880103caab06', capabilities: 128 } +126ms
spinlock: false []
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +147ms
  cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 14408, nwkaddrofinterest: 14408 } +27ms
  serialport write 9 bytes of data +21s
  zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd +7ms
  cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +691ms
  cc-znp:AREQ <-- ZDO:nodeDescRsp, { srcaddr: 14408, status: 0, nwkaddr: 14408, logicaltype_cmplxdescavai_userdescavai: 2, apsflags_freqband: 64, maccapflags: 128, manufacturercode: 4107, maxbuffersize: 71, maxintransfersize: 45, servermask: 0, maxouttransfersize: 45, descriptorcap: 0 } +249ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +938ms
  zigbee-shepherd:request REQ --> ZDO:activeEpReq +4ms
  cc-znp:SREQ --> ZDO:activeEpReq, { dstaddr: 14408, nwkaddrofinterest: 14408 } +10ms
  serialport write 9 bytes of data +951ms
  cc-znp:SRSP <-- ZDO:activeEpReq, { status: 0 } +15ms
  cc-znp:AREQ <-- ZDO:activeEpRsp, { srcaddr: 14408, status: 0, nwkaddr: 14408, activeepcount: 2, activeeplist: <Buffer 01 02> } +484ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +506ms
  zigbee-shepherd:request REQ --> ZDO:simpleDescReq +19ms
  cc-znp:SREQ --> ZDO:simpleDescReq, { dstaddr: 14408, nwkaddrofinterest: 14408, endpoint: 1 } +27ms
  serialport write 10 bytes of data +526ms
  cc-znp:SRSP <-- ZDO:simpleDescReq, { status: 0 } +22ms
  cc-znp:AREQ <-- ZDO:simpleDescRsp, { srcaddr: 14408, status: 0, nwkaddr: 14408, len: 22, endpoint: 1, profileid: 49246, deviceid: 2096, deviceversion: 2, numinclusters: 1, inclusterlist: <Buffer 00 00>, numoutclusters: 6, outclusterlist: <Buffer 00 00 03 00 04 00 06 00 08 00 05 00> } +484ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +513ms
  zigbee-shepherd:request REQ --> ZDO:simpleDescReq +4ms
  cc-znp:SREQ --> ZDO:simpleDescReq, { dstaddr: 14408, nwkaddrofinterest: 14408, endpoint: 2 } +10ms
  serialport write 10 bytes of data +519ms
  cc-znp:SRSP <-- ZDO:simpleDescReq, { status: 0 } +19ms
  cc-znp:AREQ <-- ZDO:simpleDescRsp, { srcaddr: 14408, status: 0, nwkaddr: 14408, len: 20, endpoint: 2, profileid: 260, deviceid: 12, deviceversion: 0, numinclusters: 5, inclusterlist: <Buffer 00 00 01 00 03 00 0f 00 00 fc>, numoutclusters: 1, outclusterlist: <Buffer 19 00> } +510ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +535ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 1 +58ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 1, srcendpoint: 1, clusterid: 0, transid: 1, options: 48, radius: 30, len: 9, data: <Buffer 00 01 00 04 00 05 00 07 00> } +65ms
  serialport write 24 bytes of data +593ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +17ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +22ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 1 } +430ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 1 +440ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 0, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 23, securityuse: 0,timestamp: 3776319, transseqnumber: 0, len: 31, data: <Buffer 18 01 01 04 00 00 42 07 50 68 69 6c 69 70 73 05 00 00 42 06 52 57 4c 30 32 31 07 00 00 30 03> } +24ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +81ms
  zigbee-shepherd Identified Device: { manufacturer: Philips, product: RWL021 } +6ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 2 +35ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 1, srcendpoint: 1, clusterid: 0, transid: 2, options: 48, radius: 30, len: 6, data: <Buffer 00 02 0c 00 00 f0> } +112ms
  serialport write 21 bytes of data +582ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +17ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +22ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 2 } +364ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 2 +365ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 0, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 23, securityuse: 0,timestamp: 3777938, transseqnumber: 0, len: 31, data: <Buffer 18 02 0d 01 00 00 20 01 00 20 02 00 20 03 00 20 04 00 42 05 00 42 06 00 42 07 00 30 00 40 42> } +17ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +176ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 3 +18ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 1, srcendpoint: 1, clusterid: 0, transid: 3, options: 48, radius: 30, len: 13, data: <Buffer 00 03 00 00 00 01 00 02 00 03 00 04 00> } +183ms
  serialport write 28 bytes of data +583ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +26ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +30ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 3 } +291ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 3 +292ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 0, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 23, securityuse: 0,timestamp: 3779556, transseqnumber: 0, len: 35, data: <Buffer 18 03 01 00 00 00 20 01 01 00 00 20 02 02 00 00 20 01 03 00 00 20 01 04 00 00 42 07 50 68 69 6c 69 70 73> } +16ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +63ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 4 +6ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 1, srcendpoint: 1, clusterid: 0, transid: 4, options: 48, radius: 30, len: 11, data: <Buffer 00 04 00 05 00 06 00 07 00 00 40> } +58ms
  serialport write 26 bytes of data +393ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +29ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +33ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 4 } +420ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 4 +421ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 0, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3781193, transseqnumber: 0, len: 49, data: <Buffer 18 04 01 05 00 00 42 06 52 57 4c 30 32 31 06 00 00 42 08 32 30 31 36 30 33 30 32 07 00 00 30 03 00 40 00 42 0c 35 2e 34 35 2e 31 2e 31 37 38 34 36> } +22ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +52ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +0ms
6/1/2018, 8:53:10 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 5 +27ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 1, srcendpoint: 1, clusterid: 3, transid: 5, options: 48, radius: 30, len: 6, data: <Buffer 00 05 0c 00 00 f0> } +60ms
  serialport write 21 bytes of data +527ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +40ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +42ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 5 } +399ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 5 +402ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 3, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3782799, transseqnumber: 0, len: 4, data: <Buffer 18 05 0d 01> } +20ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +25ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +484ms
6/1/2018, 8:53:10 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 6 +12ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 1, srcendpoint: 1, clusterid: 4, transid: 6, options: 48, radius: 30, len: 6, data: <Buffer 00 06 0c 00 00 f0> } +23ms
  serialport write 21 bytes of data +483ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +26ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +30ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 6 } +454ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 6 +454ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 4, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3784432, transseqnumber: 0, len: 4, data: <Buffer 18 06 0d 01> } +10ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +13ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +506ms
6/1/2018, 8:53:11 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 7 +7ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 1, srcendpoint: 1, clusterid: 5, transid: 7, options: 48, radius: 30, len: 6, data: <Buffer 00 07 0c 00 00 f0> } +15ms
  serialport write 21 bytes of data +504ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +25ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +33ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 7 } +466ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 7 +462ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 5, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3786057, transseqnumber: 0, len: 4, data: <Buffer 18 07 0d 01> } +10ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +14ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +517ms
6/1/2018, 8:53:11 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 8 +8ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 1, srcendpoint: 1, clusterid: 6, transid: 8, options: 48, radius: 30, len: 6, data: <Buffer 00 08 0c 00 00 f0> } +15ms
  serialport write 21 bytes of data +515ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +15ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +18ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 8 } +478ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 8 +479ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3787682, transseqnumber: 0, len: 4, data: <Buffer 18 08 0d 01> } +11ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +14ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +525ms
6/1/2018, 8:53:12 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 9 +14ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 1, srcendpoint: 1, clusterid: 8, transid: 9, options: 48, radius: 30, len: 6, data: <Buffer 00 09 0c 00 00 f0> } +21ms
  serialport write 21 bytes of data +525ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +17ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +21ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 9 } +462ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 9 +461ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 8, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3789274, transseqnumber: 0, len: 4, data: <Buffer 18 09 0d 01> } +11ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +15ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +504ms
6/1/2018, 8:53:12 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 10 +21ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 2, srcendpoint: 1, clusterid: 0, transid: 10, options: 48, radius: 30, len: 6, data: <Buffer 00 0a 0c 00 00 f0> } +217ms
  serialport write 21 bytes of data +710ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +20ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +214ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 10 } +284ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 10 +283ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 0, srcaddr: 14408, srcendpoint: 2, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3790956, transseqnumber: 0, len: 31, data: <Buffer 18 0a 0d 01 00 00 20 01 00 20 02 00 20 03 00 20 04 00 42 05 00 42 06 00 42 07 00 30 00 40 42> } +19ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +84ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 11 +9ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 2, srcendpoint: 1, clusterid: 0, transid: 11, options: 48, radius: 30, len: 13, data: <Buffer00 0b 00 00 00 01 00 02 00 03 00 04 00> } +78ms
  serialport write 28 bytes of data +407ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +24ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +28ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 11 } +378ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 11 +382ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 0, srcaddr: 14408, srcendpoint: 2, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3792506, transseqnumber: 0, len: 35, data: <Buffer 18 0b 01 00 00 00 20 01 01 00 00 20 02 02 00 00 20 01 03 00 00 20 01 04 00 00 42 07 50 68 69 6c 69 70 73> } +35ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +118ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 12 +5ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 2, srcendpoint: 1, clusterid: 0, transid: 12, options: 48, radius: 30, len: 11, data: <Buffer00 0c 00 05 00 06 00 07 00 00 40> } +96ms
  serialport write 26 bytes of data +525ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +26ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +30ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 12 } +380ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 12 +380ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 0, srcaddr: 14408, srcendpoint: 2, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3794166, transseqnumber: 0, len: 49, data: <Buffer 18 0c 01 05 00 00 42 06 52 57 4c 30 32 31 06 00 00 42 08 32 30 31 36 30 33 30 32 07 00 00 30 03 00 40 00 42 0c 35 2e 34 35 2e 31 2e 31 37 38 34 36> } +16ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +48ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +2s
6/1/2018, 8:53:14 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 13 +14ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 2, srcendpoint: 1, clusterid: 1, transid: 13, options: 48, radius: 30, len: 6, data: <Buffer 00 0d 0c 00 00 f0> } +50ms
  serialport write 21 bytes of data +472ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +20ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +24ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 13 } +441ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 13 +440ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 1, srcaddr: 14408, srcendpoint: 2, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0,timestamp: 3795829, transseqnumber: 0, len: 10, data: <Buffer 18 0d 0d 01 20 00 20 21 00 20> } +13ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +22ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 14 +5ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 2, srcendpoint: 1, clusterid: 1, transid: 14, options: 48, radius: 30, len: 7, data: <Buffer 00 0e 00 20 00 21 00> } +17ms
  serialport write 22 bytes of data +491ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +30ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +33ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 14 } +472ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 14 +473ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 1, srcaddr: 14408, srcendpoint: 2, dstendpoint: 1, wasbroadcast: 0, linkquality: 18, securityuse: 0,timestamp: 3797489, transseqnumber: 0, len: 13, data: <Buffer 18 0e 01 20 00 00 20 1e 21 00 00 20 c8> } +30ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +47ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +1s
6/1/2018, 8:53:15 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 15 +17ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 2, srcendpoint: 1, clusterid: 3, transid: 15, options: 48, radius: 30, len: 6, data: <Buffer 00 0f 0c 00 00 f0> } +38ms
  serialport write 21 bytes of data +570ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +17ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +20ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 15 } +451ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 15 +453ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 3, srcaddr: 14408, srcendpoint: 2, dstendpoint: 1, wasbroadcast: 0, linkquality: 18, securityuse: 0,timestamp: 3799145, transseqnumber: 0, len: 4, data: <Buffer 18 0f 0d 01> } +11ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +18ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +500ms
6/1/2018, 8:53:16 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 16 +8ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 2, srcendpoint: 1, clusterid: 15, transid: 16, options: 48, radius: 30, len: 6, data: <Buffer00 10 0c 00 00 f0> } +20ms
  serialport write 21 bytes of data +498ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +16ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +19ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 16 } +479ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 16 +480ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 15, srcaddr: 14408, srcendpoint: 2, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0, timestamp: 3800798, transseqnumber: 0, len: 4, data: <Buffer 18 10 0d 01> } +12ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +17ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +524ms
6/1/2018, 8:53:16 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 17 +8ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 2, srcendpoint: 1, clusterid: 25, transid: 17, options: 48, radius: 30, len: 6, data: <Buffer00 11 0c 00 00 f0> } +16ms
  serialport write 21 bytes of data +524ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +16ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +18ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 17 } +484ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 17 +485ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 25, srcaddr: 14408, srcendpoint: 2, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0, timestamp: 3802462, transseqnumber: 0, len: 4, data: <Buffer 18 11 0d 01> } +23ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +28ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +540ms
6/1/2018, 8:53:17 PM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 18 +16ms
  cc-znp:SREQ --> AF:dataRequest, { dstaddr: 14408, destendpoint: 2, srcendpoint: 1, clusterid: 64512, transid: 18, options: 48, radius: 30, len: 6, data: <Buffer 00 12 0c 00 00 f0> } +25ms
  serialport write 21 bytes of data +547ms
  cc-znp:SRSP <-- AF:dataRequest, { status: 0 } +15ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +18ms
  cc-znp:AREQ <-- AF:dataConfirm, { status: 0, endpoint: 1, transid: 18 } +468ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 18 +472ms
  cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 64512, srcaddr: 14408, srcendpoint: 2, dstendpoint: 1, wasbroadcast: 0, linkquality: 21, securityuse: 0, timestamp: 3804111, transseqnumber: 0, len: 4, data: <Buffer 18 12 0d 01> } +11ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +11ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +516ms
6/1/2018, 8:53:17 PM INFO Connecting with device, please wait...
  zigbee-shepherd Device: 0x0017880103caab06 join the network. +29ms
  zigbee2mqtt:controller Recieved zigbee message with data 0x0017880103caab06 +29ms
6/1/2018, 8:53:17 PM INFO New device joined the network!
  zigbee2mqtt:controller Recieved zigbee message with data online +4ms

@Koenkk
Copy link
Owner

Koenkk commented Jun 1, 2018

Do you see anything in the log right after pressing the buttons?

@tb-killa
Copy link
Contributor

tb-killa commented Jun 1, 2018

Sadly No ...

@Koenkk
Copy link
Owner

Koenkk commented Jun 1, 2018

Can this remote be used without a gateway? (so directly paired to a bulb)

@tb-killa
Copy link
Contributor

tb-killa commented Jun 1, 2018

Yes but i buy it standalone. Maybe someone use it in combination.
From what i found so far on different implementations it seems to be that we have to bind the switch explicit to our zigbee-Endpoint.
https://github.com/sticks18/SmartThings---Devices/blob/master/Hue%20Dimmer%20Remote%20as%20Button%20Controller.groovy#L113

@Koenkk
Copy link
Owner

Koenkk commented Jun 1, 2018

That's possible using: https://github.com/zigbeer/zigbee-shepherd/wiki#API_bind

@tb-killa
Copy link
Contributor

tb-killa commented Jun 1, 2018

Give some sample Code or Fragments and i will test it :)

@Koenkk
Copy link
Owner

Koenkk commented Jun 1, 2018

Can you add this to lib/zigbee.js handleReady function.

        // TEMP: Bind Hue dimmer to coordinator.
        let hueremote = '0x0017880103caab06';
        hueremote = this.shepherd.find(hueremote, 1);
        let coordinator = this.shepherd.list().find((d) => d.type === 'Coordinator');
        coordinator = this.shepherd.find(coordinator.ieeeAddr, 1);

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

@tb-killa
Copy link
Contributor

tb-killa commented Jun 2, 2018

Added but after Restarting in Debbing Mode:

6/2/2018, 7:47:43 AM INFO zigbee-shepherd ready
6/2/2018, 7:47:43 AM INFO Connected to MQTT server
6/2/2018, 7:47:43 AM INFO MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +4s
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +4ms
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +2ms
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +4ms
  zigbee-shepherd:request REQ --> ZDO:bindReq +6s
  zigbee-shepherd:request REQ --> ZDO:bindReq +10s
  zigbee-shepherd:request REQ --> ZDO:bindReq +10s
  zigbee-shepherd:request REQ --> ZDO:bindReq +10s
FAILED TO BIND :(

Another question: as you could see i got entrys in my database and insert the dummy converter.
But i could join the device a second one to the zigbee2mqtt .

6/2/2018, 7:50:19 AM INFO Zigbee: allowing new devices to join.
  zigbee-shepherd:request REQ --> ZDO:mgmtPermitJoinReq +2m
  zigbee-shepherd:msgHdlr IND <-- ZDO:permitJoinInd +79ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:mgmtPermitJoinRsp +2ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +5s
spinlock: false []
  zigbee-shepherd:request REQ --> ZDO:nodeDescReq +431ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd +6ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +120ms
  zigbee-shepherd:request REQ --> ZDO:activeEpReq +2ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +627ms
  zigbee-shepherd:request REQ --> ZDO:simpleDescReq +3ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +522ms
  zigbee-shepherd:request REQ --> ZDO:simpleDescReq +3ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +526ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 1 +37ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +32ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 1 +437ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +61ms
  zigbee-shepherd Identified Device: { manufacturer: Philips, product: RWL021 } +6ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 2 +49ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +20ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 2 +381ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +86ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 3 +12ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +21ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 3 +404ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +74ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 4 +12ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +38ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 4 +408ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +83ms
6/2/2018, 7:50:29 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 5 +59ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +19ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 5 +395ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +7ms
6/2/2018, 7:50:30 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 6 +17ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +17ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 6 +466ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +15ms
6/2/2018, 7:50:30 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 7 +18ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +15ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 7 +485ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +26ms
6/2/2018, 7:50:31 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 8 +7ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +21ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 8 +472ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +14ms
6/2/2018, 7:50:31 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 9 +17ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +18ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 9 +483ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +21ms
6/2/2018, 7:50:32 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 10 +18ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +24ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 10 +476ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +76ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 11 +5ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +15ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 11 +435ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +48ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 12 +25ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +23ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 12 +433ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +44ms
6/2/2018, 7:50:33 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 13 +26ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +16ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 13 +447ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +18ms
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 14 +4ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +15ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 14 +488ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +25ms
6/2/2018, 7:50:35 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 15 +15ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +14ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 15 +481ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +12ms
6/2/2018, 7:50:35 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 16 +7ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +14ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 16 +496ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +16ms
6/2/2018, 7:50:36 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 17 +16ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +15ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 17 +485ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +14ms
6/2/2018, 7:50:36 AM INFO Connecting with device, please wait...
  zigbee-shepherd:request REQ --> AF:dataRequest, transId: 18 +9ms
  zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +38ms
  zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 18 +470ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +14ms
6/2/2018, 7:50:37 AM INFO Connecting with device, please wait...
  zigbee-shepherd Device: 0x0017880103caab06 join the network. +21ms
6/2/2018, 7:50:37 AM INFO New device joined the network!

Do you analyse my database entrys ? There we find two EP ID´s insert .

@Koenkk
Copy link
Owner

Koenkk commented Jul 14, 2018

@tb-killa so that means { batteryPercentageRemaining: 200 } = 100%?

@tb-killa
Copy link
Contributor

@Koenkk If we change 200 dec to hex it returns: C8 so if i check via official document it means 100%.

@tb-killa
Copy link
Contributor

@Koenkk This seems to work and its valid:

return {Battery: Math.round(msg.data.data['batteryPercentageRemaining']/2)};

@tb-killa
Copy link
Contributor

Damn: I got the Messages Drops again.
The remote got red led and dely in pressing buttons.
I think it forget their config and go in repairing mode again.

2018-7-15 11:26:35 DEBUG Recieved zigbee message with data "online"
device already in network
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +4s
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +8ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +2ms
2018-7-15 11:26:39 DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":1,"stepsize":30,"transtime":9}}
2018-7-15 11:26:39 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"down-press","brightness":205}'
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +1s
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +8ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +2ms
2018-7-15 11:26:40 DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":30,"transtime":9}}
2018-7-15 11:26:40 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"up-press","brightness":255}'
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +644ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +22ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +2ms
2018-7-15 11:26:41 DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":1,"stepsize":30,"transtime":9}}
2018-7-15 11:26:41 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"down-press","brightness":205}'
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +392ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +8ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +3ms
2018-7-15 11:26:41 DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":30,"transtime":9}}
2018-7-15 11:26:41 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"up-press","brightness":255}'
  zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +715ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +34ms
  zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +6s
spinlock: false []
device already in network
  zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd +22ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +11ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +8ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +10ms
2018-7-15 11:26:48 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}
2018-7-15 11:26:48 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"off"}'
  zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +3s
spinlock: false []
device already in network
  zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd +53ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +9ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +5ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
2018-7-15 11:26:51 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{}}
2018-7-15 11:26:51 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"on"}'
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +2s
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +5ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +2ms
2018-7-15 11:26:53 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{}}
2018-7-15 11:26:53 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"on"}'
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +644ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +7ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +2ms
2018-7-15 11:26:54 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}
2018-7-15 11:26:54 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"off"}'
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +5s
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +5ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
2018-7-15 11:26:59 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{}}
2018-7-15 11:26:59 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"on"}'
  zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +808ms
spinlock: false []
device already in network
  zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd +29ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +25ms
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +5ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
2018-7-15 11:27:00 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{}}
2018-7-15 11:27:00 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"on"}'
  zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +2s
  zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +4ms
  zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +2ms
2018-7-15 11:27:02 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{}}
2018-7-15 11:27:02 INFO MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"Battery":52,"action":"on"}'

@Koenkk
Copy link
Owner

Koenkk commented Jul 15, 2018

@tb-killa could it be a battery problem?

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Jul 15, 2018
@tb-killa
Copy link
Contributor

@Koenkk Maybe, has to check this.
But if i follow this conversation it seems to be a generic problem:
https://community.smartthings.com/t/hue-dimmer-switch-connected-to-st/25840/158
Maybe because original it seems to be a ZHA Device .?

@Koenkk
Copy link
Owner

Koenkk commented Jul 15, 2018

As some seem to have it and some not, could it be the model? Because we have: 'RWL020', 'RWL021'

@tb-killa
Copy link
Contributor

Yes it thought about this too.
Strange report from zigbee2mqtt:
Every "Drop" and "Hangup" from the Device with "Red-LED" this messages come up:

 zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +992ms
spinlock: false []
device already in network

Could we check why this happened ?

@jasonmhite
Copy link

jasonmhite commented Jul 15, 2018

@Koenkk the remote I tested with is an RWL021 and I didn't notice this issue when I was testing it out yesterday. I have another but I think it's also a '21. I only played with it for 10 minutes or so though, does this error show up immediately or do I need to test for longer?

@tb-killa
Copy link
Contributor

You need some more time.
I could trigger this by pushing multiple Times fast the on or off Button.

@arteck
Copy link
Contributor

arteck commented Jul 16, 2018

i have here 2x RWL021 .. no problems .. since 3 days..

@tb-killa
Copy link
Contributor

@Koenkk: Does we should do some more Tests or could we close this and bring in the Device Support as official ;) ?
PS: After i Change my location of my Coordinator i doesn´t got any drops, seems to be the fault.
Hint: We should change as last action the Time of BatteryReport to 3600 seconds max = 1h to conserve the battery!

@Koenkk
Copy link
Owner

Koenkk commented Jul 21, 2018

@tb-killa it's already supported in the dev branch: https://github.com/Koenkk/zigbee2mqtt/tree/dev

Can this issue be closed?

@tb-killa
Copy link
Contributor

If nobody will bring in changes we should close it and merge to Master.

@nunoronconcouto
Copy link

{ groupid: 0,
  clusterid: 6,
  srcaddr: 125,
  srcendpoint: 1,
  dstendpoint: 1,
  wasbroadcast: 0,
  linkquality: 68,
  securityuse: 0,
  timestamp: 11020967,
  transseqnumber: 0,
  len: 3,
  data: { '0': 1, '1': 84, '2': 1 },
  zclMsg: 
   { frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
     manufCode: 0,
     seqNum: 84,
     cmdId: 'on',
     payload: {} } }
cmd { groupid: 0,
  clusterid: 6,
  srcaddr: 125,
  srcendpoint: 1,
  dstendpoint: 1,
  wasbroadcast: 0,
  linkquality: 68,
  securityuse: 0,
  timestamp: 11020967,
  transseqnumber: 0,
  len: 3,
  data: { '0': 1, '1': 84, '2': 1 },
  zclMsg: 
   { frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
     manufCode: 0,
     seqNum: 84,
     cmdId: 'on',
     payload: {} } }
  zigbee2mqtt:info 2018-9-10 01:39:12 MQTT publish, topic: 'zigbee2mqtt/0x0017880103a510d5', payload: '{"battery":100,"linkquality":68,"action":"on"}'

@nunoronconcouto
Copy link

zigbee2mqtt:info 2018-9-10 19:11:05 MQTT publish, topic: 'zigbee2mqtt/0x0017880103a510d5', payload: '{"battery":100,"linkquality":92,"action":"up-press","brightness":105}'
zigbee2mqtt:info 2018-9-10 19:11:06 MQTT publish, topic: 'zigbee2mqtt/0x0017880103a510d5', payload: '{"battery":100,"linkquality":94,"action":"up-press","brightness":155}'
zigbee2mqtt:info 2018-9-10 19:12:39 MQTT publish, topic: 'zigbee2mqtt/0x0017880103a510d5', payload: '{"battery":100,"linkquality":94,"action":"down-press","brightness":105}'
zigbee2mqtt:info 2018-9-10 19:12:39 MQTT publish, topic: 'zigbee2mqtt/0x0017880103a510d5', payload: '{"battery":100,"linkquality":94,"action":"down-press","brightness":155}'

@Curtis777
Copy link

is there any noob "How to get it work" to try them out before i return the remote ?

@directman66
Copy link

The remote control 324131092621 does not respond to button presses. After pairing came only the answer about the connection and battery status.

2019-6-14 20:15:27 - info: Starting zigbee2mqtt version 1.4.0 (commit #927c4db)
2019-6-14 20:15:29 - info: Coordinator firmware version: '20190315'

only once message
zigbee2mqtt/0x0017880104f2abb5 | {"battery":99.5,"linkquality":55}

@hawaltie
Copy link

hawaltie commented Jul 6, 2019

In my case the the hue dimmer switch remote control does respond to button press. In mqtt it reports the following:
zigbee2mqtt/0x0017880102d5ef3c', payload '{"battery":100,"linkquality":39,"counter":1,"brightness":105,"action":"on-press","duration":0
This trigger does not change the state of the remote for some reason, and therefore the related action is not triggered. Anyone a clue why the state is not changed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new device support New device support request
Projects
None yet
Development

No branches or pull requests