Cumulus Support

Having a bit of a re-vamp of my CumulusMX system, my ISP is stopping FTP / Web page as part of my broadband package, so I have set up a new Windows 2022 server and will be hosting it myself. As part of that I moved my CumulusMX folder from my existing server onto the new, and once it was running I upgraded to the latest version 3.26.0 (build 3248). Turned off FTP upload, and set up local copy, and got the locally hosted web page up an running.

That was a few days ago, today (not sure why I hadn't noticed before) I was looking at the wind speed chart, and noticed that the wind gust looked totally different to what it used to look like, rather then the blocky look it was like a bar chart up and down all over the place.

Started to look at settings, and then suddenly remembered that I hadn't allowed port 22222 through the firewall (I have a WLL), so I enabled that and the wind guest was back to what I remembered.

However while looking at the settings I noticed that "Calculate average wind speed" was ticked. Now thinking that didn't need to be ticked for a WLL I turned it off, however the Wind Speed line then seemed to flat line at the value it was on. Put the tick back on and the line moved again, turned the tick off, and again the wind speed line flat lined. I have highlighted this in yellow on the below chart.
For reference, my other instance of CumulusMX (on the same PC) pointing at the Davis Console (Via a Meteobridge) shows a moving line at the same time as the flat line.
Is this expected behaviour of the WLL. Do I need to have "Calculate average wind speed" ticked, or do I have a setting wrong somewhere, or is this a bug.

Ian.

You do need to keep the calculate average speed ticked (for now anyway).

The WLL does not send any average speed values in the broadcast data.
It does send various averages in the "current data", but that only updates once a minute.

For now, if broadcast traffic is being received, MX will use that to calculate the average (each time you start MX it enables that option) and ignore the 1 minute updated values in the current data.

If broadcast traffic is not being received, then it will fall back to using the WLL provided average from the current data.

However, your "choppy" gust graph when broadcasts were not being received does not look right and I'll investigate that. But the good news is that the average looked fine!

Ok. Makes sense. Thanks.

I am running Cumulus MX with a WLL and have the same issue any time broadcasts stop being received. I have attached a screenshot of my wind chart from today, and as you can see, this was occurring for nearly the entire day. If you open the Cumulus dashboard while this is happening, the reported gust value is always equal to the current wind value, ie. it does not seem to remember/use the 10-min gust value at all. You'll see things like an average wind speed of 11 gusting to 3.

I have found the bug and fixed it for the next release