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

@vmsman Thank you for replying. I went to your chat, but not sure what to do there. Are you affiliated with Monocle? Thanks again!

For anyone else who runs into this i never did resolve it, i just made a task to restart the service every half hour.

@mfoster978

Here’s is a log.txt I pasted the log into.

https://drive.google.com/file/d/1FO3geAw1FBGNntQnoj_adqiVaLk8zcav/view?usp=drivesdk

Please let me know what you think.

Thanks,
Mike

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

@arthur360

I notice two issues in the log file.

1.) It looks like there is another instance of Monocle Gateway running and is already using the ports 8555 and 443. This is probably because you have the Windows Service for Monocle Gateway running in the background. (see: https://monoclecam.com/monocle-gateway/install/windows#windows-service).
Try stopping the service before running the Monocle Gateway executable in your command shell.

2.) The second error : [ERROR] [Monocle Error] getaddrinfo ENOTFOUND api.monoclecam.com is suggesting that the computer can’t communicate to the Internet or at least is not able to resolve the address api.monoclecam.com via a DNS server.

Thanks, Robert