Recently all my pixelblaze v3 firmware v3.67.pb32 will not finish connecting whether in AP or Client mode. They just cycle through the images below and it will never connect.
I have tried via a MacBook pro, iPhone, iPad and I have tried multiple browsers.
everything used to work flawlessly, now nothing.
Do these load when you put them in AP mode?
Wondering if it’s a router issue. Does the recovery page load status?
I have tried with multiple routers. I can get the the recovery page and recover but always the same result with the rotating cube of death.
Can I also assume you power cycled them?
Just today I had a 3.67 get stuck like that. It’s in marginal wifi territory. Power cycle fixed it.
When you say you get the same recovery page, Ben means the URL of http:///recovery. Does that load? Are you saying that somehow fixes it? How long does it stay “fixed” for (and are you saying it will always revert to the stuck state)?
You kind of implied multiple PBs on 3.67… how many? Do all of them do this? Are they all using the same image with the same patterns? Because in the past certain deep runtime bugs can actually get PBs into a tough state but ai haven’t seen the in a long time.
Basically moar details please.
Sorry for any confusion. Below is the flow of events.
I power on the pixelblaze.
I hold down the button to go back to setup mode
I connect to the pixelblaze wifi via my Mac/iPhone/iPad
Sometimes after a long long wait I will get the pop-up setup window. Sometimes not.
I can sometimes connect to my network and the pixelblaze confirms success and drops its wifi
I also try to access the pixelblaze “web interface” @ 192.168.4.1. This is when I get the spinning cube of death. Pixelblaze will not progress past this point. Refreshing browser, clearing cache, private tab…Nothing Just Loading….Connecting….Reconnecting…..Reading Config… and this repeats.
I can get both the 192.168.4.1/update and /reset but the same spinning cube situation.
It is strange everything worked fine 1 month ago.
Thanks for your help.
To help rule out software changes, you can install an older version. If that works then something in the update changed, and I have a bug to hunt!
Otherwise the usual suspects. Power, metal and wires, routers, etc.
That you can get through the WiFi setup process leads me to think it’s not a corrupted web app file. And also points to possibly something at the network level, since setup is in AP mode and works independently of your network gear, just the PB and the device you use to configure it.
I’d power cycle the router for sure. I’ve had that inexplicably happen to me, where the router shadow banned the PB from fully working.
If WiFi setup page is slow or iffy, that can indicate power or WiFi signal issues with the install, like an aging power supply or metal/wires messing with the radio.
The recovery page has some info on the top left. Does that populate for you? That comes from the websocket. Only difference is the recovery page is much smaller, like 3k of data vs 300k.
Spinning cube stuck on connecting is usually because it can’t make a websocket connection. But in some cases the whole web app file is corrupt and won’t ever load (not even for WiFi setup mode).
