Hey there!
It seems everything went thru normal, but I can’t open HomeAssistant thru the normal mode
xxx.xxx.x.x:8123. It shows me “The site cant be reached”
1 Like
I don’t see the homeassistant container in your docker list.
And supervisor does not like portainer running…
Is there any particular reason you chose the Supervised install method?
I need the supervised, because of the many additions it offers.
That doesn’t look like debian 11. Raspbian is not debian.
1 Like
if you start it, you can see the log in portainer
Or by typing
docker logs homeassistant
It says BullsEye and 11, codename Debian. When I installed I used the Debian 11(bullseye) repository.
I am officially confused by debian/raspbian differences, and why debian would call itself raspbian, so ignore that answer 
What guide did you use to install?
I mean what guide for installing supervised.
Sorry, here is the guide. Instead of x86 I used arm7 release version.
An “exec format error” suggests a CPU architecture mismatch between the container and the hardware.
1 Like
I have used os-agent_1.2.2_linux_armv7.deb. Trying to use amd64, tells me that it is armf architecture. So I believe I had done the right thing regarding the CPU architecture.
There is official documentation, and there is youtube, and frequently they don’t coincide.
Use the official documentation.
1 Like
That’s quite a vague answer.
If you mean “add-ons” then there are better options. Like HA OS either as an image install or in a VM.
If you mean additional applications, then that is not supported in a supervised install. To be officially supported the OS running the supervised install must be Debian (and not a derivative of Debian, like you have shown above), and must be dedicated to only running Home Assistant. Nothing else. No other apps. Supervised has some very restrictive conditions. You would be better off using a container install or a VM install. So you can run your other applications in containers or other VMs.
1 Like
This guide is known to work:
1 Like