Wyze Cam v3 :
Version: 4.36.14.3497
What’s New:
Wyze Battery Cam Pro:
Version: 1.4.3.4543
What’s New:
All cameras updated tfirmware without issue. I saw disclaimer about BCPro not being able to update if battery level was below 20%. Then I wondered why since I have all hooked up to their own solar panel which keeps charged to 100%. I checked and they are at 100%. I activated update on those and they went right through.— DJ
I think that’s a generic warning. Like you I’m on solar, have seen it in the past and remember scratching my head.
Has anyone else noticed that with this firmware, v3 cameras in a group can only be opened once from within the group? If I try opening the same camera again from within the group, it hangs up on “Connecting camera… (1/3)”. Restarting the app (Android) will allow the camera to be opened again, but only one time. Opening the camera from the Devices tab does not have this issue. I have v4, Pan v2, Pan v3, OG and OGT cams in the same group, and only the v3s exhibit this behavior after they were updated with this firmware.
Wyze Android app: v3.5.0.664
Samsung Galaxy S20+ 5G (Android 13)
Wyze Cam V3 with beta FW 4.36.14.3497:
As expected, it will still cause the V3 camera to restart itself automatically when the internet is out for more than 30 minutes. Once the camera is restarted then it will start recording in 20250507 folder with the timestamp of 2025-05-07 18:58:38 in the microSD card. It will overwrite the old footage. Alternatively, you can access the footage on the Wyze app as well on May 7th 2025 starting at 6:58pm. Keep this date in mind when you power cycle your cameras without internet or when you experience internet outage for more than 30 minutes. This date and time is only unique with this particular firmware as that should be the firmware build date.
Alternatively, users can manually flash back to FW 4.36.11.8391 as the Cam V3 doesn’t automatically restart when the internet is out for more than 30 minutes. If you wish to be on the latest firmware due to security improvements and other bug fixes, then another possible workaround would be enabling local NTP server and NTP intercept on your router as mentioned below. However, not a lot of router have this type of function available so YMMV.
Lastly, if you happen to power cycle your V3 camera while there is no internet then it will start recording on the date based on the firmware build date. The actual time might be different than listed below due to DST in my Eastern Time Zone. The Wyze app might think there’s recorded footage (green progress line on the timeline), but if you don’t see any footage then check ±1 hour.
I can’t recreate this issue on my end, but I only have Cam V3s in a group so it’s not the same setup as yours.
Wyze Android app: v3.5.0.664
Samsung Galaxy S20 FE on One UI 5.1 (Android 13)
Even though I don’t have a Cam v3, I enjoy the detail in these reports, and now I wonder when you’re going to start presenting it in tabular form:
| Firmware Version | Build Date | µSD Recording Start Time |
|---|---|---|
| 4.36.11.8391 | 2024-01-04 | 20:39 |
| 4.36.13.0416 | 2024-07-03 | 01:09 |
| 4.36.14.2953 | 2025-03-21 | 01:00 |
| 4.36.14.3289 | 2025-04-17 | 20:23 |
| 4.36.14.3497 | 2025-05-07 | 18:58 |
You don’t even have to use Discourse’s “Insert Table” tool. Markdown makes it easy enough:
|Firmware Version|Build Date|µSD Recording Start Time|
|:-|:-|:-|
|4.36.11.8391|2024-01-04|20:39|
|4.36.13.0416|2024-07-03|01:09|
|4.36.14.2953|2025-03-21|01:00|
|4.36.14.3289|2025-04-17|20:23|
|4.36.14.3497|2025-05-07|18:58|
I appreciate your diligent work!
Thanks for the valuable feedback. I too am running v3.5.0.664 of the Android app. Device is Samsung Galaxy S20+ 5G (Android 13).
I decided to resurrect an old Samsung tablet with Android 10 on it, and updated the Wyze app to 3.5.0.664. Wouldn’t you know, it doesn’t have the issue that my S20+ has. Guess it’s time to do more troubleshooting.
UPDATE:
Turned out not to be the firmware, but the app. I had updated the app to .664 a day or so before updating the firmware, and hadn’t yet noticed the issue with my v3s. Installed 3.4.5.650 of the app and all is good again.