LeeG

An "If Control" statement DOES NOT have a False state. If Control 'Main Bath Contact.1' is switched Off is True (driving Then clause) when door is closed (sends an Off command). Again, that statement has no False state. It cannot drive the Else clause. If Control 'Main Bath Contact.1' is not switched On can only be True because it is If Control (no False state) but since the 'not' is included it drives the Else clause when True (when On command sent). This action of driving the Else when True is unique to If Control '....' is NOT switched xx. The net, when Off command is received the Then clause executes. When On command is received the Else clause is executed because of the 'not' in the statement. Note: If Control DOES NOT look at Status of device. If Control is looking at the command the device sends to the PLM/ISY. If Status looks at the Status of the device.

You are right on target. Three to cover the individual Controller devices for 31% and three to set back to 81%.

The Admin Console (UI) is current but the ISY Firmware level is back level. 4.2.30 ISY firmware should be installed. I've been running 4.3.10 (RC5) since it was released. Expecting the next 4.3.xx image which will likely be the next Official release and last 4.x.x. I would be concerned that 4.2.30 Admin Console running against 4.2.18 ISY could be causing issues.

I do not have any new ideas at present. The Program is pretty simple. Once triggered with "If Control" it should Wait 15 minutes and then run the next statements. It should show "Running 'Then' " for those 15 minutes. What ISY firmware is being used? Does Help | About show same level for Firmware and UI?

Check the Folder Program HallLightsTimer is in. Suspect the Folder has turned False which stops Program execution.

If you have a 2413S PLM that is in the area of two years old or so it has likely failed. They have an issue with failing capacitors that fail around the 2 year mark. If electronically inclined there are forum topics that identify the capacitors that fail. SmartLabs has corrected the issue with the PLM hardware v1.C and later. This topic has details for repairing PLM http://forum.universal-devices.com/topic/13866-repair-of-2413s-plm-when-the-power-supply-fails/

Why is changing Darkness Sensitivity and/or Night Only Mode important for Program interface. If there is a broad user need to set either Option under a Program perhaps it can be considered as a future capability.

There is no API to adjust that value.

None that I know of. The Motion Sensor is normally asleep so it would not accept a command even if there was a command available.

Sorry, no. The MS Scene cannot be made inactive. Insteon does not have that function. Set Scene '.....' Off turns the Scene Responder(s) Off See the other post for changing the MS Scene On Level

The Motion Sensor cannot be stopped from using the Scene. Something like this changes the On Level the Motion Sensor uses. The lower Garage Lite On Level in the IF and Then clauses likely needs to change to match your situation. GarageSceneAdjust - [iD 0097][Parent 0001] If Status 'Garage Lite' is 30% Then In Scene 'MotionSensor2-Sensor' Set 'Garage Lite' 30% (On Level) Else In Scene 'MotionSensor2-Sensor' Set 'Garage Lite' 100% (On Level)

The Set Scene ...... On or Off works in Then and Else clause. TestSceneBeep - [iD 003C][Parent 0001][Not Enabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'ScenePrimaryBeep' Off Else - No Actions - (To add one, press 'Action')

Smoke and CO alarms sound at all devices and therefore trip the respective Smoke Bridge node. Things like Low Bat that are apparently not sounded at any device beyond the one having the issue would be limited.

Using a good well filtered 12v DC supply, connect Gnd (-) to I1- and +12v to I1+. Input I1 turns On when DC supply is On.

Check the size of the opening between door and door frame. For two devices to switch to Open, Closed, Open suggests the possibility the Hidden Door Sensor is too close to its Open/Close state. The Hidden Door Sensor comes with a spacer/filler that moves the Sensor closer to the door frame so the switch is less likely to change state as the door moves past the door frame. Would also like to see a Tools | Diagnostics | Event Viewer at LEVEL 3 trace of the Open/Close/Open sequence. If multiple Dual Band devices pick up the Hidden Door Sensor, one on 120v leg1 and one on 120v leg 2, the PLM may be seeing a delayed message sequence.

Great points. My examples were in the context of using a simple "If Control" or "If Status".as they have the most basic rules for the individual statement and are the easiest to understand. A complex If with multiple conditions, whether True or False depends on an evaluation of all Conditions in the If clause. An iF clause can have a dozen statements, some Anded together, some Ored together, with parens to combine conditions. I thought it best to present how the individual statement behaves before opening Pandora's box with a complex If. DoorSensor - [iD 005E][Parent 0001] If Control '2B.09.AE.1 - Door Open' is switched On Then do something when door opened Else the Else is never executed with this 'If Control' DoorSensor - [iD 005E][Parent 0001] If Status '2B.09.AE.1 - Door Open' is On Then do something when door opened Else do something when door closed Sorry, the Status example got lost in the first post.

rlanza1054 Some noted points need correction. Using a SwitchLinc as an example ...... "If Control 'switchlinc' is switched On' triggers Program with True Condition each time the On paddle is physically pressed. If the SwitchLinc is already On and the On paddle is pressed the Program is triggered with True evaluation. Tapping the On paddle three times (not fast enough to generate a Fast On) would trigger a Program three times each with a True Condition. Sending an On command to the SwitchLinc DOES NOT trigger a Program with the above statement, must be a press of the On paddle. The above statement NEVER triggers a Program with a False Condition. "If Control 'switchlinc' is not switched Off" triggers a Program when the Off paddle is pressed and the Condition is False because of the 'not'. Same process applies if the Off paddle is tapped multiple times (not fast enough to generate Fast Off). Each Off paddle tap triggers the Program with a False Condition. Sending an Off command to the SwitchLinc DOES NOT trigger Program. "If Status 'switchlinc' is On" triggers a Program with a True Condition when the SwitchLinc turns On. This happens when the ON paddle is tapped that turns the SwitchLinc On; this trigger also happens when an On command (Scene or Direct command) is sent to the SwitchLinc that turns the SwitchLinc On. The Program is NOT triggered when additional On paddle presses occur nor is a Program triggered when additional On commands are sent to SwitchLinc. Unlike "If Control", "If Status" also triggers a Program when Status changes. If the checked Status (On in this example) does not match, the Condition will be False. It may seem complex but it really is not. "If Control" requires a physical change initiated to the device itself. "If Status" requires the "state" of the Switchlinc to change either physically by switch action or by command sent to device. So, which do you code in a Program, which situation is the Program designed to handle. Any change in 'state', paddle or command, use If Status. Any change that must occur because device is physically operated, use If Control.

An appliance of concern that runs 24 hours a day is unusual. Looking at what is running or not running is done when it is not failing. Or just leave it alone and debug it the symptom when it comes back. The beauty of all this is the choices are all yours.

As was noted, nothing in the attached document covers the internal workings. The float looks like mine and is likely 120v as the type of switch that covers 120v AC as well as low voltage DC (needed for I/O Linc) would be unusual. Those floats can control 120v pumps directly. No reason for the manufacturer to make that investment in the float switch. The light and buzzer power is not known based on the document.

My pump up septic system high level float uses 120v so be sure what your system uses before connecting to an I/O Linc.

I suggest looking at what appliance(s) are not active now. Those symptoms between two PLMs that just stop indicates an outside source of interference. Something that is injecting noise or absorbing Insteon signal.

Around page 9 of KPL User Guide under Local On Level Local On-Level The Local On-Level is the brightness that the light(s) physically wired to KeypadLinc will come on at when turned on locally. The default is 100%. Local On-Level can be set to any one of 33 settings 32 fixed brightness levels (3% to 100%) Or “Resume Bright” • Previous brightness level is stored when turned off and recalled to that level brightness when turned back on To set KeypadLinc’s Local-On-Level: 1. Press & hold On and/or Off (or Main in 8-button configuration) until the connected light is at the brightness desired when turned on locally (turn the light off if you wish to use the “Resume Bright” feature) 2. Tap KeypadLinc’s Set button KeypadLinc will (Beep) 3. Test the Local On-Level settings by tapping

Thank you. I suspect this is more related to the MorningLinc firmware level rather than the hardware level which is on the paper sticker. The MorningLinc firmware level can be found on line 2, right side of Admin Console display of MorningLinc (either node). This MorningLinc has v.3A firmware where Factory Reset works as described in User Guide.

I have v.3A MorningLincs. Just Factory Reset one and no longer have lockset control so Factory Reset works on v.3A units. clarkes71 What firmware is on your MorningLinc?

it very unreliable using set button (it was working fine before isy). The ISY is not involved with the comm between MorningLinc Set button and lockset. Look for some change in position of MorningLinc to lockset. Also batteries in lockset could be low reducing reliability. Is this v.42 MorningLinc the old style with LED on side next to Set button or newer style with LED on top edge of unit?