Read the statement by Michael Teeuw here.
MMM-voice
-
@daveyg_71 when you do what strawberry suggested after you reboot redo the
arecord -l
Like he said you may have to do it a couple times but it should show you more than likely your mic is 1
-
@Nonamexp my guess is because you installed it in /root/… instead of /home/pi/… so it cant find the file
-
@strawberry-3.141 Thanks for the advice. I plugged the mic into my Mac and I couldn’t get it to see it. Must be the mic. I ordered a new one so I will find out in a few days.
-
If I run the installation, there is allways a error when it wants to install the PocketSphinx.
What is wrong? -
@SimJim do you have some more output to provide?
-
This is what happens all the time…

-
@SimJim i will test this tonight
-
I’ve the next problem: On the Mirror shows the message ‘Error’ , ‘No Moduls identified’.
in the Error Log: Error: spawn pocketsphinx_continuous ENOENT-2help me pls ;(
-
@Nonamexp as I said due to installing in root directory the binary will not be found
@SimJim Error code 56 indicates a curl receive error of CURLE_RECV_ERROR which means there was some issue that prevented the data from being received during the clone process. Typically this is caused by a network setting, firewall, VPN client, or anti-virus that is terminating the connection before all data has been transferred. It’s not related to this module this is something general
-
@cowboysdude I got the new mic, and the pi can see it now, but the mirror is showing error next to the microphone.
Is there anything wrong with my config file?
{ module: 'MMM-voice', position: 'bottom_bar', config: { microphone: 1, keyword: 'MAGIC MIRROR', timeout: 15, } }, -
@daveyg_71 there is an error log in the mmm-voice directory can you post it? and do you get any errors in the terminal or electron console?
-
@strawberry-3.141 said in MMM-voice:
@daveyg_71 there is an error log in the mmm-voice directory can you post it? and do you get any errors in the terminal or electron console?
What please do what @strawberry-3-141 said :) Look in the directory for an error log… or when you start your mirror run it in dev mode: npm start dev
-
@strawberry-3.141 I opened up the error log and this is all I see:
1271271271271111111111111111
The mirror starts up with no problems. It just says error next to the microphone symbol.
-
i have sometimes the same error. Do u have restart the mirror via pm2 restart mm?
-
Hi @strawberry-3.141, I’ve just tried running the dependencies.sh from the latest .git to install MMM-voice and hit this error in step 5;
[STEP 5/6] Installing npm dependencies
dependencies.sh: line 106: cd: /root/MagicMirror/modules/MMM-voice: No such file or directory
npm WARN enoent ENOENT: no such file or directory, open ‘/root/pocketsphinx/package.json’despite the fact that pocketsphinx seemed to come down and compile okay. I’m logged in as the pi user via ssh and ran the shell script with sudo bash dependancies.sh.
Do you have any suggestions as to what’s happened?
many thanks
-
@darrene yes dont run the script with sudo. as you can see it tries to install and look for files in root instead of home pi
-
@strawberry-3.141 Doh! Thank you :)
-
Hmm, I too am getting the ‘Error’ mic icon message, once it finishes its initialisation phase when the mirror starts up.
I’m started in dev mode - both the web and terminal consoles look clean - the last report I have in the terminal is 'MMM-voice: Starting pocketsphinx, so I don’t know if I should expect anything further messages in that console.
I’ve taken a look in the MMM-voice/error.log which contains the value ‘127’. It’s repeatable - if i stop the mirror, remove the error log and restart, I get the same results. As a test I’ve tried altering the microphone value in the config.js from it’s initially correct value of 1 - It doesn’t affect the error, which leads me to believe it may not be a hardware issue(?)
It’s such a shame - all steps reported to have completed okay, the microphone was detected - nothing looks to have been out of the ordinary.
Is there anything else I can do to test or anywhere else I can look, before I try flattening the SD card and reinstalling? -
progress of a sort…
tried a sudo apt-get update, followed by a rebootsame clean startups but between the ‘initialising’ and ‘error’ states I briefly get a ‘no mode found’ and the 127 error is gone - now I just get a 1 returned in the error log
-
@darrene no Mode found is the expected behaviour, you can also Enable debug:true this will give You an debug log
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login