Strangeness: Timer Times Out...immediately!

[JimSpy]

Well, this is something I've never seen before...my timeout is timing out immediately, no matter what I do

If I turn on my air purifier, I want it to turn off after 15 minutes, so I don't choke on ozone. See fig. 1.

This event has worked for years. But now, all of a sudden, if I turn on the air purifier, it turns off immediately. I don't even know how to troubleshoot this!

Here is the log, with Detailed Insteon logging....

Jan-26 2:40:20 PM

Device Control

Device: First Floor Arizona Room Air Purifier to On (100) by/from: CAPI Control Handler

Jan-26 2:40:20 PM

Insteon

CAPIControl: Label=On, Value=100, ControlType=Button

Jan-26 2:40:20 PM

Insteon

Sending command 02 62 1D 86 2E 0A 11 FF to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False

Jan-26 2:40:20 PM

Insteon

..Got RF PLM Response 02 62 1D 86 2E 0A 11 FF 06

Jan-26 2:40:21 PM

Insteon

Received STX 0x50 (Raw Insteon Rec):1D 86 2E 3D 98 D6 26 11 FF

Jan-26 2:40:21 PM

Insteon

Received a Direct ACK from Arizona Room Air Purifier (1D.86.2E): 1D 86 2E 3D 98 D6 26 11 FF

Jan-26 2:40:21 PM

Insteon

Setting status and value for device 1D.86.2E:1. Old status:0 Old Value:0, New Status:2 New Value:100

Jan-26 2:40:21 PM

Event

Event Trigger "Energy Saving Events Air Purifier Timer"

Jan-26 2:40:21 PM

Device Control

Device: First Floor Arizona Room KPL A - Air Purifier to Off (0)

Jan-26 2:40:21 PM

Insteon

CAPIControl: Label=Off, Value=0, ControlType=Button

Jan-26 2:40:21 PM

Insteon

Attempting to get a KPL LED status response from Insteon device 3B.8F.7B

Jan-26 2:40:21 PM

Insteon

Sending command 02 62 3B 8F 7B 0A 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False

Jan-26 2:40:21 PM

Insteon

..Got NAK from the RF PLM for command

Jan-26 2:40:21 PM

Insteon

..Retry #1 required. Pausing 250ms for RF PLM to clear...

Jan-26 2:40:21 PM

Insteon

Received STX 0x51 (Raw Insteon Rec):8D C6 2E 3D 98 D6 14 11 FF B8 60 72 97 77 F8 08 0E 89 5F 50 00 00 12

Jan-26 2:40:21 PM

Insteon

..Got RF PLM Response 02 62 3B 8F 7B 0A 19 01 06

Jan-26 2:40:21 PM

Insteon

Received STX 0x50 (Raw Insteon Rec):3B 8F 7B 3D 98 D6 2A 02 F0

Jan-26 2:40:21 PM

Insteon

Received a Direct ACK from Arizona Room KeyPadLinc (3B.8F.7B): 3B 8F 7B 3D 98 D6 2A 02 F0

Jan-26 2:40:21 PM

Insteon

Setting status and value for device 3B.8F.7B:3. Old status:0 Old Value:0, New Status:3 New Value:0

Jan-26 2:40:21 PM

Insteon

Checking for keypadlinc button sync on device 3B.8F.7B src index 3, SrcIsSyncTarget=True...

Jan-26 2:40:21 PM

Insteon

Sending command 02 62 3B 8F 7B 1A 2E 00 00 09 F0 00 00 00 00 00 00 00 00 00 00 D9 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False

Jan-26 2:40:21 PM

Insteon

SyncResponderDevices called for device code: 3B.8F.7B:3

Jan-26 2:40:21 PM

Insteon

Sending sync command 19 to linked responder device: Arizona Room Air Purifier (1D.86.2E)

Jan-26 2:40:22 PM

Insteon

..Got RF PLM Response 02 62 3B 8F 7B 1A 2E 00 00 09 F0 00 00 00 00 00 00 00 00 00 00 D9 06

Jan-26 2:40:22 PM

Insteon

Received STX 0x50 (Raw Insteon Rec):3B 8F 7B 3D 98 D6 2A 2E 00

Jan-26 2:40:22 PM

Insteon

Sending command 02 62 1D 86 2E 0A 13 00 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False

Jan-26 2:40:22 PM

Insteon

Received a Direct ACK from Arizona Room KeyPadLinc (3B.8F.7B): 3B 8F 7B 3D 98 D6 2A 2E 00

Jan-26 2:40:22 PM

Insteon

..Got RF PLM Response 02 62 1D 86 2E 0A 13 00 06

Jan-26 2:40:22 PM

Insteon

Received STX 0x50 (Raw Insteon Rec):1D 86 2E 3D 98 D6 26 13 00

Jan-26 2:40:23 PM

Insteon

Received a Direct ACK from Arizona Room Air Purifier (1D.86.2E): 1D 86 2E 3D 98 D6 26 13 00

Jan-26 2:40:23 PM

Insteon

Setting status and value for device 1D.86.2E:1. Old status:100 Old Value:100, New Status:3 New Value:0

Why is it firing right away?

[sparkman]

Your first event action turns it off after 15 minutes, your second one turns it off immediately. Your first action creates a delayed device action, but it does not pause the rest of the event from executing. You don't need the second device action. I would recommend adding an action before your first one to cancel any delayed device actions for that device.

[JimSpy]

My second action? You mean, turning off the corresponding KeyPadLinc button? But it's been like that for over a year! I thought the second action waited for the first to complete?

[randy]

Actually the actions are for two different Devices. When "First Floor Arizona Air Purifier" turns On it sets up a delayed device action to turn it back Off after 15 minutes. The second Action turns off "First Floor Arizona KPL-A Air Purifier" Off immediately. The log entries verify that is exactly what is happening. I would guess 15 minutes later in the log, the Delayed Action Event will run and turn the "First Floor Arizona Air Purifier" Off.

[randy]

My second action? You mean, turning off the corresponding KeyPadLinc button? But it's been like that for over a year! I thought the second action waited for the first to complete?

No and they never would have been delayed. A delayed Device Action will only delay the one Action. Everything else in the Event will run Immediately. If you want both Actions to be delayed, you either need to put a 15 minute Wait in before both of them and remove the delay on the one Action, or you need to add the delay to the second Action as well.

[JimSpy]

Hmmmmm.....Okey dokey. (Walks away scratching head, muttering "but I didn't change anything...")

[joegr]

If you have "sync linked responder devices" checked for the keypad in the Insteon plugin, then it will turn the Air Purifier off when it turns the button off.

[sparkman]

My second action? You mean, turning off the corresponding KeyPadLinc button? But it's been like that for over a year! I thought the second action waited for the first to complete?

Sorry, thought they were the same device. No, the second one does not wait the 15 minutes. It gets executed immediately.

[JimSpy]

If you have "sync linked responder devices" checked for the keypad in the Insteon plugin, then it will turn the Air Purifier off when it turns the button off.

I do have it checked, although I've never quite understood this function. I think it's supposed to tie the button together with it's target device so that if one turns on so does the other. But I've never been able to get that to work reliably, which is why I have the event do both separately.