- Sun Aug 16, 2015 11:49 am
#26183
The NTPClient.begin() is using a integer for TimeZoneOffset, so your define with 5.5 won't work, except if you change the code to use a "float" instead of a "int".
Moderator: igrr
- Thu Aug 27, 2015 3:58 am
#27144
still not updating i can ping it and get a response and if i run ntp client it updates
but the clock example only gets the time on boot.
i have the led now and the time does not drift overnight but no updates.
but the clock example only gets the time on boot.
i have the led now and the time does not drift overnight but no updates.
Code: Select all
...WiFi connected
IP address:
192.168.1.110
Received NTP Response
Unix time = 1440630820
No NTP Response :-(
No NTP Response :-(
No NTP Response :-(
No NTP Response :-(
No NTP Response :-(
No NTP Response :-(
No NTP Response :-(
No NTP Response :-(
No NTP Response :-(
- Thu Aug 27, 2015 6:16 am
#27156
Just one minor issue with the code.
Anyone wanting to use it outside of the PST time zone will, of course, tweak the value from -8.
However, for Europeans, we will also want to change the daylight saving rule, since ours is slightly different from the U.S.A.
It's relatively simple to do, though.
Regards
Steve
Anyone wanting to use it outside of the PST time zone will, of course, tweak the value from -8.
However, for Europeans, we will also want to change the daylight saving rule, since ours is slightly different from the U.S.A.
It's relatively simple to do, though.
Regards
Steve
