note on issues with tapo protocol
Are you sure this makes sense? Does anyone else confirm this? Is there a discussion of this problem somewhere?
Are you sure this makes sense? Does anyone else confirm this? Is there a discussion of this problem somewhere?
This is my personal experience. I was struggling with setting the tapo protocol for a C210 camera and couldn't make it work (plaintext, md5, sha256). At some point I saw I had 2FA, switched it off, and voila - tapo protocol working - 2-way audo, microphone and the works (plaintext and sha256 worked fine).
All this time rtsp was working fine with a secondary account set up in the app.
While I'm here commenting, can i set the sub-stream (the small one) via the tapo protocol? I couldn't find any documentation on the subject.
You can use subtype query param
https://github.com/AlexxIT/go2rtc/blob/34b103bbcba512a07fb1ea8a3c219ae31d2201bf/pkg/tapo/client.go#L114-L120
Are you sure this makes sense? Does anyone else confirm this? Is there a discussion of this problem somewhere?
This is my personal experience. I was struggling with setting the tapo protocol for a C210 camera and couldn't make it work (plaintext, md5, sha256). At some point I saw I had 2FA, switched it off, and voila - tapo protocol working - 2-way audo, microphone and the works (plaintext and sha256 worked fine).
All this time rtsp was working fine with a secondary account set up in the app.
While I'm here commenting, can i set the sub-stream (the small one) via the tapo protocol? I couldn't find any documentation on the subject.
Thanks man you saved my day. I had the same issue until I read your comment.
One of my tapo cameras started to fail. I found that on this model (C520WS), go2rtc was getting "unauthorized" when using tapo protocol. The solution is to go to the tapo app and enable "Me>Tapo lab>Third-party compatibility".
My other tapo cameras have not been affected