Installing Home Assistant Supervised on Debian 11

I can confirm, upgrading to Docker 20.10.5 has resolved my issues. Thanks!

I have reinstalled home assistant and now it is working. I think something else went wrong in the first place.

1 Like

Although I love this site, its search sucks, so sorry if this was asked before, I can’t find it.

On Rasbian, it’s easy to turn off the Pi’s LED. Those commands do not work in Debian so the question is, how to I turn off the red and green light on a Raspberry Pie 3B running Debian 10?

Thanks

I installed Home Assistant Supervised on Debian 10 on a Raspberry Pi 4. All working properly so far. However, what I’m missing is being able to address the GPIO ports.

With HASSIO this worked previously. So the hardware ports are ok.
Are there any suggestions on how to achieve this with Debian 10?

My previous crappy SSD failed after just three months, and now I’ve put some effort into reducing disk writes to try and extend the life of the new one.

I put it on paper, should anyone be interested…

Sorry if this the wrong thread to post this, but I think the answer to this question may be related to how I have installed HA (supervised on Debian Buster/64 on pi):
What is the currently recommended method for a complete backup of the complete pi installation, not just HA supervised through snapshots (I mean the whole system-bootable or .img)? I boot from an SSD connected to a USB3 port. Ideally I would like to automate such a procedure at a given time point. Target could be an SD, USB stick/HDD or network. I’ve run across https://github.com/billw2/rpi-clone and https://github.com/framps/raspiBackup along with various other tutorials/methods. But they usually talk about SD backups etc. and it seems that the whole procedure could be a tad easier (GUI oriented). Why can’t more “mainstream” solutions be used, like for example https://www.bacula.org/ ?
Finally, I see in all tutorials that it’s recommended to stop various services before the actual backup process is started. Which services should be stopped in HA supervised installation before a complete backup?

You’re always going to have to stop a boatload of services to make a reliable backup on a running system.

The only recommended way to backup an entire system drive is :
*shut down system
*clone the OS drive, using something like Clonezilla.

However, if your Pi is only running Home Assistant, then there’s really no valid reason to avoid using the snapshot feature. Make sure your snapshots are stored outside of the Pi.

Whichever backup method you select, you will always have to restore the system image. Might as well re-install Debian and install Home Assistant, and restore your latest snapshot. It would take about the same time as restoring a full system image, or any other kind of total backup.

All-in-all, this is pretty far removed from the original topic.

Thanks for the prompt answer. I also hinted that the question is removed from the topic, but I thought it could be considered relevant for users with a similar installation.
Your recommendation seems sound, albeit not automated. And it involves completely shutting down the system for a relatively big amount of time, which I’d like to avoid. Unfortunately I don’t run only HA, thus I opted for a supervised installation, in order to be able to use Pi for other purposes too. So, I’ve tinkered a lot with Linux and other settings in my installation, which I wouldn’t want to lose in case the SSD fails.
I find it a little bit odd that a simple full backup of an installation seems so complicated in Linux, but then again I consider myself relatively unexperienced in this field yet.

well, doing a backup on a live system is tricky, on every OS.
If you’re willing to take chances regarding restorability, then you’ll be fine without shutting down, and you can automate.
If you want max restorability, you’ll need to shutdown & go manual.
You could also do smt like this : https://askubuntu.com/a/7811 … but the more you personalize your system, the less likely this will work as expected.

This is where hypervisors (Proxmox & co) really shine. Live backups, zero downtime, 100% recovery.
It all depends on how far down the rabbit-hole you want to go.

1 Like

Ok, I guess I’ll have to research further.
One final question, in case I went with the manual procedure for the time being: I suppose the concept is to simply attach the bootable ssd to another Linux installation and clone it to target. Can eg. Clonezilla or any other solution actually do that? I’d immediately think yes, but all tutorials I came across refer to a situation, where you actually boot from their live usb and clone the bootable drive to target. I just want to clone the connected (bootable) Pi ssd in a VM Debian 10 to target.

i don’t understand what you’re saying.

I have Debian 10 in a VM. I was thinking of using that, in order to physically connect the Pi ssd and clone it to target (usb stick/HDD). Can I do that with Clonezilla or any other software? Sorry for my English.

Yes, that would work with clonezilla (or any other disk clone tool).

I use a cronjob running a script to backup my user folders which contains my docker (non HA) persistent volumes. Using that with snapshots I can restore my system in under an hour. I have never tried to backup stuff I have installed in Linux I just note in a text file what packages I use and manually reinstall them… that could be automated with a script if you needed…

Agree. I still prefer straight debian and I run everything extra in docker which is easy to backup so I just need to know the 10 or so packages I need to add.

It seems that I’ll have to put clonezilla on the usb that I want to put my backup and boot a pc from this usb https://clonezilla.org/show-live-doc-content.php?topic=clonezilla-live/doc/03_Disk_to_disk_clone
Then the target gets overwritten by the backup.
Odd that no simple interface exists to just “clone a connected source to a connected target”.

Could you please elaborate on the cron script? And what is the target?

*Any backup script will require you to first install an OS before giving you the opportunity to restore your backup. If you haven’t properly documented your installation, you will shoot yourself in the foot.

*Regarding Clonezilla, either you boot from the LiveCD (usb) or you install Clonezilla as an app in a pre-existing Linux OS (sudo apt-get install clonezilla).
You connect source & target drives, and you clone from one to the other.

Target is a USB-Drive.
The script just tars the user folders and copies it to dropbox and also the USB-drive