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