Welcome to the Cumulus Support forum.

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Cumulus MX V4 beta test release 4.0.0 (build 4017) - 17 March 2024

Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

Http Ecowitt - polling interval and wind

From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

sutne
Posts: 372
Joined: Sun 14 Oct 2012 4:23 pm
Weather Station: HP2553 (WS80) and HP2564 (WS90)
Operating System: Raspbian Bullseye and Bookworm
Location: Rjoanddalen and Kronstad, Norway
Contact:

Http Ecowitt - polling interval and wind

Post by sutne »

My Ecowitt Hp2553 is set to upload data to CumulusMX each 20 s, same as interval in CMX.
But when enabling data logging I observe that data is uploaded at 28 and 56 s each minute.
My previous station logged to CMX each 5 s.
I observe that because of this the wind has general higher value than before.
Looking at the console the wind fluctate f.ex between 2 and 6 m/s, but CMX show mostly 5-6, probably because what is reported is the highest value the last 30 s.

Does anyone know why we cannot have interval down to 5s?

Code: Select all

 2021-11-28 09:46:28.093 ProcessData: Payload = PASSKEY=AFF35B8D5120ADB430A4CB3B06C9F2B2&stationtype=EasyWeatherV1.5.9&dateutc=2021-11-28+08:46:27&tempinf=68.7&humidityin=43&baromrelin=29.625&baromabsin=27.263&tempf=14.5&humidity=82&winddir=359&winddir_avg10m=355&windspeedmph=7.4&windspdmph_avg10m=10.3&windgustmph=16.3&maxdailygust=16.3&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=1.319&monthlyrainin=6.378&yearlyrainin=34.894&solarradiation=5.05&uv=0&wh80batt=3.08&wh25batt=0&freq=868M&model=HP2553AE_Pro_V1.7.6
2021-11-28 09:46:28.097 ProcessData: StationType = EasyWeatherV1.5.9, Model = HP2553AE_Pro_V1.7.6, Frequency = 868MHz
2021-11-28 09:46:28.107 ProcessData: Complete
2021-11-28 09:46:56.079 ProcessData: Processing posted data
2021-11-28 09:46:56.080 ProcessData: Payload = PASSKEY=AFF35B8D5120ADB430A4CB3B06C9F2B2&stationtype=EasyWeatherV1.5.9&dateutc=2021-11-28+08:46:55&tempinf=68.7&humidityin=43&baromrelin=29.622&baromabsin=27.260&tempf=14.7&humidity=81&winddir=359&winddir_avg10m=9&windspeedmph=9.2&windspdmph_avg10m=10.3&windgustmph=13.0&maxdailygust=16.3&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=1.319&monthlyrainin=6.378&yearlyrainin=34.894&solarradiation=5.05&uv=0&wh80batt=3.08&wh25batt=0&freq=868M&model=HP2553AE_Pro_V1.7.6
2021-11-28 09:46:56.083 ProcessData: StationType = EasyWeatherV1.5.9, Model = HP2553AE_Pro_V1.7.6, Frequency = 868MHz
2021-11-28 09:46:56.092 ProcessData: Complete
2021-11-28 09:47:00.303 Current CPU temp = 47.2°C
2021-11-28 09:47:28.402 ProcessData: Processing posted data
2021-11-28 09:47:28.402 ProcessData: Payload = PASSKEY=AFF35B8D5120ADB430A4CB3B06C9F2B2&stationtype=EasyWeatherV1.5.9&dateutc=2021-11-28+08:47:27&tempinf=68.7&humidityin=43&baromrelin=29.622&baromabsin=27.260&tempf=14.5&humidity=81&winddir=351&winddir_avg10m=350&windspeedmph=7.2&windspdmph_avg10m=10.3&windgustmph=11.4&maxdailygust=16.3&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=1.319&monthlyrainin=6.378&yearlyrainin=34.894&solarradiation=5.13&uv=0&wh80batt=3.08&wh25batt=0&freq=868M&model=HP2553AE_Pro_V1.7.6
2021-11-28 09:47:28.407 ProcessData: StationType = EasyWeatherV1.5.9, Model = HP2553AE_Pro_V1.7.6, Frequency = 868MHz
2021-11-28 09:47:28.418 ProcessData: Complete
2021-11-28 09:47:56.098 ProcessData: Processing posted data
2021-11-28 09:47:56.100 ProcessData: Payload = PASSKEY=AFF35B8D5120ADB430A4CB3B06C9F2B2&stationtype=EasyWeatherV1.5.9&dateutc=2021-11-28+08:47:55&tempinf=68.7&humidityin=43&baromrelin=29.634&baromabsin=27.272&tempf=14.4&humidity=82&winddir=350&winddir_avg10m=355&windspeedmph=7.4&windspdmph_avg10m=10.3&windgustmph=11.2&maxdailygust=16.3&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=1.319&monthlyrainin=6.378&yearlyrainin=34.894&solarradiation=5.21&uv=0&wh80batt=3.08&wh25batt=0&freq=868M&model=HP2553AE_Pro_V1.7.6
2021-11-28 09:47:56.105 ProcessData: StationType = EasyWeatherV1.5.9, Model = HP2553AE_Pro_V1.7.6, Frequency = 868MHz
2021-11-28 09:47:56.123 ProcessData: Complete
User avatar
philpugh
Posts: 380
Joined: Tue 24 May 2011 8:34 am
Weather Station: See Signature
Operating System: Debian 11 (RPi4)
Location: Antrobus, Cheshire, UK
Contact:

Re: Http Ecowitt - polling interval and wind

Post by philpugh »

Hi, A couple of questions

1/ What is your real time interval set to in CumulusMX?

It should be set to 20 secs to match the data rate to make more of the received data.

2/ Which wind value in CumulusMX are you using to make the comparison?

There are gusts, 10 min average at least. Note that the Ecowitt station reports 10 min average as well as gust wind speeds.
Phil Pugh
GW1000 + WH65/WH57/WH31; HP2551 + WS68/WH40A; GW2001 WittBoy
cumulusutils generating website
http://goosegate.uk/
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Http Ecowitt - polling interval and wind

Post by HansR »

@sutne: I had the same issue when switching to the Ecowitt sensor. My solution was to use the Speed for average calc: option in common options for the Station settings. Even though it is not a full 100% clear to me how that works internally, the result now matches my own physical observation (it now gives an average of 2 bf and non 4 bf. This is a difference not easy to miss).
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
sutne
Posts: 372
Joined: Sun 14 Oct 2012 4:23 pm
Weather Station: HP2553 (WS80) and HP2564 (WS90)
Operating System: Raspbian Bullseye and Bookworm
Location: Rjoanddalen and Kronstad, Norway
Contact:

Re: Http Ecowitt - polling interval and wind

Post by sutne »

1/ What is your real time interval set to in CumulusMX?
I thought the realtime interval only was for uploading to the web-site.
I am discussing the data seen from the local CumulusMx compared to the console.

HansR:
My solution was to use the Speed for average calc: option in common options for the Station settings.
I looked at those and unchecked them since it seems the HP2553 calculate it.
And the graph looks better now:
4FA73A00-3C34-4CF0-AA47-F2EC4ACDAC62.jpeg
You do not have the required permissions to view the files attached to this post.
sutne
Posts: 372
Joined: Sun 14 Oct 2012 4:23 pm
Weather Station: HP2553 (WS80) and HP2564 (WS90)
Operating System: Raspbian Bullseye and Bookworm
Location: Rjoanddalen and Kronstad, Norway
Contact:

Re: Http Ecowitt - polling interval and wind

Post by sutne »

Both ‘Calculate average wind speed’ and ‘Use wind speed for average calculation’ must be set, then the graph will be correct.

But nobody can explain why interval set to 20 s gives only 2 data transfer pr minute?
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Http Ecowitt - polling interval and wind

Post by HansR »

sutne wrote: Mon 29 Nov 2021 9:14 am Both ‘Calculate average wind speed’ and ‘Use wind speed for average calculation’ must be set, then the graph will be correct.
Right I have all calcs done by Cumulus so I thought you had that set too.... my bad.
sutne wrote: Mon 29 Nov 2021 9:14 am But nobody can explain why interval set to 20 s gives only 2 data transfer pr minute?
I am sure somebody can, it might even be hidden in the wiki somewhere ;)
No doubt an answer will appear sometime.
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Http Ecowitt - polling interval and wind

Post by HansR »

And looking at your logging again: we are talking about posted data. So the Ecowitt sends data to CMX which is only listening and probably won't process anything if it does not receive a message. Even if it had been set to 5 seconds. The Ecowitt must be the driving factor here.

So CMX is not asking, CMX is just waiting. Try varying the Ecowitt frequency and see what happens.
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Http Ecowitt - polling interval and wind

Post by HansR »

With my equipment (a GW1100 versus your HP2553) it does 20 seconds, a bit more, sometimes 21.
So the question is: could it be a device delay? I don't know what easyweather does, but are there some devices between before it sends to CMX. It needs to work the data for your local display doesn't it. 10 - 12 seconds seems a lot but you never know. You could try changing the Ecowitt transmit frequency and then see what happens.
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Http Ecowitt - polling interval and wind

Post by HansR »

And indeed: if I change the frequency on the GW1100 to 60 seconds, the CMX logfile does receive its payload message every 60 seconds. So CMX is listener to the Ecowitt device.

The delay from the 20 seconds (configured) to the 30+ seconds observed in your case must be an Ecowitt device delay. I would not worry about it too much, CMX picks up the messages and calculates correctly to the time it receives and logs the averages to the log frequency you have configured (mine is 5 minutes).
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
philpugh
Posts: 380
Joined: Tue 24 May 2011 8:34 am
Weather Station: See Signature
Operating System: Debian 11 (RPi4)
Location: Antrobus, Cheshire, UK
Contact:

Re: Http Ecowitt - polling interval and wind

Post by philpugh »

As I understand it the 'data transfers' from CumulusMX - that is logging data, updating databases etc - happens at the real time interval set in CumulusMX. The data arriving at CumulusMX from the Ecowitt doesn't trigger any of this processing. Mark recommended that I set my real time interval to 20 secs to match. It makes the data look more sensible?
Phil Pugh
GW1000 + WH65/WH57/WH31; HP2551 + WS68/WH40A; GW2001 WittBoy
cumulusutils generating website
http://goosegate.uk/
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Http Ecowitt - polling interval and wind

Post by HansR »

philpugh wrote: Mon 29 Nov 2021 10:48 am As I understand it the 'data transfers' from CumulusMX - that is logging data, updating databases etc - happens at the real time interval set in CumulusMX. The data arriving at CumulusMX from the Ecowitt doesn't trigger any of this processing. Mark recommended that I set my real time interval to 20 secs to match. It makes the data look more sensible?
I am not sure what realtime interval you are talking about now?
Do you mean the interval you setup at the FTP settings?

Then be aware that the FTP frequencies (realtime and file FTP frequencies) are not related to the device sampling interval which I discussed above (changing the 20 to the 60 seconds.

But to put them both to 20 seems reasonable yes.

And logging to the database is at a frequency you set to 1 min, 5 minutes, 10 minutes or whatever. The real values read by device are compressed to those values. (If I am wrong then correct me)
Last edited by HansR on Mon 29 Nov 2021 11:06 am, edited 1 time in total.
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Http Ecowitt - polling interval and wind

Post by HansR »

So there are different interval settings:
  1. Reading from the device (not configurable afaik)
  2. Writing to the logfile : Station=>general setting=>loginterval
  3. Writing to FTP on two frequencies: realtime and the FTP file frequency :
    • Internet Settings=>Interval Configuration=>Normal Interval)
    • Internet Settings=>Interval Configuration=>Real time Interval Settings
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
mcrossley
Posts: 12685
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: Http Ecowitt - polling interval and wind

Post by mcrossley »

As Hans has pointed out the HTTP protocol is a *sender* from your station, Cumulus just listens. Using the App to configure the station I believe 20 seconds is the minimum value you can set. Though using the API I believe it can be set lower.

Using the GW1000 protocol CMX will poll for data every 10 seconds unless you have an ultrasonic wind sensor when it polls every 4 seconds (the WS80 has an update rate of 4.75 seconds)
User avatar
HansR
Posts: 5870
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Http Ecowitt - polling interval and wind

Post by HansR »

I do have a ws80 (ultrasone) but I only see the 20 sec. Message appear in the cmx log. There is no 4 sec update. So why would you poll at 4 sec if the gw1100 only sends at the 20 sec frequency? Apart from that: cmx does not know i have a ws80, it only sees the gw1100 which assembles all data and sends it in one message to cmx.

It remains somewhat confusing that ecowitt :)
Hans

https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
User avatar
mcrossley
Posts: 12685
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: Http Ecowitt - polling interval and wind

Post by mcrossley »

The key part of my message was "Using the GW1000 protocol". That is the preferred way to communicate with a GW1000 as it has a full API that CMX uses, CMX can detect what sensors you have attached and actively polls for data rather than passively listening like the HTTP protocols.
Post Reply