Can someone please explain why periodically this Piston tries to lock the doors 3 times after the 300 second wait? One of the locks is a Viper smart start and I’m limited on its usage, yearly. i cant have it receiving 3 locks 2-3 times a week when i get home.
This Piston is Tripling Commands. Why?!?!?
eibyer
#2
That is one long piston… without digging into the details, you have triggers inside an on event statement, start with that.
guarddog13
#3
I guess I’m confused. I don’t know what the problem is? Is that not supposed to be the case? Should it be if presence is and not change to?..
eibyer
#4
on event catches the presence events from your presence sensor, so that triggers the piston, then inside your on event, you have changes to which also triggers the piston, so that’s two already… that’s where I stopped 
guarddog13
#5
Ohhhh I thought i had to have the on event. I’m obviously still learning. i guess that explains why it seems to work but acts wonky.
eibyer
#7
I’m on mobile now so can’t really look in detail. I use separate ifs most of the time, there are times when else catches events that I do not anticipate early on.
guarddog13
#8
Its still long and still is having errors. There’s no pattern to it either. It either stops at unlocking the door or it goes all the way through and locks the two doors three times.
guarddog13
#9
I wonder if its the constant calls I’m doing to set variable. Those contact sensors are GCal events.
This started when I rebuilt all my presence pistons and carried those variables from a different piston and that piston was having similar errors which it quit having.