|
|||||||||||||||||||||||||||||||||
Supported sensors:
|
|||||||||||||||||||||||||||||||||
Announcement
Collapse
No announcement yet.
Ecowitt PWS - Local Official protocol
Collapse
This is a sticky topic.
X
X
-
Ecowitt PWS - Local Official protocol
Tags: None
- Stuck
-
Originally posted by jim@beersman.com View PostThe Ambient Weather WS-2000 and WS-5000 console have the ability to send to local just like the Ecowitt GW-1000 device. Just slight differences in the format between the two. In the latest Ambient Weather AWNET (4.2.9) tool the configuration is identical to that of the Ecowitt WS View app
WS2000 and WS5000 doesn’t share the same protocol as GW1000, so you are not able to fetch the data via TCP connection. The main reason is that GW1000 wifi OSC chip handles data reception and wifi bridge feature by the same processor. However with WS2000 and WS5000, the data handling was done on the display controller side, and it just pass the data to wifi for sending to the weather server.
So their structure is not the same. We will have more devices with GW1000 feature coming: WN1900 – a station with display, WH2680, GW1100 new gateway are supporting this feature.
Comment
-
Technically they are correct in the awnet app it's listed as Ambient Weather Protocol and the Ecowitt is listed as Ecowitt Protocol. But in reality they are almost identical with only the difference being the names of some of the devices and the order of the header information. I have been using this method of pulling data for more than a year to gather data from my WS-2000.
Comment
-
For Ecowitt I am talking to the GW1000 which does not have a screen but is their communication hub. And with Ambient Weather the Screen is the communication hub and that is what is sending the data both to the Ambient Weather Hub and to my Custom App via a telnet connection. When I get a chance I will send you data sample from both devices so you can see the differences. (Currently middle of the night here monitoring an upgrade of systems at work)
Comment
-
To my knowledge AmbientWeather has not provided a documented protocol to their local data access. In fact it is just with the most recent awnet app update that you could even configure the console to send local. But you could cheat and use the Ecowitt WS View app to enable the AmbientWeather console to send local for some time, that is how I discovered it was possible. Like I said I can send you a copy of the data stream but I have no Official protocol documentation.
Comment
-
Originally posted by alexbk66 View PostI know how to communicate with GW1000, I have protocol documentation from FOSHK (the manufacturer). But if you can point me to the AmbientWeather local protocol, I can also implement it.
http://download.ecowitt.net/down/sof...n=EasyWeather2
The link below is to the Weather Exchange forum, and post 27 contains a an Ecowitt Protocol Simulator
https://www.wxforum.net/index.php?to...5964#msg415964
This is the parent thread for Fine Offset clones and note there is a whole thread identifying that not all AmbientWeather are made by Fine Offset
https://www.wxforum.net/index.php?board=111.0
Comment
-
Thanks guys for your info. As I said, I do have official Ecowitt documentation and full set of Ecowitt sensors from Fine Offset, the only problem is that this documentation looks like google translate from Chinese, but I mostly worked it out and already added local Ecowitt support to my AKWeather plugin (almost finished).
And for AmbientWeather I did get reply that they only have Cloud API, which I also added to my plugin.
And regarding "unofficial" APIs - I don't really like bothering with unofficial stuff which can break any time. I prefer convincing the manufacturer, doesn't always work though
Comment
Comment