WeeWX rain not matching console and WU
75 views
Skip to first unread message
Gábor Szabados
May 15, 2019, 5:44:01 AM5/15/19
to weewx-user
Hi,
I am quite new to WeeWX but I have managed to set it up on Raspberry Pi Zero W. I am using a unit which is a Eurochron EFWS 2900, one of the FineOffset clones. It sends the data to the console and the console is connected by Wifi to the Rpi0 W. The Rpi0 W has the wifi set up as AP and client. The routing works well, and interceptor is set up to sniffing in wu-client mode.
The total daily rain shown on the console is matching the total daily rain on the WU page. But the WeeWX page shows far more rain than the previous two. At the moment for today it shows double amount. On some other days it was 3-4 times more than the two other places. I believe the console and the WU page shows the right values.
Suddenly I cannot find out what is the source of the issue. I am quite new to WeeWX, and missing some skills to debug it. I have some far recognized that at sometime it logs a bigger amount of rain than it should be.
What I have noticed, that the log has the following lines, what might be the reason for the issue.
May 15 06:35:24 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.05 last=0.06
May 15 06:54:59 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.07 last=0.08
May 15 06:56:47 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.07 last=0.08
May 15 06:58:10 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.07 last=0.08
May 15 07:00:18 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.07 last=0.08
May 15 07:04:35 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.07 last=0.08
May 15 07:07:05 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.07 last=0.09
May 15 07:15:07 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.09 last=0.1
May 15 07:17:15 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.09 last=0.1
May 15 07:19:26 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.09 last=0.1
May 15 07:28:58 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.1 last=0.11
May 15 07:40:28 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 07:40:43 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 07:43:26 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 07:45:01 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 07:45:50 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 07:47:10 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 07:48:26 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 07:49:50 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 07:49:53 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 07:52:29 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.11 last=0.12
May 15 08:31:08 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.15 last=0.16
May 15 08:32:59 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.15 last=0.16
May 15 08:36:14 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.15 last=0.16
May 15 08:46:02 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.16 last=0.17
May 15 08:59:22 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.17 last=0.18
May 15 09:48:26 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.18 last=0.19
May 15 09:49:02 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.18 last=0.19
May 15 09:51:11 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.18 last=0.19
May 15 09:53:19 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.18 last=0.19
May 15 09:55:14 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.18 last=0.19
May 15 09:55:38 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.18 last=0.19
May 15 09:57:50 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.18 last=0.19
May 15 10:00:12 WeeWX weewx[26882]: interceptor: MainThread: rain counter wraparound detected: new=0.18 last=0.19
The 0.19 inch rain is matching with that I can see on the console and in WU, meanwhile WeeWX shows 0.32 inch. I have seen previously in the logged data that occasionally WeeWX is logging more rain then what what was reported by the station.
I don't know is it an Interceptor a WeeWX logging issue.
I am using WeeWX 3.9.1, and Interceptor 0.45.
I've attached the WeeWX configuration too.
I have a feeling that the interceptor's this section is causing the issue, when it logs the new value to rain:
| def _delta_rain(rain, last_rain): | |
| if last_rain is None: | |
| loginf("skipping rain measurement of %s: no last rain" % rain) | |
| return None | |
| if rain < last_rain: | |
| loginf("rain counter wraparound detected: new=%s last=%s" % | |
| (rain, last_rain)) | |
| return rain | |
| return rain - last_rain |
Suddenly I have no idea why the values are wrapped around.
Thank you in advance for any help!
Best Regards,
Gábor Szabados
Gábor Szabados
May 15, 2019, 6:15:04 PM5/15/19
to weewx-user
Hi,
I've looked at the logs and this is what happens:
May 15 23:23:10 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter rainin=0.07
May 15 23:23:10 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter absbaromin=29.74
May 15 23:23:10 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter monthlyrainin=1.34
May 15 23:23:10 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter weeklyrainin=0.82
May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter rainin=0.05
May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter absbaromin=29.74
May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter monthlyrainin=1.33
May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter weeklyrainin=0.81
May 15 23:24:26 WeeWX weewx[419]: interceptor: MainThread: rain counter wraparound detected: new=0.31 last=0.32
May 15 23:24:27 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter rainin=0.07
May 15 23:24:27 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter absbaromin=29.74
May 15 23:24:27 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter monthlyrainin=1.34
May 15 23:24:27 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter weeklyrainin=0.82
May 15 23:24:46 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter rainin=0.07
May 15 23:24:46 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter absbaromin=29.74
May 15 23:24:46 WeeWX weewx[419]: interceptor: MainThread: unrecognized parameter monthlyrainin=1.34
All the wraparounds are causing the interceptor driver to set the last rain value to the new, and then a correct record comes again, which adds the same difference again and again. (If we are disregarding, that it really returns the new value as the amount of rain and that is even worse.)
I have still no idea why the messages are containing these values, and triggering the wraparound. Should this be reported as bug for Interceptor?
Thanks,
Gábor
Gábor Szabados
May 16, 2019, 4:26:35 AM5/16/19
to weewx-user
It has turned out that the wraparound packets were from a previous time when I started inspect the dateTime of the messages. I've implemented a modification into my interceptor to check the time and don't let previous rain values to mix up things.
Can anyone tell me, when Interceptor passes the data to WeeWX, does the dateTime value from the messages are used? I am just worried about that these out of order messages can screw other things up too? I only guess that the console is resending some messages to WU when it has not confirmed received. That is may causing the disorder.
Thanks for any help!
Gábor
Can anyone tell me, when Interceptor passes the data to WeeWX, does the dateTime value from the messages are used? I am just worried about that these out of order messages can screw other things up too? I only guess that the console is resending some messages to WU when it has not confirmed received. That is may causing the disorder.
Thanks for any help!
Gábor
Reply all
Reply to author
Forward
0 new messages