@bravenel I believe I located a bug in Room Lighting... but Here's my rule, and here's the logs...
Here's my rule... ** Note the status is Active **
Here's the log of the multisensor in that room...
Here's the logs for the Room Lighting rule...
As you can see, I have hub mesh running with the rule running on my zigbee hub while my multisensor is on my zwave hub in hub mesh. the zwave multisensor is not being detected by Room Lighting as being inactive, even though on the zwave hub where it resides it says it's inactive and on the zigbee hub the hub mesh device is showing it as inactive, but Room Lighting indicates and believes it's still active.
So in this scenario, the light comes on, but never shuts off until I manually shut it off.
I don't see any events logged for the "Hall Bathroom MultiSensor on HE Z-Wave" becoming inactive. So the app thinks it's active, and you have that as a condition under which not to turn off. That in and of itself is what you'd expect as to Room Lights behavior, right?
So this isn't a Room Lights bug, but something to do with that device or Hub Mesh. Does Room Lights have an active subscription to that device? Does it ever log any events from it?
So, Room Lights doesn't subscribe to a device that is used as a Condition to Limit Off. Instead, what it does is grab the device's currentMotion state at the time of that test. I'm going to test this to see if there is some issue or not.
Ok, here's the log of the meshed multisensor on the zigbee hub.
To answer your question, yes, if the multisensor is active, don't turn off the vanity light. If both motion sensors are inactive, turn off the vanity light. If the door contact sensor is closed, keep the light on until it's changed closed and all motion activity is inactive.
That shows that at 11:55, when Room Lights went to turn off, the sensor was still active. So Room Lights did what it was supposed to do, and not turn off.
Ok, but if you look at the rule as I captured it, both motion sensors are "inactive", so the vanity light should be off, but instead it's active and turned on. RL logs aren't picking up that the mesh device is going inactive, even though the logs for said device on the zigbee hub clearly show it going inactive.
It went inactive later. It was active at the time of the Turn Off Event (the first motion sensor going inactive). I don't know what you're trying to do, but it did just what you told it.
RL logs don't have any additional logging after that 11:55 event because it's not recognizing the inactive change.
It doesn't matter what happens to it after 11:55, as this motion sensor is not a Means to Turn Off, only a Condition to Limit Turning Off. It doesn't subscribe to it, doesn't see events from it. It just looks at it for that one instant. And at the crucial instant, it was active --> no turn off.
So I'm confused on how to write this rule then... because what I'm trying to do is say, only turn on by the zigbee motion sensor, regardless of activity of the zwave motion sensor. But only turn off the light if both motion sensors are inactive. But if only the zwave motion sensor is on, keep the light on (someone in the shower with the curtain closed and the zigbee sensor doesn't pick up any motion).
If you want the lights to turn off when both motion sensors are inactive, just make both of them Means to Turn Off. Once both are inactive, the lights will turn off.
Only one as Means to Turn On, both as Means to Turn Off. I do that in some of mine. The second motion sensor won't turn the lights on, but they don't turn off until both are inactive.
Ok... I'll give that a try... LOL sorry, and still getting used to this "change".
1 Like
No problem. A bit of a learning curve.
You will see logs that say, after the first motion goes inactive, "Not Turning Off, motion still active"; and then when the second one goes inactive, the turning off logging.
1 Like
Thanks! This was the last lighting automation I was really struggling with and one of the most important ones in my house! LOL
So just out of curiosity, in what manner would this "Condition" be used in a lighting scenario?
I couldn't answer that. There are hundreds of potential situations one could define in Room Lights. No doubt not all of them will find use. However, use cases in Home Automation are all over the map, and nothing should be ruled out of being possible. There's always a balance to be made between app features and usability, including understandability. Room Lights pushes this to an extent I'm not 100% happy with (complex) -- but on the other hand it is pretty comprehensive.
One thing that happened with Room Lights, that I think is a good thing to a point, is that as soon as we released it people asked for additional features. Some we did, some we said no to. I'm pretty sure there were meaningful use cases behind most of those requests.
Maybe what I’m about to say isn’t the right terminology but hear me out for a second. You mention that conditions are not subscribeable or at least that how I’m understanding and because of that they have no refresh property to check again after running once. But I have a scenario in which running periodically and refreshingbwoukd be valuable.
Take this rule for an example…
In this scenario, my tv is connected to homebridge. If the tv is on, I have a virtual switch I. HomeKit turn on which is also tied into my hub. If that switch is on, and illuminance from my weather station is above 8000, keep my living room lamp turned off. If it’s below, turn on and stay on until the TV is turned off. Essentially keeping the light on as long as the Tv is on, and if it’s off then the light is on and off based on a motion sensor in that room. Both are on or off based on illumination.
What I’m seeking in this scenario is i turn the TV on and it’s a bright sunny day, and so the lamp doesn’t come on, but while im sitting there, a huge thunderstorm rolls through, and illination drops below 8000. Ideally without having to rerun the rule by turning the tv on or off, I’d like it to recognize the change in the lighting and just turn on the light until illumination goes back above 8000. Or do I need to write the rule different then how I have it?
Make illuminance an additional Means to Activate.
So I set the rule with a single sensor means to activate but bkth sensors as means to deactivate, however only one deactivates and the lights went out. It doesn’t appear to be working as an “and” statement. Here’s my rule showing the light off and one sensor active and the other inactive. Wife started yelling at me this morning thinking I was screwing with her while she was in the shower! Lol
