LeeG

First, the Backlight level cannot be set for individual buttons. Setting a Backlight value applies to all buttons. The newer devices use Backlight value as a % On rather than an Off/On value. An Off/On setting of 7/15 (0x7F) is 100% On. An Off/On value of 3/15 (0x3F) is approx 50% On level. An Off/On value of 0/0 turns the button LEDs completely Off. It does not logically turn the button Off, only the LEDs Off for those who want a dark KPL at night. Going from 0/0 to 7/15 will turn the LEDs back to the previous button LED On/Off state. That is, a button LED that was On before going to 0/0 will be On when going back to 7/15.

I think running a 4.x.x UI against a 3.3.10 could be an issue. I don't have a 3.3.10 environment to test this. Suggest pulling the UI from the ISY itself and see if that resolves the display problem. http://192.168.2.3/admin using your IP address will pull the UI from the ISY itself. Check the result with Help | About.

I did not see anyone from UDI indicate this as a new problem. From what Chris posted they have not been able to recreate locally. Fixing something that cannot be recreated locally is usually a challenge. Have you been able to run the REST test Chris suggested as a means of getting more information?

If these devices/firmware displayed before but not now I would look at the UI and the level of Java. Has Java been updated since the last time the display was correct? Does Help | About show the correct UI level? If Java has been updated it may be necessary to clear the Java cache including Applications and reestablish the Admin Console. Obviously the base 3.3.10 has not changed.

What are the device types that do not appear below? What are their firmware levels? Not all devices such as Controller Only nodes do not appear below the line. It may also be that 3.3.10 does not understand what the device is if released after 3.3.10 shipped.

The Failed status is the result of not seeing an ACK from a given device. Note the line in Red from 22.CB.5B and this device is marked Succeeded. The remaining devices do not send an ACK or the PLM does not process it. This could be caused by missing Responder link records in the PLM. Could also be caused by one or more CFLs that are noisy when turned On. Thu 03/27/2014 02:01:20 PM : [GRP-RX ] 02 61 19 13 00 06 Thu 03/27/2014 02:01:20 PM : [iNST-SRX ] 02 50 22.CB.5B 24.1B.E3 61 13 19 LTOFFRR(19) Thu 03/27/2014 02:01:20 PM : [std-Cleanup Ack] 22.CB.5B-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 ----- Front House-Garage Test Results ----- [Failed] Garage Outdoor Lights (23 F2 6E 1) [Failed] MB C - Front House (24 16 3B 5) [succeeded] Hallway A - Front House (22 CB 5B 3) [Failed] Front House Lights (23 F2 B0 1) ----- Front House-Garage Test Results ----- Thu 03/27/2014 02:01:29 PM : [iNST-ACK ] 02 62 00.00.19 CF 13 00 06 LTOFFRR(00)

The On condition for a Dimmer is 100%. If all On Levels should be considered use "not Off".

Each Controller (Red node below ISY Scene name) has been clicked and the Responder buttons for that Controller set to 0% On Level?

Take a look at this topic. A few posts in shows the configuration of two Scenes where one button is a Controller and the other buttons are Responders with 0% On level. This topic has multiple KPLs. Look at the Scenes for only 1 KPL. viewtopic.php?f=27&t=11249&hilit=fanlinc

Glad to hear things are working. Thanks for posting back the results.

All the motion sensor options should be set through the ISY. Set Jumper 5 which enables the motion sensor for software updates. Put the motion sensor into linking mode by pressing the Set button until the Red LED blinks continuously. Click on the Sensor node and select the Options button at the bottom of the right side node display. Check Sensing mode: and uncheck On Only mode which causes the motion sensor to send On commands only. The timeout interval now has no affect. The motion sensor will send an On command each time motion is sensed. The motion sensor is dependent on motion. Standing in the area will not trigger motion On. Many users are using motion sensors. Once you get the motion sensor set up correctly it will work with the above programs.

The ambient temp comes back as a number which is * 2 (in .5 degree increments). Divide the response by 2. 144 / 2 = 72.0 degrees.

Set the Motion Sensor to On Only mode and check Sensing mode (Occupancy mode). The motion sensor will issue a motion On without waiting for the timeout interval to expire.

Any additional motion On messages will trigger the Then clause again starting a new Wait interval. The Else runs when the To time is reached which turns the Scene Off If Control 'MS I2CS-Sensor' is switched On And From 6:00:00AM To 6:00:00PM (same day) Then Set Scene 'Scene1' On Wait 1 minute Set Scene 'Scene1' Off Else Wait 1 minute Set Scene 'Scene1' Off

One of the time ranges is covered by this example If Control 'MS I2CS-Sensor' is switched On And From 6:00:00AM To 6:00:00PM (same day) Then Set Scene 'Scene1' On Else - No Actions - (To add one, press 'Action') Create two more Programs with the other time ranges. Insure the time ranges do not overlap. If Control 'MS I2CS-Sensor' is switched On And From 6:00:01PM To Sunset (same day) Then Set Scene 'Scene2' On Else - No Actions - (To add one, press 'Action')

"If Control" should not be used as a Folder condition. If Control is looking at the command that is flowing from the KPL button. Should the Programs only execute when the KPL button is On use "If Status 'kplbutton' is On".

Michel The X10 messages come from the test Program at the bottom of one of my previous posts. It is a test Program only to show if a Program was being triggered. At the time you noted the Program was issuing an X10 On when the Program was triggered. I changed the Program to issue an X10 Off (rather than an X10 On) when the Program was triggered True by the If Status 'EZIO8SSA' is Off. I was issuing a Query using the Admin Console. I have confirmed a Query from a Program does not trigger the Program. No Program trigger in trace below from a Program issued Query. Mon 03/24/2014 02:19:34 PM : [iNST-TX-I1 ] 02 62 0D FC 71 0F 4F 02 Mon 03/24/2014 02:19:34 PM : [iNST-ACK ] 02 62 0D.FC.71 0F 4F 02 06 IOCTL (QUERY) Mon 03/24/2014 02:19:34 PM : [iNST-SRX ] 02 50 0D.FC.71 22.80.0B 2B 4F 00 IOCTL (00) Mon 03/24/2014 02:19:34 PM : [std-Direct Ack] 0D.FC.71-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 03/24/2014 02:19:34 PM : [iNST-TX-I1 ] 02 62 0D FC 71 0F 49 00 Mon 03/24/2014 02:19:35 PM : [iNST-ACK ] 02 62 0D.FC.71 0F 49 00 06 RINPUT (00) Mon 03/24/2014 02:19:35 PM : [iNST-SRX ] 02 50 0D.FC.71 22.80.0B 2B 49 30 RINPUT (30) Mon 03/24/2014 02:19:35 PM : [std-Direct Ack] 0D.FC.71-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 03/24/2014 02:21:51 PM : [ Time] 14:22:18 0(0) Mon 03/24/2014 02:21:51 PM : [iNST-TX-I1 ] 02 62 0D FC 71 0F 4F 02 Mon 03/24/2014 02:21:51 PM : [iNST-ACK ] 02 62 0D.FC.71 0F 4F 02 06 IOCTL (QUERY) Mon 03/24/2014 02:21:51 PM : [iNST-SRX ] 02 50 0D.FC.71 22.80.0B 2B 4F 00 IOCTL (00) Mon 03/24/2014 02:21:51 PM : [std-Direct Ack] 0D.FC.71-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 03/24/2014 02:21:51 PM : [iNST-TX-I1 ] 02 62 0D FC 71 0F 49 00 Mon 03/24/2014 02:21:51 PM : [iNST-ACK ] 02 62 0D.FC.71 0F 49 00 06 RINPUT (00) Mon 03/24/2014 02:21:52 PM : [iNST-SRX ] 02 50 0D.FC.71 22.80.0B 2B 49 30 RINPUT (30) Mon 03/24/2014 02:21:52 PM : [std-Direct Ack] 0D.FC.71-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sorry to have wasted time chasing a 'normal' situation.

pkopp Thanks for posting back. The post by Tom Fitz. (Smarthome forum post) covers those who do not have automation. I think it is easier to just do it through the ISY. Also, as I mentioned in an earlier post, now that ISY has the toggle mode definition a Restore Device will bring the definition back if the KPL is every reset.

"How do I assess the folder condition" Go to Programs | Summary. The Status column shows the current True/False evaluation of the Folder.

That would indicate a new PLM is needed. It may not solve all the comm problems but the ISY can not do anything until it can talk to the PLM.

Once the ISY is in safe mode recycling the PLM alone is not sufficient. The PLM does not signal after a power cycle so the ISY will still assume it cannot communicate with the PLM. Reboot the ISY after power cycling the PLM. It may still go into safe mode if the PLM is dead but it may work if the PLM is intermittent.

KPLs have never been able to have buttons (except load control button) turned On/Off with Direct commands. It is an Insteon limitation. The Direct On/Off commands have no means of identifying which KPL button to turn On/Off. These commands never had that capability. The structure of a link record does have that capability which is why a Scene must be used.

That is the manual method of setting a button toggle mode. It is also described in the KPL User Guide. It is much simpler to press two buttons on the ISY display. Also the Restore Device puts it back if it is accidentally reset.

Use the ISY to set ON/OFF button to non-toggle Off mode.

If Control 'xxxxx' is switched On never produces a Program trigger that is False so the Else clause cannot run terminating the Wait.