Fine Offset WH-2650 and weewx

[Massimiliano Neri]

Hi, I just bought a WaldBeck Halley WH-2650, basically a clone of the WH-2650 Fine Offset, can you tell me how to configure weewx.conf to intercept its data string?

I thank you in advance.

[kan6526]

--------------------weewx.conf ------------------

[Interceptor]

    driver = user.interceptor

    device_type = observer

    mode = sniff

    iface = eth0

    pcap_filter = src 192.168.2.252 and dst port 80

----------------------------------------------------------------------

my WH2950 ip:192.168.2.252

[Massimiliano Neri]

Hi Kan6526.

I having the Wh-3650 instead of the console I have a wifi receiver. I connect this receiver with the ws-view app to my ASUS home router.
the weewx software I installed it in a little orange pi zero that turns a debian distribution.
Now here is my doubt, why should I declare eth0 on the line of the configuration of the observer if the receiver does not have the ethernet port?
Can you tell me that you are using to run weewx?

[kan6526]

Hi  Massimiliano Neri

about pi zero ,You can refer to this .

< Can you tell me that you are using to run weewx?

I am very happy to tell you anything, as long as you can accept my bad English. :D

Weewx installed on PC , it is NAT gateway server. (192.168.2.10)

ws-view app setup WH2950-----------> WIFI home router (DHCP client ) ----------->Linux server (eth0:192.168.2.10) ----->PPP0 ---------->internet

you have observer Should be simpler.

[Massimiliano Neri]

I did a search with a port scanner. The observer basically does not have a door 80 or any other door. I saw a post in this group made by Tanwe Hyalin, but I did not understand how he ran the wh2650 station. in your opinion how was it configured?

Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha scritto:

[Tanwe Hyalin]

I have mine configure like this:

weewx.conf

[Interceptor]
    driver = user.interceptor
    device_type = observer

    port = 666

And to redirect the traffic to that port I edited /etc/firewall.user in my router and added the following:

iptables -t nat -A PREROUTING -s 192.168.1.103 -p tcp --dport 80 -j DNAT --to-destination 192.168.1.6:666
iptables -t nat -A POSTROUTING -j MASQUERADE

[Massimiliano Neri]

Thank you Tanwe Hyalin .

Can I know what router do you have? 192.168.1.103 is the ip bridge observer in dhcp mode?

Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha scritto:

[kan6526]

192.168.1.103   is WH-2650 bridge

 

192.168.1.6   is weewx pi

[Tanwe Hyalin]

Exactly.

I also gave both WH2650 and pi a static IP.

My router is a TL-WR1043ND flashed with Gargoyle, https://www.gargoyle-router.com/

[Massimiliano Neri]

The latest WH-2650 interfacing tests with weewx seem to work all the same even if I have to complete some tests, however there are still problems.

For the tests I used a "tp-link tl-wa701nd" where I installed the Gargoyle firmware, connected the "Orange Pi Zero" through its WiFi, connected to the tp-link also the bridge of the WH-2650, made the changes that Tanwe Hyalin told me at /etc/firewall.user.

On Orange Pi Zero I installed weewx and the "interceptor" extension, configuring the software according to the specifications given in previous posts.

Made all this works perfectly.

As I said before some problems remain, and I can not find the part of the iptables in my main router ASUS RT-AC68U, I entered ssh mode but I can not see where I can enter the changes to the firewall.

Does anyone have any ideas? I did not want to put another router to handle the WH-2650 weewx and the bridge.

Soon I would like to try again, install the OpenWRT image on the small Orange Pi Zero, install weewx inside OpenWRT, make the firewall changes and connect the bridge directly to the Orange Pi Zero OpenWRT in order to have everything on one device .

As soon as I have completed the tests, I postpone my conclusions.

Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha scritto:

[Massimiliano Neri]

The latest WH-2650 interfacing tests with weewx seem to work all the same even if I have to complete some tests, however there are still problems.

For the tests I used a "tp-link tl-wa701nd" where I installed the Gargoyle firmware, connected the "Orange Pi Zero" through its WiFi, connected to the tp-link also the bridge of the WH-2650, made the changes that Tanwe Hyalin told me at /etc/firewall.user.

On Orange Pi Zero I installed weewx and the "interceptor" extension, configuring the software according to the specifications given in previous posts.

Made all this works perfectly.

As I said before some problems remain, and I can not find the part of the iptables in my main router ASUS RT-AC68U, I entered ssh mode but I can not see where I can enter the changes to the firewall.

Does anyone have any ideas? I did not want to put another router to handle the WH-2650 weewx and the bridge.

Soon I would like to try again, install the OpenWRT image on the small Orange Pi Zero, install weewx inside OpenWRT, make the firewall changes and connect the bridge directly to the Orange Pi Zero OpenWRT in order to have everything on one device .

As soon as I have completed the tests, I postpone my conclusions.

Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha scritto:

[Tanwe Hyalin]

I'm a bit confused about your setup, you are using 2 routers? How is everything connected? I know that there's community firmware for the Asus RT-AC68U, Asuswrt-Merlin, so maybe that could be an option if the standard firmware does not give you access to iptables. I'm not sure but the interceptor driver can also be used in sniffer mode, as per kan6526 suggestion, thus no modifications to iptables should be required.

My setup is like this, my raspberry pi (raspbian, weewx, interceptor driver) and bridge are connected (via wifi) to the router TL-WR1043ND (running gargoyle firmware), at this router I placed the two lines mentioned before in iptables, the correct place for that on the gargoyle/openwrt firmware is /etc/firewall.user. These two lines redirect the traffic leaving from port 80 of the bridge to the ip of the raspberry pi, at the pi the redirected traffic enters at port 666 were the interceptor driver is waiting for it.

[Massimiliano Neri]

Yes, I did this test to verify everything and it works. But I have the ASUS RT-AC68U router and there is not or at least I do not find any iptables. For the moment I would not replace the original firmware with the AsusWRT-Merlin, since I have two routers of the same model with AiMesh, and replacing it then I do not know if it works well. However I am doing further tests. I've already tried the sniffer method and weewx crashes, but as I told you I'm still running tests. I'll let you know.

Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha scritto:

[Massimiliano Neri]

Tanwe Hyalin I have the problem of absolute and relative pressure that is sent by the string on wunderground, in fact there are two entries "baromin" inside the string, one of absolute pressure and the other of relative pressure. I'm using the Meteotemplate extension to send data to my portal with this template and unfortunately it presents the absolute pressure and not the relative pressure. do you know how I can solve the problem?

Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha scritto:

[Tanwe Hyalin]

I modified th file interceptor.py as per https://github.com/matthewwall/weewx-interceptor/issues/28 to fix this issue.

[Massimiliano Neri]

Can you tell me the exact line on the code of the interceptor.py? File. in fact, after the driver version change the number of lines no longer corresponds. I installed the latest version of the driver. is it possible that matthewwall fixes the file directly?

Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha scritto:

[Tanwe Hyalin]

I changed line 1048 in the interceptor.py file from "if software_type == 'WH2600GEN_V2.2.5':" to "if software_type == 'WH2600GEN_V2.2.5' or software_type == 'WH2650A_V1.2.1':" so it could identify our firmware.

[steep...@gmail.com]

Hello Tanwe and Massimiliano,

I have been following this thread with interest. I too have the WaldBeck Halley WH-2650 which I have recently purchase as a backup for my main station.

I have connected it to Weather Underground, Weather Cloud and Met Office with no problems so I know that data streams are being generated and reaching their target. However when I do a network scan with TCPflow, it detects no data flow or any open ports. I am using the interceptor.py and it set up to sniff in observer mode and no interception is happening. I have followed all the suggestions made apart from IP Tables as I cannot install an appropriate firmware on my router to enable this. I am at a loss to see where to go next. Do you have any more ideas that I could pursue?

Regards

Ian

[Tanwe Hyalin]

I haven't used the sniffer mode with the WH2650 so take this with a grain of salt, our bridge is exclusively wifi as such if your router has an option called "Isolation mode" enabled it could hide the device from the interceptor so the first thing I would try would be that, disabling that feature, if that does not work, honestly I don't think there's much you can do besides getting a device to intercept the bridge, either a small router  or rasperry pi/orange pi zero just for this purpose. Again the ideal situation would be for a driver that could mimick the WS View app and grab the weather data directly from the station, that why I shared the source code for the app. While I'm slowly analysing the source, I doubt I will be able to create a driver capable of doing that (not enough time or technical skills with network comunication protocols).

[Massimiliano Neri]

Hello Steep...

I am testing myself to make it work, and I managed to do it even if I have to refine the iptables to make the installation cleaner.
The bridge of this weather station does not have a built-in webserver, so if you do a port scanner I would not find any available port anymore you have to connect it via wifi to the router and it does not have an ethernet connector.
However, no fear, it is more difficult to configure it with weewx than other weather stations, but it works well once connected with this software.
The IPTABLES rules listed by Tanwe are important to make it work, the port 80 you see in the rule is an interception that directs on another port that you choose and that is available to do the iptables.
I personally am configuring the weewx software with the interceptor driver, directly on an Orange Pi Zero for $ 10.
Orange Pi Zero has Ubuntu's Bionic image installed, and I've set up the small mini PC to serve as a HotSpot, and then connect the WH-2650 bridge directly to the Orange.
So in my case the bridge does not connect to the home router but to the mini PC where weewx also runs, and only the Orange Pi is connected to the router via ethernet cable.
I created thanks to Tanwe's information on the routes of the iptables and the station works, but as I mentioned you are to refine, in fact if I use the app of the smartphone that is connected to the Orange via wifi, the app itself can not find the bridge device. Of course, the station was connected to the hotspot before I made the rules.
Apart from this detail, everything seems to work, so if you need information, I can tell you where you came from the configuration.

Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha scritto:

[steeple ian]

Hello Massimiliano,
,

Thank you for you feedback. I have a spare Raspberry Pi 3 which I can utilise. I will set it up this evening with the version of Linux you are using, If you can guide me from that, I will be very pleased.

Regards,

Ian

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[steeple ian]

Hello Tanwe,

I am looking into my router but I suspect that the isolation mode is disabled by default anyway.

Regards,

Ian

--

[steeple ian]

The most recent version of Ubuntu for RaspberryPi is 16.04, so I have installed Debian 9 (Stretch) instead.

[Tanwe Hyalin]

Even disabling isolation mode, grabing wifi traffic is not trivial as it requires a wifi card that has that capability, using the standard ethernet is a lot easier and less prone to issues, unfortunately we don't have that luxury with our bridge.

I'm not sure about all configurations that have to be made to the PI to make it act like a router, but from a cursory look on google there's a couple of tutorials that should help you on that task, on the plus side, by using the pi as router + installing weewx on it you shouldn't need nothing else to send the weather data to wherever you want.

[Massimiliano Neri]

Ian can tell you how I did with the distribution of Ubuntu that you can find on the www.armbian.org site for Orange Pi Zero. I do not know how to set it on the raspberry by not having it. I have always used various types of Orange cards.

If you can set up your raspberry as a hotspot, I can list the procedures for installing iptables and the rest of the configuration.

Hoping it is more or less identical.

Il giorno venerdì 23 novembre 2018 00:11:49 UTC+1, Massimiliano Neri ha scritto:

[steeple ian]

Massimiliano,

I have tried two options on my RaspberryPi,  Openwrt or creating a Wi-fi access point. Of the two I think the access point is the way to go. If you could direct me from that standpoint I will be very grateful. The OS I am using is Raspbian Stretch, a Debian version for ARM.

Regards

Ian

Sent from my iPad

--

[Massimiliano Neri]

Yes, yes, I chose to do a HotSpot with my Orangepi Pi Zero H2.

As an operating system I chose Armbian Bionic mainline kernel 4.14.y, which can be found at this link:

https://www.armbian.com/orange-pi-zero/

I have done this procedure to install the weewx and the driver interceptor:

1) Launched on the command line "armbian-config", set the time zone, the keyboard and the language, find all this under the heading 'Personal'.

2) return to the main menu and go to "Network", select 'IP' and assign a static address to the network card eth0 (mine is 192.168.10.66) save and run on reboot.

3) restart "armbian-config", go to 'System' and install the beta version packages with the voice 'Nightly', then restart.

4) run the command line command 'apt-get update' and 'apt-get upgrade'.

5) run on the command line "armbian-config", go to 'Network' and activate your access point with the 'HotSpot' entry.

6) install weewx from the documentation found on the program website: http://www.weewx.com/

7) install the extension for weewx "interceptor" following the indications you find on this link: https://github.com/matthewwall/weewx-interceptor

8) Connect your smartphone with the Orange Pi access point (your case with the Raspberry), install the "WS View" app that you find in the google app store, open the app itself and with this colleague the WH-2650 weather station bridge to the access point of the used device.

Check that the station emits on your wunderground account that you should have created and always configured with the same with "WS View".

Before moving on with "Ws View", you need to calibrate the sensors of the station or make the setting operations you believe.

9) Now at the command line of Orange Pi Zero, type: "iptables -t nat -A PREROUTING -s 172.24.1.65 -p tcp --dport 80 -j DNAT --to-destination 192.168.10.66:666", where 172.24.1.65 is the ip of the station bridge and 192.168.10.66 is the ip of the Orange Pi eth0 network card. the final door 666 you could choose it as you want, as long as it is not occupied.

Clearly you have to replace the example ip with your ip that you will soon have discovered with a program of scanning the ports (there are also for smartphones, and I suggest you install one from google play).

Save the configuration of this iptables with the command:

iptables-save> /etc/iptables/iptables.ipv4.nat

This last one is used to load the typed iptables every time, every time the Orange is turned on.

To verify that the iptables command has been loaded, type:

iptables -t nat -L --line-numbers

This displays all the iptables of your card, and you should also find the one that directs your weather bridge on the eth0.

10) open the weewx.conf file at the command line by typing:

nano /etc/weewx/weewx.conf

Scroll to the end of the file and set the [Interceptor] section with these lines:

[Interceptor] 

    driver = user.interceptor

    device_type = observer

    port = 666

The [[Wunderground]] section should be set up with your account:

[[Wunderground]]

        # This section is for configuring posts to the weather

        Underground.

        # If you wish to do this, set the option 'enable' to true,

        # and specify a station (e.g., 'KORHOODR3') and

        password.

        # To guard against parsing errors, put the password into

       quotes.

  enable = true

  station = XXXXXXX

  password = YYYYYYY

Save the edited file with CTRL + O.

11) Restart weewx with the command:

/etc/init.d/weewx restart

If the Raspberry is the same as my Orange Pi Zero, you should see the WH-2650 data on wunderground and weewx.

Greetings from the MAX.

[steeple ian]

Hi Massimiliano and Tanwe,

I have got it working by replicating the OrangePi hotspot set up on a RasberryPi. I am letting it stabilise for a few days before I transfer the hotspot setup to my public facing server. I will post a link when it is up and running.

Thanks for all your help. Would never had made this far so quickly without your help.

Cheers,

Ian

[Massimiliano Neri]

Perfect Ian ...

I refer an error to the directory path of the file 'iptables.ipv4.nat'

The original location of the file on Orange Pi Zero with Armbian Bionic is '/etc/iptables.ipv4.nat', so the command to save the added iptables is:

iptables-save > /etc/iptables.ipv4.nat

Remember to check the exact location in your raspberry or another linux distribution of the iptables.ipv4.nat file.

[steeple ian]

Yes I had worked that one out. In Debian 9 it is '/etc/iptables/rules.v4'.

I now  have to replicate everything on my main server which is an Intel NUC, just hoping there is a suitable driver for the wifi antenna on that device.

Thanks once again for your help.

Cheers,

Ian

--

[steeple ian]

Hi Massimiliano and Tanwe,

Here is the finished article https://claydonsweather.org.uk weeWX, weather34 template, web server, web cam and wi-fi hotspot all running perfectly on an Intel NUC/Debian 9 combination. Seems very solid so far. Had to re-calibrate pressure in weeWX as the WH2650 was running high compared to my other station and surrounding stations. All the dynamic charts (links under the panels) are running off .csv data generated from the weeWX database using the Cheetah templating engine.

Best regards,

Ian

[Massimiliano Neri]

very nice weather portal ... you're a big one :-)

[Massimiliano Neri]

Hello. I would like to modify the sensor map of a WH-2650 on the Interceptor driver, so that the internal sensor placed on a solar screen acts as an external thermo-hygrometer sensor. Clearly the external sensor of the wh-2650 must be redirected as an internal sensor or at most must return null values.  Any idea of ​​how to do it? have you already changed the sensor map of the Interceptor?

[mwall]

On Tuesday, December 18, 2018 at 9:09:45 AM UTC-5, Massimiliano Neri wrote:

Hello. I would like to modify the sensor map of a WH-2650 on the Interceptor driver, so that the internal sensor placed on a solar screen acts as an external thermo-hygrometer sensor. Clearly the external sensor of the wh-2650 must be redirected as an internal sensor or at most must return null values.  Any idea of ​​how to do it? have you already changed the sensor map of the Interceptor?

you should be able to specify the sensor map in the [Interceptor] stanza in your weewx configuration file.

[Interceptor]

    outTemp = temperature_out

    inTemp = temperature_in

take a look at the Observer section of interceptor.py to see what the default sensor_map is for that station type (i assume that you are using the observer as the device_type)

m

[Massimiliano Neri]

Hello Matt

Yes I'm using the observer as a device-type.

As you can see from the attached photo, the WH-2650 weather station has a sensor that independent of temperature, humidity and atmospheric pressure.

This sensor is usually placed inside the house, and clearly the external sensor package already contains a thermohygrometer sensor, but according to some, in the summer months by readings of some degree higher than normal, due to inadequate solar screen.

Now this is the idea, ie insert the sensor for indoor, inside a solar screen to make it an outdoor sensor.

For this I would like to map the weewx to collect the internal temperature and humidity data, and insert these values into the external temperature and umidity  variables.

I am attaching a track intercepted by the observer:

[Massimiliano Neri]

Hi Matt. I have mapped these values ​​as the following example:

[Interceptor] # This section is for the network traffic interceptor driver. # The driver to use: driver = user.interceptor # Specify the hardware device to capture. Options include: # acurite-bridge - acurite internet bridge # observer - fine offset WH2600/HP1000/HP1003, aka 'observer' # lw30x - oregon scientific LW301/LW302 # lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge device_type = observer port = 666 [[sensor_map]] outTemp = temperature_in outHumidity = humidity_in

But I found that the other values ​​such as pressure, rain etc etc are no longer sent. Do I need to write the whole map again? Or how can I solve the problem?

[mwall]

On Wednesday, January 2, 2019 at 11:34:03 AM UTC-5, Massimiliano Neri wrote:

I have mapped these values ​​as the following example:

[Interceptor] ... [[sensor_map]] outTemp = temperature_in outHumidity = humidity_in

But I found that the other values ​​such as pressure, rain etc etc are no longer sent. Do I need to write the whole map again?

yes.  something like this:

[[sensor_map]]

    pressure = pressure

    barometer = barometer

    outHumidity = humidity_in

    outTemp = temperature_out

    windSpeed = wind_speed

    windGust = wind_gust

    windDir = wind_dir

    windGustDir = wind_gust_dir

    radiation = radiation

    dewpoint = dewpoint

    windchill = windchill

    rain = rain

    rainRate = rain_rate

    UV = uv

    txBatteryStatus = battery

m

 

[Massimiliano Neri]

Hi Matt.

I solved with this map:

 [[sensor_map]]

        pressure = pressure

        barometer = barometer

        outHumidity = humidity_in

        inHumidity = humidity_in

        outTemp = temperature_in

        inTemp = temperature_in

        windSpeed = wind_speed

        windGust = wind_gust

        windDir = wind_dir

        windGustDir = wind_gust_dir

        radiation = radiation

        dewpoint = dewpoint

        windchill = windchill

        rain = rain

        rainRate = rain_rate

        UV = uv

        txBatteryStatus = battery

Unfortunately I read the specifications of the indoor sensor in question, and the temperature has a range of only 0 - 60 degrees Celsius.

So unusable for outdoor.

Thanks for your help.