I’m hoping someone from wyze can answer us here, but I believe the cameras are requiring a ping back from api.wyze.com over the Internet in order to keep the stream active.
Not sure why that is needed as plenty of other higher end cams do not need this to keep an RTSP stream up. Just seems like they don’t want to completely cut the cord for some of us.
Wow great, hopefully it’ll be coming to v4s soon! Just upgraded my cameras to v4 all except one.
Yes, Dave said V4s are next!
Like you, I upgraded a lot of my cams to v4s so that I could have 2K resolution. Probably definitely look forward to that one getting it.
You should only be getting this error if the camera firmware hasn’t been upgraded to the RTSP firmware mentioned at the top of this forum.
Need cameras updated
New RTSP app
Should be good to go.
Thanks a bunch, I’ve downloaded and upgraded one camera out of about 10 of them, two Pan V3, so far it’s working flawlessly. I’m using Scrypted to stream it.
Nice, I’ll have to look into scrypted. I pull everything into frigate and then home assistant. Working flawlessly so far as well for me.
Any problems with Wyze required special password characters in Frigate? Did you use URL Encoding or which special characters work?
I tried different ones *, vs @, encoding, had it running once, but a couple power blips took it out. Wouldn’t recover. Ever.
So I’m finally back for one more try. Don’t wanna blow up Frigate again and wreck the two Reolink that work perfectly and install in 15 minutes.
Any help appreciated. Sample config less passwords etc. In case its me.
Doing one or all ifnthey work, Pan V3s all over again, the one of three that did work for about a week. The other two Pans, one flashed wouldn’t stream to Frigate and one wouldn’t flash at all.
I’m flashing this time with a 32gb new SD instead of a 64gb.
Went with the ! special character and no special encoding when placing it into the frigate config for me.
I do have all my frigate cams using forced tcp instead of udp/either. Don’t fret if they havent shown up in frigate immediately either. Give it a bit, sometimes they are just buggy. Gotta remember we are using 30 dollar hardware here, at least in the case of my v3’s.
Good luck in your endeavor!
Update: I got it to flash, I was using a different power brick. I’m not sure if that was actually the reason.
Now, I’m with the same boat as the other folks, Code -36 and I can’t configure RTSP, it keeps telling me lost connection to the device.
Ok, so I’ve upgraded the V3 ones, and they’re working flawlessly. Now I’m having a hard time flashing the Pan V3. I’m holding the setup with one hand and plugging it to the wall with the other. Stays red for a while then starts booting normally with the same firmware. No purple whatsoever. Is there a special trick? I tried using a different sd-card, but that didn’t help. Any help would be appreciated.
What card size and format are you using? I’ve been successful only with 32 GB cards formatted FAT32 with just the single .bin file in the root directory. I haven’t tried smaller cards using that format, but I would expect those to work.
Are you using the .bin specific to Cam Pan v3? If the Cam Pan v3 doesn’t see the correct filename (recovery_wyzepan3.bin) in the card’s root directory, then it’s probably not going to show you the purple LED and attempt to flash.
And now I see that you updated your post while I was writing. 
Cam Pan v3 uses a 5V ⎓ 2A power adapter, while most stationary Wyze Cams use 5V ⎓ 1A, just FYI.
Thank you for the quick reply and clarifications, I’m not sure if you have the Pan V3, if you do, are you experiencing the same issue with Code -36?
You’re welcome!
I have only a single Cam Pan v3 flashed for this, and I haven’t been super engaged with testing this particular feature because I have been busy with other things and don’t use Home Assistant, so my limited experience with this so far has been to get RTSPS working for the one Cam and then test streaming it to FFplay (which it will apparently continue to do even when the app sets the Cam to Privacy Mode).
I’ve had that Cam powered down and offline but fired it up again to check. This is my experience:
| Cam | Firmware | App | Plugin | App Live Stream Result |
|---|---|---|---|---|
 Pan v3 |
4.50.16.5055 | v3.9.0.a905 | 3.8.0.7 |  |
| Pan v3 |
4.50.16.5055 | v3.8.7.725 | 3.8.0.8 | “Failed to connect. Error: (code -36)” |
I don’t use iOS at all, but my conclusion from this is to continue using the specific app provided for RTSP testing until Wyze merges everything that’s necessary into the production channel.
I’m into round two for my three Pan V3s.
Did one successfully again, streams in VLC anyhow. Didn’t drop it in Frigate yet.
I also had one Pan Cam refusing to flash at all, like yours, one that flashed and wouldn’t stream to Frigate, but did to VLC.
I’m trying again. I only had error 36 before if I tried to open a flashed camera in the standard app.
Only opens flashed Pan Cam in the RTSP app for me or error 36. Same for round 2.
I’m using Android if it matters.
Personally, I also found if I didn’t turn off Record to SD before flashing, after flashing or trying to, it writes trash files to the RTSP flash SD on boot up if you had an SD in it to start with.
I’m using a brand new 32gb SD and will try flashing the other two again tomorrow
Thanks for the quick reply.
Let’s hope you will have better results tomorrow.
Anyone know if firmware is getting pushed today? Saw a comment on a thread from WyzeDave saying 12/1 was the planned rollout date for rtsp in the app without manual flashing.
It’s a long thread, after my failed first attempts weeks ago with three Pan V3s. Who reads a thread this long? 
What worked for me today.
Purchased a 32gb new SD, Verbatim. $6 Amazon Black Friday. Cost me a dollar with Prime points.
SD was already fat32, added Wyze RSTP firmware file to empty SD.
Added RTSP app back on my phone the hot fix one, skipped the first.
I record to SD, so I turned off Record to SD in Wyze app on all three Pan V3s. (records trash to flash SD if on at bootup.)
Flashed garage cam yesterday. Flashed fine. Flashed the other two today and they also flashed. So far…
Added garage Pan V3 to Frigate. Streaming.
Will add other two today…
What I/we didnt know initially.
32gb SD or (less) reading above, clean formatted fat32.
That was my problem all along as my old SD was 64gb.
Why 32gb worked? 
Who knows? Wyze?
Otherwise follow the original posted directions.
May vary with other cams or not.
Here’s my config snippet example redacted some. if it’s helpful at all. Systems vary. All three Wyze Pan V3s streaming. Any issues unknown at this point, just put them in today.
HP Z1 G5 Workstation, Ubuntu desktop, running in 1tb NVMe, 64gb RAM, Frigate Storage NVMe 1tb for now. (I know, overkill, it was new in box and cheap.) It’s a beast.
Frigate in Docker on host.
HAOS in Ubuntu KVM VM
mqtt:
enabled: true
host: 192.168.x.x
user: mqtt-user
password: REDACTED
go2rtc:
streams:
# Reolinks
reolink_sub:
- rtsp://admin:REDACTED@192.168.x.x:554/Preview_01_sub
reolink_main:
- rtsp://admin:REDACTED@192.168.x.x:554/Preview_01_main
reolink2_sub:
- rtsp://admin:REDACTED@192.168.x.x:554/Preview_01_sub
reolink2_main:
- rtsp://admin:REDACTED@192.168.x.x:554/Preview_01_main
ffmpeg:
hwaccel_args: preset-vaapi
detectors:
coral:
type: edgetpu
device: usb
cameras:
wyze_pan_v3:
ffmpeg:
inputs:
- path: rtsp://USERNAME:PASSWORD@192.168.x.x:554/stream0
input_args: -rtsp_transport tcp -timeout 5000000
roles:
- detect
- record
detect:
enabled: true
width: 640
height: 360
fps: 5
objects:
track:
- person
motion:
threshold: 25
contour_area: 30
wyze_pan_v3_2:
# same block, different credentials/IP
wyze_pan_v3_3:
# same block, different credentials/IP
# rest of recording/snapshots/detect sections unchanged
The format of the SD card is important. Fat32 only accepts up to 32gb partitions, I bet your 64GB card was being formatted to EXfat or something like that.
You’d have to use diskpart, partition that 64gb card into two smaller, then make those fat32. Not worth it usually. Glad you got them working!
Not a Linux expert, yet.. Getting there though. Still tweaking, seems like forever, lol. Some, but not all, videos & snaps come in black in web ui review. Will observe and enjoy the win so far, before breaking it again. Detections all black. 
