• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. Popular
    Log in to post
    • All categories
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All Time
    • Day
    • Week
    • Month
    • P

      Dont get Alexa Working
      General Discussion • • painkillerde

      8
      0
      Votes
      8
      Posts
      375
      Views

      P

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

    • A

      Running on Multi-Homed Host
      Monocle Gateway • • autodrivel

      7
      0
      Votes
      7
      Posts
      1033
      Views

      Monocle

      @shdwlynx

      No you were first :-) . I just figured this question would continue to come up and deserved its own pinned topic page.

      Thanks, Robert

    • N

      Monocle Alexa Skill in Spain [COMPLETE]
      Feature Requests • • Nyutu

      7
      0
      Votes
      7
      Posts
      868
      Views

      Monocle

      @Nyutu

      That is odd. I would suggest contacting Amazon Alexa support. There is nothing on our side we can really do to troubleshoot multiple camera skills and why Alexa would have problems … as long as the device names are different across the multiple camera skills (which in your case they are “Front Door” (Ring) and “Nursery” (Monocle) ).

      The Monocle skill is a “smart home skill” and thus all of the voice commands are entirely managed by Amazon. So it’s not like we are getting the request and can’t figure out which camera to provide. We only receive request from Amazon with the targeted camera that Alexa has pre-determined.

      Thanks, Robert

    • M

      Monocle Pricing
      General Discussion • • michael

      7
      0
      Votes
      7
      Posts
      731
      Views

      C

      @Monocle I agree that if the fee is low and infrequent its not a big deal. I also get that by having a recurring fee it keeps the community engaged and keeps Monacle’s interest in responding to the community and improving the product.

    • A

      Dahua IPC-HDBW4421F-AS & Alexa ECHO Show 5
      Support • • aatommy

      7
      0
      Votes
      7
      Posts
      1836
      Views

      C

      @aatommy said in Dahua IPC-HDBW4421F-AS & Alexa ECHO Show 5:

      Thanks, I have already tried that, I also tried some other Dahua Cameras with the same results. My conclusion is something to do with the show5, I can connect all my cameras using the free Dahua supported IMOU App (only sends substream) which seems a better option than having to have a proxy server running, I liked the idea of having the cameras run internally on my network and that I might be able to choose the wide screen display option, but on reading the forum it suggests that Amazon are going to force additional security which means I would have to use the gateway.
      The way the Monocle works and the simplicity all make for easy setup but like others I have been frustrated with getting it working, I will try on Fire TV when it arrives, just to see if it was me all along.

      i have same problem with dahua camera

    • W

      Gateway does not work - what can I do?
      Support • • Walter

      7
      0
      Votes
      7
      Posts
      757
      Views

      Monocle

      @Walter

      OK, I was able to reproduce a similar error. Although it may have been because I did not have a monocle.token file in place when the service was installed.

      After making sure my monocle.token file did exist at /etc/monocle/monocle.token and making sure that file did contain valid token data (file was not empty), I was able to use the following commands to get the daemon updated on the system and working:

      First, I used the --uninstall flag to remove the daemon/systemd config

      sudo monocle-gateway --uninstall

      Next, I used the --install flag to reinstall the daemon/systemd config

      sudo monocle-gateway --install

      And finally, I was able to start and view the Monocle Gateway

      monocle-gateway --restart monocle-gateway --tail

      If you are still getting those “condition check” errors, use this command and post what it prints out:

      systemctl status monocle-gateway.service

      As for this specific error:

      ****************************************************************** * __ __ ___ _ _ ___ ___ _ ___ * * | \/ |/ _ \| \| |/ _ \ / __| | | __| * * | |\/| | (_) | .` | (_) | (__| |__| _| * * |_| |_|\___/|_|\_|\___/ \___|____|___| * * * ****************************************************************** pkg/prelude/bootstrap.js:1183 throw error; ^ Error: EISDIR: illegal operation on a directory, read at Object.fs.readSync (fs.js:634:3) at Object.fs.readSync (pkg/prelude/bootstrap.js:555:32) at tryReadSync (fs.js:474:20) at Object.fs.readFileSync (fs.js:515:19) at Object.fs.readFileSync (pkg/prelude/bootstrap.js:684:36) at Object.<anonymous> (/snapshot/monocle-gateway/lib/monocle/MonocleGateway.js:1:2954) at Module._compile (pkg/prelude/bootstrap.js:1259:22) at Object.Module._extensions..js (internal/modules/cjs/loader.js:711:10) at Module.load (internal/modules/cjs/loader.js:610:32) at tryModuleLoad (internal/modules/cjs/loader.js:549:12)

      I get this if the /etc/monocle/monocle.token path is a directory and not a file. It should be a file.

      You can list the path like this and make sure its a file.

      ls -la /etc/monocle/ total 16 drwxrwxr-x 3 root monocle 4096 Jul 26 16:37 . drwxr-xr-x 109 root root 4096 Jul 26 16:13 .. -rw-r--r-- 1 root root 285 Jul 26 16:14 monocle.token

      Using the file command the output should not be a “directory”.

      file /etc/monocle/monocle.token /etc/monocle/monocle.token: directory

      Using the file command the output should be a “ASCII text” file.

      file /etc/monocle/monocle.token /etc/monocle/monocle.token: ASCII text

      Thanks, Robert

    • A

      Raspbian Buster & RPi4 for Gateway? [ANSWERED]
      Monocle Gateway • • AMDPower

      7
      0
      Votes
      7
      Posts
      467
      Views

      F

      @mattman
      The file is monocle.token
      If you type into console “sudo vi etc/monocle/monocle.token” then paste the key from the website into that. Press shift+; and type in “wq” and press enter. That will create the file in that directory.

    • S

      Gateway / Fire Tablet Problem
      Support • • stardeo

      7
      0
      Votes
      7
      Posts
      315
      Views

      Monocle

      @stardeo ,

      OK, no problem at all. Just let me know if you want to pursue this again down the road.

      It looks like some sort of networking issue where the Alexa device is unable to connect to the Monocle Gateway. We would expect additional line of information in the log when Alexa attempts to connect and start the RTSP session.

      Thanks, Robert

    • H

      Dahua XVR5104HS
      Dahua • • Hector

      7
      0
      Votes
      7
      Posts
      538
      Views

      Monocle

      @Hector

      Glad to hear that worked!

    • A

      Support for Brazil [BLOCKED]
      Feature Requests • • alferreira

      7
      0
      Votes
      7
      Posts
      589
      Views

      P

      @Monocle Hello Robert! If you need help translating from English to pt-br, count me in. I can also contribute with technical help, if you need some code adjustment for Brazil.

    • M

      Monocle Alexa Skill in Brazil [BLOCKED]
      Feature Requests • • MagusAgnus

      7
      0
      Votes
      7
      Posts
      655
      Views

      Monocle

      @llozer

      Update posted here:
      https://forum.monoclecam.com/topic/301/support-for-brazil-blocked

    • ?

      What camera do you use? / Camera Recommendations
      General Discussion • • A Former User

      7
      0
      Votes
      7
      Posts
      564
      Views

      C

      It’s great that you’re exploring reliable CCTV options, especially with a focus on quality and independence from cloud services. While TrendNet has served you well, upgrading to a modern, robust camera can enhance your security setup. For seamless integration, consider consulting professionals in your area who can guide you toward trusted brands and models. Searching for locksmith near me might also connect you with security experts offering tailored solutions, ensuring you choose a dependable system free from the pitfalls of unreliable online reviews.

    • ?

      Hikvision DS-2CD2532F-IWS on Echo Show 5
      Support • • A Former User

      7
      0
      Votes
      7
      Posts
      366
      Views

      ?

      Many thanks for your prompt reply and for your further explanations.
      Even if we can not fix my issue, this is really great support.

      Have a nice weekend!

      Thanks again, Markus

    • D

      Alexa "Camera Not Responding"
      Support • • dmoney517

      7
      0
      Votes
      7
      Posts
      409
      Views

      D

      @Monocle
      Thank you for the reply. I have both the PC running the Gateway as well as the Show 5 on the same network.

      Note - I have Google Wifi - and confirmed both devices are on the same AP.

      I opened 443 and the device running the Gateway.

      Confirmed firewall is allowing the monocle apps (even temporarily turned if off just to test).

      I was able to ping the dns assignment and it responded with the proper IP for the device running the Gateway.

      Still unable to connect.

      Please let me kbow of there is anything I can check.

    • C

      Unifi G3 Flex - was working, now not. [SOLVED]
      Ubiquiti / UniFi • • cory_booth

      7
      0
      Votes
      7
      Posts
      886
      Views

      Monocle

      @cory_booth

      Thanks for the guide and here is the link for future readers:

      https://forum.monoclecam.com/topic/484/add-gateway-to-qnap
    • W

      Lag time
      Support • • Wayne K

      7
      0
      Votes
      7
      Posts
      329
      Views

      W

      I am hardwired ethernet thru poe switch to each camera
      I am using the following settings
      Digest
      H264
      None on audio
      1920*1080
      @noaudio, @proxy

      Thanks for the reply’s
      Wayne

    • M

      Camera Not Responding. with and without Gateway
      Support • • monocleAxis

      7
      0
      Votes
      7
      Posts
      220
      Views

      B

      Using basic auth is not a good solution for those of us who use Axis Camera Station. Digest appears to not be working with Monocle. Would be great if this could be fixed.

    • C

      Failed with result 'exit-code'.
      Monocle Gateway • • clgillespie

      7
      0
      Votes
      7
      Posts
      419
      Views

      C

      @clgillespie

      pi@raspberrypi:~ $ sudo monocle-gateway --tail ****************************************************************** * __ __ ___ _ _ ___ ___ _ ___ * * | \/ |/ _ \| \| |/ _ \ / __| | | __| * * | |\/| | (_) | .` | (_) | (__| |__| _| * * |_| |_|\___/|_|\_|\___/ \___|____|___| * * * ****************************************************************** <<TAIL>> LOG FOR THE [MONOCLE-GATEWAY] SERVICE -- Logs begin at Thu 2020-06-04 20:28:13 EDT. -- Jun 04 20:28:18 raspberrypi monocle-gateway[444]: ****************************************************************** Jun 04 20:28:18 raspberrypi monocle-gateway[444]: * __ __ ___ _ _ ___ ___ _ ___ * Jun 04 20:28:18 raspberrypi monocle-gateway[444]: * | \/ |/ _ \| \| |/ _ \ / __| | | __| * Jun 04 20:28:18 raspberrypi monocle-gateway[444]: * | |\/| | (_) | .` | (_) | (__| |__| _| * Jun 04 20:28:18 raspberrypi monocle-gateway[444]: * |_| |_|\___/|_|\_|\___/ \___|____|___| * Jun 04 20:28:18 raspberrypi monocle-gateway[444]: * * Jun 04 20:28:18 raspberrypi monocle-gateway[444]: ****************************************************************** Jun 04 20:28:19 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:28:19 raspberrypi monocle-gateway[444]: MONOCLE RUNTIME ENVIRONMENT Jun 04 20:28:19 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:28:19 raspberrypi monocle-gateway[444]: VERSION = 0.0.4 Jun 04 20:28:19 raspberrypi monocle-gateway[444]: OS/ARCH = linux/arm Jun 04 20:28:19 raspberrypi monocle-gateway[444]: PROCESS = monocle-gateway (PID=444) Jun 04 20:28:19 raspberrypi monocle-gateway[444]: TIMESTAMP = 2020-06-05T00:28:19.677Z Jun 04 20:28:19 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:28:19 raspberrypi monocle-gateway[444]: MONOCLE GATEWAY SERVICE (Version: 0.0.4) Jun 04 20:28:19 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [Monocle Starting] Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [Monocle Connecting] Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [Monocle Started] Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [RTSP Server Starting] Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [RTSP Server Listening] 0.0.0.0:8555 (RTSP) Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS) Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [RTSP Proxy Started] (PID=546) Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [RTSP Server Listening] 0.0.0.0:8554 (PROXY) Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [RTSP Server Started] Jun 04 20:28:19 raspberrypi monocle-gateway[444]: 2020-06-05T00:28:19.793Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443 Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [ '[Monocle Error]', Jun 04 20:28:19 raspberrypi monocle-gateway[444]: 'getaddrinfo EAI_AGAIN api.monoclecam.com:443' ] Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [Monocle Disconnected] Jun 04 20:28:19 raspberrypi monocle-gateway[444]: [Monocle Reconnecting] ... in 7 seconds (attempt #1) Jun 04 20:28:26 raspberrypi monocle-gateway[444]: [Monocle Connecting] Jun 04 20:28:26 raspberrypi monocle-gateway[444]: 2020-06-05T00:28:26.811Z [ERROR] [Monocle Error] getaddrinfo EAI_AGAIN api.monoclecam.com:443 Jun 04 20:28:26 raspberrypi monocle-gateway[444]: [ '[Monocle Error]', Jun 04 20:28:26 raspberrypi monocle-gateway[444]: 'getaddrinfo EAI_AGAIN api.monoclecam.com:443' ] Jun 04 20:28:26 raspberrypi monocle-gateway[444]: [Monocle Disconnected] Jun 04 20:28:26 raspberrypi monocle-gateway[444]: [Monocle Reconnecting] ... in 10 seconds (attempt #2) Jun 04 20:28:36 raspberrypi monocle-gateway[444]: [Monocle Connecting] Jun 04 20:28:37 raspberrypi monocle-gateway[444]: [Monocle Connected] Jun 04 20:28:37 raspberrypi monocle-gateway[444]: [RTSP Server Registered] Jun 04 20:28:37 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:28:37 raspberrypi monocle-gateway[444]: MONOCLE RTSP SERVICE - INITIALIZED Jun 04 20:28:37 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:28:37 raspberrypi monocle-gateway[444]: FQ DN = d3060404-c9cf-4890-84ac-3cbb65168330.mproxy.io Jun 04 20:28:37 raspberrypi monocle-gateway[444]: HOST = 192.168.1.107 Jun 04 20:28:37 raspberrypi monocle-gateway[444]: PORT = 443 Jun 04 20:28:37 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:39:21 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:39:21 raspberrypi monocle-gateway[444]: INITIALIZE RTSP STREAM: Front Yard Jun 04 20:39:21 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:39:21 raspberrypi monocle-gateway[444]: - NAME : Front Yard Jun 04 20:39:21 raspberrypi monocle-gateway[444]: - LABEL : PRIMARY Jun 04 20:39:21 raspberrypi monocle-gateway[444]: - URL : rtsp://192.168.1.108:544/cam/realmonitor?channel=1&subtype=1 Jun 04 20:39:21 raspberrypi monocle-gateway[444]: - UUID : STREAM:96fe6e79-e8dc-48da-9002-7f650bc32ad2 Jun 04 20:39:21 raspberrypi monocle-gateway[444]: - SESS : 5d70c14e-8c3f-4423-9e30-442ac6e40a2b Jun 04 20:39:21 raspberrypi monocle-gateway[444]: - MODIF : Mon Jun 01 2020 11:08:08 GMT-0400 (EDT) Jun 04 20:39:21 raspberrypi monocle-gateway[444]: - TAGS : @tunnel Jun 04 20:39:21 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:39:23 raspberrypi monocle-gateway[444]: 2020-06-05T00:39:23.284Z [INFO] [192.168.1.135:48170 <B1mrEGvhI>] RTSP CLIENT SOCKET CONNECTED Jun 04 20:39:23 raspberrypi monocle-gateway[444]: 2020-06-05T00:39:23.406Z [INFO] [192.168.1.135:48170 <B1mrEGvhI>] RTSP CLIENT ATTACHED TO STREAM: Front Yard (STREAM:96fe6e79-e8dc-48da-9002-7f650bc32ad2) Jun 04 20:39:23 raspberrypi monocle-gateway[444]: 2020-06-05T00:39:23.425Z [ERROR] [192.168.1.135:48170 <B1mrEGvhI>] [RTSP ENDPOINT SOCKET ERROR] [192.168.1.135:48170 <B1mrEGvhI>] Error: connect ECONNREFUSED 192.168.1.108:544 Jun 04 20:39:23 raspberrypi monocle-gateway[444]: [ '[192.168.1.135:48170 <B1mrEGvhI>]', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: '[RTSP ENDPOINT SOCKET ERROR]', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: '[192.168.1.135:48170 <B1mrEGvhI>]', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: { Error: connect ECONNREFUSED 192.168.1.108:544 Jun 04 20:39:23 raspberrypi monocle-gateway[444]: at Object._errnoException (util.js:1031:13) Jun 04 20:39:23 raspberrypi monocle-gateway[444]: at _exceptionWithHostPort (util.js:1052:20) Jun 04 20:39:23 raspberrypi monocle-gateway[444]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14) Jun 04 20:39:23 raspberrypi monocle-gateway[444]: errno: 'ECONNREFUSED', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: code: 'ECONNREFUSED', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: syscall: 'connect', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: address: '192.168.1.108', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: port: 544 } ] Jun 04 20:39:23 raspberrypi monocle-gateway[444]: 2020-06-05T00:39:23.432Z [ERROR] PROXY ENDPOINT ERROR; Error: connect ECONNREFUSED 192.168.1.108:544 Jun 04 20:39:23 raspberrypi monocle-gateway[444]: [ 'PROXY ENDPOINT ERROR;', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: { Error: connect ECONNREFUSED 192.168.1.108:544 Jun 04 20:39:23 raspberrypi monocle-gateway[444]: at Object._errnoException (util.js:1031:13) Jun 04 20:39:23 raspberrypi monocle-gateway[444]: at _exceptionWithHostPort (util.js:1052:20) Jun 04 20:39:23 raspberrypi monocle-gateway[444]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14) Jun 04 20:39:23 raspberrypi monocle-gateway[444]: errno: 'ECONNREFUSED', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: code: 'ECONNREFUSED', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: syscall: 'connect', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: address: '192.168.1.108', Jun 04 20:39:23 raspberrypi monocle-gateway[444]: port: 544 } ] Jun 04 20:39:23 raspberrypi monocle-gateway[444]: 2020-06-05T00:39:23.434Z [INFO] [192.168.1.135:48170 <B1mrEGvhI>] RTSP ENDPOINT SOCKET CLOSED [192.168.1.135:48170 <B1mrEGvhI>] Jun 04 20:39:45 raspberrypi monocle-gateway[444]: 2020-06-05T00:39:45.379Z [DEBUG] [192.168.1.135:48170 <B1mrEGvhI>] [CLIENT REQUEST] --> [TEARDOWN] rtsp://d3060404-c9cf-4890-84ac-3cbb65168330.mproxy.io:443/STREAM:96fe6e79-e8dc-48da-9002-7f650bc32ad2?session=5d70c14e-8c3f-4423-9e30-442ac6e40a2b Jun 04 20:39:45 raspberrypi monocle-gateway[444]: 2020-06-05T00:39:45.379Z [TRACE] [192.168.1.135:48170 <B1mrEGvhI>] [CLIENT REQUEST] --> [HEADERS] { Jun 04 20:39:45 raspberrypi monocle-gateway[444]: "session": "", Jun 04 20:39:45 raspberrypi monocle-gateway[444]: "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)", Jun 04 20:39:45 raspberrypi monocle-gateway[444]: "cseq": "2" Jun 04 20:39:45 raspberrypi monocle-gateway[444]: } Jun 04 20:39:45 raspberrypi monocle-gateway[444]: 2020-06-05T00:39:45.385Z [DEBUG] [192.168.1.135:48170 <B1mrEGvhI>] [ENDPOINT REQUEST] --> [TEARDOWN] rtsp://d3060404-c9cf-4890-84ac-3cbb65168330.mproxy.io:443/STREAM:96fe6e79-e8dc-48da-9002-7f650bc32ad2?session=5d70c14e-8c3f-4423-9e30-442ac6e40a2b Jun 04 20:39:45 raspberrypi monocle-gateway[444]: 2020-06-05T00:39:45.386Z [TRACE] [192.168.1.135:48170 <B1mrEGvhI>] [ENDPOINT REQUEST] --> [HEADERS] { Jun 04 20:39:45 raspberrypi monocle-gateway[444]: "session": "", Jun 04 20:39:45 raspberrypi monocle-gateway[444]: "user-agent": "Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)", Jun 04 20:39:45 raspberrypi monocle-gateway[444]: "cseq": "2" Jun 04 20:39:45 raspberrypi monocle-gateway[444]: } Jun 04 20:40:15 raspberrypi monocle-gateway[444]: 2020-06-05T00:40:15.378Z [WARN] [192.168.1.135:48170 <B1mrEGvhI>] RTSP CLIENT SOCKET TIMEOUT Jun 04 20:40:15 raspberrypi monocle-gateway[444]: 2020-06-05T00:40:15.394Z [INFO] [192.168.1.135:48170 <B1mrEGvhI>] RTSP CLIENT SOCKET CLOSED Jun 04 20:40:15 raspberrypi monocle-gateway[444]: 2020-06-05T00:40:15.394Z [INFO] [192.168.1.135:48170 <B1mrEGvhI>] RTSP CLIENT DETACHED FROM STREAM: Front Yard (STREAM:96fe6e79-e8dc-48da-9002-7f650bc32ad2) pi@raspberrypi:~ $ sudo monocle-gateway --status ****************************************************************** * __ __ ___ _ _ ___ ___ _ ___ * * | \/ |/ _ \| \| |/ _ \ / __| | | __| * * | |\/| | (_) | .` | (_) | (__| |__| _| * * |_| |_|\___/|_|\_|\___/ \___|____|___| * * * ****************************************************************** GETTING <<STATUS>> FOR THE [MONOCLE-GATEWAY] SERVICE ● monocle-gateway.service - Monocle Gateway Service Loaded: loaded (/etc/systemd/system/monocle-gateway.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-06-04 20:28:17 EDT; 5min ago Main PID: 444 (monocle-gateway) Tasks: 10 (limit: 4915) Memory: 50.0M CGroup: /system.slice/monocle-gateway.service ├─444 /usr/local/bin/monocle-gateway └─546 /usr/local/bin/monocle-proxy -p 8554 Jun 04 20:28:36 raspberrypi monocle-gateway[444]: [Monocle Connecting] Jun 04 20:28:37 raspberrypi monocle-gateway[444]: [Monocle Connected] Jun 04 20:28:37 raspberrypi monocle-gateway[444]: [RTSP Server Registered] Jun 04 20:28:37 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:28:37 raspberrypi monocle-gateway[444]: MONOCLE RTSP SERVICE - INITIALIZED Jun 04 20:28:37 raspberrypi monocle-gateway[444]: ------------------------------------------------- Jun 04 20:28:37 raspberrypi monocle-gateway[444]: FQDN = d3060404-c9cf-4890-84ac-3cbb65168330.mproxy.io Jun 04 20:28:37 raspberrypi monocle-gateway[444]: HOST = 192.168.1.107 Jun 04 20:28:37 raspberrypi monocle-gateway[444]: PORT = 443 Jun 04 20:28:37 raspberrypi monocle-gateway[444]: ------------------------------------------------- pi@raspberrypi:~ $ sudo monocle-gateway --status ****************************************************************** * __ __ ___ _ _ ___ ___ _ ___ * * | \/ |/ _ \| \| |/ _ \ / __| | | __| * * | |\/| | (_) | .` | (_) | (__| |__| _| * * |_| |_|\___/|_|\_|\___/ \___|____|___| * * * ****************************************************************** GETTING <<STATUS>> FOR THE [MONOCLE-GATEWAY] SERVICE ● monocle-gateway.service - Monocle Gateway Service Loaded: loaded (/etc/systemd/system/monocle-gateway.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-06-04 20:28:17 EDT; 5min ago Main PID: 444 (monocle-gateway) Tasks: 10 (limit: 4915) Memory: 50.0M CGroup: /system.slice/monocle-gateway.service ├─444 /usr/local/bin/monocle-gateway └─546 /usr/local/bin/monocle-proxy -p 8554 Jun 04 20:28:36 raspberrypi monocle-gateway[444]: [Monocle Connecting] Jun 04 20:28:37 raspberrypi monocle-gateway[444]: [Monocle Connected] Jun 04 20:28:37 raspberrypi monocle-gateway[444]: [RTSP Server Registered] Jun 04 20:28:37 raspberrypi monocle-gateway[444]: -------------------------------------------------
    • D

      Unable to view cameras on Echo Show 8
      Support • • djvc

      7
      1
      Votes
      7
      Posts
      227
      Views

      F

      @Monocle

      Thank you, the tag @fake-fmtp along with @proxy-tcp works a treat now. Takes around 15 seconds to load the stream but once it does it is fine. No failures either!
      I moved my DNS to PiHole and disabled the “DNS Proxy” option in my router settings. Added an exception for the Alexa device on both its WiFi IP’s and made them static… Happy days till something updates…

      Cheers

    • T

      Not able to connect to Reolink cameras using monocle gateway
      Reolink • • tcj2001

      7
      0
      Votes
      7
      Posts
      666
      Views

      G

      In my journey with the Reolink NVR/Cameras (model RLC-820A), I had no luck connecting with the “_main” view, I needed to use the following in order to get the cameras to work: rtsp://192.x.x.x:554/h264Preview_01_sub. Hope that helps someone.