I locally bumped the package to 2.0.0 (only changed pkgver=2.0.0;_tag=4ce4bad3fa1ca2d61f758284bc8a14eba580ebc9) without any noticeable issues (ymmv). my addon-logging problems persist though.
Search Criteria
Package Details: homeassistant-supervised 2.0.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/homeassistant-supervised.git (read-only, click to copy) |
|---|---|
| Package Base: | homeassistant-supervised |
| Description: | Home Assistant Supervised |
| Upstream URL: | https://www.home-assistant.io/ |
| Keywords: | haos hass homeassistant supervised |
| Licenses: | Apache |
| Conflicts: | docker-desktop |
| Submitter: | rokam |
| Maintainer: | rokam (frostwork) |
| Last Packager: | rokam |
| Votes: | 4 |
| Popularity: | 0.000000 |
| First Submitted: | 2022-08-05 22:00 (UTC) |
| Last Updated: | 2025-01-02 20:28 (UTC) |
Dependencies (14)
- curl (curl-http3-ngtcp2AUR, curl-gitAUR, curl-c-aresAUR)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- docker (rancher-desktop-gitAUR, podman-docker-gitAUR, rancher-desktopAUR, docker-gitAUR, docker-cli-binAUR, podman-docker)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- homeassistant-osagentAUR
- jq (jaq-binAUR, jq-gitAUR)
- systemd (systemd-chromiumosAUR, systemd-fmlAUR, systemd-selinuxAUR, systemd-gitAUR)
- udisks2
- wget (wget-gitAUR, wurlAUR)
- git (git-gitAUR, git-glAUR) (make)
- apparmor (apparmor-gitAUR) (optional) – enhanced security
- cifs-utils (optional) – support for SMB/CIFS mounts
- networkmanager (networkmanager-gitAUR, networkmanager-iwdAUR) (optional) – support for built-in network management
- nfs-utils (optional) – support for NFS mounts
Required by (0)
Sources (1)
frostwork commented on 2024-12-23 17:56 (UTC)
frostwork commented on 2024-12-23 14:28 (UTC)
sorry for the noise: the upstream issue was reopenend, @agners confirmed that cgroupsv2 support is (mostly) functional: https://github.com/home-assistant/supervised-installer/issues/372#issuecomment-2559786136
frostwork commented on 2024-12-23 14:04 (UTC)
Hi there.
assuming the main reason for not bumping this package is the still missing support for cgroup v2.
The upstream issue (https://github.com/home-assistant/supervised-installer/issues/372) was (auto-)closed recently with "not planned" (bumping that as well).
I use home assistant with cgroup v2 since some months "without" problems. The only visible problem is, that addons don't show their logs in the webui ("500 Internal Error"), which doesn't seem to be cgroup related though.
happy holidays and a great start into a hopefully good and peaceful new year!
gaelic commented on 2024-06-19 18:07 (UTC) (edited on 2024-06-19 18:48 (UTC) by gaelic)
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.
User8395 commented on 2024-02-19 21:08 (UTC) (edited on 2024-02-19 21:30 (UTC) by User8395)
Created an AUR account just to comment this, the homeassistant container's port 8123 needs to be forwarded to the host port 8123.
Adrian.Chmiel commented on 2024-01-19 07:05 (UTC)
@whoami, MACHINE env. variable has been described on wiki https://wiki.archlinux.org/title/Home_Assistant_Supervised
rokam commented on 2024-01-18 13:18 (UTC)
@whoami, you can run this command before installing.
export MACHINE=qemuarm-64
It doesn't work ootb because there are multiple machines for the same arch.
whoami commented on 2024-01-17 05:36 (UTC)
I set the MACHINE environment variable to qemuarm-64 on Orange PI Zero 3. But it always stops working on the check_machine() function
MACHINE environment variable unknown! Please choose one of the following options:
- generic-x86-64
- odroid-c2
- odroid-c4
- odroid-n2
- odroid-xu
- qemuarm
- qemuarm-64
- qemux86
- qemux86-64
- raspberrypi
- raspberrypi2
- raspberrypi3
- raspberrypi4
- raspberrypi3-64
- raspberrypi4-64
- tinker
- khadas-vim3
error: command failed to execute correctly
if I'm setting MACHINE manually in .INSTALL script inside block, then works fine:
"aarch64")
MACHINE=${MACHINE:=qemuarm-64}
HASSIO_DOCKER="${DOCKER_REPO}/aarch64-hassio-supervisor"
;
txomon commented on 2024-01-05 01:03 (UTC)
Taking into account how the .INSTALL script is set, I think at least NetworkManager and apparmor should be added as non-optional requirements,
rokam commented on 2023-06-05 20:16 (UTC)
Yes, that might be apparmor related
Pinned Comments
gaelic commented on 2024-06-19 18:07 (UTC) (edited on 2024-06-19 18:48 (UTC) by gaelic)
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.
rokam commented on 2022-08-05 22:03 (UTC) (edited on 2022-08-05 22:04 (UTC) by rokam)
You need to add
systemd.unified_cgroup_hierarchy=falsein your kernel parameters.Read more at: https://wiki.archlinux.org/title/Kernel_parameters