IoP behavior change for keypad status trigger evaluation?

[AKAPADIA]

I have the following program that checks the status of a keypadlinc button, and if the status is On, waits 1.5 hours and then sets the switch to Off. My assumption is that the event would fire when the button is turned On and the program would run, and as long as the button is untouched, the event wouldn't fire retrigger and 1.5 hours later, the button would reset to Off.

On my old Isy this worked as per my above assumptions. On the Polisy, I find that the button never resets well beyond the 1.5 hour mark and in the UI the program shows that it's running. I can only imagine that the status must be getting reevaluated repeatedly, thus resetting the clock - or else there is some other issue. At any rate, this seems like a behavior change at the least when compared with the old Isy? 

Wondering whether my assumption is incorrect OR there is some other potential issue afoot here?

[Athlon]

Rather than 'Status', try 'if Master Bed Light.D is switched On'.

 

[lilyoyo1]

Status should work. While control is fine, it wouldn't cover what he's trying to do should he turn his lights on with voice or app control. 

@arshishkI've experienced the same thing. I ended up creating a variable which for some reason works without fail

 

[bhihifi]

@lilyoyo1 A state variable set in another program if status is on and then polled in the timer program? Do you reset the state variable after the interval?

 

[lilyoyo1]

15 minutes ago, bhihifi said:

@lilyoyo1 A state variable set in another program if status is on and then polled in the timer program? Do you reset the state variable after the interval?

 

Yes I do. it'll reset once it's off regardless of how it's turned off

[vbPhil]

5 hours ago, arshishk said:

Wondering whether my assumption is incorrect OR there is some other potential issue afoot here?

Your assumption looks correct to me, but you never know what evil lurks.

Another technique that I use is with 2 programs; one is the trigger and the other the control. The trigger program contains your IF statement and then calls the control program. The control program has no IF statements. In the body it immediately disables the trigger program, does what it needs to and then re-enables the trigger program. I've never had a problem using WAIT in the control program this way. I use this with a WirelessTag moisture sensor to detect a water level and it was notorious with successive false triggers around the event.

[Michel Kohanim]

@arshishk,

Is this a KPL button?

With kind regards,
Michel

[lilyoyo1]

52 minutes ago, Michel Kohanim said:

@arshishk,

Is this a KPL button?

With kind regards,
Michel

It happens with my keypads 

[stillwater]

@Michel Kohanim  Apparently yes a KPL button.  First sentence of first post from @arshishk  was "I have the following program that checks the status of a keypadlinc button, and if the status is On, waits 1.5 hours and then sets the switch to Off."

[AKAPADIA]

@Michel Kohanim, yes, it's a KPL button. Of course, since I posted, it hasn't happened ... I use this feature once a day.

[Michel Kohanim]

@arshishk, 

What is Master Switch D? If a KPL button, you cannot turn it on/off. You have to put it in a scene and turn on/off the scene. And, then wait for All On and All Off bug to hit you.

With kind regards,
Michel

[AKAPADIA]

@Michel Kohanim, yes, this is a Scene that targets a KPL button; I'm turning the scene off. This exact same program worked for years with the ISY. It fails on the Polisy. It failed just now again tonight. The program keeps running as if the timer has either been refreshed or has not run out and the admin console shows that the program is running (green icon) even after the timer should have fired. 

Edited April 26, 2022 by arshishk

[Michel Kohanim]

@arshishk,

Thank you. How about the Last run time and Last finish time columns. Are they accurate? 

With kind regards,
Michel