I have a camera where the RTSP URI changes constantly. The URI is in the format of "rtsp:/x.x.x.x:554/live/1jfiegbrxl2aa_p0_PHKYHCXMNFDM". The last portion changes. The camera is fine/stable in the TinyCam app. ONVIF works fine when adding the camera in Blue Iris, but I don't see a way for Blue Iris to track the URI change.
Camera's RTSP URI Changes
- Thread starter djmadfx
- Start date
Camera make and model?
Did you ever scan a QR code or enter a UID/serial number from the cam using an app on a smartphone and create an account?
Did you ever scan a QR code or enter a UID/serial number from the cam using an app on a smartphone and create an account?
Yes, I scanned the QR on the camera to add it to the Vimtag app. I added some more info below.
Camera: VSMAHOME Mini G3 Pro -- App: Vimtag
I just did some digging and came across this -- Vimtag Mini G3-8310 -- I really hope it's not a backstream kind of situation.
Camera: VSMAHOME Mini G3 Pro -- App: Vimtag
I just did some digging and came across this -- Vimtag Mini G3-8310 -- I really hope it's not a backstream kind of situation.
As an Amazon Associate IPCamTalk earns from qualifying purchases.
Then it's likely using their cloud.
The second link you provided, the second post is from me where I got the TP-LINK Tapo C110 providing RTSP and 2 way audio with Blue Iris, re-stated below with links to how it works with BI..... rock-steady, no wierd URL changes:
If you really want to stream the video and audio from a smallwireless cam to Blue Iris, return it and get this one from amazon ==>> TP-Link Tapo 2K Indoor Security Camera for Baby Monitor, Dog Camera w/ Motion Detection, 2-Way Audio Siren, Night Vision, Cloud &SD Card Storage (Up to 256 GB), Works with Alexa & Google Home (C110)
and set it up like I did here ==>> Blue Iris Camera Compatibility
I had it streaming RTSP to Blue Iris 5 and also VLC. Not bad looking for a $25 wireless only, little cam with 2-way audio and selectable 720p/1080p/2K resolution.
EDITED 6/14/23 @ 0746 CT: Let me correct my previous statement that the Tapo C-110 has to stream to the cloud. That is not correct, I missed a step. Once you set the cam up with the Tapo app, go to that camera's "Settings" (the gear icon at upper right) => "Advanced Settings" => "Device Account". Create a username for the cam and a password and save it, then enter those EXACT credentials into Blue Iris for that cam.
I now have a $25 indoor, 1080p/2K wireless cam, with a mic (speaker AND mic works in the Tapo app for 2-way talk) , SD card storage and IR that streams RTSPwith audio to Blue Iris, no cloud or P2P involved. The 5VDC USB wall power supply is UL-listed as well. I can see this little guy in my garage's utility closet, staring at the status LEDs on my fiber modem or watching the status LEDs on my water heater...both non-critical roles but very convenient, IMO....for $25!
Last edited:
As an Amazon Associate IPCamTalk earns from qualifying purchases.
Ah, I didn't notice the poster until now! I was able to block internet for the device via my router and the video stream still worked locally. I confirmed by trying to connect through the cloud app using cell data. I'll do a little more digging before potentially returning.
My ultimate goal is to stick with this camera as it is a sub-$20 (after coupon) 2.5k/4mp IP65 indoor / outdoor camera. I created a python script that polls the camera for the RTSP URI. I just need to have it poll every X seconds and update the RTSP URI within Blue Iris if a change occurs. The URI should technically not change unless there is another device accessing it, but this will ensure that it remains updated.
After messing around with this for the day the following would be the best solution (aside from giving up and returning the cameras):
Within the camera properties utilize Watchdog to trigger "Find/inspect" when connection is lost for X seconds. It's not possible at this time. Waiting on a response from Blue Iris support to see if they have any suggestions. It's a bit of a dirty setup, but keeping everything in the Blue Iris software itself would be great.
Within the camera properties utilize Watchdog to trigger "Find/inspect" when connection is lost for X seconds. It's not possible at this time. Waiting on a response from Blue Iris support to see if they have any suggestions. It's a bit of a dirty setup, but keeping everything in the Blue Iris software itself would be great.
I finally found a solution and it seems to be working great! I installed Agent DVR -- iSpy - Open source camera security software -- and added the camera within there. I was then able to add the MJPEG for the camera URL within Blue Iris. Agent DVR has built in functionality to handle cameras that have a changing RTSP URI. I hope the instructions below help someone.
1. Download and install Agent DVR -- Download Video Surveillance Software
2. Access the interface via (replace x.x.x.x with the IP of where the software is running).
3. Click the Server Menu icon >> New Device >> Click on the Display Slot (or Skip) >> ONVIF >> All options should be Off on the Configure screen
4. Max Framerate: 30 (or your chosen value)
5. Source Type: ONVIF >> Click ...
-The camera's ONVIF URL should show within the Available list (mine is: ).
-Discover: Click on Get Video URLs and select the video URL under Live URL. Note the dimensions shown for the Live URL.
-Force Reload: On (this will handle the changing RTSP URI)
6. Click on OK >> and then OK again.
7. Go back into the Server Menu >> Settings >> Select Playback from the dropdown at the top >> For the Maximum MJPEG Size input the size (or higher) that was shown for the Live URL in the 5th step.
8. Within Blue Iris for the camera's URL you would input the following: -- Replace the x.x.x.x for the Agent DVR IP -- oids value is the camera number within Agent DVR -- size is the Live URL value or smaller depending upon your usage.
1. Download and install Agent DVR -- Download Video Surveillance Software
2. Access the interface via (replace x.x.x.x with the IP of where the software is running).
3. Click the Server Menu icon >> New Device >> Click on the Display Slot (or Skip) >> ONVIF >> All options should be Off on the Configure screen
4. Max Framerate: 30 (or your chosen value)
5. Source Type: ONVIF >> Click ...
-The camera's ONVIF URL should show within the Available list (mine is: ).
-Discover: Click on Get Video URLs and select the video URL under Live URL. Note the dimensions shown for the Live URL.
-Force Reload: On (this will handle the changing RTSP URI)
6. Click on OK >> and then OK again.
7. Go back into the Server Menu >> Settings >> Select Playback from the dropdown at the top >> For the Maximum MJPEG Size input the size (or higher) that was shown for the Live URL in the 5th step.
8. Within Blue Iris for the camera's URL you would input the following: -- Replace the x.x.x.x for the Agent DVR IP -- oids value is the camera number within Agent DVR -- size is the Live URL value or smaller depending upon your usage.
That is a high CPU usage for that machine. People are running 50 cams on a 4th gen at less CPU%.
Can you not pull in substreams?
Recent BI additions have shown running the GPU increases CPU% so turn off hardware acceleration.
Can you not pull in substreams?
Recent BI additions have shown running the GPU increases CPU% so turn off hardware acceleration.
As an Amazon Associate IPCamTalk earns from qualifying purchases.
Yes, the RTSP stream does not have any sort of password which does not matter for my use case. The internet access can be blocked for the cameras which eliminates any external threats. The only thing is that they would need internet access to modify a setting. I don't plan on changing any settings though. This is more of a temporary setup, I hope.
Mike A.
Known around here
- Joined
- May 6, 2017
- Messages
- 3,833
- Reaction score
- 6,393
Might be better to go with another better supported cam that doesn't require all of this? I can appreciate the challenge of making something work when you need/have to but you've already put in way too much effort than money saved toward something that's likely just going to end up giving you mediocre results in the end. Been there done that with other cheap cams. Not worth the trouble.
Yeah, it's one of those moments where you say to yourself, "I'll just try this and it should work..." and it turns into a whole mess where you regret even purchasing the item. Definitely not worth the trouble unless Blue Iris gets an update to refresh the ONVIF data if a camera disconnect is detected.
My thoughts as well.
I sometimes get an urge to accept a challenge and come out the victor, just makes me feel like I'm not losing my touch. That being said, during the process I try to keep sight of reality....is this something that needs to be out there and working NOW or can I afford to spend this much time on it right now? If it comes back "NOW" I get something out there working and resolving the immediate need THEN I come back and continue the challenge of fiddle-farting around with the gadget, trying to get it it work.
I can't believe it's been a month already! Just wanted to post a couple of (positive) updates.
I reached out to Ken and he added a couple of updates to Blue Iris (beta builds currently):
API:
/admin?camera=cam1&ippath=/whatever
You can use the API and update the video path via ippath.
JSON:
"cmd":"camconfig"
"ippath":"whatever"
I ended up using the JSON route as I integrated it along with the following script: Python code to trigger BI camera
That script allows you to not have to screw around with the web UI login.
---
I also made a request (Add support ONVIF source · Issue #380 · AlexxIT/go2rtc) for ONVIF functionality to be added to go2rtc -- GitHub - AlexxIT/go2rtc: Ultimate camera streaming application with support RTSP, RTMP, HTTP-FLV, WebRTC, MSE, HLS, MP4, MJPEG, HomeKit, FFmpeg, etc. -- and it has been added in the master release as of now.
I have some cameras using the JSON update. The python script gets triggered when the camera goes offline for 10 seconds. It then updates to ippath. I have a couple of cameras using go2rtc now. go2rtc is a cleaner setup for now. Testing both methods to see which works best.
I hope this helps other people out with this same issue.
I reached out to Ken and he added a couple of updates to Blue Iris (beta builds currently):
API:
/admin?camera=cam1&ippath=/whatever
You can use the API and update the video path via ippath.
JSON:
"cmd":"camconfig"
"ippath":"whatever"
I ended up using the JSON route as I integrated it along with the following script: Python code to trigger BI camera
That script allows you to not have to screw around with the web UI login.
---
I also made a request (Add support ONVIF source · Issue #380 · AlexxIT/go2rtc) for ONVIF functionality to be added to go2rtc -- GitHub - AlexxIT/go2rtc: Ultimate camera streaming application with support RTSP, RTMP, HTTP-FLV, WebRTC, MSE, HLS, MP4, MJPEG, HomeKit, FFmpeg, etc. -- and it has been added in the master release as of now.
I have some cameras using the JSON update. The python script gets triggered when the camera goes offline for 10 seconds. It then updates to ippath. I have a couple of cameras using go2rtc now. go2rtc is a cleaner setup for now. Testing both methods to see which works best.
I hope this helps other people out with this same issue.