| 16 Dec 2024 |
 @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 |
| @hexa:lossy.network | I could have rebased further | 22:30:20 |
| netpleb | Ok, that was my plan. Was mostly just not sure if this is a common thing people run into and whether there is a well known way to resolve it (other than "just trying it" on nixos-unstable and seeing if it works :-) ) | 22:31:14 |
| netpleb | Anyway, yes, it looks like the commit in question is in the git history...so I will upgrade back to nixos-unstable. Thanks again for getting all this frigate/hass stuff working! I will surely have more questions :) | 22:33:23 |
 ibizaman | Hi 👋 I installed music assistant and wanted to add the home assistant plugin at /settings/addprovider/hass but got [Errno 2] No such file or directory: 'uv'. I'm happy to put up a PR for fixing this but I'm not sure where to start. I tried to looks at the different music-assistant related packages in nixpkgs and sprinkle some uv python package here and there but without result. Same for adding the Sonos player provider. I'm on nixpkgs 22c3f2cf41a0e70184334a958e6b124fb0ce3e01 FWIW | 22:33:45 |
| @hexa:lossy.network | hm, does it complain for providers you've added declaratively? | 22:34:48 |
| @hexa:lossy.network | same as with home-assistant, you can | 22:35:14 |
| @hexa:lossy.network | * same as with home-assistant, you can't install dependencies interactively | 22:35:25 |
| ibizaman | That difference didn't occur to me at all. I have this currently, let me try adding hass:
services.music-assistant = {
enable = true;
providers = [
"airplay"
"jellyfin"
"radiobrowser"
"sonos"
"spotify"
];
};
| 22:40:41 |
| @hexa:lossy.network | we might be lacking deps for some oft hose | 22:46:06 |
| @hexa:lossy.network | * we might be lacking deps for some of those | 22:46:08 |
| @hexa:lossy.network | sonos = ps: [
]; # missing aiosonos
| 22:46:55 |
