weewx.engine: Ignore historical record

[Dirk Howard]

I have WeeWX installed on a Raspberry PI. I am getting and error that seems to keep me from updating the weather from my Vantage Pro II.

Sep 02 19:40:16 weewxpi weewxd[63594]: WARNING weewx.engine: Ignore historical record: {'dateTime': 1767095700, 'usUnits': 1, 'interval': 5, 'rxCheckPercent': 87.97916666666666, 'outTemp': 55.1, '
highOutTemp': 55.4, 'lowOutTemp': 55.1, 'rain': 0.0, 'rainRate': 0.0, 'barometer': 29.936, 'wind_samples': 103.0, 'inTemp': 72.6, 'inHumidity': 34.0, 'outHumidity': 73.0, 'windSpeed': 0.0, 'windGu
st': 0.0, 'ET': 0.0, 'forecastRule': 45}

I am not sure how to clear this error to move on past this record.

[Tom Keffer]

The timestamp in the record is 4 months in the future, so it is getting rejected.This can happen if the internal clock in the VP2 was not set correctly, perhaps because the clock in your RPi is not set correctly. See the wiki article on the Raspberry Pi.

It's hard to say much more without seeing the log. Set debug=1, restart weewx, let it run through the first archive cycle, then post the log. See the wiki article on logs for more details.

-tk

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/0368c7c1-b0a3-4003-9938-113e6810eebdn%40googlegroups.com.

[Dirk Howard]

The time is correct on the RPi and the Vantage console.

Here is a log snippet. Let me know if I need a larger snapshot.

Sep 07 11:45:04 weewxpi weewxd[76855]: INFO weewx.engine: 'pyephem' detected, extended almanac data is available

Sep 07 11:45:04 weewxpi weewxd[76855]: DEBUG weewx.engine: Finished loading service weewx.engine.StdReport
Sep 07 11:45:04 weewxpi weewxd[76855]: INFO __main__: Starting up weewx version 5.1.0
Sep 07 11:45:05 weewxpi weewxd[76855]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console
Sep 07 11:45:05 weewxpi weewxd[76855]: INFO weewx.engine: Clock error is 3.54 seconds (positive is fast)
Sep 07 11:45:05 weewxpi weewxd[76855]: INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
Sep 07 11:45:05 weewxpi weewxd[76855]: INFO weewx.manager: Starting backfill of daily summaries
Sep 07 11:45:05 weewxpi weewxd[76855]: INFO weewx.manager: Daily summaries up to date
Sep 07 11:45:05 weewxpi weewxd[76855]: DEBUG weewx.drivers.vantage: Getting archive packets since 2025-08-30 04:50:00 MDT (1756551000)
Sep 07 11:45:05 weewxpi weewxd[76855]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console
Sep 07 11:45:07 weewxpi weewxd[76855]: DEBUG weewx.drivers.vantage: Retrieving 478 page(s); starting index= 0
Sep 07 11:45:07 weewxpi weewxd[76855]: WARNING weewx.engine: Ignore historical record: {'dateTime': 1767095700, 'usUnits': 1, 'interval': 5, 'rxCheckPercent': 87.97916666666666, 'outTemp': 55.1, '

highOutTemp': 55.4, 'lowOutTemp': 55.1, 'rain': 0.0, 'rainRate': 0.0, 'barometer': 29.936, 'wind_samples': 103.0, 'inTemp': 72.6, 'inHumidity': 34.0, 'outHumidity': 73.0, 'windSpeed': 0.0, 'windGu
st': 0.0, 'ET': 0.0, 'forecastRule': 45}

Sep 07 11:45:07 weewxpi weewxd[76855]: DEBUG weewx.drivers.vantage: DMPAFT complete: page timestamp 2025-08-30 05:00:00 MDT (1756551600) less than final timestamp 2025-12-30 04:55:00 MST (17670957
00)
Sep 07 11:45:07 weewxpi weewxd[76855]: DEBUG weewx.drivers.vantage: Catch up complete.
Sep 07 11:45:07 weewxpi weewxd[76855]: INFO weewx.engine: Starting main packet loop.
Sep 07 11:45:08 weewxpi weewxd[76855]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console
Sep 07 11:45:08 weewxpi weewxd[76855]: DEBUG weewx.drivers.vantage: Requesting 200 LOOP packets.
Sep 07 11:45:08 weewxpi weewxd[76855]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console

[Tom Keffer]

Amazing what a log can reveal. It looks like the memory in your logger is corrupted. The key is the large number of unarchived pages (478), yet when you try to read them, oldest to youngest, you get a date in the future.

Follow the suggestions in the wiki on Corrupt station memory.

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/3cc74a7f-8fd5-462c-893d-cf82fb1b0e82n%40googlegroups.com.

[Dirk Howard]

Tom,

It turns out that I needed to dump the station log, clear the station memory and then delete log entries from the sqlite3 database that were future values. 

weectl device --dump

weectl device --clear-memory

sqlite3 /var/lib/weewx/weewx.sdb

I now seem to be up and running correctly.

Thank you so very much for your insight and help.

Dirk