Update 4.9s

What's hot...

Moderator: Mattk

User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 7854
Joined: Mon Oct 01, 2007 10:51 pm

Update 4.9s

Post by admin »

Update to Meteohub V4.9s (NSLU2, x86, SheevaPlug, DreamPlug, iConnect, DC01, mini X) brings these features:
  • enhances demo period to 31.5.2013
  • fixes dew point inconsitencies by limiting lower bound humidity value to be reported from Hideki stations to 10%.
  • fixes a bug crashing data logger process when having envoy8x connected to an additional temp sensor.
Update Link: http://www.meteohub.de/files/update-v4.9s.upd
User avatar
N5XL
Senior Boarder
Senior Boarder
Posts: 45
Joined: Wed Dec 28, 2011 6:04 am
Location: Scottsdale, Arizona

Re: Update 4.9s

Post by N5XL »

Just put 4.9s through the test. It is working well !

Ham radio operators thank you for the fixes.

73
de
N5XL
ulbr2000
Junior Boarder
Junior Boarder
Posts: 21
Joined: Mon Dec 08, 2008 12:07 pm

Re: Update 4.9s

Post by ulbr2000 »

Hello Boris,

could you please consider fixing the weathernet issue writing following messages

2012.12.24 04:22:02 prognostix: weathernet: windfinder: upload to windfinder:
2012.12.24 04:42:05 prognostix: weathernet: windfinder: upload to windfinder:
2012.12.24 04:52:11 prognostix: weathernet: windfinder: upload to windfinder:

regards

Ulrich
el-rain
Junior Boarder
Junior Boarder
Posts: 27
Joined: Tue Aug 14, 2012 11:10 am

Re: Update 4.9s

Post by el-rain »

Hi,
have something strange with airpressure received from a Envoy,not sure if this is a bug related to 4.9s

Yesterday I installed an Envoy and connected to my meteohub running 4.9s.
No ISS installed yet so only Envoy internal sensors. I create some graph to compare airpresure, Temp and humidity of my WS2300 and the Envoy.

Both station are setup in Meteohub to use the weatherstation height for the sea-level preasure claculation.
If I now change the station hight I normally expect that after the recalculation is done that the local preasure isn't changed but the sea-level preasure.

But when I check my graph I see that the local presure change about the same value as the sea-level. Strange is that I can see this as well in the data view of the thb sensor.

i.e.
changed from 75m to 70m:
..
20121229162810 thb1 151 64 0083 10011 0 10099
20121229163114 thb1 151 64 0083 10017 0 10099
..
changed from 70m to 65m:
..
20121229232114 thb1 141 61 0067 10006 0 10088
20121229232212 thb1 141 61 0067 10005 0 10087
20121229232302 thb1 141 61 0067 10011 0 10087
20121229232309 thb1 142 61 0068 10011 0 10087
..
changed back from 65m to 75m:
..
20121230112509 thb1 120 65 0056 10052 2 10128
20121230112611 thb1 120 65 0056 10052 2 10128
20121230112714 thb1 120 65 0056 10041 2 10129
20121230112807 thb1 120 66 0058 10041 2 10129
..
Compare presure between WS2300 (WS) and envoy (DV)<br />red/green local preasure, blue/pruple sea-level presure
Compare presure between WS2300 (WS) and envoy (DV)
red/green local preasure, blue/pruple sea-level presure
vergleich_ws2300_envoy.png (8.22 KiB) Viewed 20996 times
Time in the graph is in CET, time from the dataview is in UTC.

Can somebody explain to me why the local preasure is changed as well in the data view when change the station hight!?
As you see the last value (see-lecel presure read from the Encoy) will not change, same I would expect for the local presure in the dataview.

Stations are mounted on the attic only about 30cm distance to each other, a 3port powerplug in between.
Temprature are the nearly the same, max difference is about .25°C
Humidity have a constant difference of about 8% between them.

regards
El
User avatar
N5XL
Senior Boarder
Senior Boarder
Posts: 45
Joined: Wed Dec 28, 2011 6:04 am
Location: Scottsdale, Arizona

Re: Update 4.9s

Post by N5XL »

El,

When I change altitude in Meteohub to a different value, my actual pressure as recorded by Meteohub does not change, however my sealevel pressure and altimeter change accordingly (as they should).

Here is an easy experiment to do. Set up your station to be at 0 meters altitude in Meteohub. Once set, inspect the sensors and make sure they are reporting data. Once they are reporting data, type this into your web browsers address bar.

http://THE IP ADDRESS OF YOUR METEOHUB STATION/meteograph.cgi?text=all for example, I would type in http://192.168.1.149/meteograph.cgi?text=all

Scroll down the page and look for the pressure sensor in question and observe the values given for it. (I have three pressure values, each given with 4 different units of measure). Record the values given.

Now change the altitude in Meteohub to your normal station altitude, save and let the sensors refresh. Once they refresh, reload the webpage from above and record the values for pressure at the new altitude and compare the data.

Here I have done this and copied and paste my station values for altitude 826 meter and altitude 0 meters. I do not see the same thing you are seeing. Are you sure you are plotting the right values?

Image
el-rain
Junior Boarder
Junior Boarder
Posts: 27
Joined: Tue Aug 14, 2012 11:10 am

Re: Update 4.9s

Post by el-rain »

Hi David,
what you describe is exactly what I expected as well. Data I put in before was from the dataview menu. I have no idea why the graph looks that strange, seems there is some recalculation done after the change and after that it looks always somehow different.

I did the test like you suggested and what I see is that the actual_thb1_press_hpa change while the actual_thb1_sealevel_hpa stay in same range.
meteohub-testdata.png
meteohub-testdata.png (24.34 KiB) Viewed 20950 times
As you see the press_hpa is changed and sealevel_hpa stay in normal range. During the test timeframe the preassure was rising about +1 hpa, I see this as well on thb0 (my WS2300), so don't worry about that. Only change I did is going on the weatherstation menu on Metehub and change the station height and saved this change.

I stored as well the full output of http://THE IP ADDRESS OF YOUR METEOHUB STATION/meteograph.cgi?text=all if this is needed I can upload this.
After each change I create a new graph show thb0/1 and thb0/1-sea and looks very strange.
envoy_back_to_75m_recalculation_done.png
envoy_back_to_75m_recalculation_done.png (6.99 KiB) Viewed 20950 times
Hope this show why this confuse me, I don't understand why the local measured preasure is changed but not the sealevel.

Happy New Year
vy73
El
User avatar
N5XL
Senior Boarder
Senior Boarder
Posts: 45
Joined: Wed Dec 28, 2011 6:04 am
Location: Scottsdale, Arizona

Re: Update 4.9s

Post by N5XL »

El,

I imagine you have the other weather station attached to Meteohub at the same time as the Envoy? Can you also share the data recorded for "actual thb0 height m", "actual thb0 press hpa", "actual thb0 sealevel hpa" during the same time frame as you change altitude?

Have you experimented with the Envoy attached to Meteohub alone to see if the problem is still there?
Last edited by N5XL on Tue Jan 01, 2013 6:46 pm, edited 1 time in total.
User avatar
N5XL
Senior Boarder
Senior Boarder
Posts: 45
Joined: Wed Dec 28, 2011 6:04 am
Location: Scottsdale, Arizona

Re: Update 4.9s

Post by N5XL »

El,

When you change altitude in Meteohub, do you only change the altitude in Meteohub or do you also change the elevation on the Envoy at the same time?

Do you have any values input into Envoy for station elevation and sea level barometer? If you do, set both of these to zero and see if the problem goes away.
el-rain
Junior Boarder
Junior Boarder
Posts: 27
Joined: Tue Aug 14, 2012 11:10 am

Re: Update 4.9s

Post by el-rain »

N5XL wrote: I imagine you have the other weather station attached to Meteohub at the same time as the Envoy?
Yes.
N5XL wrote: Can you also share the data recorded for "actual thb0 height m", "actual thb0 press hpa", "actual thb0 sealevel hpa" during the same time frame as you change altitude?
I changed the altitude only for the Envoy, so the WS2300 always set to 75m in Meteohub

When set Envoy to 0m at 13:22:
actual_thb0_height_m 75
actual_thb0_press_hpa 995.1
actual_thb0_sealevel_hpa 1003.9

When set Envoy to 500m at 13:35
actual_thb0_height_m 75
actual_thb0_press_hpa 995.4
actual_thb0_sealevel_hpa 1004.3

When set Envoy back to 75m at 13:50:
actual_thb0_height_m 75
actual_thb0_press_hpa 995.8
actual_thb0_sealevel_hpa 1004.6
N5XL wrote: Have you experimented with the Envoy attached to Meteohub alone to see if the problem is still there?
No, didn't test this behavior. Before I installed the Envoy at the final location I only test if all works generally. This test was done with a x86 Meteohub image running in a VM and ISS in an other room while the Envoy and Console are next to each other in my working room.
N5XL wrote: When you change altitude in Meteohub, do you only change the altitude in Meteohub or do you also change the elevation on the Envoy at the same time?
Do you have any values input into Envoy for station elevation and sea level barometer? If you do, set both of these to zero and see if the problem goes away.
The wetherstations are installed at the house of my parents in an other township, so all changes are only done remotely via the Meteohub web gui.
The Envoy was set to 75m via Weatherlink when I installed this, just done to have the chance to play with the different ways could be choosed in Meteohub to get sea level preasure.
Will try to set this to 0m when I'm there next weekend. As I understood the Envoy is a "Console without Display" I thought this shouldn't madder, as in a Console I need to set the altitude to get sea-level shown on the Display. Anyway will give this a try.
meteohub_weatherstation.jpg
meteohub_weatherstation.jpg (114.08 KiB) Viewed 20941 times
Sorry Menu is in German, only change the station's altitude for the Vantage and sea level calculation is set to based on station's altitude.

vy73
El
wfpost
Platinum Boarder
Platinum Boarder
Posts: 591
Joined: Thu Jun 12, 2008 2:24 pm
Location: HONSOLGEN
Contact:

Re: Update 4.9s

Post by wfpost »

just realized, that email stopped after updating to version 4.9r

Always getting segfault errors, even with the testmail function
just updated to 4.9s, but still the error with not sending emails


Jan 4 00:15:20 meteohub kernel: sendmail[3263]: segfault at 00000000 eip 00000000 esp bfa8acac error

Dec 30 09:00:42 meteohub kernel: sendmail[13089]: segfault at 00000000 eip 00000000 esp bfb1935c error 4
Dec 30 23:55:10 meteohub kernel: sendmail[26211]: segfault at 00000000 eip 00000000 esp bf8b853c error 4
Dec 30 23:59:41 meteohub kernel: sendmail[26833]: segfault at 00000000 eip 00000000 esp bfc7a0dc error 4
Dec 30 23:59:45 meteohub kernel: sendmail[26844]: segfault at 00000000 eip 00000000 esp bfc372ec error 4
Dec 31 09:00:47 meteohub kernel: sendmail[31099]: segfault at 00000000 eip 00000000 esp bfa6327c error 4
Dec 31 23:55:03 meteohub kernel: sendmail[8773]: segfault at 00000000 eip 00000000 esp bfd8532c error 4
Dec 31 23:55:04 meteohub kernel: sendmail[8782]: segfault at 00000000 eip 00000000 esp bfc676bc error 4
Dec 31 23:55:05 meteohub kernel: sendmail[8785]: segfault at 00000000 eip 00000000 esp bff3636c error 4
Dec 31 23:57:02 meteohub kernel: sendmail[9070]: segfault at 00000000 eip 00000000 esp bfc956fc error 4
Dec 31 23:57:03 meteohub kernel: sendmail[9078]: segfault at 00000000 eip 00000000 esp bf9e723c error 4
Dec 31 23:59:42 meteohub kernel: sendmail[9402]: segfault at 00000000 eip 00000000 esp bfb6312c error 4
Dec 31 23:59:46 meteohub kernel: sendmail[9412]: segfault at 00000000 eip 00000000 esp bfbb792c error 4
Jan 1 09:00:48 meteohub kernel: sendmail[18881]: segfault at 00000000 eip 00000000 esp bfe3e71c error 4
Jan 1 23:55:15 meteohub kernel: sendmail[3541]: segfault at 00000000 eip 00000000 esp bfe1651c error 4
Jan 1 23:59:42 meteohub kernel: sendmail[4154]: segfault at 00000000 eip 00000000 esp bfd94b4c error 4
Jan 1 23:59:46 meteohub kernel: sendmail[4165]: segfault at 00000000 eip 00000000 esp bfc42b2c error 4
Jan 2 09:00:46 meteohub kernel: sendmail[9515]: segfault at 00000000 eip 00000000 esp bfe73e0c error 4
Jan 2 23:55:12 meteohub kernel: sendmail[21171]: segfault at 00000000 eip 00000000 esp bfa0abac error 4
Jan 2 23:59:41 meteohub kernel: sendmail[21787]: segfault at 00000000 eip 00000000 esp bf95605c error 4
Jan 2 23:59:45 meteohub kernel: sendmail[21797]: segfault at 00000000 eip 00000000 esp bfefe47c error 4
Jan 3 09:00:47 meteohub kernel: sendmail[31390]: segfault at 00000000 eip 00000000 esp bf83bf0c error 4
Jan 3 23:55:09 meteohub kernel: sendmail[8203]: segfault at 00000000 eip 00000000 esp bfce50cc error 4
Jan 3 23:59:41 meteohub kernel: sendmail[8847]: segfault at 00000000 eip 00000000 esp bf8b2d2c error 4
Jan 3 23:59:45 meteohub kernel: sendmail[8860]: segfault at 00000000 eip 00000000 esp bf80f14c error 4
Jan 4 00:01:09 meteohub kernel: sendmail[9316]: segfault at 00000000 eip 00000000 esp bff995ac error 4
Jan 4 00:02:07 meteohub kernel: sendmail[9423]: segfault at 00000000 eip 00000000 esp bfeae28c error 4
Jan 4 00:02:15 meteohub kernel: sendmail[9441]: segfault at 00000000 eip 00000000 esp bfbc1c6c error 4
Jan 4 00:03:23 meteohub kernel: sendmail[9622]: segfault at 00000000 eip 00000000 esp bfb0881c error 4
Jan 4 00:03:24 meteohub kernel: sendmail[9630]: segfault at 00000000 eip 00000000 esp bfdf376c error 4
Jan 4 00:04:04 meteohub kernel: sendmail[9730]: segfault at 00000000 eip 00000000 esp bff9930c error 4
Jan 4 00:04:05 meteohub kernel: sendmail[9740]: segfault at 00000000 eip 00000000 esp bfda279c error 4
Jan 4 00:06:59 meteohub kernel: sendmail[10558]: segfault at 00000000 eip 00000000 esp bfbc96bc error 4
el-rain
Junior Boarder
Junior Boarder
Posts: 27
Joined: Tue Aug 14, 2012 11:10 am

Re: Update 4.9s

Post by el-rain »

Hi,
today I was on the location of my weatherstation and changed the settings in the Envoy ist self with Weatherlink software.

station elevation was on 75m change this to 0m
sea level barometer was empty and I let it empty

This changes was done at about 12:00 UTC. After that I collected again
press_hpa and sealevel_hpa for thb1 (Envoy) and thb0 (WS-2300).
meteohub_test2_data.png
meteohub_test2_data.png (34.41 KiB) Viewed 20871 times
As you see problem still the same, to me this looks like meteohub somehow take the local pressure of the Envoy as sealevel and calculate the local from that value by tacking the altitude.
When I read the data from the Envoy with weatherlink it self all looking as I expect them.

Any Idea if this could be fixed somehow by reconfiguration of my Meteohub installation or by change settings of the Envoy?
Is there any debug or verbose flag could be set via console to get out put of the data Meteohub fetch from the Envoy??

regards
El
User avatar
N5XL
Senior Boarder
Senior Boarder
Posts: 45
Joined: Wed Dec 28, 2011 6:04 am
Location: Scottsdale, Arizona

Re: Update 4.9s

Post by N5XL »

El,

You need to also try the Envoy by itself without the other wx station connected to Meteohub.
el-rain
Junior Boarder
Junior Boarder
Posts: 27
Joined: Tue Aug 14, 2012 11:10 am

Re: Update 4.9s

Post by el-rain »

Hi,
will try, but what would be the best way to do this?

- just delete the other station in meteohub
- just unplug it from meteohub
- unplug and delete this from meteohub
- unplug and reset meteohub to default.

As my system was broken in Dezember after 4 Month have anway not much historic data, so no problem if I loose them.

vy73
El
User avatar
N5XL
Senior Boarder
Senior Boarder
Posts: 45
Joined: Wed Dec 28, 2011 6:04 am
Location: Scottsdale, Arizona

Re: Update 4.9s

Post by N5XL »

You should be able to unplug the WS2300, leave the Envoy attached and then reboot Meteohub. The only available sensors then will be from the Envoy.
el-rain
Junior Boarder
Junior Boarder
Posts: 27
Joined: Tue Aug 14, 2012 11:10 am

Re: Update 4.9s

Post by el-rain »

Meanwhile I tried to just delete the WS2300 and reboot meteohub.

No change still doing it wrong.

Will anyway go there again this evening, so I will unplug the WS2300 for a test.
Post Reply