Weewx / Interceptor stopped updating database and reports

[Darren Parris]

Hi

I hope someone can help, I have posted on WXForums see link below and it was suggested try here.

In a nutshell, I'm using weewx 4.5.1 on a raspberry pi, using the interceptor driver to capture the weather data. All has been working fine for a long time, On Sept 12, the reports stopped being generated and the database file timestamp has stopped being updated. I'm not aware of any changes being made at this time.

I have re installed the RPi, with latest Raspbian, reinstalled Weewx, interceptor etc, still have the same issue over the database and reports not being updated. If I set the simulator driver, all works instantly. DB and reports are updated.

More detailed  background to the issue and steps already taken can be seen here.

https://www.wxforum.net/index.php?topic=42742.new#new

A couple of syslog entries below shows that data is being captured, however I have just noticed that the date time value remains the same. Is that correct?

Sep 27 12:16:40 piweather weewx[1273] DEBUG user.interceptor: raw packet: {'dateTime': 1632741017, 'usUnits': 1, 'rain_total': 13.61, 'temperature_out': 57.7, 'humidity_out': 71.0, 'dewpoint': 48.4, 'windchill': 57.7, 'wind_dir': 255.0, 'wind_speed': 5.59, 'wind_gust': 7.61, 'solar_radiation': 91.93, 'uv': 2.0, 'temperature_in': 73.4, 'humidity_in': 56.0, 'pressure': 30.44, 'battery': 2.0, 'rain': 0.0}

Sep 27 12:16:40 piweather weewx[1273] DEBUG user.interceptor: mapped packet: {'dateTime': 1632741017, 'usUnits': 1, 'pressure': 30.44, 'outHumidity': 71.0, 'inHumidity': 56.0, 'outTemp': 57.7, 'inTemp': 73.4, 'windSpeed': 5.59, 'windGust': 7.61, 'windDir': 255.0, 'radiation': 91.93, 'dewpoint': 48.4, 'windchill': 57.7, 'rain': 0.0, 'UV': 2.0, 'txBatteryStatus': 2.0}

Sep 27 12:20:08 piweather weewx[1273] DEBUG user.interceptor: raw packet: {'dateTime': 1632741017, 'usUnits': 1, 'rain_total': 13.61, 'temperature_out': 57.7, 'humidity_out': 70.0, 'dewpoint': 48.0, 'windchill': 57.7, 'wind_dir': 192.0, 'wind_speed': 4.47, 'wind_gust': 7.61, 'solar_radiation': 88.4, 'uv': 2.0, 'temperature_in': 73.4, 'humidity_in': 56.0, 'pressure': 30.44, 'battery': 2.0, 'rain': 0.0}

Sep 27 12:20:08 piweather weewx[1273] DEBUG user.interceptor: mapped packet: {'dateTime': 1632741017, 'usUnits': 1, 'pressure': 30.44, 'outHumidity': 70.0, 'inHumidity': 56.0, 'outTemp': 57.7, 'inTemp': 73.4, 'windSpeed': 4.47, 'windGust': 7.61, 'windDir': 192.0, 'radiation': 88.4, 'dewpoint': 48.0, 'windchill': 57.7, 'rain': 0.0, 'UV': 2.0, 'txBatteryStatus': 2.0}

Please let me know if you want any more information or log files etc.

[Darren]

I have just noticed this in the syslog

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: using rain_total 13.61 from yearlyrainin

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: firmware WH2600GEN_V2.2.5: baromin is pressure

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: ignored parameter ID=XXXX

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: ignored parameter PASSWORD=XXXXXXXX

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: ignored parameter rainin=0.00

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: ignored parameter weeklyrainin=0.99

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: ignored parameter monthlyrainin=4.05

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: ignored parameter softwaretype=WH2600GEN_V2.2.5

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: ignored parameter action=updateraw

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: ignored parameter realtime=1

Sep 27 13:07:52 piweather weewx[27609] DEBUG user.interceptor: ignored parameter rtfreq=5

[Darren]

syslog extract

[gjr80]

Hi,

Posting your problem to multiple threads won’t get you more help, in fact it will possibly hinder us helping you. Since this thread is dedicated to your issue let’s keep this issue in this thread and leave the other.

Your problem is with your station; the data it is emitting always has the same date-time field (dateutc) and consequently the mapped packets always have the same the same timestamp. The net effect of this on WeeWX is that archive records are never generated, so nothing is saved to database and no reports run etc. In effect WeeWX reads data but does nothing else. I see wind speed is changing in each packet so the station appears to be otherwise operating OK and emitting different packets, they just have the same date-time.

How to fix, I don’t know but you need to start with your station. Can you reset it? If there is no means of hardware reset remove all power sources, including battery, for say 10 minutes and then restore power. I can’t see there is a setting in the station that would do such a thing, sending packets with the same date-time is non-sensical. Does your station post directly to WU or the likes? If so is that working?

Another solution would be for the interceptor driver to ignore the station emitted date-time and use the WeeWX system time, this is a common approach amongst some drivers but the interceptor does not presently support this. It would take changes to the interceptor code.

Just an aside for future issues. It is likely the re-install of the OS and WeeWX and the change to python3 was unnecessary. If python version was an issue you would have had very clear errors in your log. Reinstalling WeeWX is seldom required, typically only required if you need a new version with new features, that was not the case for you. Re-installing the OS is almost never required, you must be thinking Windows; this is Linux :).

Gary

[Darren]

Thank you for the response.

Firstly I didn’t intend to post multiple times, I only commented on the other post to see if a solution had been found, was asked to submit log. I then realised, the log file should really have been on my own post.

My RPi was solely being used for weewx so no big loss for reinstalling etc. also gave me the opportunity to upgrade OS. 

I had noticed the datetime stamp was the same and questioned it, but you have now confirmed the issue is with my hardware. I will investigate further, I have already done a ‘factory reset’ earlier today but no joy. 

I really appreciate your time and assistance, the writers of weewx and the intercept driver, and the whole community of helpers, without any of that I wouldn’t have been able to use it in the first place.

If I find a way to resolve, I will update.

[Darren]

Thank you to all for advice.

I went back to the UK retailer where I purchased it many years ago  and logged a support ticket.

Very helpful, suggested a firmware upgrade to the Rx and bingo it is fixed, all working again.