I have a Cam V3 in the garage with a rule to turn ON the Garage lights when “motion” is detected and to keep the lights on for 10 Minutes. But this is not working right.
As backup there is a Wall Sensor with a similar rule to turn ON the Garage lights when “motion” is detected and to keep the lights on for 10 Minutes.
See attached video, where I enter the garage → 3 secs later the camera sees me and turn ON the lights, but then 5 sec later the lights go out. There is NO specific rule to turn the lights off, They should turn OFF after 10 minutes.
All bulbs (V2) + Cam V3 + Wall Sensor V2 are up to date firmware wise.
Any ideas why this might be happening ?
I wish the app had some logs so we could try and debug this.
Looks like you need to adjust your rules. In both cases, you have Turn on and Turn on For, Remove the Turn On as that will conflict with the Turn on For process.
Another option, is to setup 2 rules: Rule one is to turn on the lights when Motion is Detected: Turn On Rule
Rule 2 will trigger when No Motion is seen for 10 minutes. Then Turn off the lights. This will allow your lights to stay on when motion is detected. then when you leave the Garage and motion has stopped for 10 minutes, the lights will go ot…
When trigger ends, inverse action automatically executes. The undesired inverse action of “Turn on” is turning lights off when motion ends which is why you need to remove “Turn on” from both rules as spamoni wrote. You need only “Set brightness…” and “Turn on for…” as actions. “Turn on for” has no inverse action as it is absolute. Also, just FYI… the order of execution of each action within a rule is not guaranteed.
Thanks spamoni and Seapup.
I have removed the “Turn On” and left only the “Turn On for”.
I will test it for a few days.
I wish the app would not allow for this conflicting rule “Turn On” + “Turn On For”.
You can also remove the brightness line item also. If you only ever have the brightness at 100, then no need to tell it to turn on to 100 everytime as this setting is remembered.
Tried again this morning and the light turned ON only for 26 secs.
Rules were modified yesterday (see attached image with new rules).
See attached video; it shows the light goes out at sec 26 while I was still in the garage and the camera was “seeing” me.
Hmmm… my son was just in the garage I saw him on the camera.
He got in his car and left.
The garage lights stayed ON for 10 minutes.
It’s like it has a mind of its own…I mean is NOT consistent at all.
Can you post a screenshot of what your automation history shows? Make sure to click the arrow I circled so that it opens up that menu and shows the different actions and their results. Please show the time. From the event above and other ones that might be relevant. Thanks
An issue exists where specifying “Turn on for X” does not result in a log entry when the turn off action occurs. I just tested this and the issue is still present… no log entry.
I just tested your automations and you are correct. There is a bug where the “turn on for X time” value is completely unpredictable and unreliable. Sometimes turn off occurs when motion is no longer detected, sometimes it’s just a random time less than the specified time, and sometimes it actually turns off at the specified time.
Rather than debug this issue for Wyze (I don’t have time today), just do what most of us do by default… don’t specify “turn on for X time”. Just use “Turn on” and create a separate automation trigger for turning off.
Edit both of your automations and change (uncheck) the action “Turn on for 10 minutes” to simple “Turn on”.
Create one new Automation Device Trigger to cover turning off for both of your Turn On automations. Set trigger to your bulb (or bulb group) with “has been on for 10 minutes” and action to “Turn off”. Example:
Doing your automation this way will result in light on as long as there is motion from either or both motion sources as motion resets the “Turn off” trigger’s timer. When no motion from either source for 10 minutes, “Turn off” trigger executes and turns off your light.
Thanks everyone.
Looking at the history as Omgitstony suggested, it seems this is a timing issue.
a) My wall sensor V2 detected motion (although nobody was there) at 6:24 am and turned ON the lights (this was a false positive detection, but that is not the point here). See red line on attached picture. This started this sensor’s 10 mins timer.
b) I went into the garage at 6:34 am and the V3 Cam detected me (see lines Orange and light-blue), not sure why it shows twice on the history. I don’t recall but the garage lights were probably ON when I entered the garage, due to the false detection above.
c) It just so happened that at 6:34 am the first timer (form the wall sensor) was jus about to elapse thus turning off the lights. (see brown line)
If you have a SD card in the camera that is set to continuous recording, you could review the footage to see what happened and if the lights did turn on at 6:24.
In other news. A+++ on the visual aids! Very nice!
Thanks Seapup,
I tried adding a new Automation device Trigger to turn the lights off with “Has been on for” option, but it doesn’t allow to select a “group” as the device, only individual lights. Having 3 lights on this garage group, then would need 3 new rules.
I would never figure out that automation stuff. I just have a 360 degree motion sensing light socket on the garage ceiling with an LED bulb. It can sense motion at 20 feet, and turns off automatically after 5 min if no motion is detected.
Not sure but with the camera and a sensor both doing the same thing turning on the lights for 10 minutes maybe one is turning the lights on and when the other activates it is turning them off, try disabling one of them and see if the light still turns off after the 5 sec.
Thanks @Seapup.
I modified the rules as suggested (not using Turn for X minutes and using one of the bulbs to turn off the group after CAM hasn’t detected movement" did the trick. I have tested this for several days and it is working fine.
