MMM-awesome-alexa

[sdetweil]

@uok825 yep, so server is running on port 8080…

sudo kill -9 1308

but pm2 stop
should have stopped that, does on my pi0

[uok825]

@sdetweil
What is that error?

[sdetweil]

@uok825 no idea… not my module… his code is impossible to understand, typescript compiled to js, then minified…

[uok825]

@sdetweil I killed -9 1308, what is next? changing port to 8080 again?

[sdetweil]

@uok825 yeh i guess… then npm start to verify runs, then ctrl-c and make sure it stops (ps -ef | grep node
the pm2 start and pm2 stop

[uok825]

@sdetweil sure, i doing. I need to fix this alexa problem

[nkchokshi]

Anyone can help me please how do i get an authentication number for Alexa? I have tried to add
https://192.168.0.10:1234
https://192.168.0.10:3000/authresponse
https://magic-mirror-avs.github.io/Alexa-Web-Helper/authresponse

none of these pages are giving me code after when i click agree, to consent screen. i just end up with

Amazon Error page with no number on address bar.

We’re sorry!
An error occurred when we tried to process your request. Rest assured, we’re already working on the problem and expect to resolve it shortly.

[sdetweil]

@nkchokshi which return url did I specify in Amazon, and u MUST use that one

u want one that will be on the local. machine. so, localhost:7777 might be good

[Ghost2000]

I have the same problem with the token can someone help me.

Will the module be updated again? or is there a new module?

[sdetweil]

@Ghost2000 hasn’t been updated in 17 months, 3 years before that. so, not likely to get update.

they are very picky about what they allow for auth callback urls. http://localhost:someportnumber >1000

they will pop up a screen to request logon and authorize this app to access your account, u click approve, and then the page appears with the error at the top using your auth URL and the code.

I know this works, cause I do it in another application