You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
running fine using WiFi transport, but connecting to internet via SIM800L using TinyGSM library it fail retrieving the time.
void setupDateTime() {
DateTime.setTimeZone(TZ_Europe_Rome);
DateTime.setServer("it.pool.ntp.org");
DateTime.begin(15000);
if (!DateTime.isTimeValid()) {
Serial.println("Failed to get time from server.");
} else {
Serial.printf("Date Now is %s\r\n", DateTime.toISOString().c_str());
Serial.printf("Timestamp is %ld\r\n", DateTime.now());
}
}
And this is the log of my code :
Initializing modem
[7247] ### TinyGSM Version: 0.10.9
[7247] ### TinyGSM Compiled Module: TinyGsmClientSIM800
[7559] ### Modem: SIMCOM SIM800L
Modem Info: SIM800 R14.18
Waiting for network... success
Network connected
Connecting to APN ... TM
[29020] ### Network time zone updated.
[29024] ### Network time and time zone updated.
[29025] ### Daylight savings time state updated.
GPRS connected
IP: 10.193.141.85
IMEI: 8667820xxxxxxx
Operator: vodafone
Signal quality: 20
GPRS ready ✔
setTimeZone to CET-1CEST,M3.5.0,M10.5.0/3
setServer to it.pool.ntp.org,time.apple.com,time.windows.com
forceUpdate,timeZone:CET-1CEST,M3.5.0,M10.5.0/3, server:it.pool.ntp.org, timeOut:15000
Failed to get time from server.
Connecting to MQTT broker m23.cloudmqtt.com ...
MQTT connected ✔
Server disconnected
GPRS disconnected ✔
Poweroff modem ✔
Stop run
The text was updated successfully, but these errors were encountered:
I have a problem with WiFi also, works in the house, but in Dual Axis Solar Tracker 300' away, doesn't pickup WiFi. Is there another way? I'm using the library to update RTC (DS3232RTC) if differs by some setting (10 minutes).
Hi,
running fine using WiFi transport, but connecting to internet via SIM800L using TinyGSM library it fail retrieving the time.
And this is the log of my code :
The text was updated successfully, but these errors were encountered: