Honestly, I think I finally have this little jerk working, after all this troubleshooting.
Here’s a recap of my woes for anyone stumbling upon this page, looking for help:
My girlfried bought me a Pi v3B last Christmas, and I had been trying to figure out what to do with it, since I like the Pi v4-8GB.
I found Mycroft, and the Google AIY v1 was listed as supported.
I bought an AIY v1 voice kit for $30 off eBay and printed an enclosure on my Sovol SV01 3D printer.
The new Buster Raspbi images break the AIY v1 mic, unless the 91-pulseaudio-rpi.rules file is edited, using what I have written in one of the above posts.
The file is found in /lib/dev/rules.d. Once edited, reboot and test out mic.
Switch listener from Sphinx to Precise; since it loads Sphinx from default.
I am using the default Hey Jarvis wake-word, which was selected when doing the online pairing.
Edit mycroft-config with what I have in one of the above posts.
Change mic volume from 100% to 30-35% in alsamixer.
From what I see here[1], there is only Hey Mycroft . From the source code[2], I can see an URL which I’m not able to browse so maybe there are the three others there.
@JarbasAl@goldyfruit Here is a screenshot of my phone on the account.mycroft.ai page. I have selected Hey Jarvis, and my .conf file has Precise configuration. It is working. I’m not sure what you guys are seeing, but that is what I have.
Regardless of the wake-word used, my wake-word problem was my mic input being too loud. Once lowered, the wake-word activated Mycroft from only a few feet away.
I do not know your program but if the voice recognition relies on the pyaudio library, it has been ascertained that the updated version of pulseaudio conflicts with pyaudio
@nerlins Good to hear you are up and running as well.
will check if the 91-pulseaudio-rpi.rules file is still around after I did rerun the setup-wizard
I had the mic work randomly once on an install without changing the file. It was like magic, but then went away. I would alter the file, like I did, because the mic now works 100% of the time.
this probably happened because as soon as you installed the image, pulseadio was not yet updated to the rpi2 version which contains that file 91.
maybe not everyone knows that after 2 days, the Raspberry is set to download updates automatically and consequently pulseaudio as well that’s why many users say they haven’t touched anything and that it broke by itself. on January 8th they released the new kernel update but I still haven’t checked if they fixed that problem.
Update:
I now changed to an USB mic instead, as I have a suspision that the mic may never have worked (as I did’nt have success with Googles official install either). So, unless other people have same problem, it might be a hw problem.
@rune1979 Sorry, I haven’t logged in here for a bit. I just updated the system and now my Google AIY voicekit skill isn’t working. I’ll see what’s going on.
Actually, no, it looks like it just needed to be rebooted. Honestly, I never had mic problems after I edited that file pulseaudio file. Also, ended up rebuilding my Mycroft from scratch, using the recipe procedure (I had a lot of trouble with the pre-made images):
Another point that should be made is that you shouldn’t have to edit that file anymore. After all my troubles there was another update which fixed the pulseaudio issues. You might be right that the mic didn’t work. If the USB mic works, then great. It also might be worth purchasing another kit if you can find one on the cheap.
FTR, I recently was able to install the official Picroft_v20.08_2020-09-07.img.zip onto a RP3B with the AIY voicehat v1 hardware and didn’t have to do anything special to make the mic and speaker work except choose “AIY voice hat” during the installation. Installing the voicehat skill after that made the light work too.
