LeeG

I did a quick test of those combinations and confirmed your observations. Note that the only change in 4.1.2 is to use 0/0 as a total Off for all button LEDs, whether the button is logically On or Off. That was the object of this topic, to be able to turn all buttons physically Off at night without having to turn each button logically Off. There is a unique command executed to make 0/0 have all button LEDs Off. Other than that no changes were made in how the KeypadLinc reacts to the other combinations. I suspect that the LEDs in the KeypadLinc have the same limitations larger LED bulbs have in not being able to dim them below a certain level. Makes it impossible to have a button that is Off at the very dim level you are looking for.

Looks like you need to upgrade to the Pro version.

Unfortunately I don't know what is being invoked on the iPad to be able to test the same thing here (albeit not on an iPad). Hopefully someone else can jump in here or if you identify exactly what is being invoked. The HTML interface does not guide me to what is actually being used on the iPad.

Look at the 4.1.2 announcement, first post. It has the URL.

The limit is 256 devices/scenes. How many do you have now?

The backlight On level is what is being defined. The button Off LED level follows the On level. The Off LED level is approx 8 increments below the button On level. Have a few buttons On and a few Off and watch how they look as the various backlight On levels are set. The change in backlight level is immediate (as fast as the ISY can issue a command and the command reach the KeypadLinc). Set Off=1 On=15 (1F); then set Off=2 On=15 (2F); then Off=3 On=15 (3F). The max that can be set is Off 7 On 15 (7F) which is 100% backlight On level. As the backlight On level increases, so does the backlight Off level.

Sorry for the confusion. The post that described setting the Scene level was in response to the first post that indicated the Scene On/Off was going to 100% where the Keypadlinc was going to the defined values. The later post indicated setting the Scene responder values but did not mention setting the KeypadLinc responder values. In insteon each Controller has a unique set of responder values. The PLM is the Controller when the Scene name is used. The KeypadLinc button is the Controller when the KeypadLinc button is pressed. Of course the responder values can be the same for both Controllers but Insteon allows each Controller to have a different set of responder values.

racekarl The newer devices treat those On/Off numbers as a combined On percentage value, not an On and Off level. For example Off=3 On=10 is really a hex number of 3A which is a percentage of On level rather than an Off/On definition. Changing the low order digit (what the Admin Console describes as On level) has a relatively small effect that may require taking off the button cover to observe small changes. It is also easier to see the changes the low order byte makes when viewing the KeypadLinc in low level lighting. Setting the backlight level applies to all buttons on the KeypadLinc. An individual KeypadLinc button backlight level cannot be set. This is the command issued when setting the above 3A definition Fri 01/17/2014 05:49:14 PM : [iNST-TX-I2CS] 02 62 22 8B E0 1F 2E 00 01 07 3A 00 00 00 00 00 00 00 00 00 00 90

I would start from scratch. Really a personal choice on your part if it actually works.

I have questioned the ability of move something as old as an ISY-26 backup file into today's world. UDI response was that they try and keep the ability to role the old files into the latest hardware; depends on the firmware levels which were not identified.

You are very welcome.

Do not run the two ISYs at the same time. Assuming the ISY-26 backup will install on a 994i, the PLM address will have to be changed in all the devices. As that happens the old ISY will no longer be operational.

A PLM with v.52 firmware is very old. I think the latest 2413S has v.9B. I would get a new 2413S PLM (only one being sold). The 2413 does not provide power to the ISY because the 2413 is Dual Band. You will need an external power supply to power the 994i. Cannot say whether the ControLincs will work better without knowing why they are not working now.

The xxx Ctr nodes are Controller Only nodes. They have no state information to query. The ISY logs whatever the thermostat sends in terms of On or Off commands for these nodes. Until the thermostat sends something for the particular node it will be blank. The image I posted has a blank Cool Ctr node as the thermostat has not called for AC since the ISY was last booted. It will remain blank until the change in season when I switch to Cool mode.

It does on mine which is of no use to your situation. What ISY firmware and UI is being used? Click Help | About

From the post Cool Ctl is not On, it is blank. Means the thermostat has not called for Cooling since the ISY was booted the last time. The thermostat mode indicates whether the thermostat is controlling heating or cooling. Heat Ctl node On indicates the thermostat is asking for Heat from the HVAC. In Heat Mode the Heat Ctr node will cycle On/Off as the ambient temp moves Down/Up.

Each Motion Sensor should have three links that start with E2 and point to the PLM. Like the first three link records shown here in blue M2-Sensor / 27 B5 10 1 0FF8 : E2 01 1E.45.BE FF 1F 01 0FF0 : E2 02 1E.45.BE FF 1F 02 0FE8 : E2 03 1E.45.BE FF 1F 03 0FE0 : A2 01 27.B4.FC 03 1F 01 0FD8 : E2 01 27.B8.15 03 1F 01 0FD0 : A2 01 27.B8.15 03 1F 02 0FC8 : 00 00 00.00.00 00 00 00 Those shown in Red should not be there and likely came from pressing the Set button on another motion sensor or another device while the motion sensor was still in linking mode. If 27.B4.FC and 27.B8.15 are the other motion sensors and they do not have anything in the Membership list then deleting the motion sensors, doing a factory reset and adding them back to the ISY being certain to take the motion sensor out of linking mode before moving to the next. If either 27.B4.FC or 27.B8.15 are not motion sensors then those devices will have to be cycled as well because they will also have links that should not exist.

A single press of the KeypadLinc button CANNOT be sending a Fast On/Fast Off. Each Controller has a unique set of Responder values. The Scene Responder values were set based on your earlier post. In addition click on the Red KeypadLinc button node name below the Scene name and set the Responder values for that KeypadLinc button. The values set for the Scene name where the PLM is the Controller are different from those associated with a KeypadLinc button press.

The KeypadLinc is now not working since its Responder values were not changed. In Insteon every Controller has a unique set of Responder characteristics. What is the HTML interface you are using and how do you invoke it? I don't normally use it but tried the Dashboard and it does not show Fast On/Fast Off.

The Controller in the HTML situation is the PLM. Click the Scene name itself and set the Responder values as desired.

That Icon should have been deleted when the Java Applications etc were selected for deletion. Note the reference to 4.0.5 in the URL. That is why things are deleted from Java. C:\Windows\SysWOW64\javaws.exe -localfile -J-Djnlp.application.href=http://isy.universal-devices.com/99i/4.0.5/admin.jnlp "C:\Users\JGD\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\39\448168a7-57d6f9c9" Make sure all browser sessions are shut down. Delete the Java cache including the applications and then use the URL of choice from the 4.1.2 announcement.

The link database is a few problems. The entries that start with A2 01 are responder entries that are not logical because the motion sensor is normally asleep. This motion sensor is also a Controller (the red entry that starts with E2 01) which is odd since the On/Off is being performed with a Program. Take a look at the Insteon addresses and see what other devices are involved. It may be that during the early stages of setup some of the motion sensors were cross-linked when they were not being taken out of link mode. M2-Sensor / 27 B5 10 1 0FF8 : E2 01 1E.45.BE FF 1F 01 0FF0 : E2 02 1E.45.BE FF 1F 02 0FE8 : E2 03 1E.45.BE FF 1F 03 0FE0 : A2 01 27.B4.FC 03 1F 01 0FD8 : E2 01 27.B8.15 03 1F 01 0FD0 : A2 01 27.B8.15 03 1F 02 0FC8 : 00 00 00.00.00 00 00 00 Device Record Count : 7

What URL is now being used that results in the 4.0.11 UI?

There are always new devices released after an ISY image has been released. Not sure if the 4.0.11 UI has support. For sure 4.1.2 does.

Put the motion sensor into linking mode with its Set button. Right click Sensor node, select Diagnostics | Show Device Links Table and post the results. How long of time elapses between the first and second trigger?