I just noticed a few slightly worrying messages in the log:
3/20/19 13:16:27 timesync: Kiss-o’-Death, code RATE, ip: 184.108.40.206
3/20/19 13:16:36 timesync: Kiss-o’-Death, code RATE, ip: 220.127.116.11
3/20/19 13:16:46 timesync: Kiss-o’-Death, code RATE, ip: 18.104.22.168
3/20/19 13:16:55 timesync: Kiss-o’-Death, code RATE, ip: 22.214.171.124
Though everything seems to be working fine anyway
ALPHA channel, running 02_04_00. Up since 3/12/19, and no more messages since 3/20/19
Yea, that’s nothing to worry about.
IoTaWatt checks the time with pool.ntp.org every hour. The pool servers, in an effort to minimize load, push back when they get a lot of requests from a specific IP. This is their way of telling IoTaWatt to back off, which it does… somewhat.
I have tried to register IoTaWatt as a regular user of the service, but the request has gone unanswered. So beginning with the next release, I will be switching over to time.google.com. For all the capacity problems that ntp.org has, this is a trivial service for google, who are in a better position to do this globally anyway.