Repeated Package Notifications - Every Time a Car Goes By

Hi,

Adding some color to this issue. 1st package recording/notification works fine. I’ve limited the trigger area and sensitivity, and the tagging helps with what is triggering.

But then the repeat notifications are from any motion NOT limited to the trigger area. So, every time a car or pedestrian goes by.

I can’t find a setting that seems to solve.

Can help?

A possible explanation is that something within the detection zone triggered a search of the whole frame, which then found the package and the passing car; not that the passing car triggered the package tag.

True, and I’ve cut the detection zone way down to be sure that no tree shadows, wind driven items, etc are not in the frame. Checked each notification too.

It more acts like the detection zone is not working on the repeats.

A few more details. This porch is a direct sun exposure facing west. So far, all examples are the afternoon, full sunlight, sun in the west.

Sensitivity is turned down to 3, and tagging is on to identify the trigger.

A couple of examples:

A white van is going across the upper frame, crossing thru sunlight and tree shadows. Way outside the detection zone.

As the video starts there’s a vehicle on the street moving across on the upper frame, again, way outside the detection area. As the vehicle leaves camera view the camera exposure changes, the top step darkens, and a detection tag shows on the darkening spot.

Welcome to the Forum, @KenYz! :wave:

Based on what you’ve written, I think you’re doing the right things so far. I wonder if a couple of other things might help to get your issue some visibility:

  1. You haven’t mentioned what camera you’re using. I don’t know if that’s a contributing factor to this particular problem or not, but adding that detail can be helpful (especially if you can add that tag to your topic), as it can be a clue to other users of the same product, and that can attract users who have hands-on experience with that device for additional help.
  2. You mentioned that “tagging is on to identify the trigger”, but I’m not sure if you mean that you have a Motion Tagging option enabled—which draws green rectangles on the video to indicate where the camera interpreted movement—or that you’ve selected “Package” on something like a Customize Detections or Customize Recordings screen—which tags or labels an event with the type of detection that was triggered. If it’s the former and you’re using Motion Tagging plus a Detection Zone, then sometimes posting screenshots of how you have your Detection Zone set and an example of a captured event showing a green box can be helpful in getting some additional eyes to suggest possible improvements to your settings.

Are you able to re-aim your camera so that the unwanted motion is out of view? I like my Porch camera to also see my walkway and driveway. I only have Person detection so I do not get many Notification. I could easily re-aim if needed.

Thanks,

  1. It’s a Duo Cam Doorbell
  2. Yes, it’s Motion Tagging that is meant. I can show detection zone when it’s daylight.

And let me clarify the problem. The first package notification is accurate. A person has come to the porch and placed a package. Then, if a car goes by, there is another, redundant package notification, even though the car is way outside the detection area. Nothing else has happened, and the package is still on the porch. Seems like a bug to me.

One package event had 6 repeated notifications related to cars. And a clue, but not definitive: just 1 notification that had any Motion Tagging. That notification did not show any actual motion, just changing exposure before/after a car went by. This changing exposure that was motion tagged was the top step, and within the detection area. Then, this sensitivity and additional notifying seems to stop after a time, or maybe a day change, and the redundant notifications stop.

And thanks for the suggestion on Recording Preferences. I will try eliminating cars as a Smart Motion.

1 Like

Sorry for not answering directly. Re-aiming is pretty limited because it’s a doorbell camera. I also positioned it to be out of direct sunlight as much as possible, so that’s a limiter too.

1 Like

That’s helpful. Thanks for providing that. :+1:

What firmware version is installed? There were a lot of complaints in the Forum shortly after Duo Cam Doorbell launched because it was hammering users with package detection notifications for things like doormats. (You can find those topics if you search for them.) Wyze has issued a number of firmware updates for that product since it was released, and I believe some of those have specifically addressed the package notifications issue. For instance, the update from January of this year mentions “Improved motion filtering algorithm to avoid false detections caused by color changes and device sleep transitions” in the Release Notes, and I wonder if that’s the kind of thing related to the experience you’re describing.

Thank, yes firmware is up to date.

Were these false detections for 1st time notifications, or after the 1st? Sounds like the first. This issue I’m having is for notifications after the 1st one. Don’t need another, and would choose reminders if I did.

And I’m drumming now, I know, but there are no other repeat notifications when there are no cars, which are way outside the detection zone I’ve selected. I also don’t get false detections when cars go by and there is no package on the porch, so looks like the detection zone is working.

adding setup images

Nope, the latter, at least in this topic that came to mind:

The images you shared are helpful. Thanks! :+1:

I think the Detection Zone looks pretty good, but I wonder if something in the excluded area is still causing enough pixel change that the camera is interpreting that within the zone you set. What I mean is that when you have Motion Tagging enabled (as you do), if you watch events often you’ll see the green Motion Tagging box move and shrink and grow moment to moment as it follows a target within the video, and sometimes an edge or corner of the box where movement is being interpreted can encroach upon the Detection Zone, indicating that it triggered the event. A couple of other things to try:

  1. Share some event captures that show the green Motion Tagging box so that they can be compared to what you’ve set for your Detection Zone.
  2. Enlarge your exclusion (greyed) area a little to give your Detection Zone more of a buffer and see if that reduces the notifications you’re seeing while still alerting you for things that you want to be notified about.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.