MMM-voice

[daveyg_71]

@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.

[SimJim]

If I run the installation, there is allways a error when it wants to install the PocketSphinx.
What is wrong?

[strawberry 3.141]

@SimJim do you have some more output to provide?

[SimJim]

This is what happens all the time…

[strawberry 3.141]

@SimJim i will test this tonight

[Nonamexp]

I’ve the next problem: On the Mirror shows the message ‘Error’ , ‘No Moduls identified’.
in the Error Log: Error: spawn pocketsphinx_continuous ENOENT-2

help me pls ;(

[strawberry 3.141]

@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

[daveyg_71]

@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,
                    }
            },

[strawberry 3.141]

@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?

[cowboysdude]

@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