LeeG

Insteon does not make a 3 way switch. One SwitchLinc physically controls the load, the other SwitchLinc and KeypadLinc are powered from unswitched 120v and linked to the SwitchLinc that is physically controlling the load. This requires changing the function provided by the wiring in a standard 3 way configuration. One Scene is used, with the SwitchLinc 1, SwitchLinc 2, and the KeypadLinc button being Controllers in that one Scene.

A 3 way usually means 2 devices that can control the load, one physically, one being linked. Did not realize that 3 switches were involved. This is usually referred to as a 4 way circuit. Regardless of the terms used, all the devices that control the load either directly or with a link need to be Controllers in the Scene for all the Controllers to have the correct status. Glad you got it working.

Both devices need to be a Controller of the 3 way Scene. Please identify what type device is the new switch. New KPLs are Dual Band which 3.3.10 does not support.

But that requires removing the ZWave card. As already noted there is one slot for an additional protocol (besides Insteon), either ZigBee or ZWave, but not both.

The specific time trigger is True at 8:30:00 (assuming Sunrise is 8:00:00). It triggers the Program as True and runs the Then which Waits for 5 minutes. It does not trigger the Program True or False at 8:30:01. It never triggers the Program as False. Just as If Control 'xxxxx' is switched On triggers a Program True when On is received from device 'xxxxx', it never triggers a Program as False. Once in a Wait the If can trigger the Program again (not the time trigger if past that time). Should the Sensor change state while in the From/To time range the Program is triggered. False if the new Status is On or True if the new Status is Off. The Program is triggered False at the To time if in the Wait at that time.

The only device in this trace with the (i.e. DB range) message is 16.77.E5. If this is powerline only it suggests a comm issue with powerline only device but Hops Left count does not help with that conclusion. See if 16.77.E5 is on the opposite 120v leg to the PLM. The Hops Left=3 may be related to messages that were moved cross phase by RF or received directly by PLM RF over RF crosslink. Device 2B.A9.0E is showing Hops Left=3 but no (i.e. DB range) messages. Hops Left= count is sure a challenge as it has always been a good indication of comm. Good thing this PLM is not generally available. From the comments I assume there have been comm issues before changing PLMs. The Hops Left counts will make comm evaluation difficult.

"However, I have 5 min wait timer. At 831am the Or second clause now evaluate as False" There is no False trigger for Or Time is Sunrise + 30 minutes It triggers True at the specified time of Sunrise+30. If it triggered False a program could not use it. The False trigger comes from the Sensor turning On or running out of the first time range.

The 02 51 ..... Extended message containing the actual link record does not have the correct address for the link record being read, thus the (i.e. DB range) part of the explanation message. Nor is the actual link record being returned. On the third request the link record is correct. With the I2CS "check digit" of 0xDA on all three Extended messages, which would be incorrect on the first two messages, either the device is sending a bad message or the PLM is scrambling part of the message. Is this device the only one having the problem? What is the type of device? Is this the special PLM?

I'll go through that trace. The Hops Left=3 is not a general situation at 4.2.16 as I am seeing the expected Hops Left=2. Do you have the special PLM with the All On change? What is the type of device where the link database is being read?

That sounds like a good answer to me, thanks. I don't know where mine was in the 21 hour cycle but it would have been luck if it had timed out during the few hours I waited. I also suspect the On versus Off command on the Heartbeat depends on whether the door is open (On) or Closed (Off).

Easy mistake to make. There are various rules/actions which apply to what happens when a physical device is interacted with versus what an application can do through a PLM. All the rules for how an I/O Linc Relay responds in the three Momentary modes do not apply if Direct commands are used. Also Smarthome does not document that behavior in the User Guide because Insteon devices cannot send Direct commands (except for PLM).

A Heartbeat=On indicates a Heartbeat message received. Mine show On from an earlier Heartbeat message before I changed the Heartbeat timing to 5 minutes where no Heartbeat message received. I just rebooted an ISY with 4.2.16 and both Hidden Door Sensors came up blank. I think I have seen one of the Insteon devices with a Heartbeat node cycle between On and Off messages but not sure if that was a Hidden Door Sensor. I check for both On and Off commands in the Program that monitors the Heartbeat node but not sure that is necessary.

Normal Insteon operation. Turn an individual device On/Off, that device alone reacts, regardless of whether linked to other devices. The Scene has to be turned On/Off for the linked (Scene) devices to respond together. EDIT: pressing the button/paddle turns the Scene On/Off as that is the only way an Insteon device can react. Only applications communicating through a PLM have the option to control an individual device with Direct commands or a Group (Scene) of devices with Scene commands.

Both of these Sensors are set to 21.5 hours. I was getting Heartbeat messages. Will have to wait for a full cycle to see if they still work.

'Insteon has no concept of "scene" at all," The term Scene originates with Insteon. From the KPL User Guide Title "INSTEON® 6 and 8-Button Scene Control Keypad with Dimmer" Okay. I thought a solution was needed.

I normally run Heartbeat at the longest interval but moved one back to 5 minutes. Have not received a Heartbeat in over 30 minutes. Makes me wonder if it actually supports such a short interval. EDIT: after more than 2 hours and no Heartbeat went back to the longest value. It could take 24 hours before knowing the Heartbeat is back to where it was.

I suggest doing a Factory Reset on the KPL that is not reacting to a 0% On Level correctly, Delete from ISY and add back. Do NOT use Button Grouping. Post the KPL Controller entry in the Scene that does not correctly turn Off a button LED with 0% On Level. The reason each Controller has to be set is each Insteon Controller in a Scene (PLM for Scene name, other defined Controllers for the same Scene), the Responder Link Record in each Responder is keyed to the Controller Insteon address. SceneC - PLM is Controller KPL1 button C - Controller KPL2 button C - Controller KPL1 button C has a Responder link record keyed to the PLM address KPL1 button C has a Responder link record keyed to KPL2 button C These two Responder link records above in KPL1 for button C can have different On Levels which function independent of each other. KPL2 button C has a Responder link record keyed to the PLM address KPL2 button C has a Responder link record keyed to KPL1 button C These two Responder link records above in KPL2 for button C can have different On Levels which function independent of each other.

There is no external antenna for Insteon. All Insteon powerline and Dual Band RF comm is done ISY to/from the PLM. Where the other devices that had chatter on the same circuit? Thinking of line or neutral connection in the power panel if they were on the same circuit.

The OP mentioned the garage devices were installed 2 years ago. If they are KPLs they are likely not Dual Band being 2 years old.

Clicking on the Scene name and setting On Levels does not affect each Controller. Click the Red button node below the Scene name and set those On Levels as needed.

There have been some 14 ISY images released since 4.0.5. None should have fixed that as no command or command sequence should lock up a device when the paddle is pressed. Sounds like a power issue rather than a command issue. Max Hops=1 Hops Left=0 is an inbound message. Those are expected and good values.

For specific times remove the (random) option If From 7:00:00PM To 11:50:00PM (same day) Then Set 'OutLetLinc Dimmer' On (turns On at 7 PM) Wait 2 hours Set 'OutLetLinc Dimmer' Off (turns Off at 9 PM) Wait 30 minutes Set 'ToggleLinc Dimmer' On (turns On at 9:30 PM) Wait 1 hour Set 'ToggleLinc Dimmer' Off (turns Off at 10:30 PM) Else Set 'ToggleLinc Dimmer' Off Set 'OutLetLinc Dimmer' Off

PurdueGuy I agree with everything you said. Max Hops=3 Hops Left=0 is at the extreme end of the functional scale. It is also changing (Hops Left=1) which is not a good indication.

One approach. Offers random On and Off times. If From 7:00:00PM To 11:50:00PM (same day) Then Set 'OutLetLinc Dimmer' On Wait 2 hours (Random) Set 'OutLetLinc Dimmer' Off Wait 30 minutes (Random) Set 'ToggleLinc Dimmer' On Wait 1 hour (Random) Set 'ToggleLinc Dimmer' Off Else Set 'ToggleLinc Dimmer' Off Set 'OutLetLinc Dimmer' Off The program(s) can be as simple or sophisticated as desired.

The Sensor is switched On indicates motion. A Wait 3 minutes should be in the Then. Also the motion sensor should be in On Only mode so the motion Off does not conflict with what the program is doing. If From 5:30:01AM To 10:29:59PM (same day) And Control 'Motion Sensor-Sensor' is switched On Then Set 'Light Bulb' Fast On Wait 3 minutes Set 'Light Bulb' Off Else Wait 3 minutes Set 'Light Bulb' Off Failed to copy the full Program