@timster,
FredEBear’s issues ended up being something related to the router’s settings and/or support for 2.4GHz. He switched to a different router and the problems went away (at least the problems in that thread). I’m not sure if it was a device incompatibility, or just a router setting that prevents access. I do know that some routers have settings that prevent one client from accessing another, or don’t put every WiFi network on the same IP subnet, which wouldn’t work with Pixelblaze since it is all local.
Since your issue is different – your setup was known to work and still works sometimes – I think this is worth moving to another thread. As I do, I want to mention another recent thread with similar symptoms that ended up being power supply related.
This isn’t really something I can optimize around much more than I already have. If your signal is too weak for the bandwidth of live previews, it will eventually kick the connection (rather than stall the entire system), and the app will reconnect. You can click the live preview to disable that, which can help.
@Scruffynerf ,
Yes, the ESP32 has been much more difficult. I recently saw that espressif is specifically hiring for a software networking engineer to work on their LwIP fork. So I’m hopeful that they realize they have some issues and are looking to address the underlying problems.
Right, perhaps just copy paste from the last several connectivity issues, and maybe there’s a way to get Discourse to start the Troubleshooting category topics with a template like used for bug reporting, read this FAQ, try these things first, collecting basic info, steps to reproduce, etc.