I am testing some rules I created, and plan on using a Zen16 as remote fingers to trigger a remote. When testing it out, I find this to happen sometimes in the log
2020-06-15 10:53:38.910 pm info Up: switch is off 2020-06-15 10:53:38.178 pm info Up: switch is on 2020-06-15 10:53:37.005 pm info Up: switch is off 2020-06-15 10:53:36.863 pm info Up: switch is off ... 2020-06-15 10:58:33.077 pm info Up: switch is off 2020-06-15 10:58:32.937 pm info Up: switch is off 2020-06-15 10:58:31.955 pm info Up: switch is off 2020-06-15 10:58:31.606 pm info Up: switch is on ... 2020-06-15 10:58:45.974 pm info Up: switch is off 2020-06-15 10:58:45.088 pm info Up: switch is on 2020-06-15 10:58:43.976 pm info Up: switch is off 2020-06-15 10:58:43.736 pm info Up: switch is on
I can hear the relay trigger, but it shows as off in the logs (sometimes it's the first time, sometimes it shows properly). I have it with an auto-off of 1 second in the device. In this instance, I am triggering the relay in a repeat statement, then delay 1 second, then trigger it again.
On: Up Delay 0:00:01 On: Up Delay 0:00:01
Would it be better to remove the auto-off from the device and trigger it off in my rules? I'm trying to have this be as consistent as possible while also maintaining some speed
Update: running 18.104.22.168
From what I've also noticed, the rule will just trigger an action and continue to the next one, not waiting for the previous action to complete. This can lead to actions being performed out of order.
I don't have an example I can show now, but I did it have when I first tested my rule by triggering a switch and logging a log message. Most times the switch would trigger then the message would log (as intended), but sometimes the message would log then the switch would trigger. This resulted in me putting delays into my rule despite me not wanting to slow things down, I had to give the hub a chance to catch up.