Firmware update resulted in revision: "unknown"

[angelo]

Hello

I finally found some time to play with the pinocc.io again and hq showed that an update was ready to go. 1 Scout updated no issues. The lead scout (with WiFi) would not update though.
Following instructions outlined here: http://support.pinocc.io/hc/en-us/articles/202958774-Bootstrapping-Your-Scout
I updated through the Arduino IDE.
The unit works nicely after that BUT scout.report results in:
{"type":"scout","lead":true,"version":1,"hardware":1,"family":1000,"serial":3000538,"sketch":"Custom","build":-1,"revision":"unknown","at":47680}

Where the Sketch is Custom and build and revision are not known.

Questions:
1) Are future updates recognized and will the automatic HQ update work?
2) How can I get the unit back to "factory reset"?

Thanks for the help

Angelo

[alexglow]

Hey Angelo, sorry for the trouble!

1) Are future updates recognized and will the automatic HQ update work?

Actually, no! This is intentional, because people with custom builds typically aren't interested in overwriting them with the default Bootstrap. When you build Bootstrap from the Arduino IDE, your build and version are set to the values you're seeing. HQ sees that you have a custom build, and won't show you the red dot or prompt you to update it.

2) How can I get the unit back to "factory reset"?

You can "force" the Scout to go back to a nice clean state using the debug page, here: http://hq.pinocc.io/debug and clicking "Upload" while your Scout is plugged in and switched on. We only recommend using that if, as in your case, you've had some trouble and need a clean slate.

If you have any trouble from here on, just let us know.

[jingman]

I updated @alexglow's response with a different answer to the first question.

[alexglow]

Thanks, @jingman! I didn't even know about that feature.