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

    Problems with Alexa Show & Unifi Cameras

    Support
    2
    5
    167
    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.
    • B
      BY96 last edited by

      Hello,

      I am new to Unifi Protect and learned recently about Monocle and the ability to stream video on demand to Alexa Show devices. I set up the gateway on my PC today but cannot get it to work.

      Regarding the Unifi cameras, I know to change from RTSPS to RTSP and followed the instructions online to change the camera address (remove the “S”, change port, remove everything after the $). I think my problem is with the DNS rebinding.

      I get a "[ERROR] DNS RESOLVE ERROR…]

      I am using an Araknis 220 router and cannot find a way to include an exception to get the DSN to rebind to the gateway’s IP address. Can anyone give me some hints as to where in my router settings I can setup an exception? I am very naive when it comes to router settings and don’t know where to look.

      Thank you!

      B 1 Reply Last reply Reply Quote 0
      • B
        BY96 @BY96 last edited by

        @BY96

        I also tried to run the Monocle Gateway on a RPi. It came back with the same error. Here is the text:

        2024-04-23T01:41:01.697Z [ERROR] DNS RESOLVE ERROR: Error: queryA ENODATA 9212b465-e7df-4f74-a637-146b87c06420.mproxy.io
        ‘DNS RESOLVE ERROR: Error: queryA ENODATA 9212b465-e7df-4f74-a637-146b87c06420.mproxy.io’
        2024-04-23T01:41:01.699Z [ERROR] DNS RESOLVE ERROR: Error: queryA ENODATA 9212b465-e7df-4f74-a637-146b87c06420.mproxy.io
        ‘DNS RESOLVE ERROR: Error: queryA ENODATA 9212b465-e7df-4f74-a637-146b87c06420.mproxy.io’

        I really would appreciate some help. I really want to get my cameras viewable on an Echo Show. Thank you!!

        B 1 Reply Last reply Reply Quote 0
        • B
          BY96 @BY96 last edited by

          @BY96

          As another data point, I ran the “9212b465-e7df-4f74-a637-146b87c06420.mproxy.io” address through DNS Lookup and it pointed to the IP address for the RPi.

          V 1 Reply Last reply Reply Quote 0
          • V
            vmsman @BY96 last edited by

            @BY96 I would have to ask you many more questions to understand how you are receiving this error. Come by my chat and we can try to work it out.

            B 1 Reply Last reply Reply Quote 0
            • B
              BY96 @vmsman last edited by BY96

              @vmsman Thank you for replying. I went to your chat, but not sure what to do there. Are you affiliated with Monocle? Thanks again!

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

              © 2018 shadeBlue, LLC.