Closed wranglatang closed 3 years ago
Has anyone seen the below issue before? It throws and then restarts the system
Wed, 16 Jan 2019 10:31:32 GMT zigbee-shepherd Device: 0x001e5e09020d60d6 leave the network. zigbee2mqtt:debug 2019-1-16 10:31:32 Received zigbee message of type 'devLeaving' with data '"0x001e5e09020d60d6"' zigbee2mqtt:warn 2019-1-16 10:31:32 Message without device! Wed, 16 Jan 2019 10:31:32 GMT zigbee-shepherd:msgHdlr IND <-- ZDO:leaveInd Wed, 16 Jan 2019 10:32:37 GMT zigbee-shepherd:msgHdlr IND <-- ZDO:tcDeviceInd Wed, 16 Jan 2019 10:32:38 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] Wed, 16 Jan 2019 10:32:38 GMT zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 Wed, 16 Jan 2019 10:32:38 GMT zigbee-shepherd spinlock: false [] Wed, 16 Jan 2019 10:32:38 GMT zigbee-shepherd:request REQ --> ZDO:nodeDescReq Wed, 16 Jan 2019 10:32:38 GMT zigbee-shepherd:msgHdlr IND <-- ZDO:endDeviceAnnceInd Wed, 16 Jan 2019 10:32:38 GMT zigbee-shepherd:msgHdlr IND <-- ZDO:nodeDescRsp Wed, 16 Jan 2019 10:32:38 GMT zigbee-shepherd:request REQ --> ZDO:activeEpReq Wed, 16 Jan 2019 10:32:38 GMT zigbee-shepherd:msgHdlr IND <-- ZDO:activeEpRsp Wed, 16 Jan 2019 10:32:38 GMT zigbee-shepherd:request REQ --> ZDO:simpleDescReq Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:msgHdlr IND <-- ZDO:simpleDescRsp Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:request REQ --> AF:dataRequest, transId: 1 Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: dataConfirm, msg: [object Object] Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:msgHdlr IND <-- AF:dataConfirm, transId: 1 Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:msgHdlr IND <-- AF:incomingMsg, transId: 0 Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: zclIncomingMsg, msg: [object Object] Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd Identified Device: { manufacturer: Computime, product: SAL6EM1 } Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:request REQ --> AF:dataRequest, transId: 2 Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:request RSP <-- AF:dataRequest, status: 0 Wed, 16 Jan 2019 10:32:39 GMT zigbee-shepherd:af dispatchIncomingMsg(): type: incomingMsg, msg: [object Object] /zigbee2mqtt-1.0.1/node_modules/zcl-packet/lib/functional.js:27 throw new Error('Unrecognized cluster'); ^ Error: Unrecognized cluster at new FuncPayload (/zigbee2mqtt-1.0.1/node_modules/zcl-packet/lib/functional.js:27:15) at /zigbee2mqtt-1.0.1/node_modules/zcl-packet/lib/zcl.js:33:22 at Dissolve.<anonymous> (/zigbee2mqtt-1.0.1/node_modules/zcl-packet/lib/zcl.js:121:9) at Object.onceWrapper (events.js:315:30) at emitOne (events.js:116:13) at Dissolve.emit (events.js:211:7) at Dissolve.<anonymous> (/zigbee2mqtt-1.0.1/node_modules/dissolve-chunks/index.js:73:29) at emitNone (events.js:106:13) at Dissolve.emit (events.js:208:7) at emitReadable_ (/zigbee2mqtt-1.0.1/node_modules/dissolve/node_modules/readable-stream/lib/_stream_readable.js:456:10) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! zigbee2mqtt@1.0.1 start: `node index.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the zigbee2mqtt@1.0.1 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2019-01-16T10_32_39_531Z-debug.log 2019-01-16T10:32:40: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT] 2019-01-16T10:32:40: PM2 log: App [npm:0] starting in -fork mode- 2019-01-16T10:32:40: PM2 log: App [npm:0] online > zigbee2mqtt@1.0.1 start /zigbee2mqtt-1.0.1 > node index.js
Has anyone seen the below issue before? It throws and then restarts the system