| 15 Jan 2025 |
 laurynasp | I am still at the early stages of understanding of HA design / architecture.
Is there a way to declare or script configuration flows?
I have come across the statement below on https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md#decision
Integrations that communicate with devices and/or services are only configured via the UI. In rare cases, we can make an exception
Given my superficial understanding of HA, it would seem intentional effort to prevent from programatic configuration of devices and services. That sounds too suprising, that I am certain I have missed something.
Could anyone point to an example either on how to define configuration flows?
| 03:41:21 |
| laurynasp | * I am still at the early stages of understanding of HA design / architecture.
Is there a way to declare or script configuration flows?
I have come across the statement below on https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md#decision
Integrations that communicate with devices and/or services are only configured via the UI. In rare cases, we can make an exception
Given my superficial understanding of HA, it would seem intentional effort to prevent from programatic configuration of devices and services. That sounds too suprising, that I am certain I have missed something.
Could anyone point to an example either on how to define configuration flows?
| 03:42:30 |
| laurynasp | * I am still at the early stages of understanding of HA design / architecture.
Is there a way to declare or script configuration flows?
I have come across the statement below on https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md#decision
Integrations that communicate with devices and/or services are only configured via the UI. In rare cases, we can make an exception
Given my superficial understanding of HA, it would seem intentional effort to prevent from programatic configuration of devices and services. That sounds too suprising, that I am certain I have missed something.
If anyone could point me to an example on how to define configuration flows, would be greatly appreciated
| 03:43:57 |
 CRTified | In reply to @laurynasp:matrix.org
I am still at the early stages of understanding of HA design / architecture.
Is there a way to declare or script configuration flows?
I have come across the statement below on https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md#decision
Integrations that communicate with devices and/or services are only configured via the UI. In rare cases, we can make an exception
Given my superficial understanding of HA, it would seem intentional effort to prevent from programatic configuration of devices and services. That sounds too suprising, that I am certain I have missed something.
If anyone could point me to an example on how to define configuration flows, would be greatly appreciated
It used to be possible to use only yaml for configuring essentially everything, but there is continuous progress to remove that ability | 07:03:34 |
|  fleaz joined the room. | 07:38:12 |
 mfed3 | Hey I searched this in the whole channel didn't see anyone reporting / talking about it | 11:20:43 |
| mfed3 | 
Download image.png | 11:20:46 |
| mfed3 | It appears the nixos configuration settings have not caught up to that change: | 11:21:59 |
| mfed3 | 
Download image.png | 11:22:03 |
 @hexa:lossy.network | there is an open issue about it | 11:22:46 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/issues/373674 | 11:22:59 |
| mfed3 | 
Download image.png | 11:23:06 |
| mfed3 | Ah awesome thanks hexa | 11:23:11 |
| mfed3 | I'll just leave my config on imperial for now since it's only a warning | 11:23:43 |
| @hexa:lossy.network | does it say when that was deprecated | 11:24:51 |
| @hexa:lossy.network | and when that is going to be removed | 11:24:55 |
| mfed3 | It told me 25.1 it's "deprecated" which we're in on nixos unstable already but didn't say when it would truly throw an error unfortunately | 11:25:31 |
| @hexa:lossy.network | I mean … y'all get the warning since probably 2025.1.0 | 11:25:34 |
| @hexa:lossy.network | ok, cool | 11:25:42 |
| @hexa:lossy.network | so no backport | 11:25:44 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/374025 | 11:25:53 |
| mfed3 | Yea true we're technically on 2025.1.2 | 11:26:00 |
| @hexa:lossy.network | I'm going to make it a hard swich | 11:26:12 |
| @hexa:lossy.network | so we can nudge more people to switch that at eval time | 11:26:28 |
| @hexa:lossy.network | I guess | 11:26:29 |
| mfed3 | Sounds good, | 11:36:38 |
| mfed3 | * Sounds good | 11:36:43 |
 Samsonite | hey hexa sorry if i'm getting annoying at this point, in an effort to not keep spamming my homeassistant/frigate issue here, should i open an issue or request or something in github? | 14:05:05 |
| @hexa:lossy.network | hm so | 14:05:25 |
| @hexa:lossy.network | try one more thing | 14:05:28 |
