Reading Weather Station data from a different subnet than the Hub is connected to

I’ll have the Hub connected to a Wifi router but my laptop (with Weather Display) is connected to a different network:

-->optic fibre --> ISP router---> WD laptop (Eth)
… . . . . . . . . . . . . . . . . . . . . . . . . . . .|---> Wifi router <--> WF Hub

Will this configuration work? I want WD to log the Hub’s data. Do I need to open some port on the ISP router? Or?

Thank you

UDP broadcasts do not cross IP subnet boundaries. WD will need to have a network interface of some sort on the same network as the WF Hub. Does the laptop have a wifi adapter that could connect to the same network as the WF Hub with a static IP address and no default gateway defined???

1 Like

@weather-display can confirm this, but my experience and understanding is that if you do not check the “use UDP data” box in the WD cronweatherflow component then WD will collect the data (and log it) from the WF backend from anywhere that has an Internet connection.

@vreihen is quite correct that if you want to log the UDP data stream directly then your logging computer must have an interface in the same network segment as the Hub since UDP broadcasts do not travel outside their local subnet.

1 Like

Laptop has a wifi adapter but the signal strength is weak at its location. I will need to move it to other place or extend the wifi range.
Thank you all for replies.

or by a small raspberry pi … cheap, doesn’t consume much energy and does the job perfectly

HI. yeah, you might need to extend the wifi range with a repeater if you want to get the UDP packets direct
(otherwise WD’s cronweatherflow program can get the data via a websocket from the WF cloud servers (as described above)

1 Like

Which software on RPi can work with WF? I could use one easily.

For now I use weewx but I tested Weather Display

both work, maybe there are others but those two are confirmed.

No real reason why I use one or the other … both can read the udp packages (weewx via a plugin you can find on this forum, WD is all inbuild …

I’d say, test both and pick the one you like most. WD (@weather-display) is tester and the weewx plugin coder (@vreihen) is tester aswell

happy testing :wink:

1 Like

By WD you mean a ConsoleWD, right? I don’t use a desktop release (Jessie for RPi) but ust a console.

in more linux distribs you have a pi version


You can also use this to capture and archive WeatherFlow UDP data.

indeed, so new I’m not yet used to it and I personally didn’t test it yet … soon

sorry Gary

Great, thanks all for feedback! I’ll also try to redirect the traffic on port 50222 to my different subnet. But I may give a RPi a try first.
I’m used to WD but my colleague uses a weewx with his station. I’m happy there are options. Also the default software seems to do a very good job!

I use both WeatherDisplay by Brian Hamilton on my MacBook and WFArchiver by Gary Funk on a Raspberry Pi 3b. Both are excellent for what I need to do. And both authors are WeatherFlow Field-Testers.

1 Like

You have the choice of changing your network by changing the subnet to a /23 or changing the Wi-Fi router to a Bridge.

Is there a reason you have the two segregated?

1 Like

I’ll set up a Sky (only) to a location without RPi or PC in the local wifi. Is there any other software I could use to read the data in another location similar to cronweatherflow ? I like WD but would only be logging wind, solar and rain. I’m also not sure WD would work without the Air (no pressure value).

I think you need a hub within RF range of the Sky, as the hub is what sends the data…

Yes, I will have one Sky and one Hub in location A and would like to log data in location B. I could probably do it with weatherdisplay but would like to avoid having a PC for this. WD is able to take data locally (within same network where Hub is) or remotely. It reads from the WF’s server I guess.

You can read from location B… as long as B has a HUB and it’s talking to the WF servers.

1 Like

I can imagine different scenario but all need coding skills. As you pointed out, Sky and Hub need to be used together as the Sky can not communicate to something else. Plus the hub pre processes data and you would loose all the benefit of it if it were direct communication with the Sky.

  • you use some UDP package grabber and store locally to a database that you push or pull to another server but you don’t have realtime

  • you use an UDP grabbing package and push it to a remote database (sql allows to store remotely even 10k miles away)

Some here on forum posted code on how to grab the UDP packages but from there you need to add whatever system you would like to achieve your goal. But in any case you will need a device (PI or even an small Arduino thing cold to it I think) to grab the data and push or pull the data across

the only other option is to go grab the data again from WeatherFlow servers via the API (links on in top menu)