| 20 Jun 2021 |
 CRTified | In reply to @joerg:bethselamin.de
Do you have a source for that? This reads different: https://www.home-assistant.io/blog/2020/04/14/the-future-of-yaml/ The section about ADR0010 explains that in the long term, YAML will fade out, as new integrations won't be allowed to use of YAML (except in rare cases) | 11:45:03 |
 Mic92 (Old) | In reply to @schnecfk:ruhr-uni-bochum.de
The section about ADR0010 explains that in the long term, YAML will fade out, as new integrations won't be allowed to use of YAML (except in rare cases) Mhm. I am probably ok with having only my automations in yaml for now. Maintaining a project like home-assistant seems otherwise like a huge effor. | 11:46:26 |
| CRTified | At least for some integrations, although the line between "communicates with a service" and "bridges a protocok" seems fairly thin to me | 11:46:57 |
| Mic92 (Old) | Well maybe depends on the integration | 11:47:00 |
 @hexa:lossy.network | Mic92: https://github.com/home-assistant/core/pull/37800#issuecomment-657707769 | 11:47:58 |
| CRTified | I mean, even esphome does not support yaml anymore | 11:48:04 |
| @hexa:lossy.network | huh, what? | 11:48:28 |
| @hexa:lossy.network | oh, you mean on the home-assistant side | 11:48:35 |
| @hexa:lossy.network | but esphome works great with zeroconf | 11:48:46 |
| CRTified | In reply to @hexa:lossy.network
oh, you mean on the home-assistant side https://www.home-assistant.io/integrations/esphome/ that one, yes | 11:49:02 |
| @hexa:lossy.network | also they're talking about doing this because then they have control over config migration | 11:49:58 |
| 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 |
