| 8 Nov 2024 |
 @hexa:lossy.network | the other would be to try and revert to an older remarshal version that still emits yaml 1.1 | 14:19:46 |
 mattleon | In reply to @hexa:lossy.network
so one thought about remarshal is that we could patch hass to use yamlcore and thus interpret things as yaml 1.2 Have you already made progress on this? If not, I'd be happy to start on it | 23:29:55 |
| @hexa:lossy.network | no, we probably need a treewide fix | 23:30:26 |
| @hexa:lossy.network | so remarshal_0_17 and provide that as pkgs.formats.yaml_1_1, and the latest as yaml_1_2 | 23:30:57 |
| mattleon | Ah, that makes sense. Much more maintainable than trying to carry a large hass patch | 23:31:44 |
| 9 Nov 2024 |
 mfed3 | Trying to follow some of the comments up above about Declarative Nix scripts resolving "on" to state = "on" to state = true in yaml | 04:46:10 |
| mfed3 | Noticing all my automations with on/off checks are broken with that issue. Can someone direct me to which pull request fixes that or is this an ongoing issue that needs a fix still | 04:47:08 |
| @hexa:lossy.network | todo | 04:47:25 |
| mfed3 | Roger. Is there a current workaround I can substitute ? | 04:47:40 |
| @hexa:lossy.network | rollback | 04:47:45 |
| mfed3 | Thanks, appreciate it | 04:48:13 |
| mfed3 | My current version is 2024.10.4, should I just roll back to 2024.10.3? Or is there a version you recommend and know is good | 05:01:08 |
| @hexa:lossy.network | can you provide a config that obviously breaks? | 05:02:24 |
| @hexa:lossy.network | ideally one that breaks hard | 05:04:09 |
| mfed3 | Yea let me find the simplest one that doesn't any extra factors other than the on off true false things going on, some of my automations have a lot of conditions going on | 05:06:42 |
| mfed3 |
{ config, pkgs, ... }:
{
services.home-assistant.config.automation = [
{
alias = "Iron Auto Off";
trigger = {
platform = "state";
entity_id = "switch.sonoff_s31_lite_zb_switch_2";
to = "on";
for = "00:15:00";
};
action = {
service = "switch.turn_off";
entity_id = "switch.sonoff_s31_lite_zb_switch_2";
};
}
];
} | 05:09:46 |
| @hexa:lossy.network | does that fail to validate the config? | 05:10:15 |
| mfed3 | * what's the code block escape I need again | 05:10:26 |
| @hexa:lossy.network | three backticks | 05:10:34 |
| @hexa:lossy.network | ``` | 05:10:45 |
| mfed3 | { config, pkgs, ... }:
{
services.home-assistant.config.automation = [
{
alias = "Iron Auto Off";
trigger = {
platform = "state";
entity_id = "switch.sonoff_s31_lite_zb_switch_2";
to = "on";
for = "00:15:00";
};
action = {
service = "switch.turn_off";
entity_id = "switch.sonoff_s31_lite_zb_switch_2";
};
}
];
}
| 05:10:46 |
| mfed3 | 
Download image.png | 05:11:00 |
| mfed3 | Then what ends up happening is it converts the "on" to true in the automation, but it compiles | 05:11:24 |
| @hexa:lossy.network | hrm | 05:11:33 |
| @hexa:lossy.network | I need something that will fail obviously in a nixos test | 05:11:41 |
| mfed3 | Ah I see, yea I have like 23 out of 50 automations with this type of issue right now, but 100% of all the nix builds and passes | 05:13:02 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/354687 | 05:36:03 |
|  Niten changed their display name from Peter to Niten. | 20:30:13 |
| 10 Nov 2024 |
 johnhamelink | Hi, I just noticed that in the nixos.wiki page for home-assistant, it mentions that the declarative style might not be supported going forward. I just wanted to flag that I'm using it quite successfully. You can see most of my config here - I have quite an extensive config and I do plan on building it out further going forward. I was very much enjoying being able to use nix to split out and organise the home assistant config. https://git.sr.ht/~johnhamelink/nix/tree/master/item/os/hosts/sun/services/home-assistant | 00:54:07 |
 CRTified | In reply to @johnhamelink:matrix.org
Hi, I just noticed that in the nixos.wiki page for home-assistant, it mentions that the declarative style might not be supported going forward. I just wanted to flag that I'm using it quite successfully. You can see most of my config here - I have quite an extensive config and I do plan on building it out further going forward. I was very much enjoying being able to use nix to split out and organise the home assistant config. https://git.sr.ht/~johnhamelink/nix/tree/master/item/os/hosts/sun/services/home-assistant Do you have a declarative way of configuring e.g. the mqtt component, or do you have to enter credentials by yourself in the HA GUI? I didn't spot anything related to mqtt config besides the component definition in your config, so I might have missed it | 02:56:30 |
