It works as described!
The clock is found on I2C bus. (I have ESP8266 + DS3231 with V1 code).
Settings can be changed, at least after pressing "Set" once. Before that some of the settings are greyed out.
"Communicating with: NixieFirmwareV1, I2C v54" is shown.
There's one little issue though. At restart the time is shown in UTC (I'm CET) on clock as well as in status, even though correct (my) settings are set.
"Confirming" the settings without changing anything by pressing "Set" in Time Server settings resolves it. To my understanding this means the clock is set one hour back (in my case) if the power goes out and comes back.
Has this anything to do with the DST bug fix?
Else, everything seems fine! I like the little changes, "Current status" page makes more sense now (seconds instead of ms and so on).
Let's see what happens 2019-03-31 02:00 (DST start).
Having some entries "dimmed" so you can't set them (e.g. scroll back is off, you can't change steps) was part of Ian's code. I'll probably remove that and let you set things anyway. I had the same, had to do it twice, once to enable a feature, second time to set the particulars.
Not sure about the UTC thing - it's working for me. What POSIX string do you have set? I'll see if I can duplicate. Does it perhaps correct itself if you wait a minute or two for the next time the module updates the clock, or if you click the "full update now" link on the status page?
The DST bug fix was that the library would switch to DST at the wrong time, but that would only show up within a day of the time change.
The "dimmed" entries are not really a problem for me.
The UTC thing can be.
My settings are:
It doesn't seem to correct itself, at least not within an hour or so.
At restart it sets the time correct according to the DS3231 but as soon as NTP time is fetched it changed to UTC. Until the settings are are confirmed once more then it's correct CET. I think that's how it behaves with my settings.
The ezTime library is version 0.7.9
Hi Mike, my horror project at work looks like it might have gone over the edge, and I started on the process of merging the code, I guess it will take me a few days to get my head around it fully. Of course, I'm liking it a lot...
Just to coordinate efforts a bit:
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.
On my next generation code base (used in my ESP only clocks, not yet released), I have done a lot of work round using JSON configuration on SPIFFS. This doesn't work by default on all ESP-01s, but I have a patched driver for the flash chip alternatives.
However, I'm starting on the V2 code on a new branch. I'm using version v355mjs.9. Is that the right one?
I'll happily add you as a contributor to the repository if you want...
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
NTP server se.pool.ntp.org
NTP status Last poll valid
Time server URL
Uptime 0 days, 0 hours, 3 mins, 27 secs
after a restart of ESP from web gui or power cycle.
But now it doesn't seem to happen every time.