April-23rd-2021, 08:52 AM
Well I see the log file you sent
msg : string[1575]
string[1575]
/__bledev/6901420e6d8c err:Error: Missing Peripheral Device
=>Error: Missing Peripheral Device
at Peripheral.a (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/dist/generic-ble.js:216:31)
at Object.onceWrapper (events.js:420:28)
at Peripheral.emit (events.js:326:22)
at PeripheralRemovableNoble.Noble.onDisconnect (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/node_modules/@abandonware/noble/lib/noble.js:245:16)
at BluezBindings.emit (events.js:314:20)
at ProxyInterface.<anonymous> (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/dist/noble/lib/bluez/noble/lib/bluez/bindings.js:623:18)
at ProxyInterface.emit (events.js:314:20)
at EventEmitter.$listeners.<computed> (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/node_modules/dbus-next/lib/client/proxy-interface.js:108:17)
at EventEmitter.emit (events.js:326:22)
at handleMessage (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/node_modules/dbus-next/lib/bus.js:11...
In this log file you see that the public node "node-red-contrib-generic-ble" reports an error. This is not a root cause of netPI but a root cause and malfunction of this node.
Hilscher is not aware of any guarantee of 3rd party software like Node-RED and all the public nodes that are included in our Node-RED container example build. So I am sorry to say that I cannot help here.
The maintainer of the "node-red-contrib-generic-ble" is this one here https://flows.nodered.org/node/node-red-...eneric-ble. He has the responsobility. But even so ... all nodes of Node-RED are open source and public. They can be used for free as they come ... so there is no guarantee of 100 % errorr free function at any time.
msg : string[1575]
string[1575]
/__bledev/6901420e6d8c err:Error: Missing Peripheral Device
=>Error: Missing Peripheral Device
at Peripheral.a (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/dist/generic-ble.js:216:31)
at Object.onceWrapper (events.js:420:28)
at Peripheral.emit (events.js:326:22)
at PeripheralRemovableNoble.Noble.onDisconnect (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/node_modules/@abandonware/noble/lib/noble.js:245:16)
at BluezBindings.emit (events.js:314:20)
at ProxyInterface.<anonymous> (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/dist/noble/lib/bluez/noble/lib/bluez/bindings.js:623:18)
at ProxyInterface.emit (events.js:314:20)
at EventEmitter.$listeners.<computed> (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/node_modules/dbus-next/lib/client/proxy-interface.js:108:17)
at EventEmitter.emit (events.js:326:22)
at handleMessage (/usr/lib/node_modules_tmp/node-red-contrib-generic-ble/node_modules/dbus-next/lib/bus.js:11...
In this log file you see that the public node "node-red-contrib-generic-ble" reports an error. This is not a root cause of netPI but a root cause and malfunction of this node.
Hilscher is not aware of any guarantee of 3rd party software like Node-RED and all the public nodes that are included in our Node-RED container example build. So I am sorry to say that I cannot help here.
The maintainer of the "node-red-contrib-generic-ble" is this one here https://flows.nodered.org/node/node-red-...eneric-ble. He has the responsobility. But even so ... all nodes of Node-RED are open source and public. They can be used for free as they come ... so there is no guarantee of 100 % errorr free function at any time.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)