Observed that on poor wifi environment the nerdminer time is not correctly shown
Seem that timeClient.update() does not return a true, but is not checked and mTriggerUpdate is popullated with millis(). After that the NerdMiner took 5 hours to update the time.
With my pull request If the timeClient.update() function does not make a real update don't change mTriggerUpdate, this ensure that the time shown on screen at power up is updated as soon as gets connected and updated.
Observed that on poor wifi environment the nerdminer time is not correctly shown Seem that timeClient.update() does not return a true, but is not checked and mTriggerUpdate is popullated with millis(). After that the NerdMiner took 5 hours to update the time. With my pull request If the timeClient.update() function does not make a real update don't change mTriggerUpdate, this ensure that the time shown on screen at power up is updated as soon as gets connected and updated.