Zigbee2mqtt: Zigbee 3.0 Konke devices

[kirovilya]

Konke - is a brand of IoT http://www.ikonke.us/ with a cheap zigbee-devices:
Temperature sensor https://ru.aliexpress.com/item/33015776787.html
Contact sensor https://ru.aliexpress.com/item/33015624877.html
Motion sensor https://ru.aliexpress.com/item/33014773963.html
Mutifunctional button https://ru.aliexpress.com/item/33015636907.html

I bought a button and a motion sensor. With the button everything is fine, but with a motion sensor - no.

He gives the model in an unusual way. We had to slightly change the receipt of the model https://github.com/kirovilya/zigbee-shepherd/commit/0d857c2f5362c31765ccab607303871c80879fb4

Also, it is not possible to configure the device to send messages about the motion.
I added configure code https://github.com/kirovilya/zigbee-shepherd-converters/blob/master/devices.js#L4729 :

        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const actions = [
                (cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb),
                (cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb),
            ];
            execute(device, actions, callback);
        }

But have error in log:

2019-07-04T11:32:10.498Z zigbee-shepherd:request REQ --> AF:dataRequest, transId: 1
2019-07-04T11:32:10.499Z cc-znp:SREQ --> AF:dataRequest, { dstaddr: 1684, destendpoint: 1, srcendpoint: 1, clusterid: 1280, transid: 1, options: 48, radius: 30, len: 14, data: <Buffer 00 01 02 10 00 f0 1e 74 e8 18 00 4b 12 00> }
2019-07-04T11:32:10.508Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'AF',  cmd: 'dataRequest',  payload: { status: 0 },  fcs: 100,  csum: 100 }
2019-07-04T11:32:10.508Z cc-znp:SRSP <-- AF:dataRequest, { status: 0 }
2019-07-04T11:32:10.508Z zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0
2019-07-04T11:32:17.262Z cc-znp { sof: 254,  len: 3,  type: 'AREQ',  subsys: 'AF',  cmd: 'dataConfirm',  payload: { status: 240, endpoint: 1, transid: 1 },  fcs: 55,  csum: 55 }
2019-07-04T11:32:17.263Z cc-znp:AREQ <-- AF:dataConfirm, { status: 240, endpoint: 1, transid: 1 }
2019-07-04T11:32:17.263Z zigbee-shepherd:af dispatchIncomingMsg(): type: dataConfirm, msg: {"status":240,"endpoint":1,"transid":1}
2019-07-04T11:32:17.264Z zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 1
2019-07-04T11:32:17.266Z zigbee-shepherd-converters:devices Configured '(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb)' with result 'Error: AF data request fails, status code: 240. MAC transaction expired.'
Configure 0x086bd7fffee9826b 3AFE14010402000D Error: AF data request fails, status code: 240. MAC transaction expired.

But than I successfully get zoneStatus message:

2019-07-04T11:34:57.791Z cc-znp { sof: 254,  len: 29,  type: 'AREQ',  subsys: 'AF',  cmd: 'incomingMsg',  payload:   { groupid: 0,     clusterid: 1280,     srcaddr: 1684,     srcendpoint: 1,     dstendpoint: 1,     wasbroadcast: 0,     linkquality: 126,     securityuse: 0,     timestamp: 15763610,     transseqnumber: 0,     len: 9,     data: <Buffer 09 08 00 01 00 00 17 00 00> },  fcs: 66,  csum: 66 }
2019-07-04T11:34:57.792Z cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 1280, srcaddr: 1684, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 126, securityuse: 0, timestamp: 15763610, transseqnumber: 0, len: 9, data: <Buffer 09 08 00 01 00 00 17 00 00> }
2019-07-04T11:34:57.792Z zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: {"groupid":0,"clusterid":1280,"srcaddr":1684,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":126,"securityuse":0,"timestamp":15763610,"transseqnumber":0,"len":9,"data":{"type":"Buffer","data":[9,8,0,1,0,0,23,0,0]}}
2019-07-04T11:34:57.794Z zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0
2019-07-04T11:34:57.794Z zigbee:controller event msg { groupid: 0,  clusterid: 1280,  srcaddr: 1684,  srcendpoint: 1,  dstendpoint: 1,  wasbroadcast: 0,  linkquality: 126,  securityuse: 0,  timestamp: 15763610,  transseqnumber: 0,  len: 9,  data:   { '0': 9,     '1': 8,     '2': 0,     '3': 1,     '4': 0,     '5': 0,     '6': 23,     '7': 0,     '8': 0 },  zclMsg:   { frameCntl:      { frameType: 1, manufSpec: 0, direction: 1, disDefaultRsp: 0 },     manufCode: 0,     seqNum: 8,     cmdId: 'statusChangeNotification',     payload: { zonestatus: 1, extendedstatus: 0 } } } { modelId: '3AFE14010402000D' }
Device 0x086bd7fffee9826b incoming event:{"groupid":0,"clusterid":1280,"srcaddr":1684,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":126,"securityuse":0,"timestamp":15763610,"transseqnumber":0,"len":9,"data":{"0":9,"1":8,"2":0,"3":1,"4":0,"5":0,"6":23,"7":0,"8":0},"zclMsg":{"frameCntl":{"frameType":1,"manufSpec":0,"direction":1,"disDefaultRsp":0},"manufCode":0,"seqNum":8,"cmdId":"statusChangeNotification","payload":{"zonestatus":1,"extendedstatus":0}}}
Publish {"linkquality":126}
2019-07-04T11:34:57.795Z zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: {"groupid":0,"clusterid":1280,"srcaddr":1684,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":126,"securityuse":0,"timestamp":15763610,"transseqnumber":0,"len":9,"data":{"0":9,"1":8,"2":0,"3":1,"4":0,"5":0,"6":23,"7":0,"8":0},"zclMsg":{"frameCntl":{"frameType":1,"manufSpec":0,"direction":1,"disDefaultRsp":0},"manufCode":0,"seqNum":8,"cmdId":"statusChangeNotification","payload":{"zonestatus":1,"extendedstatus":0}}}
2019-07-04T11:34:57.795Z zigbee:controller debug handleMessage { type: 'statusChange',  endpoints:   [ Endpoint {       isLocal: [Function],       device: [Device],       profId: 260,       epId: 1,       devId: 1026,       inClusterList: [Array],       outClusterList: [Array],       clusters: [Ziee],       onAfDataConfirm: null,       onAfReflectError: null,       onAfIncomingMsg: null,       onAfIncomingMsgExt: null,       onZclFoundation: [Function: bound onZclFoundation],       onZclFunctional: null,       foundation: [Function],       functional: [Function],       bind: [Function],       unbind: [Function],       read: [Function],       write: [Function],       report: [Function] } ],  data: { cid: 'ssIasZone', zoneStatus: 1 },  linkquality: 126 }
handleMessage. {"type":"statusChange","endpoints":[{"device":{"_id":3,"type":"EndDevice","ieeeAddr":"0x086bd7fffee9826b","nwkAddr":1684,"manufId":4098,"manufName":"Konke","powerSource":"Unknown","dateCode":"","modelId":"3AFE14010402000D","zclVersion":3,"appVersion":20,"stackVersion":0,"hwVersion":1,"epList":[1],"status":"offline","joinTime":null,"endpoints":{"1":"[Circular]"}},"profId":260,"epId":1,"devId":1026,"inClusterList":[0,1,3,1280],"outClusterList":[3],"clusters":{"zapp":null,"genBasic":{"dir":{"cid":"genBasic","sid":"dir","value":1},"attrs":{"cid":"genBasic","sid":"attrs"}},"genPowerCfg":{"dir":{"cid":"genPowerCfg","sid":"dir","value":1},"attrs":{"cid":"genPowerCfg","sid":"attrs"}},"genIdentify":{"dir":{"cid":"genIdentify","sid":"dir","value":3},"attrs":{"cid":"genIdentify","sid":"attrs"}},"ssIasZone":{"dir":{"cid":"ssIasZone","sid":"dir","value":1},"attrs":{"cid":"ssIasZone","sid":"attrs"}}},"onAfDataConfirm":null,"onAfReflectError":null,"onAfIncomingMsg":null,"onAfIncomingMsgExt":null,"onZclFunctional":null}],"data":{"cid":"ssIasZone","zoneStatus":1},"linkquality":126}
2019-07-04T11:34:57.796Z zigbee:controller event statusChange { type: 'statusChange',  endpoints:   [ Endpoint {       isLocal: [Function],       device: [Device],       profId: 260,       epId: 1,       devId: 1026,       inClusterList: [Array],       outClusterList: [Array],       clusters: [Ziee],       onAfDataConfirm: null,       onAfReflectError: null,       onAfIncomingMsg: null,       onAfIncomingMsgExt: null,       onZclFoundation: [Function: bound onZclFoundation],       onZclFunctional: null,       foundation: [Function],       functional: [Function],       bind: [Function],       unbind: [Function],       read: [Function],       write: [Function],       report: [Function] } ],  data: { cid: 'ssIasZone', zoneStatus: 1 },  linkquality: 126 } { cid: 'ssIasZone', modelId: '3AFE14010402000D' }
Device 0x086bd7fffee9826b emit event statusChange with data:{"cid":"ssIasZone","zoneStatus":1}

(sorry, it is logs from ioBroker.zigbee)

There is also new cmdID:

2019-07-04T11:31:57.297Z zigbee-shepherd:af Message has unsupported cmdID: statusChangeNotification

Can the device be normally configured, but did not respond to the request? How to handle this situation?

I will fill this issue with my research on these new devices.

updated:

• it's work only on 15, 20, 25 channels

[tb-killa]

Please provide your modification via PR because we need them for other devices too.
Do you add the statusChangeNotification to your https://github.com/Koenkk/zigbee-shepherd/blob/f6dc5b4469a87c90007dfc9f0d329cdb01d35072/lib/components/af.js#L691 and do your test again?

[kirovilya]

I completely forgot: it's work only on 15, 20, 25 channels

[kirovilya]

@tb-killa I added statusChangeNotificationas you requested. And than also enrollReq command.
Attached some logs
iobroker.2019-07-04.log

[tb-killa]

Please test with this:

const actions = [
                (cb) => device.bind('ssIasZone', coordinator, cb),
                (cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb),
            ];

[kirovilya]

@tb-killa Thank you, I will try in evening

[tb-killa]

Hi @kirovilya any news?

[kirovilya]

@tb-killa get error TypeError: attrId should be a number or a string.
I think that the correct format is
(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb),
but AF data request fails, status code: 240. MAC transaction expired. :(

[kirovilya]

Strange, if I leave only one line in the configuration, it is sometimes successful, and sometimes not.

2019-07-07T08:11:03.455Z zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: {"groupid":0,"clusterid":1280,"srcaddr":34884,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":149,"securityuse":0,"timestamp":2214121,"transseqnumber":0,"len":4,"data":{"0":24,"1":1,"2":4,"3":0},"zclMsg":{"frameCntl":{"frameType":0,"manufSpec":0,"direction":1,"disDefaultRsp":1},"manufCode":0,"seqNum":1,"cmdId":"writeRsp","payload":[{"status":0}]}}
2019-07-07T08:11:03.459Z zigbee-shepherd:request REQ --> AF:dataRequest, transId: 2
2019-07-07T08:11:03.460Z cc-znp:SREQ --> AF:dataRequest, { dstaddr: 34884, destendpoint: 1, srcendpoint: 1, clusterid: 1280, transid: 2, options: 48, radius: 30, len: 6, data: <Buffer 00 02 0c 00 00 f0> }
2019-07-07T08:11:03.462Z zigbee-shepherd-converters:devices Configured '(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb)' with result 'OK'
Successfully configured 0x086bd7fffee9826b 3AFE14010402000D

When two lines of configuration, sometimes it falls not on the first, but on the second line:

2019-07-07T07:05:05.053Z cc-znp:SREQ --> AF:dataRequest, { dstaddr: 34884, destendpoint: 1, srcendpoint: 1, clusterid: 1280, transid: 2, options: 48, radius: 30, len: 6, data: <Buffer 00 02 0c 00 00 f0> }
2019-07-07T07:05:05.060Z zigbee-shepherd-converters:devices Configured '(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb)' with result 'OK'
2019-07-07T07:05:05.082Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'AF',  cmd: 'dataRequest',  payload: { status: 0 },  fcs: 100,  csum: 100 }
2019-07-07T07:05:05.084Z cc-znp:SRSP <-- AF:dataRequest, { status: 0 }
2019-07-07T07:05:05.085Z zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0
2019-07-07T07:05:05.370Z zigbee-shepherd:request REQ --> AF:dataRequest, transId: 3
2019-07-07T07:05:05.372Z cc-znp:SREQ --> AF:dataRequest, { dstaddr: 34884, destendpoint: 1, srcendpoint: 1, clusterid: 1280, transid: 3, options: 48, radius: 30, len: 5, data: <Buffer 01 03 00 00 17> }
2019-07-07T07:05:05.386Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'AF',  cmd: 'dataRequest',  payload: { status: 0 },  fcs: 100,  csum: 100 }
2019-07-07T07:05:05.388Z cc-znp:SRSP <-- AF:dataRequest, { status: 0 }
2019-07-07T07:05:05.389Z zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0
2019-07-07T07:05:06.007Z cc-znp { sof: 254,  len: 3,  type: 'AREQ',  subsys: 'AF',  cmd: 'dataConfirm',  payload: { status: 240, endpoint: 1, transid: 3 },  fcs: 53,  csum: 53 }
2019-07-07T07:05:06.010Z cc-znp:AREQ <-- AF:dataConfirm, { status: 240, endpoint: 1, transid: 3 }
2019-07-07T07:05:06.011Z zigbee-shepherd:af dispatchIncomingMsg(): type: dataConfirm, msg: {"status":240,"endpoint":1,"transid":3}
2019-07-07T07:05:06.014Z zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 3
2019-07-07T07:05:06.018Z zigbee-shepherd-converters:devices Configured '(cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb)' with result 'Error: AF data request fails, status code: 240. MAC transaction expired.'
Configure 0x086bd7fffee9826b 3AFE14010402000D Error: AF data request fails, status code: 240. MAC transaction expired.
Dev 0x086bd7fffee9826b 3AFE14010402000D not configured yet, will try again in latest 300 sec.

[kirovilya]

it seems the sensor goes to sleep does not accept configuration commands. only sometimes, when he is active, is it possible to transfer a command to it.

[kirovilya]

One of the assumptions. Such devices must be configured at the time when they themselves send a message to coordinator. It may be possible at this moment to send them a command.

For example, there were first messages from a device with the enrollRsptype, then they were replaced with the cmdEnrollReqtype. Now comes statusChangeNotificationat motion detection.
Those. as if configuration messages arrive, but not immediately.

[kirovilya]

Also with genPowerCfg. The command is sent, but the response is not waiting. Then come the data on the battery.

2019-07-07 12:56:41.126  - debug: zigbee.0 2019-07-07T09:56:41.126Z zigbee-shepherd:request REQ --> ZDO:bindReq
2019-07-07 12:56:41.128  - debug: zigbee.0 2019-07-07T09:56:41.128Z cc-znp:SREQ --> ZDO:bindReq, { dstaddr: 34884, srcaddr: '0x086bd7fffee9826b', srcendpoint: 1, clusterid: 1, dstaddrmode: 3, addr_short_long: '0x00124b0018e87346', dstendpoint: 1 }
2019-07-07 12:56:41.141  - debug: zigbee.0 2019-07-07T09:56:41.141Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'ZDO',  cmd: 'bindReq',  payload: { status: 0 },  fcs: 69,  csum: 69 }
2019-07-07 12:56:41.142  - debug: zigbee.0 2019-07-07T09:56:41.142Z cc-znp:SRSP <-- ZDO:bindReq, { status: 0 }
2019-07-07 12:56:51.128  - debug: zigbee.0 2019-07-07T09:56:51.128Z zigbee-shepherd:request REQ --> ZDO:bindReq
2019-07-07 12:56:51.130  - debug: zigbee.0 2019-07-07T09:56:51.130Z cc-znp:SREQ --> ZDO:bindReq, { dstaddr: 34884, srcaddr: '0x086bd7fffee9826b', srcendpoint: 1, clusterid: 1, dstaddrmode: 3, addr_short_long: '0x00124b0018e87346', dstendpoint: 1 }
2019-07-07 12:56:51.147  - debug: zigbee.0 2019-07-07T09:56:51.147Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'ZDO',  cmd: 'bindReq',  payload: { status: 0 },  fcs: 69,  csum: 69 }
2019-07-07 12:56:51.151  - debug: zigbee.0 2019-07-07T09:56:51.150Z cc-znp:SRSP <-- ZDO:bindReq, { status: 0 }
2019-07-07 12:57:01.135  - debug: zigbee.0 2019-07-07T09:57:01.134Z zigbee-shepherd-converters:devices Configured '(cb) => device.bind('genPowerCfg', coordinator, cb)' with result 'Error: Timed out after 10000 ms'
2019-07-07 12:57:01.136  - debug: zigbee.0 Configure 0x086bd7fffee9826b 3AFE14010402000D Error: Timed out after 10000 ms
2019-07-07 12:57:01.137  - warn: zigbee.0 Dev 0x086bd7fffee9826b 3AFE14010402000D not configured yet, will try again in latest 300 sec.
2019-07-07 13:00:21.056  - debug: zigbee.0 2019-07-07T10:00:21.056Z cc-znp { sof: 254,  len: 27,  type: 'AREQ',  subsys: 'AF',  cmd: 'incomingMsg',  payload:    { groupid: 0,     clusterid: 1,     srcaddr: 34884,     srcendpoint: 1,     dstendpoint: 1,     wasbroadcast: 0,     linkquality: 102,     securityuse: 0,     timestamp: 1553966,     transseqnumber: 0,     len: 7,     data: <Buffer 08 7e 0a 20 00 20 1c> },  fcs: 76,  csum: 76 }
2019-07-07 13:00:21.058  - debug: zigbee.0 2019-07-07T10:00:21.058Z cc-znp:AREQ <-- AF:incomingMsg, { groupid: 0, clusterid: 1, srcaddr: 34884, srcendpoint: 1, dstendpoint: 1, wasbroadcast: 0, linkquality: 102, securityuse: 0, timestamp: 1553966, transseqnumber: 0, len: 7, data: <Buffer 08 7e 0a 20 00 20 1c> }
2019-07-07 13:00:21.060  - debug: zigbee.0 2019-07-07T10:00:21.060Z zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: {"groupid":0,"clusterid":1,"srcaddr":34884,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":102,"securityuse":0,"timestamp":1553966,"transseqnumber":0,"len":7,"data":{"type":"Buffer","data":[8,126,10,32,0,32,28]}}
2019-07-07 13:00:21.075  - debug: zigbee.0 2019-07-07T10:00:21.075Z zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0
2019-07-07 13:00:21.079  - debug: zigbee.0 2019-07-07T10:00:21.078Z zigbee:controller event msg { groupid: 0,  clusterid: 1,  srcaddr: 34884,  srcendpoint: 1,  dstendpoint: 1,  wasbroadcast: 0,  linkquality: 102,  securityuse: 0,  timestamp: 1553966,  transseqnumber: 0,  len: 7,  data: { '0': 8, '1': 126, '2': 10, '3': 32, '4': 0, '5': 32, '6': 28 },  zclMsg:    { frameCntl: { frameType: 0, manufSpec: 0, direction: 1, disDefaultRsp: 0 },     manufCode: 0,     seqNum: 126,     cmdId: 'report',     payload: [ [Object] ] } } { modelId: '3AFE14010402000D' }
2019-07-07 13:00:21.081  - debug: zigbee.0 Device 0x086bd7fffee9826b incoming event:{"groupid":0,"clusterid":1,"srcaddr":34884,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":102,"securityuse":0,"timestamp":1553966,"transseqnumber":0,"len":7,"data":{"0":8,"1":126,"2":10,"3":32,"4":0,"5":32,"6":28},"zclMsg":{"frameCntl":{"frameType":0,"manufSpec":0,"direction":1,"disDefaultRsp":0},"manufCode":0,"seqNum":126,"cmdId":"report","payload":[{"attrId":32,"dataType":32,"attrData":28}]}}
2019-07-07 13:00:21.082  - debug: zigbee.0 Publish {"linkquality":102}
2019-07-07 13:00:21.085  - debug: zigbee.0 2019-07-07T10:00:21.084Z zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: {"groupid":0,"clusterid":1,"srcaddr":34884,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":102,"securityuse":0,"timestamp":1553966,"transseqnumber":0,"len":7,"data":{"0":8,"1":126,"2":10,"3":32,"4":0,"5":32,"6":28},"zclMsg":{"frameCntl":{"frameType":0,"manufSpec":0,"direction":1,"disDefaultRsp":0},"manufCode":0,"seqNum":126,"cmdId":"report","payload":[{"attrId":32,"dataType":32,"attrData":28}]}}
2019-07-07 13:00:21.097  - debug: zigbee.0 2019-07-07T10:00:21.093Z zigbee:controller debug handleMessage { type: 'attReport',  endpoints:    [ Endpoint {       isLocal: [Function],       device: [Object],       profId: 260,       epId: 1,       devId: 1026,       inClusterList: [Array],       outClusterList: [Array],       clusters: [Object],       onAfDataConfirm: null,       onAfReflectError: null,       onAfIncomingMsg: null,       onAfIncomingMsgExt: null,       onZclFoundation: [Function: bound onZclFoundation],       onZclFunctional: null,       foundation: [Function],       functional: [Function],       bind: [Function],       unbind: [Function],       read: [Function],       write: [Function],       report: [Function] } ],  data: { cid: 'genPowerCfg', data: { batteryVoltage: 28 } },  linkquality: 102,  groupid: 0 }
2019-07-07 13:00:21.100  - debug: zigbee.0 handleMessage. {"type":"attReport","endpoints":[{"device":{"_id":2,"type":"EndDevice","ieeeAddr":"0x086bd7fffee9826b","nwkAddr":34884,"manufId":4098,"manufName":"Konke","powerSource":"Unknown","modelId":"3AFE14010402000D","epList":[1],"status":"offline","joinTime":null,"endpoints":{"1":"[Circular]"}},"profId":260,"epId":1,"devId":1026,"inClusterList":[0,1,3,1280],"outClusterList":[3],"clusters":{"zapp":null,"genBasic":{"dir":{"cid":"genBasic","sid":"dir","value":1},"attrs":{"9":255,"10":{"_isCb":false},"11":"","65533":1,"cid":"genBasic","sid":"attrs","zclVersion":3,"appVersion":20,"stackVersion":0,"hwVersion":1,"manufacturerName":"Konke","modelId":"3AFE14010402000D","dateCode":"","powerSource":0,"appProfileVersion":255}},"genPowerCfg":{"dir":{"cid":"genPowerCfg","sid":"dir","value":1},"attrs":{"65533":1,"cid":"genPowerCfg","sid":"attrs","batteryVoltage":28,"batterySize":255,"batteryVoltMinThres":0,"batteryVoltThres1":0,"batteryVoltThres2":0,"batteryVoltThres3":0,"batteryAlarmState":0}},"genIdentify":{"dir":{"cid":"genIdentify","sid":"dir","value":3},"attrs":{"65533":1,"cid":"genIdentify","sid":"attrs","identifyTime":0}},"ssIasZone":{"dir":{"cid":"ssIasZone","sid":"dir","value":1},"attrs":{"65533":1,"cid":"ssIasZone","sid":"attrs","zoneState":0,"zoneType":13,"zoneStatus":1,"iasCieAddr":"0x00124b0018e87346","zoneId":255}}},"onAfDataConfirm":null,"onAfReflectError":null,"onAfIncomingMsg":null,"onAfIncomingMsgExt":null,"onZclFunctional":null}],"data":{"cid":"genPowerCfg","data":{"batteryVoltage":28}},"linkquality":102,"groupid":0}
2019-07-07 13:00:21.102  - debug: zigbee.0 2019-07-07T10:00:21.100Z zigbee:controller event attReport { type: 'attReport',  endpoints:    [ Endpoint {       isLocal: [Function],       device: [Object],       profId: 260,       epId: 1,       devId: 1026,       inClusterList: [Array],       outClusterList: [Array],       clusters: [Object],       onAfDataConfirm: null,       onAfReflectError: null,       onAfIncomingMsg: null,       onAfIncomingMsgExt: null,       onZclFoundation: [Function: bound onZclFoundation],       onZclFunctional: null,       foundation: [Function],       functional: [Function],       bind: [Function],       unbind: [Function],       read: [Function],       write: [Function],       report: [Function] } ],  data: { cid: 'genPowerCfg', data: { batteryVoltage: 28 } },  linkquality: 102,  groupid: 0 } { cid: 'genPowerCfg', modelId: '3AFE14010402000D' }
2019-07-07 13:00:21.103  - debug: zigbee.0 Device 0x086bd7fffee9826b emit event attReport with data:{"cid":"genPowerCfg","data":{"batteryVoltage":28}}
2019-07-07 13:00:21.106  - debug: zigbee.0 Publish {"battery":"60.00","voltage":2800,"linkquality":102}
2019-07-07 13:01:10.815  - debug: zigbee.0 Pending device configs: ["0x086bd7fffee9826b"]
2019-07-07 13:01:11.119  - debug: zigbee.0 2019-07-07T10:01:11.119Z zigbee-shepherd:request REQ --> ZDO:bindReq
2019-07-07 13:01:11.120  - debug: zigbee.0 2019-07-07T10:01:11.120Z cc-znp:SREQ --> ZDO:bindReq, { dstaddr: 34884, srcaddr: '0x086bd7fffee9826b', srcendpoint: 1, clusterid: 1, dstaddrmode: 3, addr_short_long: '0x00124b0018e87346', dstendpoint: 1 }
2019-07-07 13:01:11.131  - debug: zigbee.0 2019-07-07T10:01:11.131Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'ZDO',  cmd: 'bindReq',  payload: { status: 0 },  fcs: 69,  csum: 69 }
2019-07-07 13:01:11.132  - debug: zigbee.0 2019-07-07T10:01:11.132Z cc-znp:SRSP <-- ZDO:bindReq, { status: 0 }
2019-07-07 13:01:21.121  - debug: zigbee.0 2019-07-07T10:01:21.121Z zigbee-shepherd:request REQ --> ZDO:bindReq
2019-07-07 13:01:21.123  - debug: zigbee.0 2019-07-07T10:01:21.123Z cc-znp:SREQ --> ZDO:bindReq, { dstaddr: 34884, srcaddr: '0x086bd7fffee9826b', srcendpoint: 1, clusterid: 1, dstaddrmode: 3, addr_short_long: '0x00124b0018e87346', dstendpoint: 1 }
2019-07-07 13:01:21.137  - debug: zigbee.0 2019-07-07T10:01:21.137Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'ZDO',  cmd: 'bindReq',  payload: { status: 0 },  fcs: 69,  csum: 69 }
2019-07-07 13:01:21.141  - debug: zigbee.0 2019-07-07T10:01:21.140Z cc-znp:SRSP <-- ZDO:bindReq, { status: 0 }
2019-07-07 13:01:31.124  - debug: zigbee.0 2019-07-07T10:01:31.124Z zigbee-shepherd:request REQ --> ZDO:bindReq
2019-07-07 13:01:31.126  - debug: zigbee.0 2019-07-07T10:01:31.126Z cc-znp:SREQ --> ZDO:bindReq, { dstaddr: 34884, srcaddr: '0x086bd7fffee9826b', srcendpoint: 1, clusterid: 1, dstaddrmode: 3, addr_short_long: '0x00124b0018e87346', dstendpoint: 1 }
2019-07-07 13:01:31.139  - debug: zigbee.0 2019-07-07T10:01:31.139Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'ZDO',  cmd: 'bindReq',  payload: { status: 0 },  fcs: 69,  csum: 69 }
2019-07-07 13:01:31.141  - debug: zigbee.0 2019-07-07T10:01:31.141Z cc-znp:SRSP <-- ZDO:bindReq, { status: 0 }
2019-07-07 13:01:41.126  - debug: zigbee.0 2019-07-07T10:01:41.126Z zigbee-shepherd:request REQ --> ZDO:bindReq
2019-07-07 13:01:41.128  - debug: zigbee.0 2019-07-07T10:01:41.128Z cc-znp:SREQ --> ZDO:bindReq, { dstaddr: 34884, srcaddr: '0x086bd7fffee9826b', srcendpoint: 1, clusterid: 1, dstaddrmode: 3, addr_short_long: '0x00124b0018e87346', dstendpoint: 1 }
2019-07-07 13:01:41.141  - debug: zigbee.0 2019-07-07T10:01:41.141Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'ZDO',  cmd: 'bindReq',  payload: { status: 0 },  fcs: 69,  csum: 69 }
2019-07-07 13:01:41.143  - debug: zigbee.0 2019-07-07T10:01:41.143Z cc-znp:SRSP <-- ZDO:bindReq, { status: 0 }
2019-07-07 13:01:51.128  - debug: zigbee.0 2019-07-07T10:01:51.128Z zigbee-shepherd:request REQ --> ZDO:bindReq
2019-07-07 13:01:51.130  - debug: zigbee.0 2019-07-07T10:01:51.130Z cc-znp:SREQ --> ZDO:bindReq, { dstaddr: 34884, srcaddr: '0x086bd7fffee9826b', srcendpoint: 1, clusterid: 1, dstaddrmode: 3, addr_short_long: '0x00124b0018e87346', dstendpoint: 1 }
2019-07-07 13:01:51.144  - debug: zigbee.0 2019-07-07T10:01:51.144Z cc-znp { sof: 254,  len: 1,  type: 'SRSP',  subsys: 'ZDO',  cmd: 'bindReq',  payload: { status: 0 },  fcs: 69,  csum: 69 }
2019-07-07 13:01:51.151  - debug: zigbee.0 2019-07-07T10:01:51.150Z cc-znp:SRSP <-- ZDO:bindReq, { status: 0 }
2019-07-07 13:02:01.133  - debug: zigbee.0 2019-07-07T10:02:01.133Z zigbee-shepherd-converters:devices Configured '(cb) => device.bind('genPowerCfg', coordinator, cb)' with result 'Error: Timed out after 10000 ms'
2019-07-07 13:02:01.134  - debug: zigbee.0 Configure 0x086bd7fffee9826b 3AFE14010402000D Error: Timed out after 10000 ms
2019-07-07 13:02:01.134  - warn: zigbee.0 Dev 0x086bd7fffee9826b 3AFE14010402000D not configured yet, will try again in latest 300 sec.

[tb-killa]

Any news on this?
I buy two devices, but they will arrived sadly at the end of this month.

[kirovilya]

@tb-killa No news. :(
I added converters for these devices to my converters-fork, but I haven’t done the PR yet as I couldn't correctly configure the devices. Only as I described above - performed one configure-message at a time.

[tb-killa]

Please provide your database.db content for the the ias device.
Maybe it support the polling cluster?
Or we have do some bad magic trick like hold device online by flooding with basic readinga and do our configuration part between this time slots.

[kirovilya]

shepherd.zip

[fairecasoimeme]

For motion sensor and door sensor, you have to manage 0x500 cluster with enrollment mechanism.
The most important things that the two sensors talk to 0x15 endpoint.
you can see some traces here :
http://faire-ca-soi-meme.fr/domotique/2019/07/16/test-du-kit-zigbee-konke-smart-home/

[kirovilya]

@fairecasoimeme Great! Thanks for the detailed investigation! I read.

[anshgh]

Hi
Why are Konke devices missing on this page?
http://www.zigbee2mqtt.io/information/supported_devices.html

[kirovilya]

@anshgh Cause it's not complete yet

I tried to add endpoint 21 to the coordinator - I started receiving requests for cmdEnrollReq. Now need to learn how to respond to them from the coordinator.

[tb-killa]

@kirovilya Any News ? My Devices arrived and i do some tests with manual adding ep15 to coordinator but this doesn´t seemt to work in right way.

Maybe we should forward ep:15 to ep:1 as we do with others via https://github.com/Koenkk/Z-Stack-firmware/commit/265ca6dc9027b61efd182b0cfaf55c706827a3dd#diff-722c0d664df72aed6df38b27a738c95eR74

@Koenkk Do you could compile Test-Firmware where we also forward EP:15 to EP:1 ?
This could maybe help to integrate this Product.

[Koenkk]

15 or 21? https://github.com/Koenkk/zigbee2mqtt/issues/1689#issuecomment-513146534

[tb-killa]

And that's the subtlety. Instead of addressing endpoint 0x01 (normally the coordinator), it sends its request to 0x15 .

Source from https://github.com/Koenkk/zigbee2mqtt/issues/1689#issuecomment-512192524

[Koenkk]

@kirovilya could you modify the firmware to also forward ep15?

@tb-killa looks like something is wrong with your manual zigbee-shepherd-covnerters setup, probably the format is not OK.

[tb-killa]

Got new Messages =)

@Koenkk @kirovilya Maybe we doesn´t need some tweaks on firmware side because the iasZone is also in EP:1 by Default.

My devices.js entry

// Konke
    {
        zigbeeModel: ['3AFE14010402000D'],
        model: '3AFE14010402000D',
        vendor: 'Konke',
        description: 'Motion Sensor',
        supports: 'motion',
        fromZigbee: [fz.generic_batteryvoltage_3000_2500, fz.ignore_power_change,
fz.ignore_basic_change, fz.ignore_genIdentify_change],
        toZigbee: [],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
             const device = shepherd.find(ieeeAddr, 1);
             const actions = [
                 //(cb) => device.write('ssIasZone', 'iasCieAddr', coordinator.device.getIeeeAddr(), cb),
        (cb) => device.bind('ssIasZone', coordinator, cb),
        (cb) => device.functional('ssIasZone', 'enrollRsp', {enrollrspcode: 0, zoneid: 23}, cb),
        (cb) => device.report('ssIasZone', 'zoneStatus', 0, 1000, null, cb),
                (cb) => device.bind('genPowerCfg', coordinator, cb),
                (cb) => device.report('genPowerCfg', 'batteryVoltage', repInterval.HOUR, repInterval.MAX, cb),
             ];
             execute(device, actions, callback);
         }
    },

Trick: Push the little Button inside the Motion Sensor Multiple Times to Trigger the "Configuration" Part and wait for the Response.

2019-7-21 19:03:07 - debug: Received zigbee message of type 'devInterview' with data '"0x086bd7fffee97be7"'
2019-7-21 19:03:11 - debug: Received zigbee message of type 'readRsp' with data '{"cid":"genIdentify","data":{"65533":1,"identifyTime":0}}' of device '3AFE14010402000D' (0x086bd7fffee97be7) of endpoint 1
2019-7-21 19:03:11 - debug: Received zigbee message of type 'devChange' with data '{"cid":"genIdentify","data":{"65533":1,"identifyTime":0}}' of device '3AFE14010402000D' (0x086bd7fffee97be7) of endpoint 1
2019-7-21 19:03:11 - warn: No converter available for '3AFE14010402000D' with cid 'genIdentify', type 'devChange' and data '{"cid":"genIdentify","data":{"65533":1,"identifyTime":0}}'
2019-7-21 19:03:11 - warn: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
2019-7-21 19:03:11 - debug: Received zigbee message of type 'devInterview' with data '"0x086bd7fffee97be7"'
2019-7-21 19:03:15 - debug: Received zigbee message of type 'readRsp' with data '{"cid":"ssIasZone","data":{"zoneState":0,"zoneType":13,"zoneStatus":205,"iasCieAddr":"0x0000000000000000","zoneId":255}}' of device '3AFE14010402000D' (0x086bd7fffee97be7) of endpoint 1
2019-7-21 19:03:15 - debug: Received zigbee message of type 'devChange' with data '{"cid":"ssIasZone","data":{"zoneState":0,"zoneType":13,"zoneStatus":205,"iasCieAddr":"0x0000000000000000","zoneId":255}}' of device '3AFE14010402000D' (0x086bd7fffee97be7) of endpoint 1
2019-7-21 19:03:15 - warn: No converter available for '3AFE14010402000D' with cid 'ssIasZone', type 'devChange' and data '{"cid":"ssIasZone","data":{"zoneState":0,"zoneType":13,"zoneStatus":205,"iasCieAddr":"0x0000000000000000","zoneId":255}}'
2019-7-21 19:03:15 - warn: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
2019-7-21 19:03:17 - debug: Received zigbee message of type 'readRsp' with data '{"cid":"ssIasZone","data":{"65533":1}}' of device '3AFE14010402000D' (0x086bd7fffee97be7) of endpoint 1
2019-7-21 19:03:17 - debug: Received zigbee message of type 'devChange' with data '{"cid":"ssIasZone","data":{"65533":1}}' of device '3AFE14010402000D' (0x086bd7fffee97be7) of endpoint 1
2019-7-21 19:03:17 - warn: No converter available for '3AFE14010402000D' with cid 'ssIasZone', type 'devChange' and data '{"cid":"ssIasZone","data":{"65533":1}}'
2019-7-21 19:03:17 - warn: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
2019-7-21 19:03:17 - debug: Received zigbee message of type 'devInterview' with data '"0x086bd7fffee97be7"'
zigbee-shepherd:af Message has unsupported cmdID: enrollReq

After adding the cmdID and Restart i got this after first Push on the EndDevice:

zigbee2mqtt:debug 2019-7-21 19:14:13 Received zigbee message of type 'cmdEnrollReq' with data '{"cid":"ssIasZone","data":{"zonetype":13,"manucode":4098}}' of device '3AFE14010402000D' (0x086bd7fffee97be7) of endpoint 1
  zigbee2mqtt:warn 2019-7-21 19:14:13 No converter available for '3AFE14010402000D' with cid 'ssIasZone', type 'cmdEnrollReq' and data '{"cid":"ssIasZone","data":{"zonetype":13,"manucode":4098}}'
  zigbee2mqtt:warn 2019-7-21 19:14:13 Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

Now we need to do the cmdEnrollReq Response ?
Ideas ?

Edit#1:

After some Minutes i Receive this one too:

2019-7-21 19:49:06 - debug: Received zigbee message of type 'statusChange' with data '{"zonestatus":1,"extendedstatus":0,"cid":"ssIasZone"}' of device '3AFE14010402000D' (0x086bd7fffee97be7) of endpoint 1
2019-7-21 19:49:06 - warn: No converter available for '3AFE14010402000D' with cid 'ssIasZone', type 'statusChange' and data '{"zonestatus":1,"extendedstatus":0,"cid":"ssIasZone"}'
2019-7-21 19:49:06 - warn: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

Edit#2:

After Restart new Message :)

zigbee-shepherd:af Message has unsupported cmdID: statusChangeNotification

Edit#3:

And now after another Restart:

  zigbee2mqtt:debug 2019-7-21 19:57:26 Received zigbee message of type 'cmdStatusChangeNotification' with data '{"cid":"ssIasZone","data":{"zonestatus":205,"extendedstatus":0}}' of device '3AFE14010402000D' (0x086bd7fffee97be7) of endpoint 1
  zigbee2mqtt:warn 2019-7-21 19:57:26 No converter available for '3AFE14010402000D' with cid 'ssIasZone', type 'cmdStatusChangeNotification' and data '{"cid":"ssIasZone","data":{"zonestatus":205,"extendedstatus":0}}'
  zigbee2mqtt:warn 2019-7-21 19:57:26 Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

Edit#4:
The Motion Sensor only Report True on Motion, it doesn´t report false.
I modify the bitron motion converter and use them for this device too.

Works :)

[tb-killa]

Will publish the end version of the devices.js entry and the modifications for af.js and the converter soon.

[kirovilya]

Sorry, I was busy.
I tried made Zive app with handlers:

// Init Command Response Handler
cieClusters.init('ssIasZone', 'cmdRsps', {
    enrollReq: (zapp, data, cb) => {
        zapp.functional(
            data.src.ieeeAddr,
            data.src.epId,
            'ssIasZone',
            'enrollRsp',
            {enrollrspcode: 0x00, zoneid : 6},
            {direction: 0},
            cb
        );
    },
    statusChangeNotification: (zapp, argObj, cb) => {},
});

and mount it to the 21 (0x15) endpoint (some rewrite mount method here and parameters):

this.shepherd.mount(cieApp, 21, (err, epId) => {
    if (!err) {
        this.debug(`Mounted the cieApp (epId ${epId})`);
    } else {
        this.error(`Failed to mount the cieApp`);
    }
});

Now I request cmdEnrollReq and send enrollRsp from 21 (0x15) endpoint.

It worked for the contact sensor. But it did not work so well for the motion sensor.
Contact sensor send data to endpoint 1:

zigbee:controller event cmdStatusChangeNotification { type: 'cmdStatusChangeNotification',  endpoints:    [ Endpoint {       isLocal: [Function],       device: [Object],       profId: 260,       epId: 1,       devId: 1026,       inClusterList: [Array],       outClusterList: [Array],       clusters: [Object],       onAfDataConfirm: null,       onAfReflectError: null,       onAfIncomingMsg: null,       onAfIncomingMsgExt: null,       onZclFoundation: [Function: bound onZclFoundation],       onZclFunctional: null,       foundation: [Function],       functional: [Function],       bind: [Function],       unbind: [Function],       read: [Function],       write: [Function],       report: [Function] } ],  data: { cid: 'ssIasZone', data: { zonestatus: 1, extendedstatus: 0 } },  linkquality: 157,  groupid: 0 } { cid: 'ssIasZone', modelId: '3AFE130104020015' }
Device 0x086bd7fffee96d7c emit event cmdStatusChangeNotification with data:{"cid":"ssIasZone","data":{"zonestatus":1,"extendedstatus":0}}
No converter available for '2AJZ4KPDR' with cid 'ssIasZone' and type 'cmdStatusChangeNotification'

But motion sensor send to endpoint 21 (0x15) and not found model :( :

zigbee:controller debug handleMessage { type: 'cmdStatusChangeNotification',  endpoints:    [ Coordpoint {       isLocal: [Function],       device: [Object],       profId: 260,       epId: 21,       devId: 1024,       inClusterList: [],       outClusterList: [Array],       clusters: [Object],       onAfDataConfirm: null,       onAfReflectError: null,       onAfIncomingMsg: null,       onAfIncomingMsgExt: null,       onZclFoundation: [Function: bound onZclFoundation],       onZclFunctional: [Function],       isDelegator: [Function],       foundation: [Function],       functional: [Function],       bind: [Function],       unbind: [Function],       read: [Function],       write: [Function],       report: [Function] } ],  data: { cid: 'ssIasZone', data: { zonestatus: 1, extendedstatus: 0 } },  linkquality: 123,  groupid: 0 }
zigbee:controller debug Message without modelId! undefined

[bedenko]

@kirovilya: could you elaborate on how did you manage to pair Konke button?
I flashed CC2531ZNP-with-SBL.hex (from CC2531_20190425.zip).
I held reset button until led began to flash, but i get nothing in console. Not even with DEBUG=* flag set.

[kirovilya]

it's work only on 15, 20, 25 channels

[bedenko]

Ouch, i missed that part.
It is working now. Thank you!

[elpaul]

I have a problem with the button. Sometimes it works well for a long time, and sometimes it stops working and then I see something in the logs:
zigbee2mqtt:info 8/12/2019, 5:53:54 AM MQTT publish: topic 'zigbee2mqtt/0x086bd7fffebfe5ee', payload '{"linkquality":76,"battery":"NaN","voltage":null}'

[kirovilya]

Hi! I made changes https://github.com/kirovilya/zigbee-shepherd/commit/a4c71f5715a4461be886b1abfeca09ccd7e725d8 and https://github.com/kirovilya/zigbee-shepherd-converters/commit/8090ad0bc5511bb09cc0e8f08a00ab8840d69041

Can anyone else besides me verify the correct pairing and working of Konke motion sensor and contact?

For me It's began to pair and work correctly with these changes.

[zhapwey]

good I have a konke temperature sensor is already done to include it in the library or is it pending?
What can I get with him

Best Regards

[kirovilya]

@zhapwey temperature sensor is already works, but in dev-branch of z2m

[elsbrock]

Can anyone else besides me verify the correct pairing and working of Konke motion sensor and contact?

Could you provide the steps to build it? What version of zigbee2mqtt do I need to check out?

I have a motion sensor here and am interested in getting it mainlined.

[elsbrock]

@kirovilya highlight in case you missed my reply

[kirovilya]

@elsbrock Now there is no version of z2m that can work with this sensor. If you can, make changes to the code described above. I checked, but my sensor is not always configuring correctly.

[elsbrock]

I am aware, was trying to understand how I can apply your changes to zigbee2mqtt, because it looks like one of the libraries was changed to another one?

[kirovilya]

@elsbrock You must find and modify the code lines in the same files in your libraries.
Nobody can confirm this changes, so I not to do PR to zigbee-shepherd for z2m.
after the moving to a new version of the zigbee-herdsman, I will do PR to it.

[paulgking]

@kirovilya I've applied similar changes to my setup for the motion sensor and so far it appears to be working, has registered ok and I get notifications on sensor activation. I have done this for two sensors so appears to not be just blind luck.

Though no homeassistant MQTT messages, and the battery level I suspect needs work, both reporting 2800 voltage and 60.00%, hard to tell if this is accurate or not, but as both just out of the box would seem odd they are precisely the same level run down.

[paulgking]

Subsequent to a restart or two, it is no longer working, getting:

/app/lib/extension/deviceReceive.js:109

                if (c.cid === cid) {

                      ^



TypeError: Cannot read property 'cid' of undefined

    at mappedDevice.fromZigbee.filter (/app/lib/extension/deviceReceive.js:109:23)

    at Array.filter (<anonymous>)

    at DeviceReceive.onZigbeeMessage (/app/lib/extension/deviceReceive.js:105:52)

    at extensions.filter.forEach (/app/lib/controller.js:143:31)

    at Array.forEach (<anonymous>)

    at Controller.onZigbeeMessage (/app/lib/controller.js:143:14)

    at Zigbee.onMessage (/app/lib/zigbee.js:275:18)

removing the devices seems to stop that, so I assume they aren't setting up properly.

[kirovilya]

@paulgking I will rewrite the code a bit, after switching to zigbee-herdsman. And make PR

[paulgking]

I've now sniffed the traffic between the konke hub and a motion sensor. I'm not seeing anything unusual.

Device joins network.
Hub writes IASCIEAddress
Sensor Responds ok
Hub reads IASCIEAddress
Sensor Responds
Sensor sends EnrollRequest
Hub Response to EnrollRequest
Hub reads attributes (Zone State, Zone Type, Zone Status)
Sensor Responds State:Enrolled, Type: MotionSensor, Status 0

I can't see endpoint 21 anywhere, it's all on endpoint 1.

I'll reconfiqure the shepard-converters to the simple form and try sniffing that, probably tomorrow now.

edit: correct request and response sources.

[paulgking]

Update on that I've traced trying to join to Zigbee2Mqtt with a basic setup.

This time the message setup is quite different, I never see the output IASCIEAddress stuff, but I do see an incoming Enroll Request on endpoint 21.

Not clear why we'd get this different behaviour.

One thing I note is that with the Konke hub, after joining the hub does send a "Match Descriptor" request for IAS and the response acknowledges specifying endpoint 1.

That isn't the same for Zigbee2Mqtt where we get a simple descriptor request and response, the response includes IAS as an input cluster.

This is beyond my understanding at this point, but will keep trying chip away.

[tb-killa]

hi @kirovilya @paulgking

I push some changes from my working implementation.
i test with motion and contact sensors at now more than 5 days and it seems to be stable.
please check and do test again and report.

https://github.com/Koenkk/zigbee-shepherd-converters/pull/628
https://github.com/Koenkk/zigbee-herdsman/pull/34
https://github.com/Koenkk/zigbee-herdsman/issues/35

[tb-killa]

Does someone who own the konke hub too could check if the motion sensor show some sort of blue led trigger on motion?

With Z2M we see the motion only in converter state but would be interested if this could work too.

[paulgking]

@tb-killa The konke app is pretty limited so no options to set, not even a battery level display for the motion sensor. No visible output on the sensor itself when triggered, just at Zone Status Change Notification message, with "Alarm 1" set.

[paulgking]

Had this up and running for a few days now. One of the motion sensors didn't seem to register properly and was only reporting link quality and battery, at some point it started working, so perhaps to 100% but working reliably now.

Thanks.

[paulgking]

I noticed both my two motion sensors were saying voltage 2900 battery 80.00 out of the box, so did some experimentation with one of them.

Testing up to a bench power supply and seeing what I got with one of my devices (the other I assume will be the same)

At 3.00v it was reading voltage 2800, battery 60%. This is the nominal voltage of a new battery (in reality they are slightly higher, hence my 2900 80%), so it's clearly not reading very well.

At 2.70v it's reading voltage 2500, battery 0%.

At 2.50v it's reading voltage 2300, battery 0% (Not sure if this would work with a real battery, since the power supply can generate the current requirements, don't know enough about the batteries to know if it could, though it seems to be less the 20ma drawn at startup - maybe higher this is just by eye on a meter)

At 2.75v it's reading voltage 2600, battery 20%

At no stage did I see the low battery indicator in the alarm messages.

So basic observation is that it's reading somewhere around 0.2v low, the % steps are 20%. The low battery indicator doesn't work and the % remaining is pretty misleading.

Given the konke hub/app don't show battery on these, my guess would be the battery stuff simply hasn't been setup/calibrated and is likely just a side effect of the code they based theirs on - quite possibly setup for a higher initial voltage battery.

So I doubt anyone should be relying on the battery values it gives for anything meaningful, later versions/revisions of the motion sensor firmware could resolve this I guess.

[tb-killa]

I thought battery percentage are from Z2M internal calculation per Converter? We should check them up because we report only voltage. Maybe we need some tweak for this.
But thanks for the response because this show up the devices work with Z2M.

[paulgking]

Good point, I hadn't considered we maybe generating the %. I've done some further testing and it works down to 2.1v from a power suppy reading 2000 for voltage at that stage. At 2v it stops starting up. So if it is Z2M computing % we can probably do something better, though I doubt it scales linearly.

Still the low battery flag in the alert never happens.

[tb-killa]

It's here https://github.com/Koenkk/zigbee-shepherd-converters/blob/b38f3db77e8bf82526454057e3ca76785fed3489/converters/fromZigbee.js#L1456

This converter is used for the motion actually.
Please test and tweak so we could prepare an PR.

[ukrtrip]

Hello! I purchased a few Konke sensors on aliexpress.
The motion sensor has a model 2AJZ4-KPBS and is detected by the Z2M as '3AFE27010402000D'. I added it to the devices.js - It works correctly:
(LOG: _MQTT publish: topic 'zigbee2mqtt/KonkeMotionSensor', payload '{"occupancy":false,"tamper":false,"battery_low":false,"linkquality":42,"battery":"100.00","voltage":3000}'_)
devices.js:

{
    zigbeeModel: ['3AFE14010402000D', '3AFE27010402000D'],
    model: '2AJZ4KPBS',
    vendor: 'Konke',
    description: 'Motion sensor',
    supports: 'occupancy',
    fromZigbee: [fz.iaszone_occupancy_1_with_timeout, fz.battery_3V],
    toZigbee: [],
},

Please add the '3AFE27010402000D' zigbeeModel to the main (and dev) repository.
This is tested in the last dev repository (zigbee-herdsman: 0.9.2, zigbee-herdsman-converters: 11.1.24)

A few photos from the inside

[Koenkk]

@ukrtrip added, thanks!

[yarosman]

Hello, could you tell what is the current status for these devices supporting ?

[DimsterTim]

Would be nice if someone adds Konke:

1. Door Sensor 2AJZ4KPDR with the "modelId":"3AFE270104020015".
   zigbee2mqtt:debug 10/26/2019, 10:49:23 AM Received zigbee message of type 'endDeviceAnnce' with data '"0x086bd7fffee96aad"' of device '3AFE270104020015' (0x086bd7fffee96aad) of endpoint 1
   zigbee2mqtt:warn 10/26/2019, 10:49:23 AM Device with modelID '3AFE270104020015' is not supported.

1. Motion Sensor 2AJZ4KPBS with the "modelId":"3AFE28010402000D".
   zigbee2mqtt:debug 10/26/2019, 10:41:28 AM Received zigbee message of type 'readRsp' with data '{"cid":"genBasic","data":{"manufacturerName":"Konke","modelId":"3AFE28010402000D","powerSource":3}}' of device '3AFE28010402000D' (0x14b457fffe46a74e) of endpoint 1
   zigbee2mqtt:warn 10/26/2019, 10:41:28 AM Device with modelID '3AFE28010402000D' is not supported.
   zigbee2mqtt:warn 10/26/2019, 10:41:28 AM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html
   zigbee2mqtt:debug 10/26/2019, 10:41:31 AM Received zigbee message of type 'readRsp' with data '{"cid":"genBasic","data":{"zclVersion":3,"appVersion":40,"stackVersion":0,"hwVersion":1,"dateCode":"190829"}}' of device '3AFE28010402000D' (0x14b457fffe46a74e) of endpoint 1
   zigbee2mqtt:warn 10/26/2019, 10:41:31 AM Device with modelID '3AFE28010402000D' is not supported.

I added your code and getting the following on motion:
zigbee2mqtt:warn 10/26/2019, 2:32:14 PM No converter available for '2AJZ4KPBS' with cid 'ssIasZone', type 'statusChange' and data '{"cid":"ssIasZone","zoneStatus":1}'
zigbee2mqtt:warn 10/26/2019, 2:32:14 PM Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

[Koenkk]

I've also ordered some Konke sensor: door contact, water detector, button and occupancy sensor.

@DimsterTim I've got the same model ID's so these are supported now.

I also did some improvements regarding pairing, they should pair successful now (zigbee-herdsman). If not try pressing the reset button again and then they should. Changes are in latest zigbee2mqtt-dev.

[DimsterTim]

Nice! I wonder when it will appear in Zigbee2mqtt Hass.io Add-on..

[Koenkk]

@DimsterTim already available in latest zigbee2mqtt edge addon.

[pbangsoe]

Is there any downside if I change channel to support Konke
I have Ikea, Hue, Xaomi devises set up default with channel 11.

I understand that I have to pair devices again, but will there be any problems with other or new devices if I change the channel to 20

[Koenkk]

@pbangsoe no this doesn't matter

[pbangsoe]

@pbangsoe no this doesn't matter

@Koenkk Thanks

[rcpoison]

According to the description the motion sensor supports "light intensity" (https://www.aliexpress.com/item/33014773963.html), but I don't see that metric.
Is it false advertisement or simply not implemented in zigbee2mqtt?

[alex-savin]

Today received a bunch of Konke devices, was trying to pair them.

But have got some errors with Temp/Humidity sernsor

zigbee2mqtt:warn  2019-11-27T18:46:49: Received message from unsupported device with Zigbee model '3AFE220103020000'
zigbee2mqtt:warn  2019-11-27T18:46:49: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

[rcpoison]

@alex-savin I've already added that model#.
You can either build the git version or manually edit devices.js.
See: https://github.com/Koenkk/zigbee-herdsman-converters/commit/99cb6c3502c585f78243ec5651ae1511188d5fbb

[SeLLeRoNe]

Hey guys, I am trying to pair a 2AJZ4KPBS but for some reason it always fail.

Some background informations:

• It was paired, and it was working with the current setup until yesterday evening
• Yesterday evening I rebooted the NUC where z2m runs and on restart, that Konke motion sensor was no longer available
• I tried to repair it without success, so I changed the channel from 25 to 20 and now to 15, it start the pairing but always fail, doesn't matter if I press once,twice, 5 secs, forever

One thing I noticed is that if I try the pairing for a few times with failures, all my mains connected zigbee devices (ikea lamp, HEIMAN Siren, CC2531 Router) starts to go offline and remains offline for about 5 minutes, then they come back online by themself (if I don't keep trying the pairing).

I am using the stack-3 firmware both on my coordinator and on the cc2531 Router.

I am not sure is there anything I can do to provide more informations, if so, please let me know.

Thanks
Andrea

[CodeFinder2]

Just paired a Konke multi function button / switch on channel 15 on latest dev branch succesfully, although I received some strange errors:

$ npm start

> [email protected] start /opt/zigbee2mqtt
> node index.js

zigbee2mqtt:info  2019-12-22 13:28:22: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2019-12-22.13-28-22'
zigbee2mqtt:debug 2019-12-22 13:28:22: Loaded state from file /opt/zigbee2mqtt/data/state.json
zigbee2mqtt:info  2019-12-22 13:28:22: Starting zigbee2mqtt version 1.8.0-dev (commit #66b3bcb)
zigbee2mqtt:info  2019-12-22 13:28:22: Starting zigbee-herdsman...
zigbee2mqtt:debug 2019-12-22 13:28:22: Using zigbee-herdsman with settings: '{"network":{"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[15],"networkKey":"HIDDEN"},"databasePath":"/opt/zigbee2mqtt/data/database.db","databaseBackupPath":"/opt/zigbee2mqtt/data/database.db.backup","backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyUSB0"}}'
zigbee2mqtt:info  2019-12-22 13:28:29: zigbee-herdsman started
zigbee2mqtt:info  2019-12-22 13:28:29: Coordinator firmware version: '{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190619}}'
zigbee2mqtt:debug 2019-12-22 13:28:29: Zigbee network parameters: {"panID":6754,"extendedPanID":"0xdddddddddddddddd","channel":15}
zigbee2mqtt:info  2019-12-22 13:28:29: Currently 0 devices are joined:
zigbee2mqtt:warn  2019-12-22 13:28:29: `permit_join` set to  `true` in configuration.yaml.
zigbee2mqtt:warn  2019-12-22 13:28:29: Allowing new devices to join.
zigbee2mqtt:warn  2019-12-22 13:28:29: Set `permit_join` to `false` once you joined all devices.
zigbee2mqtt:info  2019-12-22 13:28:29: Zigbee: allowing new devices to join.
zigbee2mqtt:info  2019-12-22 13:28:29: Connecting to MQTT server at mqtt://localhost
zigbee2mqtt:info  2019-12-22 13:28:29: Connected to MQTT server
zigbee2mqtt:info  2019-12-22 13:28:29: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
zigbee2mqtt:info  2019-12-22 13:28:29: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.8.0-dev","commit":"66b3bcb","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190619}},"log_level":"debug","permit_join":true}'
zigbee2mqtt:debug 2019-12-22 13:33:22: Saving state to file /opt/zigbee2mqtt/data/state.json
zigbee2mqtt:debug 2019-12-22 13:38:22: Saving state to file /opt/zigbee2mqtt/data/state.json
zigbee2mqtt:debug 2019-12-22 13:43:22: Saving state to file /opt/zigbee2mqtt/data/state.json
zigbee2mqtt:info  2019-12-22 13:46:04: Device '0x086bd7fffee976a6' joined
zigbee2mqtt:info  2019-12-22 13:46:04: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":{"friendly_name":"0x086bd7fffee976a6"}}'
zigbee2mqtt:info  2019-12-22 13:46:04: Starting interview of '0x086bd7fffee976a6'
zigbee2mqtt:info  2019-12-22 13:46:04: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"0x086bd7fffee976a6"}}'
zigbee2mqtt:debug 2019-12-22 13:46:05: Device '0x086bd7fffee976a6' announced itself
zigbee2mqtt:debug 2019-12-22 13:46:06: Received Zigbee message from '0x086bd7fffee976a6', type 'readResponse', cluster 'genBasic', data '{"modelId":"3AFE170100510001","manufacturerName":"Konke","powerSource":0}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2019-12-22 13:46:06: No converter available for '2AJZ4KPKEY' with cluster 'genBasic' and type 'readResponse' and data '{"modelId":"3AFE170100510001","manufacturerName":"Konke","powerSource":0}'
zigbee2mqtt:debug 2019-12-22 13:46:08: Received Zigbee message from '0x086bd7fffee976a6', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3,"appVersion":23,"stackVersion":1}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2019-12-22 13:46:08: No converter available for '2AJZ4KPKEY' with cluster 'genBasic' and type 'readResponse' and data '{"zclVersion":3,"appVersion":23,"stackVersion":1}'
zigbee2mqtt:error 2019-12-22 13:46:08: Failed to interview '0x086bd7fffee976a6', device has not successfully been paired
zigbee2mqtt:info  2019-12-22 13:46:08: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_failed","meta":{"friendly_name":"0x086bd7fffee976a6"}}'
zigbee2mqtt:info  2019-12-22 13:46:08: Configuring '0x086bd7fffee976a6'
zigbee2mqtt:debug 2019-12-22 13:46:10: Received Zigbee message from '0x086bd7fffee976a6', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3,"appVersion":23,"stackVersion":1}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2019-12-22 13:46:10: No converter available for '2AJZ4KPKEY' with cluster 'genBasic' and type 'readResponse' and data '{"zclVersion":3,"appVersion":23,"stackVersion":1}'
zigbee2mqtt:debug 2019-12-22 13:46:13: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryVoltage":31}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:46:13: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":143}'
zigbee2mqtt:error 2019-12-22 13:46:18: Failed to configure '0x086bd7fffee976a6', attempt 1 (Error: AREQ - ZDO - bindRsp after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10))
zigbee2mqtt:debug 2019-12-22 13:46:38: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":128}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:46:38: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":114,"click":"single"}'
zigbee2mqtt:info  2019-12-22 13:46:38: Configuring '0x086bd7fffee976a6'
zigbee2mqtt:debug 2019-12-22 13:46:40: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":128}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:46:40: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":122,"click":"single"}'
zigbee2mqtt:debug 2019-12-22 13:46:45: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":128}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:46:45: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":101,"click":"single"}'
zigbee2mqtt:info  2019-12-22 13:46:45: Succesfully configured '0x086bd7fffee976a6'
zigbee2mqtt:debug 2019-12-22 13:46:46: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":128}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:46:46: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":85,"click":"single"}'
zigbee2mqtt:debug 2019-12-22 13:46:48: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":129}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:46:48: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":88,"click":"double"}'
zigbee2mqtt:debug 2019-12-22 13:46:54: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":128}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:46:54: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":93,"click":"single"}'
zigbee2mqtt:debug 2019-12-22 13:46:57: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":130}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:46:57: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":111,"click":"long"}'


zigbee2mqtt:debug 2019-12-22 13:47:06: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":128}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:47:06: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":119,"click":"single"}'
zigbee2mqtt:debug 2019-12-22 13:47:07: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":128}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:47:07: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":117,"click":"single"}'
zigbee2mqtt:debug 2019-12-22 13:47:09: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":128}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:47:09: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":98,"click":"single"}'
zigbee2mqtt:debug 2019-12-22 13:47:10: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":128}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:47:10: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":98,"click":"single"}'
zigbee2mqtt:debug 2019-12-22 13:47:11: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":129}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:47:11: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":85,"click":"double"}'
zigbee2mqtt:debug 2019-12-22 13:47:13: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":129}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:47:13: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":83,"click":"double"}'
zigbee2mqtt:debug 2019-12-22 13:47:15: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":129}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2019-12-22 13:47:15: MQTT publish: topic 'zigbee2mqtt/0x086bd7fffee976a6', payload '{"battery":"100.00","voltage":3100,"linkquality":85,"click":"double"}'
zigbee2mqtt:debug 2019-12-22 13:47:16: Received Zigbee message from '0x086bd7fffee976a6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":129}' from endpoint 1 with groupID 0

I don't know if they can be fixed. The device was working though (single, double, long press, see log). ;-)

[bearli97]

Hi, I think I've got the Konke Motion Sensor 2AJZ4KPBS working now with the 1.8.0-dev. Is there a way to change the "state":"ON"-duration, which is preconfigured in the Konke with 90 seconds? Or would you suggest using rules and a timed switch in my openHAB?

[JHeijting]

Hi there,

I would like to add a Konke Motion Sensor 2AJZ4KPBS to my collection. Is there any way to pair this device with channel 11? I'm not feeling like repairing my 18 devices when switching channel.

At this point I receive the _No converter available for 'ZNCZ02LM' with cluster 'genTime' and type 'read' and data '["time"]'_ message when trying to pair the Konke Motion Sensor.

[SeLLeRoNe]

As stated in the docs (https://www.zigbee2mqtt.io/devices/2AJZ4KPBS.html), that little thing only works on channels 15, 20 or 25. I have the same thing and using channel 15 works.

It's a pain to pair, and the battery they sent originally are gone after a couple of weeks, which made pairing very hard.

[JHeijting]

Thanks for your reply. That's a shame... I think I gonna need a solution to move the coordinator around instead of having tot remover all my switchen from the walls to pair.

[stale[bot]]

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.