Chat freely about anything...

User avatar
By QuickFix
LBussy wrote:Sorry - can't figure out how to edit my post.

Editing a post is only practical if you do it right after you post something; I would have missed any edit you would have made, once I have read your initial reply.
You can edit your own posts by pressing the cog in the upper right of your message, choosing "Edit post". :idea:

LBussy wrote:"which board?" it's a Wemos D1 Mini R2.

A proven development board is always more stable than something untested you've designed yourself, so a Wemos should electrically (normally) be no problem.
(The ESP8266 is actually a chip that is normally mounted on a module, with a name like ESP-01 or ESP-12, and for those there are development boards, like (the one you're using) the Wemos and NodeMCU.)

LBussy wrote:Actually, right now it's plugged into my laptop for easier debugging since this started. I can always switch to a powered USB hub.

Unless you have an old or some sort of "low power" laptop not able to deliver the required 500mA needed by your Wemos, there's not much to worry about I guess.
If you can, use a powered USB hub to be certain or power the Wemos from a solid 5V supply on the 5V-pin of the Wemos.

I'm not saying that the hardware is the problem, but when I hear "Intermittent problem" without any real constant factor, you have to make sure all variables (like the power supply, but also the AP, etc.) are removed from the equation.
User avatar
By LBussy
#83487 Yep, understood. Debugging is not always completely science but it definitely needs to start that way.

Like I said, it seemed weird that “random” crashing was happening just in network related libs. Then again, if I’m honest I think statistically it makes sense since there’s more lib than program right now. :)