I'm trying to downgrade our Spike Prime Hub from the Spike App v3's firmware to the Spike App v2's firmware. Has anyone been successful? Or does anyone have suggestions on how to flash the firmware to a version that's compatible with Spike App v2.0.8 or v2.0.9?
Context
I upgraded our hub to Spike 3. This is the default recommended behavior through the new v3 app as of December 1st, 2022, as follows.
DO NOT DO THESE STEPS IF YOU NEED YOUR v2 CODE TO WORK WITH YOUR SPIKE PRIME HUB
Navigate to Spike App v3 (link above) and notice that there is a new version of the app Select Prime Click Update Hub on the popup Follow the steps to update the firmware for the v3 Spike App
After doing so, I realized our existing v2 Spike Prime code would no longer be compatible. There's a different filename extension for the new files (.llsp3
vs .llsp
). Eventually, I want to switch to the newer app, but for now, I am trying to get our .llsp code working again.
Attempted resolution
- As suggested at this support page (screenshot below) and via built-in troubleshooting steps in the app, I went to https://spike.legoeducation.com/hubdowngrade to downgrade.
However that page just loads the new v3 of the app.(Now fixed.)
If I add a(Now fixed.)/
to the end of that URL, I get something different. There is a note "This might take several minutes", but nothing ever loads. (For those familiar with Chrome DevTools, there were lots of 403 Forbidden errors. To see the details download this HAR archive of the result and open it with Google's HAR Analyzer- Because I know v2 of the app is available at a similar URL (starting with
spikelegacy
instead ofspike
), I attempted using the tool at https://spikelegacy.legoeducation.com/hubdowngrade/.However, when I follow the steps, the connection pop-up says "No compatible devices found."(Now fixed.)
If anyone on LEGO's DevOps team reads this, it seems that:
- The
/hubdowngrade
endpoint of the new v3 site isn't properly configured to redirect to/hubdowngrade/
- The
/hubdowngrade/
endpoint successfully resolves to downloading some text/HTML. - However, something about the configuration of
/hubdowngrade/*
endpoints results in 403 Forbidden responses. This results in some ~60 failed requests.
Edit: It seems they have resolved the issue with the downgrade page.