| 6 Feb 2025 |
 @hexa:lossy.network | continuing to bisect the stream test | 18:09:16 |
 colonelpanic | has anyone had success getting wyoming working?
My suspicion is that my audio is not properly getting handled by the satellite but it doesnt seem like theres super easy ways to work out what its actually receiving | 22:09:17 |
| @hexa:lossy.network | that's not a super helpful error message, and yes I've had wyoming-satellite running for a ong time | 22:17:52 |
| @hexa:lossy.network | basically run the thing under a user that has an audio daemon running | 22:18:12 |
| @hexa:lossy.network | and inspect with e.g. pavucontrol or ncpamixer what audio interfaces it has bound to | 22:18:25 |
| colonelpanic | @hexa:lossy.network: oh there is no error message. | 22:29:45 |
| colonelpanic | It just doesn't seem to work. It just logs that it's waiting for a wake word and never triggers. Im running it under my main user, because that was the only thing that seemed to work | 22:30:30 |
| @hexa:lossy.network | so is it recording? | 22:31:15 |
| colonelpanic | Yes it seems like it's bound to the correct audio interface that seems to register sounds level in pavuconteol | 22:31:18 |
| @hexa:lossy.network | and it registered in home-assistant? | 22:31:34 |
| @hexa:lossy.network | and you set up a pipeline for it? | 22:31:39 |
| colonelpanic | Well I mean it *seems* to be. But I guess I'm not sure how to check on that | 22:31:43 |
| @hexa:lossy.network | you have wyoming-openwakeword running? | 22:31:49 |
| colonelpanic | Yes it's registered in home assistant, | 22:31:57 |
| colonelpanic | Yes and I set the flag to the address for the wake word server running | 22:32:13 |
 dotlambda | In reply to @hexa:lossy.network
continuing to bisect the stream test Any results? | 22:32:18 |
| @hexa:lossy.network | I'm unfortunately not using the satellite anymore since I've bought the voice pe hardware | 22:32:27 |
| @hexa:lossy.network | bisect goes across staging, so lots of fun involved | 22:32:38 |
| @hexa:lossy.network | tried nixpkgs-staging-bisecter, but it crashed on me | 22:32:54 |
| colonelpanic | Yeah I was going to say, I actually had to do an overlay for the satellite to make it work because a dependency got bumped that is stricter about the chunking | 22:33:03 |
| @hexa:lossy.network | hydrasect doesn't work anymore either | 22:33:05 |
| colonelpanic | So I guess I'd be surprised if anyone else had it working | 22:33:12 |
| @hexa:lossy.network | hm | 22:33:23 |
| colonelpanic | @hexa:lossy.network: do you have the exact config you were using when you had it working? | 22:33:32 |
| @hexa:lossy.network | services.wyoming.satellite = {
enable = false;
user = "hexa";
group = "users";
sounds = {
awake = "/etc/nixos/start_of_input.wav";
done = "/etc/nixos/end_of_input.wav";
};
extraArgs = [
"--snd-volume-multiplier" "0.5"
];
};
| 22:33:48 |
| @hexa:lossy.network | * services.wyoming.satellite = {
enable = false;
user = "hexa";
group = "users";
sounds = {
awake = "/etc/nixos/start_of_input.wav";
done = "/etc/nixos/end_of_input.wav";
};
extraArgs = [
"--snd-volume-multiplier" "0.5"
];
};
| 22:33:51 |
| colonelpanic | Wow okay, don't you need to specify the wake word address? | 22:34:23 |
| @hexa:lossy.network | uh no | 22:34:33 |
| @hexa:lossy.network | that is a pipeline that goes via home-assistant | 22:34:40 |
| @hexa:lossy.network | home-assistant is like a control panel for that pipeline | 22:34:51 |
