-
Notifications
You must be signed in to change notification settings - Fork 121
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
Can't call motors from movehub #34
Comments
Hi,
|
Hi I believe this could be the case. We updated MoveHub to latest firmware, and we are using pylgbst-1.0.1 (downloaded the zip file from releases page and installed with pip3). I'm no Python expert: how could we use your latest sources? thanks! |
Please upgrade the library, I just made new release. Like this: |
I upgraded according to your instructions. However now we don't get a connection with the MoveHub (it gets discovererd, see logs below). I tried bluepy and pygatt (on Raspberry Pi 3). Pygatt did work before.
|
This is because I changed the lookup name. In my Hub, it's "Move Hub" and I thought that's for everyone. hub=MoveHub(get_connection_auto(hub_mac='00:16:53:AA:D4:F5')) |
It works now, thanks! |
Hello
my son and I are exploring your beautiful library for Lego Boost. We have a Raspberry Pi and have already managed to make a connection with Lego Boost (Vernie), and used the Color/Distance sensor and changed de LED colors. Next step: motors, but here it fails.
When we try to access the motor_AB (or any other motor), we notice that the type of the variable is
NoneType
instead ofEncodedMotor
, hence we were unable to drive the motors. I suspect de motors are not found upon connecting. We got the following warnings when we connect:It would much appreciated if you could help us out!
Thanks!
Kris
PS: we are using the standard Vernie robot for our experiments. When using the Lego app, everything works as expected.
The text was updated successfully, but these errors were encountered: