meteohub.de

DEUTSCH:

Dieses experimentelle Update hat WD-Live analog dem Dashboard integriert und beseitigt einige Bugs. Desweiteren wurde ein obligatorische einmalige Bestätigungsfunktion für die Lizenzbedingungen für Meteohub und WD-Live integriert. Die WD-Live Funktionen sind noch nicht voll ausgetestet. Feedback ist willkommen.

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

Änderungen gegenüber V2.6a:

* Beseitigt einen Fehler der zur wiederholten Ausgabe von Regenfall beim Export nach WSWIN und WD führen kann.
* Erlaubt das rekursive Hochladen von Inhalten im "/public/uploads" Inhaltsverzeichnis via FTP.
* Enthält eine Evaluierungsversion von WD-Live für lokale Tests. Zur Einbindung von WD-Live auf dem eigenen Web-Server bitte ein entsprechendes Package hier herunterladen: http://www.weather-display.com/wdlive.php
* Verlangt bei der erstmaligen Benutzung oder nach Änderung der IP nach einer Bestätigung der Lizenzbedingungen für Meteohub und bei Auswahl der Wd-Live Option für WD-Live
* die Variablen actual_daylength_standard_hh:mm, actual_daylength_civiltwilight_hh:mm, actual_daylength_nauticaltwilight_hh:mm wurden umbenannt in actual_daylength_standard_hhmm, actual_daylength_civiltwilight_hhmm, actual_daylength_nauticaltwilight_hhmm.
* Kalibrierte Werte der relativen Luftfeuchte werden auf Werte von 0 bis 100 begrenzt.
* Verkürzt das WD-Live Update-Intervall auf eine Minute.
* Hebt die Beschränkung der Icon-Größe von 10KB auf.
* Das Handbuch wurde aktualisiert.

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

ENGLISH:

This updates introduces an integration of WD-Live like the Dashboard in Meteohub. WD live support is still experimental. To get things formally right, a one time click license agreement for Meteohub and WD-live must be processed.

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

Changes since V2.6a:
* Fixes a bug that causes events with duplicate rainfall when exporting data to WSWIN and WD in an 1 minute time schedule.
* Supports recursive FTP uploads of contents in directory "/public/uploads".
* Includes an evaluation version of WD live for local testing. To get WD live working on your own web server please have a look here: http://www.weather-display.com/wdlive.php
* Requires a formal acceptance of license terms of Meteohub and WD Live when using Meteohub for the first time or after an IP change.
* Limits calibrated humidity values to a rang from 0 to 100.
* Increases update interval for wd-live to every minute.
* Removes the size limit of 10KB for icons.
* Manual has been updated to reflect recent changes.

Since updating to 2.6b this error with WD-Live occurs:
Ungültige CRON Zeitangabe "" für Upload "WD-live".

the WD Files are no longer uploaded to my webserver.
Is it intended that the upload interval for WD-Live is fixed to one minute and cannot be changed at all?

I have put the download of the update on hold for a while, and fixed this problem. Download of fixed 2.6b is now working again, please give it a second chance. FTP uploads for WD-Live should work now ok.

admin wrote:I have put the download of the update on hold for a while, and fixed this problem. Download of fixed 2.6b is now working again, please give it a second chance. FTP uploads for WD-Live should work now ok.

Yep, it works fine now. Thanks!

wfpost wrote:Is it intended that the upload interval for WD-Live is fixed to one minute and cannot be changed at all?

I'm also interested in an answer to that.

I realise that this is still experimental, but more control over timings of the various files would be appreciated - nice also to be able to set the external filenames individually too (as for the other CRON jobs).

PS. Not everyone who uses the clientraw files uses them for WDL.
A number of other systems use them as a generic near-real-time data format. :)

There 4 files to upload. the clientraw and clienthour are updated and uploaded every minute, clientdaily and clientextra every 15 minutes.

I thought it would be more easy for users to get this "pre-packaged" by just selecting one wd live upload. Do you really think it would be an improvement to have all these four files on individual target names and upload schedules? I could do that... no problem.

admin wrote:I thought it would be more easy for users to get this "pre-packaged" by just selecting one wd live upload.

I think that is an excellent easy to use option for standard WDL use.

Do you really think it would be an improvement to have all these four files on individual target names and upload schedules? I could do that... no problem.

I think that it would add a great deal of flexibility for testing and for non-standard use if it was possible to specify the individual client* files on the "Graph Uploads" tab.

That would both allow:

a) custom timing (though presumably never faster that the 'standard' - I have no problem with that)

b) custom naming - e.g. for testing[1] or for other reasons[2].

Does that make sense?

Just suggestions. In the end it's your software. Your choices count. :)


[1] At present the only way to see what is produced is to set up a CRON job, which for me would send the files to a location already receiving live client* files from another source - unless I temporarily change the upload location, but that would mean that other active MH uploads would be sent there too instead of to the live location.

[2] e.g. My website already uses a MH generated html template file as an automatic 'fallback' for when WD isn't running (based on php compare of file date/times). If differently named client* files from MH were available the fallback mechanism could switch to those instead of the more limited html template file.
The idea being that the WD produced client* have precedence because (so far as I am aware) they contain 'richer' data at present because they also incorporate data not available to MH (I'm mainly thinking of the 'Temp in a Jar' solar and of 'current conditions' ).

I would go for at least allowing to set the update interval.
Let´s say, one switches off the DSL Router at night from 1-6 o´clock, I fear the alarm log will get flooded with entries.

Maybe it´s possible to have two variables
One fully automatic
WD-live
and another one manuel
WD-live-manual

I know, that me be confusing to some.

A general question about WDL.
Can the WDL applet embedded in the exact way the dashboard can be used?
What I mean?
When embedding the dashboard into a website, there´s no need to upload any sensor data, the data will be called from meteohub when the dashboard is opened.

For WDL all data is in /myweb/uploads folder
So when I was to have the WDL code written into an external website, but refer to the local meteohub url (with DynDNS), would that work, or would it bring up a serial number or any other issue with WDL?

That method would not need me to upload any WDL files to my webserver. The same as with the dashboard.

As far as I understand the limitations of flash, it does not allow an applet to load code not located on the same url as the applet itself.

So having the applet on a web server and requesting data directly from a folder on your meteohub will not work.

what should work is, when you refer to the applet and the data at your meteohub folder "http://mymeteohub.dyndns.org/myweb/uplo ... config.xml".

I have not tried this...

what also should work, is using these tags in wdlconfig.xml
<clientraw>http://adr.homedns.org/myweb/uploads/cl ... /clientraw>

<clientrawextra>http://adr.homedns.org/myweb/uploads/cl ... ntrawextra>

<clientrawdaily>http://adr.homedns.org/myweb/uploads/cl ... ntrawdaily>

<clientrawhour>http://adr.homedns.org/myweb/uploads/cl ... entrawhour>

But, it doesn´t work:
Always "Error loading data ..."
But I can open the four clientraw-file-urls in the browser without any problems :dry:

Opps: Isee, it´s what you mentioned:
If however the files are in a different location then enter the full path to each file in these boxes. Note that the domain must be the same as your WDL swf and configuration xml file. If they are not then WDL will not load the files. This is a security feature within Flash itself.

That would mean I needed my serial number changed :unsure:

This parameter contols the above security?
<param name="allowScriptAccess" value="sameDomain" />