Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

puppet-homeassistant should be archived. #43

Open
traylenator opened this issue Apr 4, 2022 · 2 comments
Open

puppet-homeassistant should be archived. #43

traylenator opened this issue Apr 4, 2022 · 2 comments

Comments

@traylenator
Copy link
Contributor

traylenator commented Apr 4, 2022

This module should be archived.

It's a long time since home assistant could be configured purely with yaml and as such this module is useless I believe.

@tobixen
Copy link

tobixen commented Mar 17, 2023

Although quite much of the HomeAssistant state and configuration is outside Puppet, this module does seem to be useful for me.

@tobixen
Copy link

tobixen commented Mar 17, 2023

This puppet module puts the configuration under /etc/homeassistant, and that's where I think it belongs. Unfortunately, it also puts quite some state and even log files under the same directory. I think the problem is that the upstream HomeAssistant project is not good enough at separating "configuration" and "state" (and to some extent, even code).

If one considers things like user management (stored under /etc/homeassistant/.storage/auth_provider.homeassistant) to be "state" rather than "configuration", then it's perfectly OK that the puppet module doesn't handle it.

I've been through some rounds of installing/migrating HomeAssistant, this is the first time I try to do things via Puppet. Some notes:

  • I've tried to do it through pacman -S home-assistant on Archlinux. I'm quite unhappy about the results, got a relatively old version of HomeAssistant, and the particularly the location of configuration files (/var/lib/hass/, but there is again a symlink to /var/lib/private/hass, and the /var/lib/private is supposed to be accessible only by root - making it hard to maintain configuration files manually).
  • I've tried to do it through the official documentation ("core"). That's "for experts only", and one will have to manage the user account manually and eventually write up a systemd file, etc.
  • I don't want a containerized solution, as I feel that gives me less control (and it's not only me - I'm doing some library development, from time to time HomeAssistant users report bugs, but when running things under docker it's very hard for them to test out a patch or a bugfixing branch of the library).
  • I installed HomeAssistant on a raspberry pi to have in the boat, then I went for the "OS"-solution. I regret on that, I feel I have very little control, difficult to locate the configuration files, difficult to piggyback other services on the same raspberry, etc.
  • So far, I feel that this puppet module gave me the most sane setup - got an up-to-date version of home assistant installed, user account, a sane systemd-file, a sane location of the configuration files. I migrated .storage and some other things from my old instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants