meteohub.de

My set-up is:
WMR100 - Meteohub - WD - WDLive

My WMR100 has additional sensors. I can get the additional sensor information to WDLive as extra sensors but I really want to replace the main units outside temp/hum with that of one of the additional sensors.

It would be nice if we could change which sensor meteohub sends data out to WD as the outside temp/hum, like we can on the weather networks page.

Hope that makes sense!

Meteohub should present you drop-down lists for sensor selection on WD, WD-Live pages.

Doesn't that do? Please remember to press "save" on sensors page, to register new sensors.

I can only find a page that for WD-Live!

I have this set-up but it only produces clientraw type files which are only for WD-Live. It only does this once a minute, not every 10 seconds like WD.

Plus I can't find any way to merge existing WD-Live data (about 2 years) with new data.
I have to start all over again.

WD has some great record and trend graphs which does not record the extra sensors.

If I plugged my WMR100 into my weather display machine via USB, the WMR100 set-up page allows me to choose which sensor to use for outside temp/hum, but with MeteoHub you get no choices just raw feed take it or leave it.

I know! is it a MeteoHub issue or WD issue

I just want to swap the outside temp/hum for that of the additional sensor.

admin wrote:Meteohub should present you drop-down lists for sensor selection on WD

Maybe EmjayNet is using the Logging ptotocol?
In which case WD will be using th0 as outside temp/hum.

A trick I have sometimes used to modify WD behavour is to set up an Apache server with a 'proxy' meteolog.cgi script on it! I then give WD the IP of the Apache server. The proxy script passes the call from WD to the real meteohub, then uses regex to tweak the returned text before feeding it back to WD!

Relatively complex, but effective...

I may need to tweak th0 myself shortly as a couple of hours ago my th0 (less than a year old) suddenly and for no apparent reason started reporting temps >3 degrees higher than seems reasonable. :(

Yep, thats it "Logging protocol"

Sorry using the wrong terminology

Is there another way to make WD take information from Meteohub? Should i be using "WD Data Export"

I looked at the Meteohub WD-Live but theres to much missing (Icons, moon, current condictions) to be much use.

What I throught was so simple, is now so complex.

OK been doing research, and I could either try to port skyewrights meteolog.cgi to run on IIS with Perl
or
Run Apache along side IIS using port 8080 instead of the standard port 80.

Hopefully there is flexability for this solution!

I like the idea of porting it as Im already running IIS & Perl on the WD machine, but can resort to Apache if I can't do it.

What do you think skyewright?
Can I get a copy of your meteolog.cgi?

What do you think skyewright?

It doesn't matter where or how it runs, just so long as it sits between WD and Meteohub. :)

Can I get a copy of your meteolog.cgi?

Sure. Attached as a .txt file (since Joomla doen't like .cgi).
I'm no Perl expert. You can probably improve it!

From commented out lines you'll see that I've used it for various purposes over time.

Currently it just does:

a) Converts T (temp only) sensors into a TH equivalent, for better handling by WD.

b) Swaps over th0 and th5.
I only just added that, because of a fault that has cropped up today. :(
I didn't really need to do a full swap, but I decided to do so to continue recording the 'faulty' th0, and the "vacated" th5 slot was handy...



How's that? [file name=meteolog.txt size=1365]http://www.meteohub.de/joomla/images/fb ... teolog.txt[/file]

Excellent. Thanks for file and extra info.

I will let you know how I get on during the week.

OK, skyewright

Could not get your script to run under IIS, did not want to spend ages on a total rewrite so went for simple option of installing Apache. Had a bit of a problem getting Apache to install with IIS present but got there in the end.

Script now running exactly as you said! :woohoo:

Its a pity Boris does not implement this into MeteoHub!

Anyway many thanks for help and hope to speak again :)

EmjayNet wrote:Script now running exactly as you said! :woohoo:

Glad to hear it.

EmjayNet wrote:Its a pity Boris does not implement this into MeteoHub!

Here's how I see the situation - Boris's thoughts may not be the same...

As I see it the idea behind the "Export" and "Weather Network" features is different to the idea behind the logging protocol.

The "Export" and "Weather Network" features are designed to provide data to specific externally defined models, so the configurability has to be at the Meteohub end.

On the other hand, the logging protocol aims to provide any external system with generic access to all the Meteohub sensors and sensor data. It is then up to the external system how it handles the data, i.e. the configurability is expected to be at the receiving end.

It so happens that WD does not (yet) provide any such configurability. Maybe that will change someday?

In the meantime the fact that it is possible to sit a proxy between Meteohub and WD and tweak the data in transit is, to an extent, an illustration of just how flexible and powerful the protocol is. :)

If I had more spare time then maybe I would ponder on the possibilities for making the proxy more user friendly, and maybe even doing away with the need for the server, but in practice that is highly unlikely to happen - I already spend far too much time on weather related stuff! :lol:

Of course, if someone wanted to take the idea and develop it...