[41south]

I'll move this problem here so as not to confuse it with the other date problem.

This 'rogue' REC data is causing the Weewx connection to my W/Duino to fail, if it's coming from the logger (due to the other date issue with RTC) can that be cleared?


REC:    2019-09-11 12:25:00 NZST (1568161500) appTemp: 25.1971216855, barometer: 995.97062139, cloudbase: 1389.00049386, consBatteryVoltage: None, dateTime: 1568161500, dewpoint: 13.1290899619, ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, forecastRule: 193, heatindex: 24.2222222222, highRadiation: 12.0, highUV: 0.0, humidex: 27.090004937, inDewpoint: 12.0486967731, inHumidity: 48.0, inTemp: 23.7222222222, interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 0.0, maxSolarRad: 678.570029189, outHumidity: 50.0, outTemp: 24.2222222222, radiation: 9.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None, usUnits: 16, UV: 0.0, windchill: 24.2222222222, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0

LOOP:   2018-10-30 16:40:01 NZDT (1540870801) altimeter: 1001.46292981, appTemp: 19.8074938836, barometer: 1001.76134514, cloudbase: 1199.9199747, consBatteryVoltage: 0.0, dateTime: 1540870801, dayET: 0.0, dayRain: 0.0, dewpoint: 10.1454875124, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, extraTemp4: 0.0, extraTemp5: 0.0, extraTemp6: 0.0, extraTemp7: 0.0, forecastIcon: 0, forecastRule: 0, heatindex: 19.7222222222, humidex: 21.0679676888, inDewpoint: 9.58203446493, inHumidity: 52.0, insideAlarm: 0, inTemp: 19.7222222222, leafTemp1: 0.0, leafTemp2: 0.0, leafTemp3: 0.0, leafTemp4: 0.0, leafWet1: 0.0, leafWet2: 0.0, leafWet3: 0.0, leafWet4: 0.0, maxSolarRad: 556.845996519, monthET: 0.0, monthRain: 0.0, outHumidity: 54.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 19.7222222222, pressure: 1001.07369386, radiation: 6.0, rain: None, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, stormRain: 0.0, stormStart: 943873200, sunrise: 1540810800, sunset: 1540810800, trendIcon: -1, txBatteryStatus: 0, usUnits: 16, UV: 0.0, windchill: 19.7222222222, windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0, windSpeed10: 0.0, yearET: 0.0, yearRain: 0.0

[werk_ag]

I don't know how Weewx works, but a wrong timestamp on a logger record shouldn't prevent it to connect. At least with Cumulus, if a record has timestamp from a past date, the record is ignored, if the timestamp is from a date in the future, then it will be wrongly inserted in the logs, but connection with the station always starts.

Please do a search on the forum about Weewx, I can't remenber exactly, but I have a memory of some config related to the logger. For testing connection, try to disable the use of the data logger on Weewx, not in WeatherDuino. It should be possible, as many original Davis Weather Stations don't have the data logger addon.

The software doesn't provide any way to erase the data logger chip. There is a reason for this, but its a long story...

[41south]

When you say do a search on the forum do you mean this one or the Weewx forum?

This is the Weewx error


Oct 30 16:39:56 raspberrypi weewx[5059]: manager: Unable to add record 2019-09-11 12:25:00 NZST (1568161500) to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

It makes sense that it does not want to add future dates but I'm not sure why it stops the connection from working. It seems to pick up this faulty record every archive period of 5 mins

Have a look at my site www.41south.net.nz and you'll see that that record completely screws with the data

[engolling]

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

[41south]

The REC dates are random too

REC:    2018-12-14 00:15:00 NZDT (1544699700) appTemp: 19.3255115734, barometer: 1016.01803929, cloudbase: 1161.7160116, consBatteryVoltage: None, dateTime: 1544699700, dewpoint: 10.0074331515, ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, forecastRule: 193, heatindex: 19.2777777778, highRadiation: 0.0, highUV: 0.0, humidex: 20.5594798103, inDewpoint: 11.8966103902, inHumidity: 63.0, inTemp: 19.1111111111, interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 0.0, maxSolarRad: 0.0, outHumidity: 55.0, outTemp: 19.2777777778, radiation: 0.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None, usUnits: 16, UV: 0.0, windchill: 19.2777777778, windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0

There has to be a way to fix this after the date/time problems - other than just getting Weewx to ignore the data, which doesn't seem right to me

[engolling]

AFAIK the REC data is the data stored in the EEPROM of the WeatherDuino internal datalogger. So if your internal clock is wrong you have bad records in your logger memory.

engolling

[41south]

Agree, so how to clear the bad records now that the clock problem is hopefully fixed?

[werk_ag]

You can use the attached small utility to erase the flash memory.

[werk_ag]

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.

Records are stored in the Flash Memory strictly following the Davis format. Even the chip used is the same than the one used on original Davis data loggers. The EEPROM only stores config parameters

[engolling]

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.

Records are stored in the Flash Memory strictly following the Davis format. Even the chip used is the same than the one used on original Davis data loggers. The EEPROM only stores config parameters

Thanks for the answer. I mistook the flash memory with the EEPROM.