I guess I didn’t realize there were so many variables to tweak. It’s a bit different than just point and shoot.
BTW, when doing all of this testing, I’ve run across a couple of …call them “annoyances” rather than “issues”… that probably could use an enhancement request. Do I simply make up a new ticket with “Enhancement Request” in it’s title?
#1 Example: there are quite a few recordings in the Event list, let’s say 6 recordings in each hour and there are 6 hours of recordings (total = 36 recordings in the list). I play one from hour 3 (the middle of the list). Once I’ve played it, when I arrow back to the list it drops me at the most recent recording (the top of the list). So I have to scroll back down to the middle in order to play my next recording. Expected Result would be to drop me back to the last place I was at in the list (in this case drop me back in the middle and highlight the one that I just played).
#2) Using the example above, I have done a Select All and Deleted all of the recordings. Minutes later I hear the notification that a new recording has been made. In order to see any of the new recordings from the same cameras, I must click on the (x Cameras) button, then I have to click on [Show results] button. Can a single (Refresh) button be placed where the (Person) and (Motion) are located now since those 2 buttons bring back exactly the same list? Expectations for those 2 buttons would be clicking on (Person) only brings back Persons and (Motion) only brings back Motions, so I haven’t figured out exactly what the difference between those 2 buttons is supposed to do.
And “yes”, before I retired, I was Quality Control Mgr for a software company here in Dallas. Old Habits you know!
Hmm, I am debating whether those count as feature requests (which would go in the “wishlist” area of the forum (after searching to make sure a similar wishlist for that functionality doesn’t already exist):
Or if those should actually be considered bugs. I can see arguments both ways. If it is considered a bug, then it would be best to report it in the next “Fix It Friday” on April 1st when Wyze employees will actually look over all the reported bugs (though they’ll only publish an official response on the highest rated bugs). Could be worth doing both.
Searching wishlist and roadmap didn’t find either issues, so I added them to wishlist. I figured the moderators could turn them into bugs if they didn’t belong in wishlist.
Does Wyze have a Knowledge Base repository? The information I’ve gleaned from this Detection Zone and Sensitivity testing should be in a KB instead of merely hiding inside a ticket, don’t ya think? Perhaps not. I’ve seen others ask similar Detection Zone questions with very little ultimate success, or if they did resolve it was never added to their tickets.
Well, CarverOfChoice, I thank you for your insights and direction in t-shooting this wacky issue. I believe I can resolve my different scenarios now quite proficiently. I’ve enjoyed messing around with the different experiments as well. Cheers!
