• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    "Hmmm, the camera isn't responding"

    Support
    5
    11
    346
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jg00d3 last edited by

      I have been running monocle gateway with my Unifi udm pro nvr setup for a year or so and everything has worked great until approx. 2 weeks ago. It was working before I went on vacation and now that I am back it is not working. I get the “Hmmm, the camera isn’t responding”. I can use VLC to open the media streams. I’ve restarted the Echo show 8 and the monocle gateway running on raspberry pi and still have the same issue.

      when I view the gateway tail log I can see alexa requesting the camera info, here is the log:

      Jul 15 01:12:38 monocle monocle-gateway[471]: -------------------------------------------------
      Jul 15 01:12:38 monocle monocle-gateway[471]: INITIALIZE RTSP STREAM: Entrance
      Jul 15 01:12:38 monocle monocle-gateway[471]: -------------------------------------------------
      Jul 15 01:12:38 monocle monocle-gateway[471]: - NAME : Entrance
      Jul 15 01:12:38 monocle monocle-gateway[471]: - LABEL : PRIMARY
      Jul 15 01:12:38 monocle monocle-gateway[471]: - URL : rtsp://192.168.1.1:7447/mzGfdJFNLM7UsZKR
      Jul 15 01:12:38 monocle monocle-gateway[471]: - UUID : STREAM:9d22275a-cbc0-4d55-b4c9-c7f9f9e2865a
      Jul 15 01:12:38 monocle monocle-gateway[471]: - SESS : 3e8a88fa-d59c-478c-a712-c401104f9e0e
      Jul 15 01:12:38 monocle monocle-gateway[471]: - MODIF : Thu Mar 17 2022 13:14:19 GMT-0700 (PDT)
      Jul 15 01:12:38 monocle monocle-gateway[471]: - TAGS : @tunnel
      Jul 15 01:12:38 monocle monocle-gateway[471]: -------------------------------------------------

      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.752Z [INFO] [192.168.100.116:49958 <S1kYZo0i5>] RTSP CLIENT SOCKET CONNECTED
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.880Z [INFO] [192.168.100.116:49958 <S1kYZo0i5>] RTSP CLIENT ATTACHED TO STREAM: Entrance (STREAM:9d22275a-cbc0-4d55-b4c9-c7f9f9e2865a)
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.882Z [INFO] [192.168.100.116:49958 <S1kYZo0i5>] RTSP ENDPOINT SOCKET CONNECTED {192.168.1.1:7447}
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.883Z [DEBUG] [192.168.100.116:49958 <S1kYZo0i5>] [CLIENT REQUEST] --> [DESCRIBE] rtsp://3b0d9191-e6f9-4dd6-b840-966eaec69e53.mproxy.io:443/STREAM:9d22275a-cbc0-4d55-b4c9-c7f9f9e2865a?session=3e8a88fa-d59c-478c-a712-c401104f9e0e
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.884Z [TRACE] [192.168.100.116:49958 <S1kYZo0i5>] [CLIENT REQUEST] --> [HEADERS] {
      Jul 15 01:12:38 monocle monocle-gateway[471]: “accept”: “application/sdp”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “user-agent”: “stagefright/1.2 (Linux;Android 5.1.1)”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “cseq”: “1”
      Jul 15 01:12:38 monocle monocle-gateway[471]: }
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.886Z [DEBUG] [192.168.100.116:49958 <S1kYZo0i5>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://192.168.1.1:7447/mzGfdJFNLM7UsZKR
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.887Z [TRACE] [192.168.100.116:49958 <S1kYZo0i5>] [ENDPOINT REQUEST] --> [HEADERS] {
      Jul 15 01:12:38 monocle monocle-gateway[471]: “accept”: “application/sdp”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “user-agent”: “stagefright/1.2 (Linux;Android 5.1.1)”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “cseq”: “1”
      Jul 15 01:12:38 monocle monocle-gateway[471]: }
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.889Z [DEBUG] [192.168.100.116:49958 <S1kYZo0i5>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.889Z [TRACE] [192.168.100.116:49958 <S1kYZo0i5>] [ENDPOINT RESPONSE] <-- [HEADERS] {
      Jul 15 01:12:38 monocle monocle-gateway[471]: “cseq”: “1”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “cache-control”: “no-store”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “content-base”: “rtsp://192.168.1.1:7447/mzGfdJFNLM7UsZKR/”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “content-length”: “685”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “content-type”: “application/sdp”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “date”: “Fri, 15 Jul 2022 08:12:38 UTC”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “expires”: “Fri, 15 Jul 2022 08:12:38 UTC”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “pragma”: “no-cache”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “server”: “EvoStream Media Server (www.evostream.com)”
      Jul 15 01:12:38 monocle monocle-gateway[471]: }
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.896Z [TRACE] [192.168.100.116:49958 <S1kYZo0i5>] [ENDPOINT RESPONSE] <-- [BODY]
      Jul 15 01:12:38 monocle monocle-gateway[471]: v=0
      Jul 15 01:12:38 monocle monocle-gateway[471]: o=- 4833 0 IN IP4 192.168.1.1
      Jul 15 01:12:38 monocle monocle-gateway[471]: s=B4FBE4FFB008_1
      Jul 15 01:12:38 monocle monocle-gateway[471]: u=www.evostream.com
      Jul 15 01:12:38 monocle monocle-gateway[471]: [email protected]
      Jul 15 01:12:38 monocle monocle-gateway[471]: c=IN IP4 192.168.1.1
      Jul 15 01:12:38 monocle monocle-gateway[471]: t=0 0
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=recvonly
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=control:*
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=range:npt=now-
      Jul 15 01:12:38 monocle monocle-gateway[471]: m=audio 0 RTP/AVP 96
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=recvonly
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=rtpmap:96 mpeg4-generic/48000/1
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=control:trackID=0
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=f
      mtp:96 streamtype=5; profile-level-id=15; mode=AAC-hbr; config=1188; SizeLength=13; IndexLength=3; IndexDeltaLength=3;
      Jul 15 01:12:38 monocle monocle-gateway[471]: m=audio 0 RTP/AVP 96
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=recvonly
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=rtpmap:96 opus/48000/2
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=control:trackID=1
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=fmtp:96
      Jul 15 01:12:38 monocle monocle-gateway[471]: m=video 0 RTP/AVP 97
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=recvonly
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=control:trackID=2
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=rtpmap:97 H264/90000
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=fmtp:97 profile-level-id=4d401f; packetization-mode=1; sprop-parameter-sets=Z01AH5pkAgAk/4C3AQEBQAAA+gAAOpgnaCIRqA==,aO48gA==
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.896Z [INFO] [192.168.100.116:49958 <S1kYZo0i5>] RTSP ENDPOINT AUTHENTICATION SUCCESSFUL: NONE
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.901Z [DEBUG] [192.168.100.116:49958 <S1kYZo0i5>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.901Z [TRACE] [192.168.100.116:49958 <S1kYZo0i5>] [CLIENT RESPONSE] <-- [HEADERS] {
      Jul 15 01:12:38 monocle monocle-gateway[471]: “cseq”: “1”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “cache-control”: “no-store”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “content-base”: “rtsp://192.168.1.1:7447/mzGfdJFNLM7UsZKR/”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “content-length”: “660”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “content-type”: “application/sdp”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “date”: “Fri, 15 Jul 2022 08:12:38 UTC”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “expires”: “Fri, 15 Jul 2022 08:12:38 UTC”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “pragma”: “no-cache”,
      Jul 15 01:12:38 monocle monocle-gateway[471]: “server”: “EvoStream Media Server (www.evostream.com)”
      Jul 15 01:12:38 monocle monocle-gateway[471]: }
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.902Z [TRACE] [192.168.100.116:49958 <S1kYZo0i5>] [CLIENT RESPONSE] <-- [BODY]
      Jul 15 01:12:38 monocle monocle-gateway[471]: v=0
      Jul 15 01:12:38 monocle monocle-gateway[471]: o=- 4833 0 IN IP4 192.168.1.1
      Jul 15 01:12:38 monocle monocle-gateway[471]: s=B4FBE4FFB008_1
      Jul 15 01:12:38 monocle monocle-gateway[471]: u=www.evostream.com
      Jul 15 01:12:38 monocle monocle-gateway[471]: c=IN IP4 192.168.1.1
      Jul 15 01:12:38 monocle monocle-gateway[471]: t=0 0
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=control:*
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=recvonly
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=range:npt=now-
      Jul 15 01:12:38 monocle monocle-gateway[471]: m=audio 0 RTP/AVP 96
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=rtpmap:96 mpeg4-generic/48000/1
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=fmtp:96 streamtype=5; profile-level-id=15; mode=AAC-hbr; config=1188; SizeLength=13; IndexLength=3; IndexDeltaLength=3;
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=control:trackID=0
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=recvonly
      Jul 15 01:12:38 monocle monocle-gateway[471]: m=audio 0 RTP/AVP 96
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=rtpmap:96 opus/48000/2
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=control:trackID=1
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=recvonly
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=fmtp:96
      Jul 15 01:12:38 monocle monocle-gateway[471]: m=video 0 RTP/AVP 97
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=rtpmap:97 H264/90000
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=fmtp:97 profile-level-id=4d401f; packetization-mode=1; sprop-parameter-sets=Z01AH5pkAgAk/4C3AQEBQAAA+gAAOpgnaCIRqA==,aO48gA==
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=control:trackID=2
      Jul 15 01:12:38 monocle monocle-gateway[471]: a=recvonly
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022
      -07-15T08:12:38.910Z [INFO] [192.168.100.116:49958 <S1kYZo0i5>] RTSP CLIENT SOCKET CLOSED
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.911Z [INFO] [192.168.100.116:49958 <S1kYZo0i5>] RTSP CLIENT DETACHED FROM STREAM: Entrance (STREAM:9d22275a-cbc0-4d55-b4c9-c7f9f9e2865a)
      Jul 15 01:12:38 monocle monocle-gateway[471]: 2022-07-15T08:12:38.911Z [INFO] [192.168.100.116:49958 <S1kYZo0i5>] RTSP ENDPOINT SOCKET CLOSED [192.168.100.116:49958 <S1kYZo0i5>]

      Does the log info help to figure out where the issue is?

      M 1 Reply Last reply Reply Quote 0
      • M
        monome @jg00d3 last edited by

        @jg00d3 Same situation. My issue occurred after unifi software update, whereas they introduced a second audio codec into the stream.
        I always ran my setup with @noaudio flag, but that only gets rid of the fist audio stream, leaving the second, new, one intact. My current theory is that “rtpmap:96 opus/48000/2” audio option is throwing Alexa off, and causing her to abort. As soon as info about that option is sent to Alexa, the stream closes from her end.
        Seems the fastest / most reliable solution would be to update the monocle code to better handle filtering out multiple audio streams using @noaudio flag, or provide an option to filter out specific streams, such as @noopus. Ideally both.

        Gene

        J 1 Reply Last reply Reply Quote 0
        • J
          jg00d3 @monome last edited by

          @admin @Monocle Any way to block the second audio stream to get this to work? I am totally unable to use monocle now and I was using it on a daily basis prior to this 2nd audio stream update rolled out through Unifi Protect.

          Thank you!

          admin 1 Reply Last reply Reply Quote 1
          • C
            choerizo last edited by

            same issue here. following for any fixes

            1 Reply Last reply Reply Quote 0
            • N
              nicholasng last edited by

              I’m also having the same problem

              N 1 Reply Last reply Reply Quote 0
              • N
                nicholasng @nicholasng last edited by

                I think I’ve found a (fairly convoluted) solution.

                I managed to stumble across RTSP Simple Server which I set up on the same machine running monocle-gateway. I effectively set up RTSP Simple Server as a RTSP server in between Unifi Protect and Monocle Gateway which drops the second audio track from the Unifi Protect RTSP feed.

                There were two things to change in the standard rtsp-simple-server.yml file. One was the rtspAddress (to avoid a port conflict with Monocle Gateway):

                rtspAddress: :8654

                The second was to set up the Unifi Protect feed and a second feed which removed the problematic audio track:

                  cam:
    source: rtsp://[UDM Pro IP]:7447/[redacted]
    runOnReady: ffmpeg -i rtsp://localhost:$RTSP_PORT/$RTSP_PATH -map 0:0 -map 0:2 -f rtsp rtsp://localhost:$RTSP_PORT/camupdated

                I then set the Monocle RTSP path as rtsp://[local address of the computer running rtsp-simple-server]:8654/camupdated, and set the @proxy tag.

                It’s a little slow, but seems to work well.

                M 1 Reply Last reply Reply Quote 1
                • M
                  monome @nicholasng last edited by

                  @nicholasng nice, though running ffmpeg would introduce an added overhead / delay. How does your setup handle unifi reboot? Would the stream simply need to be restarted, or the whole RTSP SimSrv?

                  Thanks to @bally12345, I’ve discovered Scrypted, which is another workaround which I’m currently using. Delay seems minimal and as an added benefit I can view the stream on the nest hub in my office, as well as Alexa in the kitchen.

                  N C 2 Replies Last reply Reply Quote 0
                  • N
                    nicholasng @monome last edited by

                    @monome that’s a really good point on UniFi reboot - must admit I haven’t tried it but suspect I might need to then refresh the separate relay server. There is some delay but given my use case I hadn’t really noticed it.

                    I did have an initial try of Scrypted but seem to be coming up against some weird Alexa permissions issue (though given others have had success it might be something specific to my setup) - will give it another go!

                    1 Reply Last reply Reply Quote 0
                    • C
                      choerizo @monome last edited by

                      @monome thanks for the tip on Scrypted. Just installed and it’s working. Good bye Monocle.

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        monome @choerizo last edited by

                        @choerizo Be sure to use RTSP plugin, rather then unifi. RTSP provies more features (such as no audio), and seems more responsive.

                        1 Reply Last reply Reply Quote 1
                        • admin
                          admin @jg00d3 last edited by

                          @jg00d3 said in "Hmmm, the camera isn't responding":

                          @admin @Monocle Any way to block the second audio stream to get this to work? I am totally unable to use monocle now and I was using it on a daily basis prior to this 2nd audio stream update rolled out through Unifi Protect.

                          Thank you!

                          I just received my new Unifi cameras and will be setting them up and try to resolve this issue within the next week. Removing a second audio channel should be fairly simply … I think.

                          Please stay tuned …

                          Monocle: https://monoclecam.com
                          Getting Started | Troubleshooting Guide | FAQ | Contact Support

                          1 Reply Last reply Reply Quote 3
                          • First post
                            Last post
                          Privacy Policy  |  Terms & Conditions

                          © 2018 shadeBlue, LLC.