| 24 Feb 2025 |
 @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 |
| macaroniskengz | Redacted or Malformed Event | 01:16:23 |
| macaroniskengz | Is it possible to declare HASS users? | 01:18:25 |
| macaroniskengz | * Is it currently possible to declare HASS users? | 01:18:29 |
| @hexa:lossy.network | also … no | 01:18:39 |
| @hexa:lossy.network | you have to do the onboarding, which creates the first user | 01:18:45 |
| @hexa:lossy.network | and that user can create api tokens and other users | 01:18:58 |
| macaroniskengz | Thanks for the clarification. This is very unfortunate, but I guess inevitable without major changes in Home Assistant | 01:20:56 |
| macaroniskengz | Another question, can I pass a secret into Home Assistant and somehow use it when creating the token? | 01:22:05 |
| macaroniskengz | I want my credentials declared as much as possible. | 01:22:32 |
| macaroniskengz | * Another question, can I pass a secret into Home Assistant and somehow use it when creating the token after onboarding? | 01:22:47 |
| @hexa:lossy.network | you can use auth-oidc | 01:22:54 |
| @hexa:lossy.network | if you want to tie it into an idm/sso setup | 01:23:06 |
| @hexa:lossy.network | but again, not declarative user management | 01:23:16 |
| @hexa:lossy.network | * but again, no declarative user management | 01:23:20 |
| @hexa:lossy.network | https://github.com/christiaangoossens/hass-oidc-auth | 01:23:43 |
| macaroniskengz | Not really, seems overkill to be honest as I don't have any OID infrastructure yet | 01:23:57 |
| macaroniskengz | Maybe I just have to accept that Home Assistant will come with some state and I cannot do anything about it | 01:25:51 |
| macaroniskengz | A more HASS related question: can I obtain a "short-lived" access token by performing the usual login flow as part of the frontend to use the WebSockets API? I mean: instead of using a Long Lived Access Token to use the API, I perform the flow and after passing my credentials to Home Assistant I receive a access token that expires in some time. | 01:29:43 |
| @hexa:lossy.network | home-assistant stores the session data in local storage | 01:31:14 |
