Page 2 of 3
Re: Http Ecowitt - polling interval and wind
Posted: Mon 29 Nov 2021 9:32 pm
by Phil23
The other thing that comes into play here is the reporting intervals of that actual sensors back to the HP2551 or GW1000.
As in:-
Code: Select all
WS68 16.5
WH69 16
WS80 4.75
WH31 61
WH32 64
They vary quite a bit & may appear to be all over the shop, but that's to try & avoid sensors tramping on each others transmissions.
If they all reported at the same interval & two drifted into sync, it would otherwise take a while for them to drift apart again.
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 10:55 am
by sutne
And the HP2551/3 does not use the same protocol as GW1000\1100?
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 11:19 am
by HansR
sutne wrote: ↑Tue 30 Nov 2021 10:55 am
And the HP2551/3 does not use the same protocol as GW1000\1100?
What did you setup? (btw: the GW1000 differs from the GW1100)
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 11:53 am
by sutne
I use Ecowitt HTTP as station in CMX.
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 12:30 pm
by HansR
OK, so that means that the protocol is the same and works as the GW1100 (the GW1000 is different).
The argument of the push by Ecowitt / poll by CMX holds too for your device.
If CMX missed a poll it will wait 10 seconds (see Marks post), apparently that is the case in your situation where you have 30 second intervals.
If you switch datalogging on, you will see the actual message received from the Ecowitt by CMX.
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 1:22 pm
by mcrossley
sutne wrote: ↑Tue 30 Nov 2021 10:55 am
And the HP2551/3 does not use the same protocol as GW1000\1100?
No, those station only support the HTTP Ecowitt (and Wunderground but forget that) protocol. They do not support the GW1000/1100 API (GW1000 station type) required for polling.
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 1:25 pm
by mcrossley
There is a possibility that I could add an option to the HTTP Ecowitt station set-up to set a fast update time (say 4 seconds) rather than the Applet's minimum of 20 seconds.
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 2:10 pm
by sutne
HansR:
If CMX missed a poll it will wait 10 seconds (see Marks post), apparently that is the case in your situation where you have 30 second intervals.
If you switch datalogging on, you will see the actual message received from the Ecowitt by CMX.
The minimum in the console is 16 s. I set it to 16 and had 3 polls pr minute in the beginning, but then it was quickly down to 2, at 00 and 44 every minute. That is looking at Station update in the Dashboard.
Enabling Data logging shows that data is acquired at 00, 16 and 44. But I never see 16 in the Dashboard.
Mark, are you interested in a log file with more logging, or is this something I just have to accept?
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 3:27 pm
by mcrossley
If you are using the HTTP station then it is entirely driven by your station, there is no polling, Cumulus just sits and waits for the data to be sent to it. So I doubt the logs will show anything of interest - unless the station is sending unexpectedly formatted messages, in which case you would be seeing errors in the log.
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 7:13 pm
by sutne
Then again I have to ask: when the MxDiag log shows the HP2553 is sending 3 times each minute,
Why do the Dashboard in the local CMX interface only show 2 station updates per minute?
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 7:48 pm
by mcrossley
What updates twice a minute?
CMX updates the console data for every message received, the "Last station update" will be updated every time a message is received.
Re: Http Ecowitt - polling interval and wind
Posted: Tue 30 Nov 2021 9:44 pm
by sutne
What updates twice a minute?
On the Dashboard in the Local time box, the Last Station update is only updated twice a minute, at 00 and 44 sec.
But the MxDiag log shows this every minute:
Code: Select all
2021-11-30 15:00:16.688 ProcessData: Processing posted data
2021-11-30 15:00:16.689 ProcessData: Payload = PASSKEY=AFF35B8D5120ADB430A4CB3B06C9F2B2&stationtype=EasyWeatherV1.5.9&dateutc=2021-11-30+14:00:16&tempinf=57.9&humidityin=47&baromrelin=29.451&baromabsin=27.089&tempf=19.4&humidity=90&winddir=36&winddir_avg10m=21&windspeedmph=3.6&windspdmph_avg10m=6.0&windgustmph=5.4&maxdailygust=19.2&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=6.378&yearlyrainin=34.894&solarradiation=3.79&uv=0&wh80batt=3.12&wh25batt=0&freq=868M&model=HP2553AE_Pro_V1.7.6
2021-11-30 15:00:16.692 ProcessData: StationType = EasyWeatherV1.5.9, Model = HP2553AE_Pro_V1.7.6, Frequency = 868MHz
2021-11-30 15:00:16.704 ProcessData: Complete
2021-11-30 15:00:28.192 SFTP[Int]: Uploading daily graph data files
2021-11-30 15:00:28.192 SFTP[Int]: Done uploading daily graph data files
2021-11-30 15:00:28.192 SFTP[Int]: Uploading Moon image file
2021-11-30 15:00:28.666 SFTP[Int]: Done uploading Moon image file
2021-11-30 15:00:44.690 ProcessData: Processing posted data
2021-11-30 15:00:44.690 ProcessData: Payload = PASSKEY=AFF35B8D5120ADB430A4CB3B06C9F2B2&stationtype=EasyWeatherV1.5.9&dateutc=2021-11-30+14:00:43&tempinf=57.9&humidityin=47&baromrelin=29.448&baromabsin=27.086&tempf=19.4&humidity=90&winddir=43&winddir_avg10m=25&windspeedmph=4.3&windspdmph_avg10m=5.8&windgustmph=5.4&maxdailygust=19.2&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=6.378&yearlyrainin=34.894&solarradiation=3.79&uv=0&wh80batt=3.12&wh25batt=0&freq=868M&model=HP2553AE_Pro_V1.7.6
2021-11-30 15:00:44.694 ProcessData: StationType = EasyWeatherV1.5.9, Model = HP2553AE_Pro_V1.7.6, Frequency = 868MHz
2021-11-30 15:00:44.708 ProcessData: Complete
2021-11-30 15:01:00.196 Current CPU temp = 45.1°C
2021-11-30 15:01:00.608 ProcessData: Processing posted data
2021-11-30 15:01:00.608 ProcessData: Payload = PASSKEY=AFF35B8D5120ADB430A4CB3B06C9F2B2&stationtype=EasyWeatherV1.5.9&dateutc=2021-11-30+14:00:59&tempinf=57.9&humidityin=47&baromrelin=29.448&baromabsin=27.086&tempf=19.4&humidity=90&winddir=37&winddir_avg10m=25&windspeedmph=3.8&windspdmph_avg10m=5.1&windgustmph=5.4&maxdailygust=19.2&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=6.378&yearlyrainin=34.894&solarradiation=3.79&uv=0&wh80batt=3.12&wh25batt=0&freq=868M&model=HP2553AE_Pro_V1.7.6
2021-11-30 15:01:00.610 ProcessData: StationType = EasyWeatherV1.5.9, Model = HP2553AE_Pro_V1.7.6, Frequency = 868MHz
2021-11-30 15:01:00.617 ProcessData: Complete
2021-11-30 15:01:16.514 ProcessData: Processing posted data
2021-11-30 15:01:16.514 ProcessData: Payload = PASSKEY=AFF35B8D5120ADB430A4CB3B06C9F2B2&stationtype=EasyWeatherV1.5.9&dateutc=2021-11-30+14:01:15&tempinf=57.9&humidityin=47&baromrelin=29.448&baromabsin=27.086&tempf=19.4&humidity=90&winddir=41&winddir_avg10m=25&windspeedmph=3.8&windspdmph_avg10m=5.1&windgustmph=5.4&maxdailygust=19.2&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=6.378&yearlyrainin=34.894&solarradiation=3.71&uv=0&wh80batt=3.12&wh25batt=0&freq=868M&model=HP2553AE_Pro_V1.7.6
2021-11-30 15:01:16.518 ProcessData: StationType = EasyWeatherV1.5.9, Model = HP2553AE_Pro_V1.7.6, Frequency = 868MHz
2021-11-30 15:01:16.532 ProcessData: Complete
2021-11-30 15:01:21.220 Realtime[58]: Start cycle
2021-11-30 15:01:21.221 Realtime[58]: Creating realtime.txt
2021-11-30 15:01:21.223 Realtime[58]: Processing realtime file - realtimegauges.txt
2021-11-30 15:01:21.233 Realtime[58]: Processing extra file[1] - /home/pi/CumulusMX/web/realtime-xT.txt
2021-11-30 15:01:21.257 Realtime[58]: Processing extra file[2] - /home/pi/CumulusMX/web/realtimetagsT.php
2021-11-30 15:01:23.440 Realtime[58]: End cycle
2021-11-30 15:01:44.505 ProcessData: Processing posted data
2021-11-30 15:01:44.506 ProcessData: Payload = PASSKEY=AFF35B8D5120ADB430A4CB3B06C9F2B2&stationtype=EasyWeatherV1.5.9&dateutc=2021-11-30+14:01:43&tempinf=57.9&humidityin=47&baromrelin=29.451&baromabsin=27.089&tempf=19.2&humidity=90&winddir=32&winddir_avg10m=25&windspeedmph=5.1&windspdmph_avg10m=4.9&windgustmph=6.0&maxdailygust=19.2&rainratein=0.000&eventrainin=0.000&hourlyrainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=6.378&yearlyrainin=34.894&solarradiation=3.71&uv=0&wh80batt=3.12&wh25batt=0&freq=868M&model=HP2553AE_Pro_V1.7.6
2021-11-30 15:01:44.510 ProcessData: StationType = EasyWeatherV1.5.9, Model = HP2553AE_Pro_V1.7.6, Frequency = 868MHz
2021-11-30 15:01:44.525 ProcessData: Complete
2021-11-30 15:02:00.224 Current CPU temp = 45.1°C
The reason I started looking at this was because the HP2553 showed the wind fluctating between 2 and 3 m/s and occasionally having gusts at 5 -6 m/s updating each 4 sec but the wind gauge on the CMX dashboard was steady between 5-6 and very seldom updating.
It got better when I checked the Average wind by CMX boxes, but I got curious why it was seldom updating.
Re: Http Ecowitt - polling interval and wind
Posted: Wed 01 Dec 2021 11:30 am
by mcrossley
That is odd because the second last thing CMX does before the "ProcessData: Complete" message is output is set the station update time to "now". The dashboard then updates every 3 seconds and pushes that time to your browser. So you should from that log snippet see the "Last Cumulus update" time update every 3 seconds, and the "Last station update" time update at xx:00 xx:16 and xx:44
Really odd that the station does not push every 16 seconds as requested. Maybe try setting it 20 seconds which is a divisor of 60 and see if you get three updates a minute?
Re: Http Ecowitt - polling interval and wind
Posted: Wed 01 Dec 2021 4:01 pm
by sutne
I do not have access to the console now, but it was originaly set to 20 s and then I had 2 Last station update pr hour, with 28 and 32 s intervals.
Re: Http Ecowitt - polling interval and wind
Posted: Thu 02 Dec 2021 4:47 pm
by mcrossley
I had a play around with my GW1000 and set it to 16 second updates (the minimum on that too - limited by the app).
It actually sends data regularly every 17 seconds, but unlike your console it sends the messages starting at whenever the config is set rather than on the minute. I think the random time is better as processing takes place on the minute for logging and rollover etc.
It reset it to 20 seconds and it sends data every 21 seconds. So it looks like somebodies arithmetic is off in the GW1000 firmware!
So your odd message times would seem to be down to some weird stuff happening in the console. I'd report it and see if it ever gets fixed in a future firmware update.