LeeG

You have three choices, live with the problems, diagnosis the problems or remove Insteon. Obviously your level of frustration is high at the moment. Perhaps sit on it for a few weeks and see if it is something that can be lived with the way it is. If not then the choice is pretty simple, diagnosis the issues or remove Insteon. I have some problems because much of install in the main house is old I1 devices that do not repeat I2 extended commands. Cannot replace the old ICONs with new ones as the line has been discontinued. Cannot replace the ICONs with SwitchLincs because Smarthome vision of White does not match anything else White in the house. I am in the process of removing Insteon from all non-essential areas. I would like to maintain remote control/monitor of detached garage and a few other things. This requires moving to some other protocol which is difficult at present with the limited types of devices in other protocols. Turns out knowing the right thing to do is easy. Admitting it to one’s self and them implementing is the hard part. Whether you chose to stay with Insteon and diagnosis the problems I wish you luck in whatever direction to take. Lots a good folks here that will help with the analysis if you are willing to put in the time and effort on your end. And it will take lots of time and effort on your end.

rpsa Use "If Control xxxx is switched On" rather than If Status. The event trace shows only On commands from the three Groups 1,3,5 that have been traced across the multiple traces that have been posted. If Status is looking for a change in Status which does not happen when the Smoke Bridge is sending only On commands.

The KeypadLinc Secondary button D (?) All On/All Off is a Controller of ISY Scene xxx. The ISY Scene xxx has Secondary buttons A,B,C as Responders set to 100% On Level. The three devices controlled by Secondary buttons A,B,C are also Responders in Scene xxx. Pressing Secondary button D On turns on Secondary button LEDs for A,B,C as well as turning On the Responders of buttons A,B,C. Pressing Secondary button D Off turns everything Off.

Wired Dual Band devices do not have the range of an Access Point. They are installed inside a box with 120v wiring on at least one side of the device. If installed in metal boxes RF coverage is restricted even further. Could try pulling the SwitchLinc out of the box so that there is less potential RF interference. As you say, until good tools are provided by SmartLabs this will be a guessing game of trial and error.

kingwr I have 2477D SwitchLinc Dual Band installed. You have an I2CS SwitchLinc which did not respond as required. Below is what should have happened. The message in Blue is the PLM going into linking mode which should have generated a message from the SwitchLinc (you take no action to cause that message to be sent). The message in Red is missing from your SwitchLinc. Note that a few lines above a message from your SwitchLinc has Hops Left=0. Likely the new I2CS SwitchLinc does not have good communication at its install location. Suggest putting it on an Appliance cord that is plugged into the PLM plug point. It will likely add at that location. May continue to have problems at its original install location as all link management will have to be done with extended commands because it is an I2CS device. Thu 03/21/2013 12:56:49 PM : [22 8b e0 ] Added to list of devices to link to ISY Thu 03/21/2013 12:56:49 PM : [iNST-TX-I1 ] 02 62 22 8B E0 0F 0D 00 Thu 03/21/2013 12:56:49 PM : [iNST-ACK ] 02 62 22.8B.E0 0F 0D 00 06 (00) Thu 03/21/2013 12:56:50 PM : [iNST-SRX ] 02 50 22.8B.E0 19.70.06 AB 0D FF (FF) Thu 03/21/2013 12:56:50 PM : [std-Direct Nack] 22.8B.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/21/2013 12:56:50 PM : [iNST-TX-I2CS] 02 62 22 8B E0 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Thu 03/21/2013 12:56:50 PM : [iNST-ACK ] 02 62 22.8B.E0 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01) Thu 03/21/2013 12:56:50 PM : [iNST-SRX ] 02 50 22.8B.E0 19.70.06 2B 09 01 LNK-ON (01) Thu 03/21/2013 12:56:50 PM : [std-Direct Ack] 22.8B.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/21/2013 12:56:50 PM : [LNK-BGN ] 02 64 01 00 06 Thu 03/21/2013 12:56:52 PM : [LNK-STAT ] 02 53 M(01) gid=00 22.8B.E0 011C 41 Thu 03/21/2013 12:56:52 PM : [iNST-TX-I1 ] 02 62 22 8B E0 0F 0D 00 Thu 03/21/2013 12:56:52 PM : [LNK-END ] 02 65 06

Device 1D 2E 0D did not respond Device 1D 28 A8 responded but at the extreme end of reliability (Hops Left=0) Device 21.08.D8 responded but at the extreme end of reliability (Hops Left=0) Device 1D D5 68 did not respond Device 1D DD EE did not respond The Query Insteon Engine to device 1D.28.A8 got no response. The Insteon network is not working at all for most of the devices and barely for those that did respond. Use an Appliance cord (plug on one end, bare wires on the other) to connect one of the devices that are not responding at all to the Appliance cord and plug the device into the PLM plug point. Does the device work there. If not replace the PLM. I am inclined to believe there is some other problem but the simplest way to verify that is use a new PLM. If I am wrong the PLM is bad and problem solved. If the new PLM has the same problem then the Insteon network will have to be analyzed to identify the actual problem. The PLM can be factory reset and a Restore Modem (PLM) done to rebuild the link database. The link database has no part to play in querying a device so it is not in question at this point. It is the factory reset of the PLM that is functional.

I think your efforts are targeted at the wrong aspect of the installation. Using a different ISY, restoring ISY backups, restoring PLM, etc, none of that is addressing the Insteon network performance which has partially stopped working according to the initial post. Some devices are responding, many are not. Look at the devices for a pattern. Are the working devices and the failing devices on the same or opposite 120v legs, are devices near to or further away from the PLM, do the Access Points still pass the 4 tap Set button test to confirm they are in RF range of each other and on opposite 120v legs. Any new surge suppressor power strips, be sure PLM is plugged directly into an outlet, not a power strip. Are there other electronics powered from the same circuit that are not on a FilterLinc. Try running Tools | Diagnostics | Event Viewer at LEVEL 3. Query and turn On/Off a few of the devices that are working. Do the same for a few of the devices that are not working. Post the event trace. It should provide a picture of how well the Insteon network is performing.

The temperature range can be done with If Status '2441TH - Main' >= 50° (Temperature) And Status '2441TH - Main' <= 64° (Temperature)

JScott Thanks for taking the time to post back. That feedback is so useful to others who are/will read this topic. It is unfortunate that the current garage kit only includes the NC magnetic contact. Some prefer the Sensor to be On when the door is closed but many prefer the opposite. Was so easy when the combined NO/NC switch was standard part of the garage kit.

I'll bet it is. Some of the Search hits are pretty dated. Likely anything dating back to 2009/2010 no longer applies. Those hits discuss the use of the "Mutually Exclusive Buttons" button which no longer exists (doc is usually the last thing to get cleaned up). The March 2013 entry does describe the Buttons Grouping button which does work as described. However, the KPL function for establishing Mutually Exclusive (Radio) buttons is better implemented with Scenes as the Warning at the top of the Buttons Grouping display indicates. The use of Scenes setting the On Level to % 0 is much simpler than trying to understand all those vertical lists of buttons and the selections below. Anytime you find yourself running in circles with the doc post the question. There are lots of good folks on this forum and UDI tech support is always an option. You will not find a better tech support group.

The v.9B PLM firmware does not eliminate the duplicate message traffic with Hops Left=0.

JScott I reread your first post. With the Sensor turning On with the Query I would check the I/O Linc options in use. This sounds much more like Trigger Reverse is in use than duplicate Relay status messages. The Relay is Off in a garage application except for the second or so the Relay starts door movement. If a duplicate Relay message was the cause it would be interpreted as Sensor Off rather than Sensor On.

JScott Absent an event trace it does sound like the same situation unless you are using Trigger Reverse. Use of Trigger Reverse is a separate issue. I received a new 2413S PLM yesterday with firmware v.9B. I'm hoping to replace the PLM in my test bed this weekend to see if the v.9B firmware is any better at catching the duplicate messages. I’ll post the results when testing with the new PLM is complete.

The individual devices must be added to the Program

danncas Sorry, I used the wrong nomenclature for the Group Devices function. I incorrectly referred to it as Group Buttons rather than Group Devices. When a right click is done on the KeypadLinc Primary node it is Group Devices or Ungroup Devices. The second image in your last post with the "-" to the left of the KeypadLinc Primary node is what happens when the Group Devices option is selected. Since the posted image shows that option in effect the option shown when a right click is done is Ungroup Devices to reverse what was done with Group Devices . The first image in your last post is what is displayed when Buttons Grouping button is clicked. This option was used in the very distant past to define Mutually Exclusive (Radio) buttons. This option SHOULD NOT BE USED. There is a Warning at the top of the display (partially cut off in posted image) that Scenes should be used instead. Neither Group Devices nor Buttons Grouping has anything to do with a button being an All On or All Off button. To have a button be an All On or All Off simple make that button a Controller of an ISY Scene that has all the devices that should respond to the button press as Responders. Not considering the 6 button KPL ON/OFF buttons as they are exceptions, any given KPL button can be in default Toggle mode such that pressing the button On makes the button All On and pressing the button Off makes the button All Off. If a given button should be dedicated to All Off for example simply define that button as non-toggle Off mode. In non-toggle Off mode the button only ever issues an Off command. The 6 button KPL ON/OFF buttons by their nature are already in non-toggle mode. Pressing the ON button always sends a On and pressing the OFF button always sends an Off. The ON/OFF buttons CANNOT control different Scenes. If they are used for All xxx function, the ON button is All On and the OFF button is All Off. The devices controlled by an All On or All Off button are simply what devices are defined as Responders in the ISY Scene controlled by the button.

Just to be sure about what is being discussed, there is a Group Buttons function which is accessed by doing a Right click on a KeypadLinc button node in the My Lighting tree. Using Group Buttons puts a "+/-" sign to the left of the KeypadLinc Primary node and places all the KeypadLinc Secondary button nodes below the Primary node. Buttons Grouping is a button at the bottom right side of a node display. It is described above but SHOULD NOT BE USED. To achieve Mutually Exclusive/Radio buttons use an ISY Scene to establish the button relationships.

Using a SynchroLinc is another option. With the intermittant power usage involved in a wash cycle it takes some ISY Programming to not produce a complete message too soon but others have done it.

The specs on the relay contacts indicate 5A @ 30V AC/DC. So long as the current draw does not exceed 5 Amps it should be okay.

It is not normal. Usually caused by something blocking the push of data from the ISY to the Admin Console such as Kaspersky or Avast AV or something with a firewall.

The I/O Linc Sensor and I/O Linc Relay operate as separate devices. The Sensor turns On/Off based on the dry contact switch connected to the Sense Input. The Relay Responds to On/Off commands independent of the Sensor state. There can be a relationship between the Sensor and the Relay but that is not a requirement.

This statement Set 'X10 Bridge - 0 / 1E.7B.6B.1' Off performs no function. The EZX10RF nodes are Controller Only nodes. They cannot be turned On/Off from a Program. If the Timer has been set for this X10 code the node will return to Off when the timer expires. Otherwise an X10 Off must be received by the EZX10RF to set this node Off. EDIT: yes, a disabled Program runs when invoked from another Program. It will not trigger by the If section if disabled.

Try an Off/On number of 0/1 if using the Admin Console. Or 1% if using a Program. The LEDs of buttons that are On cannot be turned Off completely. Otherwise buttons that are On could not be distinguished from buttons that are Off.

Each Controller in a Scene has a unique set of Responder On Level and Ramp Rate values. From the post it sounds like you set the Scene (when PLM is Controller) Responder On Levels and Ramp Rates. Now click on the Red KeypadLinc button node name below the Scene name. There are another set of Responder On Level and Ramp Rate values for when the KPL button is the Controller. Set those values as desired.

The Adjust Scene statements change the Responder On Level for Scene Bedroom.1 but they have no direct effect on the KeypadLinc load. They have an effect if the Scene is then turned On. The KeypadLinc load can be controlled using Direct commands that turn the KeypadLinc On to the various On Levels. No Scene needed. NOTE THAT CONTROLLING AN OUTLET WITH A DIMMER IS AGAINST CODE AND DANGEROUS. An OutletLinc Dimmer has a special magnetic key that must be in place for the OutletLinc Dimmer to affect the load level.

Don't think that will be a problem. I would use the same 24v AC Zone power for both EZFlora devices. Make sure the AC connections are the same on both devices.