So I understand this, does that mean node red does not run well inside home assistant in a container, in bullseye?
No? Node red runs fine.
If you’re doing a supervised install you should install the addon for it and let supervisor setup and manage the docker container. You should not create and start a container yourself from a node red public image using the docker cli or docker compose.
In a docker install do the opposite. There’s no supervisor so there’s no addons. If you want node red then find a public image (or build one) and create and start a container from it yourself.
I think I understand😅
I am having trouble installing some nodes in node red.
One for sure is Govee bt.
It gave me some python errors then npm errors.
I had all this node red working on a rpi3b.
Then started down the home assistant rabbit hole.
Ending with a nuc running bullseye and going to get the nuc to manage the node red things also.
I won’t do it, but it seems I could install node red in root of bullseye and in home assistant.
I have node red up and running with a simple MQTT flow in home assistant/node red so I know it works.
Thanks for the help.
1 Like
Hi folks!
I used this method without any issues. And HA worked great. Until one day when it started to give me some weird errors. Maybe they are not related to what I am about to tell you later on. But just in case. The error I got was the following while trying to update HA and addons inside of HA: ‘AddonManager.update’ blocked from execution, system is not healthy>>
Anyway I decided to reinstall everything from scratch. So I did a fresh reinstall of Debian 11 and followed the rest of the steps, including the ones is Section 3, my ethernet connection stopped working. I pinged the pc HA is running on and it gives me time out. I don’t believe I have an IP Address anymore for the ethernet card.
I executed the commands via ssh so for sure everything was working until the last step 3.1
BTW, when I physically type ha core check, I get Error: Can’t execute command. Details in the attached pic.
I tried the process to reinstall Debian 11 and then HA 2 times. Any idea what I am doing wrong? Or it’s not working anymore? Thank you!
I just saw there is a bug present which breaks the network.
I saw there is a solution.
Enabling “Automatically connect” with nmtui seems to fix this issue.
Newbie here. What does that mean? What exactly should I do? What command should I send?
LE: I found this 16.04 - How to trigger network-manager autoconnect? - Ask Ubuntu
Executed this commandnmcli device set IFNAME autoconnect yes (where IFNAME is my ethernet name) but I still have same issue.
If you are referring to the first problem, it is too late for that now as I did a fresh reinstall. But thank you so much.
Now I am stuck with the other issue which it seems to be a recent issue. @Markymark posted this link above: https://github.com/home-assistant/supervised-installer/issues/217
From my understanding, the last version of HA breaks the network of the host OS. Any idea what version to install and how to actually install an older version of HA?
A PR has been merged to the installer which may address the network issue.
Hi,
I was getting this error and I applied your suggested fix.
However I am still getting this error 
`E: The repository ‘Index of linux/ubuntu/ bookworm Release’ does not have a Release file.
I am doing this on Rpi 4 (4gb ram)
sudo apt update && sudo apt upgrade -y
Hit:1 http://deb.debian.org/debian buster InRelease
Ign:2 https://download.docker.com/linux/debian bookworm InRelease
Err:3 https://download.docker.com/linux/debian bookworm Release
404 Not Found [IP: 18.67.111.89 443]
Hit:4 http://deb.debian.org/debian-security buster/updates InRelease
Hit:5 http://deb.debian.org/debian buster-updates InRelease
Reading package lists... Done
E: The repository 'https://download.docker.com/linux/debian bookworm Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
my /etc/apt/sources.list
cat /etc/apt/sources.list
deb http://deb.debian.org/debian buster main
deb-src http://deb.debian.org/debian buster main
deb http://deb.debian.org/debian-security/ buster/updates main
deb-src http://deb.debian.org/debian-security/ buster/updates main
deb http://deb.debian.org/debian buster-updates main
deb-src http://deb.debian.org/debian buster-updates main
Did some more reading, could it be because I installed Debian 12? I just went to this page and got the latest, Tested images. I see a few comments suggesting version 12 is not supported.
@kanga_who I wonder if adding to your guide could help noobs like me not download the wrong version And then spending hours not understanding why it doesn’t work
adding to your guide could help noobs like me
This installation method is not meant for noobs!
This method is considered advanced and should only be used if one is an expert in managing a Linux operating system, Docker and networking.
This comes from ADR-0014
1 Like
Fair enough, I am just happy I figured it out on my own, It’s working now 
This guide is not for a Pi, there is a seperate guide for that.
The name of the guide is “Installing Home Assistant Supervised on Debian 11”
1 Like
No worries, agreed! I think that’s what’s go me relaising I was on the wrong path
Sorry I must have had both guides open, I was following the Pi guide and posted on the wrong one, sorry
This works! 
well done and thank you 
Super!!
Thank a lot!!
Works like a charm. Just installed Debian 11 + HASSIO Supervised on a Dell Laptop.
Thank you!
Is this still relevant - given that these instructions were posted in MAY 2020? (post #1)
It is. The OP keeps it always current (last edit as of today): 10 days ago.
4 Likes