Package Details: home-assistant 1:2026.8.1-1

Git Clone URL: https://aur.archlinux.org/home-assistant.git (read-only, click to copy)
Package Base: home-assistant
Description: Open source home automation that puts local control and privacy first
Upstream URL: https://home-assistant.io/
Licenses: Apache-2.0
Submitter: AlD
Maintainer: AlD (graysky)
Last Packager: graysky
Votes: 10
Popularity: 0.24
First Submitted: 2025-11-07 22:41 (UTC)
Last Updated: 2026-08-11 16:51 (UTC)

Latest Comments

1 2 3 Next › Last »

graysky commented on 2026-08-10 07:57 (UTC)

You can grab and apply this: https://gist.github.com/graysky2/913b2a3c352aaf8ca94e84a8eb943e43

graysky commented on 2026-08-10 07:55 (UTC)

Until the AUR push ban is lifted, there can be no updates.

graysky commented on 2026-07-28 10:55 (UTC)

I applied to -3, thanks

AlD commented on 2026-07-28 10:41 (UTC)

Sorry, I misread the RestartSec change and actually didn't realize that the package already has Restart=on-failure, which was already present in the official package.

Anyway, added you as maintainer now.

graysky commented on 2026-07-27 19:38 (UTC)

  1. I don't think it needs a separate hardened package. This is just, in my opinion, good practice on a machine that has a shared environment. If you keep the current permissions that they shipped with the official package, you risk anybody on the system being able to read credential files and stuff that are in there, which I think is a security no-no. If anyone needs to read those files, it's either the root user or someone in the hass group. I've been running it like this since I sent you that link last night and everything works. The service lockdowns seem sane to me.

  2. I'm not sure what you mean about restart policy. The 30 second timeout?

You can add me as a co-maintainer if you want. Or you can just make the changes, whatever you like. You're doing a great job.

AlD commented on 2026-07-27 11:52 (UTC) (edited on 2026-07-27 11:54 (UTC) by AlD)

@graysky Thanks a lot, those look great.

My only reservations would be:

1) The package didn't have these security measures while it was still an official Arch package. Assuming that the official packages should be the guiding star for AUR, would it be better to split the security scoping changes out to a …-hardened variant of the package?

Of course, if there's no negative side-effects to be expected (have you tested this?), the point is rather moot and we could just give it a try.

2) A small nit: I usually dislike packages shipping their own restart policy. I much rather have services stay down when they crash by default, and only if there's no solution have my own system override to restart automatically.

For HA in particular I don't really see the need. At least for me it's rock stable.

In any case, those changes are great. I could add you as co-maintainer if you'd like.

graysky commented on 2026-07-26 09:42 (UTC)

Great job creating this package. I have a few suggestions to harden it a bit. Have a look here and tell me what you think.

Changes hit, packaging, systemd service and a little about the build

https://gist.github.com/graysky2/3ed7151d1fc12051c74d0a193351b141

smmalis37 commented on 2026-07-16 23:57 (UTC)

Yep that did it, thanks!

AlD commented on 2026-07-16 12:57 (UTC) (edited on 2026-07-16 12:57 (UTC) by AlD)

Oh well, I guess the stack of patches will keep growing.

smmalis37 commented on 2026-07-16 06:29 (UTC) (edited on 2026-07-16 06:29 (UTC) by smmalis37)

After updating to 2026.7.2 I'm getting this error from multiple integrations:

Exception: Version mismatch: this is the 'cffi' package version 2.0.0, located in '/var/lib/hass/.venv/lib/python3.14/site-packages/cffi/api.py'.  When we import the top-level '_cffi_backend' extension module, we get version 2.1.0, located in '/var/lib/hass/.venv/lib/python3.14/site-packages/_cffi_backend.cpython-314-x86_64-linux-gnu.so'.  The two versions should be equal; check your installation.

This seems to be the opposite problem of what https://github.com/home-assistant/core/pull/175907 was supposed to fix haha. Does there need to be some patch here to fix it? Is it something wrong with my environment? I tried deleting the entire .venv and letting startup recreate it, no change.

1 2 3 Next › Last »