Devices work but not when in a scene?

[windrockwater]

Hello,

Sandy fried MANY of my insteon devices. So I am replacing them and updating my ISY99 programs, etc. I replaced two outletlincs (that operate some low voltage lighting). They are now version v.42. They seem to be fine as individual control and I can control them fine if I select them under My Lighting. But if I add them to a new scene (they automatically go in as responders) the scene will actually control them. The admin panel shows the devices as 'ON' but if I query them they are actually OFF and update as OFF. I hope this makes sense. Why will devices not be responding to scene control but respond just fine as individual devices?

 

Any ideas?

[LeeG]

What ISY firmware level is being used?

 

Those will be I2CS devices which may require a later level of ISY than is being used.

 

Controlling an ISY Scene does not have the automatic retry associated with a direct command. Also link records are required for a Scene to function which might not be there if the ISY firmware is too old.

 

To control low voltage lights the OutletLincs must be relay type which can only be a Responder.

 

Use the 4 tap Set button set on the Access Points to insure they are working correctly. Verify they are in RF range and on opposite 120v legs.

 

Also try a Scene Test for a Scene that does not control the OutletLinc. If the Scene Test fails either there are link record problems or powerliine issues such as no phase coupling anymore.

[windrockwater]

I just managed to get 3.2.6 installed yesterday. After I saw your post I decided to upgrade to the latest 3.3.4. I tested my Access Points and they seem to be working fine, on two floors, and on the two phases. I do seem to be having trouble with some other scenes. For example a KPL button that controls a scene no longer seems to be controlling the scene (none of the devices in the scene respond to the button press).

 

I do not know what is quirky about these outletlincs but they do not want to join a scene (via a KPL button or thru ISY admin panel. BUt they are quick and resposive to device control under My Lighting. There are a few switchlincs (v3A) too that are doing the same thing. Any ideas?

 

Thanks for the help BTW.

[LeeG]

If the OutletLincs were added before the I2CS ISY support was installed they will not be handled correctly. Try a right click on node, select Diagnostics | Query Insteon Engine. Then remove the OutletLinc from the Scene and add it back.

 

If it does not work right click node, select Diagnostics | Show Device Links Table. When display is complete click Compare button. It there are mismatches (other than last End Of List record) the OutletLinc will have to be Deleted and added back under 3.3.4 to get it recognized as an I2CS device.

 

For the KeypadLinc button not turning On the Responder devices, do a Show Device Links Table on the KPL Primary node, followed by Compare when the Show display completes. If there are mismatches/missing links (other than End of List link) try a Restore Device to get the link records back in the KPL. Could be a problem with the Responder device links but if multiple responders are not reacting more likely a KPL link record problem.

[windrockwater]

If the OutletLincs were added before the I2CS ISY support was installed they will not be handled correctly. Try a right click on node, select Diagnostics | Query Insteon Engine. Then remove the OutletLinc from the Scene and add it back.

 

If it does not work right click node, select Diagnostics | Show Device Links Table. When display is complete click Compare button. It there are mismatches (other than last End Of List record) the OutletLinc will have to be Deleted and added back under 3.3.4 to get it recognized as an I2CS device.

 

For the KeypadLinc button not turning On the Responder devices, do a Show Device Links Table on the KPL Primary node, followed by Compare when the Show display completes. If there are mismatches/missing links (other than End of List link) try a Restore Device to get the link records back in the KPL. Could be a problem with the Responder device links but if multiple responders are not reacting more likely a KPL link record problem.

 

That worked just fine (the both your first suggestion and for the KPL fix) Awesome. Thanks alot.