| 26 Jan 2025 |
 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 |
| @qbit:tapenet.org | hm | 00:30:36 |
| @qbit:tapenet.org | wesphome --version shows the expected version | 00:32:53 |
| @qbit:tapenet.org | oh.. my god.. lol | 00:33:39 |
| @qbit:tapenet.org | bitten by the tailnet.. | 00:33:49 |
| @qbit:tapenet.org | i don't know where anything runs on my network anymore \o/ | 00:33:55 |
| @qbit:tapenet.org | thanks for the clue sticks! | 00:39:01 |
| @hexa:lossy.network | yw | 00:39:44 |
| laurynasp | qbit: out of curiosity, what do you use "services.esphome" for? | 12:11:18 |
| laurynasp | I am asking because I used it, but found it impractical for my use case, which was automating setup/updates of my esp32 devices, This was mostly because (i) nixos service does not have many options exposed (e.g. preExec systemd services) and (ii) esphome itself does not like symlinks. Both things together made it difficult to use "auto-generated" config files for my devices
| 12:11:28 |
