-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Feature] Add "address" and "light" to class "remote" #404
Comments
What is the use case for this? |
Edit:
|
👍 Another case was even used in our own video. But since disconnect() was not available I cheated and just turned the whole hub off instead 😄 |
This adds a light attribute for controlling the status light on the Powered Up Handset. Issue: pybricks/support#404
This adds a light attribute for controlling the status light on the Powered Up Handset. Issue: pybricks/support#404
Setting the light color seems relatively slow. Would it be faster if we didn't use RGB mode, or is two extra bytes negligible given the overhead data? EDIT: This seems to be primarily the case when used in a loop. So we can just document it and recommend not to change it too fast. Single changes look fast enough. |
As a minor note, |
The remote seems to remember the light used last. Maybe we can add call |
This adds a close method to disconnect the handset. The name close() is chosen because it is a common pattern in Python and will allow the object to be used in generic cases that want a closable object. Issue: pybricks/support#404
This is available at https://beta.pybricks.com now. |
Hi dlech yes indeed, thanks a lot! |
It is possible to give each remote a unique and meaningful name. We hoped this would be nicer than using the Blueooth address. And if you can be sure that only one remote is advertising at a time, then you don't need the name at all. |
Hi all,
the features "address" and "light" are discussed/planned , but yet not implemented in class "remote"
Use of "address"
Use of "light"
Perhaps discuss a "disconnect" for the remote?
The text was updated successfully, but these errors were encountered: