Split a rule and only 1 of the 2 is working

I have two Inovelli LZW41's in my hallway. I had them both on a motion lighting app and they were working fine but I wanted to make a change where in the evening if the TV is on I only want the one farthest away to come and to not come on at all at night on so I split the rule as so:

Now quite often one or the other will not turn on or will not turn off. How do I fix this so it works 100% of the time?

Both lights are routed HUB -> Aeotec Series 7 repeater -> Bulb interestingly one bulb shows 40kps and the other 9.6kps so I'm going to do a Zwave repair to see if that will help that.

Okay did that and now both bulbs are direct to the hub. I'll see if they behave better over the next few hours.

So it got better but it was still happening. So I put the 2 lights in a group and ended up with 3 rules 1 for the group when I want both lights and then the other rules control the other lights as needed. So far that's behaving. Go figure.

The device settings could have an impact on how they respond as well.

Tried to make them simple settings but to just totally not turn one or the other on or off at random seemed really odd.

Try something like this in RM4j to pause and another to resume the rule. You can pause and resume Motion Lighting, RM4, and Simple Automation rules.

Ya I do that other places in this case it's a hallway and I was just disabling 1 of 2 lights I want the one farthest from the TV, the one by the door, to still come on at night even if the TV is on. I still can't get over how there are so many ways to do the same thing here though. We should have a discussion area for people to share various rules they setup. New people could learn without asking as many questions and others might find a better way to do something they already do. Heck in 2 months I've rewritten several rules as I have learned more. Love it.

The thing is everyone has different philosophies on how they want to run their network. Some want it all in one place and don't care if RM4 is a huge app and will run slower. Some want the fastest possible and use dedicated apps for each function. Some have multiple hubs and have local execution on each hub then link for display. Some split out the networks. Hard to accommodate for everyone and have a guide that works for everyone. Just figure out what your end goal is and build for that.

1 Like

Agree 100% the main issue here was that two lights both triggered by the same sensor were behaving oddly when running each light from a different rule but now that I defined them as a group they seem to be working 100% of the time as I got rid of 2 rules being triggered from the same sensor. I don't know how often someone tries to do it that way it just seemed like it should work. But at any rate I've worked around it to my satisfaction so it's all good now.

Bah it's still not working 100% I end up with one light or the other not wanting to shut off. I currently have them in a group and I'm turning the group on and off but often only 1 or the other will turn off. The dashboard may or may not show the bulb lit still and if I click on it on the dashboard it hangs on the hour glass. I have to go to the driver itself and click on or off to get it to respond. I'm using the May of 2020 version of Copeland's driver since the bulbs wouldn't respond for me at all with the default Inovelli Driver that is built in to the hub. Maybe Inovelli has a newer driver that I don't know about I'll check with them.

Here is how I have it setup:

Decided to try the built in Inovelli drivers even though they didn't seem to work when I set these up initially. I have set them and they are working but I don't know yet if they will turn off and on any better. The first cycle was good as far as coming on and off but they seem to take longer to come on using this driver. Maybe the next firmware release will help with that. Now to see if they work better like this.

Make a rule with both to turn on with hall motion and all of the dimmer settings you prefer with a switch to disable when on (TV) and mode to disable (Night)

Second rule with just the one light and dimmer settings you want to come on in the evening disable when off (TV) and mode to disable (Night)

Maybe a third rule to catch any outlier I'm missing. Like TV on during any other mode other than evening.

Actually I have these right now:



And the "Denon Virtual" comes on and off with another rule that toggles it but it's surely not part of the issue. In fact during the day right now while trouble shooting I've disabled the last two rules so only the first is active.

image

Add this to the rules so its disabled during any other time.

Problem is you have an on set and even though a dimmer setting isn't chosen it just turns on for those other modes so it just turns on to whatever the previous setting was. You need to either restrict it by time or mode.

image

1 Like

I had it that way I'll put it back. I'm just trying everything I can think of.

Just remember there is a mode restriction for both off and on.

image

Okay but I gotta think if that was the problem both would not work or both would and it would be 100% of the time not at random like I'm seeing. I'll make those changes too cuz who knows! Thanks for all the ideas Lewis!

I have a lot of weird use cases because no one in my house knows how to turn off a light. It's the whole reason I started out in home automation in the first place. I can't remember the last time I used a light switch now. My wife even has a confused look on her face when we visit friends and lights don't come on automatically.

1 Like

I will say this one and one exactly like it for my guest bathroom work flawlessly but the difference is this rule is turning on and off a ZEN30 switch and the one above is turning on and off individual Inovelli smart bulbs.

I don't have a lot of rules with complex restrictions. I think restricting the modes on and off will work for you. You'll need two evening rules though one for when TV is on and one for when TV is off.