meteohub.de

Hi

Just picked up a WS-2000 the other day and I am currently trying to connect to my meteobridge running on my RPi and am having no luck getting the two to "talk" to each other. On my Ambient console I have set the following:

State "Enabled"
Protocol Type "Same As AMBWeather"
IP/Hostname 192.168.xx.xxx
Port "80"
Interval "60 second"
Path "/public/ecowitt0.cgi"


I have included a screen shot of my station tab and log hoping that might be helpful. As a side note, I have also tried a couple variations of the IP/Hostname: http://192.168.xx.xxx as an example and have also tried a couple variations of the path name in addition to adjusting the interval.

System info is below:

System
Platform: Raspberry Pi 3 Model B+
RAM: 941 MB total, 817 MB free (13% used)
Storage: WD SLC, 29.3 GB total, 26.9 GB free (8% used, 3766.9 yrs)
SW Version: Meteobridge 5.4 (Jul 16 2022, build 2583), FW 1.3
Uptime: 0 hours, 54 minutes Buffer: 2 items (0%)

Quick note, when browsing to http://meteobridge-ip-address/public/ecowitt0.cgi the page response is FAILED.


Thanks
g

1. the IP/Hostname to configure in the WS View app, awnet app or inside the console is the IP address ONLY - no http etc. in front
2. your issue may be that Ambient consoles like the WS-2000 console due to their (Ambient's) proprietary firmware do not use Ecowitt protocol for the custom server but Ambient protocol which is unfortunately different from the Ecowitt protocol - and the Meteobridge (MB) driver is made for Ecowitt protocol afaik.

One way to circumvent this would be to install the FOSHKplugin on your RPi which can (amongst many other things - it's an information broker) convert the Ambient protocol into Ecowitt protocol and forward the converted format to Meteobridge.
This hasn't been tested yet as MB comes with its own operation system and usually makes it difficult to install other software except MB.
(I could try/test it, when I find the time, but such "solutions" are not really welcome by the MB developer - and they may need some special precautions and processes to be in place covering the MB update procedure.)

If you have a 2nd RPi (or NAS), you could run it (FOSHKplugin) there and forward the outcome to your MB RPi. This version has been tested and works perfectly.
However, all pretty complex ... - if you want to go down this road ....

The easiest way to make it work would be getting yourself an Ecowitt GW1100 console/hub/gateway, very small piece, matchbox-size, for about 35 USD. It can also receive (in spite of proprietary firmware) the WH65 outdoor array of the WS-2000 - AND you can connect MB to the GW1100 directly (as GW1000). It is usually available in the U.S. via amazon.com, but seems to be out-of-stock right now. You can order it from Ecowitt directly (shipping time 10-14 days): https://www.ecowitt.com/shop/goodsDetail/107#
Make sure you order the 915 MHz variant which matches your outdoor array.

That's a solution many users of Ambient WS-2000 or WS-5000 stations use.
You can find more information regarding the topic in general (and in more detail) at: wxforum.net
- the Ambient, Ecowitt, Fine Offset board is: https://www.wxforum.net/index.php?board=111.0
- the thread describing my proposed solution is: https://www.wxforum.net/index.php?topic=37760.0
- you also find the FOSHKplugin thread in the same board as a sticky thread
- the basic (MUST READ) thread also explaining about Ambient's proprietary firmware on FineOffset hardware is:
https://www.wxforum.net/index.php?topic=40730.0

So, a lot to study - but it's worth it

never mind the model name/number GW1000 - it's the predecessor model of the GW1100 - the functionality is identical

Hi

Thanks for the info, a lot of stuff to digest. Per the Meteobridge release page it specifically mentions the Ambient WS-2000 being supported so I was hoping for “plug and play” solution.

I will look at the links you provided and checkout FOSHKplugin as I do have an extra RPi that I used to spoof the Acurite sever when they went belly up a few years back. Hopefully the learning curve will not be to steep. At least I am comfortable with meteobridge since I have been using since 2014…always good to learn something new.

Thanks again
g

hymrog wrote: ↑Sun Jul 17, 2022 12:54 pm Hi
Thanks for the info, a lot of stuff to digest. Per the Meteobridge release page it specifically mentions the Ambient WS-2000 being supported so I was hoping for “plug and play” solution.

I'm not sure Boris is/was aware of the differences in the protocol - I think he assumed that they both send the same data via custom server, which is true for the WU protocol, but not for the Ecowitt protocol. I might be wrong and he has considered the differences, but how would his software know how to tell one from the other ....???

I'm also using CumulusMX (CMX) which supports now the custom server. There you have three different choices: WU, Ecowitt and Ambient.
I used FOSHKplugin ß-testing CMX some time ago for "faking" an Ambient console.

The nice thing with FOSHKplugin is that you can make up 100 (was 50 earlier) forwards to different receivers with and without conversions ...
like this you can send data in Ecowitt format to Meteobridge and e.g. also to PWT (Personal Weather Tablet) repurposing an old Android tablet ...

If you want to see what your console posts, you can use the EAR service of the FOSHKplugin author: http://ear.phantosoft.de
see also https://www.wxforum.net/index.php?topic=43041.0

Hi -

Thanks for the tip regarding the FOSHKplugin software (very feature packed)...worked like a charm. Too bad that you still need the "middle-man" to send the data to the meteobridge but not too big of a deal...I did learn something new today which is always good.

Maybe Boris will update to allow the use of WS-2000 with the Ambient protocol.

Thanks again
g

Gyvate wrote: ↑Sun Jul 17, 2022 1:51 pm I'm not sure Boris is/was aware of the differences in the protocol - I think he assumed that they both send the same data via custom server, which is true for the WU protocol, but not for the Ecowitt protocol. I might be wrong and he has considered the differences, but how would his software know how to tell one from the other ....???

So far Meteobridge did assume that all "ecowitt protocols" are the same between all the various clones around. If someone can point me to the differences WS-2000 introduces, I will try to reflect this in an upcoming version.

admin wrote: ↑Mon Jul 18, 2022 12:21 pm

Gyvate wrote: ↑Sun Jul 17, 2022 1:51 pm I'm not sure Boris is/was aware of the differences in the protocol - I think he assumed that they both send the same data via custom server, which is true for the WU protocol, but not for the Ecowitt protocol. I might be wrong and he has considered the differences, but how would his software know how to tell one from the other ....???

So far Meteobridge did assume that all "ecowitt protocols" are the same between all the various clones around. If someone can point me to the differences WS-2000 introduces, I will try to reflect this in an upcoming version.

They are the same for all clones - except for the Ambient FOSHK clone consoles, as they are posting to their own weather network, ambientweather.net (while Ecowitt/FOSHK clone consoles post to ecowitt.net) - and for this they use a different protocol from the ecowitt protocol, the Ambient format. And this then applies also to the custom serer functionality. They also have their own app, the awnet app.
@admin: Please see your mail @smartbedded.com

Hi

I see there was an update today regarding the WS-2000 reporting issue. Just gave it a go and no luck. Wondering if you could review again.

Edit: Tried to go back to using the FOSHKplugin but it seems to no longer work after updating to the latest meteobridge version which included support for the WS-2000.

Platform: Raspberry Pi 3 Model B+
RAM: 941 MB total, 811 MB free (13% used)
Storage: WD SLC, 29.3 GB total, 26.8 GB free (8% used, 3766.9 yrs)
SW Version: Meteobridge 5.4 (Jul 18 2022, build 2587), FW 1.3
Uptime: 18 hours, 54 minutes Buffer: 1 items (0%)

Thanks
g

Probably what we call in my mother tongue "imbadprovement" - trying to improve and ending up worse.
I suggested to create a separate driver for the Ambient models - which should have avoided the breakdown of both interfaces ...
Let's see - it will take a bit longer

I just made the code a bit more tolerant to WS2000 specifics. I would wonder if that has broken something. If so, can someone give me a hint, what exactly is no longer working?