This problem sadly never got resolved. We tried many different things. We used different pieces of SW, different libraries, different approaches (RMT, separate pinned task, etc). As far as we could tell, we couldn't make any progress except that some approaches flickered a bit more and some a bit le...

Hey people I have an issue where I can see, that the ESP does perform the DHCP negotiation perfectly fine, and afterwards sends a DHCP-Decline. Based on my investigation I'm pretty sure it happens because of the ARP-Checking the LWIP does afterwards. After it has successful negotiated an IP, it does...

Thanks for your input!

We tried various combination inclusive all turned on and off. Sadly no solution either.

So we tried to power the NeoPixels from a completely different power source. We observed a stable voltage of 4,5V or 5V (depending on what we configured). Also the ESP32 has enough power (at least the voltage is stable). We analyzed the signal directly on the GPIO-Pin and as well as after our "ampli...

Hy and thanks for your answer. Yes, the NeoPixel get 5V. Important to note is, that the pixels and the control of the pixels work flawlessly. We get way more than 60Hz and can do animations and whatnot. Everything is as it should be and as we wanted. But as soon as we start using the wifi, some of t...

Hello Everyone As described by the title i try to do some "animations" with NeoPixels and a ESP32. They work perfectly fine and do exactly what expected and programmed. I use the followint RMT-based library: https://github.com/marcmerlin/IoTuz/blob/master/ws2812.cpp Now, as soon as I use the WiFi th...