| 24 Feb 2025 |
 @hexa:lossy.network | and submit a fix to close that issue | 17:11:27 |
 K900 | Problem is, I can' | 17:11:38 |
| @hexa:lossy.network | don't mention using nixos 😛 | 17:11:40 |
| K900 | * Problem is, I can't really think of an immediately obvious fix | 17:11:45 |
| K900 | But I will file an issue | 17:11:53 |
| @hexa:lossy.network | then mention the prometheus component maintainer | 17:12:12 |
 @marie:marie.cologne | do they still hate us for packaging home-assistant? | 17:12:24 |
| @hexa:lossy.network | no idea | 17:12:32 |
| @hexa:lossy.network | and I'm not interested to find out in the context of getting a bug squashed 😄 | 17:12:49 |
| K900 | https://github.com/home-assistant/core/issues/139201 | 17:16:16 |
| K900 | OK let's see where this goes | 17:16:19 |
| @hexa:lossy.network | @symphorien:xlumurb.eu zap-chip is using an eol electron version | 17:42:51 |
| @hexa:lossy.network | https://github.com/project-chip/zap/issues/1502 meh | 17:58:52 |
 symphorien | it doesn't impact home assistant does it? | 18:23:28 |
| symphorien | otherwise I can patch the requirements | 18:23:43 |
| @hexa:lossy.network | I have a PR open to remove electron up to version 30 | 19:17:22 |
| @hexa:lossy.network | and stopped there because 31 affects home-assistant | 19:17:33 |
| symphorien | ah ok | 20:07:07 |
| symphorien | hexahttps://github.com/NixOS/nixpkgs/pull/384858 gui still starts up but I don't know how to use this thing
| 20:25:56 |
| @hexa:lossy.network | me neither | 21:04:56 |
| @hexa:lossy.network | if the chip wheels still build we're fine | 21:05:03 |
| @hexa:lossy.network | ah ok … the matter integration is using the headless version | 23:45:41 |
| @hexa:lossy.network | got it | 23:45:42 |
| 25 Feb 2025 |
 macaroniskengz | Is there a way to add an admin token as a file in my declarative configuration? | 01:09:03 |
| @hexa:lossy.network | for what service? | 01:12:25 |
| @hexa:lossy.network | do you mean a long-lived access token for home-assistant? | 01:13:00 |
| @hexa:lossy.network | * do you mean a long-lived access token for home-assistant? if so, no. | 01:13:05 |
| macaroniskengz | Yes, this.
Currently I try to built a Home Assistant WS API Proxy that allows finer permissions for the API. | 01:15:30 |
| @hexa:lossy.network | I really would like for that to be possible to further test home-assistant in our nixos integration test | 01:16:02 |
| @hexa:lossy.network | but have yet to find a a way | 01:16:07 |
