LeeG

The 994i PRO replaces the 99i PRO. When you have the 994i installed contact UDI sales with the UUID of the 99i and 994i so the modules can be activated on the 994i.

There is an update option on the UDI Web site. Look toward the bottom of the page that lists the various 994i options.

The lower the sensitivity the darker to trigger Dusk/Dawn. The motion sensor will trigger in both modes. For a test I set sensitivity to 120, Night Mode: Always checked. It took 4 minutes under bright light before motion sensor turned Dusk/Dawn Off

Those facts do not correlate. If Status triggers a Program only when Status changes and the Then clause would be executed only when the Status matched the If definition. If the motion sensor was sitting in On Status the Program would not be triggered.

Use If Status in this case. If Control will trigger the Program for every motion so you could see many emails within seconds. If Status triggers the Program when it turns On and will not trigger again until an Off to On occurs. There was no detail provided so if the motion sensor or triggerlinc is sending On commands only then If Status does not work.

Sorry, has to be done one device at a time. Going through the devices if the last link record is the one that is flagged it is not necessary to take any action. The first byte being 00 indicates End of List. The other 7 bytes have no meaning. The ISY sets only the first byte to 00 to mark the End of List. The device ignores the remaining 7 bytes when the first byte is 00.

Best to post the Show Device Links Table results. The End of List record can be labeled as a mismatch even though the last 7 bytes of data have no functional meaning. The other approach is to factory reset the ToggleLincs before doing a Restore Device. This will clear the link database to zeros so the End of List record will contain zeros.

Xathros Thanks for that information. I do not have the latest KPL firmware. I'm wondering if the OP does. Would seem obvious if the Set button was blinking.

The Insteon network has to be quiet when running Show PLM Links Table. Insteon traffic that reaches the PLM alters the "next" record pointer such that either link records are skipped or read multiple times during the Show command. This causes counts to be high or low. The Show PLM Links Table should be run 3-4 times with the same count to know the count is correct.

If the non-toggle Off mode button blinks more than 2 times a responder is not ACKing the request from the KeypadLinc. Off can be an issue because the loads are On which can present noise that would not be there going from Off to On.

There should be something on this forum about that. There was some activity a few weeks/months ago when a new Kaspersky update was released. I use another AV package so did not pay attention to what had to be done, only that there was something required.

A KeypadLinc button in non-toggle mold should blink twice when pressed. In non-toggle On mode the button LED stays on after the two blinks, in non-toggle Off mode the button LED should turn Off after the two blinks. Blinking more than 2 times in any mode indicates a responder did not ACK the command sent by the KeypadLinc.

Kaspersky is a common source of blockage. I think there is a mechanism to add the ISY IP address to allow Kaspersky to work but I don't what that is specifically.

The Discovering Nodes message usually means the Start Linking function was initiated and the Finish button on the popup that displays in response to clicking Start Linking was not clicked. If the popup did not display the first time Start Linking is clicked that usually means the AV/firewall is blocking the push of data from the ISY to the Admin Console. If the Start Linking popup did display what AV is being used? The ISY must be rebooted to clear a Start Linking that did not result in a popup the first time Start Linking is clicked.

See if the Insteon address of the OutletLinc is already defined to the ISY. With no error messages it sounds like the Insteon address is already defined. Click on My Lighting/ISY to display list of all devices. Click the Address column heading to sort by Insteon address. If that is not helpful run Tools | Diagnostics | Event Viewer at LEVEL 3. Repeat the New INSTEON Device and post the event trace.

Here are the six adjust scene statements. It would be good to expand on the issue because the adjust scene statements may not be the issue If From 3:00:00PM To Sunrise - 1 hour (next day) Then In Scene 'Hardware / Family Room Light' Set 'Hardware / Family Room Light' 30% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light' 30% (On Level) In Scene 'Hardware / Family Room Light' Set 'Hardware / Family Room Light Slave' 30% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light Slave' 30% (On Level) In Scene 'Hardware / Family Room Light Slave' Set 'Hardware / Family Room Light Slave' 30% (On Level) In Scene 'Hardware / Family Room Light Slave' Set 'Hardware / Family Room Light' 30% (On Level) Else In Scene 'Hardware / Family Room Light' Set 'Hardware / Family Room Light' 100% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light Slave' 100% (On Level) In Scene 'Hardware / Family Room Light Slave' Set 'Hardware / Family Room Light Slave' 100% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light' 100% (On Level) In Scene 'Hardware / Family Room Light Slave' Set 'Hardware / Family Room Light Slave' 100% (On Level) In Scene 'Hardware / Family Room Light Slave' Set 'Hardware / Family Room Light' 100% (On Level)

Perhaps if you identify the issue you are having. There are two more Adjust Scene statements needed but I want to be sure we are working on the same problem.

My last post was wrong. The Local On Levels are being set. What is not being set is what the Responder switch does when the paddle is pressed in the other switch. Sorry for the confusion. The Folder names, which are actually very good, got me moving in the wrong direction.

I may not understand the problem. The Responder values for when the ISY is turning the Scene On/Off are being set. Those statements are in Red If From 3:00:00PM To Sunrise - 1 hour (next day) Then In Scene 'Hardware / Family Room Light' Set 'Hardware / Family Room Light' 30% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light' 30% (On Level) In Scene 'Hardware / Family Room Light' Set 'Hardware / Family Room Light Slave' 30% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light Slave' 30% (On Level) Else In Scene 'Hardware / Family Room Light' Set 'Hardware / Family Room Light' 100% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light Slave' 100% (On Level) In Scene 'Hardware / Family Room Light Slave' Set 'Hardware / Family Room Light Slave' 100% (On Level) In Scene 'Scenes / Family Room Lighting' Set 'Hardware / Family Room Light' 100% (On Level) What is not being set is the Local On Level values in both switches. These are the values that affect what the switch does where the paddle is being pressed.

Is the 2441ZTH linked to a 2441TH with the 2441ZTH set as the Master?

Post the current Program issuing the Adjust Scene statements. Need to know the ISY Scene name and the name of each Controller Confirm this is an ISY Scene with two additional Controllers

When something is not sent such as not sending a Set Point it may be the ISY thinks the thermostat is already set to that value. In general the ISY does not send a value it thinks is already in the device. Try sending a different value and then go back to the value that did not get sent.

No change in Direct versus Scene since Insteon was released in 2005. Why would one add a device to Scene xxxx if the Program and RemoteLinc2 were not to control the additional device?. Should the devices being controlled by the Program and RemoteLinc2 become different then two Scenes would be used. It is your choice. Where only two devices are concerned the delay in the Time Program turning on the first device versus the second device is small. A Scene has the two devices turn On or Off together. If you prefer Direct use it that way.

I prefer a Scene to direct device control, particularly in the RemoteLinc2 case. Same ISY Scene for both Program and RemoteLinc2. For the RemoteLinc2 case there is no delay in invoking a Program to then invoke the Scene. ISY Scene xxxx RemoteLinc2 button - Controller Hall Light - Responder Lamp - Responder The existing Time based Program does a Then Set Scene xxxx On Else Set Scene xxxx Off

The additional parens indicated larryllix will have the Program look like this If ( ( On Mon, Tue, Wed, Thu, Fri Time is 4:31:00AM Or On Sat, Sun Time is 8:01:00AM Or Time is 3:31:00PM Or Time is 7:01:00PM ) And Status 'WH On-Off Module' is not On ) Or ( ( On Mon, Tue, Wed, Thu, Fri Time is 6:01:00AM Or On Sat, Sun Time is 10:01:00AM Or Time is 5:31:00PM Or Time is 9:31:00PM ) And Status 'WH On-Off Module' is not Off ) Then Send Notification to 'Terry All' content 'WH Status' Else - No Actions - (To add one, press 'Action')