KA_HappyPlace Posted December 5, 2012 Posted December 5, 2012 I installed two 2477D Insteon switchlinc dimmers to control kitchen lights and seem to have sporadic problems with the switch on the "non-load" side. The load side is V.41 and the non load is V.38. I'm wondering if that could cause problems and if there is a way to upgrade Insteon devices to the same version. Steps taken so far to resolve are as follows: Factory reset on both 2477D's. Restore device with isy99 Any suggestions besides locating finding another 2477D in my system with the same version and physically switching the dimmers? Thanks, Keith
LeeG Posted December 5, 2012 Posted December 5, 2012 Insteon device firmware cannot be updated. Swap the location of the two switches. I think you will find the problem is related to the location rather than firmware level.
KA_HappyPlace Posted December 8, 2012 Author Posted December 8, 2012 I don't follow that swapping the location has anything to do with this issue. Please explain.
Brian H Posted December 8, 2012 Posted December 8, 2012 If you swap the two switches and the problem is still in the original location. You have a power line signal problem to that location and it is not firmware related.
LeeG Posted December 8, 2012 Posted December 8, 2012 Thanks Brian, exactly what I was trying to say. All kinds of Insteon devices at various firmware levels can be cross-linked without concern for type of device or firmware level. A ToggleLinc can be cross-linked with a SwitchLinc, a SwitchLinc can be cross-linked with an ICON, a KeypadLinc can be cross-linked with a SwitchLinc, a Dimmer can be cross-linked with a Relay. The concept of one Insteon device controlling another Insteon device is so basic a function that it does not matter type of device or level of firmware. Swapping the switch locations is an easy way to verify. They do not have to be relinked or changed in any way other than physically changing their respective install points. If this was originally a 3-way circuit using standard 3-way switches the wiring had to be retasked to provide unswitched power to one of the locations. There could be issues with the way that was done. If this is a new logical 3-way install the SwitchLincs could be on different circuits, even different 120v legs (phases) which brings coupling into play. All kinds of possibilities unrelated to firmware levels.
KA_HappyPlace Posted December 8, 2012 Author Posted December 8, 2012 Thanks guys. I hadn't considered the switches being on different phases. I have 51 devices, all Insteon of which 3/4 are dual band. Plus two access points (2443) verified to be on the 2 different phases. This was a single switched light that I made into a 3way. One switchlinc has the load, the other does not. They were cross linked via isy99i pro. There just seems to be a "delay" in responding. The non-load switch is in a gang box with a keypadlinc and another switchlinc dimmer neither of which give me problems. And the two switchlinc's in question are within 8 feet of each other so I would think the RF would help. By the way, should the Access Points be linked with the isy99 as I cannot seem to get them linked or do they just "function" without linking? Thanks again, Keith
LeeG Posted December 8, 2012 Posted December 8, 2012 Access Points are not linked together and not linked to the ISY PLM and not added to the ISY. They function as soon as they have power. The Delay is in the linked SwitchLinc response? Insteon devices automatically retry device to device control commands. If the non load SwitchLinc is not getting an ACK from the load control switch it will retry up to three times. This can produce an observable delay. The Scene (Group) protocol starts off with a message that all linked responders should react to. This is almost instantaneous but the initial message has no ACK because multiple responders could be reacting. The initial message is followed up with a message directed to each responder individually. Normally this message has no physical affect because the first message caused the responder to react. If the first message was missed do to mesh network problems one of the three follow up message attempts usually work but this does result in a slower responder action as it takes time for a message to timeout and be retried.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.