Hi,
Recently, I’ve been noticing that as I issue voice commands in OVOS, it rarely detects my wake word now. I am using the default trigger phrase hey_mycroft
, but I’ve also been working on converting my precise-engine model to tflite. To ensure it isn’t just my custom model, I’ve switched it back in a new Raspberry Pi install on the Pi 4: 4 GB, and still notice it struggling just as much before I do anything custom to OVOS. It used to work really well, but it seems like the default wakeword detection has gotten worse for me over time, even on fresh installs of OVOS and Raspberry Pi OS. I’ve tested my mic (Logitech C270) in general and it still works just as well in general, so I’m assuming it could be from recent changes on OVOS (which I’ve been updating).
I decided to try my current webcam (Logitech C922) and it works a little better, but still misses the hotword every once in a while with the default wakeword model. I’ve also noticed that it keeps listening for much longer than it used to before executing the spoken command. I tried making my command succinct to make it clear when I was done issuing my command, but it still does that, unlike before when things were working better with OVOS/Mycroft. I’m assuming the stop listening default thresholds must have also changed over recent OVOS updates?
Do you have any idea why these things would have changed over time? I would still like to use my old webcam (C270) for the mic since it used to work very well when I first started using OVOS and back when I used Mycroft. I am trying to get this back to normal with hey_mycroft
before I start adding my custom trigger phrase into the mix, which doesn’t work at all (but used to very well in Mycroft’s precise-engine-0.3.0
with my own voice data).
For when I do get my custom trigger phrase working after resolving this issue with hey_mycroft
in general, can you also confirm whether my hotwords entry is correct, which I adapted from hey_mycroft
:
"computer": {
"module": "ovos-ww-plugin-precise-lite",
"local_model_file": "/home/pi/.local/share/mycroft/trigger_phrases/computer.tflite",
"expected_duration": 3,
"trigger_level": 3,
"sensitivity": 0.31,
"listen": true,
"fallback_ww": "hey_mycroft"
},
I appreciate any insights you have to offer for me to get a usable voice assistant working again, mainly from the hotword not being detected reliably anymore even on a fresh OS install!