recommend to run portainer on different VM or server and remote access to HA. That what I did, portainer is a great tools when handling error, especially when HA fail to run. I also hate this new supervisor version since now I cant even run NGINX Proxy Manager on the same machine.
It is a bad direction, but I guess they really want to down the number of users of supervised, so there is a reason to stop with it.
I am trying to install in on Debian WSL2. It is not working
root@SergeyHC:~# dpkg -i os-agent_1.2.2_linux_x86_64.deb
Selecting previously unselected package os-agent.
(Reading database ... 84584 files and directories currently installed.)
Preparing to unpack os-agent_1.2.2_linux_x86_64.deb ...
Unpacking os-agent (1.2.2) ...
Setting up os-agent (1.2.2) ...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Created symlink /etc/systemd/system/multi-user.target.wants/haos-agent.service ā /lib/systemd/system/haos-agent.service.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
dpkg: error processing package os-agent (--install):
installed os-agent package post-installation script subprocess returned error exit status 1
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...
Errors were encountered while processing:
os-agent
Is it fixible?
Unfortunately the end-goal is to end supervised installs all together. It was tried in the past and failed due to negative reactions from users, it is now implemented step-by-step indirectly, by making such decisions. We have to live with it for as long as HA is free software. I was also bugged with the big, yellow, flashy āunsupportedā warning in the beginning, but I eventually got used to it. In any way it doesnāt mean a thing if you know what you are doing, apart from reminding you the direction of the project.
It is also obvious to me that in the long run the goal is to completely dumb it down and then commercialise this great piece of software. Donāt get me wrong, but this is the nature of free software. When it has great success, someone has to pay the bills.
And yes, we are now even one (small) step closer to eliminating supervised installs, at least aesthetically: Newest version 2021.12 altogether removes the Supervisor side bar item from the main menu and moves it to the Configuration menu according to the release notes (I havenāt upgraded yet). Letās get that out of our sight and weāll take it from thereā¦
Hi,
I bought a HpT620 thinclient. Iāve downloaded Debian 11 and made usb device with Rufus. I booted in UEFI mode everything went perfect only the Grub install pint was missing it was automatically done. After the reboot the system says not bootable device. Secure boot is off. I booted from USB again but this time legacy mode. The grub install point now appeared and after reboot the system starts. The problem is that Debian is booting only in legacy mode in EUFI not. It this a problem or should I live with this?
Thank you
What are the disadvantages of UEFI?
64-bit are necessary.
Virus and Trojan threat due to network support, since UEFI doesnāt have anti-virus software.
When using Linux, Secure Boot can cause problems.
First of all thanks for the tutorial. I used it and HA works for me, the problem is that the portainer and yatch stopped working in OMV and all the containers that I had configured.
Totally agree on the path and considerations
I have an error while during the setup of supervisor, what I must doe now ?
root@raspberrypi4:~# dpkg -i homeassistant-supervised.deb
Selecting previously unselected package homeassistant-supervised.
(Reading database ... 91257 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.
Adding 'diversion of /etc/NetworkManager/NetworkManager.conf to /etc/NetworkManager/NetworkManager.conf.real by homeassistant-supervised'
Adding 'diversion of /etc/NetworkManager/system-connections/default to /etc/NetworkManager/system-connections/default.real by homeassistant-supervised'
Adding 'diversion of /etc/docker/daemon.json to /etc/docker/daemon.json.real by homeassistant-supervised'
Adding 'diversion of /etc/network/interfaces to /etc/network/interfaces.real by homeassistant-supervised'
Unpacking homeassistant-supervised (1.0.2) ...
**dpkg:** dependency problems prevent configuration of homeassistant-supervised:
homeassistant-supervised depends on os-agent.
**dpkg:** error processing package homeassistant-supervised (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
homeassistant-supervised
root@raspberrypi4:~#
If I install os agent is this the output:
root@raspberrypi4:~# gdbus introspect --system --dest io.hass.os --object-path /io/hass/os
node /io/hass/os {
interface org.freedesktop.DBus.Introspectable {
methods:
Introspect(out s out);
signals:
properties:
};
interface org.freedesktop.DBus.Properties {
methods:
Get(in s interface,
in s property,
out v value);
GetAll(in s interface,
out a{sv} props);
Set(in s interface,
in s property,
in v value);
signals:
PropertiesChanged(s interface,
a{sv} changed_properties,
as invalidates_properties);
properties:
};
interface io.hass.os {
methods:
signals:
properties:
@org.freedesktop.DBus.Property.EmitsChangedSignal("invalidates")
readonly s Version = '1.2.2';
@org.freedesktop.DBus.Property.EmitsChangedSignal("true")
readwrite b Diagnostics = false;
};
};
root@raspberrypi4:~#
SOLVED
have you done sudo apt-get update && sudo apt-get upgrade? to update debian? this is a dpkg error not a HA error
I followed your guides both for debian 10 and 11 for several times and never had an issue.
Thank you, for making home assistant more accessible to the new comers.
@ [kanga_who] Thanks so much for this. I spent the better part of the morning trying to follow other guides and after finding yours, had my server up and running in under 20 minutes. Thanks for taking the time!
How did you solve this?
Fully new clean install based on several install pages
I cant see the supervisor tab for some reason and i checked the container is there but i dont know why i dont have a supervisor tab
because itās moved under configuration in 2021.12.x
i just noticed i have not used home assistant in forever
Please help, error during installation:
version.home-assistant.io: Unknown name or service
ā¦
Error response from daemon: Get āhttps://registry-1.docker.io/v2/ā: certificate is valid for jenkins.bison.services, *.bison.services, not registry-1.docker.io
I reviewed everything in Google, nothing helps.
P.S. DNS set to 8.8.8.8. The network is stable, I do not use proxy, the server IP address is static.
Hi all! Just set up my new mini PC using this guide and got everything is running smoothly!
Iām a long time HA user but Iām completely new to both Debian and Docker so sorry if this is a dumb question.
Iād like to be able to access the Home Assistant command line from another computer. When I was just running HA on a RPI, I just used the SSH add-on. Now when I SSH to the machine, Iām obviously accessing Debian instead.
I tried SSHing to the hassio IP address that I found through ip a
in Debian as well as the address listed in the web terminal add-on, neither work.
After a lot of Googling and searching in this thread, I think I need to SSH to the machine and then somehow launch the HA command line through Dockerā¦?
Iāve tried these commands:
sudo docker exec -it homeassistant bin/bash
sudo docker exec -it homeassistant bash
sudo docker exec -it hassio_supervisor bin/bash
sudo docker exec -it hassio_supervisor bash
The seem to work but Iām not getting the view Iām looking for. I would like to be able to access the config folder and all the hassio commands etc. Any help appreciated!