-
Notifications
You must be signed in to change notification settings - Fork 124
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
Raspberry Pi: demo.py sometimes work, sometimes not #69
Comments
The proper way to troubleshoot this is to enable DEBUG level logging in demo.py (instead of INFO). Then run it again and share the log. |
Hey, here is the log.
|
So it looks like there is indeed something that makes pylgbst to not receive any incoming messages from BLE after LEDRGB attach message. The library is helpless here, since it simply does not get any communication from underlying BLE stack. I would give a try to another connection library, for example pygatt. Again, I don't see anything that would cause such a pause on the library side (I can be wrong, though, since I did not write that part of library). |
I tried every other backend, but non of them work. Always with the following error (here for
I also used
So I run I checked it also on another raspberry pi, same issue there. I also tried your bleak-troubleshooting #70 branch with following log
Greetings Tonka |
Do you have |
|
|
installing dbus-python via |
Hi, i was struggling with rpi and my lego boost. thanks to this issue i got the demo.py running within docker on rpi3. maybe you can make use of it: https://gitlab.com/tigabeatz/rpi-docker-lego i needed
and
to run the demo.py i start it with gatt and the boosts mac, otherwise i do not get connections:
|
Hey @undera ,
I have troubles to get the
demo.py
example from your repo to work always. It worked multiple times (3-4 times), but most of the time the hub switches offWARNING:hub:Hub switches off
, before an action can be started and the program stuck on that state. The bot turns off after 10 seconds of not interaction which is the default as far as I can tell. I've tried it on my mac, but no bluetooth backend seems to support MacOS so not test possible. For me it looks like the program on the pi is so slow (maybe wait for an event) and reach timeout before.Hardware: raspberry pi 3 B, Lego Boost Robot
python: 3.7.3
virtual env: yes, with python3 -m venv
Bluetooth backend: bluepy 1.3.0
Firmware-Version:
2.0.00.0017
Here is the application stdout from
demo.py
. It extremely fast found the hub but it stuck on the lineINFO:hub:Attached peripheral: LEDRGB on port 0x32
for some time, so it seems that the program is waiting for something here.Maybe you have an idea how I can debug that problem.
Greetings
Tonka
The text was updated successfully, but these errors were encountered: