Blue Iris RTSP
-
Yes, it should be rtsp://…… Sorry for the typo.
The screenshots are really helpful. I’m wondering whether the cameras being on 192.168.20.x and BI on 192.168.50.x is a problem. Assuming not, let’s try to get VLC working.
Try streaming your camera directly to VLC, without BI playing a part, using rtsp://Roger:[camera-password]@192.168.20.104:554/live/main. It works for me in VLC when I use Media > Open Network Stream > [rtsp URL], and I’m not sure whether MLR is causing a problem.
If that works, try streaming the camera to VLC from BI, using rtsp://admin:[BI-user-password]@192.168.50.200:81/ESideCam&w=1280&h=720. Again, it works for me in VLC when I use Media > Open Network Stream > [rtsp URL]. -
@majones I tried both ways. The actual password of the camera is admin, I caught that after the screenshot and tried it that way and no go. I also logged into my Camera network wifi on my laptop and tried running all those from from BI and the raw camera feed. I can access the camera web interface from my Unfiltered network (the adult network that has no content and malware restrictions) and my Camera network, so I should be able to run the feed I would think. I’ve disabled Norton on the plex/BI server for all these tests so that’s not the issue. Below is the screenshot of my Camera.net rules, and I don’t think any of them are interfering. I’ve disabled all one at a time and no luck. I enabled the all access rule and nothing either. The only thing left is PiHole running as the DNS server. I don’t think that it but I’m far from an expert. I’m about to go nuts.
-
To recap, is your objective to view your cameras on an Echo Show? If so, then Monocle is the right tool, and let’s keep going. If you want to view your cameras on an Andrioid device, why not stick with TinyCam Pro that seems to be working for you?
-
Thanks for hanging in there. My objective is for my wife to be able to say “Alexa, show me Patio camera” or whatever on Firestick. When we get more Amazon devices, Yes, show them on Show or whatever. We’re in the process of switching over to Amazon from Google devices. When Google combined Music with Youtube music, we canceled it. Doing Bday stuff this weekend, but come Monday I’ll start trying to figure this out again! I’ll reconfigure the pfSense rules and play with them and see if that’s causing my problems.
-
Does this thread have any bearing on my problem? One guy checked the RTP/UDP option to get his working (with a firmware upgrade). I know it’s an old thread. Just fishing now…
-
-
@majones I think I’ve got it. I went down the rabbit hole again before the birthday stuff starts. I found this article tinkering with piHole to see if it was my problem. https://forum.monoclecam.com/topic/4/dns-rebinding. This may solve my monocle access at least, which is what I’m trying to do. Internally it does not solve it I wouldn’t think. I just need to research how to allow rebinding through pfSense (later tonight)
-
Fingers crossed for you. If I was you, first I’d get a direct RTSP feed from a camera to run on VLC, and then confirm that feed works with your Firestick. I’m not sure if it’s a hard and fast rule, but the Firestick may be limited to 1920x1080, so you may need to use a substream from your camera to be compliant as a direct feed. When you move on to BI, you can use your main stream into BI and extract a resized RTSP output stream by specifying h and w.
-
@majones Well, I am completely embarrassed now. It seems I got so absorbed in trying to figure out why my VLC wouldn’t display cameras and tinkering with PiHole, pfSense, and Norton’s, I completely forgot I didn’t install the damn Monocle service to point Monocle to the correct internal IP addresses, outlined HERE. I asked early in this thread how Monocle can find your internal camera IP addresses without some kind of client within your network. I read about it then, and then got so absorbed I never installed it.
I got that running on my BI/Plex server, and bam, Alexa found all my cameras and displays them. I still can’t get them to show me the stream in VLC, but the end goal is accomplished, so I’ll walk away for now and be happy. I so much appreciate your help and guidance. I’m working my way through all these cameras and smart home shit, and still got a long way to go.
The stream is around 30 seconds behind live, but I guess that’s acceptable enough. I doubt there’s any way to improve that.
-
-
@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. -
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
-
@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?
-
@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
-
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
-
@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. -
Thanks for the response, i have installed the Monocle service, will it automatically start now when or if i have to restart windows.
Thanks
-
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
-
@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. -
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.
