Well, then one should not use Windows either, nor Android nor Apple and many other software.
But I think we are getting off-topic here.
2 Likes
As HA focuses on privacy:
Open source home automation that puts local control and privacy first.
I would hope people also try to in-cooperate this when publishing guides around HA and prefer privacy respecting FOSS software which is more efficient (and faster) than other solutions which track/spy on the users without consent (and probably violates EU GDPR laws) and only works with ads.
Some decades ago spy- and adware were quite common but luckily this times are almost over.
Not sure about the windows and the apples (don’t use that) but my androids are free from ads/trackers (and google ware). Difference between win/apple to android is that you get a black box closed source OS which does whatever the manufactures wants - the later on the other hand is open source which allows privacy respecting interaction without tracking or ads. 
Feel free to move along when you’re ready.
This is a Community Guide not an excuse for you to be overly verbose.
4 Likes
I’m very much aware of that 
Just wanted to point out the facts as many people aren’t aware of it or know the implications of the software they are using 
Regarding etcher many people actually recommending it without knowing they are promoting adware with tracking 
So as a suggestion for your guide you might add the information that etcher includes ads and tracking (so everyone is aware before taking the decision using it) and maybe even give some alternatives like usbimager or rpi-imager (the later does include analytics) so people have a choice 
Hello, triyng to install on Debian 12 and getting an error on step:
dpkg -i homeassistant-supervised.deb
root@rpi4-20230612:/usr/local/src# dpkg -i homeassistant-supervised.deb
(Reading database ... 30664 files and directories currently installed.)
Preparing to unpack homeassistant-supervised.deb ...
[warn]
[warn] If you want more control over your own system, run
[warn] Home Assistant as a VM or run Home Assistant Core
[warn] via a Docker container.
[warn]
[warn] ModemManager service is enabled. This might cause issue when using serial devices.
Leaving 'diversion of /etc/NetworkManager/NetworkManager.conf to /etc/NetworkManager/NetworkManager.conf.real by homeassistant-supervised'
Leaving 'diversion of /etc/NetworkManager/system-connections/default to /etc/NetworkManager/system-connections/default.real by homeassistant-supervised'
Leaving 'diversion of /etc/docker/daemon.json to /etc/docker/daemon.json.real by homeassistant-supervised'
Leaving 'diversion of /etc/network/interfaces to /etc/network/interfaces.real by homeassistant-supervised'
Unpacking homeassistant-supervised (1.5.0) over (1.5.0) ...
Setting up homeassistant-supervised (1.5.0) ...
parse error: Invalid numeric literal at line 1, column 10
dpkg: error processing package homeassistant-supervised (--install):
installed homeassistant-supervised package post-installation script subprocess returned error exit status 4
Errors were encountered while processing:
homeassistant-supervised
root@rpi4-20230612:/usr/local/src#
What can be wrong?
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Welcome to the forum, DabbyAI 
Problems like this usually arise if one does not strictly follow the guide.
Note paragraph 1.5 and paragraph 1.6 (first section)! There is a reason behind the instruction to continue all after the OS installation as an unpriviledged user (but not as root) by prepending “sudo” (or “sudo -i”) to commands.
Furthermore disable ModemManager from starting after reboots:
sudo systemctl status ModemManager
If modem manager is running stop and disable it:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
Now make sure the latest NetworkManager is installed:
sudo dpkg -s network-manager
The output should show:
Package: network-manager
Status: install ok installed
If not, install NetworkManager:
sudo apt install network-manager
Just to make sure reboot the host:
sudo systemctl reboot
Now continue with:
cd /usr/local/src
sudo dpkg -i homeassistant-supervised.deb
1 Like
just solved this problem by enabling vpn on my router for this step
sudo dpkg -i homeassistant-supervised.deb
some resources seems to be blocked by my ISP 
Having problems with my DNS after installing network manager.
so when I get to this part
root@rpi4-20230612:~# curl -fsSL get.docker.com | sh
I receive this error
curl: (6) Could not resolve host: get.docker.com
Any ideas?
Probably NetworkManager messing with your settings. I’m betting your resolv.conf is overwritten by it and now it’s empty. This is a recurring problem to which I, besides a dirty hack, have no solution.
For now, put some dns entry in it, but count on it that NM will overwrite it again at some time.
Adding a DNS entry in HA’s network settings didn’t solve it for me.
/etc/resolv.conf
nameserver 1.1.1.1
1 Like
One solution to prevent resolv.conf gets overwritten with every restart of the host I have described here. Not a dirty hack but the change of a simple configuration variable within NetworkManager.conf.
1 Like
I’ll try that one Tamsy, thanks.
Do you also have a solution for preventing NM making a new connection profile on every boot? I have a whole bunch of them and they keep growing in number. Seached Google on this and many people have this problem, but no working solutions.
I never heard nor experienced such a behavior. Maybe this happens every time you manually set the DNS server through resolv.conf? I would delete all profiles except the main profile, configure NetworkManager.conf as described (don’t forget to add a DNS server to resolv.conf after having restarted NM) and watch whether this behavior is still happening.
It is indeed a strange problem, you can look it up yourself on Google should you be interested.
Deleting the profiles is tricky when doing so from a remote location, if you delete the active one you loose your connection.
Before your suggestion about DNS=none I changed resolv.conf’s attributes with chattr +i /etc/resolv.conf, making it read only
Well, that’s indeed a dirty hack 
Will do it later after I’m back home.
What do you see when executing from the CLI:
sudo nmcli connection show
root@pi344:~# nmcli connection show
NAME UUID TYPE DEVICE
Supervisor eth0 ec28412f-2106-48e2-9178-eff102a08002 ethernet eth0
Supervisor eth0 a599dac3-9b87-4cbd-a135-0d834153f6ed ethernet –
Supervisor eth0 2c40c00f-8c9a-4582-9015-894b2b58c8c2 ethernet –
Supervisor eth0 4f20ae74-c026-41a6-aa11-bea76c3c90fa ethernet –
Supervisor eth0 8a70959d-c364-4fb2-ad77-58119cc94a60 ethernet –
Supervisor eth0 d6e11048-c04f-426f-8333-26f3744a116c ethernet –
Supervisor eth0 c813899a-41fb-486f-924c-e045dedf6ef3 ethernet –
Supervisor eth0 f5226b2b-7610-4b69-bff3-b2b3494c4cae ethernet –
Supervisor eth0 5ec304b5-5f2c-42f5-aafc-ec22560f6ac5 ethernet –
Supervisor eth0 1e450762-1921-43b8-9f22-f5b99a33a475 ethernet –
Supervisor eth0 f0ecf4ad-5727-43d0-87e3-d8b4999d5344 ethernet –
Supervisor eth0 6ed24a1d-8ebf-45a9-8944-051bd54b99ce ethernet –
Supervisor eth0 84d670a7-3715-4a8d-9add-88a5691823ae ethernet –
Supervisor eth0 03b2521b-0316-470f-9743-55a8c57265ac ethernet –
Supervisor eth0 21455580-de3a-4b52-9069-ef797baff276 ethernet –
Supervisor eth0 964f0b82-dcab-4313-a804-9e0c2bd1cead ethernet –
Supervisor eth0 8717ecc3-3c31-47f2-8195-e5fe2461c098 ethernet –
Supervisor eth0 85233ad5-f8b6-4e6f-b8f8-ad65442bbc6d ethernet –
Supervisor eth0 7d89c902-b4a9-45d8-8266-ce5f30fb5b7e ethernet –
Supervisor eth0 874b8d5b-1af4-4662-ba08-c060939b62ea ethernet –
Supervisor eth0 21e18ec6-1fae-4ffd-8087-069e67c26bb4 ethernet –
Supervisor eth0 fd18e2b6-0882-411c-97b4-d935fbb00380 ethernet –
Supervisor eth0 1253a9c7-c90d-41bd-b3f7-535af4048738 ethernet –
First make sure to not to touch the active connection. Check by executing:
sudo nmcli connection show --active
Note the UUID of the active connection. Don’t tamper with this one!
While we could delete all the non-active connections by using only one command and some awk magic lets do this one by one starting from the bottom working ourselves up:
sudo nmcli connection delete uuid 1253a9c7-c90d-41bd-b3f7-535af4048738
sudo nmcli connection delete uuid fd18e2b6-0882-411c-97b4-d935fbb00380
all the way up to:
sudo nmcli connection delete uuid a599dac3-9b87-4cbd-a135-0d834153f6ed
Restart NetworkManager:
sudo systemctl restart NetworkManager.service
Now check the connection(s) again:
sudo nmcli connection show
You shoulds only see:
NAME UUID TYPE DEVICE
Supervisor eth0 ec28412f-2106-48e2-9178-eff102a08002 ethernet eth0
Finally configure nm to not to overwrite /etc/resolv.conf with every reboot as described earlier today.
1 Like
@Tamsy & @Patrick010 FYI - being a noob to some extent to Linux and Python (I have HA Supervised running on a RPI4 w/8Gig of Ram and not using any microsd card but a 1tb samsung T7 SSD) - I am not upgrading yet, but earlier when I did sudo apt update and sudo apt upgrade I did have some container related upgrades which caused by HA Supervised to be unhealthy (cgroup version issue). So I reran “curl -fsSL get.docker.com | sh” and homeassistant-supervised.deb but those did not resolve the issue. So “for fun” I did try the in-place upgrade to Debian 12 anyway (which is probably a bad starting point from trying same) but that did cause me to have both two of the “Supervisor eth0” entries above, and DNS not resolving either (able to ping 1.1.1.1 but not google.com for example). So, I just restored from a backup and will just do the full - from scratch - Debian 12 install later. Tamsy you may remember that following your and kanga-who’s instructions I did have that DNS hiccup which I resolved so I am digging to find out what I did before to resolve that issue. When I do the reinstall from scratch for Debian 12, I will very thoroughly document any resolution I do for the DNS issue (if I have that iossue again) - so you can decide where or if to include that with your installation instructions -
I have done this countless times, but the entries keep coming back. No idea what’s causing it
You made this clear before. What I am wondering about is does it still happen after you made the change to NetworkManager.conf (and restarted nm)? 
This should have been enough to resolve the issue:
1 Like