Timeline for What is the ideal way to check if time on ESP8266 via NTP is ready?
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 4, 2023 at 11:13 | answer | added | shumifan49 | timeline score: -1 | |
| Apr 4, 2023 at 10:15 | answer | added | shumifan49 | timeline score: 1 | |
| Feb 2, 2023 at 17:06 | vote | accept | Nick Bolton | ||
| S Dec 9, 2022 at 16:14 | vote | accept | Nick Bolton | ||
| Dec 9, 2022 at 16:14 | |||||
| Dec 7, 2022 at 14:00 | answer | added | 6v6gt | timeline score: 3 | |
| Dec 6, 2022 at 11:09 | history | edited | Nick Bolton | CC BY-SA 4.0 |
added 170 characters in body
|
| Dec 6, 2022 at 11:06 | vote | accept | Nick Bolton | ||
| S Dec 9, 2022 at 16:14 | |||||
| Dec 6, 2022 at 9:48 | history | edited | Nick Bolton | CC BY-SA 4.0 |
edited title
|
| Dec 5, 2022 at 22:05 | comment | added | DataFiddler | I guess, localtime even starts at 31-Dec-1969 afternoon in a western time zone. Thus comparing the local year with 70 is really a strange approach. Rather test the raw time_t value. | |
| Dec 5, 2022 at 21:42 | answer | added | Edgar Bonet | timeline score: 3 | |
| Dec 5, 2022 at 21:09 | comment | added | Nick Bolton |
Unfortunately, it doesn't seem to return -1. When the year is 70, the result from time is 18 (I guess that's how many seconds the device has been online). When the year is valid, it returns expected epoch, e.g. 1670274493.
|
|
| Dec 5, 2022 at 21:01 | comment | added | Edgar Bonet |
Doesn't time() return −1 if it cannot get the time? At least that is what it is supposed to do.
|
|
| Dec 5, 2022 at 20:52 | history | edited | Nick Bolton | CC BY-SA 4.0 |
added 114 characters in body
|
| Dec 5, 2022 at 20:38 | history | asked | Nick Bolton | CC BY-SA 4.0 |