Archiving: best practices recommendation

[Warichet]

Hi,

I want to save some statistics (list) for further reference.
Some every week, some every month.

I know it can be done with the UZSU.
I would appreciate some guide lines on best practices about how to do it right, or a pointer to a doc if it has already been described somewhere.


Thank you.

[Michel]

There are no guidelines available.

It depends on your special needs and the data you want to archive. The only thing I would think about is how to work with the archived data in future and to choose the proper format (xls,html etc...)

So my guideline would be: Just do it!

[Warichet]

The only thing I would think about is how to work with the archived data in future and to choose the proper format (xls,html etc...)

Thank you for the quick reply.
I guess I didn't make myself very clear.
The question was more about the setup within the UZSU.
Should I fill-in dates for a whole year in advance ? or work with calendar ? can it be donce cyclic ?
Could I arrange things in such a way that a List gets archived every week and restarted clean again. And the same for a monthly archive of another List ?

Thank you for your patience.

[MatthiasS]

It can be done cylic.

You can use placeholders (button) "**" in order to say: every first day in month and so on....

[makki]

As I think to build a seperate solution for graphing (of archived values etc.) with mrtg and/or rrdtool due to the limited possibilities of the HS in long-term recording/graphing for analysis purposes anyway, I currently simply save every Archive&List (configured as circular with the max possible) as CSV daily to the NAS daily triggered by "Neuer Tag".
This gives the possibility to get data from any point in time, concat if required and simply open&report in Excel or similar..
The "storage-cost" is imho negliable with Gigabytes available nowadays; my archives for two months take 20MB currently..

Makki

[Warichet]

As I think to build a seperate solution for graphing

I thought about it as well, but I'd like to stick with an integrated solution on a single box. I think it would make it easier to display the graphics in the Visu (although, I might be wrong here, with cMove many things are possible).

due to the limited possibilities of the HS in long-term recording/graphing for analysis purposes

That wan't please everyone

triggered by "Neuer Tag".

Ah ?!? is that a system parameter ? something available in the HS ? Maybe I missed it.

Suche nach Neuer Tag liefert keine Treffer.

[MarkusS]

http://www.dacom-homeautomation.de/l...d=51&Itemid=78

Bausteine 17556 und 17557 von Gaston.

Man kann sich natürlich auch eine "neuer Tag"-Schaltuhr bauen.

Gruss
Markus

[Warichet]

Hi,

Suppose that I've already a list, i.e. dayly temperature.
I want the archive to be closed every end of month and restarted anew for the next month.

Could someone be so kind to give a short list of the steps needed in order to setup such a cyclic archive ?

[MatthiasS]

This is not possible. You cannot close an existing archive. All archives are cyclic.

What you can do is to send an archive at the end of the month by email. If your archive contains data for exactly one month, each archive contains data for one month.

[Warichet]

This is not possible. You cannot close an existing archive. All archives are cyclic.

OK
I thought I'd already seen something similar
Would it be possible via List ? so putting data in a List and starting a new List every month and archiving the old one ?