@mdame

The current release of Monocle Gateway is generically compiled for newer ARM architecture such as in the RPi3B/3B+. Please open a support ticket via the link below and reference this forum topic and we can provide you an “untested” version compiled specifically for the Raspberry Pi.

https://monoclecam.com/contact

Thanks, Robert

@TracyReznik1325 said in ANNKE N46PI NVR Setup Details:

v380

not sure what you’re referring to here?

@vmsman our the man. i can’t say for sure 100% but i think i have it going. for some reason it did not like the ports i was using so i just guessed and used ports around the area the nvr was set at and now i see both camera at home and away. hip hip hurray! your help was good. i did not use most of it but not to worry any ideas people offer prompts more thought and ideas. and that is what it did for me. thanks much for all the suggestions given they gave me ideas. if for some reason it stops i will visit this again and see if anyone has more ideas. again thanks much.

Hey there so I have still been struggling with this. I got delayed b/c of a project at my house. I have tried @hangup @proxy @proxy-tcp in all matter of combinations.

This is what I found, @hangup @noaudio @tunnel is the optimal configuration. However, after a few switches between cameras, none work. If I go onto the monocle dashboard and change a config, suddenly the cameras start working again for a period of time. That is really odd behavior.

@matt187

Thanks for pointing this out. The Echo Show 5 should work for most cameras when using the Monocle Gateway. Wansview cameras seem to be problematic however, they work on older Echo Show devices, but not the latest 5" and 8" models. Good to know that accessing their streams through the Synology NVR software/platform will allow them to work with Alexa devices. I’ll have to play with that setup here as well.

Thanks, Robert

@BigRic thanks for the reply. Thankfully the camera I want to view most of the time is an IP reolink and works great. It also has much better video then my analog Q-See cameras. I guess I will start replacing them with reolink cameras.

@cjtrevor

Glad to hear its working now. My guess is that there is something in the RTSP client that the IP camera does not like. Switching to @proxy uses a different RTSP client.

@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

@Habib

There is not a newer version available at this time, but one is in the works, but won’t likely be available until Q1 2020.

@SchmuFoo (Jan)

Yes, the Alexa devices will only connect via RTSP to port 443.
You can override the SSL hosted port used by Monocle Gateway by overriding the rtsp.ssl.port property in monocle.properties as in the example below where port 8443 is used instead.

#-------------------------------------- # RTSP SERVICE PROPERTIES #-------------------------------------- rtsp.ssl.port=8443

You can also use a proxy server, but not NGINX or APACHE. You will need a TCP proxy server as the cameras use RTPS and not HTTP. You may be able to use something like stunnel, HA Proxy or maybe traefik something that does full TCP proxying. In this case you may have to have a valid SSL certificate at the terminating proxy server using your own domain record.

If terminating your own SSL cert and providing your own DNS hostname, you would also need to update these properties:

#-------------------------------------- # RTSP SERVICE REGISTRATION OVERRIDES #-------------------------------------- #rtsp.register.fqdn= #rtsp.register.host=

Let me know if this is something you decide to pursue if you run into any trouble perhaps I can help.

Thanks, Robert

@jannnfe

Please see:

https://monoclecam.com/monocle-gateway/install/docker https://hub.docker.com/r/monoclecam/monocle-gateway https://github.com/MonocleCam/monocle-gateway-docker

You can move your existing gateway with the same monocke.token file into a docker container. If you keep the same monocle.token file, your DNS hostname will stay the same. When a new IP is registered, it will get updated in the public DNS registry and will get propagated across the Internet. This may take several minutes or up to an hour to propagate. You may have to reboot your Alexa devices to get the updated IP as Alexa seems to cache DNS entries for a long time.

You can also generate a new token file to speed the migration up, but then you would also need to update Fritz with a new DNS hostname.

Thanks, Robert

Based on priobe’s comments I thought I had an “ah-ha” moment - perhaps only 1 of my 6 cameras would work with Monocle when connected through the DVR as priobe mentioned. I was only testing with one camera.

So, I went through and added my 5 other cameras. Then I attempted to call them up through Alexa one by one, hoping that I would hit on the one camera that CAN be seen through the DVR using Monocle.

Alas, none of them work.

So next question. My home network is on the 10.10.10.XXX space. This includes the DVR. The IP cameras themselves are on a private network within the DVR and have the 192.168.254.XXX space. I know I can change the IP address of each camera within the DVR interface. Is it possible - WITHOUT BREAKING OTHER THINGS - to assign each camera to the 10.10.10.XXX network space behind my router / firewall to see if then I can address each camera individually within Monocle as opposed to the DVR??

Please advise.

@Deathstalker

Sorry, about the delay in getting this issue resolved. I was away from my office all last week and unable to access the necessary details and resources to work on this problem.

PLEASE TRY AGAIN NOW. (You may need to restart your Monocle Gateway instances.)

The issue started when I replaced all the SSL certificates at the end of January. Even though we have a pre-paid and valid 5 year certificate, the SSL rules require that it gets replaced annually now. So after updating all the certificates and restarting all the services that allow Monocle to function, it all appeared to be working from my local testing. However somewhere in the changes … the Monocle/Alexa authentication service failed to re-connect to the Monocle backend database properly. Perhaps it was holding onto (cached) the previous SSL for its secure connection which then expired. I’ll have to dig a bit deeper to better understand why it continued to fail to connect over the course of several days, but I believe this was the underlying issue causing failed account re-linking, failure to refresh Alexa tokens and failure for Monocle Gateway to reconnect and throw 401 errors.

Please let me know if any of you have further issues getting Monocle working again.

Thanks, Robert

@Monocle said in Koogeek/Smart Life Camera not working:

@fakefmtp

Monocle support is very bad, I have connection issue with Reolink camera, tried everything

@osensnolf

Glad to hear it’s working now. Thanks, Robert

@Monocle
Sweet! Thx!!

@pyranna

No, it’s fine in the same directory as the executable. We suggest the /etc/monocle folder because that’s a more common Linux config path. However if future versions support a web interface allowing the user to change the token, then a fixed path may be required then.

Thanks, Robert

I am sure any device camera so long as it can send a url would work.

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