Topic: WS-2000 Help

[Theo]

I just got my Raspberry Pi and am attempting to get weewx going.  I am VERY Linux knowledgeable and VERY WS-2000/Weather Stations unknowledgeable. 

I have a RPi 3+ with wifi and I am running CentOS on my Pi.  I have weewx installed and configured. 

From what I have gleaned, the way to interface with the WS-2000 is by capturing http calls from the WS-2000?  Is this the correct approach (I have pretty strong network controls and there is no easy way to promiscuously monitor traffic without adding more gear (or until I get my pfsense router set up)).

I see USB drivers, can I usb attach to the WS-2000 to pull data?

(I can't seem to get pycap installed, but tcpdump shows that I am not seeing any other traffic but mine in any event).

Any hints/tricks/direction on best way to get weewx working with my WS-2000 would be appreciated.

[galfert]

WeeWx needs the Interceptor driver. Then you need to create a separate hotspot on the Pi. The WS-2000 then connects to the Pi's Hotspot. Then WeeWx with the Interceptor driver can see and capture the network traffic intended for WU. I haven't personally done this but that's pretty much what I've read that others have done.

[Theo]

Thanks. I ended up using SDR with an antenna to capture from the Sensor Array, it is working pretty good so far.   

[galfert]

What SDR are you using?

Let us know about the experience and how you did it. What guide did you follow if any?

[Theo]

This post is a good place to start - http://www.wxforum.net/index.php?topic=35494.0

I am using rtl_sdr and rtl_433.  It was a bit of a struggle to get it up and running, but I have clear signaling from the Sensor Array (WH65B) and it is working well.  I have not solved the WH32B yet, I can see the WH31's, but the 32B does not show up on my SDR scan. 

I am happy to assist anyone trying this out on CentOS, as I found some things that needed to be done outside of the instructions.

[Storm017]

Did you scan around 915Mhz? Believe that is the frequency WH32B transmits at.

[Theo]

Yup, and I can see all of the other devices except the W32B.  I have more testing to do this weekend, but in the mean time I picked up a WS25, which is supported by RTL_433.

[Storm017]

When you say “I can see all of the other devices except the W32B”, do you mean that RTL_433 software is decoding all other sensors?  If you use “sdr console” or “gqrx”, do you actually see the signal and it is a not in the “grass” then one can assume RTL_433 software, as of the last revision, does not decode the W32B.

[Theo]

 Yes, I see the WH65B and all of my WH31Es without issue.  When I try to capture the WH32B and can decode the signal and RTL_433 generates an error when I remove and replace the battery.  One of the developers gave me some suggests as to what to try and I will be attempting to capture the data tomorrow.

[kbellis]

WeeWx needs the Interceptor driver. Then you need to create a separate hotspot on the Pi. The WS-2000 then connects to the Pi's Hotspot. Then WeeWx with the Interceptor driver can see and capture the network traffic intended for WU. I haven't personally don't this but that's pretty much what I've read that others have done.

Could you please post the link to the referenced article(s) more clearly describing the exact process?

[galfert]

WeeWx needs the Interceptor driver. Then you need to create a separate hotspot on the Pi. The WS-2000 then connects to the Pi's Hotspot. Then WeeWx with the Interceptor driver can see and capture the network traffic intended for WU. I haven't personally don't this but that's pretty much what I've read that others have done.

Could you please post the link to the referenced article(s) more clearly describing the exact process?

See the following thread and focus on Methods 2, 2.5 and 3.
https://www.wxforum.net/index.php?topic=34922.0

Also see the following regarding WeeWx Interceptor driver
https://github.com/matthewwall/weewx-interceptor/blob/master/readme

[kbellis]

Thanks George! I'll try and get in touch with Gregory.