Any plans to support Meteobridge

Hi Brian,

I didn’t have (enabled) checked off along with (use with meteohub). The meteohub data access: line just keeps repeating. Also when starting WD a current status windows pops up. Getting missed data. Just keeps saying increase time.

This is what I’m getting now under debug info:

Doing checking of time zone calculation
Daylight saving in use
Loaded all time records
Date /time (PC) that WD was last running is: 06/19/2015 16:43:00
converted to UTC Date /time that WD was last running is: 20150619204300
getting missed data initial 20150619204300 20150619204400
[10061] Connection refused
[10061] Connection refused
[10061] Connection refused
[10061] Connection refused
[10061] Connection refused
[10061] Connection refused
Doing checking of time zone calculation
Daylight saving in use
meteohub data access:->http://192.168.29.246:1/meteolog.cgi?mode=data&type=xml&start=20150619205900&end=20150619210000
[10061] Connection refused

Vinny

Hi
the problem is the [10061] Connection refused
error
are you sure you have the port number set correct?

The command used is invalid. There should be no port (or the default port 80) specified

http://192.168.29.246/meteolog.cgi?mode=data&type=xml&start=20150619205900&end=20150619210000

But this is a METEOHUB command not supported by Meteobridge.
And as Meteobridge has no storage for detailed weather-data I think it can not accept a timeframe for historical data anyway either.

Meteobridge WiKi: http://meteobridge.com/wiki/index.php/Add-On_Services
The correct meteobridge url should be
meteobridge:[email protected]/cgi-bin/livedataxml.cgi
which returns data such as:

<logger>
  <TH date="20150622151420" id="th0" temp="14.7" hum="90" dew="13.1" />
  <T date="20150622151432" id="t1" temp="25.0" />
  <TH date="20150622151432" id="th1" temp="25.0" hum="0" dew="25.0" />
  <TH date="20150622151432" id="th10" temp="14.4" hum="48" dew="0.0" />
. . . shortened . . . 
 <WIND date="20150622151459" id="wind0" dir="221" gust="1.3" wind="1.8" chill="14.7"/>
 <RAIN date="20150622151432" id="rain0" rate="0.0" total="187.0" delta="0.0"/>
 <THB date="20150622151436" id="thb0" temp="21.6" hum="40" dew="7.4" press="1002.0" seapress="1006.7" fc="0"/>
</logger>

The Meteohub command as used above returns similar data but a little different, no quotes and no proper end />

<logger>
  <THB date=20150622152950 id=thb0 temp=23.1 hum=49 dew=11.8 press=1002.2 seapress=1006.3 fc=0>
  <TH date=20150622152938 id=th0 temp=14.6 hum=88 dew=12.6>
  <T date=20150622152950 id=t1 temp=25.0>
  <TH date=20150622152950 id=th1 temp=25.0 hum=0 dew=25.0>
  <TH date=20150622152912 id=th10 temp=14.4 hum=48 dew=0.0>
 . . .  shortened . . . 
  <SOL date=20150622152936 id=sol0 rad=265>
  <RAIN date=20150622152950 id=rain0 rate=0.0 total=230.4 delta=0.0>
  <WIND date=20150622152946 id=wind0 dir=224 gust=0.9 wind=1.8 chill=14.6>
  <DATA date=20150622152928 id=data1 val=2660309.00>
  <DATA date=20150622152928 id=data3 val=0.73>
  <DATA date=20150622152928 id=data2 val=1.00>
</logger>

I hope this helps a little bit,

Wim

the IP setup should not contain the port number
just the IP only
as WD adds the port number
so maybe that is the problem there

I never added the port number in the ip address. 1 was selected by default
and is the only com port available according to WD. I just put 192.168.29.246
with 0 and also backed spaced 0 out but WD keeps adding 0 back in. I also tried
Wim van der Kuil’s ip suggestion.

192.168.29.246
meteobridge:[email protected]/cgi-bin/livedataxml.cgi
[email protected]/cgi-bin/livedataxml.cgi

all above ip’s lead to this in debug info:

getting missed meteohub data 20150624182400 20150624182500
OK
Not Found
OK

and a rapidly flashing message that cannot be read because it is flashing to fast.
I have to unckeck enabled and restart WD. Then on restart with enabled unchecked
under debug info:

getting missed meteohub data 20150624182400 20150624182500
OK
Not Found
OK
( connected OK to com port 1 ) only appears under debug info after enabled is
unchecked and WD is restarted.

I ran Advanced port scanner.
Under 192.168.29.246 ports (scanned 67 of 67, opened:3 closed:64)
open ports (3)
22 open (ssh)
53 open (domain)
80 open (www-http)
closed ports (64)
0 - 21 closed
23 - 52 closed
54 - 79 closed
81 - 65535 closed

Vinny

Hi
the not found error points to the IP address not being correct somehow
can you post a screen shot of the com port setup , meteobridge setup?
also have you tried build 81?
thanks

I also sent the settings files.


that port number being set to zero will be problem

I only tried 0 because the default 1 would give the same error. 1 is the only port available according to WD.

how do you mean only 1 according to WD?
the port number is often like 80 or 8080

The port you should use is 80
You can select that by using the scroll bars or type the value.
At least that can be done at my version 81.

Wim


wd.jpg

com/ip port
comm port setup
com port 1 selected by default and only port shown as available

Please bear with me on this not understanding this at all. Apparently I’m confusing com port and port numbers.
I only looked under comport number because of the info under debug info.

getting missed meteohub data 20150623182900 20150623183000
OK
Not Found
OK
connected OK to com port 1

As for using port 80, this is what I get with port 80 under debug info

ip address vp/vue ip data logger
meteobridge:[email protected]/cgi-bin/livedataxml.cgi

port number
80

ip address vp/vue ip data logger
192.168.29.246

port number
80

under debug info with both above settings

getting missed meteohub data 20150623182900 20150623183000
OK
Not Found
OK
connected OK to com port 1

I have the latest build installed. Port 80 was the original setup and didn’t work.

ip address vp/vue ip data logger
meteobridge:[email protected]/cgi-bin/livedataxml.cgi

port number
80

ip address vp/vue ip data logger
192.168.29.246

port number
80

under debug info both scenarios above

getting missed meteohub data 20150623182900 20150623183000
OK
Not Found
OK
connected OK to com port 1

Vinny

I think it can work. The xml packages are quite similar.
Only Meteobrisdge needs a userid:password@ before the ip-address. Meteohub does not need that.

As I said Meteobridge does not support historical data. It has no memory, as only Meteohub has local memory to store historical data.
So the message “Not found” is the logical conclusion WD for the missing historical data. But they can also be missing for other reasons, so WD will be used to stations not supplying missing data.

Then it connects again to the Meteobridge using WD-internal-port1 (which, i think, is connected to => 192.168.29.246:80)

So what happens after “connected OK to com port 1”

The question is: Is there any data arriving in WD ? Is the dashboard showing data for temperature and so on?
If it does not show any data, try to add that userid:password@ part before your 192.168.29.246 and see if the data is shown then.

And very soon Brian will wake up again on the other side of the globe to help you further.

Wim

Nothing happens with connected OK to com port 1. No data on the main screen but on the bottom of
the main screen data received green is showing receiving data and data quality is green.

Meteobridge does support historical data. Tolerated age of data and save historical data are options
under select station. I installed meteobridge on a d-link dir-505. Tolerated age of data and save
historical are both set to 10 minutes.

The last 4 lines of the debug info below just keep repeating until I uncheck enabled. meteobridge is the
username but password is not I just substituted it for this post. Below is what shows in debug info.

getting missed meteohub data 20150624114300 20150624114400
OK
Not Found
OK
OK
Not Found
OK
Error with TCP/IP Socket connection
OK
Not Found
OK
OK
Not Found
OK
OK
Not Found
OK
Error with TCP/IP Socket connection
OK
Not Found
OK
OK
Not Found
OK
OK
Not Found
OK
Error with TCP/IP Socket connection
OK
Not Found
OK
OK
Not Found
OK
OK
Not Found
OK
Error with TCP/IP Socket connection
OK
Not Found
OK
OK
Not Found
OK
OK
Not Found
OK
Error with TCP/IP Socket connection
OK
Not Found
OK
OK
Not Found
OK
OK
Not Found
OK
Error with TCP/IP Socket connection
OK
Not Found
OK
OK
Not Found
OK
OK
Not Found
OK
Doing checking of time zone calculation
Daylight saving in use
meteohub data access:->http://meteobridge:[email protected]/cgi-bin/livedataxml.cgi:80/meteolog.cgi?mode=data&type=xml&start=20150624202600&end=20150624202700
OK
Not Found

Vinny

meteohub data access:->http://meteobridge:[email protected]/cgi-bin/livedataxml.cgi:80/meteolog.cgi?mode=data&type=xml&start=20150624202600&end=20150624202700

The port number is in the wrong place in that string, and I don’t think it will take that start/end stuff. The meteobridge manual page for grabbing data is here.

connected OK to com port 1
ignore that...that is refering to a com port not an IP port since the meteobridge does not have any memory, then go to control panel, data logger, and turn the switch off there then restart WD so that it does not try to get history data on start up and only live data then the problem might be that need to add in user/pass to the query?

I turned off the data logger and restarted WD. Getting missed meteohub data still pops up
on start up and in debug info. How would I enter my username and password with the url.

I entered as Wim suggested:
meteobridge:[email protected]/cgi-bin/livedataxml.cgi
meteobridge is the username I substituted password for the real password

Per the manual page I linked above that’s the correct way to send the username/pw.

I will check on if the data logger switch is off, still trying to get history data and apply a fix and get back to you