nwts' latest firmware is up around the corner! I could not release the beta version ahead the DST change in the US, but it's now possible before the European DST change.
A few lines:
You need a ESP-01 programmer to flash the firmware. It's not possible with Over The Air (OTA) or other methods. Only with a programmer (USB or TTL based). More details on easy programmers in the firmware update manual
Flashing will erase your configuration! You need to enter nwts' license again and configure nwts to reconnect to your Wi-Fi network
You can contact me on bugs, but I prefer that you post in this discussion too, so others wont report the same bug over and over
If you're using a Mr Nixie's (Jürgen Grau) nwts, take notice that the default baud-rate is changed from 4800bps to 9600bps! If you're using a ASK receiver and/or your clocks are configured for 4800bps, don't forget to change this in nwts' webpage
Note: nwts beta has debug mode enabled! I've noticed with some clocks that the debug messages might cause the input buffers of some clocks to go haywire and the clock might change to an invalid date and not recover, until you remove the backup battery! Debug is only intended to be used when connected to the computer. If nwts is connected to a clock, please disable it.
Added time zone and DST support.
Custom latitude and longitude. Selected browsers can auto-fill
Select which NMEA messages to send and send only when clock RTC is in sync
Select date format in Webpage
Adjust delay or advance of time with drift correction
nwts user manual (v1.5 to v1.7)
Note: there's no v2.1 manual yet. The changes to version 2.1 are in the firmware upgrade document. After beta period is over, I'll make a consolidated manual with all features of nwts
On PV Electronics and Mr Nixie's clocks, if the GPS time is set (green LED is on), the clock will only check the correct time every 10 min.
So during DST change, there's a chance that your clock might take up to 10 min to update to the new time.
given that you are providing both the schematic for the hardware and the firmware, how do you ensure that some random company doesn't steal your work? or it has something to do with Licence status we see on the screenshot ?
neat, but this means you need to run one server to provide the licence information, right ? what happens when you decide that you don't want to run the service anymore ?
I am only asking because I'm curios about the way the service is supposed to work, the number of companies that run a similar service and they decide to stop offering it is increasing and you'll just be left with your hardware but without a way to use it.