Yup, main processor involved is the 16MHz arduino one. So current thinking is that this is just a raw processing power bottleneck, correct? Sadly I need all those beautiful Arduino mega pins, so I’m stuck with it at the moment. It’s plenty powerful to run my scripts, but sadly not powerful enough for fast read/writes from Blynk, I suppose.
Good to know now before I put the effort into all the workarounds. Main workaround is probably just going to make sure I am staggering my writes so they don’t pile up. I also have at least one process that can freak out with long pauses, so possibly temporarily shut that one down while a read/write is happening. Not ideal, but can definitely make it work.
I’ve thought about doing something crazy and having the arduino handle all the IO and a pi zerow or something handle the UI and communication over serial/WIFI. That’re similar(ish) to my current strategy, which is also why I have all that “extra” in the main loop. The arduino is effectively running the automation scripts, and I have Blynk to tell it what mode to be in and monitor the various sensors of interest.
Also, before someone says it, the automation scripting is far, far more complicated than eventor widgets can handle.