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

    A little help with a couple of cameras? [SOLVED]

    Support
    2
    9
    415
    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.
    • L
      Legsmaniac last edited by Monocle

      Pretty please?
      I have set up Monocle with Gateway and it’s working great with several of my Foscam cameras with both my Echo Show 5 and Echo Spot. However, I have two cameras I’m struggling with.

      One is a Sricam SP009A and despite following several suggestions I’ve found on this forum, it’s no go. I’ve tried all sorts of ways. Tried with and without port number, tried tunnel and proxy, also tried noaudio, etc. Has anyone here got a Sricam SP009 and successfully set it up?

      And lastly, I am struggling also with a Foscam C1. As above. I’ve litterally spent hours on and off trying various settings.

      Any help would be most appreciated.

      Monocle 1 Reply Last reply Reply Quote 0
      • Monocle
        Monocle @Legsmaniac last edited by

        @Legsmaniac

        I have had a similar Sricam model working in the past, but I have not tested the SP009A.
        If I really correctly, this camera needed to use either @proxy or @proxy-tcp and may have also needed @noaudio as well.

        Feel free to post a snippet from the monocle gateway log while you are requesting this camera and we can take a look and see if there is anything obvious.

        Thanks, Robert

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

        1 Reply Last reply Reply Quote 0
        • L
          Legsmaniac last edited by

          Yes, I have tried those you say should work, amongst others.

          OK, with the setup @proxy and @noaudio, 720P res, H264 and Audio Codec NONE, this is what Gateway responds with…

          2019-11-29T16:51:50.801Z [INFO]  [RTSP PROXY] REGISTERING STREAM [Door Camera/PRIMARY]; (STREAM:a62bb3b5-d534-4a68-9e0e-9198b0ec4285)
          2019-11-29T16:51:51.738Z [INFO]  [192.168.1.34:33056 <H1g33aRhS>] RTSP CLIENT SOCKET CONNECTED
          2019-11-29T16:51:51.863Z [INFO]  [192.168.1.34:33056 <H1g33aRhS>] RTSP CLIENT ATTACHED TO STREAM: Door Camera (STREAM:a62bb3b5-d534-4a68-9e0e-9198b0ec4285)
          2019-11-29T16:51:52.803Z [ERROR] Uncaught Exception connect ECONNREFUSED 127.0.0.1:8554
          [ 'Uncaught Exception', 'connect ECONNREFUSED 127.0.0.1:8554' ]
          2019-11-29T16:51:52.806Z [ERROR] Error: connect ECONNREFUSED 127.0.0.1:8554
          [ { Error: connect ECONNREFUSED 127.0.0.1:8554
              at Object._errnoException (util.js:1031:13)
              at _exceptionWithHostPort (util.js:1052:20)
              at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14)
              errno: 'ECONNREFUSED',
              code: 'ECONNREFUSED',
              syscall: 'connect',
              address: '127.0.0.1',
              port: 8554 } ]
          2019-11-29T16:51:53.869Z [ERROR] [192.168.1.34:33056 <H1g33aRhS>] [RTSP ENDPOINT SOCKET ERROR] [192.168.1.34:33056 <H1g33aRhS>] Error: connect ECONNREFUSED 127.0.0.1:8554
          [ '[192.168.1.34:33056 <H1g33aRhS>]',
            '[RTSP ENDPOINT SOCKET ERROR]',
            '[192.168.1.34:33056 <H1g33aRhS>]',
            { Error: connect ECONNREFUSED 127.0.0.1:8554
              at Object._errnoException (util.js:1031:13)
              at _exceptionWithHostPort (util.js:1052:20)
              at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14)
              errno: 'ECONNREFUSED',
              code: 'ECONNREFUSED',
              syscall: 'connect',
              address: '127.0.0.1',
              port: 8554 } ]
          2019-11-29T16:51:53.872Z [ERROR] PROXY ENDPOINT ERROR; Error: connect ECONNREFUSED 127.0.0.1:8554
          [ 'PROXY ENDPOINT ERROR;',
            { Error: connect ECONNREFUSED 127.0.0.1:8554
              at Object._errnoException (util.js:1031:13)
              at _exceptionWithHostPort (util.js:1052:20)
              at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1195:14)
              errno: 'ECONNREFUSED',
              code: 'ECONNREFUSED',
              syscall: 'connect',
              address: '127.0.0.1',
              port: 8554 } ]
          2019-11-29T16:51:53.874Z [INFO]  [192.168.1.34:33056 <H1g33aRhS>] RTSP ENDPOINT SOCKET CLOSED [192.168.1.34:33056 <H1g33aRhS>]
          

          Thanks.

          Monocle 1 Reply Last reply Reply Quote 0
          • Monocle
            Monocle @Legsmaniac last edited by

            @Legsmaniac said in A little help with a couple of cameras?:

            ECONNREFUSED 127.0.0.1:8554

            OK, I think this :

            ECONNREFUSED 127.0.0.1:8554
            

            is a problem.

            Are you running this gateway on windows? If so, please simply restart the gateway and share the log from the startup messages. Looking to see if the “monocle-proxy” process is failing for some reason.

            Thanks, Robert

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

            1 Reply Last reply Reply Quote 0
            • L
              Legsmaniac last edited by

              Would it really be failing if all the other cameras work? I mean, for example, even after trying to call for the Door Camera (Sricam) which fails (as above), I can call for any of the Foscam cameras successfully.

              And yes, it’s running on Windows 10.

              Monocle 2 Replies Last reply Reply Quote 0
              • Monocle
                Monocle @Legsmaniac last edited by

                @Legsmaniac

                If using a camera with @tunnel it may still be working but if using @proxy I would expect it to fail based on the error I am seeing.

                Make sure to install this dependency and restart the gateway service …

                1.) Download and install the Microsoft Visual C++ 2010 Runtime Dependencies.

                Download the latest Microsoft Visual C++ 2010 SP1 Redistribution Package directly from Microsoft for Windows here. This package installed the underlying dependencies for Monocle Gateway.

                Download Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) from Official Microsoft Download Center

                After download, please install this package from the installer file.

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

                1 Reply Last reply Reply Quote 0
                • Monocle
                  Monocle @Legsmaniac last edited by

                  @Legsmaniac

                  It could also be a Windows firewall issue … if Windows firewall is enabled you might try temporarily disabling it to see if that helps.

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

                  1 Reply Last reply Reply Quote 0
                  • L
                    Legsmaniac last edited by

                    Thank you!! Thank you!! Thank you!! Thank you!! Thank you!! :slightly_smiling_face: :slightly_smiling_face: :slightly_smiling_face:

                    The C++ Redists fixed it. And the Foscam C1 now works with @proxy.

                    All sorted now, thank you SO much. You can mark this topic Solved.

                    Monocle 1 Reply Last reply Reply Quote 0
                    • Monocle
                      Monocle @Legsmaniac last edited by

                      @Legsmaniac

                      Glad to hear it and you are most welcome!

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

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

                      © 2018 shadeBlue, LLC.