To make the issue more clear, I have recorded a video that shows the issue 
that I am trying to resolve: video 
<https://drive.google.com/file/d/1WoQfeVg0ZHdXKacnUuNZLpeMxCEKahsB/view?usp=sharing>

As can be seen, the wind speed displayed by the console is not reflected in 
that displayed by weewx   weewx is only show speeds that are multiples of 
1.6 kph (i.e. 1mph).

Here is an excerpt of what's in my DB for wind speeds and wind gust.

MariaDB [weewx]> select round(windSpeed,1) as windSpeed, round(windGust,1) 
as windGust from archive order by dateTime desc limit 10;
+-----------+----------+
| windSpeed | windGust |
+-----------+----------+
|       0.4 |      2.0 |
|       0.3 |      2.0 |
|       0.6 |      4.0 |
|       0.3 |      2.0 |
|       0.9 |      4.0 |
|       0.7 |      3.0 |
|       0.8 |      4.0 |
|       0.6 |      4.0 |
|       0.4 |      3.0 |
|       0.4 |      3.0 |
+-----------+----------+

The wind gust is obviously in increments of 1mph while the wind speed shows 
more variation.  Based on what I've seen in weewx, I did not think that 
there were any non-zero wind speeds being recorded but I was obviously 
mistaken about that.  Nonetheless, those speeds are not being displayed in 
the live widget.

Basically, my expectation is that, within reason, the speeds displayed by 
weewx and that by the console are the same.

In case it's not obvious, the skin that I'm using is Belchertown with mqtt 
integration.
On Tuesday, December 9, 2025 at 10:00:35 AM UTC-8 vince wrote:

> I’m running two weewx instances as a test.  One uses the Davis serial 
> datalogger attached to the old style console and the Vantage driver. The 
> other uses a SDR to sniff the RF and the rtldavis driver.
>
> In a couple wet/windy days testing the NOAA reports are identical for 
> temperature and rain. The wind readings are very similar but not identical, 
> differing by only a fraction of a mph in high speed and average speed and 
> differing slightly in dominant direction.
>
> I can look a little deeper with a few days more data, but I don’t see 
> crazy differences here so far.
> On Tuesday, December 9, 2025 at 12:05:40 AM UTC-8 John Smith wrote:
>
>> On Tue, 9 Dec 2025 at 17:44, Danny Ciarniello <[email protected]> 
>> wrote:
>>
>>> The issue is not one of units; it's an inconsistency between what the 
>>> Weatherlink console is displaying and what weewx is.  
>>>
>>
>> Then what is it?
>>  
>>
>>> For example, for the series of speeds that I posted previously, which 
>>> were taken from the console, weewx recorded 0 as the speed.  From 
>>> observation, when the console displays a speed between 0 and 1.6kph, weewx
>>>
>>
>> Which could easily be explainable as rounding somewhere...
>>  
>>
>>> records 0; for speeds between 1.6 and 3.2 kph, weewx displays 1.6kph, 
>>> for speeds between 3.2 and 4.8kph,
>>>
>>
>> To see 1.6, 3.2 and 4.8km/hr sounds exactly like it's converting from 
>> whole mph readings...
>>  
>>
>>> weewx displays 3.2kph and so on.  Obviously, if those values are 
>>> converted to mph, the progression is 1mph, 2mph, 3mph which implies that 
>>> for some reason, weewx is only recording speeds in increments of 1mph.  A 
>>> complication is that while that is generally what happens, I do 
>>> occasionally see weewx recording wind speeds that are not multiples of 
>>> 1mph.  Wind gust, however, is *always* a multiple of 1mph.
>>>
>>
>> As I said, mine always reports whole numbers, but in km/hr, never 
>> fractions...
>>  
>>
>>> The rtldavis/weewx-rtldavis and the console are obviously receiving the 
>>> same signal but they are interpreting it differently.
>>>
>>
>> Exactly what I said... What the console shows doesn't have to match the 
>> units of the values in the background... 
>>
>

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/9ccb1462-2e18-4833-b242-c9429785fcfbn%40googlegroups.com.

Reply via email to