LeeG

The local control devices can be set to come on at the defined Local On Level OR come on at the last On Level (Resume Bright). Check the User Guide for each device to see how to set each device to come on to the defined Local On Level. Once set to come on at the defined Local On Level the values set by the ISY for On Level (applied locally) should be used.

Java has been updated to 51. Add the ISY IP address to the Java Exception Site List, under the Java Security tab. Another reason to update to a 994i. 4.1.2 contains the update Java 51 requires.

If you are going to mimic all the button actions in a Program there needs to be multiple Programs. One to handle On one to handle Fast On although this might be rolled into the On Program one to handle Dim one to handle Bright one to handle Off one to handle Fast Off although this might be rolled into the Off Program Each requires different commands sent to the Responder

Thanks for posting back. It did not seem reaonable that any level of KPL firmware would drop the ability of a button to react as a Scene Responder.

The Motion Sensor has to change states to appear in the Log. It could be in On Only mode for example or not sending Off commands, perhaps because the battery is low. A low battery can produce false motion messages. When the potential Program is identified it can be Disabled to verify it is the source of the Set Scene ..... On. Can also run Tools | Diagnostics | Event Viewer at LEVEL 3 and watch the messages being sent, assuming it is a Motion Sensor triggering the Program.

If you still have the Scene with what is probably a v.43 KPL, run a Scene Test against that Scene. The fact that the KPL button did not respond does not mean it should not respond. The Scene Test will show if the KPL is receiving the Scene command.

The Log indicates a Program is issuing the Set Scene. Right click My Programs, select Find/Replace. Search for Scene Outside Lights Full On name. From the time spacing it looks like it might be a Motion Sensor driving the Program.

Correct, a Scene cannot be added to another Scene. If adding anther Controller simply add the new Controller to the existing Scene KPL button - Controller SwitchLinc - Controller new device - Controller If the KPL should turn On/Off from the new Controller but the KPL should not control the new Controller new device - Controller KPL button - Responder SwitchLinc - Responder The KPL button and SwitchLinc are Responders so these two devices stay in sync. If neither matches the desired results please expand on what is required.

For the Scene question a Wait may help. I would put the UPS, battery backup and other devices on a FilerLinc. They often have such good noise reduction capability the Insteon signal is reduced to the point where it may not be reliable. I don't know have a v.43 KeypadLinc so have no direct experience to comment on. I would expect the KeypadLinc to be sending the missing message and it is not received at the PLM. That message is not ACKed because all Responders should see that message making a ACK impossible. As far as wired Dual Band devices providing coupling, the 4 tap set button test will verify coupling.

The installed devices should have no links to device that has not been added to the ISY.

If Java was updated to _51 then that is the cause. Either move to 4.1.2 or add the ISY IP address to the Java Exception Site List.

This is the message the ISY is looking for to recognize a button press. It happened only once even though there are other I2CS messages coming from the Keypadlinc from the other presses. Sat 02/15/2014 12:13:51 PM : [iNST-SRX ] 02 50 2A.15.B9 00.00.01 C7 11 00 LTONRR (00) Note the information message that the other messages are ignored because they are not what is expected. Sat 02/15/2014 12:13:30 PM : [iNST-SRX ] 02 50 2A.15.B9 11.00.01 C7 06 00 (00) Sat 02/15/2014 12:13:30 PM : [std-Group ] 2A.15.B9-->11.00.01, Max Hops=3, Hops Left=1 Sat 02/15/2014 12:13:30 PM : [iNST-INFO ] Previous message ignored. Four Scenes were invoked which may indicate an Insteon network issue when combined with the above. Sat 02/15/2014 12:13:51 PM : [iNST-TX-I1 ] 02 62 00 00 47 CF 11 00 Sat 02/15/2014 12:13:51 PM : [iNST-TX-I1 ] 02 62 00 00 48 CF 11 00 Sat 02/15/2014 12:13:51 PM : [iNST-TX-I1 ] 02 62 00 00 45 CF 11 00 Sat 02/15/2014 12:13:51 PM : [iNST-TX-I1 ] 02 62 00 00 41 CF 11 00 Are there other symptoms that indicate an Insteon network issue? Are Access Points used to couple the 2 120v legs? Are there Surge/Noise suppression power strips in use around the PLM, are there unfiltered electronic devices near the PLM?

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Press either the ON or OFF button once and post the trace. The green LED indicates the responder ACKed the button press message which would indicate the ON message was ACKed by the PLM. It would flash Red if the Responder did not ACK. Older KeypadLincs would flash the button LED several times (more than 2) if a Responder did not ACK.

Device links are deleted when using the first option. If you think that is not working run Tools | Diagnostics | Event Viewer at LEVEL 3 when adding a device and see if the links are deleted. The first option is used so that links that come from Smarthome or other environments do not adversely affect the ISY environment.

I see no reason why it would take 2 ON button or OFF button actions to trigger the respective Programs. Watch the Programs | Summary display (Last Run Time and Status) to see if the Program is triggered on the first press. Are these Programs in a Folder that may have to change to True before allowing the Program to run?

This link to the first post in the Variables forum category may be helpful viewtopic.php?f=68&t=6063

"The way I heard it the first choice should be only used for the first install of a unit. And use the 2nd when installing another unit." Not sure what the second part is asking. Use the first option to delete links. The second option adds devices found in the links and deletes links. This could be used to add a series of devices found in the links table but it can find devices not supported by the ISY if coming from another HA application. I recommend using the first option all the time. The only exception would be the MorningLinc which has a unique sequence to support the additional security in the MorningLinc.

1) Is my understanding correct that this will fix the problem and I shouldn't have it again as the 994 will be updated to reflect future changes in insteon devices? Yes. The newest KeypadLincs are Dual Band not supported on the 99i. 3) How do I transfer my modules? I have both the ELK and Portal (for Mobilinc) modules. Contact UDI with the UUID of the 99i and 994i. They will activate the modules on the 994i. 4) I just ordered the upgrade for the 99i as that was what I had, can I add the IR option at a later date? It looked like that wouldn't be a problem but I would like to be sure. Yes. The PRO and IR options can be added later. The IR option requires installing the IR board which is easy to do.

Right click the Program name and select Copy to Clipboard. Paste the Program to the forum post.

That is certainly not the expected behavior.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Change the Set Point values in the Program to something other than 60 as the ISY will not send 60 if it thinks that is the value in the thermostat. Be sure to Save the Program change. Fast Off the the switch and post the event trace. To the question of Init versus current value, the Init value is what the ISY will set the Variable to when the ISY is rebooted. If you want the Variable to be set to the current value when the ISY is rebooted set the Init value whenever the Variable value is changed.

It is likely in a Folder that is False. Yes, it was not triggered. Or if the Last Run Time is when the Variable was changed to 1 there is something perhaps not Saved as the Program should have triggered True if the Folders above it are True.

No time lag. What thermostats are being used? Does the Programs | Summary page show the Program was triggered? If the Variable was set to 1 before the Program was created the Variable has not changed value which is required for the Program to trigger. Change the Variable to 0, then back to 1.

Secondary KeypadLinc button LEDs must be controlled with a Scene. When the Program is triggered to Open or Close the curtains the Program turns a Scene On or Off that has buttons A-D as Responders. The OFF button cannot be independently turned On or Off. The ON/OFF button can be set to non-toggle Off mode which will have the OFF button dark all the time but it cannot be independently controlled from a Program or Scene. The Programs that react to buttons A-D can turn KeypadLinc Off which will turn the ON button Off but this will turn On the OFF button (unless ON/OFF is non-toggle Off mode).

"Only issue so far is that I get a $ sign which you do not have? What did I do wrong?" The ISY puts a $ in front of variable names to indicate a variable is being used. It is not uncommon for posted examples to be manually typed rather than entered as actual Programs and copied. Expect to see some variation in what ISY produces versus posted examples. Many posted examples are not absolutely correct syntax.