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.