| 8 Nov 2024 |
 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 |
