I’m having same issue with Gateway not working after a few days. Here is the log hopefully someone can assist. Fyi I’m only using one instance of gateway.

MONOCLE RTSP SERVICE - INITIALIZED FQDN = 20fa027d-d919-4768-b031-5403dba0a00d.mproxy.io
HOST = 192.168.1.72
PORT = 443

WARNING
GATEWAY INSTANCE PROMOTED!

Another gateway instance has detached from your user account!
This could cause problems, please make sure that only one instance of Monocle Gateway is running on your network and associated with your account.

THIS GATEWAY INSTANCE [192.168.1.72] IS NOW THE ACTIVE GATEWAY FOR THIS ACCOUNT.

2020-12-04T08:57:35.849Z [ERROR] [Monocle Error] read ECONNRESET
[ ‘[Monocle Error]’, ‘read ECONNRESET’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 8 seconds (attempt #1)
[Monocle Connecting]
[Monocle Connected]
[RTSP Server Registered]

MONOCLE RTSP SERVICE - INITIALIZED FQDN = 20fa027d-d919-4768-b031-5403dba0a00d.mproxy.io
HOST = 192.168.1.72
PORT = 443

2020-12-04T09:20:09.977Z [ERROR] [Monocle Error] Closing connection due to PING response timeout; last PING response received was at: [2020-12-4 01:14:29]
[ ‘[Monocle Error]’,
‘Closing connection due to PING response timeout; last PING response received was at: [2020-12-4 01:14:29]’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 5 seconds (attempt #1)
[Monocle Connecting]
2020-12-04T09:29:56.255Z [ERROR] [Monocle Error] read ECONNRESET
[ ‘[Monocle Error]’, ‘read ECONNRESET’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 13 seconds (attempt #2)
[Monocle Connecting]
2020-12-04T09:30:09.264Z [ERROR] [Monocle Error] getaddrinfo ENOTFOUND api.monoclecam.com api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo ENOTFOUND api.monoclecam.com api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 18 seconds (attempt #3)
[Monocle Connecting]
2020-12-04T09:30:27.266Z [ERROR] [Monocle Error] getaddrinfo ENOTFOUND api.monoclecam.com api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo ENOTFOUND api.monoclecam.com api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 23 seconds (attempt #4)
[Monocle Connecting]
2020-12-04T09:31:02.316Z [ERROR] [Monocle Error] getaddrinfo ENOTFOUND api.monoclecam.com api.monoclecam.com:443
[ ‘[Monocle Error]’,
‘getaddrinfo ENOTFOUND api.monoclecam.com api.monoclecam.com:443’ ]
[Monocle Disconnected]
[Monocle Reconnecting] … in 29 seconds (attempt #5)

Thanks all is good!

ah. I didn’t pay close enough attention- I see the firestick now - there has been recent dialogs about a nuance between the 5 and 10" vs the 8" having some problems with SSL cert and I have 1 of each so was looking for your feedback thats why my stupid question.
1 sec speeds - wow. I’ve a full 5 second display delay - but I blame that on the BlueIris server being underpowered on my end (and too many HD cams feeding!)
I recently installed a 10Gb switch at a prison to handle some traffic of the 300+ cameras - I’ve been considering getting one for the house and then a few 10Gb NIC for each of my machines (3 servers, 1 workstation). Not sure if that will have any impact on the delay tho. I guess I could throttle the streams and see if the speed improves. When I switched from Direct to cam using Monocle web proxy to BlueIris front ending my cameras I doubled the delay from 2.5 secs to 5. I had to do this because certain cams just won’t work due to various reasons - but the BI solution got all my cameras going :) I’m looking at your solution as a way to possibly improve that delayed response. thanks for all the input!

Thank you for the replies. Ever since I installed the camera, I have been using Blue Iris to rotate the image and never used the camera software. I was able to flip the image with the camera’s setting and all is good.

Thank you for the help

@czandor It might be possible to accomplish stopping the feed using 1-2 Alexa routines

@Rossbro2 :
I get the “not quite sure” response from time to time, and one of these usually gets it going again:

On the Monocle Gateway Dashboard web interface, edit and save the camera without making changes (this will usually correct the issue on its own). Restart the Monocle Gateway. At alexa.amazon.com, in the Smart Home–>Devices tab, remove the camera (or just “Remove All”), then hit Discover and wait for it to finish.

Check cam in Alexa after each step.

I have Amcrest, Wyze, and Wi cameras on the gateway, and this usually will fix the “I’m not sure what went wrong” Alexa error on each.

And the relevance of this is??

I came here looking for this exact solution and found it, i am not much of a computer guy at all, but found the instructions and managed to get it up and running very well, albeit after a week of torture, i managed to find all the solutions here in the forums, personally i thinks works well and i cannot find anything else near, to do what Monocle does.

I do have a Smartthings hub which seems to predominantly work via Github and have only ever had headaches trying to install and get stuff working with the open source stuff, it just seems to be a minefield, a confusing one especially for people like myself who just want a nice .exe to do all the work, to the point where my ST hub is just a coaster for my cup of tea now. I cannot even get my Sage doorbell to work though ST to Alexa and all i see recently on the forums is people complaining.

The majority want something that just works and Monocle seems to, without to much hassle.

@rafale said in Alternatives to Monocle?:

Not sure why you would need a raspberry pi. I have been using this service for months without a proxy/gateway. Is it not working for you as just a skill? I don’t have a reolink camera so I can’t comment so much on if it does require a pi, maybe the question was rather whether or not you should have invested in a less picky camera?

What are you using then if not the Monocle gateway, BI one or something.

Es liegt nicht an der Fritzbox!

Die DNS-Server beim Provider blocken interne IP. Mit anderen DNS-Servern oder mit DNSSec klappt es.

It is no Issue with the Fritzbox-Router!

The automatic assigned upstream DNS-Server block private IP at provider’s site. So the use of other DNS-Server or DNSSec solve this issue.

@majones said in Dont get Alexa Working:

sudo lsof -i -P -n | grep LISTEN

i have got a second docker using it als reverse proxy. All 443 and 80 communication is routed there. So i have to reroute monocle traffic to the monocle docker container … i’ll try and write back.

I’ve finally got my cameras to work through my 2nd generation echo show and also my Amazon Fire TV however I still cannot view through my echo show 5, it just keeps saying “camera is not responding”. I’m thinking its the echo show 5 that’s the issue?

For my FB Portal is the same, would like to have this option!