Good that it is cleaned up. I will release v0.3.2 directly.

As for sensor packet loss, how long is a piece of string. I have three 
moisture sensors, one about five metres from the GW1000, another 10 metres 
and another 30 metres all through an internal plasterboard wall and window; 
the 30 metre one with a chunk of brick veneer house sticking out into the 
path. The first two are rock solid, the 30 metre one was rock solid but is 
about 60-40 connected/not connected these days, maybe it’s a battery issue. 
On the other hand I have two WH31 the furthest is about 30 metres away 
through brick veneer wall and in a locked steel shed with no windows and it 
is rock solid. Likewise the other WH31 about 10 metres away through a 
plasterboard wall. The performance of the WH31 in the shed surprised me. 
The 30m WH51 does not surprise me. My WH41 is only a couple of metres from 
the GW1000 and has a plasterboard wall between it and the GW1000 and it is 
rock solid, it is powered by a 5V plug pack though.

Assuming your batteries/power is good I would say you either got Friday 
afternoon devices or there is some interference. I would expect better.

Gary

On Friday, 23 April 2021 at 15:29:47 UTC+10 [email protected] wrote:

> even after only a few hours it is obvious that it has cleaned up the 
> battery status data
>
> the following graphs show before and after new gw1000.py at 12pm:
>
>
>
> as to why the sensor packet loss is so high, that is something else for me 
> to investigate (none are more than 10m from receiver). is this level of 
> loss normal for gw1000?
>
> On 22 Apr 2021, at 5:55 pm, Graham Eddy <[email protected]> wrote:
>
> this reminds me strongly of windDir value when windSpeed==0
>
> On 22 Apr 2021, at 3:46 pm, gjr80 <[email protected]> wrote:
>
> Sensor signal level 0 is a valid signal level so we cannot just omit a 
> sensor entirely just because the GW1000 reports signal level = 0. At the 
> same time we know that the battery state data is at best unreliable, and in 
> some cases plain invalid, so I am happy for the driver to ignore battery 
> state in such cases.
>
>
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3f791523-b2c9-42d5-9425-b5f815d1148en%40googlegroups.com.

Reply via email to