Will Weewx work with Lacrosse 330-2315?

[Boston Tom]

This a a relatively new product release from Lacrosse.  Does anyone know if Weewx is compatible with the hardware?

[mwall]

On Wednesday, September 20, 2017 at 8:12:12 PM UTC-4, Boston Tom wrote:

This a a relatively new product release from Lacrosse.  Does anyone know if Weewx is compatible with the hardware?

since the 330 series sends directly to weather underground, you should be able to use the weewx-interceptor driver to capture data.

https://github.com/matthewwall/weewx-interceptor

m 

[Boston Tom]

Thanks Matt, Yes I have been using your interceptor driver for a while now on my GW1000U Lacrosse bridge and it works great!  I bought this new lacrosse model and want to retire my old equipment and start feeding data from this new set-up.  I can't configure any DNS settings on my comcast router, so I am trying to figure out which option to set on the interceptor driver to capture the traffic.  Any suggestions?  I changed the device type to "observer", but when I add the IP of the lacrosse 330-2315 (address = 10.0.0.32), I get an error message in the weewx status report.  No luck leaving the device type as "lacrosse-bridge either.

[mwall]

On Friday, September 29, 2017 at 1:00:52 PM UTC-4, Boston Tom wrote:

Thanks Matt, Yes I have been using your interceptor driver for a while now on my GW1000U Lacrosse bridge and it works great!  I bought this new lacrosse model and want to retire my old equipment and start feeding data from this new set-up.  I can't configure any DNS settings on my comcast router, so I am trying to figure out which option to set on the interceptor driver to capture the traffic.  Any suggestions?  I changed the device type to "observer", but when I add the IP of the lacrosse 330-2315 (address = 10.0.0.32), I get an error message in the weewx status report.  No luck leaving the device type as "lacrosse-bridge either.

the device type should be 'observer'

the ip address is the address that the interceptor listens (or sniffs) on, so it should be the ip address of the computer on which weewx is running.

you have a few options:

a) hijack dns so that the weather station sends to weewx instead of weather underground

b) configure the weather station to send to the ip address of the computer on which weewx is running (is it possible to configure the weather station?)

c) run the interceptor in listen mode.  this can be tricky, but when it works it is rock solid.  the computer on which weewx is running must be able to see network traffic from the weather station.  that means one of these:

c1) the weewx computer must see wireless traffic (but wifi must not have encryption)

c2) the weewx computer must bridge the weather station - two network ports on the weewx computer, one to the weather station or router/switch/access-point upstream from the weather station, and one to the network's regular router/switch

d) run packet capture on the edge router and feed that into the interceptor

since you have no control over the router, you could only do (a) or (d) by inserting your own router between your network and the comcast router.  (imho, this is usually a smart thing to do, especially given the shenanigans that at&t, comcast, verizon, and other isp are prone to do).

(c1) is an easy one if it works, but i've had mixed luck sniffing wifi packets.  sometimes it just works, sometimes you only see your own traffic.  i don't have the mojo to know why.

in lieu of that, you might have to run weewx on a computer that bridges your network and the comcast router, then do (c2).

(b) is probably the easiest, but you'll have to probe the station to see if it has an http-accessible configuration.  or it might have a usb/sd card that has its configuration.

m

[Boston Tom]

No joy on the options you reccomended.......that I am capable of performing.....my skills are not high. 

I'm running weewx on an RPI.  I'm thinking of setting up the RPI as a wifi access point and directing the traffic from the weather station to the pi (instead of to the main router like it is now).  Do you think that has any chance of success? 

[vince]

On Saturday, September 30, 2017 at 11:19:27 AM UTC-7, Boston Tom wrote:

No joy on the options you reccomended.......that I am capable of performing.....my skills are not high. 

I'm running weewx on an RPI.  I'm thinking of setting up the RPI as a wifi access point and directing the traffic from the weather station to the pi (instead of to the main router like it is now).  Do you think that has any chance of success? 

Lean toward you're unlikely to succeed if your skills are indeed not high (as you put it).

A few things:

• you 'really' need some kind of residential gateway box between your network and the Comcast router.  Really.  Don't rely on them being either secure nor correct.
• if you have any kind of router/gateway box (prices can be $40-$150+) you 'will' have control over your DNS and your DHCP
• I'd always lean against turning wifi encryption off (c1 in matthew's list) 
  

Almost any kind of router/gateway box will support you controlling DHCP any way you want.  You could statically set up the weather station, or setup DHCP on the router side to provide the answer you want the weather station to get.

But get a router box no matter which way you go.

[mwall]

On Saturday, September 30, 2017 at 2:19:27 PM UTC-4, Boston Tom wrote:

No joy on the options you reccomended.......that I am capable of performing.....my skills are not high. 

I'm running weewx on an RPI.  I'm thinking of setting up the RPI as a wifi access point and directing the traffic from the weather station to the pi (instead of to the main router like it is now).  Do you think that has any chance of success?

yes.  the pi will then be a bridge between wifi and wired, so you just have to make the interceptor sniff on the wifi interface.

start by making the pi a bridge - there should be plenty of guides for doing that.

once that works, just configure the interceptor in sniff mode as explained in the weewx-interceptor readme

m 

[Boston Tom]

Success!

Pi was configured as a wireless access point,

Traffic was directed from the weather station to the pi (access point) by using the "Weather Connect" app via iPhone. 

driver = user.interceptor

    device_type = observer

    mode = sniff

    iface = wlan0

    pcap_filter = src 10.0.0.23 and dst port 80

Where "wlan0"= Pi configured as wifi access point and "10.0.0.23" is the IP address of the weather station on the network

Makes me wonder if I could have just sniffed this off the comcast router in the first place.  I will do more testing and report. 

Tom

[Alberto Sánchez]

Is it possible to do the same with Oregon WMR500?

Thanks.

[mwall]

Perhaps. It probably needs a little adjustment to recognize the soil and particulate sensors.

Please post some of the network traffic from the weather station.

m

[Alberto Sánchez]

I have not yet purchased the Oregon WMR500 station. A friend of mine was thinking of buying it, because the price is very good. And seeing this post is likely to work with the same driver, if I have a chance to test it I will post it and inform you.

[alex lalmant]

Hi,

i've an OREGON WMR500 station. I made a port scan and i found that this station use port 80 (for firmware and encoder firmware upgrade) port 7000, 7001, 9001. I'dont have a software who can see which traffic is send through this ports. So maybe this port can help.