for well over 2 years, I have had a simple rule that when a contact opens it turns on a group of lights. When the contact closes it turns off the group. About a week ago this rule stopped working. It still turns on the lights but does not turn them off when the contact closes. Unless you:
Open contact
Lights turn On
Closes contact
Lights stay on
Open contact
Lights are already on
Close contact
Lights go off
Here is the sequence from the log file
2022-10-11 12:06:49.889 PMinfoPantry Door contact is open
2022-10-11 12:06:49.926 PMinfoLights - Living Room Pantry - Simple Rule Turn On
2022-10-11 12:06:54.126 PMinfoPantry Door contact is closed
<nothing>
2022-10-11 12:07:38.140 PMinfoPantry Door contact is open
2022-10-11 12:07:38.172 PMinfoLights - Living Room Pantry - Simple Rule Turn On
2022-10-11 12:07:41.667 PMinfoPantry Door contact is closed
2022-10-11 12:07:41.786 PMinfoLights - Living Room Pantry - Simple Rule anti-Turn On
I have a couple of simple automation rules that ran fine for 9+ months but now are inconsistent, and only change has been update to 2.3.3.130.
Its a simple wired door contact to a Zooz Zen 16 which serves as the trigger to switch the light on and off. The log shows the trigger device 483 turning on, the simple automation app 258 giving command to turn on and the light switch 450 turning on. The off cycle also worked but then at the 10:44:44 mark you see the door relay is off but the app never gives the off command. I've repeated this same occurrence several times.
There are no restrictions or delays to the rule and below is the screenshot of rule setup.
I have a 2 SA rules that have been intermittent as well since upgrading to latest release. I use SA to mirror the in and off command to another switch. Like the OP the on command works but off doesn’t consistently. I remember having similar issues years ago. Ended up disabling the SA rule this morning and created a basic rule as a work around so I didn’t have to revert.
We would need to see screenshots of the rule and of the logs when it doesn't work as expected. There have been no significant changes to SAR in quite some time. So whatever is causing this is coming from some other aspect of your hub.
I have been having inconsistencies with the ZEN17 since I installed it 4 days ago, and a user reported adding a 1 second delay to send the command (in the case of a garage door) has solved the issue. It also appears to have fixed it for me as well. Perhaps a recent change in Hubitat firmware paired with these relays could be having some unintended consequences? Seems like too much of a coincidence that it's suddenly happening with apps utilizing this type of device.
Ha clicked delete instead of edit . First time I had to physically turn off the undercabinet lights. Second time there was an Anti Turn Off and it worked
@bravenel is there any additional logging or screenshots you need to help troubleshoot this? I am still having troubles with it. Here is example from just now:
Notice no anti-Turn On and I had to manually turn off the under cabinet lights.
I was having issues as well with a SA Rule that fires when my crawl space doors open that triggers the lights to turn on and off when closed. Last weekend I found the lights remained on a few times. I haven't been under there this week but wanted to mention SA Rules with a contact sensor is also hit or miss with this latest release.
FWIW SA has been hit or miss over the 4 years I have been on HE. Sometimes one release will cause a rule to fail and I will just use a RM or Basic Rule for a while and then switch back later. I had reported this several years ago too. It was also reported earlier this year by another user.
Update to post 2: I ended up just converting to RM5.1 (the import of SAR made it easy). its working fine now. Does seem to be a little slower than SAR to respond to trigger, but not an issue as its still functionally sufficient for a simple door contact/light.
As mentioned in original post 2, this does involve a Zen 16, which may or may not be coincidental with @sdjme comment on the Zen 17.
I am having a similar issue.
I have setup vitual switches that once turned on will turn off after 2 seconds.
Using simple automation i use these virtual switches to activate the output on the fibaro implants. Since running version 130 i have found the virtual switch turns on and off after 2 seconds. But the fibaro output doesnt turn off anymore, even though the virtual switch is off.. this has been workong for 12mths. Stopped after the upgrade. I also havent made any changes for months.
After the 134 upgrade that issue is now resolved. Not sure what may have triggered it considering someone suggested there were no changes to this module.
Anyone still having issues on v .134?? BecUs the upgrade certainly solved it for me.. i think the issue started after the build 132. Glad its sorted now.. it was a real PIA
. First time I had to physically turn off the undercabinet lights. Second time there was an Anti Turn Off and it worked
