So… got the dev kits… puzzled my way through set up… tested out the dev kit… published the examples… great! so I thought lets move on the the next stage… got a pre-programmed blink (it had fracture on it) and used the publish tool to push the example game on to the blink (to override the game stored on there)
connected… lit up … publish successful.
I plugged the battery back in. and DEAD! the unit is KO:d … non responsive… will not even respond to the publish tool anymore…
Is there a reset / way to debug whether the unit has had a catastrophic failure or not?
We recently got a report of something similar happening with the hourly preview build. Switching back to the stable version (currently 1.8.13) and reprogramming the blink fixed it.
Pulling the battery from a blink and then pushing the button should reset it. If you have done that and are also on the most recent Arduino, then the blink might have gotten fried. If so, please an email to support@move38.com so we can get you back in business!
FWIW, I think I just fell down this exact rabbit hole with one of my blinks. Thankfully, it was one of my own games, that had a bug I didn’t catch before on it. … So, ultimately nothing lost, except for the actual blink itself. I was just trying to update the new version (Main Street) over the published version of the game. Obviously it doesn’t work that way. [[And here I was, thinking to myself, why would anyone but the game packs, over just one set of blanks?]]
I’ll add that I saw the blink flash either red, then white, or white then red, right as it happened, and the battery looked like it perspired a bit. But yeah, it’s now dead as well.
Please send a pic or short video to support@move38.com. While it is possible to accidentally short circuit a Blink if not careful with the publish tool, this sounds unique and we will take care of you.