meteohub.de

Hello Everyone, I am using meteohub with a Vantage Pro2 Plus station at a remote location streaming data to Weather Display V10.37Q Build 23 at another location. Everything was working great up until I updated meteohub from version 4.6t to version 4.7. After the update I stopped receiving UV and Solar data from my remote weather station to my home running Weather Display. I am still receiving all other data without a problem. I also use meteohub to send data to Weather Underground and WU is still receiving UV and Solar data. Has anyone else experienced this problem? If so, is there a fix short of reverting back to meteohub 4.6t? If I have to revert back to version 4.6t can it be done remotely? It's a three hour drive to my remote weather station and if I can fix the problem at home that would be great. Thank you.

Michael

Hi,

Are you using the clientraw files to send the data from MH to WD? Or are you using another method.

Might be a good idea to look at the datafiles and see what data is being send/received.

I'm using TCP/IP through port 5500 which has worked well for me for a couple of years. I checked my data in WD and I stopped receiving UV and Solar data as soon as I updated meteohub to version 4.7. All other data is fine.

Hmm, I guess this is one for Boris, I can try to look at my rig later this week when I'm back home and see what it is doing.

MJC55 wrote:Hello Everyone, I am using meteohub with a Vantage Pro2 Plus station at a remote location streaming data to Weather Display V10.37Q Build 23 at another location. Everything was working great up until I updated meteohub from version 4.6t to version 4.7. After the update I stopped receiving UV and Solar data from my remote weather station to my home running Weather Display.

I haven't have time yet to install the 4.7 update, but perhaps there is some subtle change in the http protcol's output for uv & solar?

Could you please use the following URL in your browser (adjusting the IP to match your Meteohub), then post the result here?

http://192.168.0.77/meteolog.cgi?mode=data&type=xml

Here is the information you requested. It's early in the day so there isn't any UV reading yet but there is solar data. I checked my WD log files UV and solar data stopped on the 10th of January. That's when I updated to version 4.7. Is there a way to access the meteohub directory remotely so I could revert back to 4.6t manually to see if that corrects the problem? It's a three hour drive each way to my weather station and if I don't have to make the trip that would be great. Thank you.

<logger>
<THB date=20110118163747 id=thb0 temp=15.4 hum=34 dew=-0.4 press=944.2 seapress=1023.4 fc=2 />
<TH date=20110118163759 id=th0 temp=1.1 hum=70 dew=-3.8 />
<UV date=20110118163745 id=uv0 index=0.0 />
<SOL date=20110118163729 id=sol0 rad=14 />
<WIND date=20110118163827 id=wind0 dir=234 gust=1.3 wind=1.3 chill=-0.2 />
<RAIN date=20110118163745 id=rain0 rate=0.0 total=79.0 delta=0.0 />
</logger>

MJC55 wrote: It's early in the day so there isn't any UV reading yet but there is solar data

Here we may not see a UV of even 1 for another month or so!

Reducing your xml down to just the UV & SOL that's

MJC55 wrote: <UV date=20110118163745 id=uv0 index=0.0 />
<SOL date=20110118163729 id=sol0 rad=14 />

which is just as I'd expect.

My "live" Meteohub, the one that feeds the live copy of WD (10.37Qb9) is still running 4.6h, which produces xml like:

<SOL date=20110118163729 id=sol0 rad=14>

That is working fine and records sunshine in the daylight hours just as I'd expect.

Update 4.6u (the one after 4.6t) modified the xml output to make it more standards compliant by quoting the values, and adding the / at the end. The quoting stopped WD reading the data, so it was made optional (off by default). The trailing / didn't seem to be a problem.

Using v4.7 with my "develpoment" copies of Meteohub and WD 10.37Qb9 I can see that even with the trailing / the debug output in WD claims to have found the raw solar value. Oddly is isn't showing the non-zero value that is in the xml but maybe that's because it knows that it's after sunset (I've tweaked the value before WD see it so that it's not a zero); that possibility is perhaps supported because if I artificially strip the trailing / WD still says it's seen the value, but ignores it!

For the present I'm out of ideas.

PS. If you haven't already tried it, you can see evidence of the data arriving from Meteohub in:
WD => View => WS2010-13/WS2500 data logger setup/info

By default the data shown is very limited. You can see more if you set:

WD => Setup => Advanced/Misc Settings => Program => Log raw data for testing (as rawultimiterdata.txt)

(though you still look in WS2010-13/WS2500 data logger setup/info, not in the txt file mentioned!)

N.B. If you use that for any length of time, it's a good idea to use the "Clear data screen" button in WS2010-13/WS2500 data logger setup/info now and again (e.g. daily) else memory usage climbs.

skyewright wrote:For the present I'm out of ideas.

I've done some more work on this, and in daylight this time...

My live system has "live" system has WD (10.37Qb9) happily reading solar from Meteohub 4.6h

If I restore that WD to my test system then feed it from the same sensors as seen by Meteohub 4.7 the solar readings stop (even though WD'd debug data say;s it has found the data).

On the test system the Meteohub logging protocol data passes through a perl script where I can manipulate the data before WD sees it. If I use that script to strip the space and slash (/) from the ens of the solar entries in the xml using then WD starts seeing the solar data.

So it looks as though the " /" in the "better" xml that was introduced in 4.6u is enough to upset WD for solar. I don't have a UV sensor but it seems likely that just the same thing is also the reason for the lack of UV too.

Well I reverted meteohub back to version 4.6t and I started receiving UV and Solar data again to Weather Display. Something changed in meteohub when I updated from 4.6t to 4.7. I'll stick with v4.6t for right now. The manipulating of the WD data that you're working with is a little to technical for me. Thanks for the help.

will be fixed with next update.

Does rev 4.7d (Build 354) provide UV and Solar sensor data to Weatherbug? Sensors are enabled for sending to Weatherbug and are recorded according to the XML log (it’s night here now, so the Solar and UV data is 0):
<logger>
<THB date=20110321005740 id=thb0 temp=22.8 hum=42 dew=9.2 press=1015.5 seapress=1027.3 fc=2>
<TH date=20110321005742 id=th0 temp=12.5 hum=59 dew=4.7>
<UV date=20110321005734 id=uv0 index=0.0>
<SOL date=20110321005714 id=sol0 rad=0>
<WIND date=20110321005756 id=wind0 dir=124 gust=0.0 wind=0.0 chill=12.5>
<RAIN date=20110321005734 id=rain0 rate=0.0 total=1.8 delta=0.0>
</logger>
However, the string received by Weatherbug does not include solar or UV data. Please advise.
Thanks.

i checke. weatherbug upload does provide "UV" and "solarradiation". when you login to your Meteohub via ssh (user root, pw meteohub) and give "/home/meteohub/meteonet -d" command, you can see what values are uploaded for selected weather networks.

Thank you! I checked with Weatherbug today to ask why UV & Solar data is not showing up on the web site for my station and they responded: "the PWS stations are not pushing that data at this time." Looks like I'll need to find another way to get that data into my ISY-99 home automation system.