hi,
thank you for the explanation
michael
--
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+unsubscr...@googlegroups.com.
For more options, visit https:
michael,
some hardware (acurite, cc3000, fousb, te923, ultimeter, wmr100, wmr200,
ws1) does not measure windGustDir.
some of those drivers (wmr100, wmr200, te923, fousb) were assigning
windGustDir to windDir. by doing so, the drivers were creating bogus data.
in weewx 3.7.0 this behavior was
I just looked through the pre-3.7.0 WMR100 driver and in loop packets it quite
clearly sets windGustDir = windDir under some conditions and in all other cases
it sets windGustDir = None. The WMR100 only emit loop packets so all I can
think is that the intermingling of None values has resulted in
hi again,
but i dont understand why my database looks like this with older weewx
5.10768389526141 241.970925549116 6.03974300023612 247.5
> 4.1942659723862 281.54912604993 6.26343718543005 292.5
> windspeed winddir windgust
>windgus
Yes, there were a lot for 3.7.0, always worthwhile having a read through them
though.
Gary
--
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+unsubscr...
hi,
i see, sorry, to much changes for me ;-)
michael
Am Dienstag, 14. März 2017 08:03:58 UTC+1 schrieb gjr80:
>
> Hi,
>
> 33rd item in the 3.7.0 changelog:
>
> The observation windGustDir has been removed from wmr100, wmr200, te923,
> and
> fousb drivers. These drivers were simply assigning wi
