So, I have an event to turn the lights on when there is motion and the illuminance is a certain %. I have another event to dim the lights, if they are on, to 50% when the TV is on. I have another event to Turn the lights off when there is no motion and the TV isn't on. However, I am having trouble with once the TV is turned off, the lights stay at 50% and they don't turn off once there isn't motion in the room. Can someone help with this? I want the lights to go back to 100% once the TV is turned off and then they should turn off when there isn't motion.
Announcement
Collapse
No announcement yet.
Need help with an Event for Lights to turn off with no motion after TV is OFF
Collapse
X
-
Originally posted by pcgirl65 View PostSo, I have an event to turn the lights on when there is motion and the illuminance is a certain %. I have another event to dim the lights, if they are on, to 50% when the TV is on. I have another event to Turn the lights off when there is no motion and the TV isn't on. However, I am having trouble with once the TV is turned off, the lights stay at 50% and they don't turn off once there isn't motion in the room. Can someone help with this? I want the lights to go back to 100% once the TV is turned off and then they should turn off when there isn't motion.
One fix would be to change the last two Conditions to look for the lights to be "Not Equal to" Off. This would turn the lights Off as soon as the TV is Off and if there has been No Motion for 2 minutes. That is not what you wanted, so the next best thing is to leave that Event as is and create another Event. This Event will run when the TV is turned Off and if both lights are at some level between Off and On.
The result is that this Event will run as soon as the wattage is set to less than 10 as long as the lights are at your dim level. Of course your
"Living Room Lights Off Event will run immediately after the two lights are set to On, if there has been no motion for at least 2 minutes, turning both lights Off.
You could make the whole thing a little more predictable with a Virtual Device for room occupancy. I use a Virtual Device for room occupancy as well as one for the TV. I will post examples of that next.
HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
-
Here are my Events to control the TV virtual Device
And here are my Living Room Occupancy Events, since my Kitchen is more or less attached to the Living Room, I look at both sensors. In our house we use a rather liberal timeout of 15 minutes, before an area is deemed Vacant. You could change this to 2 minutes as in your examples, but for us that timing is way too tight. We have no desire to have lights go out immediately after we leave a room, usually we will turn them off manually (via Remote of HS Switch Scene). We also have no desire for the lights to go off on us if we are in the room but not moving sufficiently to trigger motion. The 15 minute timeout works great, still cleaning up for us if we forget to turn the lights Off but not leaving us in the dark when we are not sufficiently active.
Then you can use these Virtual Devices in your Events. You could add Conditions looking at the lights in the first Event to prevent the lights from going to 50% unless they are already On, or you could also look at room occupancy. The Virtual Devices give you so much more flexibility and predictability.
HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
Also, do Events not run on a True False reasoning? Like for example, if I have a light go on between sunrise and 11:00pm, would it not turn the light off after 11:00pm because the Event isn't true anymore? Coming from Hubitat where they use Rule Machine. This is how it works. So in this instance, if the rule isn't True, then the light shouldn't be on and it will turn it off.
Comment
-
Originally posted by pcgirl65 View PostAlso, do Events not run on a True False reasoning? Like for example, if I have a light go on between sunrise and 11:00pm, would it not turn the light off after 11:00pm because the Event isn't true anymore? Coming from Hubitat where they use Rule Machine. This is how it works. So in this instance, if the rule isn't True, then the light shouldn't be on and it will turn it off.
HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
Originally posted by pcgirl65 View PostWow! I am having a hard time understanding using virtual devices instead of just using the actual triggers that you have set in events to set the virtual devices?
:- Motion detected
- Motion ended, but not long enough ago to deem the room vacant
- Motion ended long enough ago to determine the room is vacant
HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
So this seemed to be working well until last night. For some reason the lights were on at 2:20 am. It looks like they didn't go off after there was motion detected at around 9:17pm. The TV was off all night and nobody was up after this time. Doesn't seem to be any indication of the motion being detected as off in the logs.
​ ​
Comment
-
I misunderstood. Then the first Event should have turned them Off. If both lights were on (not at some dim level) and if the TV was consuming less than 10 watts, the event should have run and turned them off. There are several things that could cause that event to not run. 1) if either light was not On or 2) the wattage device is no longer updating when the TV is Off. I suspect the latter. Most energy devices will continually update and would trigger that event, but yours may not change at all when the TV is off. Later this morning, when I am at my computer I will create a better event that can account for that as well.
You can identify if that is the problem by looking at the value and time stamp on the TV wattage device. If it stops being updated or if the value remains constant, it will not trigger the Event.HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
-
It looks like the wattage is updating a lot. Seems to update about every 2 minutes and it is always changing slightly. See in the logs.
I actually went in yesterday and changed some of the parameters so that it wouldn't update so much. Don't know if the constant updating puts a strain on the system.
Comment
-
OK, that rules out the Trigger. It is behaving as I expect it to and will be a reliable and repeated trigger. Is there a possibility that one of the two lights was not On? The Event is structured such that both must be On. If either is less than On (Off or dimmed) the Event won’t run. We can change the structure of the Event to accommodate for that. Do you have the Easy Trigger plug-in-in?
As far as a strain on the system, IMO every 120 seconds is ideal. It is frequent enough to be useful, but not so frequent as to significantly impact the Z-Wave network.HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon
Comment
Comment