Comments (132)
Koenkk
commented on June 22, 2024
2
Found this, looks promising! rogro82/com.hue.zigbee@4e2c8ae
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
2
In Koenkk/zigbee-herdsman-converters@6ee76c0 I've added support for the configure method. In this method we can do any device specific configuration (if required). configure will be called once for every start of zigbee2mqtt, so either when zigbee2mqtt starts or when the device joins the network.
Example: https://github.com/Koenkk/zigbee-shepherd-converters/blob/master/devices.js#L357
from zigbee2mqtt.
jasonmhite
commented on June 22, 2024
1
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.
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
1
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 :)
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
1
Edit: Dont know what now happend.... but after i restart my zigbee2mqtt instance a second one and let the device in pairing mode it bind it successfully :) :)
6/2/2018, 8:12:34 AM INFO Starting zigbee-shepherd
zigbee-shepherd:init zigbee-shepherd booting... +0ms
zigbee-shepherd:request REQ --> SYS:osalNvRead +118ms
zigbee-shepherd:request RSP <-- SYS:osalNvRead, status: 0 +159ms
zigbee-shepherd:request REQ --> SAPI:readConfiguration +29ms
zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +112ms
zigbee-shepherd:request REQ --> SAPI:readConfiguration +14ms
zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +28ms
zigbee-shepherd:request REQ --> SAPI:readConfiguration +13ms
zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +38ms
zigbee-shepherd:request REQ --> SAPI:readConfiguration +19ms
zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +26ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +16ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +25ms
zigbee-shepherd:init Now the ZNP is a coordinator. +3ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +7ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +34ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +3ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +12ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +4ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +18ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +7ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +17ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +6ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +13ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +21ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +15ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +14ms
zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +52ms
zigbee-shepherd:request REQ --> ZDO:activeEpReq +10ms
zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd +21ms
spinlock: false []
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +43ms
zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd +3ms
zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +2ms
zigbee-shepherd:request REQ --> ZDO:simpleDescReq +9ms
zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +281ms
zigbee-shepherd:request REQ --> ZDO:simpleDescReq +6ms
zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +31ms
zigbee-shepherd:request REQ --> ZDO:simpleDescReq +3ms
zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +70ms
zigbee-shepherd:request REQ --> ZDO:simpleDescReq +2ms
zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +20ms
zigbee-shepherd:request REQ --> ZDO:simpleDescReq +2ms
zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +23ms
zigbee-shepherd:request REQ --> ZDO:simpleDescReq +2ms
zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +30ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +21ms
zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +10ms
zigbee-shepherd:request REQ --> ZDO:activeEpReq +10ms
zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +16ms
zigbee-shepherd:request REQ --> ZDO:activeEpReq +6ms
zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +31ms
zigbee-shepherd:request REQ --> ZDO:mgmtPermitJoinReq +9ms
zigbee-shepherd:msgHdlr IND <-- ZDO:mgmtPermitJoinRsp +33ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +308ms
6/2/2018, 8:12:36 AM ERROR Not connected to MQTT server!
6/2/2018, 8:12:36 AM ERROR Cannot send message: topic: 'zigbee2mqtt/0x00158d00024a48c6', payload: '{"action":"wakeup"}
zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +106ms
zigbee-shepherd:request REQ --> ZDO:simpleDescReq +4ms
zigbee-shepherd:init Loading devices from database done. +48ms
zigbee-shepherd:init zigbee-shepherd is up and ready. +1ms
zigbee-shepherd:init Network information: +1ms
zigbee-shepherd:init >> State: Coordinator +5ms
zigbee-shepherd:init >> Channel: 11 +0ms
zigbee-shepherd:init >> PanId: 0x1a62 +1ms
zigbee-shepherd:init >> Nwk Addr: 0 +1ms
zigbee-shepherd:init >> Ieee Addr: 0x00124b000e896656 +0ms
zigbee-shepherd:init >> Ext. PanId: 0xdddddddddddddddd +1ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +5ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +14ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +3ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +6ms
6/2/2018, 8:12:37 AM INFO zigbee-shepherd started
6/2/2018, 8:12:37 AM INFO Currently 4 devices are joined:
6/2/2018, 8:12:37 AM INFO 0x00158d000183c39a (0x00158d000183c39a): WXKG03LM - Xiaomi Aqara single key wireless wall switch (EndDevice)
6/2/2018, 8:12:37 AM INFO 0x00158d000208ed96 (0x00158d000208ed96): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
6/2/2018, 8:12:37 AM INFO 0x00158d00024a48c6 (0x00158d00024a48c6): MFKZQ01LM - Xiaomi Mi smart home cube (EndDevice)
6/2/2018, 8:12:37 AM INFO 0x0017880103caab06 (0x0017880103caab06): 324131137411 - Philips Hue dimmer switch (EndDevice)
6/2/2018, 8:12:37 AM INFO Connecting to MQTT server at mqtt://192.168.178.21
zigbee-shepherd:request REQ --> ZDO:bindReq +566ms
6/2/2018, 8:12:37 AM INFO zigbee-shepherd ready
zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +37ms
zigbee-shepherd:request REQ --> ZDO:simpleDescReq +5ms
6/2/2018, 8:12:37 AM INFO Connected to MQTT server
6/2/2018, 8:12:37 AM INFO MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +371ms
spinlock: true []
zigbee-shepherd:msgHdlr IND <-- ZDO:bindRsp +18ms
GOOD!
zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp +524ms
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 1 +37ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +17ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 1 +532ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +41ms
zigbee-shepherd Identified Device: { manufacturer: Philips, product: RWL021 } +9ms
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 2 +33ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +23ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 2 +357ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +73ms
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 3 +18ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +20ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 3 +437ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +56ms
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 4 +13ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +19ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 4 +401ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +61ms
6/2/2018, 8:12:40 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 5 +35ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +49ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 5 +390ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +6ms
6/2/2018, 8:12:41 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 6 +10ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +17ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +827ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +9ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +2ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 6 +164ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +15ms
6/2/2018, 8:12:42 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 7 +31ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +18ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 7 +451ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +11ms
6/2/2018, 8:12:42 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 8 +7ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +15ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 8 +513ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +9ms
6/2/2018, 8:12:43 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 9 +6ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +19ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 9 +490ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +14ms
6/2/2018, 8:12:43 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 10 +21ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +17ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 10 +479ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +69ms
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 11 +12ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +21ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 11 +407ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +224ms
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 12 +4ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +16ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 12 +249ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +41ms
6/2/2018, 8:12:45 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 13 +15ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +38ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 13 +404ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +19ms
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 14 +7ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +26ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 14 +480ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +19ms
6/2/2018, 8:12:46 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 15 +21ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +19ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 15 +473ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +14ms
6/2/2018, 8:12:46 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 16 +8ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +18ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 16 +490ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +15ms
6/2/2018, 8:12:47 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 17 +12ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +17ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 17 +492ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +15ms
6/2/2018, 8:12:47 AM INFO Connecting with device, please wait...
zigbee-shepherd:request REQ --> AF:dataRequest, transId: 18 +11ms
zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 +17ms
zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 18 +483ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +12ms
6/2/2018, 8:12:48 AM INFO Connecting with device, please wait...
zigbee-shepherd Device: 0x0017880103caab06 join the network. +15ms
6/2/2018, 8:12:48 AM INFO New device joined the network!
device already in network
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +2s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +986ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +385ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +366ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +1s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +320ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +1s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +575ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +598ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +513ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +402ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +296ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +289ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +262ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +308ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +297ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +245ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +315ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +303ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +312ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +268ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +322ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +301ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +331ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +1m
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +526ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +490ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +470ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +523ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +495ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +616ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +523ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +457ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +475ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +523ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +644ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +505ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +519ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +417ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +489ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +443ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +495ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +426ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +446ms
What have I done so far?:
- Let the device pairing with regulary way .. (return no converter available)
- Insert an dummy converter entry
- reboot the zigbee-instance with start them via
DEBUG=zigbee-shepherd* npm start - insert the Code Segment from @Koenkk and do number 3 a second one.
- while the zigbee2mqtt instance boot up i bring the Hue Dimmer Switch in Pairing-Mode and wait for the "GOOD" Message
Now i could push the On and Off Buttons (I / O) and the LED is light up in Green Color.
Now I get this Message via Debbugging
//Push the ON Button
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +6m
//Push the OFF Button
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +21s
I modifiy the Code to bind also the level-ID and after that it also response via green LED light up by button pressing:
// 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 genOnOff :(');
} else {
console.log('GOOD TO BIND genOnOff !');
}
});
//
hueremote.bind('genLevelCtrl', coordinator, (err) => {
if (err) {
console.log('FAILED TO BIND genLevelCtrl :(');
} else {
console.log('GOOD TO BIND genLevelCtrl !');
}
});
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
1
@Koenkk i will try tomorrow if got some free time. Will report
from zigbee2mqtt.
clockbrain
commented on June 22, 2024
1
Not trying to hijack the issue but I've also got a Phillips Hue dimmer switch (RWL021 model) and I couldn't get it to pair until I tried the hue_remote branch mentioned above.
Here's my device.js entry
{
zigbeeModel: ['RWL021'],
model: '324131137411',
vendor: 'Phillips',
description: 'Hue Dimmer switch',
supports: 'on/off',
fromZigbee: [],
toZigbee: [],
},
And here is the log info when pressing the on button
2018-6-28 18:18:20 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{}}
2018-6-28 18:18:20 WARN No converter available for '324131137411' with cid 'genOnOff' and type 'cmdOn'
And the log info when pressing the off button
2018-6-28 18:18:21 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}
2018-6-28 18:18:21 WARN No converter available for '324131137411' with cid 'genOnOff' and type 'cmdOffWithEffect'
I don't get any response from the two central buttons.
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
1
I got some free time to do some work on zigbee2mqtt.
First of all thx to @Koenkk for this great work:
BTW: I use only this two snapshots:
https://github.com/Koenkk/zigbee-shepherd-converters/commit/043bc66d57c6d13f54b260ac9f9bb7d870f2203c
https://github.com/Koenkk/zigbee-shepherd/commit/bc13accb066c99e5b6658db4ab8f5c0c28b2fa4e
I modified the "devices.js" part like mentioned before inside this thread (log-infos i posted).
{
zigbeeModel: ['RWL020', 'RWL021'],
model: '324131092621',
vendor: 'Philips',
description: 'Hue Dimmer Switch',
supports: 'TODO',
fromZigbee: [fz._324131092621_on, fz._324131092621_off],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const device = shepherd.find(ieeeAddr, 1);
const actions = [
(cb) => device.bind('genOnOff', coordinator, cb),
(cb) => device.bind('genLevelCtrl', coordinator, cb),
];
execute(device, actions, callback);
},
},
after bring the device in pairing mode while zigbee2mqtt starts i could use all four buttons:
7/1/2018, 5:43:29 PM �[32mINFO�[39m zigbee-shepherd ready
7/1/2018, 5:43:29 PM �[32mINFO�[39m Connected to MQTT server
7/1/2018, 5:43:29 PM �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
7/1/2018, 5:47:55 PM �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"on"}'
7/1/2018, 5:47:59 PM �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"off"}'
7/1/2018, 5:48:02 PM �[33mWARN�[39m No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 5:48:02 PM �[33mWARN�[39m Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
7/1/2018, 5:48:03 PM �[33mWARN�[39m No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 5:48:03 PM �[33mWARN�[39m Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
We should now add our genLevelCtrl and the cmdStep inside the fromZigbee.js
Edit: You could use the genLevelCtrl in onhold mode so if you hold them we got multiple cmdStep Messages and a final
7/1/2018, 5:51:13 PM �[33mWARN�[39m No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStop'
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
1
@Koenkk will try it tomorrow.
Look at this, there is battery reporting available :
https://github.com/digitalgecko/mySmartThings/blob/master/devicetypes/digitalgecko/hue-dimmer-switch-zha.src/hue-dimmer-switch-zha.groovy
from zigbee2mqtt.
ciotlosm
commented on June 22, 2024
@Trakkasure can you check the logs and post some messages from there? Are there any WARN?
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
This device is not supported yet, so you have to follow: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices
from zigbee2mqtt.
Trakkasure
commented on June 22, 2024
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
> [email protected] 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
from zigbee2mqtt.
commented on June 22, 2024
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/
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
This looks like the same problem as with the TRADFRI remote control: #14
from zigbee2mqtt.
dabont
commented on June 22, 2024
@Koenkk Yes, you are correct. The Hue Dimmer Switch can also directly control the bulbs. Same issue as the Ikea remote.
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
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
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
Do you mean this type of Switch ?
https://youtu.be/QXBZDUR4QN0?t=44s
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
I do
from zigbee2mqtt.
jasonmhite
commented on June 22, 2024
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.
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
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?
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
Then we need to dive a little bit more in the athom implementation as they are also using zigbee-shepherd (a modified version).
from zigbee2mqtt.
jasonmhite
commented on June 22, 2024
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.
from zigbee2mqtt.
jasonmhite
commented on June 22, 2024
@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?
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@jasonmhite At this time No because i have to modifiy the "converter" first.
from zigbee2mqtt.
ciotlosm
commented on June 22, 2024
@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.
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@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.
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@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
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
Do you see anything in the log right after pressing the buttons?
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
Sadly No ...
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
Can this remote be used without a gateway? (so directly paired to a bulb)
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
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
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
That's possible using: https://github.com/zigbeer/zigbee-shepherd/wiki#API_bind
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
Give some sample Code or Fragments and i will test it :)
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
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!');
}
});from zigbee2mqtt.
tb-killa
commented on June 22, 2024
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 .
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
So that means you can now start writing converters for it? The device binding maybe failed because your device was asleep the first time.
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
With your help we could Show ;)
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
Do you get the no converter available messages now?
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
Sadly no .. the only response if one of the four buttons are pressed are from the Debug as shown.
There are no "no converter available" messages right now .
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
I run my instance again with Debug=* and got this
Button On:
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 15, securityuse: 0,timestamp: 7194027, transseqnumber: 0, len: 3, data: <Buffer 01 49 01> } +14s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +14s
Button Off
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 18, securityuse: 0,timestamp: 7203889, transseqnumber: 0, len: 5, data: <Buffer 01 4a 40 00 00> } +3s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +3s
Button Brighter
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 8, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 15, securityuse: 0,timestamp: 7212381, transseqnumber: 0, len: 7, data: <Buffer 01 4b 02 00 1e 09 00> } +3s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +3s
Button Lower
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 8, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 13, securityuse: 0,timestamp: 7219354, transseqnumber: 0, len: 7, data: <Buffer 01 4c 02 01 1e 09 00> } +2s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +2s
Hope this Informations help ?
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@kirovilya Do you could help ? It seems to be that we have to define some rule logic ?
An example Debug logging.
I pressed 4 times the "ON" button:
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 5, securityuse: 0, timestamp: 12505578, transseqnumber: 0, len: 3, data: <Buffer 01 66 01> } +2m
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +2m
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 0, securityuse: 0, timestamp: 12513423, transseqnumber: 0, len: 3, data: <Buffer 01 67 01> } +2s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +2s
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 0, securityuse: 0, timestamp: 12516683, transseqnumber: 0, len: 3, data: <Buffer 01 68 01> } +1s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +1s
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 0, securityuse: 0, timestamp: 12519914, transseqnumber: 0, len: 3, data: <Buffer 01 69 01> } +1s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +1s
As you could see we got the Buffer 01 [66] [67] [68] [69] 01 -> count consecutively if push
for "OFF" we got this Buffer 01 [6a] [6b] [6c] [6d] 40 00 00 -> count consecutively if push
for "Brighter" and lower there are two states: "push and single tap" and "push and hold".
The Hex String changed on two different states.
On which Definition inside the Code we could add this type of logic parsing ?
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
@tb-killa Here is an example of my log:
Did you see "counter"?
That these are messages from an "unjoined" door sensor ...
And now messages after it join to network:
I think messages do not received by coordinator in some cases... one of them - "sender not joined"...
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@kirovilya See my log above i doesnt See any counter.
From log the device paired and i See reactions while in debug Mode. Maybe we should add at some point inside the Code an console.log(type, msg) to Display the raw output.
@Koenkk do you think this could help?
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
@tb-killa forget "counter" :) I made a mistake. sorry
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
@tb-killa your buffer is:
cl=6 <01 67 01>
cl=6 <01 4a 40 00 00>
cl=8 <01 4b 02 00 1e 09 00>
cl=8 <01 4c 02 01 1e 09 00>
first byte 01 - frameType. 01 - "functional" type
second byte - counter
third byte - command
try put console.log after zigbee-shepherd\lib\components\af.js:693
and after zigbee-shepherd\lib\components\af.js:572
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@kirovilya
I insert your console.log entrys:
Here my results:
Button "ON"
incomingMsg { groupid: 0,
clusterid: 6,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 784085,
transseqnumber: 0,
len: 3,
data: <Buffer 01 c6 01> }
zclIncomingMsg { groupid: 0,
clusterid: 6,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 784085,
transseqnumber: 0,
len: 3,
data: { '0': 1, '1': 198, '2': 1 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 198,
cmdId: 'on',
payload: {} } }
Button "OFF"
incomingMsg { groupid: 0,
clusterid: 6,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 987063,
transseqnumber: 0,
len: 5,
data: <Buffer 01 c7 40 00 00> }
zclIncomingMsg { groupid: 0,
clusterid: 6,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 987063,
transseqnumber: 0,
len: 5,
data: { '0': 1, '1': 199, '2': 64, '3': 0, '4': 0 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 199,
cmdId: 'offWithEffect',
payload: { effectid: 0, effectvariant: 0 } } }
Button "Brighter" Simple Push
incomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1115832,
transseqnumber: 0,
len: 7,
data: <Buffer 01 c8 02 00 1e 09 00> }
zclIncomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1115832,
transseqnumber: 0,
len: 7,
data: { '0': 1, '1': 200, '2': 2, '3': 0, '4': 30, '5': 9, '6': 0 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 200,
cmdId: 'step',
payload: { stepmode: 0, stepsize: 30, transtime: 9 } } }
Button "Brighter" Push and Hold
incomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1258389,
transseqnumber: 0,
len: 7,
data: <Buffer 01 c9 02 00 1e 09 00> }
zclIncomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1258389,
transseqnumber: 0,
len: 7,
data: { '0': 1, '1': 201, '2': 2, '3': 0, '4': 30, '5': 9, '6': 0 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 201,
cmdId: 'step',
payload: { stepmode: 0, stepsize: 30, transtime: 9 } } }
incomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1260892,
transseqnumber: 0,
len: 7,
data: <Buffer 01 ca 02 00 38 09 00> }
zclIncomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1260892,
transseqnumber: 0,
len: 7,
data: { '0': 1, '1': 202, '2': 2, '3': 0, '4': 56, '5': 9, '6': 0 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 202,
cmdId: 'step',
payload: { stepmode: 0, stepsize: 56, transtime: 9 } } }
incomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1263393,
transseqnumber: 0,
len: 7,
data: <Buffer 01 cb 02 00 38 09 00> }
zclIncomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1263393,
transseqnumber: 0,
len: 7,
data: { '0': 1, '1': 203, '2': 2, '3': 0, '4': 56, '5': 9, '6': 0 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 203,
cmdId: 'step',
payload: { stepmode: 0, stepsize: 56, transtime: 9 } } }
incomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1265888,
transseqnumber: 0,
len: 7,
data: <Buffer 01 cc 02 00 38 09 00> }
zclIncomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1265888,
transseqnumber: 0,
len: 7,
data: { '0': 1, '1': 204, '2': 2, '3': 0, '4': 56, '5': 9, '6': 0 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 204,
cmdId: 'step',
payload: { stepmode: 0, stepsize: 56, transtime: 9 } } }
incomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1268393,
transseqnumber: 0,
len: 7,
data: <Buffer 01 cd 02 00 38 09 00> }
zclIncomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1268393,
transseqnumber: 0,
len: 7,
data: { '0': 1, '1': 205, '2': 2, '3': 0, '4': 56, '5': 9, '6': 0 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 205,
cmdId: 'step',
payload: { stepmode: 0, stepsize: 56, transtime: 9 } } }
incomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1270889,
transseqnumber: 0,
len: 7,
data: <Buffer 01 ce 02 00 38 09 00> }
zclIncomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1270889,
transseqnumber: 0,
len: 7,
data: { '0': 1, '1': 206, '2': 2, '3': 0, '4': 56, '5': 9, '6': 0 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 206,
cmdId: 'step',
payload: { stepmode: 0, stepsize: 56, transtime: 9 } } }
incomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1272388,
transseqnumber: 0,
len: 3,
data: <Buffer 01 cf 03> }
zclIncomingMsg { groupid: 0,
clusterid: 8,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 1272388,
transseqnumber: 0,
len: 3,
data: { '0': 1, '1': 207, '2': 3 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 207,
cmdId: 'stop',
payload: {} } }
For the "Lower" Button i could also post Informations but lets first check this one
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@Koenkk Maybe we should add an option for enable extended Zigbee-Package debugging to enable this two console.log entrys if needing.? What do you think ?
I see this the first on at debugging for the "ZB-SmartPlug-1.0.0" so maybe we need it for future work ;)
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
@tb-killa log got from af.js:693 or af.js:572 ?
after successful parsing, code emit ZCL:incomingMsg' and handled in af.js:639 - put next log after here
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@kirovilya : I insert the first as this:
var coord = af.controller.getCoord();
console.log(type, msg)
and the second one as this:
zcl.parse(msg.data, function (err, zclData) {
if (!err)
zclIncomingParsedMsgEmitter(msg, zclData);
console.log(type, msg)
});
Is this the correct ?
The code post above is the output of both console.log entries.
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
I show you the ouput with DEBUG=* npm start and with the simple push on Button "ON":
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 0, securityuse: 0, timestamp: 9180566, transseqnumber: 0, len: 3, data: <Buffer 01 46 01> } +8s
incomingMsg { groupid: 0,
clusterid: 6,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 9180566,
transseqnumber: 0,
len: 3,
data: <Buffer 01 46 01> }
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +8s
zclIncomingMsg { groupid: 0,
clusterid: 6,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 9180566,
transseqnumber: 0,
len: 3,
data: { '0': 1, '1': 70, '2': 1 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 70,
cmdId: 'on',
payload: {} } }
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
@tb-killa :) Well...
I think that we do not get these commands, because in the code, there is no handlers.
"Normal" data comes as a "report" and we see them as attReport. In this case the coordinator comes commands "on", "stop", "step" - he does not know anything about it and therefore does not react - they are essentially addressed not to coordinator, but to devices in the network.
In the af.js:662 I see the processing of one of the commands with the frametype = 1 - the message is sent and further it is caught in zigbee-shepherd\lib\shepherd.js:115 then send it to our controller zigbee-shepherd\lib\shepherd.ws:126
But on the other cmds there is no such logic and therefore these messages are not sent anywhere.
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
@tb-killa try to put after af.js:666
if(frameType === 1 && msg.zclMsg.payload)
af.controller.getShepherd().emit('ind:statusChange', targetEp, msg.clusterid, msg.zclMsg);
and you will get statusChange event with your commands in payload.
It not good solution - only for test
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@kirovilya I insert your code and it work as mentioned.
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 14408, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 0, securityuse: 0, timestamp: 15355185, transseqnumber: 0, len: 3, data: <Buffer 01 63 01> } +8s
incomingMsg { groupid: 0,
clusterid: 6,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 15355185,
transseqnumber: 0,
len: 3,
data: <Buffer 01 63 01> }
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +8s
zclIncomingMsg { groupid: 0,
clusterid: 6,
srcaddr: 14408,
srcendpoint: 1,
dstendpoint: 1,
wasbroadcast: 0,
linkquality: 0,
securityuse: 0,
timestamp: 15355185,
transseqnumber: 0,
len: 3,
data: { '0': 1, '1': 99, '2': 1 },
zclMsg:
{ frameCntl: { frameType: 1, manufSpec: 0, direction: 0, disDefaultRsp: 0 },
manufCode: 0,
seqNum: 99,
cmdId: 'on',
payload: {} } }
zigbee2mqtt:controller Recieved zigbee message with data { cid: 'genOnOff', zoneStatus: undefined } +8s
I got now the Missing Converter Message:
6/2/2018, 6:42:38 PM WARN No converter available for '324131137411' with cid 'genOnOff' and type 'statusChange'
6/2/2018, 6:42:38 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
@tb-killa So, we need new event like 'ind:cmd' with cmd and payload...
Strange, I do not undestand why coordinator received this commands...
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@kirovilya maybe because we Bind Hue dimmer to coordinator via Code? I could do a clean database and remove this special Code Segment and we could look if we get the same result.?
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
maybe because we Bind Hue dimmer to coordinator via Code?
Ah! maybe!
we could look if we got the same result.
Not get :(
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
Ok i remove my old database.db and reactivate the permitjoin.
Comment out the needing code to bind the hue switch to coordinator.
After starting via DEBUG=* npm start i let the device join.
Now if i press one of the four buttons ...... I am presenting ...... nothing.
No reaction like before :(
So yes ..
Strange, I do not undestand why coordinator received this commands...
results from our manual mapping!
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@kirovilya @Koenkk What are the next steps? How do we proceed now?
If we bind the device static via function we receive the "ind:cmd" with payload.
But there is also @kirovilya hacky code segment to allow this.
We should think about an official way to integrate this.
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
We first should find a clean solution on how to add this to af.js.
The binding part can be easily integrated, I'm thinking about model specific handlers, e.g. onStart onJoin, etc.. There we can add the binding code.
from zigbee2mqtt.
jasonmhite
commented on June 22, 2024
So to clarify, what needs to be done to get this working out of the box?
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@jasonmhite someone with the device who wants to help.
I don't have the device myself but I prepared the zigbee2mqtt/zigbee-shepherd code (from input above) to allow supporting this device, from now it should just be a matter of writing converters.
To help, go to zigbee2mqtt folder:
cd node_modules
rm -rf zigbee-shepherd-converters zigbee-shepherd
git clone https://github.com/Koenkk/zigbee-shepherd-converters.git -b hue_remote
git clone https://github.com/Koenkk/zigbee-shepherd.git -b hue_remote
cd zigbee-shepherd
npm install
cd ../zigbee-shepherd-converters
npm installNow start zigbee2mqtt, pair the device, it should now output WARN No converter available for ...blablabla..... Please post the output here (with debug log level in zigbee2mqtt)
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@tb-killa great, thanks!
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@Koenkk what about the af.js patching? Is there some solid Modification prepared against the debugging Code from @kirovilya?
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
I think this is OK: diff: Koenkk/zigbee-shepherd@bc13acc.
@kirovilya can you review this?
from zigbee2mqtt.
ryanbeaton
commented on June 22, 2024
@clockbrain looking like progress. That’s what @Koenkk was looking for
Sent with GitHawk
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
I think this is OK: diff: Koenkk/zigbee-shepherd@bc13acc.
@kirovilya can you review this?
Need more logs... not see 'dispatchIncomingMsg()' in debug log...
It is possible to extend the set of clusters in zcl-id
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@kirovilya why do we need to extend the set of clusters in zcl-id?
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@clockbrain i've updated the code, on and off button should work now. Can you try if the two central buttons also report anything now?
from zigbee2mqtt.
kirovilya
commented on June 22, 2024
@Koenkk if we found new command or attribute. may be it part of zcl-packet
from zigbee2mqtt.
clockbrain
commented on June 22, 2024
@Koenkk tested with the updated code although I did have to adjust 2 lines to reflect that I have the RWL021 model
zigbeeModel: ['RWL021'],
model: '324131137411',
With that change it did work ok but only the top and bottom buttons again. Still no response from the 2 middle buttons.
2018-6-29 17:50:09 DEBUG Using zigbee-shepherd with settings: '{"net":{"panId":6754,"channelList":[11]},"dbPath":"/opt/zigbee2mqtt/data/database.db","sp":{"baudrate":115200,"rtscts":true}}'
2018-6-29 17:50:09 INFO Starting zigbee2mqtt version 0.0.0 (commit #2ba2864)
2018-6-29 17:50:09 INFO Starting zigbee-shepherd
2018-6-29 17:50:09 INFO zigbee-shepherd started
2018-6-29 17:50:09 INFO Currently 0 devices are joined:
2018-6-29 17:50:09 WARN `permit_join` set to `true` in configuration.yaml.
2018-6-29 17:50:09 WARN Allowing new devices to join.
2018-6-29 17:50:09 WARN Set `permit_join` to `false` once you joined all devices.
2018-6-29 17:50:09 INFO Zigbee: allowing new devices to join.
2018-6-29 17:50:09 INFO Connecting to MQTT server at mqtt://192.168.x.x:1883
2018-6-29 17:50:10 INFO zigbee-shepherd ready
2018-6-29 17:50:10 INFO Connected to MQTT server
2018-6-29 17:50:10 INFO MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
spinlock: false []
2018-6-29 17:50:31 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:31 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:32 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:32 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:33 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:34 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:35 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:36 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:37 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:37 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:38 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:38 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:38 DEBUG Recieved zigbee message with data "0x0017880103cb42ce"
2018-6-29 17:50:38 INFO Device incoming...
2018-6-29 17:50:38 INFO MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
2018-6-29 17:50:38 DEBUG Recieved zigbee message with data "online"
2018-6-29 17:50:39 INFO Succesfully configured 0x0017880103cb42ce
2018-6-29 17:50:48 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{}}
2018-6-29 17:50:48 INFO MQTT publish, topic: 'zigbee2mqtt/Dimmer', payload: '{"action":"on"}'
2018-6-29 17:50:50 DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}
2018-6-29 17:50:50 INFO MQTT publish, topic: 'zigbee2mqtt/Dimmer', payload: '{"action":"off"}'
^C2018-6-29 17:51:08 INFO MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'offline'
2018-6-29 17:51:08 INFO Disconnecting from MQTT server
2018-6-29 17:51:08 INFO zigbee-shepherd stopped
from zigbee2mqtt.
clockbrain
commented on June 22, 2024
In case it helps, here is the corresponding database.db entry
{
"id": 2,
"type": "EndDevice",
"ieeeAddr": "0x0017880103cb42ce",
"nwkAddr": 53469,
"manufId": 4107,
"manufName": "Philips",
"powerSource": "Battery",
"modelId": "RWL021",
"epList": [
1,
2
],
"status": "offline",
"joinTime": null,
"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": 28,
"batteryPercentageRemaining": 200
}
},
"genIdentify": {
"dir": {
"value": 1
},
"attrs": {}
},
"genBinaryInput": {
"dir": {
"value": 1
},
"attrs": {}
},
"genOta": {
"dir": {
"value": 2
},
"attrs": {}
}
}
}
},
"_id": "4bIwno26mLBdgLFn"
}
from zigbee2mqtt.
arteck
commented on June 22, 2024
here my
{
"id":14,
"type":"EndDevice",
"ieeeAddr":"0x0017880102e251de",
"nwkAddr":1275,
"manufId":4107,
"manufName":"Philips",
"powerSource":"Battery",
"modelId":"RWL021",
"epList":[
1,
2
],
"status":"offline",
"joinTime":null,
"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":28,
"batteryPercentageRemaining":200
}
},
"genIdentify":{
"dir":{
"value":1
},
"attrs":{
}
},
"genBinaryInput":{
"dir":{
"value":1
},
"attrs":{
}
},
"genOta":{
"dir":{
"value":2
},
"attrs":{
}
}
}
}
},
"_id":"VUSgwF8ffeFm2VX3"
}
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
Can you update again, and add to node_modules/zcl-id/definitions/common.json. https://github.com/zigbeer/zcl-id/blob/master/definitions/common.json#L183, the line: "manuSpecificCluster1": 64512
from zigbee2mqtt.
clockbrain
commented on June 22, 2024
No luck. I did an overall update and then applied the hue_dimmer branch and added the "manuSpecificCluster1" definition as above. Had a bit of trouble at first till I found there are 5 installs of zcl-id so I had to make the change to all of them to be sure.
./node_modules/zcl-id/definitions/common.json
./node_modules/zigbee-shepherd/node_modules/zcl-packet/node_modules/zcl-id/definitions/common.json
./node_modules/zigbee-shepherd/node_modules/zcl-id/definitions/common.json
./node_modules/zigbee-shepherd/node_modules/zive/node_modules/zcl-id/definitions/common.json
./node_modules/zigbee-shepherd/node_modules/ziee/node_modules/zcl-id/definitions/common.json
It now fails with the following error on any button press.
2018-7-1 15:18:10 DEBUG Using zigbee-shepherd with settings: '{"net":{"panId":6754,"channelList":[11]},"dbPath":"/opt/zigbee2mqtt/data/database.db","sp":{"baudrate":115200,"rtscts":true}}'
2018-7-1 15:18:10 INFO Starting zigbee2mqtt version 0.0.0 (commit #7cec5f2)
2018-7-1 15:18:10 INFO Starting zigbee-shepherd
2018-7-1 15:18:11 INFO zigbee-shepherd started
2018-7-1 15:18:11 INFO Currently 1 devices are joined:
2018-7-1 15:18:11 INFO Dimmer (0x0017880103cb42ce): 324131092621 - Philips Hue dimmer Switch (EndDevice)
2018-7-1 15:18:11 WARN `permit_join` set to `true` in configuration.yaml.
2018-7-1 15:18:11 WARN Allowing new devices to join.
2018-7-1 15:18:11 WARN Set `permit_join` to `false` once you joined all devices.
2018-7-1 15:18:11 INFO Zigbee: allowing new devices to join.
2018-7-1 15:18:11 INFO Connecting to MQTT server at mqtt://192.168.1.6:1883
2018-7-1 15:18:11 INFO zigbee-shepherd ready
2018-7-1 15:18:11 INFO Connected to MQTT server
2018-7-1 15:18:11 INFO MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/zcl-packet/lib/functional.js:34
throw new Error('Unrecognized command');
^
Error: Unrecognized command
at new FuncPayload (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/zcl-packet/lib/functional.js:34:15)
at /opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/zcl-packet/lib/zcl.js:33:22
at Dissolve.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/zcl-packet/lib/zcl.js:121:9)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Dissolve.emit (events.js:211:7)
at Dissolve.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/dissolve-chunks/index.js:73:29)
at emitNone (events.js:106:13)
at Dissolve.emit (events.js:208:7)
at emitReadable_ (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/dissolve/node_modules/readable-stream/lib/_stream_readable.js:456:10)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2018-07-01T05_18_21_031Z-debug.log
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@tb-killa great!
- When pressing once, do you also get a cmdStop?
- Could you run with debug logging enabled and provide the output?
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@Koenkk
I will post some log for you.
This is press and hold "brighter" and then leave the button:
7/1/2018, 6:11:00 PM INFO Succesfully configured 0x0017880103caab06
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +191ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +20ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/1/2018, 6:11:00 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:11:00 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:11:00 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +777ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +15ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +2ms
7/1/2018, 6:11:01 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:11:01 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:11:01 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +776ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +7ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/1/2018, 6:11:01 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:11:01 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:11:01 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +788ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +12ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +12ms
7/1/2018, 6:11:02 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:11:02 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:11:02 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +778ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +14ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/1/2018, 6:11:03 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:11:03 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:11:03 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +961ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +8ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/1/2018, 6:11:04 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:11:04 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:11:04 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +614ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +13ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/1/2018, 6:11:05 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:11:05 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:11:05 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +784ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +16ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +5ms
7/1/2018, 6:11:05 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:11:05 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:11:05 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +315ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +15ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/1/2018, 6:11:06 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{}}
7/1/2018, 6:11:06 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStop'
7/1/2018, 6:11:06 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
This if hold the lower button and then leave:
7/1/2018, 6:12:46 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":30,"transtime":9}}
7/1/2018, 6:12:46 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:12:46 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +736ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +8ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/1/2018, 6:12:47 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:12:47 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:12:47 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +789ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +9ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/1/2018, 6:12:47 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":56,"transtime":9}}
7/1/2018, 6:12:47 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:12:47 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +137ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +13ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +2ms
7/1/2018, 6:12:48 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{}}
7/1/2018, 6:12:48 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStop'
7/1/2018, 6:12:48 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@Koenkk because of your questions above:
This is the log if i pressed once (first brighter then lower)
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +2m
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +11ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +2ms
7/1/2018, 6:14:23 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":30,"transtime":9}}
7/1/2018, 6:14:23 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:14:23 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +8s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +9ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/1/2018, 6:14:31 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":1,"stepsize":30,"transtime":9}}
7/1/2018, 6:14:31 PM WARN No converter available for '324131092621' with cid 'genLevelCtrl' and type 'cmdStep'
7/1/2018, 6:14:31 PM WARN Please see: https://github.com/Koenkk/zigbee2mqtt/wiki/How-to-support-new-devices.
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
data with stepmode: 0 is for heigher and with 1 is lower.
var direction = data.stepmode === 0 ? 'up' : 'down'; // 0=up,1=down
stepsize defined the single-press or push-and-hold state
var mode = data.stepsize === 30 ? 'press' : 'hold'; // 30=press,56=hold
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@tb-killa can you update and check if the dimming works?
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@Koenkk Nice .. work great.
7/2/2018, 8:13:55 PM DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{}}
7/2/2018, 8:13:55 PM INFO MQTT publish, topic: 'zigbee2mqtt/Philips-Hue-Switch', payload: '{"action":"on"}'
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +1s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +188ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +19ms
7/2/2018, 8:13:56 PM DEBUG Recieved zigbee message with data {"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}
7/2/2018, 8:13:56 PM INFO MQTT publish, topic: 'zigbee2mqtt/Philips-Hue-Switch', payload: '{"action":"off"}'
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +1s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +20ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/2/2018, 8:13:57 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":30,"transtime":9}}
7/2/2018, 8:13:57 PM INFO MQTT publish, topic: 'zigbee2mqtt/Philips-Hue-Switch', payload: '{"brightness":255}'
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +2s
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +12ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +9ms
7/2/2018, 8:13:59 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":1,"stepsize":30,"transtime":9}}
7/2/2018, 8:13:59 PM INFO MQTT publish, topic: 'zigbee2mqtt/Philips-Hue-Switch', payload: '{"brightness":205}'
zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] +767ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +6ms
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
7/2/2018, 8:14:00 PM DEBUG Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":1,"stepsize":30,"transtime":9}}
7/2/2018, 8:14:00 PM INFO MQTT publish, topic: 'zigbee2mqtt/Philips-Hue-Switch', payload: '{"brightness":155}'
But it think we should give the User the Choice what Attributes we should transport.
So i think we should transport via mqtt:
up
down
up-pressed-counter (since pressed event timer starts)
down-pressed-counter (since pressed event timer starts)
BTW: This Remote Device is also a great and cheap 4 Button Remote with "two buttons with multiple states".
So the WAF Factor seems to be great ;)
I will use them with some selfprinted Icons on Front for the different Rooms.
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@tb-killa implemented, possible actions are: up-press, down-press, up-hold, down-hold, up-hold-release, down-hold-release.
Can you also test if the brightness works when holding the buttons?
from zigbee2mqtt.
clockbrain
commented on June 22, 2024
I'm still keen to get this working but am a bit lost with the various patches. Is there a simple list of the patches I should apply to test this. (Not sure if I applied the previous code correctly).
Or if it is close to working I can wait till the patches are checked in and I'll try again from the master.
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@clockbrain all code is in this branch: https://github.com/Koenkk/zigbee-shepherd-converters/tree/hue_remote
from zigbee2mqtt.
clockbrain
commented on June 22, 2024
Thanks but it still doesn't want to cooperate with me. I can pair the dimmer but as soon as I press any button I get:
/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/zcl-packet/lib/functional.js:33
throw new Error('Unrecognized command');
^
Error: Unrecognized command
at new FuncPayload (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/zcl-packet/lib/functional.js:33:15)
at /opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/zcl-packet/lib/zcl.js:33:22
at Dissolve.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/zcl-packet/lib/zcl.js:121:9)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Dissolve.emit (events.js:211:7)
at Dissolve.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/dissolve-chunks/index.js:73:29)
at emitNone (events.js:106:13)
at Dissolve.emit (events.js:208:7)
at emitReadable_ (/opt/zigbee2mqtt/node_modules/zigbee-shepherd/node_modules/dissolve/node_modules/readable-stream/lib/_stream_readable.js:456:10)
I've refreshed using this sequence:
# Update
git checkout HEAD -- npm-shrinkwrap.json
git pull
rm -rf node_modules
npm install
cd node_modules
rm -rf zigbee-shepherd-converters zigbee-shepherd
git clone https://github.com/Koenkk/zigbee-shepherd-converters.git -b hue_remote
git clone https://github.com/Koenkk/zigbee-shepherd.git -b hue_remote
cd zigbee-shepherd
npm install
cd ../zigbee-shepherd-converters
npm install
I also add the line
"manuSpecificCluster1": 64512
to zcl-id/definitions/common.json as advised earlier. I make sure there is only 1 copy of zcl-id in the tree.
So, I've done this whole sequence about 5 times now and same result each time. I've also reflashed the firmware a few times in case that was the problem but would have to say I'm stuck at this point.
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@clockbrain Please read my Post above: #36 (comment)
I dont use the manuSpecificCluster1 binding.
Will provide some more logs this evening if i got some free time.
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@clockbrain sorry, you also need this zigbee-shepherd branch: https://github.com/koenkk/zigbee-shepherd/tree/hue_remote
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@Koenkk Looks great
2018-7-3 22:44:55 �[32mINFO�[39m Succesfully configured 0x0017880103caab06
2018-7-3 22:45:32 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"on"}'
2018-7-3 22:45:36 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"off"}'
2018-7-3 22:45:40 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"up-press","brightness":255}'
2018-7-3 22:45:44 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"down-press","brightness":205}'
2018-7-3 22:45:47 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"up-press","brightness":255}'
2018-7-3 22:45:48 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"up-hold"}'
2018-7-3 22:45:49 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"up-hold"}'
2018-7-3 22:45:50 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"brightness":255,"action":"up-hold-release"}'
2018-7-3 22:45:57 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"down-press","brightness":205}'
2018-7-3 22:45:58 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"down-hold"}'
2018-7-3 22:45:59 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"down-hold"}'
2018-7-3 22:45:59 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"brightness":165.3,"action":"down-hold-release"}'
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
This is my database.db entry after the successfully configured.
{"id":2,"type":"EndDevice","ieeeAddr":"0x0017880103caab06","nwkAddr":15394,"manufId":4107,"manufName":"Philips","powerSource":"Battery","modelId":"RWL021","epList":[1,2],"status":"online","joinTime":1530650683,"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":28,"batteryPercentageRemaining":200}},"genIdentify":{"dir":{"value":1},"attrs":{}},"genBinaryInput":{"dir":{"value":1},"attrs":{}},"genOta":{"dir":{"value":2},"attrs":{}}}}},"_id":"5xl8FRujrwMGLJi6"}
We need now the battery informations also to complete this issue
from zigbee2mqtt.
arteck
commented on June 22, 2024
very nice..plz marge it
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@tb-killa updated:
- For sequential hold messages, it will now always send the brightness
- Bind battery cluster, can you check if you see any
No converter availablefromgenPowerCfg?
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@Koenkk Tested:
2018-7-4 22:25:44 �[32mINFO�[39m Succesfully configured 0x0017880103caab06
spinlock: false []
2018-7-4 22:25:49 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"on"}'
2018-7-4 22:26:00 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"off"}'
2018-7-4 22:26:02 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"up-press","brightness":255}'
2018-7-4 22:26:03 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"up-hold","brightness":255}'
2018-7-4 22:26:04 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"up-hold","brightness":255}'
spinlock: true []
2018-7-4 22:26:06 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"down-press","brightness":205}'
2018-7-4 22:26:07 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"down-hold","brightness":255}'
2018-7-4 22:26:08 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"down-hold","brightness":173.9}'
2018-7-4 22:26:08 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"down-hold","brightness":94.7}'
2018-7-4 22:26:09 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"down-hold","brightness":14.900000000000006}'
2018-7-4 22:26:10 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"brightness":0,"action":"null-hold-release"}'
2018-7-4 22:26:17 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"up-press","brightness":50}'
2018-7-4 22:26:17 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"up-hold","brightness":50}'
2018-7-4 22:26:18 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"brightness":89.8,"action":"null-hold-release"}'
2018-7-4 22:26:22 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"down-press","brightness":39.8}'
2018-7-4 22:26:23 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"down-hold","brightness":39.8}'
2018-7-4 22:26:24 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"down-hold","brightness":0}'
2018-7-4 22:26:24 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"brightness":0,"action":"null-hold-release"}'
2018-7-4 22:26:34 �[32mINFO�[39m Device incoming...
2018-7-4 22:26:34 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
device already in network
2018-7-4 22:26:46 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"up-press","brightness":50}'
2018-7-4 22:26:48 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"down-press","brightness":0}'
2018-7-4 22:26:53 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"on"}'
spinlock: false []
device already in network
2018-7-4 22:27:05 �[32mINFO�[39m MQTT publish, topic: 'zigbee2mqtt/philips-hue-switch', payload: '{"action":"off"}'
Sadly no battery informations or return of No converter available
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@tb-killa can you update and try again?
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@Koenkk I updated and pair again, but sadly now new messages or power code inside debug message.
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
@tb-killa did you see the Sucesfully configured message for this device?
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
It seems to be that it failed:
2018-07-05T19:26:46.637Z - info: zigbee-shepherd ready
2018-07-05T19:26:46.676Z - info: Connected to MQTT server
2018-07-05T19:26:46.679Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
2018-07-05T19:27:36.014Z - error: Failed to configure 0x0017880103caab06
2018-07-05T19:30:34.331Z - debug: Recieved zigbee message with data {"cid":"genOnOff","data":{}}
2018-07-05T19:30:34.336Z - info: MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"on"}'
2018-07-05T19:30:35.972Z - debug: Recieved zigbee message with data {"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}
2018-07-05T19:30:35.975Z - info: MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"off"}'
2018-07-05T19:30:40.813Z - debug: Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":0,"stepsize":30,"transtime":9}}
2018-07-05T19:30:40.818Z - info: MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"up-press","brightness":255}'
2018-07-05T19:30:42.675Z - debug: Recieved zigbee message with data {"cid":"genLevelCtrl","data":{"stepmode":1,"stepsize":30,"transtime":9}}
2018-07-05T19:30:42.680Z - info: MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"down-press","brightness":205}'
2018-07-05T19:43:01.025Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:43:02.585Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:43:09.621Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:43:16.630Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:43:23.619Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:43:30.619Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:43:37.619Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:43:44.619Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:43:51.618Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:43:58.618Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:44:05.617Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:44:12.617Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:44:12.628Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:44:12.630Z - info: Device incoming...
2018-07-05T19:44:12.633Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
2018-07-05T19:44:12.638Z - debug: Recieved zigbee message with data "online"
2018-07-05T19:45:16.707Z - debug: Recieved zigbee message with data {"cid":"genOnOff","data":{}}
2018-07-05T19:45:16.710Z - info: MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"on"}'
2018-07-05T19:46:05.491Z - debug: Recieved zigbee message with data {"cid":"genOnOff","data":{"effectid":0,"effectvariant":0}}
2018-07-05T19:46:05.495Z - info: MQTT publish, topic: 'zigbee2mqtt/0x0017880103caab06', payload: '{"action":"off"}'
Will remove and try again
from zigbee2mqtt.
tb-killa
commented on June 22, 2024
Nope it doesnt configured correct :(
2018-07-05T19:56:18.865Z - info: Connected to MQTT server
2018-07-05T19:56:18.869Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
2018-07-05T19:57:02.079Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:02.085Z - info: Connecting with device...
2018-07-05T19:57:02.090Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:02.522Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:02.527Z - info: Connecting with device...
2018-07-05T19:57:02.531Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:04.095Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:04.098Z - info: Connecting with device...
2018-07-05T19:57:04.100Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:05.177Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:05.180Z - info: Connecting with device...
2018-07-05T19:57:05.183Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:05.696Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:05.701Z - info: Connecting with device...
2018-07-05T19:57:05.705Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:07.285Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:07.290Z - info: Connecting with device...
2018-07-05T19:57:07.293Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:08.170Z - error: Failed to configure 0x90fd9ffffed17c15
2018-07-05T19:57:08.879Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:08.883Z - info: Connecting with device...
2018-07-05T19:57:08.887Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:09.872Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:09.875Z - info: Connecting with device...
2018-07-05T19:57:09.878Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:10.392Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:10.394Z - info: Connecting with device...
2018-07-05T19:57:10.397Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:10.889Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:10.891Z - info: Connecting with device...
2018-07-05T19:57:10.893Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:11.398Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:11.401Z - info: Connecting with device...
2018-07-05T19:57:11.406Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:12.452Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:12.455Z - info: Connecting with device...
2018-07-05T19:57:12.457Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"connecting with device"}'
2018-07-05T19:57:12.481Z - debug: Recieved zigbee message with data "0x0017880103caab06"
2018-07-05T19:57:12.484Z - info: Device incoming...
2018-07-05T19:57:12.487Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"pairing","message":"device incoming"}'
2018-07-05T19:57:12.490Z - info: New device with address 0x0017880103caab06 connected!
2018-07-05T19:57:12.526Z - info: MQTT publish, topic: 'zigbee2mqtt/bridge/log', payload: '{"type":"device_connected","message":"0x0017880103caab06"}'
2018-07-05T19:57:12.541Z - debug: Recieved zigbee message with data "online"
2018-07-05T19:57:15.459Z - error: Failed to configure 0x0017880103caab06
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
Can you provide the log after running with the following in devices.js:
{
zigbeeModel: ['RWL020', 'RWL021'],
model: '324131092621',
vendor: 'Philips',
description: 'Hue dimmer Switch',
supports: 'on/off',
fromZigbee: [fz._324131092621_on, fz._324131092621_off, fz._324131092621_step, fz._324131092621_stop],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const ep1 = shepherd.find(ieeeAddr, 1);
const actions = [
(cb) => ep1.bind('genOnOff', coordinator, cb),
(cb) => ep1.bind('genLevelCtrl', coordinator, cb),
];
execute(ep1, actions, (result) => {
if (result) {
const ep2 = shepherd.find(ieeeAddr, 2);
ep2.bind('genPowerCfg', coordinator, (err) => {
console.log('genPowerCfg bind result', err);
ep2.report('genPowerCfg', 'batteryVoltage', 0, 1000, 0, (err) => {
console.log('genPowerCfg report', err);
callback(!err);
});
});
} else {
callback(result);
}
});
},
},from zigbee2mqtt.
tb-killa
commented on June 22, 2024
@Koenkk : Nope :(
zigbee-shepherd:msgHdlr IND <-- ZDO:bindRsp +1ms
genPowerCfg bind result null
zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] +1ms
genPowerCfg report unreportableAttribute
2018-7-6 14:57:26 ERROR Failed to configure 0x0017880103caab06
from zigbee2mqtt.
Koenkk
commented on June 22, 2024
Reading the zigbee cluster library specification, reporting of batteryVoltage is not possible, but batteryPercentageRemaining should.
Can you try:
{
zigbeeModel: ['RWL020', 'RWL021'],
model: '324131092621',
vendor: 'Philips',
description: 'Hue dimmer Switch',
supports: 'on/off',
fromZigbee: [fz._324131092621_on, fz._324131092621_off, fz._324131092621_step, fz._324131092621_stop],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const ep1 = shepherd.find(ieeeAddr, 1);
const actions = [
(cb) => ep1.bind('genOnOff', coordinator, cb),
(cb) => ep1.bind('genLevelCtrl', coordinator, cb),
];
execute(ep1, actions, (result) => {
if (result) {
const ep2 = shepherd.find(ieeeAddr, 2);
ep2.bind('genPowerCfg', coordinator, (err) => {
console.log('genPowerCfg bind result', err);
ep2.report('genPowerCfg', 'batteryPercentageRemaining', 0, 1000, 0, (err) => {
console.log('genPowerCfg report', err);
callback(!err);
});
});
} else {
callback(result);
}
});
},
},from zigbee2mqtt.
clockbrain
commented on June 22, 2024
@Koenkk I'm now getting good results from Hue dimmer except no battery information. Can I suggest you merge as-is. Its difficult for me to test the hue_remote branch because it doesn't include some devices in master that I use. Manually trying to merge the code just causes breakage.
Here's the MQTT stream I now get from the hue_remote branch
pi@raspberrypi ~ $ mosquitto_sub -t "zigbee2mqtt/Dimmer" -h 192.168.x.x-u mosuser
{"action":"on"}
{"action":"down-press","brightness":205}
{"action":"down-hold","brightness":205}
{"brightness":118,"action":"down-hold-release"}
{"action":"up-press","brightness":168}
{"action":"up-hold","brightness":168}
{"brightness":230.7,"action":"up-hold-release"}
{"action":"down-press","brightness":180.7}
{"action":"up-press","brightness":230.7}
{"action":"off"}
Minor issue - order of entries for *-hold-release is backwards to the others. Could you swap lines 547 and 548 in fromZigbee.js/_324131092621_stop to fix that?
thanks for all your good work.
from zigbee2mqtt.
Related Issues (20)
- docs: No mention of server requirement on Windows
- Skyconnect rtscts not working HOT 3
- HEIMAN HS1CG-E (Gas sensor) always reports no gas leak HOT 1
- Philips Disney StoryLight (LLC013) stops responding after 20 minutes HOT 1
- [New device support]: SLZB-07
- [New device support]: TRV ZIGBEE TS0601 / TZE200_ytryxh0a
- Error while starting zigbee-herdsman / Error Resource temporarily unavailable Cannot lock port HOT 3
- [New device support]: TS0601 _TZE204_kapvnnlk - Help need for fixing converter
- [Feature request]: Power On Behavior for FUT035Z+
- zigbee2mqtt restart every 2 minutes
- Unstable network on EmberZNet
- How can I flash SLZB-06M to cp-uart-hw-v7.4.1.0-slzb-06m-230400.gbl ? HOT 8
- BMCT-RZ does not react to external switches after pairing with Zigbee2MQTT HOT 2
- TS0042 without action HOT 2
- TS110E stopped working (unsupported) HOT 2
- [New device support]: Develco EMI 2 - P1 - EMIZB-151 HOT 1
- [New device support]: Gledopto gl-sd-001p
- Ember not working properly
- Invalid WebSocket frame: RSV1 must be clear
- z2m doesn't even try to read my local OTA index file HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from zigbee2mqtt.