62GB! Hectic.
Well, that is one of the reasons why I only backup my config files on github. See
https://github.com/tinuva/home-assistant-config
In fact, I now added a step, that it actually tests my config against future updates.
Sadly only I can see the logs of the actions, eg at
https://github.com/tinuva/home-assistant-config
But what is inside is the following.
1. config tested against stable:
Code:
Run version="stable"
ghcr.io/home-assistant/home-assistant:stable
Run matcher="/home/runner/work/_actions/frenck/action-home-assistant/v1.3/matcher.json"
Run docker run --rm \
2022.4.7
Testing configuration at /github/workspace/.
INFO:homeassistant.util.package:Attempting install of msmart==0.2.2
2. config tested against beta:
Code:
Run version="beta"
ghcr.io/home-assistant/home-assistant:beta
Run matcher="/home/runner/work/_actions/frenck/action-home-assistant/v1.3/matcher.json"
Run docker run --rm \
2022.5.0b3
Testing configuration at /github/workspace/.
INFO:homeassistant.util.package:Attempting install of msmart==0.2.2
3. config tested against dev:
Code:
Run version="dev"
ghcr.io/home-assistant/home-assistant:dev
Run matcher="/home/runner/work/_actions/frenck/action-home-assistant/v1.3/matcher.json"
Run docker run --rm \
2022.6.0.dev20220430
Testing configuration at /github/workspace/.
INFO:homeassistant.util.package:Attempting install of msmart==0.2.2
Obviously not fool proof, but it gives me a headsup. The only thing I lose, is the history on metrics, but then again give it a week and those are all back.
I also have my influxdb running on a separate vm so that is handled separately.