meteohub.de

Posted: **Sat May 09, 2009 5:21 pm**

DEUTSCH:

Update V4.2f (NSLU2 und x86) enthält die folgenden Änderungen:

* Beseitigt einen mit 4.2e eingeführten Fehler, dass beim Weglassen des Zieldateinamens beim Hochladen von Grafiken and den dann verwendeten Namen der Grafikdefinition eine laufende Nummer angehängt wird.
* Beseitigt einen Fehler bei der Ausgabe von Mindestwerten für "wind" und "gust".
* Beseitigt einen Fehler beim Einstellen der Sendefrequenz von E-Mail Metar Nachrichten.
* Unterstützt das Dänische Wetternetzwerk "borgervejr". Dieses Feature ist noch experimentell.
* Fügt den Systemsensor "Heart Beat" hinzu, der jede Minute den Wert 1.0 liefert. Dies erlaubt die Berechnung der Systemverfübarkeit.
* Erweitert die Auswertungsmöglichkeiten der virtuellen "data" Sensoren. Neben Mittelwert, Minimum und Maximum können nun auch die Summe, die Summe pro Minute, Anzahl steigender Flanken, Anzahl fallender Flanken für Auswertungen herangezogen werden.
* Fügt Unterstützung für bisher nicht Unterstütze Varianten des Oregon Sensors THGR238 zur Auswertung durch RFXCOM hinzu.
* Fügt die Auswertung von RFXmeter Sensoren durch RFXCOM hinzu. Bei Verwendung von RFXPower Sensoren wird der Stromverbrauch in Watt pro Stunde als generischer numerischer Wert ausgegeben und kann auf die "data" IDs abgebildet werden.

---------------------------------------------
ENGLISH:

Update to Meteohub V4.2f (NSLU2 and x86) brings these features:

* Fixes a bug in naming files to be uploaded introduced with version 4.2e. When a filename is missing for graph upload, Meteohub takes the name of the graph as a filename. Last version of Meteohub added a running number to the filename. This has be stripped again in current version.
* Fixes a bug when reporting minimum values for wind and gust.
* Fixes a bug that keeps Metar E-mail sending stuck to 5 minute interval.
* Adds support for Danish weather network "borgervejr". This feature is still experimental.
* Adds system data sensor "heart beat", which reports every minute a value of 1.0. This allows to compute system's availability.
* Enhances evaluation options for virtual "data" sensors. In addition to average value, minimum and maximum it supports now also sum, sum per minute, number of rising and falling edges.
* Adds support for newer models of Oregon sensor THGR328 when using RFXCOM.
* Adds support for RFXmeter sensors to be used with RFXCOM. When used with RFXPower electrical power consumption can be measured in Watts per hour and can be mapped to "data" ids for evaluation.

------------------------------------

Link: http://www.meteohub.de/joomla/index.php ... &Itemid=29

Posted: **Sat May 09, 2009 5:32 pm**

Example for use of new data features.

number of reboots per day

Posted: **Sat May 09, 2009 5:34 pm**

Posted: **Sat May 09, 2009 5:37 pm**

System availability

Posted: **Sat May 09, 2009 5:38 pm**

Posted: **Sat May 09, 2009 7:13 pm**

Boris,

So I'm sitting here in the barber shop waiting to get my haircut and reading the forum. Then I see that 4.2f is available and so I connected to my Meteohub using my Blackberry and told it to check for upgrade. Then it downloaded it and then I clicked install! Very cool!

Thanks to your new feature, I didn't even have to be in front of a computer!

Thanks and have a great day!

Posted: **Sat May 09, 2009 10:00 pm**

Hi Boris,

After upgrading to V4.2f there seems to be something wrong with the recomputation. The hist_xxx files seem to be corrupted: files end in the middle of a data record, and th0 sensor data are not logged (and therefore Meteohub is sending out wrong/no data for max/min daily/monthly/year temps). I have manually recomputed a second time with the same result.
Has anybody experienced the same behaviour?

Thanks and Best Regards

Juan [file name=hist_day1.txt size=4096]http://www.meteohub.de/joomla/images/fb ... t_day1.txt[/file]

Posted: **Sat May 09, 2009 11:34 pm**

tervingo wrote:Hi Boris,

After upgrading to V4.2f there seems to be something wrong with the recomputation. The hist_xxx files seem to be corrupted: files end in the middle of a data record, and th0 sensor data are not logged (and therefore Meteohub is sending out wrong/no data for max/min daily/monthly/year temps). I have manually recomputed a second time with the same result.
Has anybody experienced the same behaviour?

yes, as I already mentioned with another thread my meteohub system shows the same behaviour since the 4.2f version was installed.
Yesterday my th0, sol and uv min/max values disappeared, and only returned after deleting and re-adding the weather stations.
An hour ago the day1 min/max for th4 disappeared and manual data recomputation does not bring it back.

Code: Select all

actual_th4_temp_c 13.7
actual_th4_temp_f 56.7
actual_th4_hum_rel 93
actual_th4_dew_c 12.6
actual_th4_dew_f 54.7
actual_th4_heatindex_c 13.7
actual_th4_heatindex_f 56.7
actual_th4_humidex_c 16.3
actual_th4_humidex_f 61.3
actual_th4_cloudheight_m 138
actual_th4_cloudheight_ft 440
actual_th4_hum_abs 0.7
...

day1_th3_temp_c 20.7
day1_th3_temp_f 69.3
day1_th3_tempmin_time 20090509004914
day1_th3_tempmax_time 20090509165028
day1_th3_tempmin_c 12.0
day1_th3_tempmin_f 53.6
day1_th3_tempmax_c 27.2
day1_th3_tempmax_f 81.0
day1_th3_temp_trend 0
day1_th3_dew_c 10.2
day1_th3_dew_f 50.3
day1_th3_dewmin_time 20090509050139
day1_th3_dewmax_time 20090509153444
day1_th3_dewmin_c 6.5
day1_th3_dewmin_f 43.7
day1_th3_dewmax_c 15.0
day1_th3_dewmax_f 59.0
day1_th3_dew_trend -1
day1_th3_heatindex_c 20.7
day1_th3_heatindex_f hour1_utcdate 20090509212759
hour1_localdate 20090509232759
hour1_wind0_maxspeeddir_deg 202.5

Posted: **Sun May 10, 2009 12:45 am**

I also agree. You can see that most of my historical data is not showing up anymore.

http://weather.huffman.info

Posted: **Sun May 10, 2009 10:08 am**

Yes, I agree, too. There must be something wrong. Get a wrong checksum during recomputation:

logger (10.05.2009 10:00:17): station 0 (WMRS-200), wrong checksum (ff51 vs computed 0251) for sensor model 42 in byte sequence: ff ff 10 42 c1 8f 00 4b 64 00 00 00 51 ff

Posted: **Sun May 10, 2009 10:47 am**

Hi,

By what other users report, there seems to be a bug in update 4.2f with the recomputing process. I hope that Boris can come up with a new update fixing this as soon as possible.

In the meanwhile, is there any (easy) way to downgrad from an update to the previous one? (i.e. from 4.2f down to 4.2e).

Thanks

Posted: **Sun May 10, 2009 10:56 am**

deleted and moved

Posted: **Sun May 10, 2009 11:07 am**

Is it possible to downgrade to an earlier version in the same way like upgrading? - means (example) downloading upd4.2e and processing the upgrade procedure for downgrade?

Posted: **Sun May 10, 2009 11:27 am**

Rikken wrote:Yes, I agree, too. There must be something wrong. Get a wrong checksum during recomputation:

logger (10.05.2009 10:00:17): station 0 (WMRS-200), wrong checksum (ff51 vs computed 0251) for sensor model 42 in byte sequence: ff ff 10 42 c1 8f 00 4b 64 00 00 00 51 ff

The checksum error refers to data freshly received from the sensor, i.e. a bad 'packet' of data such as can happen at any time. Unlikley to be related to the recomputation issue (which I too see with 4.2f).

Posted: **Sun May 10, 2009 11:30 am**

Hi Rikken,

I just did a downgrading from 4.2f to 4.2.

The process itself went smoothly, the system restarted flawlessly.
But I did not let it run for longer time to see, if everything is working.

By the way: my recomputation finishes without errors:
wmr928fulleval(10.05.2009 11:20:00): recomputation of weather data finished: 1060002 records processed in 897 seconds (1181 records per second)

regards

meteohub.de

Meteohub Update 4.2f

Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f

Re:Meteohub Update 4.2f