ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway"
-
@thurmane0 There is currently an issue with authentication with the alexa skill associated with Monocle. My assumption is you would need to create a new token as you have moved to new hardware, but i am no expert. but, you wont be able to authenticate in the skill if you get that far.
I just didnt want you to fight the token issue and then get stuck and assume there is something wrong with your token…if you run into issue at all, assume it is on the authentication side (several open topics on the forum) and not spend many cycles on the token until the auth issue is solved by @Monocle.
Of course, just my two cents…
-
-
-
Who knows an alternative to monocle ?
-
@bouboun59 I hope Robert is OK.
-
@Graham2607 said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":
@bouboun59 I hope Robert is OK.
Robert have GoogleHome Now… Alexa left Robert :d
-
If the person developing this doesn’t want to host this anymore, I am willing to host this/get this on my dev account to get this going for everyone.
-
@ALL.
Sorry, about the delay in getting this issue resolved. I was away from my office all last week and unable to access the necessary details and resources to work on this problem.
PLEASE TRY AGAIN NOW. (You may need to restart your Monocle Gateway instances.)
The issue started when I replaced all the SSL certificates at the end of January. Even though we have a pre-paid and valid 5 year certificate, the SSL rules require that it gets replaced annually now. So after updating all the certificates and restarting all the services that allow Monocle to function, it all appeared to be working from my local testing. However somewhere in the changes … the Monocle/Alexa authentication service failed to re-connect to the Monocle backend database properly. Perhaps it was holding onto (cached) the previous SSL for its secure connection which then expired. I’ll have to dig a bit deeper to better understand why it continued to fail to connect over the course of several days, but I believe this was the underlying issue causing failed account re-linking, failure to refresh Alexa tokens and failure for Monocle Gateway to reconnect and throw 401 errors.
Please let me know if any of you have further issues getting Monocle working again.
Thanks, Robert
-
Robert have GoogleHome Now… Alexa left Robert :d
Not on GoogleHome :-)
Mostly on HomeAssistant now for everything except cameras :-)-Robert
-
That fixed it, thanks!
-
@bouboun59 said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":
Who knows an alternative to monocle ?
I’ve hear good things about Scrypted (https://www.scrypted.app/) but I have not personally tried it out.
I think they are using FFMPEG under the hood to to re-stream camera feed in a more compatible format. That is something I had considered and wanted to do for Monocle but re-streaming a bunch of camera feeds can be quite server intensive.-Robert
-
@thurmane0 said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":
Hello everyone! (This is my first post here, so please be gentle lol)
The same issue is happening on my server, and I’m happy I came across this post when doing a google search. I recently upgraded my home server that I had for years to a pretty new snazzy model. I tried running the application and have the same missing token error.
I have kinda a related side question - since I moved the monocle folder to a new hardware setup, is there anything further I have to do to normally get it working? (I’ve read somewhere about generating a new token, but I’m honestly a bit inexperienced with this software - I got it working a couple of years ago and it’s been pretty steady.
There was a server side issue , but it should be resolved now. When moving Monocle Gateway to a new host/server, yes its a good idea to generate a brand new token for it. It’s not absolutely necessary but due to DNS caching it could take serveral hours to get the chain of DNS records fully updated. Generating a new token effectively also creates new DNS record for your Monocle Gateway instance and thus side-steps the caching issues.
Thanks, Robert
-
@Ryan-Breen said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":
That fixed it, thanks!
Thanks for the confirmation!
-Robert -
@bouboun59 said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":
Not dead ;-).
But it’s still a side-project and freely provided and hosted :-). So support is not always immediate and sadly in this case a bit more delayed than usual. I’m usually able to address any server-side related outage in a more timely manner. But I dropped the ball this time around.
Thanks, Robert
-
@Graham2607 said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":
@bouboun59 I hope Robert is OK.
All is well, I was just away for a week and was not monitoring the system or this forum.
Thanks, Robert
-
Now it worked.
Notes, I did this:
1 - To install the skill, it is not located in Alexa, you need to enter the link and add it, it will say that it was not installed but it was.
https://www.amazon.com/Monocle-RTSP-RTP-IP-Cameras/dp/B079P7DZ4D
2 - Generate a new token and run monocle cam.
Thanks
-
@Monocle said in ALEXA ECHO SHOW 5 - TOKEN ERROR - Assistance Needed: Troubleshooting "monocle-gateway":
But it’s still a side-project and freely provided and hosted :-). So support is not always immediate and sadly in this case a bit more delayed than usual. I’m usually able to address any server-side related outage in a more timely manner. But I dropped the ball this time around.
Thanks, RobertThanks a lots @Robert it was a joke ;)
Your work it’s very good, and i know, that isn’t easy to manager a free project.
Monocle it’s very cool project, and I will make a donationgreat
good job
a long life for you and monocle ;)
