Ideally, I'd like the GW1000 to transmit data as and when an RF packet is received. That's what my ambient weather ObserverIP does.
I'd like to revisit this point regarding the ObserverIP. What exactly are you saying that the ObserverIP does??? The ObserverIP is inferior to the GW1000 in just about every way possible. Are you talking about the ObserverIP's Live Data page? That is what I think you are talking about. The ObserverIP Live Data page does refresh quite frequently from what I remember. This data though is just for viewing pleasure and I suppose you could use one of the scripts that scrape this page for data. This is a poor method of getting data as it overwhelms the ObserverIP and it crashes often. The GW1000 with its local network API is superior. I understand that perhaps this Live Data page on the ObserverIP could get you quicker data. But if the question is about getting quicker data to some software then you can use one of the various 3rd party software packages with the GW1000 and you'll gain much better results. The "Customized" server upload feature of the GW1000 is limited to upload every 16 seconds and perhaps you can request that this limitation be changed and that would be a firmware upgrade on the GW1000 and other consoles with this feature.
Yes, the GW1000 is way more interesting than the ObserverIP, which is why I bought one in the first place.
What the ObserverIP does do well, however, is report RF-data as soon as it's received. So for instance w/ a WH24 that reports every 16s and a WH31 that reports every 60s, the ObserverIP reports to weather underground 4x per minute (3x for each WH24 update, once for the WH31). Hope that makes sense. If it supported the WS80, I'm pretty sure it would push out a report every 5s to my weewx interceptor (aka "customized" on the GW1000).
So just to be absolutely clear: for both the ObserverIP and GW1000, I'm only interested in their push abilities, not in their local web server (ObserverIP) or WSView polling (GW1000).
I figured out how to configure the ObserverIP via telnet to report to my WeeWX instead of Weather Underground years ago and that works great.
And yes, the customized server upload feature on the GW1000 is what I'm talking about:
[ You are not allowed to view attachments ]
I may still get a WS80 even w/ the current limitations, but having the GW1000 push out all the wind data would be awesome.
Yes, I'm aware. Though you're mistaken on the upload intervals, when configuring a custom weather service, the reporting interval is one of the settings that is configured, along w/ IP/Port/Path/Protocol.
Okay you are more clear now. But I did mention that "Customized" server upload is limited to 16 seconds as a minimum and that this could be a requested change in the GW1000 firmware, or maybe it is WS View that is acting as the limiter of valid configuration to send to the GW1000.
There are other ways to get data. If you use Cumulus MX for example it uses a different means for getting data from the GW1000 that is more instantaneous. The crutch that you are experiencing stems from the limitation of the "Customized" server upload and its 16 second limit. WeeWX is in the process of being updated to support the GW1000 API instead of needing to rely on the "Customized" server upload feature. Then WeeWX will be able to query for data as frequently as it wants....just as other software that currently uses the API can....like Cumulus MX, Meteobridge, and Weather-Display.
That said your point is valid. You don't need to mention WS80 to Ecowitt. The simple request you basically have is that they change the "Customized" server upload feature to allow for less than 16 seconds as an upload interval. The WS View is just a means of getting to the GW1000 settings. Perhaps though it is WS View that prohibits sending the configuration of less than 16 seconds to the GW1000.
For my setup, the push configuration is way more interesting, because it simplifies deployment (don't need an extra piece of hardware on the same network polling the GW1000).
The GW1000 also has a firmware update bug when it's being used w/ a polling service, that'd be another reason to just use push instead.
For reference, here's the error about 16s-600s:
[ You are not allowed to view attachments ]
And not mentioning the WS80... That ship has sailed
However if any of you are interested in the same feature, send an email to support@ecowitt.com asking them to lower that limit from 16s to 5s