Cannot connect to RTSP stream upgrading from 2.8.3 to 2.9.0 #1186
Comments
|
Authentication for the webUI and streams are on by default now, so you probably need to set the username and password for the stream. The username for the stream is 
You can change the API key by setting the If you're running the bridge 100% local, then you can probably set Please see the release log for more info: |
Got it, and thank you so much for the quick reply! Really appreciate all the hard work and help you have devoted to this project. My fault for not reading the release notes carefully enough. I will correct my settings, and it sounds like this will be a better setup with authentication moving forward. |
|
@mrlt8 Upgraded back to 2.9.0, tried both with the WB_API key and then I tried WB_AUTH=False, but I am getting constant disconnects either way. The connections are more stable for me on 2.8.3, so I may just stick with that version and continue troubleshooting the client disconnects with other settings tweaking. |
|
Hmm, anything in the logs when the disconnects happen? |
No errors, just some warnings about frame size and buffer: WARNING: Skipping wrong frame_size at start of stream [frame_size=1] WARNING: clear buffer It repeats those warnings for each camera and does a "Client stopped reading [camera]" message followed by "New client reading from [camera]" one. Here's a sample (I renamed the cameras, but the number matches each of their message): [CAMERA1] WARNING: clear buffer |
|
Seeing similar here. Can't get RTSP to work after upgrading to 2.9.0 Rebroadcast Plugin]: rtsp outgoing message |
|
Thank you. I'm looking into this. |
Thank you for the clarification! I'm also using BlueIris to record/motion sense/AI verification on my streams. I was initially confused as to which API key I needed to use to connect to the streams. Your comment on this thread makes it clear, but you might want to update the changelog and wiki to explicitly state that you need to use the WB API key provided in the WebUI, and not the Wyze API key provided in their user account management on their site. Just a suggestion, I figured it out pretty quick from looking at these issue threads, but might save some other users some time if you made that more explicit in the changelog and wiki. But thanks a ton for your work on this project, it works very well for me and I would have probably spent 2-3x more on non-Wyze cams to serve my needs if not for this software being available. |
* Tweak AV sync and ffmpeg cmd #1175 #1196 #1194 #1193 #1186 * Catch AccessTokenError * don't drop timestamp #1175 #1196 #1194 #1193 #1186 * Don't use_wallclock_as_timestamps #1175 #1196 #1194 #1193 #1186 * keep audio in sync #1175 #1196 #1194 #1193 #1186 * Ignore whitespaces in api key/id #1188 * Remove quotes from credentials #1158 * HA Add FORCE_FPS option #1161 * FORCE_FPS option for all cameras #1161 * changelog
|
Added the environmental variables ON_DEMAND=False to my unraid template and upgraded to v.2.9.3 released a little while ago, but I am still getting the following disconnects and errors (renamed cameras and not showing IP address but everything matches otherwise): [CAMERA2] WARNING: clear buffer Let me know if other details are needed to troubleshoot, thank you! |
|
@xcellentavi is the connection more stable if you disable audio? |
|
@mrlt8 I just set ENABLE_AUDIO=False instead of deleting it for now, but still getting [CONTROL] ERROR - error='[-20018] AV_ER_CLIENT_EXIT', cmd='_bitrate' on 2 of my cameras, also the [-13] IOTC_ER_TIMEOUT and [-20021] AV_ER_SENDIOCTRL_ALREADY_CALLED warning messages. |
|
@xcellentavi could you try the |
|
@mrlt8 I Just installed edge build, but I am still getting the following errors and warnings throughout: [CONTROL] ERROR - error='[-20018] AV_ER_CLIENT_EXIT', cmd='_bitrate' Let me know if other details and information would be helpful from the logs. Thank you! |
|
Could you try the latest edge build? Could you also see if setting |
|
@mrlt8 just tried the latest edge build from 14 hours ago, still getting the same group of errors. ON_DEMAND=false was already in my unraid template. It seems to be struggling with just 2 of my cameras, the WyzCam V3 and the WyzeCam Pan V3. The good news is the error messages are popping up less and less, I watched the logs for a few minutes and only got one of these errors: [CONTROL] ERROR - error='[-20010] AV_ER_INVALID_SID', cmd='_bitrate' The rest were a bunch of these warnings: WARNING: Skipping wrong frame_size at start of stream [frame_size=1] I'm optimistic that this is improving with each build, but let me know if there are other settings I should be adjusting. Thank you! |
|
Checked the logs this morning, and just seeing the following message scrolling every 20 seconds or so: Connection closed because of no response from remote. Only the 2 cameras with errors and warnings are not working; all the other Wyze cameras are still streaming. I can't figure out what could cause this. The wifi signal is as strong as the other cameras, and everything is running smoothly in the wyze app. All firmware is up to date, so I don't know what else I could troubleshoot to help pinpoint the problem... |
|
Can you try rebooting the problematic cameras? The latest firmware also super buggy and seems to kick off multiple connections if you open the app. |
|
Restarted the cameras from the wyze app and then closed it immediately, restarted the container, streams came back up but still errors and warnings as before. I do have more than one of each model giving me an issue, so I don't think it's the firmware (I could be wrong) and a 3rd camera is giving me these messages: [video] super slow |
|
You should be able to ignore those warnings if the streams are working. Most of those are related to the av sync. If you don't need audio, you can disable it and most of these issues should go away. |
|
I see another edge build from 25 minutes ago, I updated to that one (not sure what edge-qsv and edge-hw are for so I only select the edge one). I set ENABLE_AUDIO=false and it's still producing errors and warnings: [-20021] AV_ER_SENDIOCTRL_ALREADY_CALLED I have 6 streams, so I'm not sure if that is making this difficult to work or if I should adjust any other settings. |
Yea, the errors wouldn't bother me if the streams were working, but they are down in the logs and I was hoping they would help figure out a solution. I understand if this is just not going to be fixed, but still appreciate the attention you put into trying to help with this! |
|
Does downgrading back to 2.8.3 resolve the issues? |
|
It's not 100% when I switch back to 2.8.3, but all the streams do work, and then 1 of the cameras stops and starts with no signal on blue iris. So it's better on 2.8.3 for me, but I'm still seeing the [-13] IOTC_ER_TIMEOUT and dropped stream for 1 of the v3 cameras. |
|
Thanks, I'll try to see if there were any changes that might be causing the issue from 2.8.3. |
Describe the bug
Updated to 2.9.0, added the newer env variables in the new unRaid template (also added API settings and removed TOTP key), but all RTSP streams stopped working on my blueiris instance. Current network IP that works in all versions 2.8.3 and below is rtsp://[localip]:8554/camera-name with user and password set as default admin. Not sure what changed otherwise in the newest update, but I downgraded back to 2.8.3 for now.
WebUI does work on latest version, so it must simply be a setting issue in blueiris I am not able to figure out.
The text was updated successfully, but these errors were encountered: