UPDATE: V3.18 addresses many of these issues
Read on for the old way of recovering from a corrupt web app
OK cool! I’ll post here in case others wander over with a similar issue, or folks are just curious.
In WiFi setup mode, the page will post to a an html form that sets things up. We can poke this manually with something like curl. If you have a Mac handy this should already be installed and you can run this in Terminal. I’m less well versed in Windows, but I know there’s a curl.exe for windows that should work similarly.
You’ll still need to be connected to the setup network, and you can close or move the capture popup out of the way. Open Terminal and run this, replacing out the MYWIFINETWORK and MYPASSPHRASE stuff for your wifi network info:
curl -i -d "mode=CLIENT&ssid=MYWIFINETWORK&passphrase=MYPASSPHRASE&discover=true" -X POST http://192.168.4.1/wifisave
That should connect, and if successful after a handful of seconds the configure network will disappear. You should now be back in client mode, but chances are whatever was preventing your wifi config screen from showing up is still happening but it should show up in the discovery service.
We can try pushing a firmware update to it, which should replace the main index page if that was causing problems.
Download the firmware for your variant:
Then visit the Pixelblaze’s IP address with /update added to the URL. There you can upload this file, and click update. It can take a few minutes to process.
Let me know if this works, or if you get stuck somewhere!