multiple programs at sunset failing

[tb93]

Hi,

 

I have (currently) a relatively simple INSTEON system comprised of 4 dual-band INSTEON dimmers (v.41), 1 dual-band switch (v.42), and 1 dual-band keypadlinc (v.41). I also have a PLY-994iIR PRO (3.3.10) connected to a dual-band EZICOMM RS232 INSTEON PLM Model #5010K (supposedly identical to the INSTEON #2413S).

 

Things are generally reliable, except for my Sunset/Sunrise program to turn on/off an outdoor light connected to the load of the keypadlinc. Sometimes it works, sometimes it doesn't. The program is trivial:

 

If

From Sunset

To Sunrise (next day)

Then

Set 'Great Room / Exterior' On

Else

Set 'Great Room / Exterior' Off

 

Notably, I have another program that also runs at Sunset/Sunrise and adjusts light levels on several dimmers (it seems to run okay).

 

I checked the log, and the ISY thinks that all programs are executing properly:

 

Great Room / Main On Level 25% Tue 2013/02/12 05:17:28 PM System Log

Great Room / Moose On Level 25% Tue 2013/02/12 05:17:28 PM System Log

Great Room / Office On Level 25% Tue 2013/02/12 05:17:28 PM System Log

Great Room / Exterior On 255 Tue 2013/02/12 05:17:28 PM Program Log

 

yet, the Great Room / Exterior light isn't (reliably) coming on or off (sometimes it works, sometimes it doesn't).

 

There are no entries of note in the error log.

 

If I manually execute the 'Then' or 'Else' part of my program, it comes on just fine.

 

Some questions:

 

Does the ISY 'queue' commands to the modem, such that it should be able to handle multiple programs executing simultaneously? Or is it possible that both programs execute at the same instant, and the commands to the modem are being jumbled?

 

Does the ISY verify that the program executed successfully by default (e.g., checking light status after execution)? Should I be doing this manually?

 

Does the modem ensure reliable communication with the keypadlinc? Does the keypadlinc ACK the command? Does the modem retry if failure?

 

Are there problems with the EZICOMM modem vs. the real 2413S?

 

Is this a reliability problem with my keypadlinc?

 

suggestions?

 

Thanks!

Ty

[LeeG]

Does the ISY 'queue' commands to the modem, such that it should be able to handle multiple programs executing simultaneously? Or is it possible that both programs execute at the same instant, and the commands to the modem are being jumbled?

 

Run Tools | Diagnostics | Event Viewer with LEVEL 3 selected before Sunset. Post the event trace of a failure.

 

Does the ISY verify that the program executed successfully by default (e.g., checking light status after execution)? Should I be doing this manually?

 

The ISY does not query devices to verify a device actually reacted as it said it did (or said it didn’t). If a device does not ACK a command the PLM will automatically retry.

 

Does the modem ensure reliable communication with the keypadlinc?

 

The PLM will retry if the device does not ACK the device command.

 

Does the keypadlinc ACK the command?

 

Yes

 

Does the modem retry if failure?

 

Yes.

 

Are there problems with the EZICOMM modem vs. the real 2413S?

 

Don’t know. Why an EZIComm rather than a 2413S?

 

Is this a reliability problem with my keypadlinc?

 

There may be reliability problems with the Insteon network that is causing the PLM to retry commands which is interfering with two Sunset Programs issuing Insteon commands at the same time. Could be a problem with KeypadLinc comm. only. That is one of the reasons for the Event trace.

 

suggestions?

 

Run the Event trace described in the first answer. Combine the Insteon commands from the two Sunset Programs into one Program or delay one of the Programs with Sunset +1 or 2 minutes.

[tb93]

OK,

 

here is the log at sunset:

 

notably, 20.FC.CE is the keypadlinc. The program sets the load of 20.FC.CE to ON, and it also reprograms ON levels for a variety of other devices.

 

You can see the exchange with 20.FC.CE at the head of the log. Interestingly, it is quite different than the exchange that I see if I manually turn on that load from within the ISY GUI.

 

thoughts? thank you for your help,

Ty

 

Here's the exchange for a manual turn-on:

Wed 02/13/2013 05:28:10 PM : [iNST-TX-I1 ] 02 62 20 FC CE 0F 11 FF

Wed 02/13/2013 05:28:10 PM : [iNST-ACK ] 02 62 20.FC.CE 0F 11 FF 06 LTONRR (FF)

Wed 02/13/2013 05:28:10 PM : [iNST-ACK ] 02 62 20.FC.CE 0F 11 FF 06 LTONRR (FF): Duplicate or ACK for a different device

Wed 02/13/2013 05:28:12 PM : [iNST-SRX ] 02 50 20.FC.CE 1E.7A.0C 2B 11 FF LTONRR (FF)

Wed 02/13/2013 05:28:12 PM : [std-Direct Ack] 20.FC.CE-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Wed 02/13/2013 05:28:12 PM : [ 20 FC CE 1] ST 255

 

Now, here's the whole log from my sunset program:

Wed 02/13/2013 04:40:03 PM : [ Time] 16:40:33 1(0)

 

Wed 02/13/2013 04:50:02 PM : [ Time] 16:50:33 1(0)

 

Wed 02/13/2013 05:00:02 PM : [ Time] 17:00:33 1(0)

 

Wed 02/13/2013 05:10:32 PM : [ Time] 17:10:33 1(0)

 

Wed 02/13/2013 05:18:45 PM : [ Time] 17:18:46 1(0)

 

Wed 02/13/2013 05:18:46 PM : [iNST-TX-I1 ] 02 62 20 FC CE 0F 11 FF

 

Wed 02/13/2013 05:18:46 PM : [ 20 96 4C 1] OL 63

 

Wed 02/13/2013 05:18:46 PM : [ 20 94 F3 1] OL 63

 

Wed 02/13/2013 05:18:46 PM : [ 20 A0 C1 1] OL 63

 

Wed 02/13/2013 05:18:46 PM : [iNST-ACK ] 02 62 20.FC.CE 0F 11 FF 06 LTONRR (FF)

 

Wed 02/13/2013 05:18:46 PM : [iNST-TX-I2CS] 02 62 20 94 F3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

 

Wed 02/13/2013 05:18:46 PM : [iNST-ACK ] 02 62 20.94.F3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

 

Wed 02/13/2013 05:18:47 PM : [iNST-SRX ] 02 50 20.94.F3 1E.7A.0C 2B 2F 00 (00)

 

Wed 02/13/2013 05:18:47 PM : [std-Direct Ack] 20.94.F3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Wed 02/13/2013 05:18:47 PM : [iNST-SRX ] 02 50 20.94.F3 1E.7A.0C 23 2F 00 (00)

 

Wed 02/13/2013 05:18:47 PM : [std-Direct Ack] 20.94.F3-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

 

Wed 02/13/2013 05:18:48 PM : [iNST-ERX ] 02 51 20 94 F3 1E 7A 0C 11 2F 00 00 01 0F FF 00 A2 00 1E 7A 0C FF 1F 01 5D

 

Wed 02/13/2013 05:18:48 PM : [Ext-Direct ] 20.94.F3-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

 

Wed 02/13/2013 05:18:48 PM : [iNST-TX-I2CS] 02 62 20 94 F3 1F 2F 00 00 02 0F EF 08 A2 16 1E 7A 0C 3F 1F 01 0E

 

Wed 02/13/2013 05:18:48 PM : [iNST-ACK ] 02 62 20.94.F3 1F 2F 00 00 02 0F EF 08 A2 16 1E 7A 0C 3F 1F 01 0E 06 (00)

 

Wed 02/13/2013 05:18:50 PM : [iNST-SRX ] 02 50 20.94.F3 1E.7A.0C 2B 2F 00 (00)

 

Wed 02/13/2013 05:18:50 PM : [std-Direct Ack] 20.94.F3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Wed 02/13/2013 05:18:50 PM : [iNST-TX-I2CS] 02 62 20 94 F3 1F 2E 00 01 06 3F 00 00 00 00 00 00 00 00 00 00 8C

 

Wed 02/13/2013 05:18:50 PM : [iNST-ACK ] 02 62 20.94.F3 1F 2E 00 01 06 3F 00 00 00 00 00 00 00 00 00 00 8C 06 (00)

 

Wed 02/13/2013 05:18:51 PM : [iNST-SRX ] 02 50 20.94.F3 1E.7A.0C 2B 2E 00 (00)

 

Wed 02/13/2013 05:18:51 PM : [std-Direct Ack] 20.94.F3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Wed 02/13/2013 05:18:51 PM : [iNST-TX-I2CS] 02 62 20 96 4C 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

 

Wed 02/13/2013 05:18:51 PM : [iNST-ACK ] 02 62 20.96.4C 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

 

Wed 02/13/2013 05:18:53 PM : [iNST-SRX ] 02 50 20.96.4C 1E.7A.0C 2B 2F 00 (00)

 

Wed 02/13/2013 05:18:53 PM : [std-Direct Ack] 20.96.4C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Wed 02/13/2013 05:18:53 PM : [iNST-ERX ] 02 51 20 96 4C 1E 7A 0C 11 2F 00 00 01 0F FF 00 A2 00 1E 7A 0C FF 1F 01 5D

 

Wed 02/13/2013 05:18:53 PM : [Ext-Direct ] 20.96.4C-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

 

Wed 02/13/2013 05:18:54 PM : [iNST-TX-I2CS] 02 62 20 96 4C 1F 2F 00 00 02 0F F7 08 A2 12 1E 7A 0C 3F 1F 01 0A

 

Wed 02/13/2013 05:18:54 PM : [iNST-ACK ] 02 62 20.96.4C 1F 2F 00 00 02 0F F7 08 A2 12 1E 7A 0C 3F 1F 01 0A 06 (00)

 

Wed 02/13/2013 05:18:56 PM : [iNST-SRX ] 02 50 20.96.4C 1E.7A.0C 2B 2F 00 (00)

 

Wed 02/13/2013 05:18:56 PM : [std-Direct Ack] 20.96.4C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Wed 02/13/2013 05:18:56 PM : [iNST-TX-I2CS] 02 62 20 96 4C 1F 2E 00 01 06 3F 00 00 00 00 00 00 00 00 00 00 8C

 

Wed 02/13/2013 05:18:56 PM : [iNST-ACK ] 02 62 20.96.4C 1F 2E 00 01 06 3F 00 00 00 00 00 00 00 00 00 00 8C 06 (00)

 

Wed 02/13/2013 05:18:58 PM : [iNST-SRX ] 02 50 20.96.4C 1E.7A.0C 2B 2E 00 (00)

 

Wed 02/13/2013 05:18:58 PM : [std-Direct Ack] 20.96.4C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Wed 02/13/2013 05:18:58 PM : [iNST-TX-I2CS] 02 62 20 A0 C1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

 

Wed 02/13/2013 05:18:58 PM : [iNST-ACK ] 02 62 20.A0.C1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

 

Wed 02/13/2013 05:18:59 PM : [iNST-SRX ] 02 50 20.A0.C1 1E.7A.0C 2B 2F 00 (00)

 

Wed 02/13/2013 05:18:59 PM : [std-Direct Ack] 20.A0.C1-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Wed 02/13/2013 05:18:59 PM : [iNST-SRX ] 02 50 20.A0.C1 1E.7A.0C 23 2F 00 (00)

 

Wed 02/13/2013 05:18:59 PM : [std-Direct Ack] 20.A0.C1-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

 

Wed 02/13/2013 05:18:59 PM : [iNST-ERX ] 02 51 20 A0 C1 1E 7A 0C 11 2F 00 00 01 0F FF 00 A2 00 1E 7A 0C FF 1F 01 5D

 

Wed 02/13/2013 05:18:59 PM : [Ext-Direct ] 20.A0.C1-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

 

Wed 02/13/2013 05:18:59 PM : [iNST-TX-I2CS] 02 62 20 A0 C1 1F 2F 00 00 02 0F EF 08 A2 11 1E 7A 0C 3F 1F 01 13

 

Wed 02/13/2013 05:18:59 PM : [iNST-ACK ] 02 62 20.A0.C1 1F 2F 00 00 02 0F EF 08 A2 11 1E 7A 0C 3F 1F 01 13 06 (00)

 

Wed 02/13/2013 05:19:00 PM : [iNST-SRX ] 02 50 20.A0.C1 1E.7A.0C 2B 2F 00 (00)

 

Wed 02/13/2013 05:19:00 PM : [std-Direct Ack] 20.A0.C1-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Wed 02/13/2013 05:19:00 PM : [iNST-TX-I2CS] 02 62 20 A0 C1 1F 2E 00 01 06 3F 00 00 00 00 00 00 00 00 00 00 8C

 

Wed 02/13/2013 05:19:00 PM : [iNST-ACK ] 02 62 20.A0.C1 1F 2E 00 01 06 3F 00 00 00 00 00 00 00 00 00 00 8C 06 (00)

 

Wed 02/13/2013 05:19:00 PM : [iNST-SRX ] 02 50 20.A0.C1 1E.7A.0C 23 2F 00 (00)

 

Wed 02/13/2013 05:19:00 PM : [std-Direct Ack] 20.A0.C1-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

 

Wed 02/13/2013 05:19:01 PM : [iNST-SRX ] 02 50 20.A0.C1 1E.7A.0C 2B 2E 00 (00)

 

Wed 02/13/2013 05:19:01 PM : [std-Direct Ack] 20.A0.C1-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

[LeeG]

The 20 FC CE device did not ACK the request to turn On. There is a series of commands that are changing Responder On Levels and Local On Levels with Adjust Scene statements that are starting at the same time. I take from this the activity from two Programs is interfering with each other since 20 FC CE did not ACK the On command.

[tb93]

hmmm...

 

so

 

Wed 02/13/2013 05:18:46 PM : [iNST-ACK ] 02 62 20.FC.CE 0F 11 FF 06 LTONRR (FF)

 

doesn't indicate an ACK from the the keypadlinc for the command to turn on the lights?

 

Assuming it doesn't, is this the expected behavior? I'm kind of surprised ISY doesn't have a serial queue for program execution? what is even stranger is that I already combined the 'exterior lights on' program and the 'adjust dim levels' program; this would suggest that the ISY actually executes 'Then' commands in parallel? that seems kind of problematic, no?

 

out of curiosity, then, what do the commands:

 

INST-TX-I1

INST-ACK

INST-SRX

Std-Direct Ack

 

mean?

 

Thanks again for your expertise,

Ty

[LeeG]

Wed 02/13/2013 05:18:46 PM : [iNST-ACK ] 02 62 20.FC.CE 0F 11 FF 06 LTONRR (FF)

 

"doesn't indicate an ACK from the the keypadlinc for the command to turn on the lights?"

 

That is not an ACK from the KeypadLinc. The PLM echoes back every Serial command sent to it with either an 06 (accepted) or 15 (rejected) appended to the end of the command. Also the message starts with 02 6x which is an outbound message.

 

The response from the device will be an 02 5x inbound message. It would look like what was received from the manual On command at the beginning of an earlier post.

 

Wed 02/13/2013 05:28:12 PM : [iNST-SRX ] 02 50 20.FC.CE 1E.7A.0C 2B 11 FF LTONRR (FF)

Wed 02/13/2013 05:28:12 PM : [std-Direct Ack] 20.FC.CE-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

 

This is the original Serial command sent to the PLM. 02 6x is outbound

Wed 02/13/2013 05:18:46 PM : [INST-TX-I1 ] 02 62 20 FC CE 0F 11 FF

 

This is the echo of the original Serial command from the PLM. 02 6x is outbound

Wed 02/13/2013 05:18:46 PM : [INST-ACK ] 02 62 20.FC.CE 0F 11 FF 06 LTONRR (FF)

 

This is a device ACK to a Standard Insteon message. 02 5x is inbound

Wed 02/13/2013 05:18:47 PM : [INST-SRX ] 02 50 20.94.F3 1E.7A.0C 2B 2F 00 (00)

Wed 02/13/2013 05:18:47 PM : [Std-Direct Ack] 20.94.F3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

 

 

This is an event trace from a Program that turns On a KeypadLinc followed by an Adjust Scene. Note that the KPL On completes with an ACK before the Adjust Scene statement is executed.

 

Wed 02/13/2013 09:51:20 PM : [iNST-TX-I1 ] 02 62 1B 57 F8 0F 11 FF

 

Wed 02/13/2013 09:51:20 PM : [iNST-ACK ] 02 62 1B.57.F8 0F 11 FF 06 LTONRR (FF)

 

Wed 02/13/2013 09:51:20 PM : [ 1D 38 0 1] OL 255

 

Wed 02/13/2013 09:51:20 PM : [iNST-SRX ] 02 50 1B.57.F8 19.70.06 2B 11 FF LTONRR (FF)

 

Wed 02/13/2013 09:51:20 PM : [std-Direct Ack] 1B.57.F8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

Wed 02/13/2013 09:51:20 PM : [iNST-TX-I2 ] 02 62 1D 38 00 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC

 

Wed 02/13/2013 09:51:21 PM : [iNST-ACK ] 02 62 1D.38.00 1F 2E 00 01 06 FF 00 00 00 00 00 00 00 00 00 00 CC 06 (00)

 

Wed 02/13/2013 09:51:21 PM : [iNST-SRX ] 02 50 1D.38.00 19.70.06 2B 2E 00 (00)

 

Wed 02/13/2013 09:51:21 PM : [std-Direct Ack] 1D.38.00-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

 

 

And these are the Program statements that generated the event trace

 

Set 'KPL 8 Dimmer v40' On

In Scene 'SwitchLLinc DB Dimmer v40' Set 'SwitchLLinc DB Dimmer v40' 100% (On Level)

 

 

Something not identified is being executed. I don't see how that event trace would come from a single Program execution.