Communication is reliable except when commands sent in succession

[prairiecode]

Hello folks,

 

I am new to Insteon, and the ISY-994i Pro that I have.  This is not precisely a ISY issue (I think), but I do notice it in the ISY.

 

My communication is 100% reliable except when multiple commands are issued in succession.  For instance, I have two SwitchLinc Dimmer switches in a "virtual 3-way" (both are controllers in a scene, and one has no load connected to it).  If I go to the "Remote" (the one with no load) and start dimming the lights, then realize "oops, too dim", and quickly switch to brightening them, it seems the switches lose communication with each other until I hit the power on or off button.

 

I have also seen the ISY-994i complain of being unable to communicate with a SwitchLinc when I am, say, making a change to a large scene (dozen or so devices in it) that touches all of the devices.

 

Other than that, I'm not having trouble.

 

I can duplicate this both with switches on the same circuit, and between a SwitchLinc and a LampLinc on different circuits (and probably different legs).  It is slightly easier to duplicate between the SwitchLinc and LampLinc.

 

All devices concerned were bought within the last 2 weeks and are APs.

 

My house is, so far as I know, electrically and RF quiet.  I am into amateur radio and it has to be this for my hobby.  No 900MHz devices were in use at the time this was going on, and the only other RF in the house at that time was Wifi.  My ham radios were not in use.  My wiring was all new in 2006 and I suspect it is still in excellent shape.  No TVs, etc. were powered on nearby.

 

Any ideas?

[LeeG]

There are two Insteon commands associated with Dim operation ( Fade Down, Fade Stop) and two for Brighten (Fade Up, Fade Stop).  It sounds like the sudden change in Fade direction may not allow the SwitchLinc to issue the Fade Stop before starting the new Fade direction.   An event viewer at LEVEL 3 may confirm that.  

[prairiecode]

That sounds plausible.  I am not quite sure how to read this event viewer dump, but basically here's what it was:

 

Both switches showed the light off (and it was).  On the "remote" (no load) switch, I pushed and held the brightness up button.  Then I released it and held the brightness down button.  The light continued to move to full brightness, and the remote switch moved to full off.  The  switches were then showing opposite states.

 

The "remote" switch is 33.2C.0E and the "load" switch is 33.2B.0E.

 

I'm new to the Insteon protocol, but I think the first line (LTMCON UP) means that I pressed and held the dimmer button in the up direction.  I'm not sure what BMAN 1 means.  Anyhow, then we see the LTMCOFF (I guess "release the brighten button").  I don't see a second LTMCON come through -- that's what I'm missing, eh?

 

Is there anything I can do about this?  Can others duplicate this in their setups?

Tue 01/27/2015 09:26:07 AM : [INST-SRX    ] 02 50 33.2C.0E 00.00.01 CF 17 01    LTMCON (UP)
Tue 01/27/2015 09:26:07 AM : [Std-Group   ] 33.2C.0E-->Group=1, Max Hops=3, Hops Left=3
Tue 01/27/2015 09:26:07 AM : [D2D EVENT   ] Event [33 2C E 1] [BMAN] [1] uom=0 prec=-1
Tue 01/27/2015 09:26:07 AM : [   33 2C E 1]     BMAN   1
Tue 01/27/2015 09:26:11 AM : [INST-SRX    ] 02 50 33.2C.0E 00.00.01 CF 18 00    LTMCOFF(00)
Tue 01/27/2015 09:26:11 AM : [Std-Group   ] 33.2C.0E-->Group=1, Max Hops=3, Hops Left=3
Tue 01/27/2015 09:26:11 AM : [D2D EVENT   ] Event [33 2C E 1] [SMAN] [0] uom=0 prec=-1
Tue 01/27/2015 09:26:11 AM : [   33 2C E 1]     SMAN   0
Tue 01/27/2015 09:26:11 AM : [D2D EVENT   ] Event [33 2B E 1] [ST] [255] uom=0 prec=-1
Tue 01/27/2015 09:26:11 AM : [   33 2B E 1]       ST 255
Tue 01/27/2015 09:26:11 AM : [D2D-CMP 001F] STS [33 2B E 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false
Tue 01/27/2015 09:26:11 AM : [D2D EVENT   ] Event [33 2B BC 1] [ST] [255] uom=0 prec=-1
Tue 01/27/2015 09:26:11 AM : [  33 2B BC 1]       ST 255
Tue 01/27/2015 09:26:11 AM : [D2D EVENT   ] Event [33 2C E 1] [ST] [255] uom=0 prec=-1
Tue 01/27/2015 09:26:11 AM : [   33 2C E 1]       ST 255

[LeeG]

That is the problem.   This is trace where I waited a few seconds before pressing Off (Down) button.

 

Tue 01/27/2015 10:54:24 AM : [iNST-SRX    ] 02 50 33.95.41 00.00.01 CB 17 01    LTMCON (UP)

Tue 01/27/2015 10:54:24 AM : [std-Group   ] 33.95.41-->Group=1, Max Hops=3, Hops Left=2

Tue 01/27/2015 10:54:24 AM : [D2D EVENT   ] Event [33 95 41 1] [bMAN] [1] uom=0 prec=-1

Tue 01/27/2015 10:54:24 AM : [  33 95 41 1]     BMAN   1

Tue 01/27/2015 10:54:25 AM : [iNST-SRX    ] 02 50 33.95.41 00.00.01 CB 18 00    LTMCOFF(00)

Tue 01/27/2015 10:54:25 AM : [std-Group   ] 33.95.41-->Group=1, Max Hops=3, Hops Left=2

Tue 01/27/2015 10:54:25 AM : [D2D EVENT   ] Event [33 95 41 1] [sMAN] [0] uom=0 prec=-1

Tue 01/27/2015 10:54:25 AM : [  33 95 41 1]     SMAN   0

Tue 01/27/2015 10:54:25 AM : [D2D EVENT   ] Event [33 95 41 1] [sT] [58] uom=0 prec=-1

Tue 01/27/2015 10:54:25 AM : [  33 95 41 1]       ST  58

 

Tue 01/27/2015 10:54:35 AM : [iNST-SRX    ] 02 50 33.95.41 00.00.01 CB 17 00    LTMCON (DOWN)

Tue 01/27/2015 10:54:35 AM : [std-Group   ] 33.95.41-->Group=1, Max Hops=3, Hops Left=2

Tue 01/27/2015 10:54:35 AM : [D2D EVENT   ] Event [33 95 41 1] [bMAN] [0] uom=0 prec=-1

Tue 01/27/2015 10:54:35 AM : [  33 95 41 1]     BMAN   0

Tue 01/27/2015 10:54:36 AM : [iNST-SRX    ] 02 50 33.95.41 00.00.01 CB 18 00    LTMCOFF(00)

Tue 01/27/2015 10:54:36 AM : [std-Group   ] 33.95.41-->Group=1, Max Hops=3, Hops Left=2

Tue 01/27/2015 10:54:36 AM : [D2D EVENT   ] Event [33 95 41 1] [sMAN] [0] uom=0 prec=-1

Tue 01/27/2015 10:54:36 AM : [  33 95 41 1]     SMAN   0

Tue 01/27/2015 10:54:36 AM : [D2D EVENT   ] Event [33 95 41 1] [sT] [7] uom=0 prec=-1

Tue 01/27/2015 10:54:36 AM : [  33 95 41 1]       ST   7

 

This is trace where I did not wait between pressing and holding Up (On), immediately pressing and holding Down (Off).  The device did ramp the LEDs down but did not send a Down message.  All of this is done with the SwitchLinc firmware.  Nothing I know of to alter this.   Need to wait a few seconds before changing ramp direction.

Tue 01/27/2015 10:57:46 AM : [iNST-SRX    ] 02 50 33.95.41 00.00.01 CB 17 01    LTMCON (UP)

Tue 01/27/2015 10:57:46 AM : [std-Group   ] 33.95.41-->Group=1, Max Hops=3, Hops Left=2

Tue 01/27/2015 10:57:46 AM : [D2D EVENT   ] Event [33 95 41 1] [bMAN] [1] uom=0 prec=-1

Tue 01/27/2015 10:57:46 AM : [  33 95 41 1]     BMAN   1

Tue 01/27/2015 10:57:50 AM : [iNST-SRX    ] 02 50 33.95.41 00.00.01 CB 18 00    LTMCOFF(00)

Tue 01/27/2015 10:57:50 AM : [std-Group   ] 33.95.41-->Group=1, Max Hops=3, Hops Left=2

Tue 01/27/2015 10:57:50 AM : [D2D EVENT   ] Event [33 95 41 1] [sMAN] [0] uom=0 prec=-1

Tue 01/27/2015 10:57:50 AM : [  33 95 41 1]     SMAN   0

Tue 01/27/2015 10:57:50 AM : [D2D EVENT   ] Event [33 95 41 1] [sT] [243] uom=0 prec=-1

Tue 01/27/2015 10:57:50 AM : [  33 95 41 1]       ST 243

 

"I'm not sure what BMAN 1 means"

 

This is Begin Manual Up (1).  The BMAN 0 is Begin Manual Down (0)

 

[prairiecode]

Interesting.  So basically this seems to be a firmware bug in the SwitchLinc (where it either isn't sending the second command, or isn't waiting long enough before doing it).  I guess pretty much everyone with Insteon would be dealing with it.

 

It can probably be worked around, but my family might start going, "Oh.  I pushed bright and it got dim.  These new switches don't work so well..."

[LeeG]

This is the first time I have heard the situation described so it likely does not happen very often.