@bhepler Are you running it from your pi or do you have the echo/dot?
If you are using the pi then yes you can customize the wake word which will trigger it into listening mode.

I’ve had the last version running since last Thursday. It’s really great now that it’s headless. I’m using snowboy and changed my wakeword to “Hey Jarvis” , I’ve used it every day since I installed it to trigger my hue lights via ifttt. Now to find a way to display the alexa cards on mm2 and that would be perfect.
Edit:
Didn’t read the article. Thought this was about the recent changes were we no longer have to click the button to activate it on the pi anymore. Anyways, I can’t really code yet and really want to do something with this as amazon have a lot of documentation online. My problem is work and personal stuff is getting on the way.

New update is sick. Really like the turn display on/off feature.

Hey guys,
I would like to do build a similar module.
I have looked at the build your own module guide and I am still lost. Can someone point me in the right direction?

I updated to the latest version they posted. It seems to be working well so far. I’m using the KITT.AI wake work engine but didn’t really have time to play with it yet. From what I understood, the sensory engine expires in 120 days(they might extend it) and will need to be reset up but the KITT.Al one should be fine. Time will tell.

This is awesome. No more commenting modules out when I do not need them. This is way more convenient.

Pixel latest raspbian update
Did anyone update to pixel?
Wanted to know if there were any issues before I dive in?
I would update myself but will not have the time to fix it if things go wrong. I’ll give it a try next weekend.

Congratulations. Well deserved.

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

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.

I’ll give this a try when I get some free time this weekend.

That’s pretty cool.
I have amazon alexa running alongside the MM2 on my pi too. Mine is just a simple work around and I have to click(I use a button) start listening each time I want to interact with it.

So it its always listening in your version?

Something must have happened. I didn’t change the code. I’ll check it when I get home.

@RedNax
I’m using degrees C.
I forgot to mention the it’s just the current temperature that’s showing temps in the hundreds. The temperature forecast is still working fine.

I have the same problem. Temperature is in the hundreds. I didn’t play around with the code.

Thank you.
I already had my garmin username in the config file but my garmin privacy settings were not public. It’s working now that I changed my garmin privacy to public.

@scarri
Hey, thanks for the module.
I got the garmin training calendar to work but cannot get the activities history to work. Is the activities module config smilar to the training calendar one?
What should I put as "userAccessToken and appAccessToken:?