LeeG

You can try doing a Restore Device rather than deleting and adding the device back. It would be very strange for all the devices to lose their respective link databases. If the Restore Device does not fix the device then a delete and add is the correction.

Do a Tools | Diagnostics | Show PLM Links Table and then click Count to get a count of the PLM link records. Then do a File | Restore Modem (PLM). Follow that with another Show PLM Links Table and Count. Are the number of link records different. Be sure no Insteon traffic is flowing when doing the Show PLM Links Table as Insteon traffic reaching the PLM can adversely affect the link records read.

All buttons are affected. It is not possible to turn the LEDs off completely..That would make it impossible to visually know whether a particular Scene was On or Off or the action the button press will cause. Obviously the 6 button ON/OFF buttons do not need an LED but the others do as well as all buttons in 8 button mode. The 7/7 is not a value the KPL hardware will react to as it would have the same affect as turning the LEDs off altogether. On and Off could not be differentiated. The hardware is going to keep what amounts to a differential of 8 between the Off and On LED levels. 0/7 is the lowest. 0/8, 0/9, 0/10, up through 0/15 will gradually increase LED brightness. 15 is the highest level for On level. At that point 1/15, 2/15, 3/15 up through 7/15 will continue to increase the LED brightness.

I just changed the LED Brightness on one of my 6 button KPLs on 3.1.16. Is it an 8 or 6 button KPL and what is the firmware of the kPL. There are some number combinations that have no effect as the KPL hardware must maintain a certain spread of numbers to insure a visual distinction between On and Off. What numbers are being set? 7/15 is max bright - 0/7 is minimum

It is included with the Pro version.

AutomationNut If it is not a communications problem either the devices or the ISY PLM have lost link records. For the ISY PLM (or any responder for that matter) to receive device status change messages both the device and the PLM must have the correct link records. You can try doing a Restore Device on one switch and see if that restores communication for that device. Lee

Sorry for the delay. Those files were not meant for human analysis. The TriggerLinc may be 14.40.29. That address does not appear in the previous posted device list. If you have an unused device that can be added to the ISY and then do a Set button link with the TriggerLinc address would be in the last link record. A Show Device Links Table will only have 2 or 3 links with the Set button link being the last.

Could be a defective PLM in that it will not interact with the powerline but does handle RF. Can you turn devices On/Off through the Admin Console. This can also be a router/AV problem blocking data the ISY is trying to push out to the Admin Console. Is Kaspersky or Avast being used?

Are button A and button B on the same KeypadLinc? That should have worked. Does the Admin Console show button A & B turning On/Off as the buttons are pressed? If yes, does the Program that is triggered by button A show a Last Run Time matching when button A is pressed Off? How many responders are being controlled by button A. It may be that the exchange of messages with button A responders was still in progress when the Program issued the Set Scene Off for button B. Try adding a Wait of 1-2 seconds before issuing the Scene Off for button B.

First run Show Device Links Table for a specific device. Then click the Compare button when the display completes. That will compare the link records read against what the ISY thinks should be there. If there are mismatches a Restore Device will bring the device link database to what the ISY thinks should be there. Need to do that for every device, otherwise broken links will be the result. Where there are mismatches likely additional Scene work in the ISY is needed to get the ISY to establish the equivalent links.

If the devices were added to the ISY with the 3rd link option, keep existing links, then no problem. Any Set button links created after the devices were added to the ISY will be a problem eventually as the ISY does not know about them and can overwrite them. Devices suddenly stop working after additional Scene work is done with the ISY. Controllers have link records which point to responders that do not have corresponding links or the reverse. Some really odd symptoms can occur. Plus if a Restore Device is ever done the Set button links done after device add will not be restored. Okay as a test/diagnostic tool (as you did tonight) to use Set button links (and some special devices require it under the ISY) but in general they should not be used in day to day operation. In fact that is how the new InLineLinc link record requirement was discovered a few weeks ago. A Set button link to an InLineLinc showed some data that was not expected but now required.

That is a good idea. 3.1.16 was released today. Once on that ISY image delete the manual Set button link and establish it with the ISY Scene. Only the InLineLinc needs to be written under 3.1.15 and above. The ISY does not know about that Set button link and will eventually run into a conflict with link records if left the way it is now.

Sorry, I was not looking far enough back when you did your post. There was another post with a similar problem that was related to Secondary button controlling the Primary load of the same KPL. That has been resolved by adding the KPL back with Auto Discovery. I'm going to delete my earlier post this topic as it makes no sense.

What ISY firmware is being used? The newest InLineLinc with the higher wattage has special link record requirements. 3.1.15 added that support. The Scene must be written by 3.1.15 or higher if it is the newest InLineLinc.

When the manufacture says incandescent only you assume the risk. Some have used CFLs with no problem. Some have had problems. There is no way to insure the CFLs will not be dimmed. Pressing a Controller button a little too long such that a ramp up or ramp down happens is inevitable. Too many different CFLs to know the results.

Smarthome says don't use them. Worst that can happen is the CFLs or the Dimmer is damaged. Give it a try.

If both the Firmware and UI lines indicate 3.1.16 I don't know why you do not see the popup. Maybe Java level. What OS and browser is being used?

Check Help | About and be sure the Firmware and UI lines both say 3.1.16. If not then clear the Java cache and be sure the URL being used invokes the 3.1.16 Admin Console.

That message indicates the ISY PLM was not able to communicate with the KeypadLinc. Double check the device address entered. If it was communicating before it should work now unless there is new source of powerline interference.

This post removed as it was not related to the topic.

Delete the KeypadLinc and add it back using Device Type - Auto Discover. That way the ISY will know the KeypadLinc firmware is at the required level to support setting the Primary On Level and Ramp Rate when a Secondary button is the Controller.

The KeypadLinc does not sleep so the link records to the KPL will be written. All battery powered devices turn the RF circuitry Off to save battery life. Once Off it is impossible for the RF device to receive any command. It is always best to put the RF device into linking mode before the ISY attempts to write to it. Waiting until the commands are in progress before establishing linking mode could produce unexpected results. If that step is forgotten let the ISY realize no communication is possible marking the node with a red ! or Green Icon indicating pending updates. At that point put the device into linking mode and click the Write Updates To Device option to initiate the update process..

What is the firmware level of the KeypadLinc? Earlier versions do not support Secondary buttons controlling the load to other than 100%.

Below the ISY Scene name that establishes the KeypadLinc button as a Controller, select that KeypadLinc button. For that KeypadLinc button as a Controller all the Responder devices will be listed with the defined Responder On Level and Responder Ramp Rate values. Set the Responder Ramp Rate for the LampLinc to the desired value. The new value should be written to the LampLinc. After that pressing the KeypadLinc button should cause the LampLinc to use the new Ramp Rate value. No (and yes). The On and Off commands honor the Ramp Rate. You can double tap the Controller button to generate a Fast On which will bring the Responder up quickly but it also brings it up to 100% On.

Is the TriggerLinc in linking mode before the Scene changes are made? EDIT: The blue trace entries indicate the device is not responding to the commands the ISY is issuing. This is what a trace looks like if the device is not in linking mode. EDIT2: running 3.1.16 a popup is displayed regarding establishing linking mode when the Device Type TriggerLinc type is selected.