-
Notifications
You must be signed in to change notification settings - Fork 10
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
org.sputnikdev.bluetooth.manager.NotReadyException: Could not power adapter #10
Comments
The very first WARNING messages are normal, that’s when you have installed transport bundles first without installing the Bluetooth binding. So this should de ignored. The second part is more interesting:
Looks like the binding cannot power up your adapter. Can you please let me know more info about your set up. What adapter you have? Can you also please run the “bluetoothctl” utility and see if that utility can power up your adapter? Something like that:
Notice this:
Is it “no” for you? If so, try to power it up:
|
Yesterday everything seemed to work smothly after few seconds. Today my log gets flooded with the notReadyException
The error messages with “Could not power adapter” “Timeout reached” and “operation in progress” are alternating
Other Setup: |
Hi @Simsal, thank you for reporting this. Let’s start from the beginning. Before yesterday you reported “Could not power adapter” error, how did you resolve this? Did you use bluetooth “bluetoothctl” tool to power up your adapter as I suggested earlier? The errors “Timeout was reached” and “Operation already in progress” show that you have managed to power up the adapter and your are trying to connect to a device. What device is it? How far is it from the adapter? Just bear in mind that, if your device is too far from the adapter, the connection might be unstable. Just in general, if RSSI value is greater than -80 (meaning actually lesser, e.g. -81, -82 etc), then it is not recommended to connect to this device as the connection will be unstable. This is probably should be limited by the Bluetooth binding… it is probably a good idea. What do you guys think? We could add a global binding setting, like a “RSSI connection threshold” that would prevent connection attempts if the device is too far. Pease also note that the Binding can be too talkative for the initial phase of betta testing, this is done on purpose for troubleshooting. For example, the errors “Timeout was reached” and “Operation already in progress” will be probably hidden in future. |
This is using bluez 5.48 on raspberry pi zero wireless… |
Thanks for your report @sozkara, could you also please let me know what OS you are using and what version of OH? I’ll try to install that thing on raspberry pi zero and see how it goes. Although I’m not sure if it is a good idea to use PI Zero as it is really low spec board… It also might be due to the new version of Bluez, from what I can see in the release notes, they have implemented another bunch of “improvements and bugfixes” 😄. My current version of Bluez is 5.47, that’s what I use for testing as it must be more stable and included by default in major linux distributions. |
I’ve tried to install the new Bluez version - v5.48. A lot of things broken. I also had “Could not power adapter” as well. But the worst thing is - not all GATT services now getting resolved, for example battery service (https://www.bluetooth.com/specifications/gatt/viewer?attributeXmlFile=org.bluetooth.service.battery_service.xml) does not get resolved any more. Who know what else wrong… I do not recommend to upgrade to 5.48 as obviously there are some changes that TinyB library does not support yet. I’ll create some bug reports for both Bluez and TinyB projects, will see how it goes. So if you are on Bluez 5.48, please downgrade it to 5.47 using this instructions |
|
@Simsal:
I tried installing your binding, getting following errors:
The text was updated successfully, but these errors were encountered: