I’ve been getting this issue sporadically with pixelblazes since I first started buying them about a year ago for personal projects. It’s what’s really preventing me from wanting to use them on projects for clients. I thought the issue might be power related but even if I run the Pixelblaze power on a separate power run from the same power supply rather than using the power out on the pblaze I still get this issue intermittently even on pixelblazes I purchased just a couple months ago. Resetting the Pixelblaze resolves the issue but it’s kind of a deal breaker having to power cycle a Pixelblaze randomly in order to change the patterns. Any idea what is causing this issue? This happens whether the Pixelblaze is in ap mode or WiFi mode. Doesn’t matter if the leds are drawing a lot of power or very little. I can get to recovery.html screen but not the ui or config screens.
Thanks for doing the basic troubleshooting and searching the forums!
You’re right that in recent firmware, the spinning cube is almost always low voltage, noisy voltage, or low WiFi signal strength (long distances or obstructions). Are these Pixelblazes possibly in an ABS or metal enclosure? I have one in ABS that works well at <50 ft from my access point, but spins at longer distances.
Do you have a voltmeter or oscilloscope, and could you measure the voltage at the point it enters the controller?