I have an Automation that turns on several outdoor cameras at 21:00 each night, and every night they trigger a motion event at 21:00. They should have logic that disables motion detection for several seconds after the cameras power on to allow the IR lamps and image to stabalize.
Welcome to the Forum, @SecurityPA!
I get what you’re asking, and I think it could be a good idea as an optional feature. This seems like a potentially relevant Wishlist topic:
You can visit that to share your ideas and click/tap the Vote button above the initial post if you’re interested.
Regarding a solution to your immediate problem, I’m wondering if you’re getting unwanted notifications at 21:00 or if you just don’t want to have these unwanted camera initialization events show up in your events timelines. I think I’d consider adding two more Schedule-type Automations for these:
- Turn on notifications (or motion detections or whatever it is you’re trying to reduce) for the cameras in question at 21:01. The options for Action that you have available may depend upon the camera model you’re using. Obviously, if you want the notifications/detections/whatever to start at 21:00, then you could do this and adjust your existing automation to initiate at 20:59.
- Whatever you turned on in Automation #1, turn these off 1 minute before the scheduled automation that turns your cameras off (presumably you’re already doing this with an Automation since you said you’re using an Automation to turn them on at the same time every night).
Thanks for the suggestion. I do not want the bogus events showing up in the timeline.
I separated enabling motion detection, turning on the camera, and turning on notifications into separate schedules, and I still get bogus events being triggered when motion detection is enabled. I tried various orders and combinations and wasted quite a bit of time. I like the DLink option. In my area we also have numerous winged things the like to fly past the camers.
Yeah, that’s a common problem even with cameras that are using IR, and even though I’m not using night vision mode with my cameras, I frequently see motion events from insects crawling across or flying in front of the doorbell camera’s lens. It’s real motion, though, and a real event, so I don’t consider it “bogus”…it’s just not something I really need to be notified about, but the camera doesn’t know the difference.
I’ve read of some users installing separate IR blasters to provide illumination at night that’s away from the camera lens itself in order to minimize attracting insects to the camera’s built-in illumination source, but I don’t have any experience with that. Aside from the Video Doorbell v2, all of my other current Wyze cameras are mounted indoors.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.