Smart Home Community > Tapo Smart Camera > RTSP bug
< Tapo Smart Camera

RTSP bug

RTSP bug

RTSP bug
RTSP bug
a week ago
Tags: #Firmware #Device Connectivity #Live View #ONVIF/RTSP #Bug
Model: Tapo C210  
Hardware Version: V2
Firmware Version: 1.4.7 Build 250625 Rel.55603n

So I just found a bug with RTSP, probably firmware, before I changed the credentials, everything was perfectly fine, but then after a while I changed the credentials of the RTSP stream for security and trying to solve another problem, but now I can only connect to the Camera ONCE then I get a 401 Unauthorised on ffmpeg, IPCams it says the camera rejected the credentials and VLC asks me to just re-enter the credentials

I don't know if it is a valid way to reproduce, seems to be happening to me

For me:
Turn off Camera Account
Reboot Camera via App
turn on Camera Account
Access rtsp stream
then stop accessing the rtsp stream, either by closing the window or ctrl+c for terminal with ffmpeg or ffplay
Try reaccess the stream again
401 Unauth or not letting you connect, SO I have to reboot the camera EACH TIME I want to access the rtsp stream

And I guess set a account, then change the password again or delete the camera account then readd a camera account and the bug should occur, or before you try reproduce the steps I did

  0      
 
  0      
 
#1
Options
7 Reply
Re:RTSP bug
a week ago

  @redozer 
 

52)20250831 16:36:15        
<4>2025-08-31 16:36:07[RTSP]Authentication pass
<4>2025-08-31 16:36:07[RTSP][rtsp] session state: idle -> init
<4>2025-08-31 16:36:07[RTSP][rtsp] session state: init -> ready
<4>2025-08-31 16:36:07[HTTP]Add a minor stream, current minor stream preview client count is 1
<4>2025-08-31 16:36:07[HTTP]current streams: main(0) minor(1) playback(0) download(0) tapocare(0) talk(0)
<4>2025-08-31 16:36:07[RTSP][rtsp] session state: ready -> playing
<4>2025-08-31 16:36:09[RTSP]New client accessing: 192.168.0.54 sock 48
<4>2025-08-31 16:36:09[RTSP]Accept client with iSessionID 1
<4>2025-08-31 16:36:09[RTSP]New client accessing: 192.168.0.54 sock 49
<4>2025-08-31 16:36:09[RTSP]Accept client with iSessionID 2
<4>2025-08-31 16:36:09[RTSP]Password is incorrect
<4>2025-08-31 16:36:09[RTSP]Password is incorrect
<4>2025-08-31 16:36:09[RTSP]CloseSession called, 1th in 3
<4>2025-08-31 16:36:09[RTSP]CloseSession called, 2th in 2
<4>2025-08-31 16:36:09[RTSP]New client accessing: 192.168.0.54 sock 48
<4>2025-08-31 16:36:09[RTSP]Accept client with iSessionID 1
<4>2025-08-31 16:36:09[RTSP]New client accessing: 192.168.0.54 sock 49
<4>2025-08-31 16:36:09[RTSP]Accept client with iSessionID 2
<4>2025-08-31 16:36:09[RTSP]Password is incorrect
<4>2025-08-31 16:36:09[RTSP]CloseSession called, 1th in 3
<4>2025-08-31 16:36:09[RTSP]Password is incorrect
<4>2025-08-31 16:36:09[RTSP]CloseSession called, 2th in 2
<4>2025-08-31 16:36:21[RTSP]New client accessing: 192.168.0.54 sock 48
<4>2025-08-31 16:36:21[RTSP]Accept client with iSessionID 1
<4>2025-08-31 16:36:21[RTSP]New client accessing: 192.168.0.54 sock 49
<4>2025-08-31 16:36:21[RTSP]Accept client with iSessionID 2
<4>2025-08-31 16:36:21[RTSP]Password is incorrect
<4>2025-08-31 16:36:21[RTSP]Password is incorrect
<4>2025-08-31 16:36:21[RTSP]CloseSession called, 1th in 3
<4>2025-08-31 16:36:21[RTSP]New client accessing: 192.168.0.54 sock 48
<4>2025-08-31 16:36:21[RTSP]Accept client with iSessionID 1
<4>2025-08-31 16:36:21[RTSP]CloseSession called, 2th in 3
<4>2025-08-31 16:36:21[RTSP]New client accessing: 192.168.0.54 sock 49
<4>2025-08-31 16:36:21[RTSP]Accept client with iSessionID 2
<4>2025-08-31 16:36:21[RTSP]Password is incorrect
<4>2025-08-31 16:36:21[RTSP]CloseSession called, 1th in 3
<4>2025-08-31 16:36:21[RTSP]Password is incorrect
<4>2025-08-31 16:36:21[RTSP]CloseSession called, 2th in 2
<4>2025-08-31 16:36:23[RTSP]CloseSession called, 0th in 1
<4>2025-08-31 16:36:23[HTTP]Delete a minor stream, current minor stream preview client count is 0
<4>2025-08-31 16:36:23[RTSP][rtsp] session state: playing -> idle
<4>2025-08-31 16:36:25[RTSP]New client accessing: 192.168.0.54 sock 43
<4>2025-08-31 16:36:25[RTSP]Accept client with iSessionID 0
<4>2025-08-31 16:36:25[RTSP]New client accessing: 192.168.0.54 sock 44
<4>2025-08-31 16:36:25[RTSP]Accept client with iSessionID 1
<4>2025-08-31 16:36:25[RTSP]New client accessing: 192.168.0.54 sock 45
<4>2025-08-31 16:36:25[RTSP]Accept client with iSessionID 2
<4>2025-08-31 16:36:25[RTSP]Password is incorrect
<4>2025-08-31 16:36:25[RTSP]Password is incorrect
<4>2025-08-31 16:36:25[RTSP]CloseSession called, 0th in 3
<4>2025-08-31 16:36:25[RTSP]New client accessing: 192.168.0.54 sock 43
<4>2025-08-31 16:36:25[RTSP]Accept client with iSessionID 0
<4>2025-08-31 16:36:25[RTSP]CloseSession called, 1th in 3
<4>2025-08-31 16:36:25[RTSP]CloseSession called, 2th in 2
<4>2025-08-31 16:36:25[RTSP]New client accessing: 192.168.0.54 sock 44
<4>2025-08-31 16:36:25[RTSP]Accept client with iSessionID 1
<4>2025-08-31 16:36:25[RTSP]CloseSession called, 0th in 2
<4>2025-08-31 16:36:25[RTSP]CloseSession called, 1th in 1
<4>2025-08-31 16:36:31[RTSP]New client accessing: 192.168.0.54 sock 43
<4>2025-08-31 16:36:31[RTSP]Accept client with iSessionID 0
<4>2025-08-31 16:36:31[RTSP]CloseSession called, 0th in 1
<4>2025-08-31 16:36:32[RTSP]New client accessing: 192.168.0.54 sock 43
<4>2025-08-31 16:36:32[RTSP]Accept client with iSessionID 0
These are the logs of me trying to access the RTSP stream. At the top it works at first but then Password is incorrect. I can send full log file

  0  
  0  
#2
Options
Re:RTSP bug
a week ago

  @redozer 

Hi,
Please confirm the following information for the reported phenomenon.


  1. How many devices are streaming the camera's live feed simultaneously, including via the Tapo app and RTSP stream?
  2. If you are unable to establish the RTSP/Onvif connection after disconnecting, please check if another device can establish the RTSP/Onvif connection with the camera.
  3. Have you collected the camera log by referring to the following instructions? If not, please refer to it to collect the camera log first.
      How to get the log of Tapo Camera 
 

Best Regards

>>How to position my TP-Link camera for optimal performance. >>What to do if the Detection feature is not working on the TP-Link Camera? >>Encrypt microSD Card: Protecting Video Recordings Stored on the SD Card.
  0  
  0  
#3
Options
Re:RTSP bug
a week ago - last edited a week ago

  @Solla-topee 

Not simultaneously, the app works fine, RTSP doesn't. Only You can connect to the device ONE TIME after restarting the tapo device will you be able to access the stream. then when trying again, you cannot access. I previously had a Yawcam Ai Instance streaming, so probably one device, but it's not streaming anymore, and I only access probably in the afternoon.
I can access all other of the three tapo cameras easily over rtsp and control them with onvif.


I have the log for the camera. I can send to you over PM

  0  
  0  
#4
Options
Re:RTSP bug
a week ago

  @redozer 

Hi, 
After establishing the RTSP stream and stopping access to the camera via the RTSP stream, please remove the camera from third-party apps (such as VLC); instead of simply closing the windows or terminal with ffmpeg or ffplay, then, test if you can establish the RTSP stream again. 
If not, try establishing the RTSP stream with another URL (such as rtsp:// IP Address/stream2, rather than stream 1) and then see if you can establish the RTSP stream successfully.
Best Regards

>>How to position my TP-Link camera for optimal performance. >>What to do if the Detection feature is not working on the TP-Link Camera? >>Encrypt microSD Card: Protecting Video Recordings Stored on the SD Card.
  0  
  0  
#5
Options
Re:RTSP bug
Friday - last edited Friday

  @Solla-topee 
I already have removed from a web ui nvr. I am no longer using it.

I cannot access. I even reset the device, still, stream1 and stream2 do not work

and yes I did cross verify username and password. Now I cannot access it at all! cannot access rtsp stream at all, after that reset now I cannot access it! I even set a new username and password, once the factory reset was over. But now I cannot access the stream at all!

  0  
  0  
#6
Options
Re:RTSP bug
Monday - last edited Monday

  @redozer 

Hi,
If you can't establish the RTSP/Onvif stream with the Tapo C210, please refer to the following instructions for troubleshooting. Then, send us the results of each step for further assistance.
What can I do if I fail to stream the Tapo camera via the RTSP/ONVIF protocol?
Best Regards

>>How to position my TP-Link camera for optimal performance. >>What to do if the Detection feature is not working on the TP-Link Camera? >>Encrypt microSD Card: Protecting Video Recordings Stored on the SD Card.
  0  
  0  
#7
Options
Re:RTSP bug
7 hours ago - last edited 7 hours ago

  @Solla-topee 
Ok so I decided

Delete current camera account
Create new one, temp creds, if you want I will send logs, and creds for the camera and connectivity of other tapo cameras
Then via VLC tried doing rtsp://user:pass@192.168.0.74
rejected
IPCams, Logged in successfully, but then Camera Rejected credentials
The forum is not letting me post another image so follow this link: login fail (leads to imgur)

here is PART of the log
<4>2025-09-10 21:23:37[RTSP]New client accessing: 192.168.0.140 sock 43
<4>2025-09-10 21:23:37[RTSP]Accept client with iSessionID 0
<4>2025-09-10 21:23:37[RTSP]New client accessing: 192.168.0.140 sock 45
<4>2025-09-10 21:23:37[RTSP]Accept client with iSessionID 1
<4>2025-09-10 21:23:37[RTSP]CloseSession called, 0th in 2
<4>2025-09-10 21:23:37[RTSP]CloseSession called, 1th in 1
<4>2025-09-10 21:23:37[RTSP]New client accessing: 192.168.0.140 sock 43
<4>2025-09-10 21:23:37[RTSP]Accept client with iSessionID 0
<4>2025-09-10 21:23:37[RTSP]New client accessing: 192.168.0.140 sock 45
                                                     
(125)20250910 21:24:02       
<4>2025-09-10 21:23:37[RTSP]Accept client with iSessionID 1
<4>2025-09-10 21:23:37[RTSP]CloseSession called, 0th in 2
<4>2025-09-10 21:23:37[RTSP]CloseSession called, 1th in 1
<4>2025-09-10 21:23:39[RTSP]New client accessing: 192.168.0.140 sock 43
<4>2025-09-10 21:23:39[RTSP]Accept client with iSessionID 0
<4>2025-09-10 21:23:39[RTSP]New client accessing: 192.168.0.140 sock 45
<4>2025-09-10 21:23:39[RTSP]Accept client with iSessionID 1
<4>2025-09-10 21:23:39[RTSP]CloseSession called, 0th in 2
<4>2025-09-10 21:23:39[RTSP]CloseSession called, 1th in 1
<4>2025-09-10 21:23:39[RTSP]New client accessing: 192.168.0.140 sock 43
<4>2025-09-10 21:23:39[RTSP]Accept client with iSessionID 0
<4>2025-09-10 21:23:39[RTSP]New client accessing: 192.168.0.140 sock 45
<4>2025-09-10 21:23:39[RTSP]Accept client with iSessionID 1
<4>2025-09-10 21:23:39[RTSP]CloseSession called, 0th in 2
<4>2025-09-10 21:23:39[RTSP]CloseSession called, 1th in 1
<4>2025-09-10 21:23:50[RTSP]New client accessing: 192.168.0.140 sock 43
<4>2025-09-10 21:23:50[RTSP]Accept client with iSessionID 0
<4>2025-09-10 21:23:50[RTSP]New client accessing: 192.168.0.140 sock 44
<4>2025-09-10 21:23:50[RTSP]Accept client with iSessionID 1
<4>2025-09-10 21:23:50[RTSP]CloseSession called, 0th in 2
<4>2025-09-10 21:23:50[RTSP]CloseSession called, 1th in 1
<4>2025-09-10 21:23:50[RTSP]New client accessing: 192.168.0.140 sock 43
<4>2025-09-10 21:23:50[RTSP]Accept client with iSessionID 0
<4>2025-09-10 21:23:50[RTSP]New client accessing: 192.168.0.140 sock 44
<4>2025-09-10 21:23:50[RTSP]Accept client with iSessionID 1
<4>2025-09-10 21:23:50[RTSP]CloseSession called, 0th in 2
<4>2025-09-10 21:23:50[RTSP]CloseSession called, 1th in 1
<13>2025-09-10 21:23:52[REMOTE_DEBUGGER]diagnose_log: id(107), offset(430080)

log from today. full log will be sent via email, not in PM, if required. 
 

  0  
  0  
#8
Options

Information

Helpful: 0

Views: 200

Replies: 7

Tags

Firmware Device Connectivity Live View ONVIF/RTSP
Bug
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.