LeeG

jp5150 I like the idea of a combination of direct links for actual load control and a Program response to control the remote KPL Secondary buttons. The load response is what needs to be instantaneous. Unless the remote KPL is in visual range a slight delay in Secondary KPL button LED response will not be noticed. Lee

mikewu99 The Scene number (actually Group number in Insteon hardware parlance) is the same for the ON and OFF buttons when in six button mode. When pressing ON the KPL sends a Group 1 On, when pressing OFF the KPL sends a Group 1 Off. Scenes are based on Group number. That is why the ON and OFF buttons cannot be used to drive different Scenes directly. As Rand already mentioned, ISY Programs can be used to trigger only from an ON button press or only from an OFF button press. There is some latency with this approach compared to a direct device link but it does work well. Lee

jp5150 I was trying to respond to the conclusion that “the only way to have 2 or more KeypadLincs control a group/scene and have the buttons reflect the status of that scene is through a program?â€. In fact that conclusion is mostly wrong. Scene On can turn On multiple KPL buttons including Secondary KPL buttons. A Scene Off can turn Off multiple KPL buttons including Secondary KPL buttons. A Scene On can turn Off multiple KPL Primary load control buttons. All KPL button LEDs stay in sync with these Scenes. The single thing that cannot be done is for a Scene On to turn Off a KPL Secondary button. I suspect there are many Scenes (ratio) that perform the required actions using the first three. Only when mutually exclusive button grouping is being simulated in a responder KPL does the Scene not have the capability required. The Smarthome forum has a specific topic “Insteon Product/Module Requests [?]†under the “Insteon†category for users to post product requests. That would be good place to log your request for additional KPL function. Lee

oberkc A KPL does not honor mutually exclusive button grouping when commands are received from another controller. This is true whether a Direct or Group command is received by the KPL. Mutually exclusive button operation (button grouping) applies only when a button is pressed on the KPL itself. jp5150 Insteon hardware does not support the button responses you are looking for with device to device links alone. This is not an ISY limitation or restriction. A Program will have to be triggered when a KPL button is pressed with the Program issuing Scene commands to adjust the responder KPL button LEDs. Scene links can be used between the KPL buttons to get the opposite button number to turn On/Off (ie 8 button C and 6 button A controllers of the same scene which will produce the necessary cross-links to keep these buttons in sync). To turn Off 6 button B,C,D with 8 button C press On requires the Program to turn Off a Scene with 6 button B,C,D as responders. Same thing in reverse. The program turns Off 8 buttons E,G,H when 6 button A is pressed On. Another approach is to not use device to device links at all, with the Program controlling all button responses in the other KPL. Various ways to do things with automation, just depends on how you want it to work and how much definition you want to do. I prefer device to device links as much as possible to produce instantaneous responder reaction where ever possible.

Partially correct. A Scene with multiple KeypadLincs work fine for configurations where mutually exclusive KPL buttons are not being simulated. Normally when a Scene is turned On by a KPL button press other KPLs that have a button cross-linked to that KPL button would be expected to turn On to stay in sync with the KPL where the button was pressed. I don't know the ratio of Scenes controlling Secondary KPL buttons in a simple cross-linking configuration versus simulating mutually exclusive buttons but my guess is most Scenes work as required. The exception is a Secondary KPL button cannot be turned Off when the Scene responder is sent an On command. The Primary load control button can be turned Off with an On command on other KPLs. Smartlabs would have to change the way KPL firmware works regarding Secondary button response. Or enhance KPLs to respect mutually exclusive button definitions (button grouping) when receiving commands from other Insteon devices.

I have reproduced your symptom. The ISY correctly set the bright level to 00 for the 6 button KPL buttons that have the slider set to 0 which represents Off. However, the KeypadLinc firmware is ignoring the bright level, instead using only the command (On or Off) to determine LED state. Now that I have recreated this I am sure this has been discovered before. A Secondary KPL button cannot be turned Off with an On command. The solution is to define a Scene that contains the KPL buttons as a responder and have a Program turn the Scene Off.

The ISY itself and each Controller can have different responder On/Off/Dim levels. Click on the 8 button KPL button C as Controller listed under the Scene definition and see what each responder is set to for that Controller.

Sorry, I should have included more detail. Yes, you are exactly right. In the New INSTEON Device popup, the Address field is the Insteon Address xx.yy.zz which is on a paper label on the front frame of the KPL or you can note the address that ISY is currently displaying for the KeypadLinc. Name is whatever you chose to uniquely identify the device, such as Living Room KPL or Master Bedroom, etc. The Device Type field is the KeypadLinc type that matches your 8 button configuration, reflecting whether it is a relay or dimmer KPL.

When you add the KeypadLinc specify the Device Type as an 8 button KeypadLinc (relay or dimmer as appropriate). The device Cat/Subcat value identifies it as a 6 button KPL because that is what it was manufactured as. Either the ISY does not check the current button configuration or that aspect of KPL configuration cannot be queried.

Battery life depends on how often motion is detected. Mine is less than 6 months old and going strong. There is no delay in a program working. The low battery may be a problem sending motion messages. Could also be a link issue that is preventing the ISY PLM from being notified of motion. The Event Viewer using the Device Communications Events option should show Insteon messages to the PLM when motion is detected. A flashing LED can also mean the responder, perhaps the PLM, did not ACK the motion message. Could explain the lack of Program trigger rather than being a low battery warning.

All the Dual Band devices send/receive messages on both powerline and RF. Does not matter whether the message originates on the powerline or RF, it is repeated on both. A caution on trying to run without the 120V legs (phases) coupled, circuit breakers alternate 120V legs vertically. I am not a radio expert but from what I remember when I was around radios and antennas it is related to whether the antenna is vertical or horizontal. I have had better results with a TriggerLinc when it is mounted vertically which I attribute to the antenna being oriented vertically rather than horizontally. Also flooring is more difficult to get an RF signal through than walls. In addition to the subfloor there is often another wood flooring on top of that. Floor joints are heavier and closer together than wall studs. I would try mounting the PLM vertically using an extension cord. That might improve the reception.

Only the 2.8.x images have SHN device support and those images are not supported on the ISY-26

MatthewInOK The ID-REQ command is not being processed by the ControLinc. I reproduced the same condition with my ControLinc. Add the ControLinc by using New INSTEON Device and select Device Type ControLinc from the pulldown. Lee

When the Jumper is in place the TriggerLinc sends On and Off commands to Group 1 which are reflected in TriggerLinc-Opened. When the jumper is removed the TriggerLinc sends only On commands, first to Group 1 (TriggerLinc-Opened) when magnet moved away from TriggerLinc, then to Group 2 (TriggerLinc-Closed) when magnet moved along side TriggerLinc. Explanation of Jumper from TriggerLinc User Guide … Jumper When the jumper is installed (default), TriggerLinc will send an INSTEON ON command when it opens and an OFF command when it closes. When the jumper is uninstalled (Multi-Scene Mode), TriggerLinc will activate Scene 1 when it opens and activate Scene 2 when it closes. Note: When installing or uninstalling jumper, battery will need to be removed then reinstalled for the new jumper setting to take effect.

Your choice. The same three device add options regarding existing links are available for a motion sensor add. Might add a fresh battery at the same time after going to all the work to bring the MS down.

I feel certain it found the motion sensor address but since it could not talk to it may have chosen not to add what appeared to be a non-existing device. The ISY would not have known to add it as a motion sensor with three nodes since the type of device could not be determined. You will have to take the motion sensor down as it has to be in linking mode for it to add to the ISY. When you click Ok on the New INSTEON Device popup there should be a prompt with instructions to put the motion sensor into linking mode.

When you added the InLineLinc to the ISY and kept the existing links, did you put the motion sensor into linking mode so the ISY could access it when the ISY found a reference to the motion sensor in the InLineLinc link database? Without the motion sensor being in linking mode the reference to the motion sensor would look like a reference to a non-existing device since the ISY could not communicate with it. I don’t know for sure but would not be surprised what looks like a non-existing device did not get added as a device entry. Also the motion sensor must be added by specifying “INSTEON Motion Sensor†as the Device Type when a motion sensor is added to the ISY. That might be another reason it did not get added. You should be able to add the Motion Sensor using New INSTEON Device, specifying a Address, Name and Device Type.

Either Tools | Diagnostics | Scene Test or right click on Scene name under My Lighting, Diagnostics | Scene Test.

Access Points are not added to the ISY. They have no configuration options and contain no links.

There are a number of posts from UDI folks that recommend NOT Removing PLM. Also that a Reset of the ISY is rarely useful. What do these phantom links look like? The ISY establishes links automatically in both the device and the PLM when a device is added to the ISY. These links support the operation of Programs and allow the ISY to maintain an accurate status of the device.

Yes. It may need to be power cycled for the Local value change through the Admin Console to take effect. Power cycle the device without changing the device state after the Admin Console update.

If you set the device Local value to something like 35% through the Admin Console, does the 35% take effect? It should be changed to something different than the current value. EDIT: if the device will react to the change in Local level through the Admin Console, the Event Viewer can be used to trace that activity and then run the Program and trace the activity associated with the Program statements. That should show any differences in the command sequence being executed between the Admin Console and the Program.

Some routers can be configured by the ISY to establish what you have already done successfully with port forwarding since you can access the ISY from a remote location. Ignore the Enable Internet option.

From the UDI Wiki ... The Process of Replacing a Device Use the "Logon to My INSTEON ISY Now!" weblink, enter your user name and password when prompted to get logged in. Frist add a device that will be the new device. Both devices have to be the same type of device in order for the new device to be displayed in the replace menu. If the device is used in any programs: Click on the Program Details tab. Use Find/Replace to Replace in All Programs the old device with the new device. Be sure to Save your program changes. Under the "Main Tab" expand the Tree "Network --> My Lighting -->" and right click the device that is being replaced. The device must be removed from any folder it is in. Select the new device that was added in the earlier step to start the process.

All of the commands sent to the motion sensor timed out. Note the timestamps between the commands are approx 9 seconds apart. The motion sensor did not receive the commands or the answer did not make it back to the PLM. Try moving the MS closer to a Dual Band device, a new battery in the MS (linking mode draws more current and may not work with a marginal battery) and that the MS remains in linking mode. It is good to wait at least 5 minutes after installing a new battery before attempting to work with the MS.