Riddle me this, Batman! šŸ¦‡

Okay, so this is not about a bat…

But I have an issue I can’t figure out. Once a week, a truck comes and picks up the trash in front of my house. The truck is big. An arm comes down the side of the truck and picks up the can, empties it, and sets it back down. There’s lots of motion and activity associated with this truck. Yet somehow, my V3 camera rarely captures this event for the cloud, so it doesn’t show up in my events list. The SD card does record the event just fine and I can go back and find it after the fact. Not sure why this big truck does not register as a motion event, at least, if not a vehicle. I have the camera set to detect everything that moves. The camera has no issues recording all other passenger vehicles, persons, pets, insects, etc. Just this big truck. :thinking:

I’ve attached a couple of pics and a short clip. Any ideas? I’m running Android 16 on a Pixel 8 Pro.

Do you have ā€œother motionā€ enabled? If not and it isn’t recognizing it as a vehicle, it won’t log an event.

1 Like

@dave27 Thanks. No, I don’t have Other Motion set. I suspect this is the problem, but was hoping not. It seems the truck (although large) should be detected as a vehicle. Not sure why I still get random ā€œmotionā€ alerts when a leaf drops in front of the camera or an insect flies past. But not the truck. Oh well…not a huge deal, but it makes me wonder what other events I may be missing.

2 Likes

If you’re getting ā€œother motionā€ it seems you may have that enabled? Unless those leaves/insects are tagged as something other than generic motion.

It wouldn’t surprise me if their pattern recognition doesn’t see the trash truck as a vehicle, but the green box in one of your pictures does mean it is seeing the motion.

On your SD card is it tagged on the timeline as anything?

1 Like

That really is an odd one. Your video clearly shows Motion Tagging with this apparent event ~08:17 today, but your the timeline on your Events tab shows events for 08:12 and 08:28 with nothing in between, and there’s no marker for the event on your microSD recording timeline at that time. (The screenshots and video are excellent, by the way!) I’d think that since Motion Tagging is enabled and detecting the pixel changes that you should at least have a cloud event for motion registered so that you can submit the video for Wyze’s detection engine to train it on this vehicle that it’s not properly tagging. I’m not sure why this is happening. :confused:

1 Like

I don’t have a subscription so I’m not sure, but when you have ā€œsmartā€ detections enabled does the SD card still record all motion? That might explain why it is there, but not tagged and not in the cloud. Though still doesn’t explain why bugs and leaves are being tagged.

Wonder if this is a wifi signal/upload speed issue where it is intermittent.

Here are screenshots of my settings. And I also noticed the green box detecting the truck as ā€˜something’ but not triggering a motion detection.

I also attached a screenshot of the SD card timeline, that shows no detection at 8:17 am.

Yes. I do this, and that’s what @jh006’s screenshots show. You can see the continuous green stripe and Smart Detection event markers on the microSD recording timeline in the first screenshot and ā€œVehicleā€ Smart Detection tags on the Events tab in the second.

I don’t have any Cam v3s, though I don’t think this kind of issue would be specific to this particular camera model. I’m puzzled about why this isn’t even being tagged as ā€œMotionā€ anywhere since Motion Tagging is apparently detecting the pixel changes. :confounded_face:

1 Like

OK those settings explain it, it is detecting the truck as motion but because you don’t have ā€œotherā€ enabled, it won’t tag it or notify since it isn’t being identified as a vehicle. It looks like you have continuous SD card recording but you can see it is not tagging that spot with anything, for the same reason.

My guess is when you have a leaf or bug notify you, there is a vehicle somewhere in the frame that it is identifying (the ā€œAIā€ is not smart enough to differentiate, it just knows there was motion and looks for something in the frame matching what you have enabled).

1 Like

I don’t think you can accurately make this determination based on the screenshots because of the differences between the Customize Detections screen (which these don’t show because @jh006 has Smart Detection Events selected) and the Customize Recordings screen (which is what the screenshots show). I believe that @jh006 would first have to select All Events on the Event Recording screen in order to see the Customize Detections screen with the Other Motion options.

1 Like

I only have v3 cameras and thought I would share my settings in case it is helpful. I have Event Recording set to All Motion Events so anything with pixel change (Detection Sensitivity set at 90) generates a Cloud Event recording.

I have Notifications set for Person only.

Everyday I review all Person Event videos. If I have time or am bored, I will briefly swipe through the Other Motion Event Cloud videos.

You might try these settings at least to test to see if they work for you.

Because of how you titled this thread, I wanted to share what I found at my local grocery store for one dollar.

2 Likes

Another reason I like my above settings is because sometime Cloud video is recorded but not Tagged correctly. This Cloud video below was trigger because of pixel change but NOT Tagged as Person. Could be because of the angle of view or distance. I like the fact that Cloud video at least got recorded even it it was not Tagged correctly.

1 Like

Fair enough, but I was basing my assumption on the fact that there are no other motion ā€œtagsā€ even on the SD card timeline, yet the trash truck was clearly detected by the green box.

On my cams without subscription, the two screens actually do the exact same thing (both settings take you to the same place), but I believe that may have changed at some point for subscribers.

1 Like

I think it’s been that way a long time for subscribers and has caused a lot of confusion, which I know @carverofchoice has said he’s reported to Wyze and tried to get them to fix. It can affect sound detection notifications in a similar way. It really seems like an odd way to do things, and I don’t understand why that one particular line (two if you count ā€œOther Soundsā€) is essentially hidden (yet enabled) for subscribers trying to configure Smart Detection Events.

I’m not immune to assumptions and in this case am operating with the idea that these Cam v3 settings are similar to what I see for Cam v4 since I don’t have any of the former and its UI has undergone some changes to align it more with the latter.

Yeah, that’s the part that really puzzles me. Clearly that recording is on the microSD card, but it’s not marked as event on that timeline or the Events tab. :man_shrugging:

2 Likes

Looks like the SD is set to continuous so that explains it being there. But the lack of tag makes me assume that ā€œother motionā€ is not set to tag/notify, maybe only record.

1 Like

I think this is working as intended. Once motion is detected it crosschecks if you have your ā€œSmart Detectionā€ enabled and then it will only record and tag cloud events based on your ā€œCustomize Recordingsā€. In his case, the main problem was that it’s not detecting the truck as a vehicle so it’s not being tagged AFAIK.

I remember selecting ā€œSmart Detectionā€ as a deterrent especially for my driveway cam due to constant activity in the area (flashing lights, leaves, rain, and etc) was causing a lot of notification / false positives.

1 Like

Could be. I don’t know if Cam v3 shows a different Customize Detections screen if All Events is selected instead of Smart Detection Events. My experience with Cam v4 and others is that this is what happens and that Other Motion is always selected in the TAG column, so I would still expect to see some kind of marker on the microSD card recording timeline because Motion Tagging is clearly showing in the video that some kind of motion detection has occurred even if the cloud isn’t identifying it as a vehicle. :man_shrugging:

1 Like

On second thought, why is it not tagging vehicle as there is a parked car on the right side of the road ? I think at that distance it should be able to decipher it as a vehicle. Maybe the leaves are camouflaging the truck and it’s playing tricks on Wyze’s AI system.

I think enabling Motion Tagging in Cam V3 situation is just those showing those boxes. I don’t think it has any impact on the tagging on the timeline.

1 Like

First…to everyone, Merry Christmas! Hope you and yours have a day of love and laughter!

:clinking_glasses::snowflake::wrapped_gift::christmas_tree::snowman::santa_claus::blush:

Second…that Batman hot wheel is FIRE! :fire:

Third, many thanks for all of your responses in this thread. I have learned a lot and see now that my settings are set up to detect vehicles, but not all motion. The garbage truck is not being detected as a vehicle, so not flagged as an ā€˜event’ via my smart detection settings. But my 24/7 recordings do capture event to SD card.

The reason other vehicles in view are not detected is because of my detection zone settings. I have blocked the areas where neighboring cars park regularly. Otherwise, I’d have too many notifications event recordings to go through every day. Check out the screenshot. The cars are outside today because we’re using the garage for temp storage. Lots of family coming over today).

2 Likes

I think that’s right. I wouldn’t expect Motion Tagging to be responsible for or cause the marking/tagging of motion events in the cloud or on the microSD recording timeline, but because Motion Tagging can be used as an indicator of motion detection—the camera is detecting enough pixel changes to draw a green box and indicate that motion has been detected—it acts like a concurrent consequence of detection and (I think) lets the user know that something should’ve been marked/tagged at that time.

1 Like