meteohub.de

I would like to know if I have something configured wrong or if this is just the way it is supposed to be.....

VP2 / Meteobridge 3.1 (Oct 20 2016, build 10630), FW 1.3 / D-LINK DIR-505 REV. A1 / WeatherLinkIP Hardware:111 Firmware:112 Bootware:101 / WU & CWOP uploaded via the MB

This is regarding using the WeatherLink program...

When I have WeatherLink running, if I use the MB's IP to connect, WU & CWOP upload correctly but the upload to weatherlink.com from the WLIP stops.

When I have WeatherLink running, if I use the WLIP's IP to connect, the upload from the WLIP to weatherlink.com continues, but the upload to WU & CWOP stop.

Is this how it is or might I have something configured wrong?


Thanks

That is the reason you can select timeouts, when the MB allows the WLIP to upload to weatherlink. This switch is next to the selection of the Davis Vantage as weather station.

This behavior is with a timeout selected: < IP (WL upload 1 min) >.

works for all the other users. please check twice.

I have checked many, many times with the same results.

I downloaded Cumulus today and have the same results with it as well until I tried its "Discon period" setting. Setting it to 5 seconds makes it works properly. Unfortunately, WeatherLink has no such setting.

I have also redone the setup, rebooted the MB, VP2, router and my PC many times with no change. I have also read every post I can find pertaining to WLIP and MB repeatedly.

Are you willing to log in remotely to see if you can spot what I am doing wrong?

Here is my WL config - is it correct? (The Remote IP Address listed is the IP address of the MB)

Here is my WL config - is it correct? (The Remote IP Address listed is the IP address of the MB)

No that is not correct. The WL remote IP address is either the public address of the WLIP logger or the DNS, it has nothing to do with the MB IP.

Thanks for the info Mattk.

I tried that and opened port 22222 on my router and was able to connect to the WLIP with WeatherLink.

It gave me the same results as using the WLIP's LAN IP - upload to weatherlink.com continues, but MB stops uploading to wunderground and CWOP. Close WeatherLink and all works fine.

No that is not correct. The WL remote IP address is either the public address of the WLIP logger or the DNS, it has nothing to do with the MB IP.

In my setup it is correct - In Weatherlink software I have to put in the ip of the MeteoBridge and the same in the Virtuel Weather Station. But I don't have a WeatherLink Ip but a WeaterLink USB.

Do you really mean that one has to use the public ip of the connected internet-service? If the Weatherlink Ip-device is behind a router it wont have a public ip. And why would one use dns-adress as ip? A DNS (http://www.webopedia.com/TERM/D/DNS.html) is something your ISP supply's so you can look up hostnames, nothing will happens if you try to connect to it.

Regards

droiddk wrote:

No that is not correct. The WL remote IP address is either the public address of the WLIP logger or the DNS, it has nothing to do with the MB IP.

In my setup it is correct - In Weatherlink software I have to put in the ip of the MeteoBridge and the same in the Virtuel Weather Station. But I don't have a WeatherLink Ip but a WeaterLink USB.

Do you really mean that one has to use the public ip of the connected internet-service? If the Weatherlink Ip-device is behind a router it wont have a public ip. And why would one use dns-adress as ip? A DNS (http://www.webopedia.com/TERM/D/DNS.html) is something your ISP supply's so you can look up hostnames, nothing will happens if you try to connect to it.

Regards

The MB is configured with the IP of WLIP, if the logger is a USB then we would be talking a different page (different scenario) based on selecting the USB button not the TCP/IP button. In TCP/IP mode the Remote IP address (as opposed direct cabled to a local mode) is typically the Public IP of the device which does change and which can be found at the bottom of the My Device window in the Weather My Account.

As the Public IP is a changing value then anybody can set up a managed DNS (such as Dyn DNS) with a host name of their choice (that does not change) that will track this changing public IP. This hostname (URL) can then be used to remotely access a station and/or logger. This remote connection is typically used for accessing remote stations as opposed to local connected stations with the remote IP/DNS being that of the router which forwards port 22222 to the IP of the logger.