@d3r said in Yet Another Voice Module (Sphinx + Alexa):
Unable to run Alexa Java Client: Error: ENOENT: no such file or directory, open './magic-mirror-voice/alexa-certificate-generator/certs/server/node.key
Do you have the optional sslKey entry in the config? If you are autogenerating all the keys, I would remove all the //optional values from the ssl configuration. May be a red herring but all I can think of w/o my computer.
I went to that directory and the files do exist. I used the script to generate them. My understanding is sphinx is working but there’s something wrong with the alexa part.
From the logs this seems to be true. Thanks for the log, it makes debugging much easier. As mentioned in OP, my life is pretty hectic right now. I’m hoping to have some chance to look into this over the next week but may not be able to provide the optimal feedback cycle for you. Thanks for the patience.
If I already have the alexa voice service set up on the pi is there an ‘easier’ way of setting this up or would it be better to start from scratch?
I’ll of course back up my sd card before playing with this.
If you already have Alexa set up, then you should have all the required bits. Just update the configuration with your productId, dsn, clientId, clientSecret, alpnVersion, vlcPath, vlcPluginPath (all of which you acquired when setting up Alexa). For first run, I’d try to do serveronly mode so you don’t have to mess with the electron node version disparity.
node serveronly
then open a browser on the pi @ http://localhost:8080. If this works, then follow the Installation Notes.
sed -i ‘s/“electron-prebuilt”: “latest”/“electron-prebuilt”: “1.2.8”/g’ package.json
sed: can’t read package.json: No such file or directory
Answered in the GitHub issue https://github.com/whyjustin/magic-mirror-voice/issues/1
So it its always listening in your version?
Yup, Sphinx is always listening (as long as Alexa is not listening). You can configure the command that invokes Alexa in the sphinx:commands dictionary. Any key in the object will be recognized by Sphinx and perform the action as configured by the value. For example:
"mirror mirror": {
action: 'alexa'
}
Saying “mirror mirror” will trigger Alexa.
Note from admin: Please use Markdown on code snippets for easier reading!
Sounds great… what is the response time like?
Response time of what? Loading time is pretty slow given the bootstrapping, but that should only happen once. The Sphinx client actively listens for commands as set in the JSON sphinx:commands dictionary and processes speech every time you pause. Alexa will record until you are quiet for over 2 seconds and then send it off the Amazon Voice Services. Guessing this response is similar to an Echo but I’ve never owned one.
Hey all,
I’m happy to be making my first post to this community. I discovered it recently when embarking upon making a Magic Mirror and am impressed by the active support and discussion that occurs. Not sure if this post belongs in Development or Showcase as the module is mostly done, but I just had a daughter and may not be able to provide initial support for it so wanted to do a soft release here first.
I know there are existing voice modules for MM2 but I found my use case was to use Alexa alongside Sphinx, providing all the voice recognition functionality within one module. This prevents different modules competing for resources (microphone) and having to synchronize the allocation and deallocation of these resources. The hope is that non-audio related functionality will be handled by other modules, there is a not yet documented command with action “sendNotification” that will allow configuring certain voice commands to invoke a process in a different module.
Another goal for this project was to eliminate the need for lengthy configuration and setup. The module prefers convention to configuration, and most of the nerdy voice recognition and Alexa setup is bootstrapped for the user during the load. This allows the user to have a simple json configuration and the module will generate the appropriate ssh keys and language models/dictionaries required for the module to work.
Enough talk, here is the module. Pull requests warmly welcome, around documentation or functionality. Thanks.
