| 25 Feb 2025 |
 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 |
| @hexa:lossy.network | * home-assistant stores the session data in local storage in the browser | 01:32:00 |
| @hexa:lossy.network | not sure how it looks on the wire | 01:32:06 |
| @hexa:lossy.network | zigbee2mqtt 2.1.1 on master https://github.com/NixOS/nixpkgs/pull/371053 | 04:09:29 |
| @hexa:lossy.network | it is opt in | 04:09:32 |
| @hexa:lossy.network | use the 25.05 cycle to migrate to zigbee2mqtt_2 | 04:09:51 |
| @hexa:lossy.network | will remove zigbee2mqtt_1 after the 25.05 branch-off, so it will not be in 25.11 | 04:10:06 |
