- Posts: 93
- Thank you received: 13
It's getting the correct time, but looks like it's not applying the TZ string - it's reporting as UTC and not CET.
Stackerlee wrote: Strange. I get this: (correct local time is 16:55 CET)
Current time source NTP
Current time Wednesday, 13-Feb-2019 15:55:57 UTC
??? My code should work with both V1 (assuming I can get Stackerlee working) and V2 clocks, so the current WiFi code for V1 clocks can simply go away.
Ian wrote: In the V1 repository, there is a branch with WiFi Manager as the way of setting the initial login up. I guess that thing will be the next to be included.
I just updated the package to v355mjs.A. Any of the previous links should point to it.
Ian wrote: However, I'm starting on the V2 code on a new branch. I'm using version v355mjs.9. Is that the right one?
I've done this and it still SOMETIMES reports UTC (wrong), sometimes CET (correct) after power cycle. So it's inconsistent.
MikeS wrote: Try resetting the WiFi config (Utility/Clear WiFi config and restart module), and then set things up again. I increased the size of the storage for settings over what Ian originally had, and it might be good to start fresh. You'll have to go back and configure with WiFi module from scratch (connect to SSID NixieTimeModule, go to http://192.168.4.1, etc).
OK, I changed it so we set the TZ string each time we get time. Try it now (now at .B, any previous link in this thread will get the latest version).
Stackerlee wrote: I've done this and it still SOMETIMES reports UTC (wrong), sometimes CET (correct) after power cycle. So it's inconsistent.
Where can the aforementioned v355mja.A be found?