Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BLE] could not start sync as Could not start scanning, state is unknown (not poweredOn) at Noble.scan #973

Open
jamesdrake101 opened this issue Dec 3, 2024 · 3 comments

Comments

@jamesdrake101
Copy link

jamesdrake101 commented Dec 3, 2024

What issue do you have? Please be as thorough and explicit as possible.

Bluetooth LE scanning fails with this error message: [Govee] [BLE] could not start sync as Could not start scanning, state is unknown (not poweredOn) at Noble.scan (/var/lib/homebridge/node_modules/homebridge-govee/node_modules/@abandonware/noble/lib/noble.js:124:21).

Details of your setup.

  • Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS? Homebridge web UI, not sure what "-X" is.

  • Which version of Homebridge/HOOBS do you have? v1.8.5

  • Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known. Linux 6.6.62+rpt-rpi-2712 arm64, Node.js v20.18.0

  • Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version? 10.12.1

  • Which Govee devices do you have that are causing issues? Please include product models if applicable. All of them. Bluetooth scanning does not work.

Please paste any relevant logs below.

[03/12/2024, 10:29:46] [Govee] ✓ Setup complete. This plugin has been made with ♥ by bwp91, please consider a ☆ on GitHub if you are finding it useful!
[03/12/2024, 10:34:46] [Govee] [BLE] could not start sync as Could not start scanning, state is unknown (not poweredOn) at Noble.scan (/var/lib/homebridge/node_modules/homebridge-govee/node_modules/@abandonware/noble/lib/noble.js:124:21).

Worked just fine only days ago. Not sure what happened.

Thanks!

@jamesdrake101
Copy link
Author

Possibly related: abandonware/noble#345

@jamesdrake101
Copy link
Author

jamesdrake101 commented Dec 3, 2024

Downgraded Raspbian kernel to d5a7dbe77b71974b9abb133a4b5210a8070c9284 (aka 6.6.51-v8-16k+) and everything is back to normal.

sudo rpi-update d5a7dbe77b71974b9abb133a4b5210a8070c9284

Clearly a recent kernel update bricked Bluetooth.

@Busyrev
Copy link

Busyrev commented Dec 9, 2024

Just for information, there is a a fix from bluetooth-hci-socket side. See stoprocent/noble#4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants