PixelBlaze V3 Works in AP Mode, Not Client Mode

Troubleshooting
1

I’m running into a befuddling problem, where I can set up the PixelBlaze on AP mode under a certain condition, but not in Client mode.

I can configure AP mode by pressing the onboard button for 5 seconds, and connecting to the SSID PixelBlaze145D0E. I’m then able to access the main configuration site at the following address: 192.168.4.1

In AP mode, everything works just fine. I did have some bad patterns loaded up, but managed to delete them from AP mode by restoring from a previous backup, and verified that they no longer appear in the list.

If I press the onboard button for 5 seconds, and configure and connect to a WiFi network, I get the following error in the browser console repeatedly when attempting to load the main setup page directly via the IP address 192.168.7.28, while the “Reconnecting” logo spins:

WebSocket connection to 'ws://192.168.7.28:81/' failed: (index):180

Which links to the following line in the function connectWebsocket(t) { method:

(websocket = new WebSocket("ws://" + t + ":81/")).binaryType = "arraybuffer",

While I can’t load the main configuration page, I am able to change patterns by pressing the onboard button. I can also successfully navigate to the following URL, which brings up a WiFi settings page. http://192.168.7.28/pbWiFiSetup.html?wifi.

If I try to save an AP configuration from the URL above (versus holding the button for 5 seconds, and connecting to the PixelBlaze145D0E SSID), the page will say that the settings saved successfully, but the AP network doesn’t show up. The board is running v5.31.

I’d really appreciate some guidance on how to troubleshoot this issue. It seems like an error state I’ve probably caused, because the board was able to connect to the same network and the main page would load successfully when the board was new out of the box.

2

It sounds like something is causing the websockets to drop. Sometimes a quick reboot of the PB clears it up. It could be WiFi or power related, or metal or wires near the antenna. What kind of distance and signal strength are you seeing?

3

I sorted it out – leaving this comment in case it helps someone else.

Seems like for some reason the websocket connection is sporadically being blocked by an Eero brand router.

I don’t have time to debug/troubleshoot exactly why. In the meantime, I set up a new router with a network just for the Pixelblazes to communicate on, and that seems to be doing the trick and working seamlessly.

Thanks for the speedy reply!

1 Like
4

Thanks for following up! Can you tell me the model, in case it comes up again?