| 18 Feb 2025 |
 uep | nixos module in a nixos-container | 08:07:10 |
| uep | (mostly because i want to give it its own IP address | 08:07:29 |
| uep | * (mostly because i want to give it its own IP address) | 08:07:32 |
 j-k | If I'm using home-assistant should I be on nixos-unstable rather than nixos-unstable-small? Looks like I got a cache miss on home-assistant | 12:26:24 |
 K900 | It's a pretty cheap build | 12:31:58 |
| K900 | But it's not blocking unstable-small no | 12:32:03 |
 @hexa:lossy.network | very few things block unstable-small :) | 12:47:23 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/blob/master/nixos/release-small.nix#L83-L162 | 12:48:20 |
| j-k | 👍️ thanks both. | 12:53:08 |
| j-k | I'm reading through the nixos org wiki entry and trying to address
Error occurred loading flow for integration nest: No module named 'grpc'
Do I need to create a PR to change the actual component-packages.nix in nixpkgs or is there a good pattern for adjusting/overriding/configuring?
| 12:59:34 |
| K900 | You can just add it to extraPythonPackages or whatever the name of that thing is | 13:00:21 |
| j-k | 👍️ cool. TY
And can I ban integrations? I'm getting logs failing to start the apple_tv integration but I don't have one on the network or in my config | 13:05:31 |
| K900 | You kinda can | 13:10:58 |
| K900 | You basically need to disable the default config | 13:11:24 |
| K900 | And then pick the bits of it that you want | 13:11:29 |
| K900 | Which is very silly | 13:11:33 |
| @hexa:lossy.network | that error is triggered by discovery | 13:11:36 |
| @hexa:lossy.network | basically home-assistant's discovery component knows what to look for as supported components | 13:12:19 |
| @hexa:lossy.network | https://github.com/home-assistant/core/blob/dev/homeassistant/components/apple_tv/manifest.json#L11-L55 | 13:12:23 |
| @hexa:lossy.network | (I feel like we've had this discussion months ago already 🤔) | 13:12:35 |
| @hexa:lossy.network | so what you'd need to disable is zeroconf, not sure you want to disable that | 13:13:27 |
| @hexa:lossy.network | https://www.home-assistant.io/integrations/default_config/ | 13:13:34 |
| j-k | eh, maybe I'll just ignore that one or just add "apple_tv" to extraComponents | 13:44:28 |
| @hexa:lossy.network | honestly, that is how I dealt with that 😄 | 13:44:52 |
 oddlama | Has anyone here already tried the HA Voice PE and had success connecting it to hass? | 14:24:14 |
| @hexa:lossy.network | yes | 14:25:51 |
| @hexa:lossy.network | it require IPv4 if you don't have that | 14:25:57 |
| @hexa:lossy.network | * it requires IPv4, if you don't have that | 14:26:02 |
| oddlama | I do have ipv4. It's a bit weird, because the esphome part works fine, and it requests the .flac file from the HA server and gets a 200 response. But the frontend somehow calls assist_satellite/test_connection on the entity which fails with a timeout without logging why that happens. | 14:29:29 |
| oddlama | Initially i found that there was an issue when the internal url is served via https, but that had already been fixed in the version I'm using | 14:30:21 |
