Yet Another Voice Module (Sphinx + Alexa)

[whyjustin]

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.

[d3r]

@whyjustin said in Yet Another Voice Module (Sphinx + Alexa):

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.
Thank you, I got till that part and the modules are currently loading. Your module and 2 others haven’t loaded yet. How long should it usually take?
I am using the firefox iceweasel browser.
Edit: I reloaded the page and not all my modules are loaded except the voice one. Which makes sense because I haven’t run the npm install from the module directory yet. Will do that and post back.

[d3r]

@whyjustin
I was able to set up the module but I think I did a few things wrong. I think I have the vlcPluginpath wrong in my configuration. I am not sure where it is located. I believe it is here "vlcPluginPath: ‘/usr/lib/vlc/plugins’ " but I am not sure what exacly I should be looking for. When the module loads, there is currently nothing under the module. If I reload the page it switches to “loading…” and is stuck on “loading…”
Also , once I run node serveronly and open up the localhhost page the voice module does start to load but I get the following error:
`
Listening for transport dt_socket at address: 5005
Unable to run Alexa Java Client: Error: ENOENT: no such file or directory, open './magic-mirror-voice/alexa-certificate-generator/certs/server/node.key

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. I’m not really sure what I should do next. I’ll keep playing with it, hopefully I’ll get it to work.

Full log here:

[whyjustin]

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.

[whyjustin]

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

[d3r]

@whyjustin Thank you. I understand you’re pretty busy with your familly so no rush.

You were correct about the optional ssl. I commented it out and was able to get to the alexa registering part
Register Alexa Java Client by navigating to https://localhost:5555/provision/143d3e3b67c6577291228ff9
Now the problem is that the module is not registering. I cannot connect to that link if I put it in a browser. Also, I think it should be localhost:3000/provision/... because that’s how the alexa standalone app registration works but I could be wrong.
I played around with the config.
port: 5555,
serviceUrl: ‘https://localhost:5555’, // if I change this to port 3000 I get an error /
redirectUrl: ‘https://localhost:3000/authresponse’, // changing this port still returns https://localhost:5555/provision/143d3e3b67c6577291228ff

Again no rush, this can wait.

[whyjustin]

Now the problem is that the module is not registering. I cannot connect to that link if I put it in a browser.

This is a long shot since you’ve setup Alexa already, but are you using a browser on the pi to connect to the site? If not you would have to replace localhost with the pi’s IP/Hostname

Also, I think it should be localhost:3000/provision/… because that’s how the alexa standalone app registration works but I could be wrong.

The oauth service can run on any port, I believe that 3000 may been taken by another process on my raspberry pi (either by Magic Mirror or something else) which is I why I used 5555. I think there is some redundancy in the three options (port/serviceUrl/redirectUrl) but it is required to keep the same port and hostname on all three. If you choose to keep 5555, you will have to update the Alexa settings that you previously set up to indicate the proper port:

https://github.com/alexa/alexa-avs-raspberry-pi/blob/master/assets/avs-web-settings-filled.png

[d3r]

@whyjustin said in Yet Another Voice Module (Sphinx + Alexa):

The oauth service can run on any port, I believe that 3000 may been taken by another process on my raspberry pi (either by Magic Mirror or something else) which is I why I used 5555. I think there is some redundancy in the three options (port/serviceUrl/redirectUrl) but it is required to keep the same port and hostname on all three. If you choose to keep 5555, you will have to update the Alexa settings that you previously set up to indicate the proper port:
https://github.com/alexa/alexa-avs-raspberry-pi/blob/master/assets/avs-web-settings-filled.png

Thank you.
Changed the port on the amazon website and I got it to work.
Your module is awesome! This is really good.

[whyjustin]

@d3r said in Yet Another Voice Module (Sphinx + Alexa):

Your module is awesome! This is really good.

Thanks, good to hear it’s working. Let me know if you have any other difficulties or feature requests. As mentioned to @cowboysdude, it is easiest for me to track these through GitHub Issues. Cheers.

[clumsy_ninja]

@whyjustin What kind of visual feedback does it display on the mirror?

[d3r]

@clumsy_ninja This module has no visual feedback. You only get an audio prompt which indicates that alexa is listening and a second audio prompt when the audio stops.

[clumsy_ninja]

@d3r Thanks. I’ve been looking at AlexaPi and i’m not sure how similar the code is but i did notice is has led’s indicating the status (listening, processing, speaking).
https://github.com/alexa-pi/AlexaPi

What i really want to achieve is a module for the mirror which shows the visual feedback with a microphone icon and also show the GUI cards alexa service returns. Problem is I’m not sure how to make this hahah I’m only use to writing in C and Java.

[whyjustin]

@clumsy_ninja said in Yet Another Voice Module (Sphinx + Alexa):

notice is has led’s indicating the status (listening, processing, speaking).
https://github.com/alexa-pi/AlexaPi

IIRC I exposed some of this stuff in the plugin, it shouldn’t be too hard to provide UI feedback for these events. Look at the events passed to the Java client here: https://github.com/whyjustin/magic-mirror-voice/blob/master/node_helper.js#L49. If you get anything working, PRs welcome.

What i really want to achieve is a module for the mirror which shows the visual feedback with a microphone icon and also show the GUI cards alexa service returns. Problem is I’m not sure how to make this hahah I’m only use to writing in C and Java.

GUI Cards are going to take more work.

[clumsy_ninja]

@whyjustin Thanks for that, I’m new to javascript myself but I’m trying to recruit a mate to give us a hand haha. I’ll post something back if I get anything working.

[clumsy_ninja]

@whyjustin Is it possible to change the activation work in your alexa? I remember seeing it defined in json somewhere but does it require voice training or something?

[lb-rezende]

Hi,

I’m having a problem installing this module and maybe someone could help me, because this is my first experience with Linux and the Magic Mirror.

I followed the link describe in the Github to install Alexa. It was everything ok, I talked to her at the end.

I followed the rest of the instructions to install the module, although when I start the Magic Mirror it keeps at “loading” and after a while the application crash.

The last message is:
Listening for transport dt_socket at address: 5005
electron js/electron.js: …/src/java.cpp:105: v8::Localv8::Value Java::ensureJvm(): Assertion `result->IsNull()’ failed.

How can I solve it?

Thanks in advance.

[whyjustin]

@clumsy_ninja said in Yet Another Voice Module (Sphinx + Alexa):

@whyjustin Is it possible to change the activation work in your alexa? I remember seeing it defined in json somewhere but does it require voice training or something?

     commands: {
        "mirror mirror": {
          action: 'alexa'
        }
      },

If you edit the above you can adjust the activation of Alexa. Haven’t spent much time with this project recently but IIRC you have to remove sphinx-model-generator/commands.dic and sphinx-model-generator/commands.lm when changing the commands.

[whyjustin]

@lb-rezende said in Yet Another Voice Module (Sphinx + Alexa):

electron js/electron.js: …/src/java.cpp:105: v8::Localv8::Value Java::ensureJvm(): Assertion `result->IsNull()’ failed.

If I were to hazard a guess the JDK isn’t installed on your machine although you previously said that you were able to verify Alexa was working. Wild guess would be to verify the steps in [0] were followed to downgrade the electron client although this may not be related.

[0] https://github.com/whyjustin/magic-mirror-voice#installation-notes

[lb-rezende]

@whyjustin

I had done that step when I installed. I checked again, and Alexa is working when I execute the last step of the installation process (the one that has to open three different terminals and then the Alexa opens).

As I said, I’m new with Linux, so probably I configured it with something missing or wrong. My config.js is this way:

            {
                    module: 'magic-mirror-voice',
                    header: 'Magic Mirror Voice',
                    position: 'top_right',
                    config: {
                            debug: true,
                            alexa: {
                                    productId: 'MagicMirrorEmmanuel',
                                    dsn: 'MagicMirrorEmmanuel'
                            },
                            ssl: {
                                    sslCaCert: './magic-mirror-voice/alexa-certificate-generator/certs/ca/ca.crt',
                                    sslKey: './magic-mirror-voice/alexa-certificate-generator/certs/server/node.key',
                                    sslCert: './magic-mirror-voice/alexa-certificate-generator/certs/server/node.crt',
                                    sslClientKeyStore: './magic-mirror-voice/alexa-certificate-generator/certs/client/client.pkcs12',
                                    sslClientKeyStorePassphrase: ''
                            },
                            companion: {
                                    port: 3000,
                                    serviceUrl: 'https://localhost:3000',
                                    redirectUrl: 'https://localhost:3000/authresponse',
                                    clientId: 'MY PRIVATE CLIENT ID',
                                    clientSecret: 'MY PRIVATE CLIENT SECRET'
                            },
                            client: {
                                    alpnVersion: '1.0.2',
                                    vlcPath: '/usr/lib/vlc',
                                    vlcPluginPath: '/usr/lib/vlc/plugins'
                            },
                            sphinx: {
                                    commands: {
                                            "mirror mirror": {
                                                    action: 'alexa'
                                                    }
                                            },
                                    dictionary: './commands.dic', // Optional
                                    model: './commands.lm' // Optional
                                    }
                            }
            },

I’m not sure about the alpnVersion, vlcPath and vlcPluginPath, because I do not know where and how to find it. The dsn line as well, where do I find it?
I already changed ports as discussed here before, but did not work.

Thanks!

[whyjustin]

@lb-rezende said in Yet Another Voice Module (Sphinx + Alexa):

I’m not sure about the alpnVersion,

Verify your java version by running java -version then you should be able to look up the ALPN here. Your version looks incorrect so maybe this is your issue.

vlcPath and vlcPluginPath,

Check the docs here, but it should boil down to running whereis vlc. The values you provided look correct for a default setup.

because I do not know where and how to find it. The dsn line as well, where do I find it?

I don’t think you need to worry about this. It’s part of the automated cert generation and the communication between the OAuth NodeJS server and the Alexa Java application. IIRC this can be any value.