Yeah, i can’t start it. Neither before reboot nor after reboot.
I made an issue. Let’s take this discussion there as the installer needs to either be updated or the guide does as it appears there’s something missing.
Please make another issue in that same repo. Seems that needs to be updated too.
6 Likes
Love the look, but unfortunately Picture Elements have stopped working with IMAGES EXAMPLE below an extract from Picture Elements Card - Home Assistant
type: picture-elements
image: /local/floorplan.png
elements:
# state_image & state_filter - toggle on click
- type: image
entity: light.living_room
tap_action:
action: toggle
image: /local/living_room.png
state_image:
"off": /local/living_room_off.png
filter: saturate(.8)
state_filter:
"on": brightness(120%) saturate(1.2)
style:
top: 25%
left: 75%
width: 15%
My simple one was
type: picture-elements
image: /local/irrigation/mon-sun1.png
elements:
- type: image
entity: input_boolean.water_monday
tap_action:
action: toggle
state_image:
'off': /local/off.png
'on': /local/on/png
Worked like a charm before update, 2022.11, even updated to 2022.11.1 still not working
But then again the Picture Elements stopped pushing aspect ratio a long time ago too, so now it CROPS instead of CONSTRAINT the image to FIT the aspect Ratio.
Would love both to be fixed, but at least the First one is a little more important
I cant even reinstall homeassistant-supervised.deb because it fails with os-agent dependency, but os-agent is installed already. I tried 1.2.0 1.3.1 and 1.4.1 versions and .deb installation fails with all of them.
And I made mistake by rebooting and now the containers wont even start. So no automation for tonight. Nice.
Make sure you’re cleaning out the folder that you’re downloading the deb installer to - I found it was making .1 - .3 entries and I was blindly reinstalling the same old supervisor (1.1.0) instead of the most recent (1.3.1)
root@homeassistant:~# dpkg -i homeassistant-supervised.deb
(Reading database ... 294458 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.3.1) over (1.1.0) ...
Setting up homeassistant-supervised (1.3.1) ...
[info] Restarting NetworkManager
[info] Restarting docker service
PING checkonline.home-assistant.io (172.67.68.90) 56(84) bytes of data.
64 bytes from 172.67.68.90 (172.67.68.90): icmp_seq=1 ttl=54 time=26.2 ms
--- checkonline.home-assistant.io ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 26.219/26.219/26.219/0.000 ms
[info] Install supervisor startup scripts
[info] Install AppArmor scripts
[info] Start Home Assistant Supervised
[info] Installing the 'ha' cli
[info] Switching to cgroup v1
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-5.10.0-13-amd64
Found initrd image: /boot/initrd.img-5.10.0-13-amd64
Found linux image: /boot/vmlinuz-5.10.0-12-amd64
Found initrd image: /boot/initrd.img-5.10.0-12-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
error: invalid volume.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Adding boot menu entry for UEFI Firmware Settings ...
done
[info] Within a few minutes you will be able to reach Home Assistant at:
[info] http://homeassistant.local:8123 or using the IP address of your
[info] machine: http://172.24.0.250:8123
[warn] A reboot is required to apply changes to grub.
All of my repairs issues have gone away.
5 Likes
sudo dpkg -i homeassistant-supervised.deb
(Reading database ... 40505 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.3.1) over (1.3.1) ...
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
Have you removed and re-installed os-agent?
Yes, it does not help.
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;
};
};
pi@homeassistant:~ $ sudo dpkg -i homeassistant-supervised.deb
(Reading database ... 40505 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.3.1) over (1.3.1) ...
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
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)