LeeG

Make sure the KPL Primary node is being clicked to see the Replace .... With option. What does Help | About show for UI line? There is a 4.0.11 UI that may work better.

That is fine in this situation. The UI (Admin Console) was updated to pick up support for some items that only needed UI updates.

The Low Batt node on each Insteon Motion Sensor may show low. The Motion Sensor sends the Low Batt message once so if the ISY is rebooted it will be lost. The idea being an email or something visual such as a KPL button is turned On when Low Batt is turned On.

It does appear we are talking about different commands. 20070810a Removed KeypadLinc and KeypadLinc Relay SD 0x1F02 to 0x1F06, and 0x2Fxx to 0x33xx, added same functionality to ED 0x2E00. Added KeypadLinc and KeypadLinc Relay SD 0x1F02 Get Signal-to-Noise Value. The 0x1F command is a Get Operating Flags rather than setting something. My information is old so your information may be later than my 2007 level command document.

If on Maverick take a look at this viewtopic.php?f=25&t=12505&start=30

The Insteon "Controller" link in the KPL that represents the button being pressed does not have the ability to affect the status of the button LED. Not an ISY choice. Using the Program to turn the button LED Off is the approach. Unless you want to assign the button to non-toggle Off mode. The button LED blinks twice and turns Off. The Program is still called, just looking for an Off command . Again, if a 6 button KPL the ON button does not allow that.

The device types have to be the same, Dimmer for Dimmer, Relay for Relay. Not a problem replacing an ICON Relay with a SwitchLinc Relay but replacing a Dimmer with a Relay (or reverse) is not supported.

The ISY has no understanding of a Hub. Linking the I/O Lincs to the Hub with the Set button will make the ISY links information invalid. Delete and add the I/O Lincs back using the 'erase existing links' option.

My text changed on purpose.

sloop I don't think you care what it is says! The topic is "craplincs" and it does not matter what they said. I tried to provide the technical data and all you want to hear "IS THAT WHAT THEY SAID". I sure hope you do not turn this web site into the same crap as you did on Smarthome. Good Luck!

"ounds like the new devices are not backward compatible with the old - at least in the protocol - is that what i am hearing?" Not sure what is meant by "at least in the protocol". Old and new devices work fine with each other at the Set button linking perspective. Applications must be different as commands that were once there have been removed with I2CS.

Devices started shipping from March 2012 have been I2CS. It took months for the entire line of devices to receive I2CS firmware. The old Peek/Poke commands (read/write 1 byte at a time) have been removed from devices completely. Set button linking between devices continue to work so using old devices with new devices work. Within whatever limitations exist for Set button configuration, exist today. Applications such as HouseLinc (now free), Indigo, ISY, etc have moved to Extended commands (8 byte read/write) for device configuration and link management.

What is a craplinc?

No. You can activate an ISY Program with a SwitchLinc Dimmer On and set the device to Full On in response.

Here is the link to the UDI Wiki http://wiki.universal-devices.com/index ... r_Messages I do not use the ISY email so not much more I can offer.

Make sure message has both Subject and Body. Either being empty will stop the email. Look at Tools | Error Log.

The technique is good. Only change is click Start Linking first. This puts the PLM into linking mode (LED on PLM is blinking) and displays a Start Linking popup with a Finish button at the bottom of the popup. Put each ToggleLinc into linking mode which will display the Insteon address in the popup window. Click the Finish button to add the ToggleLinc(s) to the ISY. Are you certain these are Insteon devices and not X10?

A Program is needed for that type of logic where all devices being Off is necessary for a button to be Off. There is an approach that folks on the Smarthome forum have discussed. Set the KPL to 8 button mode but leave the 6 button frame in place. This allows buttons A&B to be controlled totally separately from G&H. This eliminates the relationship between ON and OFF buttons that exist when in 6 button mode.

If referring to the ON and OFF buttons being configured separately I doubt that will ever happen. Although separate buttons they share the same Group number making independent identification and configuration impossible. If referring to the Secondary buttons they can be configured individually. Each button can be set to a different toggle/non-toggle/On Off mode.

fba The ISY does not support that command. It is a bit wise command that affects all the KPL buttons making it difficult to use. A Program using such a command would have to be aware of manually operated KPL buttons (whether On or Off) as well as buttons operated by Scenes running independent of the Program in question as well as Programs affecting other buttons. I don't see the ISY implementing this command. The Insteon Direct On/Off commands which would be the logical candidate have no means of indicating which KPL button should react to the command. Thus the need to use a Scene for Secondary KPL button On/Off control where a specific button is identified.

I believe setting the ON/OFF button to non-toggle Off mode will result in OFF button being dark when the KPL load is Off. This is covered in the Smarthome forum if you have access.

The Program should not be setting the BackLight level. Backlight determines how bright the On/Off levels are for the entire KPL. The Program should be turning the Secondary KPL button On or Off. Insteon Direct commands cannot be used as Direct commands have no means of indicating which KPL button should respond to the On/Off. Define an ISY Scene with the KPL button as a Responder. The Program turns the ISY Scene On/Off to turn the Secondary KPL button On/Off. Using Adjust Scene is more complex when using cross-linked devices. The Local On Level controls what happens to the device where the paddle is pressed. The Responder On Level controls what happens to the device that is cross-linked. This means that four Adjust Scene statements are required for each change in On Level. In Scene 'device1' Set 'device1' 40% - this sets the Local On Level for device1 In Scene 'device2' Set 'device2' 40% - this sets the Local On Level for device2 In Scene 'device1' Set 'device2' 40% - this sets the Responder On Level for device2 In Scene 'device2' Set 'device1' 40% - this sets the Responder On Level for device1 Note that for a device to appear as an option for use in the first parameter the device MUST be a Controller of an ISY Scene. Even if the device is not linked to anything it still must be a Controller in a Scene (dummy Scene if you will). This allows using the device node name in both the first and second parameters of the Adjust Scene statement to set the Local On Level.

The heartbeat message can contain On or Off depending on the Wet/Dry state of the Leak Sensor when the heartbeat message is sent. A Program testing for heartbeat should check for both conditions. If Control 'Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours Send X10 'A10/All Lights On (5)' Else - No Actions - (To add one, press 'Action')

First thing to verify is the button Scene works. Using the Admin Console select the button Scene, turn the button Scene On and Off several times and verify visually the KPL button LED follows as expected. Next is to split the Program into two Programs. The combination of the Wait which may be too short and the changing of the various device Status may make the execution of the statement(s) after the Wait inconsistent. In the Then clause of the current Program invoke Program 2. In Program 2 put a Wait of 10 seconds followed by the Scene On. The 10 second period is for testing only at this point.

You have to Remove the node from the Scene and then add it back as a Controller. Insteon allows a node to be a Controller of only 1 Scene so be sure the node is not already a Controller before doing the Remove.