Update 4.6p

[admin]

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

• low level driver for wsxxx improved.
• Wd-Live day/night flag supported. Switching from day to night and vice-versa is aligned to local civil-twilight calculation. Data also avail as template variable "actual_daynight_flag_local" giving result "D" or "N".
• Adds predefined conversion module "sensadd", which acts like "sensdiff", but adds the two sensor values instead of subtracting these.
• Adds predefined conversion function "select" which can pipe data of two trigger sensors to an gawk script for further computation. Manual explains how to do that.
• Fixes WLAN support for SheevaPlugs. Supported types are: adm8211, at76c50x, ath, b43, b43legacy, ipw2x00, iwlwifi, iwmc3200wifi, libertas, libertas_tf, mwl8k, p54, rndis_wlan, rt2x00, rtl818x, wll2xx, zd1211rw
• Fixes a bug in generating WD-Live "clientrawhour.txt" files
• Adds support for ELV USB-WDE1 weather station receiver (still experimental)

Link: http://www.meteohub.de/files/update-v4.6p.upd

[YJB]

I installed this on my test system this morning (NSLU2). After adding a virtual sensor I'm getting the dreaded "error receive data from socket 127.0.0.1:5555: Resource temporarily unavailable Warning: Data logging has been halted." on my sensors page. Well, not right away, but the moment the 1st data is received for data10 and data12 I get the error.

Sensor definition:
data20 power data10 sensoraddmaster 1 300
data20 power (greyed) data12 sensoraddslave 1 300

I'm also getting the following message in the meteohub.log:
logger (06.09.2010 08:45:40): child process received termination signal (11).
logger (06.09.2010 08:45:40): child process received termination signal (11).
logger (06.09.2010 08:45:41): child process received termination signal (11).
logger (06.09.2010 08:45:41): child process received termination signal (11).
logger (06.09.2010 08:45:41): child process received termination signal (11).
logger (06.09.2010 08:45:41): child process received termination signal (11).
(3-4 messages / second)

Looking at this a bit further, should there be a executable in /home/meteohub for this like sensdiff, or is this handled in a different way?

Also it appears to me that "sensoraddmaster is not following the same syntax as sensdiffmaster.

I tried to change the definition (for the purpose of the test) to:
data20 power data10 sensdiffmaster 1 300
data20 power (greyed) data12 sensdiffslave 1 300
But that doesn't work neither
Could it be that we are overflowing a buffer:
data10: 4479216.00
data12: 2750932.00

[admin]

I can confirm this bug. Seems like only NSLU2 is impacted. Will be fixed shortly.

[admin]

I fixed this bug. Please update again to 4.6p when you are impacted by this bug.

[YJB]

Thanks Boris, I can confirm that this is now working.

For clarity purposes the keywords are: sensaddmaster and sensaddslave.

As usual there is one more thing, is there a way to generate the data for this new sensor also based on my historical data?

Hmm, found a little bug as well:

4.6p_update.jpg (11.34 KiB) Viewed 8806 times

(yellow should read refresh, yellow is actually the color of the text that follows)

[admin]

good pick, should also be fixed by now... Next?

[YJB]

Thanks Boris, the color issue is now fixed as well.

4 questions:
- Can you update the manual to reflect the correct syntax: sensaddmaster and sensaddslave (and not sensoraddmaster and sensoraddslave)
- Can you show the none syntax in the manual in case you only want to trigger on the master: sensaddslave 1 none
- Migth be an idea to refer to the meteohublog for error messages since it might help debugging virtual sensor definitions (for instance I had a nice message:"logger (07.09.2010 07:48:07): processing "sensaddslave " does not return a value string, reason is: function has to be called with parameters "position" and "delay"." when playing with the "none" syntax
- is there a way to generate the data for this new sensor also based on my historical data

Thanks again!

[admin]

1) corrected
2) it is not meant to use sensadd/sensdiff/sensselect with just one sensor. Can you explain the need for this? I think regular use of virtual sensors do cover one sensor conversions
3) yes, will be mentioned in the manual
4) sorry, no.

[YJB]

Hi Boris,

I've got 2 sensors data10 and data12, these sensors are getting updated every minute.
I've got one virtual sensor defined: data20

Default definition:
data20 power data10 sensaddmaster 1 300
data20 power data12 sensaddslave 1 300
Since the sensor update will be triggered by both the master and the slave it will result in 2 updates to the virtual sensor every minute.
20100907032546 data20 724090900
20100907032548 data20 724091100
20100907032649 data20 724091400
20100907032650 data20 724091500
20100907032751 data20 724091800
20100907032752 data20 724091900

Alternate definition:
data20 power data10 sensaddmaster 1 300
data20 power data12 sensaddslave 1 none
Will trigger only on the master, and results in 1 update every minute:
20100907063349 data20 724237000
20100907063452 data20 724237800
20100907063554 data20 724238500
20100907063656 data20 724239200
20100907063759 data20 724240000

[admin]

ah, I remember. Manual will be updated to reflect this feature as well.

[YJB]

- is there a way to generate the data for this new sensor also based on my historical data

4) sorry, no.

Ok, I can understand possible reasons for not doing so. Since this is a one time excersise anyway, I will write a script that parses the raw data of all the previous months, followed by an aggregation (recompute) cycle.

[wfpost]

there seems to a problem with graphs.
When selecting actual year, the graph showing two years ahead instead of 1 year.

[Sedrani]

Hi Boris,
There seems to be a problem with Wd-Live day/night flag.
WDL continues to display only day icons.
I have a Davis Vantage Vue weather station.
Thanks.

Mauro

[YJB]

Try to run the following in your webbrowser:

Code: Select all

http://<ip of your meteohub>/meteograph.cgi?text=actual_daynight_flag_local

it should come back with either a "D" or an "N"

Also, make sure that you run the 4.6p version, since I'm not sure if this variable is already in 4.6o

Also, it this variable is not documented in the latest user guide

[Sedrani]

Thanks for your reply.
I launched the command on my web browser and the answer of the system was "N".
My Meteohub is running the 4.6p version.
Any idea?
Thanks!

Mauro