meteohub.de

DEUTSCH:

Update V4.6c (NSLU2, x86, SheevaPlug) enthält die folgenden Änderungen:

* Vergrößert interne Puffer um die Datenmenge vieler Sensoren handhaben zu können.
* Stellt die geographischen Positionsangaben in der für WD-Live geeigneten Form zur Verfügung.
* Unterstützung die "Current Cost 128 Envi" Energiemonitore als zusätzliche "Wetterstation" (noch experimentell).
* Fügt die Option "Zuschneiden" zu den Grafikdefinitionen hinzu. Dies erlaubt die Erzeugung von Grafiken ohne Rand.
* Unterstützt die Wettervorhersagewerte der ws23xx.
* Beseitigt einen Fehler bei der Berechnung der durchschnittlichen Windgeschwindigkeit bei ws23xx-Stationen im Falle ungültiger Windwerte.
* Beseitigt ein Problem mit dem Start des Datenloggers nach einem Reboot auf einigen X86-Systemen.
* Gelegentlich auftretende Socket-Connection-Probleme auf der Seite "Sensoren" beseitigt.
* Ausleseroutine für WS500 und deren Klone is nun robuster gegenüber Übertragungsfehlern.

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

Update to Meteohub V4.6b (NSLU2, x86, SheevaPlug) brings these features:

* Expands internal buffers to handle large numbers of sensors.
* Provides data about geographic position in a form requested by WD Live.
* Adds new weather station type "Current Cost Envi 128" (still experimental).
* Adds Option "crop" to graph definition page. This allows to generate graphs without border.
* Does now support forecast values for stations ws23xx.
* Fixes a bug in computation of average wind speed for ws23xx stations, when illegal wind speeds are detected.
* Fixes a bug not starting data logger correctly after a reboot on some X86 platforms.
* Fixes a bug that causes socket connection stalls in certain situations on page "sensors".
* Sensor data reading is improved to handle data transmission errors of weather station WS500 and clones.

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

Hi Boris,

It seems that the other WDLive issue is still not fixed:
Field 32 of clientraw:
<stationname>_[actual_date0_hour_local:-]:[actual_date0_min_local:-]
should be changed into
<stationname>-[actual_date0_hour_local:-]: [actual_date0_min_local:-]

Thanks!

What do you expect the change of a "_" to "-" and the extra space after ":" will do?

Display of date, time and station name works fine at my station as is (see demo section on the left).

Hi Boris,

The _ needs to change to a - in order to follow the same syntax as WD is using.

The saratoga scripts for instance, are using the timestamp part to determine whether data is current or not.

The extra space is just co-incidence, it should not matter.
You can have a look at how I'm using this script currently (http://weather.westerkerkweg.nl/), it's still not finished. The about section shows the WD variables, as well as the associated meteohubfields (more or less for my own reference)

Boris,

If your going to make changes to the clientraw template any chance you could also add the soil-1 & leaf-1 sensors to populate fields 156 Leaf Wetness C & 157 Soil moisture C for WDL output.

will all be part of next update.

I have two NSLU2 meteohubs, both running 4.6b. Immediately after I updated one of them to 4.6c, I started receiving the following error messages in the alarm log:

2010.03.28 21:25:08 meteohub: weathernet: weather underground rapid fire: error open pipe /usr/bin/wget -U meteohub -t 2 -q -O /dev/stdout http://rtupdate.wunderground.com/weathe ... =updateraw

Also the rapidfire function for weather underground ceased to work. I rebooted the 4.6c meteohub, but the problem returned so I reverted back to 4.6b, and the problem has stopped.

I have never seen this error message before I upgraded to 4.6c, so I am curious if some change to 4.6c might be causing it? Or if it is something else?

There are some mails from NSLU2 users about these problems with 4.6c.

I will try to reconstruct that this evening on my rig. When you are facing the problem, please do a manual downgrade to 4.5b for now until problem is fixed.

Hi,
I want to report problem with big CPU load. After update on 4.6c my Sheeva after 6:00 goes very slowly, CPU usage is extremly high. After rebooot everything looks good. This problem repeating everyday from update.
Previous version was ok.
Boris, please help us.
Thanks

Config: Sheeva, MH 4.6c, WS 23XX

I see the same here on a Sheeva. It seems that the loggerd process is the culprit:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1523 root 5 -15 6080 1540 1044 R 93.9 0.3 1510:34 loggerd

The time used by this process is excessive this as one realizes that the system was last rebooted on Apr 1