| 12 Dec 2024 |
 spacekitteh | ah | 23:44:39 |
 @hexa:lossy.network | because they are effectively home-assistant.overridePythonAttrs {} | 23:45:01 |
| @hexa:lossy.network | to get the same environment as home-assistant but only run the tests | 23:45:15 |
| spacekitteh | i'm surprised fetchFromGithub doesn't automatically create a derivation tbh | 23:47:52 |
| @hexa:lossy.network | all sources are fixed output derivations | 23:51:50 |
| spacekitteh | sorry, i mean it doesn't create the derivation for the decompressed src, rather than the compressed src | 23:52:48 |
| 13 Dec 2024 |
| spacekitteh | hmmm. whenever i try to use the homeassistant mobile app to connect to HA behind an nginx reverse proxy, it seems to cause a hang in nginx with zstd compression | 03:37:16 |
| 14 Dec 2024 |
| spacekitteh | in my HA home settings, is there a way to read the lat/long of my home via a sops-nix file? | 03:26:16 |
| spacekitteh | oh of course there is, i'm still waking up x3 | 05:01:27 |
| 16 Dec 2024 |
 boolis | how do I enable the wakeword engine in home-assistant?
home-assistant.config.wake_word = {};
home-assistant.extraComponents = [ "wake_word" ];
| 13:33:16 |
| @hexa:lossy.network | uh, something wyoming? | 14:44:23 |
| @hexa:lossy.network | take a look at services.wyoming.openwakeword | 14:45:35 |
| @hexa:lossy.network | then enable the wyoming component in home-assistant | 14:45:43 |
| @hexa:lossy.network | and connect the two | 14:45:49 |
| boolis | oh right, apparently I have that enabled aswell.
I had this working a while back but now it just doesnt | 14:50:46 |
| @hexa:lossy.network | hm ok | 14:51:50 |
| @hexa:lossy.network | wakeword has regressed for me recently as well | 14:51:56 |
| @hexa:lossy.network | leaking lots of fds | 14:52:11 |
| @hexa:lossy.network | ls -1 /proc/$(systemctl show -P MainPID wyoming-openwakeword)/fd/ | wc -l
| 14:52:58 |
| @hexa:lossy.network | can you check how many fds your process has? | 14:53:08 |
| boolis | 13 | 14:56:43 |
| boolis | I haven't connected home-assistant to openwakeword thou | 14:58:05 |
| boolis | but connecting the two actually enabled the engine.... but I want to use microwakeword with es32-s3-box | 14:59:43 |
| @hexa:lossy.network | ah, ok | 15:00:17 |
| @hexa:lossy.network | I have never used that, but it should use the wyoming protocol as well, no? 🤔 | 15:00:28 |
| @hexa:lossy.network | or possibly through esphome? 🤔 | 15:01:20 |
 netpleb | hexa: I have a dumb question. Right now my nixpkgs for my flake system is pointed at "https://github.com/mweinelt/nixpkgs/frigate-libedgetpu" which is an old branch that you had made. I think the branch has since been merged but github gives me a 404 so I'm not certain. Prior to using your branch, I was on nixos-unstable. | 22:27:21 |
| netpleb | Is there some way for me to use the hash in the lock file to figure out if your banch got merged into nixos-unstable? | 22:28:37 |
| @hexa:lossy.network | check the commit history on the frigate package maybe | 22:30:02 |
| @hexa:lossy.network | I'm not sure the hash would be the same | 22:30:15 |
