@justdo71 This looks great, but (maybe unfortunately) I do not use Home Assistant. I have my AD210 doorbell displaying fine (with audio also) through Monocle whenever I ask Alexa to show me the 'Doorbell". However when the doorbell is pressed Alexa only announces that someone is at the doorbell, but the camera doesn’t display anymore.

Of course the camera should display with the native Amcrest App itself without the need for Monocle, but that stopped working a while back. No idea why. :upside_down_face:

A couple of other points worth a mention…

When forwarding an RTSP feed on your router choose the TCP protocol (not both TCP and UDP).

When changing the resolution of a camera you not only need to update the monocle configuration but you also need to delete and re-add the camera in Alexa.

@VBasys Thank you for this research and breakthrough! I have submitted similarly worded feedback to Amazon.

No ideas anyone?

Did something change recently? I added a Show 8 G2 and since doing so, all of my cameras don’t work from any of my alexa devices (they all used to work fine - amcrest cams). They’ve been fine for years, no gateway needed.

My problem is resolved. I no longer need help.

Earlier I had tried (several times) to re-start the registration process from scratch with the same email, but the site would not let me. Today it did.

I didn’t receive any contact from Monocle support, so I assume no one did anything. I think that what “fixed” it was waiting long enough after trying to create an account without verifying the email address. My guess is that after some period of time (# of days?) without verifying the email address, the (partial) account creation gets cancelled, which allows someone to start creating an account with that email address from scratch.

i checked Ports Monocle Gateway is Listen

so Port 443 was forwarded by Router

but Port 8555 was listen too for Gateway, after set Portforwarding

my Cams are now responsible again by ALEXA

@starburst22

There is something else running on your system that is already using port 443. Or you have two instances of Monocle Gateway attempting to run at the same time. If you installed the gateway on Windows, it may be running as a system service in the background?

Thanks, Robert

@monocle said in Can't seem to get the gateway to work! [SOLVED]:

@TheCyberShocker

where am i wrong? MONOCLE RUNTIME ENVIRONMENT

VERSION = 0.0.4
OS/ARCH = win32\x64
PROCESS = monocle-gateway (PID=2836)
TIMESTAMP = 2022-02-14T15:11:16.257Z

MONOCLE GATEWAY SERVICE (Version: 0.0.4)

[Monocle Starting]
[Monocle Connecting]
[Monocle Started]
[RTSP Server Starting]
[RTSP Server Listening] 0.0.0.0:8555 (RTSP)
[RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS)
[RTSP Proxy Started] (PID=9692)
[RTSP Server Listening] 0.0.0.0:8554 (PROXY)
[RTSP Server Started]
2022-02-14T15:11:16.304Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRINUSE 0.0.0.0:8555
[ ‘[PROXY SERVER ERROR]’,
{ Error: listen EADDRINUSE 0.0.0.0:8555
at Object._errnoException (util.js:1031:13)
at _exceptionWithHostPort (util.js:1052:20)
at Server.setupListenHandle [as _listen2] (net.js:1367:14)
at listenInCluster (net.js:1408:12)
at doListen (net.js:1523:7)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
at Function.Module.runMain (pkg/prelude/bootstrap.js:1299:13)
at startup (bootstrap_node.js:227:16)
at bootstrap_node.js:649:3
errno: ‘EADDRINUSE’,
code: ‘EADDRINUSE’,
syscall: ‘listen’,
address: ‘0.0.0.0’,
port: 8555 } ]
2022-02-14T15:11:16.320Z [ERROR] [RTSP Server Error] listen EADDRINUSE 0.0.0.0:8555
[ ‘[RTSP Server Error]’, ‘listen EADDRINUSE 0.0.0.0:8555’ ]
2022-02-14T15:11:16.320Z [ERROR] [PROXY SERVER ERROR] Error: listen EADDRINUSE 0.0.0.0:443
[ ‘[PROXY SERVER ERROR]’,
{ Error: listen EADDRINUSE 0.0.0.0:443
at Object._errnoException (util.js:1031:13)
at _exceptionWithHostPort (util.js:1052:20)
at Server.setupListenHandle [as _listen2] (net.js:1367:14)
at listenInCluster (net.js:1408:12)
at doListen (net.js:1523:7)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
at Function.Module.runMain (pkg/prelude/bootstrap.js:1299:13)
at startup (bootstrap_node.js:227:16)
at bootstrap_node.js:649:3
errno: ‘EADDRINUSE’,
code: ‘EADDRINUSE’,
syscall: ‘listen’,
address: ‘0.0.0.0’,
port: 443 } ]
2022-02-14T15:11:16.320Z [ERROR] [RTSP Server Error] listen EADDRINUSE 0.0.0.0:443
[ ‘[RTSP Server Error]’, ‘listen EADDRINUSE 0.0.0.0:443’ ]
[Monocle Connected]
[RTSP Server Registered]

MONOCLE RTSP SERVICE - INITIALIZED

FQDN = 422ec86d-ec56-4595-8946-55b56e59a220.mproxy.io
HOST = 192.168.56.1
PORT = 443

INITIALIZE RTSP STREAM: camera da rua NAME : camera da rua LABEL : PRIMARY URL : rtsp://192.168.0.153:554/cam/realmonitor?channel=1&subtype=0 UUID : STREAM:2dfbdabd-003d-48fc-8ca7-4e32e6052440 SESS : dd30da45-478b-4b46-af0d-098ab62f0cb7 MODIF : Mon Feb 14 2022 12:12:19 GMT-0300 (Hora oficial do Brasil) TAGS : @fakefmtp,@proxy RTSP STREAM MODIFIED: camera da rua
Any existing RTSP steams will be shut down
and a new stream instance will be registered.

2022-02-14T15:12:34.223Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [DEREGISTER] rtsp://192.168.0.153:554/cam/realmonitor?channel=1&subtype=0
2022-02-14T15:12:34.223Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] {
“cseq”: “1”,
“transport”: “reuse_connection=0;preferred_delivery_protocol=udp;proxy_url_suffix=STREAM:2dfbdabd-003d-48fc-8ca7-4e32e6052440”
}
2022-02-14T15:12:34.223Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2022-02-14T15:12:34.223Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“date”: “Mon, Feb 14 2022 15:12:34 GMT”
}
2022-02-14T15:12:34.223Z [INFO] [RTSP PROXY] REGISTERING STREAM [camera da rua/PRIMARY]; (STREAM:2dfbdabd-003d-48fc-8ca7-4e32e6052440)
2022-02-14T15:12:34.239Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [REGISTER] rtsp://192.168.0.153:554/cam/realmonitor?channel=1&subtype=0
2022-02-14T15:12:34.239Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] {
“cseq”: “1”,
“transport”: “reuse_connection=0;preferred_delivery_protocol=udp;proxy_url_suffix=STREAM:2dfbdabd-003d-48fc-8ca7-4e32e6052440;username=admin;password=r2411l0604”
}
2022-02-14T15:12:34.239Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2022-02-14T15:12:34.239Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“date”: “Mon, Feb 14 2022 15:12:34 GMT”
}
2022-02-14T15:13:16.294Z [INFO] [RTSP PROXY] STREAM [camera da rua/PRIMARY] WILL BE DE-REGISTERED IN 4 MINUTES
2022-02-14T15:14:16.329Z [INFO] [RTSP PROXY] STREAM [camera da rua/PRIMARY] WILL BE DE-REGISTERED IN 3 MINUTES

@krh1009 If your cameras are all inside your private Network the no port 443 does not need to be public facing. I do not expose port 443 to the Internet in my personal setup. Monocle Gateway does need to host its services on port 443 but this can be on an internal private network address. The only catch is that Monocle must sent a valid public DNS host name to your Alexa devices when you request a camera stream. When using Monocle Gateway with an internal private IP address we create a custom DNS host name that points to your private IP address. Some routers will not resolve public DNS records to internal private IP addresses by default. Search for DNS REBIND and your router model to see if/how you need to configure it to allow these DNS host names to resolve properly.

Thanks, Robert

@xdowner

Please try again. I made some fixes today that should address this issue. You will need to re-register an email address that was not fully activated.

Thanks, Robert