Comments (26)
dzungpv
commented on June 27, 2024
1
Yes. That is my same problem. I will follow that.
Please note that delete database not complete remove device from the network. Because it write to eprom. To delete it must reflash the cc2531, remove id from configuration file and delete database
…-------- Original message --------
From: Koen Kanters <[email protected]>
Date: 6/3/18 12:37 AM (GMT+07:00)
To: Koenkk/zigbee-shepherd-converters <[email protected]>
Cc: Viet Dzung <[email protected]>, Mention <[email protected]>
Subject: Re: [Koenkk/zigbee-shepherd-converters] Device connected but still not get the data for "fromZigbee" (#7)
Isn't this similar to what currently is being done in Koenkk/zigbee2mqtt#36<Koenkk/zigbee2mqtt#36>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#7 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKEv6YN8PhWnqiG1wFc817bp2fDsV-caks5t4s1HgaJpZM4UU5q4>.
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
This is the full log after it connected:
login as: pi
[email protected]'s password:
Linux raspberrypi 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu May 31 11:45:26 2018 from 192.168.1.6
pi@raspberrypi:~ $ cd /opt/zigbee2mqtt
pi@raspberrypi:/opt/zigbee2mqtt $ DEBUG=* npm start
> [email protected] start /opt/zigbee2mqtt
> node index.js
2018-5-31 11:53:58 INFO Starting zigbee-shepherd
zigbee-shepherd:init zigbee-shepherd booting... +0ms
cc-znp The serialport /dev/ttyACM0 is opened. +0ms
zigbee-shepherd:request REQ --> SYS:osalNvRead +66ms
cc-znp:SREQ --> SYS:osalNvRead, { id: 3840, offset: 0, len: 1, value: [ 85 ] } +9ms
serialport write 8 bytes of data +0ms
cc-znp:SRSP <-- SYS:osalNvRead, { status: 0, len: 1, value: <Buffer 55> } +52ms
zigbee-shepherd:request RSP <-- SYS:osalNvRead, status: 0 +59ms
zigbee-shepherd:request REQ --> SAPI:readConfiguration +35ms
cc-znp:SREQ --> SAPI:readConfiguration, { configid: 131, len: 2, value: [ 98, 26 ] } +38ms
serialport write 6 bytes of data +75ms
cc-znp:SRSP <-- SAPI:readConfiguration, { status: 0, configid: 131, len: 2, value: <Buffer 62 1a> } +11ms
zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +13ms
zigbee-shepherd:request REQ --> SAPI:readConfiguration +12ms
cc-znp:SREQ --> SAPI:readConfiguration, { configid: 132, len: 4, value: [ 0, 128, 0, 0 ] } +13ms
serialport write 6 bytes of data +24ms
cc-znp:SRSP <-- SAPI:readConfiguration, { status: 0, configid: 132, len: 4, value: <Buffer 00 80 00 00> } +29ms
zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +29ms
zigbee-shepherd:request REQ --> SAPI:readConfiguration +12ms
cc-znp:SREQ --> SAPI:readConfiguration, { configid: 98, len: 16, value: [ 1, 3, 5, 7, 9, 11, 13, 15, 0, 2, 4, 6, 8, 10, 12, 13 ] } +13ms
serialport write 6 bytes of data +42ms
cc-znp:SRSP <-- SAPI:readConfiguration, { status: 0, configid: 98, len: 16, value: <Buffer 01 03 05 07 09 0b 0d 0f 00 02 04 06 08 0a 0c 0d> } +24ms
zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +26ms
zigbee-shepherd:request REQ --> SAPI:readConfiguration +12ms
cc-znp:SREQ --> SAPI:readConfiguration, { configid: 99, len: 1, value: [ 0 ] } +13ms
serialport write 6 bytes of data +37ms
cc-znp:SRSP <-- SAPI:readConfiguration, { status: 0, configid: 99, len: 1, value: <Buffer 00> } +17ms
zigbee-shepherd:request RSP <-- SAPI:readConfiguration, status: 0 +18ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +13ms
cc-znp:SREQ --> SAPI:getDeviceInfo, { param: 0 } +15ms
serialport write 6 bytes of data +31ms
cc-znp:SRSP <-- SAPI:getDeviceInfo, { param: 0, value: <Buffer 00 09 00 ff fe 04 66 04> } +8ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +10ms
zigbee-shepherd:init Start the ZNP as a coordinator... +1ms
zigbee-shepherd:request REQ --> ZDO:startupFromApp +1ms
cc-znp:SREQ --> ZDO:startupFromApp, { startdelay: 100 } +4ms
serialport write 7 bytes of data +12ms
cc-znp:SRSP <-- ZDO:startupFromApp, { status: 0 } +562ms
cc-znp:AREQ <-- ZDO:stateChangeInd, { state: 9 } +8ms
zigbee-shepherd:msgHdlr IND <-- ZDO:stateChangeInd +575ms
zigbee-shepherd:init Now the ZNP is a coordinator. +2ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +3ms
cc-znp:SREQ --> SAPI:getDeviceInfo, { param: 0 } +10ms
serialport write 6 bytes of data +581ms
cc-znp:SRSP <-- SAPI:getDeviceInfo, { param: 0, value: <Buffer 09 00 00 00 00 00 00 00> } +11ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +13ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +2ms
cc-znp:SREQ --> SAPI:getDeviceInfo, { param: 1 } +4ms
serialport write 6 bytes of data +15ms
cc-znp:SRSP <-- SAPI:getDeviceInfo, { param: 1, value: <Buffer 68 6b 89 0e 00 4b 12 00> } +11ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +13ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +3ms
cc-znp:SREQ --> SAPI:getDeviceInfo, { param: 2 } +5ms
serialport write 6 bytes of data +15ms
cc-znp:SRSP <-- SAPI:getDeviceInfo, { param: 2, value: <Buffer 00 00 89 0e 00 4b 12 00> } +10ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +12ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +3ms
cc-znp:SREQ --> SAPI:getDeviceInfo, { param: 5 } +5ms
serialport write 6 bytes of data +15ms
cc-znp:SRSP <-- SAPI:getDeviceInfo, { param: 5, value: <Buffer 0f 00 89 0e 00 4b 12 00> } +12ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +14ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +1ms
cc-znp:SREQ --> SAPI:getDeviceInfo, { param: 6 } +3ms
serialport write 6 bytes of data +16ms
cc-znp:SRSP <-- SAPI:getDeviceInfo, { param: 6, value: <Buffer 62 1a 89 0e 00 4b 12 00> } +12ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +14ms
zigbee-shepherd:request REQ --> SAPI:getDeviceInfo +2ms
cc-znp:SREQ --> SAPI:getDeviceInfo, { param: 7 } +4ms
serialport write 6 bytes of data +15ms
cc-znp:SRSP <-- SAPI:getDeviceInfo, { param: 7, value: <Buffer dd dd dd dd dd dd dd dd> } +8ms
zigbee-shepherd:request RSP <-- SAPI:getDeviceInfo +10ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +5ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 0, nwkaddrofinterest: 0 } +9ms
serialport write 9 bytes of data +17ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +10ms
cc-znp:AREQ <-- ZDO:nodeDescRsp, { srcaddr: 0, status: 0, nwkaddr: 0, logicaltype_cmplxdescavai_userdescavai: 0, apsflags_freqband: 64, maccapflags: 143, manufacturercode: 0, maxbuffersize: 80, maxintransfersize: 160, servermask: 1, maxouttransfersize: 160, descriptorcap: 0 } +7ms
zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +21ms
zigbee-shepherd:request REQ --> ZDO:activeEpReq +3ms
cc-znp:SREQ --> ZDO:activeEpReq, { dstaddr: 0, nwkaddrofinterest: 0 } +5ms
serialport write 9 bytes of data +22ms
cc-znp:SRSP <-- ZDO:activeEpReq, { status: 0 } +11ms
cc-znp:AREQ <-- ZDO:activeEpRsp, { srcaddr: 0, status: 0, nwkaddr: 0, activeepcount: 0, activeeplist: <Buffer > } +6ms
zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +19ms
zigbee-shepherd:request REQ --> AF:register +6ms
cc-znp:SREQ --> AF:register, { endpoint: 1, appprofid: 260, appdeviceid: 5, appdevver: 0, latencyreq: 0, appnuminclusters: 0, appinclusterlist: [], appnumoutclusters: 0, appoutclusterlist: [] } +9ms
serialport write 14 bytes of data +26ms
cc-znp:SRSP <-- AF:register, { status: 0 } +9ms
zigbee-shepherd:request RSP <-- AF:register, status: 0 +12ms
zigbee-shepherd:init Register delegator, epId: 1, profId: 260 +10ms
zigbee-shepherd:request REQ --> AF:register +1ms
cc-znp:SREQ --> AF:register, { endpoint: 2, appprofid: 257, appdeviceid: 5, appdevver: 0, latencyreq: 0, appnuminclusters: 0, appinclusterlist: [], appnumoutclusters: 0, appoutclusterlist: [] } +13ms
serialport write 14 bytes of data +22ms
cc-znp:SRSP <-- AF:register, { status: 0 } +8ms
zigbee-shepherd:request RSP <-- AF:register, status: 0 +10ms
zigbee-shepherd:init Register delegator, epId: 2, profId: 257 +11ms
zigbee-shepherd:request REQ --> AF:register +1ms
cc-znp:SREQ --> AF:register, { endpoint: 3, appprofid: 261, appdeviceid: 5, appdevver: 0, latencyreq: 0, appnuminclusters: 0, appinclusterlist: [], appnumoutclusters: 0, appoutclusterlist: [] } +13ms
serialport write 14 bytes of data +22ms
cc-znp:SRSP <-- AF:register, { status: 0 } +9ms
zigbee-shepherd:request RSP <-- AF:register, status: 0 +9ms
zigbee-shepherd:init Register delegator, epId: 3, profId: 261 +12ms
zigbee-shepherd:request REQ --> AF:register +0ms
cc-znp:SREQ --> AF:register, { endpoint: 4, appprofid: 263, appdeviceid: 5, appdevver: 0, latencyreq: 0, appnuminclusters: 0, appinclusterlist: [], appnumoutclusters: 0, appoutclusterlist: [] } +13ms
serialport write 14 bytes of data +21ms
cc-znp:SRSP <-- AF:register, { status: 0 } +8ms
zigbee-shepherd:request RSP <-- AF:register, status: 0 +10ms
zigbee-shepherd:init Register delegator, epId: 4, profId: 263 +10ms
zigbee-shepherd:request REQ --> AF:register +0ms
cc-znp:SREQ --> AF:register, { endpoint: 5, appprofid: 264, appdeviceid: 5, appdevver: 0, latencyreq: 0, appnuminclusters: 0, appinclusterlist: [], appnumoutclusters: 0, appoutclusterlist: [] } +12ms
serialport write 14 bytes of data +21ms
cc-znp:SRSP <-- AF:register, { status: 0 } +9ms
zigbee-shepherd:request RSP <-- AF:register, status: 0 +11ms
zigbee-shepherd:init Register delegator, epId: 5, profId: 264 +11ms
zigbee-shepherd:request REQ --> AF:register +1ms
cc-znp:SREQ --> AF:register, { endpoint: 6, appprofid: 265, appdeviceid: 5, appdevver: 0, latencyreq: 0, appnuminclusters: 0, appinclusterlist: [], appnumoutclusters: 0, appoutclusterlist: [] } +13ms
serialport write 14 bytes of data +22ms
cc-znp:SRSP <-- AF:register, { status: 0 } +9ms
zigbee-shepherd:request RSP <-- AF:register, status: 0 +9ms
zigbee-shepherd:init Register delegator, epId: 6, profId: 265 +12ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 0, nwkaddrofinterest: 0 } +14ms
serialport write 9 bytes of data +22ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +15ms
cc-znp:AREQ <-- ZDO:nodeDescRsp, { srcaddr: 0, status: 0, nwkaddr: 0, logicaltype_cmplxdescavai_userdescavai: 0, apsflags_freqband: 64, maccapflags: 143, manufacturercode: 0, maxbuffersize: 80, maxintransfersize: 160, servermask: 1, maxouttransfersize: 160, descriptorcap: 0 } +8ms
zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp +25ms
zigbee-shepherd:request REQ --> ZDO:activeEpReq +1ms
cc-znp:SREQ --> ZDO:activeEpReq, { dstaddr: 0, nwkaddrofinterest: 0 } +2ms
serialport write 9 bytes of data +25ms
cc-znp:SRSP <-- ZDO:activeEpReq, { status: 0 } +11ms
cc-znp:AREQ <-- ZDO:activeEpRsp, { srcaddr: 0, status: 0, nwkaddr: 0, activeepcount: 6, activeeplist: <Buffer 06 05 04 03 02 01> } +6ms
zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp +18ms
zigbee-shepherd:request REQ --> ZDO:mgmtPermitJoinReq +5ms
cc-znp:SREQ --> ZDO:mgmtPermitJoinReq, { addrmode: 2, dstaddr: 0, duration: 0, tcsignificance: 0 } +7ms
serialport write 10 bytes of data +24ms
cc-znp:SRSP <-- ZDO:mgmtPermitJoinReq, { status: 0 } +11ms
cc-znp:AREQ <-- ZDO:permitJoinInd, { duration: 0 } +4ms
zigbee-shepherd:msgHdlr IND <-- ZDO:permitJoinInd +16ms
cc-znp:AREQ <-- ZDO:mgmtPermitJoinRsp, { srcaddr: 0, status: 0 } +4ms
zigbee-shepherd:msgHdlr IND <-- ZDO:mgmtPermitJoinRsp +4ms
zigbee-shepherd:init Loading devices from database done. +140ms
zigbee-shepherd:init zigbee-shepherd is up and ready. +0ms
zigbee-shepherd:init Network information: +1ms
zigbee-shepherd:init >> State: Coordinator +0ms
zigbee-shepherd:init >> Channel: 15 +0ms
zigbee-shepherd:init >> PanId: 0x1a62 +0ms
zigbee-shepherd:init >> Nwk Addr: 0 +0ms
zigbee-shepherd:init >> Ieee Addr: 0x00124b000e896b68 +0ms
zigbee-shepherd:init >> Ext. PanId: 0xdddddddddddddddd +0ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +2ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 8250, nwkaddrofinterest: 8250 } +144ms
serialport write 9 bytes of data +163ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +3ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +0ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +0ms
2018-5-31 11:54:00 INFO zigbee-shepherd started
2018-5-31 11:54:00 INFO Currently 7 devices are joined:
2018-5-31 11:54:00 INFO 0x00158d0001d57d8b (0x00158d0001d57d8b): WXKG12LM - Xiaomi Aqara wireless switch (with gyroscope) (EndDevice)
2018-5-31 11:54:00 INFO 0x00158d0001d53642 (0x00158d0001d53642): WXKG12LM - Xiaomi Aqara wireless switch (with gyroscope) (EndDevice)
2018-5-31 11:54:00 INFO 0x00158d00020e61a0 (0x00158d00020e61a0): RTCGQ01LM - Xiaomi MiJia human body movement sensor (EndDevice)
2018-5-31 11:54:00 INFO 0x00158d000201b416 (0x00158d000201b416): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2018-5-31 11:54:00 INFO 0x00158d0001f49be4 (0x00158d0001f49be4): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
2018-5-31 11:54:00 INFO 0x00158d00010627c6 (0x00158d00010627c6): ZNCZ02LM - Xiaomi Mi power plug ZigBee (Router)
2018-5-31 11:54:00 INFO 0x000b57fffe69e05c (0x000b57fffe69e05c): LM-SZ3 - Hogar Controls Hogar Controls triple key wired wall switch (Router)
2018-5-31 11:54:00 INFO Connecting to MQTT server at mqtt://test.mosquitto.org
2018-5-31 11:54:00 INFO zigbee-shepherd ready
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +354ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 38363, nwkaddrofinterest: 38363 } +2ms
serialport write 9 bytes of data +356ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +67ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 19474, nwkaddrofinterest: 19474 } +1ms
serialport write 9 bytes of data +68ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +19ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 61886, nwkaddrofinterest: 61886 } +1ms
serialport write 9 bytes of data +20ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +19ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 53643, nwkaddrofinterest: 53643 } +1ms
serialport write 9 bytes of data +20ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +19ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 37891, nwkaddrofinterest: 37891 } +1ms
serialport write 9 bytes of data +20ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 16 } +21ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 15066, nwkaddrofinterest: 15066 } +3ms
serialport write 9 bytes of data +24ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +507ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +17ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 37891, nwkaddrofinterest: 37891 } +1ms
serialport write 9 bytes of data +18ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +14ms
2018-5-31 11:54:01 INFO Connected to MQTT server
2018-5-31 11:54:01 INFO MQTT publish, topic: 'zigbee2mqtt/bridge/state', payload: 'online'
2018-5-31 11:54:01 WARN `permit_join` set to `true` in configuration.yaml.
2018-5-31 11:54:01 WARN Allowing new devices to join.
2018-5-31 11:54:01 WARN Set `permit_join` to `false` once you joined all devices.
2018-5-31 11:54:01 INFO Zigbee: allowing new devices to join.
zigbee-shepherd:request REQ --> ZDO:mgmtPermitJoinReq +1s
cc-znp:SREQ --> ZDO:mgmtPermitJoinReq, { addrmode: 15, dstaddr: 65532, duration: 255, tcsignificance: 0 } +1s
serialport write 10 bytes of data +1s
cc-znp:SRSP <-- ZDO:mgmtPermitJoinReq, { status: 0 } +21ms
cc-znp:AREQ <-- ZDO:permitJoinInd, { duration: 255 } +5ms
zigbee-shepherd:msgHdlr IND <-- ZDO:permitJoinInd +29ms
cc-znp:AREQ <-- ZDO:mgmtPermitJoinRsp, { srcaddr: 0, status: 0 } +4ms
zigbee-shepherd:msgHdlr IND <-- ZDO:mgmtPermitJoinRsp +4ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +3s
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 8250, nwkaddrofinterest: 8250 } +3s
serialport write 9 bytes of data +3s
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +4ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +0ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +23ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 38363, nwkaddrofinterest: 38363 } +1ms
serialport write 9 bytes of data +24ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +22ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 19474, nwkaddrofinterest: 19474 } +2ms
serialport write 9 bytes of data +24ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +22ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 61886, nwkaddrofinterest: 61886 } +2ms
serialport write 9 bytes of data +24ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +22ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 53643, nwkaddrofinterest: 53643 } +2ms
serialport write 9 bytes of data +23ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +23ms
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 15066, nwkaddrofinterest: 15066 } +2ms
serialport write 9 bytes of data +26ms
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 16 } +21ms
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +41s
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +41s
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +4s
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +4s
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +8s
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +8s
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +605ms
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +606ms
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +2s
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +2s
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +203ms
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +203ms
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +200ms
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +200ms
zigbee2mqtt:zigbee Check online 0x00158d00010627c6 +0ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +1s
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 37891, nwkaddrofinterest: 37891 } +1s
serialport write 9 bytes of data +57s
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +22ms
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +5s
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 37891, nwkaddrofinterest: 37891 } +5s
serialport write 9 bytes of data +5s
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +22ms
from zigbee-herdsman-converters.
Koenkk
commented on June 27, 2024
So if I understand right.
When pressing buttons on this device you see in the log:
serialport write 9 bytes of data +55s
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +21ms
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +3s
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +3s
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +2s
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 37891, nwkaddrofinterest: 37891 } +2s
But no:
2018-5-1 18:19:41 WARN No converter available for 'WSDCGQ01LM' with cid 'msTemperatureMeasurement' and type 'attReport'
2018-5-1 18:19:41 WARN Please create an issue on https://github.com/Koenkk/zigbee2mqtt/issues with this message.
appear?
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
Yes, how to extract the data from it and add it to fromZigbee?:
```cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +3s
```
This device use silabs zigbee chip.
Sent from my Samsung Galaxy smartphone.
…-------- Original message --------
From: Koen Kanters <[email protected]>
Date: 6/1/18 12:06 AM (GMT+07:00)
To: Koenkk/zigbee-shepherd-converters <[email protected]>
Cc: Viet Dzung <[email protected]>, Author <[email protected]>
Subject: Re: [Koenkk/zigbee-shepherd-converters] Device connected but still not get the data for "fromZigbee" (#7)
So if I understand right.
When pressing buttons on this device you see in the log:
serialport write 9 bytes of data +55s
cc-znp:SRSP <-- ZDO:nodeDescReq, { status: 0 } +21ms
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 15066, relaycount: 0, relaylist: <Buffer > } +3s
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +3s
zigbee-shepherd:request REQ --> ZDO:nodeDescReq +2s
cc-znp:SREQ --> ZDO:nodeDescReq, { dstaddr: 37891, nwkaddrofinterest: 37891 } +2s
``
But no:
2018-5-1 18:19:41 WARN No converter available for 'WSDCGQ01LM' with cid 'msTemperatureMeasurement' and type 'attReport'
2018-5-1 18:19:41 WARN Please create an issue on https://github.com/Koenkk/zigbee2mqtt/issues with this message.
appear?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#7 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKEv6R6E5YQ18CrIZk8OaN0cIanubUQiks5t4CMJgaJpZM4UU5q4>.
from zigbee-herdsman-converters.
Koenkk
commented on June 27, 2024
This probably means that the switch uses a proprietary structure which should be added to https://github.com/Koenkk/zcl-packet/blob/master/lib/foundation.js.
@kirovilya has more experience with this, can you confirm?
from zigbee-herdsman-converters.
kirovilya
commented on June 27, 2024
The LM-SZ3 device connects to the coordinator, but no further events are visible?
It is possible that the device uses a zigbee-profile or clusters that are not included in the zcl-id and zcl-packet, so they can not not be processed.
In this log we do not see the profileID and Clusters that support the device.
This should be inferred by additional logging. Now I can not say exactly how.
For example, I have an IKEA remote control that also connects, but does not transmit messages or receive commands. Perhaps here is the same situation.
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
@kirovilya I have sniffer the process from the start to the moment it joint the network and start sending on/off status, this is logs file format for Wireshark and Ubiqua https://www.dropbox.com/sh/01x9p87zbxtqcjt/AABbU_w96FuDSQRyeA6R4qZba?dl=0 you can look at it. And if there is any way to make it work you can tell me.
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
This is log when it connect to CC2531:
loglm-3sz.txt
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
@kirovilya Finally! I think i have found Cluster ID is 0x00006 and Profile ID is 0x0104, how can i add it to https://github.com/Koenkk/zcl-packet/blob/master/lib/foundation.js. please check the image.
I also note that the Destination end point is: 0x06, they make it not compatible with other. I think that i need to add new Endpoint 0x06 to support this device.
from zigbee-herdsman-converters.
Koenkk
commented on June 27, 2024
Can you try binding to ep 1 of the coordinator, there is an example how to do this here: Koenkk/zigbee2mqtt#36
from zigbee-herdsman-converters.
kirovilya
commented on June 27, 2024
@dzungpv looks good. how you get Packet view? which tools? Can I repeat it with my devices on cc2531?
from zigbee-herdsman-converters.
kirovilya
commented on June 27, 2024
I now reading http://faire-ca-soi-meme.fr/domotique/2018/03/14/une-telecommande-zigbee-pour-les-controler-tous/ and try undestand how get working IKEA Remote. Very similar to your case
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
@kirovilya I use Ubiqua Protocol Analyzer and set the "Application and Trust Link Key": 5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39
You must start the Ubiqua before paired to device. Buy another CC2531 for sniffer.
@Koenkk I am not find any sample, you can send me direct link to that issue?
I read here http://faire-ca-soi-meme.fr/test/2017/10/31/test-orvibo-smarthome-compatible-zigate/ him can do with Zigate, but not know how to do with zigbee shepherd.
The problem is Destination end point it not like normal HA profile
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
@Koenkk You mean this ?:
// 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!');
}
});
It mean i must fix the id to the code. I will try and report the result
from zigbee-herdsman-converters.
kirovilya
commented on June 27, 2024
@dzungpv try find in node_modules\zigbee-shepherd\lib\initializers\init_controller.js:63 list of coordinator endpoints and change (or add) your profile and endpoint { profId: 0x0104, epId: 6 }
but it is not good :( only for test.
I successuful run Ubiqua Protocol Analyzer and grab and decrypt packages. Thank you!
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
@kirovilya I follow your method every time i press on/off there is log:
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +59ms
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 30740, relaycount: 0, relaylist: <Buffer > } +445ms
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +445ms
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 30740, srcendpoint: 1, dstendpoint: 6, wasbroadcast: 0, linkquality: 39, securityuse: 0, timestamp: 3238290, transseqnumber: 0, len: 8, data: <Buffer 18 65 01 00 00 00 10 01> } +60ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +61ms
Mean i must add support to the file https://github.com/Koenkk/zcl-packet/blob/master/lib/foundation.js ?
from zigbee-herdsman-converters.
kirovilya
commented on June 27, 2024
@dzungpv Good that you get the messages... But I do not know how to add support :(
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
@kirovilya So may be @Koenkk can help?
Logs:
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 30740, srcendpoint: 1, dstendpoint: 6, wasbroadcast: 0, linkquality: 49, securityuse: 0, timestamp: 6347774, transseqnumber: 0, len: 8, data: <Buffer 18 13 01 00 00 00 10 00> } +62ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +63ms
cc-znp:AREQ <-- ZDO:srcRtgInd, { dstaddr: 30740, relaycount: 0, relaylist: <Buffer > } +851ms
zigbee-shepherd:msgHdlr IND <-- ZDO:srcRtgInd +851ms
cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 6, srcaddr: 30740, srcendpoint: 1, dstendpoint: 6, wasbroadcast: 0, linkquality: 49, securityuse: 0, timestamp: 6350618, transseqnumber: 0, len: 8, data: <Buffer 18 14 01 00 00 00 10 01> } +56ms
zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 +56ms
data: <Buffer 18 14 01 00 00 00 10 01>
data: <Buffer 18 14 01 00 00 00 10 01> is when i turn one button on and data: <Buffer 18 13 01 00 00 00 10 00> when if off. I see 10 01 and 10 00 but do not know how to continue.
from zigbee-herdsman-converters.
tb-killa
commented on June 27, 2024
@dzungpv Do you test via the mapping like @Koenkk mentioned?
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
@tb-killa Yes, i test it and it can produce same data i post above but i can map the Destination end point to 1, but it work only 1 time, when i reset the CC2531, it not work again. So i try the second method from kirovilya.
This is the code:
// TEMP: Bind switch to coordinator.
let ep1 = this.shepherd.find('0x000b57fffe69e05c', 6);
let coordinator = this.shepherd.list().find((d) => d.type === 'Coordinator');
coordinator = this.shepherd.find(coordinator.ieeeAddr, 1);
if(ep1){
ep1.bind('genOnOff', coordinator, (err) => {
if (err) {
console.log('FAILED TO BIND :(');
} else {
console.log('GOOD!');
}
});
}
from zigbee-herdsman-converters.
tb-killa
commented on June 27, 2024
@dzungpv Do you restart your Zigbee-Instance and allow pairing-Mode ? It could be the same as by the hue dimmer switch. I bring up the end-device in pairing mode while the zigbee instance is booting up. this allowed it to map with database entry.
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
I try to restart/reset many time, include formart the sdcard, remove the database but it still the same. Most success is the previous logs
…-------- Original message --------
From: tb-killa <[email protected]>
Date: 6/2/18 7:57 PM (GMT+07:00)
To: Koenkk/zigbee-shepherd-converters <[email protected]>
Cc: Viet Dzung <[email protected]>, Mention <[email protected]>
Subject: Re: [Koenkk/zigbee-shepherd-converters] Device connected but still not get the data for "fromZigbee" (#7)
@dzungpv<https://github.com/dzungpv> Do you restart your Zigbee-Instance and allow pairing-Mode ? It could be the same as by the hue dimmer switch. I bring up the end-device in pairing mode while the zigbee instance is booting up. this allowed it to map with database entry.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#7 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKEv6bGHjgkEfd-wanTZb5kS90iOheLyks5t4ovDgaJpZM4UU5q4>.
from zigbee-herdsman-converters.
Koenkk
commented on June 27, 2024
Isn't this similar to what currently is being done in Koenkk/zigbee2mqtt#36?
from zigbee-herdsman-converters.
dzungpv
commented on June 27, 2024
I try this recently, but still the same, The device run zigbee 3.0/pro firmware, so may be zigbee-shepherd could not handle it. But zigbee 3.0/pro has backward compatible.
I use Ubiqua sniffer, it could get the packet on/off command from manufacture hub.
from zigbee-herdsman-converters.
battuashwik
commented on June 27, 2024
any update on this, i am having the same issue
from zigbee-herdsman-converters.
stale
commented on June 27, 2024
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
from zigbee-herdsman-converters.
Related Issues (20)
- BTH-RM230Z - Missing Cooling Mode HOT 54
- 3A/Nue 15w refreshed downlight RGBCW
- Creating Device with multiple endpoints (and multiple types) HOT 1
- Unsupported Attribute when writing attributes to Sonoff TRVZB HOT 8
- Aqara ZNJLBL01LM (lumi.curtain.acn002) problem after latest dev updates HOT 4
- F00YK04-18-1 problem after latest dev updates
- Add Tongou TOWSMR1 _TZE204_kobbcyum HOT 2
- Supported Device has no input cluster genAnalogInput at getEndpointsWithCluster
- Blitzwolf BSHP13 "No converter available for" HOT 1
- NodOn SIN-4-RS-20 - Add value `8` to `windowCoveringMode` HOT 1
- Vesternet VES-ZB-REM-013 multiple commands for on and off action HOT 1
- Incorrect attribute "occupancy" for iHORN LH03121 door contact sensor HOT 1
- Sonoff TRVZB attributes are not marked with device_category as configuration entities HOT 5
- New device template for SODA Circle S8 window handle `_TZE200_j7sgd8po` HOT 11
- The compiled zcl folder is missing. HOT 1
- Sonoff TRVZB exposes battery_low but never updates it HOT 2
- tuya ZG-204ZM setting motion detection mode fails (pull request #7553) HOT 6
- converter for Homr Multisensor
- Please add support for frient SIRZB-111
- Müller Tint GU10 blub is missing light entity 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 zigbee-herdsman-converters.