Arch Linux User Repository

cgroup v1 is deprecated as of now and my pc is not booting anymore with the required parameter. I am downgrading systemd for the moment, but we need a solution for this problem rather soon. From the systemd changelog (version 256):

Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now considered obsolete and systemd by default will refuse to boot under it. To forcibly reenable cgroup v1 support, SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command line. The meson option 'default-hierarchy=' is also deprecated, i.e. only cgroup v2 ('unified' hierarchy) can be selected as build-time default.

You need to add systemd.unified_cgroup_hierarchy=false in your kernel parameters.

Read more at: https://wiki.archlinux.org/title/Kernel_parameters

@rokam, there is a bug in .INSTALL: (line 47)
sed -i "s,%%HASSIO_CONFIG%%,${CONFIG},g" "${PREFIX}"/bin/hassio-supervisor

Should be:
sed -i "s,%%HASSIO_CONFIG%%,${CONFIG},g" "${PREFIX}/bin/hassio-supervisor"

"is in the wrong place
This is the reason why Martynvandijke60 had problems

Supervisor cannot download docker package, when MACHINE is not specified: (from line 119)
"arm" |"armv6l")
MACHINE=${MACHINE:=armhf}
HASSIO_DOCKER="${DOCKER_REPO}/armhf-hassio-supervisor"
;;
"armv7l")
MACHINE=${MACHINE:=armv7}
HASSIO_DOCKER="${DOCKER_REPO}/armv7-hassio-supervisor"
;;
"aarch64")
MACHINE=${MACHINE:=aarch64}
HASSIO_DOCKER="${DOCKER_REPO}/aarch64-hassio-supervisor"
;;
*)


Next thing, in my opinion is better to check
systemd.unified_cgroup_hierarchy=false
in /proc/cmdline, rarely on ARM platforms there is something in /boot

What problem is if I update ha e supervisor but not package homeassistant-supervised?

@simona, you can create a full backup and then restore it after package installation. The "migration" process will need a lot of tweeks.

I apologize in advance for the question. should it be inappropriate, please ignore it. but if i internally update home assistant already installed, don't i have to update this package every time?

@simona, that's not related to the package.

i have installed with "curl -sL "https://raw.githubusercontent.com/krdesigns-com/supervised-installer/master/installer.sh" | bash -s" what I must fix? it seem start ok.

@thepasto, I don't own a rpi4 to be able to support it. Those commands came from debconf as the original installer is for debian only.

Those command exists to identify the machine_type. And the result for you should be something like raspberrypi4-64.

Replace inside the .INSTALL file the lines 88-92:

                db_input critical ha/machine-type || true
                db_go || true
                db_get ha/machine-type || true
                MACHINE="${RET}"
                db_stop

to:

                MACHINE="raspberrypi4-64"

Also, can you please provide the output of the command: $ uname -i

We need one of the supported machine_type:

• generic-x86-64
• odroid-c2
• odroid-n2
• odroid-xu
• qemuarm
• qemuarm-64
• qemux86
• qemux86-64
• raspberrypi
• raspberrypi2
• raspberrypi3
• raspberrypi4
• raspberrypi3-64
• raspberrypi4-64
• tinker
• khadas-vim3

This is very cool, i'm trying to run it on my rpi4 armv7h,

(1/1) installing homeassistant-supervised                                            [-------------------------------------------------] 100%
PING checkonline.home-assistant.io (104.26.4.238) 56(84) bytes of data.
64 bytes from 104.26.4.238 (104.26.4.238): icmp_seq=1 ttl=56 time=12.2 ms

--- checkonline.home-assistant.io ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.210/12.210/12.210/0.000 ms
/tmp/alpm_XdMzSB/.INSTALL: line 88: db_input: command not found
/tmp/alpm_XdMzSB/.INSTALL: line 89: db_go: command not found
/tmp/alpm_XdMzSB/.INSTALL: line 90: db_get: command not found
/tmp/alpm_XdMzSB/.INSTALL: line 92: db_stop: command not found

Within a few minutes you will be able to reach Home Assistant at:
http://homeassistant.local:8123 or using the IP address of your
machine: http://192.168.1.110:8123

Maybe some dependicies are missing? Thanks

Marty, the install script usually update that tag with the config path. Can you try to reinstall it.

Hi rokam, I edited my kernel parameters rebooted my pc and now it fails to start because of a missing config dir ? The error:

jq: error: Could not open file %%HASSIO_CONFIG%%: No such file or directory

Where should i specify the config dir ?