30-10-2018, 19:17
Hi 41south,
the problem comes from the corrupt timestamps you get from the WeatherDuino bug.
There may be two issues now:
1. Datasets with wrong timestamps are in the EEPROM of the WeatherDuino saved bringing WeeWx to go mad. I don't know exactly if it's implemented in the WeatherDuino but you can try to erase the logger and start up again.
2. You have corrupt datasets in your WeeWx Database.
The solutions for your faults can be found here:
http://www.weewx.com/docs/usersguide.htm
Points: Clock skew and Corrupt station memory in the last thrid of the document.
You will get the problem over and over again as long as your WeatherDuino clock does not work properly.
Regards, engolling
the problem comes from the corrupt timestamps you get from the WeatherDuino bug.
There may be two issues now:
1. Datasets with wrong timestamps are in the EEPROM of the WeatherDuino saved bringing WeeWx to go mad. I don't know exactly if it's implemented in the WeatherDuino but you can try to erase the logger and start up again.
2. You have corrupt datasets in your WeeWx Database.
The solutions for your faults can be found here:
http://www.weewx.com/docs/usersguide.htm
Points: Clock skew and Corrupt station memory in the last thrid of the document.
You will get the problem over and over again as long as your WeatherDuino clock does not work properly.
Regards, engolling