LeeG

Note that I have a detached garage more than 300' wire distance from house. Have several Insteon devices working on both 120v legs with no problem (none are dual band) so the issue with the 2477s devices may be something else.

The I/O Linc Sensor trips with Gnd applied to Sensor. Will that 100'+ of wire between the buildings put the Sensor into an On state, probably but it depends on the total resistance of all the connections. I doubt the manufacture (Smarthome/SmartLabs) will be able to say for sure. Connect them and see is the only way to know for sure.

The Leak Sensor trips Wet based on the "conductivity" of the liquid it is sitting in. Water conductivity varies which results in the Leak Sensor switching to Dry even when sitting in the water that originally triggered the Wet state. Moving the Leak Sensor around in the water will often change the Wet/Dry state. My view is if the Leak Sensor trips Wet it is a condition that needs intervention even if the Leak Sensor moves back to Dry. "What's up with that? If it's wet, shouldn't it stay like that until it sends a Dry?" The Leak Sensor did send a Dry so the ISY is correctly noting the current state.

Insteon does not allow more than one Scene to run at a time, cancelling a Scene if need be. When DMX Relay 2 turns I/O Linc Sensor 2 On it sends a sequence of On commands to the devices assigned to that Sensor. Although the Responders to I/O Linc Sensor 2 normally respond to the first message sent by the I/O Linc Sensor 2, there is a backup message for each Responder which takes a few seconds to complete in case that first message is not seen by all the Responders. These messages will be cancelled when DMX board turns Off I/O Linc Sensor 1 which starts a new Scene Off sequence. The normal Insteon Scene message sequence is this …. Send Group Broadcast message which all Responders react to normally. Send Group Cleanup Direct message to Responder 1 Receive ACK from Responder 1 - if this ACK is not received the I/O Linc Sensor sends another Group Cleanup Direct to Responder 1 - this will occur a few times before the I/O Linc stops with this Responder Send Group Cleanup Direct message to Responder 2 Receive ACK from Responder 2 Send Group Cleanup Direct message to Responder 3 Receive ACK from Responder 3 and so on until all Responders receive a Group Cleanup Direct message which is ACKed. This sequence occurs each time an I/O Linc Sensor turns On or Off. When the next Scene starts before all these messages have been sent and ACKed, these follow-up messages will be terminated. This means that some Responders will not see the Group Cleanup Direct. This is not unique to I/O Lincs. Pressing a button/paddle on two Insteon devices at near the same time will have the same result. It is rare to have two Insteon devices pressed On/Off at the same time. In this situation two I/O Linc Sensors are being activated at near the same time all the time which will have some bad results. The DMX board can delay the change to the second I/O Linc Sensor for a few seconds to allow all the messages from Sensor 1 to complete before starting Sensor 2. An alternative would be to eliminate the Responders being linked directly to the I/O Linc Sensors, having ISY Programs issue the Scene commands. This may make things worse if Insteon comm is poor as an ISY Program turning a Scene On/Off only sends the Group Broadcast message.

"Now, my intention was for this button to be pressed once and the door unlocks all the time after just one press (is this even possible?)" Assign the MorningLinc - Off node to an ISY Scene as a Responder. Set the KPL button to non-toggle Off mode so the button will only send Off commands. The KPL button (assuming it is a Controller of the same Scene) will Unlock only the MorningLinc lockset. What level ISY is being used? Not sure why the KPL load would be affected unless the KPL load was assigned to the ISY Scene as well. EDIT: click the ISY Scene name and be sure the Scene is set to Unlock the MorningLinc lockset.

The KPL Backlight level is NOT used to turn a Secondary button On or Off. Changing the Backlight level affects all buttons on the KPL, determining how Bright an On button is, not turning a button On or Off. Define an ISY Scene and assign one or more Secondary KPL buttons to the Scene as Responders. Turn the ISY Scene On/Off to turn the KPL Secondary button(s) On/Off.

There have been reports of devices turning On which seems to be related to Motion Sensor (or other RF only device) and changing KPL backlight levels. It is believed to be related to an Insteon message becoming corrupted I think. I have not seen that so cannot provide much more than that. Restoring an ISY Backup brings the ISY back to some previous level of information. How much different that information is relative to what the devices understand will be up to you. A File | Restore Devices restores all the devices which will be some time in running but may be the only way to get the devices back to the ISY Backup that was restored. If this is done DO NOT put any RF only device into manual linking mode. After the full Restore Devices command completes all the updates to the RF only devices will be queued. Either a Red ! or Green Icon to the left of each RF only node. Put one device into linking mode, right click the device node and select Write Update to Device. When that device is complete take that device out of linking mode and move to the next RF only device. Put it into linking mode and select Write Updates to Device. Repeat for each RF only device.

The File | Restore ISY will load the backup file. This changes the information in the ISY. It does not restore information in the device(s). Does the current ISY information show the correct information for On Level of the Scene?

The following sequence does NOT stop the Program from being triggered .... If $s_HQ_ON_OFF is 1 And $i_Debounce is 0 It stops the Then clause should $i_Debounce > 0 but all that does is force a False If compare so the Else clause runs regardless of what $s_HQ_ON_OFF is set to. That is the problem with combining True and False conditions in the same Program when the False/Else runs for any False condition rather than only the one specific condition. A collection of Programs cannot be copied to the Clipboard at once.

JSchumann Link Management | New INSTEON Device. Using this was to produce a known device response should the device not work (which was not the case). I would expect Start Linking to also work but since the initial command response comes from the device, if it did not show up it would explain what did not happen but not why. The issue with the previous OP is the lack of a functional Insteon Mesh Network, no coupling. Or perhaps a very long distance between garage and house. Moving the device to the PLM location verified the device was functional.

Take a look at this UDI Wiki entry for establishing remote access .... http://wiki.universal-devices.com/index ... o_Your_ISY

"However, they are far enough apart that I don't believe the RF signal will reach from the ISY/PLM to the garage/Access Point - is that going to be a problem?" The 4 tap Set button test will show if they are in RF range. If not in range will that be a problem, depends on the rest of the system. If the PLM is on leg A and the Access Point is on leg B then no coupling is occurring. "I also have a switched relay outlet and dimming switch to install in the house, and they are both dual-band so will they bridge as well?" The OutletLinc Relay is NOT Dual Band so it will not participate in coupling. The dimming switch (SwitchLinc Dimmer?) is Dual Band. If on the same leg as the PLM no coupling. The 120v leg each device is installed on indicates if they could participate in coupling. Note that a device installed in a wall will not have the range of an Access Point. Run the 4 tap Set button test with the Access Point to see if in RF range of the PLM.

The ISY never changes the IP address. If running in DHCP the router assigns the IP address from the pool of DHCP addresses. Or the router can be set to deliver the same address. I run DHCP and find the IP address assigned by the router stays the same over very long periods of time.

Read the Access Point instructions in the User Guide for doing the 4 tap Set button test. This puts the Access Point into a test mode where it sends an RF signal for approx 4 minutes. Look at the LED on the side of the PLM. If in RF range the PLM LED will be blinking. The color of the PLM LED (green for opposite phase, red for same phase) shows whether the Access Point and the PLM are on the same phase. This is a test only situation. An Access Point is not linked or configured in any way. To see if the Motion Sensor is being seen look at the Motion Sensor - Sensor node under the Admin Console. It will show the state changes as they are seen by the ISY/PLM. If the only thing ever to be used is the Motion Sensor and the I/O Linc then setting up a single Access Point is okay. Seems unlikely that will be the end of the Insteon install when an ISY is involved. Two Access Points should be installed on opposite 120v legs to achieve coupling. Can achieve this with one Access Point and a 2413 PLM but now one location, the PLM is fixed, so placement of the Access Point is more critical because it is the only piece that can be moved around. The Access Point in the garage should be looked at as an RF receiver for the Motion Sensor, not part of the phase bridging process.

A Factory Reset will restore options to default but I did not see anything in the 2 wire user guide that covered that option. Cannot lose anything. After doing the factory reset do a Restore Device to rebuild the link database.

Plug the I/O Linc into the same plug point as the PLM. The I/O Linc is not responding with the expected 02 50 .... response. Could be a phase coupling issue, other electronic equipment plugged into the same circuit as the PLM reducing the PLM outbound signal level, etc. Not likely a device failure at this point. Use New INSTEON Device, enter the Insteon Address, Name of choice, leave Device Type set to Auto Discover. Run the Event Trace at LEVEL 3 as before so the commands can be posted if it does not work

The KPL will be below v.40 being that old. Trigger a Program with the button press and have the ISY Program turn the KPL button(s) Off.

Is the Red blinking the feature being discussed? If so this indicates a comm issue and should be fixed. Factory reset will not turn this feature Off as Off is the default.

The Insteon address of the Leak Sensor is inside the unit. Remove the top as though replacing the battery. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Select New INSTEON Address, enter Insteon Address, Name of choice and select [10.08] Leak Sensor. BEFORE clicking Ok put the Leak Sensor into linking mode by pressing the Leak Sensor Set button until Leak Sensor LED blinks continuously. Click Ok. If it does not add post the event trace.

That feature is not supported under the ISY. It usually gets in the way for a SwitchLinc where the status LEDs are so visible. The ISY expects to be the only Application Controller so using HL to do that one specific device will have to be done before adding the device to the ISY.

Unless there is something pending for the OLD KPL the Admin Console should not attempt to talk to it. Under normal conditions the OLD KPL not being there would make no difference as the "Replace .... with" function assumes the OLD KPL is gone and will not send it commands. If a Scene update is pending I'm not sure what to do. It may take the right click and do the Replace or it may try to do the update first and then handle the Replace. Will have to try that if a pending Scene change is queued. If the queued update is getting in the way, delete the specific change and then go forward. Not sure that will work either if the OLD KPL is totally dead.

What is the firmware of the KPL that has the button turn On even though the Scene has it set to Off? KPLs before v.40 firmware do not support turning a Secondary button Off with a On command.

Click the OLD KPL Primary button, not the NEW one. The NEW KPL node name is a temp name that will be eliminated by the "Replace .... with" option. There must be an equal available to see the "Replace .... with" option. Same number of buttons, same type of device, dimmer for dimmer, relay for relay.

Click the Group Devices option. It will put the Primary node first. If you don't want to run that way click Ungroup Devices to go back to what you have now. Once right clicking on the Primary node the only way I know not to see the "Replace .... with" option is not to have a replacement for the specific device type (dimmer for dimmer, relay for relay). Being Dual Band should not matter.

The Office Fan Light is reacting to a Local Ramp Rate that is not what the ISY thinks the device is set to. Click the Office Fan Light node, move the Local Ramp Rate to something else. Once that change is complete move it to something you want.