try
sudo dpkg --pending --configure
sudo dpkg --pending --configure
dpkg: dependency problems prevent configuration of homeassistant-supervised:
homeassistant-supervised depends on os-agent.
dpkg: error processing package homeassistant-supervised (–configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
homeassistant-supervised
I dont have hassio os, but can you install this os-agent package?
You have dependency problem. Maybe homeassistant-supervised is to new package for your dependencies. Maybe downgrading homeassistant-supervised will resolve this issue. I’m not sure.
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.4.1';
@org.freedesktop.DBus.Property.EmitsChangedSignal("true")
readwrite b Diagnostics = false;
};
};
That command shows that the os-agent is installed.
I would try to check what version of os-agent you have. Here is my output.
nick@hass:~$ dpkg -s os-agent
Package: os-agent
Status: install ok installed
Priority: extra
Section: default
Installed-Size: 6524
Maintainer: Home Assistant <[email protected]>
Architecture: amd64
Version: 1.4.1
Depends: udisks2
Description: Home Assistant OS Agent
Homepage: https://www.home-assistant.io
EDIT, I typed this before your last message, but wouldn’t hurt to try.
I understand that its installed but ie. homeassistant-supervised v1 requires os-agent v1. If you install homeassistant-supervised v2 it will throw you a dependency problem because this v2 requires os-agent v2.
With respect to systemd-journal-gatewayd and unsupported installs, first step is install the package.
# apt-get install systemd-journal-remote -y
OK, so here’s what the HA installer actually does and how it differs from the default Debian/Raspbian installation.
The HA installer creates the file /usr/lib/systemd/system/systemd-journal-gatewayd.socket. This has a different socket specified from the default, IE this is the key line:
ListenStream=/run/systemd-journal-gatewayd.sock
In my case on Debian/Raspbian, I don’t want the HA startup file in that location because it’s going to be overwritten by any OS upgrades to that package. The better way is to use the /etc directory for systemd.
# cp /usr/lib/systemd/system/systemd-journal-gatewayd.socket /etc/systemd/system
# vi /etc/systemd/system/systemd-journal-gatewayd.socket
Change the ListenStream line as follows and save/exit:
ListenStream=/run/systemd-journal-gatewayd.sock
# systemctl daemon-reload
# systemctl enable systemd-journal-gatewayd.socket
# reboot
Now look in /run and you should see a socket called systemd-journal-gatewayd.sock
# ls -l /run
srw-rw-rw- 1 root root 0 Nov 3 17:57 systemd-journal-gatewayd.sock
OK, so good news is now we have the socket and in the correct place for HA to look for it.
In my case the challenge is that the unsupported message has not gone away with that change. Any ideas as to why? It’s world writable.
8 Likes
check
systemctl status systemd-journal-remote
Yes, for me too. The issue on Github leaded me to the problem. using wget I got a new package with .1 at the end homeassistant-supervised.deb.1, but the install command called homeassistant-supervised.deb, so an old image was installed.
Sad, I did overlooked this…
But, hey, full reinstall of the package as a solution to keep a system running is still weird…
1 Like
This did the trick for me: error in Home Assistant is gone, and i am able to see Host logs within Home Assistant.
However, when running the below following command, i see status “inactive”. Is everything now fine, or not? I’m a bit confused.
pi@raspberrypi:~ $ systemctl status systemd-journal-remote
● systemd-journal-remote.service - Journal Remote Sink Service
Loaded: loaded (/lib/systemd/system/systemd-journal-remote.service; indirect; vendor preset: disabled)
Active: inactive (dead)
TriggeredBy: ● systemd-journal-remote.socket
Docs: man:systemd-journal-remote(8)
man:journal-remote.conf(5)
Ooh. while reading the logs, i can see it is actually not working:
sudo systemctl start systemd-journal-remote
systemctl status systemd-journal-remote gives the following output:
systemd-journal-remote.service - Journal Remote Sink Service
Loaded: loaded (/lib/systemd/system/systemd-journal-remote.service; indirect; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2022-11-04 00:49:22 CET; 6s ago
TriggeredBy: ● systemd-journal-remote.socket
Docs: man:systemd-journal-remote(8)
man:journal-remote.conf(5)
Process: 10666 ExecStart=/lib/systemd/systemd-journal-remote --listen-https=-3 --output=/var/log/journal/remote/ (code=exited, status=1/FAILURE)
Main PID: 10666 (code=exited, status=1/FAILURE)
Error: 13 (Permission denied)
Nov 04 00:49:22 raspberrypi systemd[1]: Started Journal Remote Sink Service.
Nov 04 00:49:22 raspberrypi systemd-journal-remote[10666]: Failed to read key from file '/etc/ssl/private/journal-remote.pem': Permission denied
Nov 04 00:49:22 raspberrypi systemd[1]: systemd-journal-remote.service: Main process exited, code=exited, status=1/FAILURE
Nov 04 00:49:22 raspberrypi systemd[1]: systemd-journal-remote.service: Failed with result 'exit-code'.
Nathan, I love you! 
I only looked at „latest“ in the wget but ignored the download directory. So happy now after hours of searching high and low.
2 Likes
Thanks for this, the error cleared for me. Same “issue” as @pimw though, but I guess I can live with that.
And that is why one should better not just blindly doing copy-pastes when working from the shell but also read what the shell is reporting back:
[crosspost]
BAH, I reinstalled my supervisor using the link from above and now I’ve lost my add-on options and many of my previously installed things!
How do I get them back?
I thought I’d restore the backup but I don’t even have backup listed in the settings/system menus!!
I’m seeing this in my ha su logs:
22-11-03 20:16:29 ERROR (MainThread) [supervisor.homeassistant.api] Can't update Home Assistant access token!
22-11-03 20:16:30 ERROR (MainThread) [supervisor.homeassistant.api] Can't update Home Assistant access token!
wget tells you what the downloaded file is named. If it is identical to a file in the same directory it adds .1 then .2 etc.
1 Like
I know, I just overlooked it. Frustration and concentration are not the best friends… 
2 Likes
What is an “add-on option”
What installed things. How did you install them?
What exactly did you do? The installer doesn’t just install the supervisor, it does lots of shit, none of which remove anything as far as I can see.
I had to do the same, but the warning is still present - although I’m not sure that the service has been configured properly, not sure what the configuration is supposed to be though
systemctl --state=running --type=service shows me:
UNIT LOAD ACTIVE SUB DESCRIPTION
containerd.service loaded active running containerd container runtime
cron.service loaded active running Regular background program processing daemon
dbus.service loaded active running D-Bus System Message Bus
docker.service loaded active running Docker Application Container Engine
[email protected] loaded active running Getty on tty1
haos-agent.service loaded active running Home Assistant OS Agent
hassio-supervisor.service loaded active running Hass.io supervisor
NetworkManager.service loaded active running Network Manager
polkit.service loaded active running Authorization Manager
rsyslog.service loaded active running System Logging Service
ssh.service loaded active running OpenBSD Secure Shell server
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-resolved.service loaded active running Network Name Resolution
systemd-timesyncd.service loaded active running Network Time Synchronization
systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files
udisks2.service loaded active running Disk Manager
unattended-upgrades.service loaded active running Unattended Upgrades Shutdown
[email protected] loaded active running User Manager for UID 1000
wpa_supplicant.service loaded active running WPA supplicant