@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, Robert

Thanks 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 donation

great

good job
a long life for you and monocle ;)

Working great now. Thanks so much!

OK, everything should be working again now.

Thanks, Robert

Working again. Thanks.

@andi said in Unable to login via Alexa Skill:

@Monocle Hi Robert,

Thank you for your fast and in-depth support. I could solve the issue by switching to the Desktop version of the website. It seems the Alexa App uses Google Chrome on my Android device.

Using the Desktop Version the login worked fine.

With best regards

Andreas

Glad to hear its working now.

@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

@Deathstalker

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

@cincyitguy @toto was kind enough to point me at this post. Just to completely agree I cannot get this to work either. Like you certain the streams are there and there are no network issues but the same dreaded cannot connect to the camera…so no help but at least you know your not alone.

@Toto thanks great Toto, well your reply telling me that it’s a known unresolved problem. The fact it doesn’t work…not so great.

@dannyboy91

Hi. I think you need the @fixaudio tag as well

@Monocle is there any update on this? I know others cameras can do this like blink.

@griceluke I had the same issue with Monocle unfortunately. I passed the camera feeds through Frigate and used the restreamed feed from there to feed through to Alexa rather than direct from camera.

Otherwise, you could try using ONVIF Device Manager to absolutely confirm the url and if you have 2 streams or more available, start by trying to view the lowest res stream first on the Alexa device.

I did run into a camera that I could not get to work in Monovle no matter what I did. I ended up after WAY to many hours of trying to solve it, moving to Scrypted. That also works with Alexa. Good luck!

@ericwass It could be a new OS or something. The 5 gen 3 is definitely different than my 5 gen 1. I think I like the gen 1 better.

@calumartin So after a month of troubleshooting and being a bit of a numpty I’ve narrowed my issue down to Vodafone blocking dns rebinding on their routers with no way of turning it off whatsoever.
I recently moved to their Pro2 fibre 900 plan with all the bells and whistles including a VoIP landline, which if I wanted to, I could trade for using my own router but unfortunately, I still use my landline daily.
With what I’ve seen on the patchiness of the show 5 gen3’s working at all I’m gonna wait to see if they get supported better before I get a seperate line run for my landline.
Its a shame because I went for the pro package as I thought there might be more functionality.

@ferrellsl Thanks for the tip. I did have it at 1080p because I thought the Echo Show 5 (I accidentally put 4 in my original post) supported it. However, I did change the camera to 720p and it didn’t fix the issue. I’ve tried everything I can think of. So frustrating.

@brianjd My experience with Monocle has been that it always tends to work perfectly with the Echo Show 10 and not with the 5 or 8.