-
Notifications
You must be signed in to change notification settings - Fork 46
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
Error when using raspberry pi 4 #46
Comments
I haven't really tested it on Pi4 hardware. What does your |
I created a docker container for renogy-bt for |
That would be fantastic. I've put this project on the back burner for now, but that write-up could prove very useful once I'm able to pick it up again. Thanks! |
Also, my /etc/bluetooth/main.conf:
|
On a Pi5, experiencing the same error. |
I'm not sure if this is useful, but running Running Failed connections (90% of the time)
Working connection
|
Just an update, I rewrote the bluetooth management side of this for my own purposes to connect using Bleak. https://github.com/hbldh/bleak and it is now working great on Raspberry Pi 5. It also seems to provide a much simpler way of managing device connections and callbacks. |
@matthewcobb Feel free to raise a PR against the |
Experimental bleak branch is now available |
I've been using your repo on a very old raspberry pi model B v 2.0 running Linux raspberry pi 6.1.21+ with great success. I had to use a USB dongle for Bluetooth, but it worked without a hitch.
I recently upgraded to a raspberry pi model 4B running Linux raspberrypi 6.1.0-rpi6-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.58-1+rpt2, and I cant for the life of me get connected. The error message comes from gatt I believe, and isn't very helpful:
(.venv) pi@raspberrypi:~/renogy-bt $ python example.py INFO:root:Init RoverClient: BT-TH-774B0D88 => f4:60:77:4b:0d:88 INFO:root:Adapter status - Powered: True INFO:root:Starting discovery... INFO:root:Devices found: 16 INFO:root:Found matching device BT-TH-774B0D88 => [f4:60:77:4b:0d:88] ERROR:root:Connection failed: le-connection-abort-by-local
I've tried using both the pi 4's native Bluetooth hardware and the old functioning Bluetooth dongle with similar results. bluetooth, bluez, and gatt are all the most recent versions.
Also tried:
Any advice in terms of avenues I should pursue for further debugging?
The text was updated successfully, but these errors were encountered: