I’m trying to switch from gsync to the official backup solution but … I have issues:
My backup size is now ~4.7 GB , mainly because of influxDB which has ~3.6GB.
My wishes:
Have more than only 1 backup
Use different locations
Include (at least from time to time) also InfluxDB addon
Problems:
If I include all addons, then I can keep only 1 backup in NabuCasa cloud, and max 2 (or 3) in google drive
If I don’t include InfluxDB … I loose the DB long history
If I don’t include influxDB but create an automation to run the full backup only … from time to time (e.g.: 1 per week, not each day) , then … how should I proceed so that I have space for it on google drive ? (do i need to delete an existing one manualy)
If I create (automation) only from time to time the full backup (including InfluxDB) only on the NAS … then … how to make sure that I keep only … 3 …or 5 … such backups … ?
So … lot’s of uncertenties because my big backup size …
What do you suggest me ?
Looks like this is a regression caused by the switch to the aiohttp mdns resolver. Since I used DNS hostnames (in dnsmasq) for machines via wireguard, the new resolver can no longer find them. Adding them by IP address works, but it’s a bit ugly. I’ll open a bug tomorrow.
When there is addon update prompting, I turn off the toggle to backup the addon before updating… But the addon is still being backup?? Do you guys see this behavior too??
Can anyone please clarify the new broadcast intent. There’s very little about it in the notes. Will it only work with Voice PE, or can I use other media players? If I can use other media players, can I select which ones? Thanks in advance
Awesome work!
Thanks a lot to all of the team working and contributing the development of Home Assistant! You guys listened to feedback, suggestions and critics and communicating cleary where you can follow those comments and where not (backups and NabuCasa, p.e.).
Very much appreciating the effort you all made (also, to everybody giving serious feedback).
This (and also the former) update is great step forward! I ( as I am not skilled enough to support Home Assistant Dev myself) hope, this project will lasting long and be updated to stay at state of the art. I am highly impressed and thankful. Keep goin!
I’ve configured my Synology as target for backup.
Scheduled backups work.
Just now I did an add-on upgrade with the backup toggle on.
The backup is local only and not on my Synology.
Is this by design ?
I have added Google drive (backup) yesterday.
It requires you to setup an authoriztion for your home-assistant instance to access your Google drive through google api.
While doing that, you will get a ClientID and a Client secret from Google.
And then you also need to add the “Google drive” integration in HA.
Then you provide the integration with the Google Client info you got before.
Its a bit labourious.
(look at the section Scenario 2: You do not have credentials set up yet)