That’s probably right. (I’ve ridden in cars where the stereo balance is nearly fully left or right and the equalizer is set to “muddy” and the drivers are unaware and untroubled.) So don’t use them for anything “important” until Wyze claims they can be, I guess.
Kind of like they hid the slider and left it at 50 before they hid it? It seems the easy button would be to slide it to 100 so the record on event always records motion.
Because of the need for confirming internally, I’m not going to give an immediate answer on this. I’m going to talk with the devs and make sure that all of my information is completely accurate first before I risk muddying the waters further. Thanks for bringing me in!
Thanks, Gwendolyn, I look forward to your findings!
You’re welcome! Thank you for your patience. Here’s the information verified by the dev team that I received:
V1 & V2: Record on event will be affected by motion detection zone but NOT by motion sensitivity.
Pan: Record on event will NOT be affected by either motion detection zone or motion sensitivity.
If you have an inconsistency between microSD card recording and event recording, please check the detection settings. If that doesn’t fix the problem, please send us a firmware log through the Wyze app and include info for the event video (date/time/time zone).
In V2.2, we will change it so Record on event will be affected by both motion detection zone and motion sensitivity.
Thanks, Gwendolyn! Incidentally, both my active V2 cams (w/SD installed) updated to the new firmware yesterday with no problem.
Here’s a little table from events early this morning to demonstrate explicitly what we’re talking about.
H - Headlights
P - People
Gr - Green motion
Motion tagging - ON
-Detect motion - ON
-Detect sound - OFF
-Send push notification - ON
Motion detection settings
-Sensitivity - 50 - ON
Detection Zone - ON - defined
Sound detection settings
-Sensitivity - 50 - OFF
-Record to SD card - ON
-Record on event
Night vision mode - OFF
Record sound - OFF
Camera is aimed outdoors through a window. Hope this helps. -peep
Friends Don't Waste Friends' Time
Interesting… Thank you, peepeep! This is very helpful. Happy to hear that your upgrades went through well! And your table is rockin’. Would you be up for collecting a few more instances of this over the next couple of days and then making a support ticket so I can get the devs to take a look?
Okay, I have to ask. Is this peep-eep, pee-peep, or peep-peep? There has been a bit of a debate.
Been saying pee-peep in my head so… just don’t call me late to dinner!
I’ll trade ya! If you can get those stubborn dev omitters to answer these questions, I’ll go the next step. (I’ve actually already done it - I’ll release it!)
- Is there a single motion detection system common to both cloud clips and SD events? and if so
- Is SD event detection sensitivity currently fixed at a common “50” (and if not, what’s the #?)
- Did anything change in the most recent firmware upgrade that would affect detection for SD events or cloud clips?
Gotta say, browsing the SD card playback events today was absolutely silky - bumping back and forth on the timeline with the arrow keys, moving around a chunk of playback with tap/hold/move, etc. No glitching, no WTF-ing, a completely new experience. It’s hard to believe it’s just an anomalous gift from the heavens, but I suppose that’s possible…
Hey @Overwatch, got any comments or suggestions on the dev response, etc?
Hah! I’m glad I didn’t bet on this one since I would have lost. I’ll let the others know the correct pronunciation.
I’ll see what I can do about getting your questions answered. In the meantime, I’m happy to hear that your Playback experience has improved!
I have your answers!
- Yes, it is a single motion detection system.
- No, the number is fixed to 100 so that the likelihood of missing desired events is decreased.
- No, nothing changed in the most recent firmware upgrade that would affect the discussion.
Interesting about SD event Motion Detection Sensitivity being fixed at 100. The results below are with in-app Sensitivity for Cloud Clips set to 50. Check lines 18, 25 and 27 - no SD event to match the cloud clip. Hmmm…
Thanks! I do what I can. -takes a bow-
Thank you for the table! Could you please send in an app/firmware log through the Help & Support section of Account in the Wyze app and include the table (or an image of it) as an attachment along with your time zone and the dates that you were making this table? I’d love to get the devs to look at it.
I appreciate your diligence in producing that chart. If the SD Event recording is set at 100 and not 50, then the lack of SD recording must be a bug instead of a bad design issue. With all the huffing and puffing about “what if they steal my camera”, I think this is a much bigger issue. In your larger chart, you have three events without an SD recording. I think we should also point out the possibility that during cool down, an SD record-able motion didn’t get recorded, but the only way to prove that would be to have an additional camera on continuous and watch each and every cool down segment for unrecorded events. I’m sure this happens more than stolen cameras. In a six hour window, you had three missing recordings. Three out of 25. That’s a 12% failure rate. Roughly, one in ten events don’t get recorded in event only mode. I would say that sounds consistent with my back of the envelope analysis. That’s a big deal and why I use continuous recording.
As for @speadie 's comment
It’s not encouraging that Wyze chooses to dumb down some great functionality instead of coming up with more intuitive ways to handle it.
Established last night: Wyze Ticket 183959. I referenced you and this thread in the text, just so ya know…
Good points about bug vs design flaw and a possible correlation with cool down.
And this made me laugh: another camera as opposed to “unflagging personal attention.” What happened to that awesome omniscience I used to have? How could I not’a thunk it?
An additional camera on continuous to watch the cool down segments for unrecorded events is a great idea.
I normally run at 100 in-app sensitivity setting which might suggest that if I set it back
from 50 to 100 to 100 from 50 there would be MORE unmatched cloud clips.
I have two cameras, one outdoors under an eave, one indoors aimed out a window. The original ticket was focused primarily on the outdoor camera (though I was experiencing inconsistencies with both) because it was trained on an area of practical concern: repeated mischief with a big cactus we have. The indoor camera was of less practical, more experimental, use.
I used the indoor camera for the testing I’ve documented with the table because it’s being used as Wyze designed/approved: indoors.
The outdoor camera, set at 100 sensitivity, gives me the results I’m after: very subtle movement within the detection zone generates a cloud clip/alert (but alas, not a matching SD event.) These subtle cloud clip events are consistently NOT green motion tagged. The SD event failure percentage here would be much higher if logged.
I tried continuous SD recording but didn’t continue it because:
- I didn’t want to deal with card-bricking/troubleshooting/replacement
- I preferred the indexed SD feature.
- I’m an idiot
I have found that plus ca change the more I am an idiot. But that’s a whole nuther story, eh?
C’est la vie.
What you say here (esp, These are busy people and they just don’t have time to screw around with issues…)
is the reason I haven’t shared Wyzecams with my extended family. Not-ready-for-prime-time without a significant dose of geek-freakery (not included.)
I sent your ticket over to the dev side. And we’ll work on improving the product.
We understand your reservations and apologize for the trouble.
I would think the opposite. IF, the SD recording and the cloud events are independent, a detection setting of 50 should, in theory, produce fewer cloud events as a base to look for comparable SD recordings. The number of SD recordings should remain the same, assuming the same number of motions. IOW, if you had two cameras side by side, one detection setting of 50 and one at 100, they both should have the same SD recordings. The sensitivity setting of the 50 level device should, again in theory, have fewer cloud events than the 100 setting. Also, people may be setting their sensitivity down in an attempt to miss some insect 2" from the lens and miss the dude breaking into their car 20 yards away. Being able to watch months of event only recording is pretty worthless if you miss the one event from three days ago. I just know that here the camera on event only would not have caught their approach because it was in the previous minute and if it hadn’t been for my motion light, might not have caught it at all.
We have Nest cameras and Ring cameras in our neighborhood watch and anytime we’ve needed to view something captured, it hasn’t been there. I don’t know if it’s the angle or event only type setting, but whatever it is, they’ve yet to prove their worth.
I’m impressed with Wyze’ enthusiasm for direct, informed, public criticism. It makes claims and backs them up. Well done.
I think we’re on the same page. Edited for clarity:
The “previous minute approach” is an event-only vulnerability, indeed.
Good to know about the Nest & Ring cams also being flawed. I have no experience with them.