| 22 Jan 2025 |
 @hexa:lossy.network | if you want to edit it from the frontend then home-assistant will manage storing all that information and you'll have to add the resources yourself | 17:16:45 |
| @hexa:lossy.network | if you want the latter, set lovelaceConfig = null | 17:17:14 |
 Ekleog | Thank you for all your answers! It's pretty weird, but it seems that restarting firefox fixed the issue… weird 🤷
Thank you! :D | 17:22:40 |
| @hexa:lossy.network | ok lol | 17:23:43 |
| @hexa:lossy.network | sounds like a caching issue then | 17:23:48 |
| 24 Jan 2025 |
 laurynasp | My Voice PE has just arrived, but I am having a bit of a trouble with step 7. I do not want to use cloud, and setup instructions say to use whisper and piper add-ons, which is where I get confused..
It seems that add-ons are availalabe only for HAOS and supervised, but on NixOS we have HA-core, is that correct?
I found Whisper integration, but I struggle to understand what it is for, and it page for it seems to refer to Wyoming protocol integration..
| 08:15:28 |
| laurynasp | So I thought to check if anyone has their setup available to share or knows a blog post, before I start experimenting with those integrations | 08:15:53 |
 uep | services.home-assistant = {
# ...
extraComponents = [
# ...
# voice assistant
"piper"
"whisper"
"wake_word"
"wyoming"
];
};
};
services.wyoming = {
faster-whisper.servers.whisper = {
enable = true;
uri = "tcp://127.0.0.1:10300";
device = "cpu";
language = "en";
model = "medium-int8";
};
openwakeword = {
enable = true;
uri = "tcp://127.0.0.1:10400";
};
piper.servers.piper = {
enable = true;
uri = "tcp://127.0.0.1:10200";
voice = "en_GB-semaine-medium";
};
};
| 10:57:38 |
| uep | then you add those three ports via the wyoming integration in the HA UI | 10:58:48 |
| uep | and you add the voice device via the esphome integration, which was where i got well confused | 10:59:50 |
| uep | * services.home-assistant = {
# ...
extraComponents = [
# ...
# voice assistant
"piper"
"whisper"
"wake_word"
"wyoming"
];
};
services.wyoming = {
faster-whisper.servers.whisper = {
enable = true;
uri = "tcp://127.0.0.1:10300";
device = "cpu";
language = "en";
model = "medium-int8";
};
openwakeword = {
enable = true;
uri = "tcp://127.0.0.1:10400";
};
piper.servers.piper = {
enable = true;
uri = "tcp://127.0.0.1:10200";
voice = "en_GB-semaine-medium";
};
};
| 11:00:35 |
| laurynasp | Thanks! | 11:31:01 |
| laurynasp | I got it to work, thanks a lot uep!
| 15:49:23 |
| laurynasp | P.s. I noticed that on nixos-unstable (9e4d5190a9482a1fb9d18adf0bdb83c6e506eaab), wyoming-piper-piper.service fails because voices are downloaded to --download-dir /var/lib/wyoming/piper/models , but --data-dir /var/lib/wyoming/piper and "find_voice" in (/nix/store/xxx-wyoming-piper-1.5.2/lib/python3.12/site-packages/wyoming_piper/download.py) does not seem to search recursively. For now, I just manually move downloaded voices to /var/lib/wyoming/piper/ | 15:49:28 |
| laurynasp | * P.s. I noticed that on recent nixos-unstable (9e4d5190a9482a1fb9d18adf0bdb83c6e506eaab), wyoming-piper-piper.service fails because voices are downloaded to --download-dir /var/lib/wyoming/piper/models , but --data-dir /var/lib/wyoming/piper and "find_voice" in (/nix/store/xxx-wyoming-piper-1.5.2/lib/python3.12/site-packages/wyoming_piper/download.py) does not seem to search recursively. For now, I just manually move downloaded voices to /var/lib/wyoming/piper/ | 15:49:46 |
| @hexa:lossy.network | oh no 😕 | 15:54:49 |
| @hexa:lossy.network | why can you specify both then? | 15:55:44 |
| laurynasp | * P.s. I noticed that on recent nixos-unstable (9e4d5190a9482a1fb9d18adf0bdb83c6e506eaab), wyoming-piper-piper.service fails because voices are downloaded to --download-dir /var/lib/wyoming/piper/models , but --data-dir /var/lib/wyoming/piper and find\_voice in (/nix/store/xxx-wyoming-piper-1.5.2/lib/python3.12/site-packages/wyoming\_piper/download.py) does not seem to search recursively. For now, I just manually move downloaded voices to /var/lib/wyoming/piper/ | 15:56:00 |
| laurynasp | Yeah, it does seem a bit strange.. I think data dirs can be a list of directories (having peeked at the pyton code briefly), but I am not that good at python, so I might be wrong | 15:57:16 |
| @hexa:lossy.network | https://github.com/rhasspy/wyoming-piper/blob/master/wyoming_piper/__main__.py#L43 | 16:09:45 |
| @hexa:lossy.network | the download-dir is the first data dir 🤡 | 16:09:51 |
| @hexa:lossy.network | and if there is no downloads dir, then the first data dir becomes the downloads dir | 16:10:17 |
| uep | yah, i noticed my HA box was failing builds after the last staging landed a couple of days ago, and that it was something with the voice things, but didn't look further. | 16:10:37 |
| @hexa:lossy.network | I made a bunch of changes based on homeassistant-addons | 16:10:55 |
| @hexa:lossy.network | but I only approximated them and merged after two days without review | 16:11:04 |
| @hexa:lossy.network | and obviously I made errors in that 🫣 | 16:11:11 |
| @hexa:lossy.network | ok, this is stupid | 16:12:55 |
| @hexa:lossy.network | data dir is required | 16:13:23 |
| @hexa:lossy.network | download dir is optional | 16:13:27 |
| @hexa:lossy.network | and if you set a download dir, then it does not move anything to the datadir | 16:13:46 |
