| 28 Nov 2021 |
 AngryAnt | Ah | 12:50:58 |
 @hexa:lossy.network | can you post the error log you are seeing? | 12:51:06 |
| AngryAnt | Cropped, but updated here: https://gist.github.com/AngryAnt/f0548625aa645dff387dbaf04f16f631 | 12:52:45 |
| AngryAnt | The full config file is very sparse - just has deCONZ in a podman container in addition to that home-assistant bit. | 12:55:01 |
| @hexa:lossy.network | alright | 12:56:04 |
| @hexa:lossy.network | the home-assistant package in nixos works in a somewhat special way as you might have discovered | 12:56:25 |
| @hexa:lossy.network | we're not relying on pip to fetch dependencies, but instead we're providing them from nixpkgs | 12:56:40 |
| @hexa:lossy.network | by default home-assistant gains no dependency packages for its components | 12:57:02 |
| @hexa:lossy.network | if you use the declarative services.home-assistant.config attrset the module will autodiscover the components you use and inject the dependencies. | 12:57:32 |
| @hexa:lossy.network | that behaviour is controlled by services.home-assistant.autoExtraComponents | 12:58:03 |
| @hexa:lossy.network | if you don't want that, you need to override the packages extraComponents | 12:59:26 |
| @hexa:lossy.network | fwiw, I think we could make that clearer on the wiki ("What is a good starting config") | 12:59:57 |
| AngryAnt | Definitely | 13:00:04 |
| AngryAnt | My path is likely going to be via extraComponents as I am migrating an existing hass config. | 13:00:33 |
| AngryAnt | (And I'd like to continue to use the web interface for editing that config) | 13:01:21 |
| @hexa:lossy.network | that's fair | 13:01:29 |
| @hexa:lossy.network | the override works like this: | 13:01:42 |
| @hexa:lossy.network | services.home-assistant.package = pkgs.home-assistant.override {
extraComponents = [
"deconz"
];
}:
| 13:02:20 |
| @hexa:lossy.network | though, to be fair, you might benefit from just running the vm image from home-assistant, if you don't want declarative management anyway | 13:03:10 |
| AngryAnt | It's possible to run that inside a nixos setup? | 13:03:45 |
| @hexa:lossy.network | it certainly is, if that's what you prefer | 13:04:06 |
| @hexa:lossy.network | In reply to @hexa:lossy.network
also this just appeared on lobste.rs https://myme.no/posts/2021-11-25-nixos-home-assistant.html some inspiration ^ | 13:04:26 |
| AngryAnt | Hm. That seems likely the best initial migration path for me. Get things solidly established via the VM, then review. | 13:05:20 |
| AngryAnt | When reviewing the wiki entry it could do with an outline of the alternatives and their use case: oci container vs. VM image vs. fully declarative. | 13:06:12 |
| @hexa:lossy.network | I guess most people just want the declarative approach on NixOS, that's why that does not exist | 13:06:56 |
| AngryAnt | Definitely makes sense. There's just not really any other overview source for "got: nix, want: home assistant, what now?" | 13:08:01 |
| @hexa:lossy.network | and I can't properly describe something I've never used | 13:08:12 |
| @hexa:lossy.network | yeah, that's disappointing, I agree | 13:08:35 |
| @hexa:lossy.network | let me start something up real quick | 13:08:41 |
| AngryAnt | I could provide some input if you need details from this direction. | 13:10:23 |
