LeeG

Can you post the "Heartbeat Warning" definition.

Use New INSTEON Device. Enter Insteon address, Name of choice, and default Auto Discover. Put Open Close Sensor into linking mode. Click Ok on New INSTEON Device popup.

kwindrem Good to hear you have it working. Scene XXX On and Scene XXX Off work the same whether from a SwitchLinc with a single paddle, a single KPL button working in the default Toggle mode, or using multiple buttons as you are. Once the principle is understood it usually applies to many Insteon devices.

A KPL Secondary button can be set to "non-toggle Off" such that when the button is pressed an Off command is always sent to the Scene.

It looks like something else is powered on some cycle that when On device 33.65.D7 does not either receive or cannot send response. There is no response for multiple Query and 0x2F commands. When 33.65.D7 does ACK the Hops Left=3 indicates good comm. See what else is powered that turns On and Off.

I have a second panel that covers the other end of the house (with AC on that panel) and a third panel that covers a detached garage. Should not be a problem. I do not have separate coupling on either of the secondary panels.

The Event Trace does not have the expected sequence of messages. The message in Red below is missing which should have been generated when ToggleLinc Set button was pressed for 3-5 seconds. Mon 03/28/2016 08:09:10 PM : Start Insteon Device Linking Mode Mon 03/28/2016 08:09:10 PM : [LNK-BGN ] 02 64 01 00 06 Mon 03/28/2016 08:10:10 PM : [LNK-STAT ] 02 53 M(01) gid=00 33.14.23 0141 43 Mon 03/28/2016 08:10:10 PM : [33.14.23 00] Linked device type=01.41 fw=43 Mon 03/28/2016 08:10:10 PM : [33 14 23 0 ] Added to list of devices to link to ISY Mon 03/28/2016 08:10:10 PM : [33.14.23 00] Device already added, ignored Mon 03/28/2016 08:10:10 PM : [LNK-BGN ] 02 64 01 00 06 Once the necessary Dual Band devices have been powered on and confirmed they are on opposite 120v legs I suggest using New INSTEON Device. Enter Insteon address of device being added to ISY. Enter Name of choice and leave Auto Discover. Be sure Event Trace is in LEVEL 3. Click Ok and trace activity. Post event trace if device does not add successfully. Be sure the PLM is not on a circuit with other electronics that could interfere with Insteon traffic.

That is a message from the ISY to the PLM to terminate linking mode. When Link Management | Start Linking is clicked the PLM is put into linking mode (PLM LED is blinking). This is done so the device Set button press is sent to PLM/ISY. Regardless of whether a device Set button is pressed, when the Finish button is pressed the ISY takes the PLM out of linking mode (02 65 06).

jerlands The 02 54 03 is PLM Set button pressed and held The 02 54 04 is PLM Set button released.

If the ISY was powered up and then the PLM connected to the ISY, power down ISY and PLM. Power up PLM, wait 30 seconds and power up ISY. Bring up Admin Console. Click Help | About and verify that Firmware and UI (Admin Console) are at the same level. What does Firmware and UI show for level of each. Since it sounded like you have no Insteon devices as yet, what are you trying to accomplish with no devices? The PLM is connected to the ISY.

Completed test where Motion Sensor triggered a Program multiple times before .5 minute time elapsed. Motion Sensor did not issue an Off command until the .5 minutes had elapsed without sensing motion.

The Motion Sensor has no option for sending an Off 2 seconds after the On. The smallest increment is .5 minutes (30 seconds). Try a new battery.

Each Tool in the ISY serves a purpose. The Event Viewer will show the messages received regardless of whether the message reflects a state change.

jgcharlotte "This is nuts. The sensor is sending just one 'on' command, then the program generates multiple 'lights on' commands" I'm concerned about being moved in the wrong direction by that log. You cannot tell what is actually happening because the log is showing change in state, not what messages are actually flowing from device. The Program may be triggered by messages that do not appear in the Log because state did not change. The Log is good but not for knowing what messages are actually flowing. Need to run Tools | Diagnostics | Event Viewer at LEVEL 3 to follow actual messages being generated and what they caused to happen.

Many Insteon devices use multiple Group numbers. The 8 button KPL uses 1-8, the 6 button KPL uses 5 Group number, 1, 3-6. The I/O Linc Relay can be Queried to get the node specific Group number. The hardware information also has this data. Here is a Query of an I/O Linc Relay. Thu 03/24/2016 08:59:40 AM : [iNST-TX-I1 ] 02 62 15 BB 5A 0F 19 01 Thu 03/24/2016 08:59:40 AM : [iNST-ACK ] 02 62 15.BB.5A 0F 19 01 06 LTSREQ (01) Thu 03/24/2016 08:59:41 AM : [iNST-SRX ] 02 50 15.BB.5A 22.80.0B 2B 00 00 (00) Thu 03/24/2016 08:59:41 AM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/24/2016 08:59:41 AM : [iNST-TX-I1 ] 02 62 15 BB 5A 0F 19 00 Thu 03/24/2016 08:59:41 AM : [iNST-ACK ] 02 62 15.BB.5A 0F 19 00 06 LTSREQ (LIGHT) Thu 03/24/2016 08:59:41 AM : [iNST-SRX ] 02 50 15.BB.5A 22.80.0B 2B 00 00 (00) Thu 03/24/2016 08:59:41 AM : [std-Direct Ack] 15.BB.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/24/2016 08:59:41 AM : [D2D EVENT ] Event [15 BB 5A 2] [sT] [0] uom=0 prec=-1 Thu 03/24/2016 08:59:41 AM : [ 15 BB 5A 2] ST 0 Also note that the I/O Linc Relay does NOT signal back to the PLM/ISY when the Relay changes state. A Program can turn the Relay On, the Relay timer turns the Relay Off, and the ISY Status will show Relay On as that is the last command sent even though Relay is actually Off. A Query is required to get actual Relay state into ISY Status. .

Look at the Status of the node the ISY is showing. Then Query node (right click node and select Query) to retrieve actual state of device. There are specific steps that must be followed when replacing a PLM. If not followed the ISY Status could be different from actual device state. Could also be a comm issue. What type device is controlling the pool heater?

That takes the ISY Status of the device. Check the device node for the Status. Could be different from device state if there are comm issues or link database problems.

Example from Wiki sys.node.11 22 AA 1.ST

I think the Insteon address should be in caps Pool Heater is ${sys.node.30 4A 13 1.st}

My EZSrve has its Insteon address on the back of the device.

I would Delete the device. The PLM used by the ISY never appears as a device. Tools | Diagnostics | PLM Info/Status displays the ISY PLM information.

svetter The PLM should not be listed as a device under ISY nor should it appear as a device in a Scene. Is this the PLM the ISY is using? Again, the PLM used by the ISY should never be listed as a device nor appear in a Scene.

Verify that the correct values are being set. For the ISY Scenexxxx, need to first click on Red Controller A. Set Controller A and Controller B to 100%. Then click on Red Controller B. Set both Controller A and Controller B to 20% Scenexxxx Controller A Controller B

Right click on Program name, last entry is Copy to Clipboard. Paste into forum post.

Some where update is required if PLM has Green 1011 Icon. Check other devices for similar Icon. Here is example of cross linking two devices under ISY Admin Console