@Rockwell2020

I have been working on the service backend heavily today; so there were some extended outages today.
Please try it again now. You may have to re-link the Monocle Skill to your Alexa account.

Thanks, Robert

@Monocle thanks again Robert.

@Monocle Thank you. Looking good now!

@Monocle Hi Robert, unfortunately it seems to have as it was working for so long i hadn’t changed the settings, I have a Unifi G4 Doorbell, and because the high resolution was higher than 1080, i chose medium resolution at 960x720, when first trying it would not work, so i then had to set the video resolution to 1080 and it would work. I’m really not sure what else it may have been as i hadn’t changed a thing.

Did you have any issue getting unifi-os shell to run. I am not able to get this to run once ssh in.

Hello everyone,
I wanted to share the solution to my DNS resolution issue I encountered with the Monocle Gateway running on my network, which might be helpful for others experiencing similar problems.
Setup:
Cameras: UniFi G3
Controller: UniFi Cloud Key Gen2 Plus
Display Device: Echo Show 8
Router: FRITZ!Box 7590
Issue:
I was facing persistent DNS resolution errors with the Monocle Gateway service, which prevented my Echo Show from accessing the camera stream. The error message indicated a DNS resolve error for the Monocle DNS address.
Solution:
The issue was related to DNS-Rebinding protection on my FRITZ!Box 7590. Here is how I resolved it:
Access the FRITZ!Box Interface:
Open a web browser and go to http://fritz.box.
Log in with your FRITZ!Box credentials.
Configure DNS-Rebind Exceptions:
Navigate to “Home Network” > “Network” > “Network Settings”.
In the “DNS-Rebind-Schutz” section, add the problematic DNS hostname to the exceptions list.
Click “Apply” to save the changes.
Restart the FRITZ!Box:
Go to “System” > “Backup” > “Restart” and click “Restart”.
After making these changes, the DNS resolution issue was resolved, and the Monocle Gateway service started working correctly with my Echo Show.
I hope this helps anyone facing similar issues.

@c240amg

Working on this issue today and it should be up and working later today.
Thanks, Robert

@vmsman how can i find you there?

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

I have the Echo Hub too and had such a hard time getting my cameras online. I use local IPs for the cameras basic authentication and I run the gateway with API’s and as a service. Once I did that I got everything to run.

@berto1886 My fault, problem solved. I’d to add a second address to my raspberry (where monocle gateway is installed) where the 443 door is totally dedicated to this service and not in sharing with apache server

@bocadano I’ve got the same problem, infact after a lot of trials and attempts I’ve been arrived at the conclusion that the problem is the new generation of echo show

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

@chrisko

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