Got two devices set up on Rapsbian 18.04.
After a certain period of time, the following error occurs:
May 25 21:11:12 elysium somactrl[25680]: noble: unknown peripheral null connected!
May 25 21:11:55 elysium somactrl[25680]: 2019-05-25T21:11:55.361Z soma:ca065a773594 disconnected
May 25 21:11:55 elysium somactrl[25680]: 2019-05-25T21:11:55.362Z soma:ca065a773594 connected for 184.284 seconds
May 25 21:11:55 elysium somactrl[25680]: 2019-05-25T21:11:55.471Z soma:ca065a773594 Error: Command Disallowed (0xc)
May 25 21:11:55 elysium somactrl[25680]: at NobleBindings.onLeConnComplete (/usr/local/lib/node_modules/soma-ctrl/node_modules/noble/lib/hci-socket/bindings.js:220:13)
May 25 21:11:55 elysium somactrl[25680]: at emitOne (events.js:116:13)
May 25 21:11:55 elysium somactrl[25680]: at Hci.emit (events.js:211:7)
May 25 21:11:55 elysium somactrl[25680]: at Hci.processCmdStatusEvent (/usr/local/lib/node_modules/soma-ctrl/node_modules/noble/lib/hci-socket/hci.js:674:12)
May 25 21:11:55 elysium somactrl[25680]: at Hci.onSocketData (/usr/local/lib/node_modules/soma-ctrl/node_modules/noble/lib/hci-socket/hci.js:469:12)
May 25 21:11:55 elysium somactrl[25680]: at emitOne (events.js:116:13)
May 25 21:11:55 elysium somactrl[25680]: at BluetoothHciSocket.emit (events.js:211:7)
May 25 21:11:55 elysium somactrl[25680]: 2019-05-25T21:11:55.472Z soma:ca065a773594 connected!
May 25 21:11:55 elysium somactrl[25680]: noble warning: unknown peripheral ca065a773594
May 25 21:12:08 elysium somactrl[25680]: 2019-05-25T21:12:08.205Z soma:eebe28d042aa disconnected
and earlier this happened to the other device:
ay 25 19:49:19 elysium somactrl[24059]: 2019-05-25T19:49:19.420Z soma:eebe28d042aa disconnected
May 25 19:49:19 elysium somactrl[24059]: 2019-05-25T19:49:19.420Z soma:eebe28d042aa connected for 182.086 seconds
May 25 19:49:19 elysium somactrl[24059]: 2019-05-25T19:49:19.533Z soma:eebe28d042aa Error: Command Disallowed (0xc)
May 25 19:49:19 elysium somactrl[24059]: at NobleBindings.onLeConnComplete (/usr/local/lib/node_modules/soma-ctrl/node_modules/noble/lib/hci-socket/bindings.js:220:13)
May 25 19:49:19 elysium somactrl[24059]: at emitOne (events.js:116:13)
May 25 19:49:19 elysium somactrl[24059]: at Hci.emit (events.js:211:7)
May 25 19:49:19 elysium somactrl[24059]: at Hci.processCmdStatusEvent (/usr/local/lib/node_modules/soma-ctrl/node_modules/noble/lib/hci-socket/hci.js:674:12)
May 25 19:49:19 elysium somactrl[24059]: at Hci.onSocketData (/usr/local/lib/node_modules/soma-ctrl/node_modules/noble/lib/hci-socket/hci.js:469:12)
May 25 19:49:19 elysium somactrl[24059]: at emitOne (events.js:116:13)
May 25 19:49:19 elysium somactrl[24059]: at BluetoothHciSocket.emit (events.js:211:7)
May 25 19:49:19 elysium somactrl[24059]: 2019-05-25T19:49:19.534Z soma:eebe28d042aa connected!
May 25 19:49:19 elysium somactrl[24059]: noble warning: unknown peripheral eebe28d042aa
May 25 19:49:22 elysium somactrl[24059]: 2019-05-25T19:49:22.996Z soma:ca065a773594 requesting move to 100
May 25 19:49:23 elysium somactrl[24059]: 2019-05-25T19:49:23.015Z soma:eebe28d042aa requesting move to 100
After that, the particular affected device becomes completely unresponsive and stops reacting to MQTT or HTTP endpoint requests and the somactrl needs to be restarted.
I am not a nodejs wizz, but this seems like a case of a simple exception handling?
Got two devices set up on Rapsbian 18.04.
After a certain period of time, the following error occurs:
and earlier this happened to the other device:
After that, the particular affected device becomes completely unresponsive and stops reacting to MQTT or HTTP endpoint requests and the somactrl needs to be restarted.
I am not a nodejs wizz, but this seems like a case of a simple exception handling?