RPi weewx acurite 5-in-1 error

[Sean Jahnig]

I have the acurite 5-in-1 with rpi 4 and it has been running flawlessly for a week. This morning i woke up to find this error.

Has anyone seen this error before?

Oct 27 06:55:19 raspberrypi weewx[603]: cheetahgenerator: Generated 8 files for report SeasonsReport in 0.63 seconds

Oct 27 06:55:19 raspberrypi weewx[603]: imagegenerator: Generated 14 images for SeasonsReport in 0.52 seconds

Oct 27 06:55:19 raspberrypi weewx[603]: copygenerator: copied 0 files to /var/weewx/reports

Oct 27 07:00:25 raspberrypi weewx[603]: manager: Added record 2019-10-27 07:00:00 +04 (1572145200) to database 'weewx.sdb'

Oct 27 07:00:25 raspberrypi weewx[603]: manager: Added record 2019-10-27 07:00:00 +04 (1572145200) to daily summary in 'weewx.sdb'

Oct 27 07:00:26 raspberrypi weewx[603]: cheetahgenerator: Generated 8 files for report SeasonsReport in 0.63 seconds

Oct 27 07:00:28 raspberrypi weewx[603]: imagegenerator: Generated 28 images for SeasonsReport in 1.60 seconds

Oct 27 07:00:28 raspberrypi weewx[603]: copygenerator: copied 0 files to /var/weewx/reports

Oct 27 07:00:29 raspberrypi weewx[603]: restx: WindGuru: Published record 2019-10-27 07:00:00 +04 (1572145200)

Oct 27 07:00:56 raspberrypi weewx[603]: acurite: R2: unknown calibration constants: 02 00 00 80 00 00 00 00 00 04 00 11 01 01 01 13 c1

The station is at a remote location but i am able to log in and see that the signal is 100% and the station has been online continuously without any downtime.

I tried a reboot this morning hoping it was just a once off thing - but alas, the errors are back. Nothing has changed with the setup.

Thanks,

Sean.

[p q]

I haven't see that exact error, but I have seen occasional random errors. They don't seem to affect the results.

--
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 on the web visit https://groups.google.com/d/msgid/weewx-user/d988e994-0f46-4fc1-8c43-64344ea41889%40googlegroups.com.

--

Peter Quinn
(415)794-2264

[Sean Jahnig]

Thanks for the reply.

When i run sudo service weewx status the errors seem to be gone now.

The troubling thing is that over the last 12 hours of windguru live wind reporting there are 5 or 6 periods of about 10min each where there was no report.

I will keep an eye on it.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAA1SM222DeeAnj5dKZA7bqRjUuKPZjuq3vsLA8RrPrQ2zBN_AQ%40mail.gmail.com.

[Ξ]

Today my station started doing the same AcuRite 01036, weewx v3.7.1, Arch Linux on R-Pi:

Aug 08 15:02:26 alarmpi weewxd[309]: LOOP:   2020-08-08 15:02:09 EEST (1596888129) altimeter: None, appTemp: None, barometer: None, channel: None, cloudbase: None, dateTime: 1596888129, dewpoint: None, heatindex: None, humidex: None, inDewpoint: None, maxSolarRad: None, outTempBatteryStatus: None, pressure: None, rainRate: 0.0, rssi: None, sensor_battery: None, sensor_id: None, usUnits: 17, windchill: None
Aug 08 15:02:26 alarmpi weewx[309]: acurite: next read in 12 seconds
Aug 08 15:02:38 alarmpi weewx[309]: acurite: Found station at bus=001 device=005
Aug 08 15:02:38 alarmpi weewx[309]: acurite: R2: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Aug 08 15:02:38 alarmpi weewx[309]: acurite: R2: unknown calibration constants: 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Aug 08 15:02:38 alarmpi weewx[309]: acurite: next read in 6 seconds
Aug 08 15:02:44 alarmpi weewx[309]: acurite: Found station at bus=001 device=005
Aug 08 15:02:44 alarmpi weewx[309]: acurite: R1: 01 00 00 00 00 00 00 00 00 00
Aug 08 15:02:44 alarmpi weewx[309]: acurite: R1: bogus message flavor (00): 01 00 00 00 00 00 00 00 00 00
Aug 08 15:02:44 alarmpi weewx[309]: acurite: next read in 18 seconds
Aug 08 15:03:02 alarmpi weewx[309]: acurite: Found station at bus=001 device=005

I found this https://github.com/weewx/weewx/issues/39 when I was looking for the errors, is the only solution a USB reset? I have USB mode set to 4.

- Ivo