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
LEGO Boost firmware update 2.0.00.0017 breaks extension functionality #2215
Comments
@apple502j Thank you for alerting us to this tweet! Do you have a LEGO Boost with the latest firmware? |
Nope sorry @evhan55 |
@apple502j Okay, thank you for letting us know! |
I have tested the latest LEGO Boost Firmware
to:
It looks like the Boost connect behavior has changed as well and is not incompatible with the Scratch 3 / Scratch Link connection flow as currently designed for Boost, and other miscellaneous sensor values seem to give errors in the console. It might be best to open a new issue to track all of these changes together (or as separate issues?)... |
@apple502j Thank you! It seems you are correct about this being a critical bug in the Scratch 3 LEGO Boost extension! Thanks for bringing this issue to our attention. |
Some issues I noticed so far in preliminary testing:
|
@cwillisf @ericrosenbaum To update to the latest Boost firmware:
|
Thanks for reporting this @apple502j and for doing some great initial investigation @evhan55!
I'm pretty sure what's happening is that Scratch discovers I see two different strategies to solve this: Implement scratchfoundation/scratch-link#120: Since only the functioning Exclude the faulty UUID:
|
https://twitter.com/ooba/status/1142967014761254912
According to this tweet, a recent firmware update changed Boost port IDs:
A 0, B 1, C 2, D 3
Therefore old IDs (defined at https://github.com/LLK/scratch-vm/blob/develop/src/extensions/scratch3_boost/index.js#L96 ) won't work. However, if the firmware is not updated, old IDs must be used - so it's hard to define it as constant.
The text was updated successfully, but these errors were encountered: