Downloaded and written to a brand new 16GB uSD card. I will be flashing at least several V3 cameras this evening and setting them up on my BlueIris server.
Thank You! Thank You! Thank You!!!
Downloaded and written to a brand new 16GB uSD card. I will be flashing at least several V3 cameras this evening and setting them up on my BlueIris server.
Thank You! Thank You! Thank You!!!
Oh, Looks like you folks are excited to see this, huh?
Got that right!
I was just grumbling a couple days ago when I replaced my front porch V2 camera with a V3 that I lost access to the front porch via BlueIris.
FINALLY…WYZE actually came through…lets get this firmware installed and see if I am going to buy and recommend LOTS OF v3s…Wahoooooo
I have installed this firmware on my V3 and Blue Iris is working with it, but I am getting wireless disconnection and reconnect every 5-7 minutes or so. I can see the camera FPS start to drop, the video stops updated and then 20 seconds later is connected again.
It didn’t do this when running the older hacked RTSP firmware, so I don’t believe there are wireless isuees.
Best to report all issues in the Beta test thread with a log number if possible:
Sounds like the same issue with v2 FW. Can anyone check if this firmware is implementing rtsp optimized this time, someone before was able to pinpoint the fact that some of the libraries used were expired and not optimized, and just “slapped together”. Hopefully they’ve done a better job this time though.
Have 2 wc3s with working sd cards, will not pick up the firmware…
Make sure you renamed the file correctly. Since Windows likes to hide filename extensions, many people actually renamed the file to demo.bin.bin - which will not work.
First of all, thank you (and all involved) so much. I can’t help but think it had something to do with me posting today in the subreddit that I wasn’t going to be buying a v2 Pan until they released an RTSP fw for the v3 and then ate my words, gave in and ordered one anyway. Then I find this post! I have to believe it’s karma!
And thanks for this explanation:
Honestly, it’s the first time I have ever heard a Wyze rep explain it this way and so openly. I think others were afraid that admitting that the firmware was having some growing pains with all of the new features added would open up another PR can of worms. But this (and the rest of the explanation) really shed a reasonable light on the process and admitting that it is a challenge isn’t a sign of weakness; it’s a sign of transparency. This is one of the main reasons I stuck with Wyze and why I just bought another cam (to replace a current Pan, which will go on to knock out one of the remaining non Wyze cams to become a majority).
Got some work (reviewing product from some other companies) to knock out before I can test the v3 firmware, but I downloaded it immediately. Thanks to all involved once again.
It is, I don’t have it to hide extension, it’s in fact demo.bin. We should move this to the beta thread though…
Do you mean on a V2 or is there a hacked version of RTSP for the V3 prior to this beta release?
Well, first try to install the RTSP to a v3 failed. It kept saying “ready to connect”. So I turned it off and removed the SD card and placed in my computer and it was unreadable. Even though before I tried flashing it, it was reading fine in my computer. And NO, I had the file name correct. So I am now FORMATTING the SD card on my computer and will try again.
Update: As juched said, DO NOT rename the zip file, just place as is on the SD card. For me, I removed the SD card that was present, replaced it with the firmware SD card, followed the instructions. When I returned the light was flashing red. Does NOT auto appear in the Wyze app as stated in the instructions. Powered down, replaced the SD card with the original. Deleted the old v3 in the Wyze app and pressed the + add button in the app. Powered up the v3 and pressed the setup button on the camera. Went thru the setup as usual and the camera was added to the Wyze Android app. Went into Advanced setting and enabled RTSP.
iSpy windows application does not want to PNP using similar config parameters as the v2s, ex: rtsp://username:password@192.168.1.###/live I will try again tomorrow.
STRANGE: I fired up my android version of Tiny Cam Pro , thinking I would have to reconfig it with this new v3 RTSP camera, but NO, it was working without doing anything…using the OLD NAME of the v3 that was DELETED from the Wyze app. . !! How can that happen?
It seems much more stable when using UDP mode in Blue Iris. No more disconnects.
For the firmware, ensure you don’t change the name to demo.bin, but use the name of the bin file inside the zip. Worked for me. Initially renamed the file to demo.bin and would only get “ready to connect”. Left the filename and it updated first try.
Good tip (could you post in the beta thread). What is the camera saying the FW version is?
Mine Says: 4.61.0.3
Could anyone who is testing this firmware and having issues please post in the v3 RTSP Beta thread linked below.
Thank You
I found i had to “regenerate” the URL once again for it to work. RTSP is working great for me now.
v3 RTSP up and running on Synology nicely.
4.61.0.3 here too.
Some good discussion in the Beta thread. I think they are getting it to work:
I just bought one for testing!