| 15 Jan 2025 |
 Samsonite | that backport says it was merged, right? | 02:06:05 |
| Samsonite | so if i'm on 24.11 and updated my flake then i should already have that patch | 02:06:42 |
 @hexa:lossy.network | yes | 02:23:16 |
| @hexa:lossy.network | but again, for 127.0.0.1 | 02:23:19 |
| @hexa:lossy.network | and not really configurable | 02:23:34 |
| Samsonite | my only hope then lies in fleaz | 02:36:01 |
| Samsonite | i would've thought most people who used frigate use it with homeassistant | 02:36:33 |
| Samsonite | surprised im the first one bringing this up | 02:36:40 |
| @hexa:lossy.network | Likely on the same host | 02:37:18 |
| Samsonite | listen i'm just not a hone host kinda guy, please don't host shame me | 02:49:50 |
| Samsonite | * listen i'm just not a one host kinda guy, please don't host shame me | 02:50:04 |
 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 |
