| 25 Jan 2025 |
uep | https://nixpk.gs/pr-tracker.html?pr=373454 | 22:51:40 |
| 26 Jan 2025 |
laurynasp | right I got it now - if PR was merged into stable channel, then nixpk.gs will display pipeline for stable channels. And PR for meging/backporitng into stable channels are automatically recorded on original PRs into master | 09:29:32 |
laurynasp | I noticed you have wake_word in extra components and running server on "tcp://127.0.0.1:10400". Are you using that for Voice PE or for a satellite? | 09:36:32 |
uep | voice pe | 09:37:03 |
laurynasp | Did you have much success with that? I haven't done in-depth research, but default setup for Voice PE does not seem to integrate directly. I guess that's because Voice use microWakeWord on ESP32 | 09:37:15 |
laurynasp | * Did you have much success with that? I haven't done in-depth research, but default setup for Voice PE does not seem to integrate directly. I guess that's because Voice use microWakeWord on ESP32
Or have I confused myself? | 09:37:44 |
laurynasp | Oh, I thingk I found a setting for Streaming wake word engine "hidden" in the tripple dots | 09:39:36 |
uep | though most of the setup was from before voice pe, from a previous experiment like a year ago that didn't get far, and I just uncommented it agan | 09:40:27 |
uep | so it might not be needed | 09:40:31 |
laurynasp | I don't think you need it for PE, because you have 3 inbuilt choices "ok Nabu" being preselected on the Voice PE device configuration page. I think they run via microWake on ESP32 itself. | 09:44:22 |
laurynasp | Out of curiosity, does your service has any errors? Mine seems to report
wyoming-openwakeword[32718]: Error in cpuinfo: prctl(PR_SVE_GET_VL) failed
| 09:45:11 |
laurynasp | * I don't think you need it for PE, because you have 3 inbuilt choices ("ok Nabu" being preselected) on the Voice PE device configuration page. I think they run via microWake on ESP32 itself. | 09:46:00 |
laurynasp | * Out of curiosity, does your wyoming-openwakeword.service experience any errors? Mine seems to report
wyoming-openwakeword[32718]: Error in cpuinfo: prctl(PR_SVE_GET_VL) failed
| 09:46:54 |
| philW joined the room. | 10:31:51 |
@hexa:lossy.network | In reply to @laurynasp:matrix.org
Out of curiosity, does your wyoming-openwakeword.service experience any errors? Mine seems to report
wyoming-openwakeword[32718]: Error in cpuinfo: prctl(PR_SVE_GET_VL) failed
https://github.com/pytorch/cpuinfo/commit/f0d67c613e1a859fdc41238ed5848545e8e0e102 | 11:39:07 |
| 27 Jan 2025 |
| @arjan5:matrix.org joined the room. | 20:08:59 |
| 28 Jan 2025 |
@qbit:tapenet.org | has anyone managed to overlay esphome? | 00:26:23 |
@qbit:tapenet.org | got the preview edition of hte home assistant voice device | 00:26:41 |
@hexa:lossy.network | overridePythonAttrs | 00:27:01 |
@qbit:tapenet.org | but it want's the latest esphome that 374675 added | 00:27:02 |
@hexa:lossy.network | 374675? | 00:27:14 |
@hexa:lossy.network | oh, pr | 00:27:40 |
@qbit:tapenet.org | pr you made | 00:27:41 |
@hexa:lossy.network | same as home-assistant then | 00:27:49 |
@qbit:tapenet.org | (_: super: {
esphome = super.esphome.overridePythonAttrs (oldAttrs: rec {
version = "2024.12.4";
src = super.fetchFromGitHub {
owner = "esphome";
repo = "esphome";
tag = version;
hash = "sha256-Ff3NuLHKRLoBbjqb92vvDcSbSJnjCwm5FmSDwnEI0p4=";
};
});
});
| 00:27:48 |
@hexa:lossy.network | just reference the package from the unstable channel | 00:28:03 |
@qbit:tapenet.org | is what I have, and it seems to build .. except the service doesn't snag it | 00:28:10 |
@hexa:lossy.network | sigh | 00:28:19 |
@hexa:lossy.network | I don't maintain the service, but let me look what it does | 00:28:25 |
@hexa:lossy.network | it consumes pkgs.esphome, so overlaying it should work | 00:28:57 |