-
-
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
Technic Hub can get stuck during shutdown #814
Technic Hub can get stuck during shutdown #814
Comments
shutdownloop.mp4 |
I have a hunch we are hitting something like this: #567, which prevents the program from ending, and thus preventing poweroff. |
See also the problem section in #802 |
I was able to reproduce this several times (but not always) under the following conditions:
Sometimes it works, sometimes it does not. You can tell that it happens when the remote is off but the hub keeps running without hitting the timeout. Turning off then will trigger this. |
I just had the same issue 10 minutes ago. Had to cut the power off to get rid of the blue flashlight. |
Was this in a program doing something with Bluetooth, like the remote or broadcasting/scanning? Edit, I see your edit now :) |
It happened only once to me. I do not remember exactly if it was during scanning or remote was already connected. Next time I will note it down, but I did a lot of experiments with remote trying to fix #813, and I couldn't reproduce it. |
Fixes pybricks/support#814 so the user can at least turn the hub off without removing the batteries.
Fixes pybricks/support#814 so the user can at least turn the hub off without removing the batteries.
Fixes pybricks/support#814 so the user can at least turn the hub off without removing the batteries.
Fixes pybricks/support#814 so the user can at least turn the hub off without removing the batteries.
The Technic Hub can get stuck during power off.
This appears to happen when trying to shut down the hub when a Bluetooth task within a program is busy.
Originally posted by @laurensvalk in #600 (comment)
The text was updated successfully, but these errors were encountered: