Backup contains `image.tar` file

[svasek]

Hi @Dattel,
Thank you for you work on this addon.
I found that in Home Assistant backups, your add-on includes a fairly large file called image.tar in the archive.
The solution would probably be to add the backup_exclude option to config.yaml.

Thanks,
Miloš

[Dattel]

Hi @svasek,
thanks for your suggestion. I'm not sure, how the backup actually works but figured out, that this addon is not the only one which stores an image.tar file inside the backup. It seems to be docker-related. Maybe the reason is that the addon builds it's very own image during installation instead of pulling a prebuild docker image from git.

So if i would simply ignore the image.tar on backup, i guess it would probably prevents a restore.

Aside from that im not sure, if it's worth the keep this addon up to date. As you can see, there are no updated for a couple of month now. Influx 3 is released and i personally still store all my longtermdata inside of a influx1-db (in parallel to influx2). But i figured out, that there are way more migrationplans from influx1 to other storages (e.g. victorian) as from influx2. It looks like influx2 is an unwanted child?!?

But you can convince me that it's worthwhile to keep an Influx2 plugin alive.

[svasek]

Well, to be honest, I’m considering stopping the use of Influx, since Home Assistant already provides statistical data directly.

[Dattel]

Indeet - but you are more flexible in designing your own grafana-Dashboards using your own database
Especially since Homeassistant uses downsampling for older data.

I'm considering switching my data to victorian-metrics