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

    Blue Iris RTSP

    Support
    8
    42
    4673
    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.
    • M
      majones @hockeyfreak last edited by

      @hockeyfreak
      Fantastic! My problems normally benefit from disengaging and then doing a “cold review” the next day. My Echo Shows suffer a 10s lag behind reality, which I suppose is related to the encoding at BI and then decoding at the Echo. It would be good to get rid of that, not least because the time gap after saying “Alexa, show xxxxx” and xxxxx showing can seem interminable. So, TBH, I use some Fire 7 and 8 tablets running full time with IP Camera Viewer.

      1 Reply Last reply Reply Quote 0
      • C
        chester40391 last edited by

        I am trying to get the BI RTSP to work with my Echo Show 8 devices. I have been using the Monocle gateway successfully. I am using my cameras direct RTSP feed due to the cameras being on a different VLAN and because Echo Show 5/8 require it due to the need for port 443.

        I would like to eliminate the need for the Monocle gateway #1 because my sh#$ internet IP changes VERY frequently which breaks the gateway until I restart it (Painfully too often). #2 I want to use my IP cameras as webcam and since they are on another network I need a proxy. In theory BI can serve both needs and I wont need 2 different solutions.

        I am able to make this work with my Gen1 Echo Show but not my Echo Show 8. I thought I could just change the BI port to 443 which works with VLC but not with Monocle. I tried with no tag and the tags listed in the support section @proxy, @proxy-tcp, @tunnel

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

          @chester40391 Repost with added clarity since I am not permitted to edit apparently

          I am trying to get the BI RTSP feed to work with my Echo Show 8 devices. I have been using the Monocle gateway. I have been using my cameras direct RTSP feed due to the cameras being on a different VLAN and because Echo Show 5/8 require it due to the need for port 443.

          I would like to eliminate the need for the Monocle gateway #1 because my sh#$ internet IP changes VERY frequently which breaks the gateway until I restart it (Painfully too often). #2 I want to use my IP cameras as webcam and since they are on another network I need a proxy. In theory BI can serve both needs and I wont need 2 different solutions.

          I am able to make this work with my Gen1 Echo Show but not my Echo Show 8. I thought I could just change the BI port to 443 which works with VLC from a different VLAN but not with Monocle. I tried with no tag and the tags listed in the support section @proxy, @proxy-tcp, @tunnel but none of them work. My understanding was that the Echo Show 5/8 just need to use port 443 but is there some other magic needed that is happening by using the gateway?

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

            @chester40391 Is there an extensive list of tags? Navigating the forums I see various tags which are not listed on the official page https://monoclecam.com/monocle-gateway/tagging

            1 Reply Last reply Reply Quote 0
            • A
              Andycots last edited by

              Hi all, newbie here

              I have been trying to get my cams to show on my Echo’s with hit and miss success, sometimes shows then starts buffering and stops, had 1 on and had to tell Alexa to go home because was on for ages, still all hit and miss though, mainly miss and no joy.

              I am using BI and i from what i understand you do not have to install the Monocle server if you are using the BI feeds and if you are using direct from camera feeds (not through BI) then you do need the server?

              Andy

              M 1 Reply Last reply Reply Quote 0
              • M
                majones @Andycots last edited by

                @Andycots
                I’m no expert, but whether or not the gateway is required seems to depend on the type of Echo Show you have, and the type of camera. So I run it. When setup, the gateway should be running all the time and I use TAGS to tell it how to handle each camera. In my case, for cameras streaming directly to an Echo I use @tunnel, and for streams originating from BI I use @proxy-tcp. Interminable waits for an Echo to show an image are often due to excessive resolution at the source.

                1 Reply Last reply Reply Quote 0
                • A
                  Andycots last edited by

                  Thanks for the response, i have installed the Monocle service, will it automatically start now when or if i have to restart windows.

                  Thanks

                  1 Reply Last reply Reply Quote 0
                  • A
                    Andycots last edited by

                    I am trying to install the gateway on to my BI pc and the service starts but i get errors, if i use my laptop like i first did it works fine, i there a reason why i will not work on the same pc as BI, i do have a token for each one.

                    Thanks

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      majones @Andycots last edited by

                      @Andycots
                      The gateway should work on the same PC as BI, provided the gateway has access to port 443. You can check what services are listening on what ports using the free Advanced Port Scanner and specifying the local IP address of your BI PC. That said, a number of services (eg logitech media server, monocle gateway) don’t work well for me on my BI PC, possibly due to prioritisation, so I run a raspberry pi on the network to host them and they work really well.

                      1 Reply Last reply Reply Quote 0
                      • A
                        Andycots last edited by

                        Ha, sorted now, when i installed the Visual c++ ,i put the (*64) package on, because i have a 64 bit machine, after some more intergoogleing i put the (*86) package on and i works a treat now.

                        Thanks for you help.

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

                        © 2018 shadeBlue, LLC.