TLDR; Do rules have a problem running at the same time especially when there are waits or delays built into the rule? Skip to BLOB (at the bottom) if you want.
The more I try to automate, the more crippled the system gets. So I must be doing something wrong.
5 rules to consider (Thinking that problem might have been that I had these rules doing too much, I dumbed them way down to just perform the tasks listed below. They originally did things like check to make sure the alarm got the arm command and started the countdown before locking, door lock didn't jam, etc.):
#1 - A rule that says when Fibaro Keyfob button 2 is pressed: unlock the front door (Kwikset 620), send disarm to Envisalink EVL4 (Honeywell), turn on about 7 lights (Inovelli and Zooz), set the AC to cool 73 (Go Control).
#2 - A rule that says when Fibaro Keyfob button 3 is pressed: lock the front door, lock the other 3 doors, close the two garage doors (GoControl), turn off the garage lights (Inovelli and Zooz), arm stay the Envisalink EVL-4.
#3 - A rule that says Zooz Zen32 button 4 checks state of 12 lights, and if any of them is on, when pressed it turns them off, else if all of them are off it turns 7 of them on)
#4 - A rule that is triggered by a change in the lock state of 4 locks, that says if any lock is unlocked it turns on the notification 1 child switch of about 15 Inovelli switches (makes the led light on the switch blink red), else if all 4 locks are locked, then it turns all the Inovelli notification 1 child switches off. Note: I used to have all these Notification 1s in a group (Groups and Scenes), but the group would sometimes change states and look like it turned off or on, but it wouldn't actually change the child notification switches. So I broke all these notifications out in the rules and deleted the group. This was just another layer of complexity that failed sometimes.
#5 (this used to be built into the alarm rules but I seperated it, in an attempt to simplify the rules) - A rule that is triggered by the envisalink "switch" (not the alarm state) that says when the Alarm is "off" the porch light is on, else if the Alarm is "on" the porch light is off. This is the equivalent of the blinky light on your dashboard that lets you know when your car alarm is armed or not. It also lets me know when the exit countdown is done when we are leaving.
Scenarios:
** What I want to happen:
It's early in the morning before everyone else is up. So I grab my lunch pale, and head for the door. Press keyfob button 2 to disarm the alarm and unlock the front door, and turn on some lights on my path out the front door. When the alarm disarmed the porch light should have turned on, and when the doorlock unlocked the Inovelli Notification 1s should be on and the LEDs should be flashing red. Press button 4 on the Zen32 right next to the front door to darken the house. Walk outside and press button 3 on the keyfob to lock the door (The doorlock should trigger the Inovelli Notification 1s should turn off and go back to solid blue), Arm Stay the Alarm, and 45 seconds later the porch light should go out indicating the alarm is on.
** What actually happens:
It's early in the morning before everyone else is up. So I grab my lunch pale, and head for the door. Press keyfob button 2. Usually the alarm disarms, the front door unlocks, and the lights mostly turn on. The porch light may or may not come on. The notifications might come on. Press the Zen32 button 4 and nothing happens. Run around and manually turn off the lights that came on. Head out the front door and notice the porch light isn't on. Turn around and hit the keyfob button 3 to Arm Stay. The porch light comes on (it finally caught up from the disarm??), front door locks, look through the door but the notifications are still on. Count 45 seconds for the Alarm countdown to complete. Get to about 2 minutes and the porch light still isn't off. Check the alarm status on my phone and see that is definitely is on. Give up and go to work. Text the wife to disregard the red flashing lights, and reassure her that the front door is definitely locked. Apologize to her when she calls to tell me that "nothing in this damn house is working."
Suspicions:
The Groups and Scenes app is suspect. It seems like everything was exacerbated by me putting things in groups, and it seemed like things started to run better as I removed things from the groups. I am going to take apart the last few groups and put all the individual devices in the rules rather than the groups.
Gripes:
The driver for the Fibaro Keyfob either got pulled or isn't supported anymore. I don't know but double clicks and triple clicks are no longer working/supported. So you get 6 single click buttons and 6 helds. I would have an Arm Stay Dark built for double clicking the "Arm Stay" button but double click is no longer an option. And single click is worthless on a fob with raised buttons because you get too many accidental dischages.
The Zen32 is capable of associations because it's in the manual, but no one has written a Hubitat driver to do it. So I would like the first three buttons to be associated (including the led) to three light switches accross the room, but instead I have to settle for a rule and you already know how rules are working for me.
Why are doorlocks universally garbage? You have to pair them within a foot of the hub which is a PITA because you physically install the door locks, and the hubs are no longer wireless or battery powered. Then doorlocks sometimes randomly decide to stop reporting their status, and never report their battery condition correctly. The occasionally stop responding to lock and unlock commands. This is usually after a power outage that affected the hub (for whatever reason).
/end rant
BLOB:
... but does anyone know if rules should be able to run concurrently while one of the rules is delaying or waiting. For example if my rule is waiting for the alarm to reach arm stay during the exit countdown, and the door lock locks, should the rule that watches for the change in locks be able to run and turn off my Inovelli notifications?
If read the whole thing thanks for hearing me out,
Josh
