meteohub.de

DEUTSCH:

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

* Der http data logger liefert bei Weglassen eines Zeitraumen die aktuellen Werte für alle aktiven Sensoren. Dieses Verhalten verbessert die Anbindung an WD. Die im vorangegangenen Update eingeführte Möglichkeit zur Einstellung des sofortigen Schreibens von Rohdaten sollte nun nicht mehr notwendig sein und das Speichermedium entsprechend geschont werden können.
* Verbessert das time-out Verhalten beim Lesen von via TCP/IP angebundenen Wetterstationen.
* Beseitigt einen Fehler, dass beim Vorhandensein sehr vieler Sensoren (mehr als 40) die Sensoren Seite nicht mehr angezeigt werden kann.
* Meteohub erstellt zum Export in WD die Monatsdateien "MMYYYYextralog.csv" und "MMYYYYlg.txt" nur noch auf manuelle Anforderung auf der Seite "WD Datenexport". Die Übertragung von Live-Daten an WD erfolgt nun ausschließlich über die HTTP-Datenlogger Schnittstelle.
* Meteohub erstellt zum Export in WSWIN die Monatsdateien "EXPmm_yy.csv" nur noch auf manuelle Anforderung auf der Seite "WSWIN Datenexport". Die Übertragung von Live-Daten erfolgt wie bisher über eine WSWIN Dateiüberwachung, die auf die Meteohub-Datei Datei "import.csv" gerichtet ist.
* Die auf der Seite "Grafiken Hochladen" angegebenen Dateien werden zur Entlastung des Flash-Speichers per Voreinstellung nicht mehr in den Ordner "/public/myweb/uploads/" kopiert. Falls dies doch erforderlich sein sollte, kann eine entsprechende Option auf der Seite gewählt werden.
* Es erfolgt eine Warnung, wenn ein Wetternetzwerk ausgewählt wurde aber noch keine dafür zu verwendenden Sensoren definiert sind.

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

Update to Meteohub V4.5g (NSLU2, x86, SheevaPlug) brings these features:

* Changes behavior of http data logger when called without a time frame in a way that it now reports all actual sensor data. This improves working with WD. Option introduced with last update that allows to write raw data the moment it is detected should no longer be used. It is not recommended to make use of immediate writes because this adds wear to storage media.
* Improves time-out handling of weather stations connected via TCP/IP.
* Fixes a bug that results in an empty Sensors page when too many sensors (above 40) detected.
* Meteohub generates monthly data files ("MMYYYYextralog.csv" and "MMYYYYlg.txt" ) for export into WD on manual request only. Transfer of live data to WD can be realized by making use of Meteohub's HTTP data logger interface.
* Meteohub generates monthly data files ("EXPmm_yy.csv" ) for export into WSWIN on manual request only. Transfer of live data to WSWIN can be realized by directing WSWIN's file control feature to Meteohub's file "import.csv" as with previous Meteohub versions.
* Files listed on page "Graph Uploads" are no longer copied to local folder "/public/myweb/uploads/" to reduce wear of flash storage. If these copies are still needed, this option has to be switched on separately.
* Meteohub gives a warning when a weather network has been selected without having defined sensors to be reported.

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

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

Hi Boris,
thanks for new version ... I use MH together with great forecasting sw called WXSIM. WXSIM import data from local weather station via WDlog. So I've now WDlog just for request. It's bad because my forecasts stoped. Can You give back ongoing WDlog for us ? As possibility with checkbox ?
I and my friend choosed MeteoHub for this feature.


Thanks


Mike

New behavior for uploads:
If I activate the checkbox " individ. Zeitplan
Lokale Kopie in "/public/myweb/uploads/" anlegen", it stays still empty. But it works..

Why not use a small Ramdisk for uploads?
My Alix uses only
Mem: 256760k total, 78368k used, 178392k free, 6452k buffers

then a default 8M Ramdisk like prepared should be enough:
meteohub:/data/myweb/uploads# dmesg | grep RAM
BIOS-provided physical RAM map:
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize

I use 6MB in uploads:
meteohub:/data/myweb/uploads# du -h .
6.3M .

That will not harm flash...
Big static files like wdlive could be still linked outside RAMDisk.

Good Source:
http://www.vanemery.com/Linux/Ramdisk/ramdisk.html

Just as an update...

WD export files are not generated correctly. I have a bug fix for that, which will be part of next update.

I am also working on a regular WXSIM support, but this might take a few moments more.

Ramdisk is fine on sheeva, ebox and ALIX but NSLU2 can hardly handle that. However, the tempdir where all the graphs are generated before being uploaded and deleted again is on ramdisk (/var/run/meteohub/uploads/). Difference from the localcopy folder is that files get erased after beiing uploaded, so they don not accumulate there. As said in the announcement of 4.5g, I don't believe many users need local copies of generated and uploaded data. This just makes sense if Meteohub is used as a web-server for itself but I do not recommend that because of security and performance reasons.

Just for completeness:

I read always about security.
I agree, that Meteohub is not intended to be directly accessible over Internet.
I prefer A Reverse Proxy to access Meteohub over any solution using a ftp session. scp or better sftp are already on base system. Just no GUI. Also rsync is here. If You really address security, ban ftp.
I know that many "experts" rely on ftp, because it is easy and just works.

Yes I am Network/Security-Engineer in real life and therefore a bit of professionaly paranoid.

On the Meteohub side using an FTP client does not add security risks from my point of view. You might by cautious of using a FTP server on your web server, but that is another story.

Anyway, when you have SLC storage on your ALIX flash wear might not be an issue at all.

Such discussions tend to be endless ;-)
But sorry, that point of view is simply wrong.

Just try a cheap V-Server Company, sniff a few days the traffic on Your own V-Host and you will see, that many neighbours use ftp. No matter where the client and where the server is. You get a lot of accounts including passwords, still in 2009. And when meteohub is involved, You will see the credentials every 5 Minutes. It is the cleartext that matters.. And most users do not even create a separate ftp-account for this, they use wide open admin rights.

Anybody seen such demos, no one uses ftp anymore..

Hello,

i've updateted my Meteohub to 4.5g an get an Error about the USB-Interface. The connected Weatherstation is a WMR200, the Computer is a Alix 1.D, bought with Meteohub installed.

The "meteohub-log" reports also a lot of errors. Theese are the last Lines of the Log:

And here the System-Informations

netsigi wrote:.... no one uses ftp anymore..

I don't think so. B)

Ettershaus wrote:Hello,
i've updateted my Meteohub to 4.5g an get an Error about the USB-Interface.

What version did you updated from?
You did not had that errors before?
Are you using a USB HUB or did you change USB connectors on your ALIX?

I ask because I don't remember that I have touched that USB code in the last updates.

Hello,

i'll i update from Version 4.5d :-)

The WMR200 is connected direkt to one of the USB-Ports of the Alix.

This is a bit misquoted, the "if" part is missing.

Anyway, there is always room for improvement.

Like:




;)