It’s great that this forum offers an illustrative and explanatory space for sharing concerns, much like how a locksmith provides clear solutions for lock and key issues. When dealing with technical concerns such as your Arlo Solar Panel not charging your Arlo Go or Arlo Pro camera battery, it’s essential to first ensure the panel is receiving proper sunlight and all connections are secure. Just as a locksmith carefully checks every detail, reviewing Arlo guidelines or contacting support can lead to the right troubleshooting steps.

Never mind. It must have been a transient error, because the skill is accessible again now.

I’m still seeing the DNS resolve error, so thing’s still not right.

Try unlinking and relinking the Alexa skill in the Alexa app, ensuring your login credentials are correct and the skill is properly configured. stay in touch for more info!

@przem2k Scrypted is free for basic functions such as this. The paid version offers full NVR functionality, allowing full recording of video and generated events. The free version is able to replace the functionality that is lost by Monocle no longer working.

It’s great that you’re exploring reliable CCTV options, especially with a focus on quality and independence from cloud services. While TrendNet has served you well, upgrading to a modern, robust camera can enhance your security setup. For seamless integration, consider consulting professionals in your area who can guide you toward trusted brands and models. Searching for locksmith near me might also connect you with security experts offering tailored solutions, ensuring you choose a dependable system free from the pitfalls of unreliable online reviews.

@Monocle Robert, You are the man. Thank you so much. That worked.

@Monocle Thank you. Looking good now!

To me looks like that the initial connection Alexa -> Gateway and afterwards Gateway -> camera works, but hangs right after, not sure how to proceed

@bocadano I finally used Synology docker to get it to work.

@chrisko

I’ve had the same problem no matter what settings I used.

Pastebin - sanitized Gateway output

https://pastebin.com/5GUuM0RW

First run is the Overview “camera” which is the problem child

Second run is a working camera - Amcrest front door.

@edgbarr

The computer running Monocle Gateway does not need a public IP address on the Internet. It can certainly be a private IP address inside your network behind your router/NET. It does however require outbound Internet access to communicate with the monocle services. This computer also need to be accessible on your network from the Alexa devices. The Alexa devices will talk to the Monocle Gateway when requesting camera stream rather than talking to your IP cameras directly.

Another question, if I change the Monocle settings on the official website, do I need to generate a new token?

No, settings are communicated for each camera stream every time the camera stream is requested/triggered from Alexa. We do suggest generating a new token if your IP address changes on the computer running Monocle Gateway. It’s not required but it can take up to 24 hours for the new IP address to get propagated in the DNS record. Thus a new token speeds this process up by issuing a new DNS record fore your Monocle Gateway instance.

Thanks, Robert

@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 ;)

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