LeeG

To have confirmation requires a Direct command (not a Scene).

Good point. I use the Event Viewer at LEVEL 3 so a motion sensor set for On Only will still appear in the trace.

First, change the Scene name to something other than the Controller device (Scene Office Cans, anything that is not the same as the device name). The In Scene parameter can be the Controller device name or Scene name, setting different device configuration. No way to tell how the ISY treated that parameter when the Scene and device have same name. The Program will set the 50% value at 1:37 PM exactly. If the Program was coded after that or not Saved before 1:37 PM the Program has not run True. The posted image shows the Program has not run True. The value that affects paddle press is different from value that affects the Scene Responder On Level. In Scene 'controller device name' Set 'controller device name' 50% affects what happens when the On paddle is pressed. In Scene 'scene name' Set 'controller device name' 50% affects what happens when the Scene is turned On That is why the Scene name and device name cannot be the same Then In Scene 'controller device name' Set 'controller device name' 50% In Scene 'scene name' Set 'controller device name' 50% Set Scene 'scene name' On Else In Scene 'controller device name' Set 'controller device name' 100% In Scene 'scene name' Set 'controller device name' 100% Set Scene 'scene name' On

Let it run to completion. Every link record in every device that is a Controller or Responder of the PLM has to be changed to the new PLM address. All but the newest I2CS devices have the link records modified one byte at a time. Progress can be observed as the Green 1011 Icons disappear as the updates are completed.

Both Programs can Run and at the same time. Not a matter of one or the other. Once 'Margies Closet Light' is not Off the Status check in the first Program would stop it from being True.

Is it the paddle that does not work? That is all within the SwitchLinc unless it is not directly driving a load (Red wire capped).

No difference. Both have a True evaluation at Sunset and a False evaluation at Sunset+2 hours. EDIT: this assumes the To Sunset is coded From Sunset To Sunset +2 hours (same day)

Insteon allows a device to be a Controller of one Scene only. A device cannot be a Controller in multiple Scenes. Insteon requirement/limitation..

"Only downside is it says its operating temp starts at 3 degrees. Yesterdays temperature was -30 degrees Celsius which is roughly -22 degrees Fahrenheit." How is the 2441ZTH going to report a -20 degree value? The display does not have a negative indicator nor is there a negative indicator in the Insteon command. The 2441 series thermostats report in .5 degree increments. That would allow for a maximum of 128 degree spread between lowest and highest temperature that can be reported even if the thermostat supported that wide a range. If the high order bit indicated a minus temperature the spread would be down to 63 degrees rather than 128. One might expect to get something more than the 4 to 104 spec'ed values but the basic command layout cannot support a -20/-30 degree value. The -20 degree solution will not be found in the Insteon thermostats.

All the thermostats are internal home devices. The 2441ZTH is spec'ed for 39° to 104°F (4° to 40°C)

Tapping the Set button to go through unlinking and back to non linking mode avoids pulling the battery. It does NOT unlink the device.

"How does the ISY treat concurrent runs of the same program? Is the original killed and a new one started?" Yes. The Program is triggered when Motion Sensor Status changes. This terminates the current Program (which is why the lights do not turn off) and the If is evaluated again. It is likely False (need MS settings to confirm) so the Else is driven. EDIT: The termination of the current program execution occurs when the Program is in a Wait or Repeat. If there is no Wait or Repeat the running clause (Then or Else) runs to the end.

The battery devices will remain active for approx 4 minutes when manually put into linking mode. Once New INSTEON Device completes the device can be taken out of linking mode. Tap the Set button once to put it into unlinking mode, LED should move to blinking twice in a row. Tap the Set button again to come out of unlinking mode. This is all covered in the device Owners Manual. The device has to be put into linking mode again to add it to a Scene.

DO NOT DELETE the old PLM. The procedure for replacing a PLM is described in the Wiki. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Modem_.28PLM.29

There was a time when the Show PLM display did not have the link records numbered so Count was useful. The 2412 PLM has a slower processor which may account for the 800 number. Michel will have to explain. Hard to know if 760 means anything. Plugging the PLM into the 'filtered' side of a FilterLinc may reduce the Insteon traffic so an accurate count can be obtained. One user found it necessary to use two FilterLincs, plugging a FilterLinc into the 'filtered' side of the first FilterLinc to shutdown the Insteon messages to the PLM. Cannot change the number of links used by the basic device so Scene reduction/adjustment is the only area where link records can be reclaimed.

I agree with Brian, 17 is too low for 20+ devices. There is a 6 button KPL that is missing link records for all the buttons. Likely the PLM has failed if this Show was done after a PLM Restore. What ISY firmware is being used?

shannong The 2413 holds 992 link records. The Show PLM Links Table issues a series of Get Next commands to read the link database. If the PLM receives Insteon messages during this process it affects the "next" pointer such that link records can be read more than once or skipped. Necessary to run Show PLM Links Table/Count multiple times to insure a repeatable number and stop other Insteon activity if possible. With a count over 992 it sounds like other Insteon is affecting the Show PLM Links Table.

Exactly right. Because a KPL button functions as both a Controller and a Responder the Scene cross-linked the two Controller buttons as part of the Scene definition. Lights - Button B Front KPL - B - Controller Rear KPL - B - Controller The cross-link does not happen if the buttons were defined as Responders to the Scene

The buttons should be cross-linked (Controllers in same ISY Scene) so they would be On together or Off together. If the symptom is intermittent the timing of the Program with the Ored If statements has enough variation to allow both buttons to be On/Off some/most of the time.

I would locate a jumper. The v.43 firmware could have changed how the jumper works but the Quick Start and Owners Manual indicate the jumper should be there.

phlojo The jumper should have been there. Was it obtained from Smarthome as a new device?

I coded a two KPL button B Scene, a program that has an If with the Status checks Or'ed, and turned the Scene On. The Program triggered and ran the Then clause. ButtonBoff - [iD 007A][Parent 0001] If Status 'KPL 8 Dimmer v40 / KPL 8 Dimmer v40 - B' is Off Or Status 'KPL Relay DB v40 / KPL Relay DB v40 - B' is Off Then Send X10 'B10/On (3)' Else Send X10 'B10/Off (11)' Sun 01/11/2015 09:45:45 PM : [iNST-TX-I1 ] 02 62 00 00 8E CF 11 00 Sun 01/11/2015 09:45:45 PM : [iNST-ACK ] 02 62 00.00.8E CF 11 00 06 LTONRR (00) Sun 01/11/2015 09:45:45 PM : [D2D EVENT ] Event [1B 57 F8 2] [sT] [255] uom=0 prec=-1 Sun 01/11/2015 09:45:45 PM : [ 1B 57 F8 2] ST 255 Sun 01/11/2015 09:45:45 PM : [D2D-CMP 007A] STS [1B 57 F8 2] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Sun 01/11/2015 09:45:45 PM : [D2D EVENT ] Event [19 21 DA 4] [sT] [255] uom=0 prec=-1 Sun 01/11/2015 09:45:45 PM : [ 19 21 DA 4] ST 255 Sun 01/11/2015 09:45:45 PM : [D2D-CMP 007A] STS [19 21 DA 4] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false Sun 01/11/2015 09:45:45 PM : [ X10] B10 Sun 01/11/2015 09:45:45 PM : [ X10] B10/On (3) I would need to see the parts as they were 5 weeks ago to analyze how they work.

That will do it. When the button B Scene is turned On each B button is turned On. As soon as one B button changes Status the last Program is triggered. At that point one B button is On and the other B button is Off. The If says if either B button is Off (the checks are Ored) so Program Then clause runs turning its devices Off.

Something in Set Scene 'Lights - Button B' On affects the state of 'KPL Front Door - KPL - B' Or 'KPL Back Door - KPL - B' When one turns On the other is still Off so the last Program is triggered turning those devices Off If Status 'KPL Front Door - KPL - B' is Off Or Status 'KPL Back Door - KPL - B' is Off Then Set 'Family Room Pot Lights' Off Set 'Kitchen Sink Light' Off Set Scene 'Kitchen 3 Way' Off Set 'Living Room Lights' Off Set 'KPL Front Door - Ext Lights' Off Post Scene 'Lights - Button B' to confirm

Run Tools | Diagnostics | Show PLM Links Table. If the PLM is defective the link table will be empty, assuming the PLM was not Deleted by accident.