Closed Robiv8 closed 5 years ago
from NTP client lib I see that the possible 'errors' are:
typedef enum { timeSyncd, // Time successfully got from NTP server noResponse, // No response from server invalidAddress // Address not reachable } NTPSyncEvent_t;
In your case, the 'error' is timeSyncd and it fires twice (no error the 2nd time), that's why you have your clock up to date. this part of the code is from its examples and I might fix it sometime. for now there's no function loss.
cheers
Have this error? but the time is correct in the display