MMM-AlexaPi

romain

Well, I have the same issue as johnnyboy. I reset my pi once already. I have the same message from the AlexaPi service. Also launching the mirror in dev mode show me the following error related to MMM-Alexa : " Failed to load resource: the server responded with a status of 400 (Bad Request) https://api.amazon.com/auth/o2/token "
And the color indicator is yellow. I have a lot of trouble with setting my sound card to use a mic so I wouldn’t be surprise If I had a mic issue. But this is completely unrelated to the sound. the “token” is the thing we got when we connected to the raspberypi ip adress port 5050 right ? Is there a reason it would expire ? could it be the issue ?

lucallmon

@romain MMM-Alexa is not the same as MMM-AlexaPi. They are 2 separate modules that work totally different.

romain

@lucallmon Oh. My mistake then. So… AlexaPi is for MMM-alexa or MMM-alexapi ?
I am confused.

lucallmon

@romain AlexaPi is a separate program from MM. It can be found here: https://github.com/alexa-pi/AlexaPi. Once installed and working properly, you can access it through MM with the MMM-AlexaPi module, found here: https://github.com/dgonano/MMM-AlexaPi. This is the only easy [somewhat] to install version that is voice activated and works every time. The other ones, I have been unable to get to work because there is no step-by-step guide.

romain

@lucallmon Ok, I will try it tomorrow. I have already installed AlexaPi. I though it was for the MMM-alexa module though. Anyway, thanks for the input.

johnnyboy

This post is deleted!

romain

@johnnyboy Yeah I saw, I installed it in my home folder the first time before facepalming

johnnyboy

This post is deleted!

bminer1

I’m getting a permission denied when trying to save after making the changes in /etc/opt/AlexaPi/config.yaml
I feel like ive fallen in a rabbit whole that may be alittle over my abilities.

romain

@bminer1 That’s normal, there is multiple type of user in linux with different level of permission, it’s for safety (that you or a virus doesn’t destroy your operating system). When you are connected to your regular user (pi if you are using raspbian) you have only access in writing to your home folder. However, the pi user is also a “sudo” user, which mean that you can get higher permission in exchange of providing the right password (which is your regular password in raspbian).
To do that you write sudo your_command , for example sudo nano /etc/opt/AlexaPi/config.yaml . you’ll be ask to enter a password and then you can edit your file.
It’s like being administrator on windows, but with a password instead of a window that ask you if you want to run as administrator