Smarter recorder

Feature Requests
1

It would be much more useful if the recoder handled entities in the following ways:

  1. There are entities for which it is enough to store the statuses of the last x days. The recorder knows this now.

  2. There are entities that should be stored forever, for example PIR sensor, light, heater, … There are not many of them and they do not generate much data.

  3. The most important thing: there are entities that generate a lot of data (for example, consumption meters, thermometers, …), it would be enough to store them in the long term statistic table, but not in the states table. Currently, a three-phase consumption meter generates 100,000 records per day, which must be deleted manually.

2

I agree. So far the only solution is to set two recording servers and set one to record short term data and the other to record long term data.

For some reason, you cannot have two databases on single server - one for short term and the other for the long term data. You have to run two different servers. For example MariaDB and InfluxDB. Or at least I could not find way how to set two databases on for example MariaDB.