I have a V3 mounted above my EV, and have a detection zone for just the dash of the car, specifically where the orange lights are flashing on the dash in the picture below.
I then created an Automation to flash a Wyze Light Strip at my Desk in the house when it see’s motion on this camera.
I thought the automation would only trigger from motion in the V3’s detection zone. That doesn’t appear to be the case, as the automaton is firing when it sees any motion outside of this small detection zone
Do Automations ignore Detection Zones on a v3 and I assume all Wyze Cameras?
I don’t have a v3 but my OG and v4 both turn on the spotlight only when motion is within the detection zone (and I use an automation for that, not the automatic spotlight feature).
Turn on motion tagging (green box) and see what exactly is triggering it, and whether the green box goes into the detection zone, which can trigger even though the main motion was just outside the zone.
Or maybe the v3 works differently, but I don’t see why it would.
There is some debate about whether the “reset services” under settings actually does anything for non cam plus subscribers (not sure if you are or not) but you could try that too.
While I was on Cam Unlimited my detection zones worked perfectly on both V3 and V4. Now that I have the V3’s on Cam Lite and the V4 with no subscription, both models seems to ignore the detection zone. The V4 is the worst, and that is understandable as it detects all motion without subscription. Reset services doesn’t do anything. Reducing sensitivity seems to help somewhat.
No, not at all. God forbid, I don’t want to add to your conspiracy list
I think it was just a coincidence, today cameras behave much better. The V4 is in a spot where it s sees lots of light changes , that is the reason it goes nuts.
That’s my main complaint about my v4, in the same spot where there used to be an OG, headlights washing through the DZ trigger it and rarely did with the OG. At some point they released a firmware for the OG that made it ignore lighting changes and it worked really well. Why they wouldn’t have just automatically included that same code/logic in the v4 is a bit mystifying.
Obviously I’ve toyed with sensitivity and the DZ but there really is no way to stop it from triggering on headlights without also stopping it from triggering on stuff I want tagged. Luckily it is mostly just when my outdoor lights turn off at 1AM until sunrise, when traffic is pretty light, so I’ve learned to live with it.
Right where I have circled, there is a solar light that triggers an event every day no matter how far down I go in excluding the area. Also sometimes when people walk on the sidewalk (red rectangle) it triggers events. Never had the issue when I was on Cam Unlimited which is bizarre.
Yeah the light I understand, but the sidewalk makes no sense. The DZ on my v4 seems to be razor sharp and quite accurate for people walking on the sidewalk which is just barely outside of my DZ. Though it is also at a 90 degree angle to the sidewalk, maybe that somehow comes in to play.
Sounds more like something somehow got stuck with your various subscription states. Or maybe you had smart detections with cam unlimited and that was causing it to be more accurate? But since I’ve never had any subscription and mine is accurate, that doesn’t make sense either.
Maybe just need to totally delete the cam, factory reset it, and name it slightly different when you re-add it? Some corrupted setting in the cloud or in the cam’s memory or lingering subscription stuff?
Nah, mine adheres to the DZ even during the cooldown period. I’ve got the green box enabled and when going in to watch an event video right after it happens, people will be walking by on the sidewalk and cars going by in the excluded zone, no green box. But one of those people walking a dog that walks through the DZ will trigger a green box, but no event since it is in the cooldown period.
I don’t have an OG, but that sounds like the behavior I’m looking for where an Automation will trigger only from motion in the detection zone.
I have turned on motion tagging and will continue my experiment.
I’ve moved a v2, a v3 and a v4 to the garage for my experiment. All three are pointed at the location where the dash of the car has a dual flashing orange light that I want to monitor when parked. (the dual flashing orange lights on the dash indicate that my plugged in EV is no longer receiving power from the L1 EV Charger)
I’ve an automation setup to flash a Wyze Strip Light at my desk (v4 = red, v3 = yellow, v2 = green), when the respective camera sees motion in the one single box I have for the detection zone.
I am a subscriber to Cam Unlimited, so I did the ‘reset services’ on the v2, v3 & v4.
Hopefully there I can get the v2, v3 and/or v4 to trigger an automation based solely an motion in that small detection zone comprising one box in that grid.
It should work fine on the v4, I have one and my detection zone is very accurate and behaves as expected. I do not have a subscription but that should not matter.
