| 20 Jun 2021 |
 Mic92 (Old) | In reply to @hexa:lossy.network
also they're talking about doing this because then they have control over config migration Which did not work very well in the past. I remember I had to delete my icloud storage multiple times in the past. | 11:53:11 |
 @hexa:lossy.network | yeah, well. shit happens. | 11:55:35 |
| @hexa:lossy.network | but the general arguments they're giving have merit | 11:55:46 |
| @hexa:lossy.network | because we are not really the intended target audience | 11:56:39 |
| @hexa:lossy.network | I mean, we're using hass inspite of these things | 11:57:06 |
| @hexa:lossy.network | * I mean, we're using hass in spite of these things | 11:57:32 |
 piegames | Having configuration management from both config files and UI is an incredibly hard task. Usually, you end up getting the worst of both worlds. If you then assume that the configuration is generated from something like Nix and thus is immutable to the UI, things get messy quickly in the UI. | 12:12:35 |
| @hexa:lossy.network | Fabian Affolter: homeassistant-cli click 8 compat would be nice, looks like completions are failing | 17:07:47 |
| @hexa:lossy.network | also there are two clis apparently
- https://github.com/home-assistant-ecosystem/home-assistant-cli
- https://github.com/home-assistant/cli
| 17:08:39 |
| @hexa:lossy.network | so I wonder if pkgs/server/home-assistant/cli.nix should actually package the latter? | 17:11:06 |
 dotlambda | In reply to @hexa:lossy.network
so I wonder if pkgs/server/home-assistant/cli.nix should actually package the latter? The latter is for the supervised setup only. | 17:52:47 |
| @hexa:lossy.network | oh, right. thank you! | 17:53:37 |
 Fabian Affolter | I will take a look after dinner | 17:59:00 |
| @hexa:lossy.network | thanks | 18:00:42 |
| 21 Jun 2021 |
|  @grahamc:nixos.org left the room. | 02:00:57 |
| @hexa:lossy.network |
AssertionError: sqlalchemy matches more than one derivation: {'home-assistant.python.pkgs.sqlalchemy_1_3', 'home-assistant.python.pkgs.sqlalchemy'}
| 11:09:43 |
| @hexa:lossy.network | blocks 2021.6.6 for now | 11:11:12 |
| Fabian Affolter | There is a PR for the home-assistant-cli update. I had to disable the shell completion for now as click > 8.0 works differently in that regard | 11:57:12 |
| @hexa:lossy.network | yup, it's in my backlog | 12:00:50 |
| dotlambda | will be fixed by https://github.com/NixOS/nixpkgs/pull/127707 | 18:53:10 |
| 22 Jun 2021 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/127738 | 01:36:37 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/127735 | 01:36:51 |
| 23 Jun 2021 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/127860 | 03:09:43 |
| @hexa:lossy.network | if anyone else is annoyed by broken file permissions after esphome upgrades | 03:10:01 |
|  a12l joined the room. | 11:20:45 |
 instantepiphany | In reply to @piegames:matrix.org
Having configuration management from both config files and UI is an incredibly hard task. Usually, you end up getting the worst of both worlds. If you then assume that the configuration is generated from something like Nix and thus is immutable to the UI, things get messy quickly in the UI. An interesting take on this problem:
https://github.com/lapp0/nix-gui | 12:19:18 |
| @hexa:lossy.network | right, except I wouldn't want my home automation to be able to rewrite my system configuration | 12:22:57 |
| @hexa:lossy.network | with deployment tools like morph it doesn't even know or have its original config on the same host in the first place | 12:23:45 |
| instantepiphany | In reply to @hexa:lossy.network
right, except I wouldn't want my home automation to be able to rewrite my system configuration Neither would I 🙂
If a user/app controlled nix file that a gui could edit was imported to be the configuration of your HA, then you wouldn't worry about it leaking to other system config. | 12:31:38 |
| instantepiphany | I'm not saying that I would use that app to change settings, just mentioning it as an approach someone took, we can see it actualised and think about what problems it solves and what problems it doesn't. | 12:32:36 |
