Wind Run in RTGD with SteelSeries Gauges

[Rory Gillies]

Hi,

During a clear out in my office I found an iPad 3 from years back. As it can only run iOS 9.3.6 most modern apps won't run on it so it's not much use, however I thought it would make a great real time weather display for my WeeWX installation with a Davis Vantage 2 Pro ISS and WeatherLinkLive. I had played around with the SteelSeries gauges before so I have set it up using RTGD (latest version from gjr80 on GitHub) with a 3 second interval and it's working well (with a couple of issues). I have made it as a home screen app so it runs full screen:

When using the SteelSeries report to generate gauge-data.txt the wind run odometer works as expected, however using RTGD to generate the file wind run is always zero. I have searched through the various options but can't find any setting for this, any ideas?

I also noticed that after a while (around 10 minutes but sometimes more) the interface stops updating. I think this is an issue with the iPad (it does the same on a 2022 iPad Pro) as the gauge-data.txt file is still updating. I have added a simple Javascript timer to refresh the page every 10 minutes which solves the problem but it would be nice if there was a more elegant solution.

The digital display for wind speed shows the current value from the loop packet, is there any way to make this display the average wind speed? A bit like the direction gauge shows the average direction. 

Thanks,

Rory

[John Kline]

> On Dec 29, 2023, at 4:30 AM, 'Rory Gillies' via weewx-user <weewx...@googlegroups.com> wrote:
>
> I also noticed that after a while (around 10 minutes but sometimes more) the interface stops updating.

The default is to timeout after 20m unless you have passed the correct page update password (defaults to its-me).

Are you passing it?
http://<URL>&pageUpdate=its-me

[Rory Gillies]

Thanks John, I misunderstood that setting. I have now set it to 0 to disable the feature (this is an internal display only). All working well now except for the wind run issue.

[gjr80]

I had noticed some time ago that windrun had stopped updating, but had not gotten around to looking into the issue. Your post gave me the impetus to fix the issue. I've tracked the problem down to a subtle change, from quite some time ago, in how WeeWX calculates loop packet windrun. I have patched the rtgd code and have it running on my system without problem. I will package up a new release in the next day or so.

At the moment it is not possible to display average wind speed without altering the rtgd source code. Some time ago I did add the ability for the user to map different WeeWX fields/aggregates to any gauge-data.txt field; however, I did not implement the average aggregate. I've had a look at the rtgd source and implementing average should be straight forward. Let me see what I can do. 

Gary

[gjr80]

I've released v0.6.5 of the Realtime gauge data extension that should fix the zero windrun issue. The extension package can be downloaded from the Realtime gauge data extension releases page.

Gary

[Rory Gillies]

Hi Gary, that's great, thanks for the update. I replaced rtgd.py with version 0.6.5 and the wind run odometer is now working and updating. One issue remains, the wind run displayed on the odometer is different to that displayed on my current conditions page, could this be due to the way it is calculated or accumulated? My calculation uses $day.windrun.sum, looking through rtgd.py your calculation looks the same:

   'windrun': {
        'source': 'windrun',
        'aggregate': 'sum',
        'aggregate_period': 'day',
        'group': 'group_distance'
    },

Not sure why there should be such a difference, have a look at my live page: https://www.360shetland.co.uk/weather/live.html then compare it to the Current page. At the time of writing the odometer reads 216.9 while on the Current page it is reading 134.9, a difference of 82 miles.

Thanks,

Rory

[gjr80]

Rory,

There is a bug in the realtime gauge extension windrun unit conversion, the net result was that when specifying wind speed in mile_per_hour windrun was left as the km value rather than converted to miles. Display wise that meant your gauges show units of miles, but the value displayed is the km value. Fixed in v0.6.6, you can download the v0.6.6 package from the Realtime gauge data extension releases page.

Gary

[Rory Gillies]

That’s fixed it Gary, many thanks!

Happy New Year,

Rory

-- 
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/l5mTCp0_ZmY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1af1db9e-98a3-4dae-942c-3bb176c0684dn%40googlegroups.com.