I was advised to ask about RTSP here, since the old thread with discussion of RTSP is old.
I installed the latest (4.36.16.7064) update in hopes of getting RTSP working:
and I’m stuck again unable to proceed past the disabling of RSTPS. The Accept button is not visible, and I can’t scroll to it:
despite my default text size is set to normal. I was able to work around this by installing the Wyze app on a borrowed iPad, and now I can see the Accept button, but pressing it results in this error:
and clicking through that shows that RTSPS is still enabled. Blue Iris does not work with RTSPS, so I really need to turn this off. And RTSPS doesn’t seem to be working anyway, since I pointed VLC at it, and it fails to connect, and I put Claude AI on the job for 20 minutes, and it reports:
“Why VLC (and ffmpeg) fail too: I walked through the actual RTSP Digest-auth handshake by hand (TLS connect →
DESCRIBE→ camera replies401with a nonce → resendDESCRIBEwith computed credentials on the same connection). The camera silently drops the TLS connection with zero response the moment it receives that second, authenticated request — this happened identically with the correct password and a deliberately wrong one, and reproduced twice. Every standard RTSP client (VLC, ffmpeg, Blue Iris) does exactly this challenge/retry sequence over one persistent connection per RFC 2326, so they all break the same way. A fresh connection using a stale nonce gets an actual401 Invalid Authorizationreply rather than a drop — so the server can respond, it just breaks specifically on the auth-retry-on-same-connection pattern. Repeated auth attempts also appear to trigger a temporary anti-brute-force lockout (subsequent TLS handshakes started getting reset outright), so credentials aren’t the problem — the firmware’s digest-auth implementation is.”