Hi @wizard - I spent an hour on a screen share with popcapps just now, and wanted to relay some of what I saw.
Since client mode has never worked for him (even back when his v3 was loading the patterns page just fine), he had the clever idea to just change CLIENT to AP in this:
curl -i -d "mode=AP&ssid=MYWIFINETWORK&passphrase=MYPASSPHRASE&discover=true" -X POST http://192.168.4.1/wifisave
What we were able to observe was that it would create the AP, allow the Windows computer “we” were on to connect, but would not assign an IP. No gateway was shown in ipconfig
; the interface self-assigned an IP. Contrast this with when he held the button for 3 seconds. In that mode, the Pixelblaze_XXXXXXXX SSID was connecting and assigning him an IP fine.
From that working Pixelblaze_XXXXXX SSID, /update was redirecting to /?wifi. I also helped him compose a curl form-data POST to /update with the @v3.16.pb32.stfu, but that also returns the HTML with embedded window.location redirect.
Hopefully this delete trick will work out. I think you said future firmware will allow POST to /update from WiFi setup mode, right?
And @popcapps - I know you were concerned about recovering a pattern you put some effort into. The delete of index suggested in the latest shouldn’t affect your patterns.