search

clausbroch / node-red-contrib-noble-bluetooth

A Node-RED module based on noble for interaction with Bluetooth Low Energy (BLE) devices.
MIT License
8 stars 15 forks source link

poweredOn error #3

Open gaunh0 opened 4 years ago

gaunh0 commented 4 years ago

When scan, I alway have this error:

Error scanning for devices: Error: Could not start scanning, state is unknown (not poweredOn)

clausbroch commented 4 years ago

Are you able to scan for devices a bit later, or does the error prevent detecting any devices?

hbull1 commented 4 years ago

I've had the error intermittently on a Raspberry Pi 4. I've only been able to reconnect to a device by rebooting the Pi, or running these commands in the terminal sudo systemctl restart bluetooth.service; sudo systemctl restart nodered.service;

wldevries commented 3 years ago

Restarting has no effect for me unfortunately, I keep getting the message above. Scanning on the command line on my raspberry pi with bluetoothctl works fine though.

wldevries commented 3 years ago

It seems node needs more permissions to interact with the Bluetooth device (or whatever is in between). The following fixed it for me: https://github.com/kounch/homebridge-avea-bulb/issues/4#issuecomment-336742704

WhiteLionATX commented 3 years ago

It seems node needs more permissions to interact with the Bluetooth device (or whatever is in between). The following fixed it for me: kounch/homebridge-avea-bulb#4 (comment)

this did not fix it for me on a Raspberry Pi 4.

danielfinans commented 2 years ago

Same error here. sudo systemctl restart bluetooth.service; sudo systemctl restart nodered.service; did not work. bluetoothctl detects the controller from terminal.

danielfinans commented 2 years ago

Was missing the noble module (https://github.com/noble/noble/blob/master/README.md) Then had to give permission to run without sudo. Now status is [BLE scanner:Scan for GF] BLE state: poweredOn, although not connecting. Perhaps because in use.