Page 1 of 1

Rain overshoot to 10.7 and settling down at 9.2

Posted: Mon 22 Jan 2024 10:02 am
by HansR
Today it was raining (see chart) and the rain suddenly peaked to 10.7 mm after which the system seemed to realize it was not correct and the total rain went down until it settles on 9.2. I have no calibration and no spike handling.

This seems pretty weird (never seen before) and I wonder if this is Ecowitt or CMX.
So check ecowitt.net and it seems to be Ecowitt.
I'll contact them.

Anybody else this phenomenon?
    Schermafbeelding 2024-01-22 105251.png
    Schermafbeelding 2024-01-22 105902.png

    Re: Rain overshoot to 10.7 and settling down at 9.2

    Posted: Mon 22 Jan 2024 10:12 am
    by mcrossley
    Weird, I've never seen that (but I have not had a WH40 for that long), which rain sensor are you using?

    Re: Rain overshoot to 10.7 and settling down at 9.2

    Posted: Mon 22 Jan 2024 10:16 am
    by mcrossley
    Not the same, but someone else with Ecowitt rain oddities - different values on two different gateways: https://www.wxforum.net/index.php?topic=46380.msg468842

    Re: Rain overshoot to 10.7 and settling down at 9.2

    Posted: Mon 22 Jan 2024 10:21 am
    by HansR
    mcrossley wrote: Mon 22 Jan 2024 10:12 am Weird, I've never seen that (but I have not had a WH40 for that long), which rain sensor are you using?
    WH40 on a GW1100 ... sorry should have mentioned that.
    mcrossley wrote: Mon 22 Jan 2024 10:16 am Not the same, but someone else with Ecowitt rain oddities - different values on two different gateways: https://www.wxforum.net/index.php?topic=46380.msg468842
    Yes, but there we are talking about a wittboy with a haptic sensor vs a WH40 with a classic sensor.
    I expect differences there though 3.2 vs 6.0 is quite large :shock:

    Re: Rain overshoot to 10.7 and settling down at 9.2

    Posted: Mon 22 Jan 2024 7:35 pm
    by mcrossley
    He is seeing the difference in the same sensor across gateways, the sensor id is the same with very different rain values. Though the calibration could have gone screwy in one I guess. (Haven't checked the thread since first thing this morning)