3.1.5 Beta:
Versions:
- Android: 3.1.5.b566
- iOS: 3.1.5(3)
What’s new:
- Optimized Friendly Face feature
Wyze Cam OG Beta:
Version: 1.0.84
What’s new:
- Changed to only draw motion tagging bounding box within the motion detection zone
2 Likes
I’ll load 3.1.5.b566 when Google decides to release it. I’m excluded from Friendly Faces, but will check other app areas for anomalies.
OG 1.0.84 loaded fine. Motion tagging bounding box change looks good so far.
1 Like
App loaded fine on iOS, will test with that soon.
Waiting for the App to be available for Android, as @Seapup stated.
Firmware loaded successfully on the OG Cam. However, to be clear, this is only for the OG Standard as I did not get the update for my OG Telephoto.
Will start testing soon
1 Like
App loaded fine. Cannot comment on Friendly faces says “opps this feature not available in your area”
Wyze splash screen says “Never Wonder”, but I do wonder…what is the exact law that is preventing me from using Friendly faces? Couldn’t we have the opps screen reference the ordnance or law? Law is how it is interpreted… How is it possible that our local police can use fixed camera license plate readers all over town for tracking purposes when I’m unable to make my house more secure or smarter?
Just got the app on Android. Testing so far has not yielded any issues. Both iOS and Android are functioning well.
will continue basic testing today
1 Like
I have 3 OG cameras that had the v1.0.82 DZ issue OG Firmware 1.0.82 - No release notes and breaks detection zone? - Cameras - Wyze Forum.
All 3 cameras were updated by Wyze techs to v1.0.83 with fix “the camera will only draw bounding boxes around motion inside the motion detection zone”.
I and others have had no issues after this update.
I signed up for Beta and have installed v1.0.84β on 2 of 3 OG cameras.
However, for me the DZ issue appeared on windy days with tree branches moving outside the DZ and based on LR forecast I will not see these conditions until Sept 26.
Confirming, no love for my OG-Tele cameras 
Still 1.0.80
Yep same here. A bit odd as in the past when one got an update the other got one very soon after. Maybe the issues with 1.0.82 DZ made them put the OGT on hold and it will go directly to 1.0.84.
I previously got tags person and friendly faces name, motion and 12s recording length from my doorbel pro in events tab but as of today 09-17-2024 with v3.1.5 (b566) ALL I get is tags person (No friendly faces name), motion, and recording time of 12s. All friendly faces categories ARE selected as well as motion (but not AI Events only - as only motion or Ai Events can be selected) on my doorbell pro cam (which has current firmware updates applied - up to date). Why is it not display FF info in events or in FF in the nane (no video is shown here). ALSO HOW can you in Recognized entry select a category in FF? I don’t want it to unlock when others pass or stop by my door! ( I LIVE in an APARTMENT building)
Help!
[Mod Note]: Your post was merged to the associated Beta topic for better visibility to Wyze.
App 3.1.5 b566
Android 14
Samsung S21 ultra
Been off line to forums due to an Auth2 error that support is unable to fix. I believe I used to be ronl1213, am now ronl4625.
Updated to b566 3 days ago. This is the first 3.x that I consider leaving on my phone.
-
It is reliable. It does not seem to matter if my cameras are grouped or un-grouped. I have 9 cameras, 1st one paints the screen in 3-4 seconds, subsequent cameras appear in 3-4 seconds as I scroll down the list.
-
The bouncing balls and constant “Loading Live view” appear to be resolved. Yes, every so often I do get a stuck “bouncing ball” but if I scroll past it and back it recovers. I can live with that. I have had one -5 error on 3 days.
-
With prior releases I would have to do a “force stop” anywhere from 1-3 times a day. Not acceptable. I have been on b566 for at least 3 days and have not had to do a force stop. Once a month is acceptable in my book. We will see.
If this were to be a “Release Candidate” I would agree.
To the developers and engineers, I have been following the 3x release since it’s earliest days. Your improvements are working. Good job.
In a separate post I plan to explain why I think this release for Android is “good” but why I think the IOS release is “great”.
Is it just my imagination or is no one on the beta forum. Maybe 1 or 2 entries a day. Maybe everyone is getting the auth2 error when trying to post.
1 Like
Maybe no one has anything to report? 
4 Likes
IANAL, I think its various States privacy laws. Recording a perp is one thing I suppose, recording others faces without their knowledge is another in court.
Driving is a privilege not a constitutional right.
I turned it on previously, And turned it back off. Didn’t work that great for me. Plus the distant chance of hackers obtaining for facial recognition. It’s not for me anyhow. Yet anyhow.
If there are faces here outside after dark, 99.999, they’re not friends or family.
I hope your right 
2 Likes
@ronl4625 You old account “ronl1213” has been merged into your new account “ronl4625”.
3 Likes
Thank you
3 Likes
I am a Beta Tester but in app (or anything I have seen) I don’t see where to contact for Feedback (including beta) was this an oversite? How do we suggest/report things?
The most convenient way for beta app releases, go to Account tab > App Settings > toggle on Submit Log Button:
Toggling that option on results in a paper airplane icon displayed throughout the Wyze app. Tapping the icon starts the Submit Log process and provides better context to developers because it allows you to submit a log directly from the app’s point of issue at the time of issue occurrence.
Alternatively, for both beta and production app versions, you can submit a log by going to Account tab > Wyze Support > Submit a Log.
You can also go to your Wyze product > Settings (gear icon) > Wyze Support > Submit a Log.
-
For beta releases, after you’ve submitted a log, post the Log ID number in the associated beta release announcement topic with a brief explanation of the issue.
-
For production releases, after you’ve submitted a log, contact Wyze Customer Support to start a service ticket, give them the Log ID, and optionally post the Ticket number and Log ID number in the associated production release announcement topic with a brief explanation of the issue.
2 Likes
But what if you just wanna make a suggestion or report a problem but not sure if log will help?
Just do the same without a log. But for issues, if a developer can’t recreate your issue from your description, your issue is less likely to get fixed without a log.
For completely new ideas, search the Wishlist category and if you don’t find an existing topic that covers your idea, submit a new request: How to Use the Wishlist
2 Likes
