| 6 Feb 2025 |
 dotlambda | Anyway, I think 2025.2.0 is ready barring a rebase | 16:25:31 |
 Sandro 🐧 | In reply to @robert:funklause.de
@sandro:supersandro.de: Any feature my version is missing? I didn't took a deeper look yet but probably not. Mine was pretty basic but if I find anything I'll let you know | 16:25:59 |
 @hexa:lossy.network | bisecting that as we speak | 16:26:34 |
| @hexa:lossy.network | also home-assistant-component-tests.sensor complains about a missing translation string, and that it should be added to a strings.json | 16:27:44 |
| @hexa:lossy.network | but it is already there | 16:27:53 |
| @hexa:lossy.network | would be good to understand why that breaks | 16:28:00 |
| @hexa:lossy.network | Failed: Translation not found for sensor: `issues.state_class_removed.description`. Please add to homeassistant/components/sensor/strings.json
| 16:29:16 |
| @hexa:lossy.network | anyway, merging now is pretty pointless, given that staging-next was just merged and that will clog hydra for two days or so | 16:46:57 |
| dotlambda | In reply to @hexa:lossy.network
anyway, merging now is pretty pointless, given that staging-next was just merged and that will clog hydra for two days or so It would prevent merge conflicts. | 17:07:59 |
| @hexa:lossy.network | and fix regressions, yeah | 17:08:21 |
| dotlambda | I probably won't have time to look into the handful of component tests that are still failing for a few days | 17:09:46 |
|  SomeoneSerge (utc+3) changed their display name from SomeoneSerge (Gand St. Pieters) to SomeoneSerge (UTC+U[-12,12]). | 17:48:15 |
| @hexa:lossy.network | rebased and merged | 18:09:11 |
| @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 |
