Hi, I am very new to DietPi and also home assistant which I am playing with on a VM and now trying to migrate to DietPi + nanopi R2S dedicated device.
I noticed that when installed via ‘dietpi-software’ the home assistant install there uses the ‘python environment’ install method from HA… is there a reason for prefering this method of install vs. “home assistant container”?
It seems like when I migrate from home assistant OS to either container or dietpi’s python-env mode I no longer will have access to addons: Installation - Home Assistant - any suggestions here on to make some addons I have installed now available? looks like i may have to figure out how those addons work and manually run them in docker?
For my second question (first question still open): how to backup ‘home assistant container’ (or maybe my entire DietPi install?) I am thinking I could use duplicati by mapping /mnt/dietpi_userdata/ folder as the ‘source path’ as shown in this tutorial Backing Up Home Assistant Container to Google Drive with Duplicati - YouTube
But the challenge, doesn’t matter which guide you are using, is with the network-manager package as it is conflicting with ifupdown package we use on DietPi.
I have RPI 2.
Will this not kill my SD card?
How many space Home Assistant needs?
I have already 8 GB SD Card and can’t install on it (to less free space).
I have running these softwares on raspberry pi-2 with dietpi & all these are running happliy since two years with usb ssd.
homeassistant
zigbee2mqtt (manual install)
mqtt broker
vaultwarden
adguard home
unbound
wireguard
ftp file server
samba file server
sftp server
dietpi dashboard