• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. Recent
    Log in to post
    • All categories
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • G

      Watchout for your DNS + proposals for easier investigation
      Support • • gege

      1
      0
      Votes
      1
      Posts
      411
      Views

      No one has replied

    • D

      Alexa Suddenly Stopped with Unifi
      Support • • Dave1137

      39
      1
      Votes
      39
      Posts
      15147
      Views

      D

      @Monocle I have and Thank YOU Robert. Grabbing image as I write this
      D

    • N

      UDM Pro with Unifi Protect - disconnecting
      Ubiquiti / UniFi • • nicholasng

      5
      0
      Votes
      5
      Posts
      1699
      Views

      D

      @Monocle Thank YOU Robert - we really appreciate it.

      D

    • V

      Reolink RLC-820A Not working on Monocole Gateway
      Monocle Gateway • • vmsman

      4
      0
      Votes
      4
      Posts
      1253
      Views

      Monocle

      @vmsman said in Reolink RLC-820A Not working on Monocole Gateway:

      Does it help you that these other three programs handled /h264Preview_01_main and worked with this camera?

      Not really … (unfortunately)
      The hardware is probably capable of playing the stream … it’s the viewer software that must support the H265 codec. The URL signature /h264Preview_01_mai really does not matter … it’s the data returned in the SDP (stream descriptor) that is telling the player to use the H.265 codec. Specifically this line:

      a=rtpmap:96 H265/90000

      I only noticed a single video stream (#96) and single audio stream (#97) in the log data you posted above. It’s telling the viewing software the stream supports H.265 for video and AAC audio.

      Unfortunately Amazon has not added support for any newer video codecs since H.264 for Alexa camera streaming. See https://developer.amazon.com/en-US/docs/alexa/device-apis/alexa-camerastreamcontroller.html#supported-video

      You could try using the @fakefmtp tag … but I seriously doubt it will work.

      The only thing I can think of suggesting is to have some other software (like FFMPEG/FFSERVER) ingest the H.265 stream and re-encode (transcode) it and output it via H.264. Clearly this will add latency and is a somewhat ugly solution. Other users have mentioned using SCRYPTED for their Unifi cameras. I have not tried it out yet, but I think it may be using FFMGEG under the hood to transcode the stream.

      Thanks, Robert

    • J

      HikVision DS-2CD2125FWD-IS doesn't work with Echo Show 5/8 for me
      Support • • jooonas

      5
      0
      Votes
      5
      Posts
      842
      Views

      C

      Would you need the @tunnel tag?

    • B

      Unraid and Unifi G4
      Support • • bally12345

      11
      0
      Votes
      11
      Posts
      2153
      Views

      B

      Will try take a look this week 👍

    • J

      Any Monocle Gateway updates with Unifi Protect 2.0....
      Support • • johnquilico

      3
      1
      Votes
      3
      Posts
      899
      Views

      Monocle

      Please see this thread for a test version available to address the Unifi camera issues:
      https://forum.monoclecam.com/topic/1242/unifi-camera-update-fix-available-for-testing-now/14?_=1659280156800

      Thanks, Robert

    • T

      Ubiquiti / rtsps stream support?
      Support • • Tim

      5
      0
      Votes
      5
      Posts
      1875
      Views

      Monocle

      @monome

      Thank you for the 1.x stream for backwards compatibility testing. So far its working great with the new changes to Monocle Gateway. (https://forum.monoclecam.com/topic/1242/unifi-camera-update-fix-available-for-testing-now/14?_=1659280156800)

      Thanks, Robert

    • C

      Combined streams
      Feature Requests • • cpcctv

      1
      0
      Votes
      1
      Posts
      474
      Views

      No one has replied

    • B

      Echo Show 15 compatibility
      General Discussion • • brianhb

      10
      0
      Votes
      10
      Posts
      2141
      Views

      M

      @brianhb You likely need a dedicated IP for the gateway instance.

      Here my build script which creates a dedicated macvlan for the container, thereby giving a dedicated IP to the monocle gateway.

      docker network ls --format "{{.Name}}" | grep -q ip_10_0_0_0 || docker network create -d macvlan --subnet=10.0.0.0/24 --gateway=10.0.0.1 -o parent=eth0 ip_10_0_0_0 docker pull monoclecam/monocle-gateway:latest docker stop monocle docker rm monocle docker run -d --name monocle --net ip_10_0_0_0 --ip=10.0.0.91 --log-opt max-size=10m --log-opt max-file=5 -e PUID=1002 -e PGID=100 -e UMASK=002 --restart always -v monocle:/etc/monocle monoclecam/monocle-gateway:latest docker logs monocle --since 1s -f

      Be sure to edit the subnet / name to reflect the IP subnet on your network (in my case ips are on 10.0.0.x subnet).
      DHCP on the macvlan doesn’t work, so be sure to assign a static IP to the container (in my case I’ve assigned 10.0.0.91, be sure to change it to yours.
      Remember that you’ll have to edit the monocle config file once it’s initially setup, so you’ll want to map /etc/monocle to somewhere accessible to you, otherwise lookup where monocle volume is created, and SSH into the docker host to edit the file there.

      Good luck, let me know if you have any issues / questions.