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

    Alexa camera not responding [PENDING]

    Support
    2
    3
    221
    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.
    • D
      dathomas85 last edited by Monocle

      Hi there I’m all setup almost apart from
      Now Alexa is saying that the camera is not responding. I’ve tried various tags on the cameras to no avail.

      If I go to the FQDN manually it takes me to the page I’d get if using my mobile inside my network for my cameras so I’m assuming that bits working fine just no picture yet my rtsp url work fine when in vlc.

      I’ve tried @tunnel, @proxy together @proxy alone and with @noaudio as well as @tunel with @noaudio all to no luck.

      I’m using reolink cameras RLC-410 and RLC-420 eland everything is on the same network.

      __ __ ___ _ _ ___ ___ _ ___ *
      | / |/ _ | | |/ _ \ / __| | | __| *
      | |/| | () | .` | () | (| || _| *
      || ||_/|_|_|_/ ___|_|| *
      MONOCLE RUNTIME ENVIRONMENT
      
      VERSION = 0.0.4
      
      OS/ARCH = linux/x64
      PROCESS = monocle-gateway (PID=1)
      TIMESTAMP = 2020-02-01T02:01:28.941Z
      
      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=14)
      [RTSP Server Listening] 0.0.0.0:8554 (PROXY)
      [RTSP Server Started]
      [Monocle Connected]
      [RTSP Server Registered]
      
      MONOCLE RTSP SERVICE - INITIALIZED
      
      FQDN = changedtohide.mproxy.io
      HOST = 192.168.1.100
      PORT = 443
      
      INITIALIZE RTSP STREAM: Driveway
      
      NAME : Driveway
      LABEL : PRIMARY
      URL : rtsp://192.168.1.100:554/h264Preview_02_sub
      UUID : STREAM:0eb90e68-dcf1-4e0b-b72b-6a91875dab16
      SESS : 067ced94-82d2-4671-9527-e058c08fce7c
      MODIF : Sat Feb 01 2020 01:59:36 GMT+0000 (UTC)
      TAGS : @tunnel
      INITIALIZE RTSP STREAM: Driveway
      
      NAME : Driveway
      LABEL : PRIMARY
      URL : rtsp://192.168.1.100:554/h264Preview_02_sub
      UUID : STREAM:0eb90e68-dcf1-4e0b-b72b-6a91875dab16
      SESS : 067ced94-82d2-4671-9527-e058c08fce7c
      MODIF : Sat Feb 01 2020 01:59:36 GMT+0000 (UTC)
      TAGS : @tunnel
      INITIALIZE RTSP STREAM: Driveway
      
      NAME : Driveway
      LABEL : PRIMARY
      URL : rtsp://192.168.1.100:554/h264Preview_02_sub
      UUID : STREAM:0eb90e68-dcf1-4e0b-b72b-6a91875dab16
      SESS : 2199f8b2-704a-4e7b-84b6-5f7bc08c04d1
      MODIF : Sat Feb 01 2020 01:59:36 GMT+0000 (UTC)
      TAGS : @tunnel
      INITIALIZE RTSP STREAM: Driveway
      
      NAME : Driveway
      LABEL : PRIMARY
      URL : rtsp://192.168.1.100:554/h264Preview_02_sub
      UUID : STREAM:0eb90e68-dcf1-4e0b-b72b-6a91875dab16
      SESS : 27db371b-b6ce-45fb-8a1b-329ad7111d9f
      MODIF : Sat Feb 01 2020 01:59:36 GMT+0000 (UTC)
      TAGS : @tunnel
      
      1 Reply Last reply Reply Quote 0
      • D
        dathomas85 last edited by

        Bump any one have any ideas? I can access the link in a browser etc just not showing on my Alexa.

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

          @dathomas85

          The gateway, if everything were working properly, would show additional lines a detail showing the Alexa devices connecting and then performing RTSP negotiations withe the IP cameras.
          This is almost always a network issue.

          • It could be a firewall blocking access to port 443 where the Monocle Gateway is running.
          • It could be that port 443 is already in use by some other service already running on the same system where the gateway is installed.
          • It could be (and often is) an issue of DNS rebinding (https://monoclecam.com/monocle-gateway/troubleshooting/dns-rebinding)
          • It could be (albeit a more rare situation) that the Alexa devices and Monocle Gateway are on different networks (Guest WiFi network or VLANS)

          For Reolink cameras I believe that just @tunnel is needed along with the manufacturer set to “Reolink” in the Monocle web portal.

          From the log, everything else looks to be working correctly. The link between your Alexa account and Monocle is working and your Monocle Gateway is authenticated and communicating successfully with the Monocle servers. We can clearly see the incoming camera stream requests, but we are missing the Alexa device connections that should immediately follow the “INITIALIZE RTSP STREAM” blocks.

          Thanks, Robert

          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.