Cam Pan V3 RTSP vs Blue Iris

Just reveived the OTA firmware update to my PAN V3 with RTSP support 4.50.16.5654 and everything seems to work great except when trying to add the feed to Blue Iris. I can see the live feed with no issues in VLC but when I enter the info in Blue Iris I get the No Signal error. I don’t know where I’m going wrong. Please see image and offer any insight you might have. (ignore the HTTP:// in the screen capture. I corrected to RTSP:// and it’s the same thing.)

Have you read these topics?

Some users in those mention getting RTSP to work in Blue Iris, and one thing I see mentioned more than once is making sure that the camera is set to use RTSP and not RTSPS. Comparing the screenshot in this post…

…to yours, I see at least three differences, though I don’t use Blue Iris and don’t know what effect each of these might have:

  • You have Discovery/ONFIV port set for 554; the other screenshot shows 80.
  • You have Use RTSP/stream timecode selected; the other screenshot shows it deselected.
  • You have Decoder compatibility mode deselected; the other screenshot shows it selected.

I got in touch with Blue Iris support and they figured out how to get this working in Blue Iris. Copy the settings below & it should work like a charm! (Obviously use your own Wyze cameras IP address, RTSP user name & password.) Haven’t tested the sub stream yet but it should work under /stream1

Has anyone figured out how to get PTZ working via RTSP and Blue iris. RTSP streans video fine but can’t get the PTZ working

I can’t for the life of me get this to work. I put the settings exactly as you have here (tried rtsp too) and it won’t work. That being said, I can’t get it to work in VLC either. It works fine from the app, I can see it and ping it from the PC.

My initial thoughts:

  1. What’s the exact URL you’re using to attempt streaming to VLC? (Feel free to selectively obfuscate the username and password you set for the Cam.)
  2. Is it possible that you have a firewall on the PC that’s interfering? I’m asking because of my experience streaming Cam Pan v3 via RTSP to OBS.

Welcome to the Forum, @jasonrusso! :wave:

Good thought on the firewall, however I disabled it and it still didn’t work. I use ESET for the anti-virus. These are just the results this afternoon.

1 Like

Can you telnet to the cam’s IP on port 554 - does it give any sort of response?

I’m not sure what you mean by telnet. I can ping it with a positive response, If I try to access it via a web interface it fails.

Telnet is a command line program that lets you open a connection. Windows often doesn’t have it installed by default but you can add it via optional features.

Worth a try if you are willing

you’d use “telnet 192.168.1.131 554” and see if you got any sort of response (including a “connection refused”)

Also double check that’s definitely the IP the cam currently has and isn’t some other device on your network.

It opened up a new window waiting for a prompt.

That is the correct IP. It’s in the app and I cannot ping it if i unplug the power wire.

Thank you for sharing that screenshot. It doesn’t tell me a lot, but it’s similar to what I’m seeing now on one machine. What do you find in the log when you check that?

Based on what I’m experiencing, I suspect that your problem might be with VLC or something else on your PC. I’m having issues with it now (unable to stream RTSP from either my test Cam Pan v3 or a test Tapo C120) on Trisquel/MATE, which installs VLC 3.0.16, but it’s working as expected (for both cameras) on Ubuntu/GNOME with VLC 3.0.20 and on Windows with VLC 3.0.23. I don’t know why it’s hosed right now in my Trisquel environment. I swear that was working recently when I installed ZoneMinder just to see if I could get that to work.[1] I’m not familiar with VLC’s log, but I’ll try checking that to see if it tells me anything.

Other thoughts/questions (in addition to the question about the VLC log above):

  • What version of VLC are you using?
  • What other troubleshooting have you done?
  • Do you have other RTSP-enabled cameras that you’re able to stream in VLC and/or Blue Iris?
  • Can you see the RTSP stream with FFplay? (In my Trisquel environment, I’m able to stream both cameras with FFplay even though VLC chokes on both.)
  • As @dave27 mentioned, you can telnet 192.168.1.131 554, and if the standard RTSP port is open and responding properly at that IP address, then you should see something like this:
    $ telnet 192.168.1.131 554
    Trying 192.168.1.131...
    Connected to 192.168.1.131.
    Escape character is '^]'.
    
  • You can also use something like Nmap, and a command like nmap -p 322,554 192.168.1.131 should return something like this in the results:
    PORT    STATE SERVICE
    322/tcp open  rtsps
    554/tcp open  rtsp
    
    Something like that can give you more detail about your situation, but using telnet is probably a simpler test if you already have that on your system (and the last time I had to install it on Windows, that was fairly straightforward).

If you’re confident about the username, password, and IP address that you’ve given your Cam, then I’d try telnet (and/or nmap) plus ffplay in your troubleshooting if you haven’t already done that. Note that if you use FFplay for RTSP (instead of RTSPS), then you’ll want to make adjustments to your command line arguments that differ from what’s in the RTSP Testing Instructions. Discussion at RTSP BETA RELEASE FOR v3 and Pan v3! - #432 by Crease and some preceding posts might be helpful if you choose to try that.


Edit @ 2026-03-12T22:44:09Z

Added another question above that I meant to ask earlier.

Edit @ 2026-03-13T17:15:15Z

Corrected a memory error above.


  1. I believe that I misremembered this earlier. In order to get ZoneMinder working, I was testing successfully with FFplay and not VLC on that machine. ↩︎

Sounds like you have network connectivity in that case then.

Yeah, you went way above my head, lol.

Yes, I know that the ip and user /password is correct. If I unplug the camera I can’t ping it.

I have 22 cameras in my system so I do have a clue what I am doing.

I just can’t get this one to work. I’ve added Tapo cameras with just a user name. I’m not sure why this is so stubborn

The Tapo cameras I’ve used have required a username and password to be created in a “Camera Account” for each camera in the app according to their instructions (fairly similar to enabling RTSP on a currently compatible Wyze Cam), and that’s what I’ve been able to make work.[1]

If you’re able to stream your Tapo cameras in VLC on this same PC where you’re having problems with a Wyze Cam, then I wonder what your RTSP settings screen in the Wyze app looks like for this Cam. Do you want to share a screenshot of that?

Also, did you try using FFplay to see if you could stream via RTSP or RTSPS with that? If you have FFmpeg on your system (you might already have it if you’re using other software that uses FFmpeg as a dependency), then you probably already have FFplay. If not, then you can try downloading FFmpeg to see if you can get the Wyze stream to work with that. If FFplay is able to consume the RTSP steam, then at least you’ll know that the RTSP connection to the Cam works and that your problem focus can be narrowed to VLC and/or Blue Iris.


Edit @ 2026-03-13T17:29:14Z

Updated earlier footnote.


  1. This has been my previous experience, anyway, except for whatever is causing problems in VLC for both my Tapo and Wyze cameras on this one platform I was trying to use earlier today; in my case, I think it’s an issue with that particular VLC instance at this time, and I should probably dig into the logs.

    Edit: After checking the logs and doing some searching online, I believe that it’s a problem with VLC on that machine because of Debian’s decision not to include RTSP support in the VLC version available from their repositories—and thus downstream to Trisquel’s repositories—as Trisquel has a stated mission to be “fully free” and the components required for RTSP support in VLC contain non-free code. Ubuntu operates with no such restrictions, plus I installed VLC on Ubuntu via snap and not APT, so that may also have something to do with my experience. ↩︎

To be honest, I haven’t used the Tapo cameras in VLC, I have them in Blue Iris. Yes, I had to set a user name and password in the Tapo settings. It seems like it would have been the same thing for the Wyze camera. Seems like a very similar setup. I’ll try the FF play

1 Like

This is my setting in BI. I tried it as RTSP as well, but then it greys out the make/model

1 Like

That’s helpful in some way. At least it tells you that you still don’t know if one of the problems you mentioned in your initial post is a VLC issue or a Wyze Cam issue, so you can’t just rule out one thing or the other without more data, I don’t think. Trying to stream a Tapo camera in VLC could provide some data, and if you can get your Wyze Cam to stream to VLC (which is one of the platforms listed in the 3rd Party Software Compatibility table of the Wyze RTSP Testing Instructions), then at least that’s confirmation that you have RTSP working and that you can locally stream that way.

That would be another way to confirm. Again, if you choose to try FFplay, please take note of my previous posts and links, because the command parameters provided in the Testing Instructions are specific to RTSPS and should be modified if you’re using RTSP.

When I compare your screenshot to what @MTPG13 posted above, I see that the options on the right side of the “Advanced” section of your screens differ, so I wonder if you’re using different versions of Blue Iris. I seem to recall at least one user in another Forum topic mentioning problems getting RTSP on Wyze Cams to stream in Blue Iris sometime within the past few months and updating the Blue Iris software might have helped (again, I’m going from memory and don’t actually use Blue Iris), but I don’t recall exactly which topic it was (probably one of the topics I linked in post #2 above). You can probably find that using the Forum’s search facility.

Thanks for sharing the Wyze app screenshot. It looks like you do have it enabled correctly on the Cam. :+1: