ESP8266 main loop not executed with 80 MHz

[Gunner]

@Janmuel

void loop() {
fadeLedWidget(); //timer.run();
}

Running this in the void loop() may trigger a form of governor in Blynk that prevents overt server spamming… as you are trying to process that function thousands of times a second… or even if doing it the strange way you are, it may cause other issue?? hard to say as I do NOT run code that way.

The proper way is to use BlynkTimer and timed functions with reasonable intervals for needed rates.

C++ Blynk (Legacy) - Code Examples for Basic Tasks

#12 - Timers simplified… perhaps… Some have a difficult time understanding timers… and since this is a fundamental building block of Blynk… I buried this reference in the middle of this entire topic Well anyhow… This is a “real world” timer example where i am using two timers to alternately turn ON and OFF an LED… yes, there are many ways to do this, but this example is all about timers. The first timer will run it’s assigned function 500ms (1/2 second) after boo…

As for will Blynk run fast… yes, yes it can… see here…

C++ Blynk (Legacy) - Code Examples for Basic Tasks

#5 Matrix of Randomly Flashing & Coloured Virtual RGB LEDs I posted this last year…but am tossing it in here to keep my group of sketches up to date. Sorry to those not on Local Server… it is not cheap on the energy, however nothing in it is non-recyclable… 72 LED widgets @ 200 energy means you need 14,400 units of energy to load this. This code is compiled on a Wemos D1 mini with OTA programming functionality built in… but it basically should work on most any ESP8266. http://docs.blynk.cc/…

@Janmuel

Is the ping of the server connection also having an impact?

With Cloud it WILL depend on internet latency, but with Local Server then generally only your own network latency matters.