meteohub.de

DEUTSCH:

Dieses Update fasst die 4.2x Updates der letzten Wochen zusammen. Gegenüber 4.2 sind die folgenden wesentlichen Änderungen enthalten:

• Unterstützung der ELV Wetterstationen WS300PC und WS444
• Unterstützung der Wetterstation RainWise MKIII
• Unterstützung von RFXmeter Sensoren
• Einführung von Sensoren zur Auswerung von Systemdaten
• und viele weitere Änderungen/Bug-Fixes, die dem herunterladbaren Update als Beschreibung beiliegen...

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

This update summarizes 4.2x updates of the last weeks. Most significant changes to 4.2 are:

• Support of ELV weather stations WS300PC and WS444
• Support of weather station RainWise MKIII
• Support of RXFmeter sensors
• Introduction of virtual sensors that report system status
• a lot of additional changes and bug fixes that are attached as documentation when downloading the update...

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

NSLU2 USB stick image (4GB ): http://www.meteohub.de/joomla/index.php ... &Itemid=29

NSLU2 USB stick image (2GB ): http://www.meteohub.de/joomla/index.php ... &Itemid=29

Installation image for Meteohub x86 platforms: http://www.meteohub.de/joomla/index.php ... &Itemid=29

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

Documentation version 4.3 (English ): http://www.meteohub.de/joomla/index.php ... &Itemid=29

Documentation version 4.3 (Deutsch ): http://www.meteohub.de/joomla/index.php ... &Itemid=29

It appears that the "last15m" "last60m" reading for data7 heartbeat are now counting too many times during these time periods.

Does that mean that "last24h" is also counting too many times?
[*]
last15m_data7_valuesum_int 16
last60m_data7_valuesum_int 61

The data looks normal
[*]
20090516020000 data7 100
20090516020100 data7 100
20090516020200 data7 100
20090516020300 data7 100
20090516020401 data7 100
20090516020500 data7 100
20090516020600 data7 100
20090516020700 data7 100
20090516020800 data7 100
20090516020901 data7 100
20090516021000 data7 100
20090516021100 data7 100
20090516021200 data7 100
20090516021300 data7 100
20090516021401 data7 100
20090516021500 data7 100
20090516021600 data7 100
20090516021700 data7 100
20090516021800 data7 100
20090516021901 data7 100

That heart beat thing is a tricky one :-)

When computation of "last15m" starts, Meteohub takes actual time minus 900 seconds as a starting point to look for heart beat entries in raw data. While Meteohub is doing this new heart beat entries might be added. Metohub continues evaluating raw data until end of file. So a new heart beat that has happened during evaluation already running is also taken into account. I will introduce an end marker to keep the new entries out of evaluation.

Hopefully, I am not boring you with details, but I wanted to explain, why Meteohub might register a heart beat too much, especially, when system load is high and evaluation of data takes a bit longer.

Actually I like the details about what's going on in the software. I think a lot of us here enjoy that sort of thing. :)

I can understand how complicated it is with timing, because time never stops and so you have to know and plan where the program will be in the future and take that into count.

Good luck and thanks for the insight!