LeeG

If you have not found the problem before 10 PM, run Tools | Diagnostics | Event Viewer with Level 3-Sevice communications events selected before 10 PM.. The Program statements will be traced at 10 PM. Post the event viewer file.

Do not create set button links when using the ISY. There are a few exceptions for special devices which include instructions on how to do set button links with those devices. The ISY will not be aware of the link created and will overlay and/erase the set button links. Define an ISY Scene, add the RL2 button as a Controller and the SwitchLinc either as a responder or controller depending on how the SwitchLinc will be used. Remember to put the RL2 into linking mode before adding the RL2 button to the ISY Scene.

That is the problem with not issuing the Fade Stop. That is not the normal sequence so hard to tell. Does either Staircase or Staircase Slave button press turn it to 30% after 10PM. You did add the additional 4 Adjust Scene statements to both the Then and Else clauses in the Program. Does the Programs | Summary tab show the Program ran at 10PM and the Status is False indicating the Else clause ran. For now you can change the Set Scene xxx Fade Down to Set Scene xxx Off. That will eliminate the question about Fade Down until the 10PM On Level is resolved.

The backlight is always 100% or the load is coming on at 100%

What is the brightness issue? I thought that was the Fade Up not working.

Putting the Fade Stop first is an odd fix as the Fade Stop normally occurs after the Fade Down. I suspect the Fade Stop is actually clearing the previous Fade Down. Something like this would be better ... Then Wait 10 seconds Set Scene 'Staircase Pair' Fade Down Wait ?? seconds Set Scene 'Staircase Pair' Fade Stop where the ?? value is what is need to bring the level to Off. This will take a few tests to determine a good value. If my suspicion is correct about the Fade Stop actually clearing the previous Fade Down, a Fade UP may have a problem because the previous Fade Down had no ending Fade Stop. I suggest moving the Fade Stop after the Fade Down before spending time on the Fade Up issue.

"Trying to reset the state right after the fade down would affect the fade down itself " It could. Would depend on the On Level when the Fade Down was issued. "Setting the starting state is a much more elegant solution. Is this correct?" It has not been clear to me where the Fade Down is issued relative to the overall logic. Perhaps seeing the Program would help. "thing I need to do with timers now is detect a double 'on tap' " The Insteon hardware issues a Fast On command when a double tap of the On paddle occurs. This overrides the On Level and Ramp Rate settings, turning the device 100% On with a relatively fast ramp rate. The Fast On can be checked in a Program If statement.

The two Adjust Scene statements alone affect what happens when the ISY Scene name is used in a Program. They do not affect what happens when the paddle of either switch is operated. The additional 4 lines in my post change the values for when each switch paddle is used. The On Level and Ramp Rate information is stored in each responder under the address of the controller device. There are three controller devices involved, ISY PLM, Staircase, Staircase Slave. It is necessary to change the responder values for all three controllers, thus the need for six Adjust Scene statements. Actually when specifying one of the devices in both name fields the Local On Level is being set rather than the responder information in a link record. Fade Up/Down Fade Stop are issued in pairs. When you press a paddle and hold it the equivalent of a Fade Up/Down is issued. When the paddle is released the equivalent of a Fade Stop is issued. Don't know what the device firmware will do if the Fade Stop is not issued. Suggest posting the actual Program along with an Event Viewer trace with the Level 3-Device communication events selected. The difference could be that the device reaches the end of the ramp and posts a state change within the 30 seconds that does not happen in 5 seconds.

"Did I mess up how ISY's management/control by installing HL?" I do not have a list of symptoms you will see from using both ISY and HL. As symptoms surface and root cause is determined you can publish that list yourself. Keep in mind as you evaluate each new symptom, there are two independent applications trying to accomplish the same things with the same set of devices. As HL finds changes to device link databases initiated by the ISY it will re-sync its own database. If it becomes necessary to restore device under ISY the process will wipe out all the link information that HL established. I have used both products but never let them overlap devices. It would be interesting if HL had a mode where it did no device management at all. No event processing. Simply a way to use its tools without using it major function. Not likely to every have that option. "Is there a comparable ISY tool I don't know about that can do the same diagnostics" No. The ISY Scene test does show results by device. There is no control over hops nor means of charting results, albeit primitive. Smarthome is trying to manage its product line. Not sure the ISY and HL have the same requirements or objectives.

For two devices to control the same load and the status LEDs to stay in sync, yes they both need to be added to the ISY Scene as Controllers. The ISY will cross link the devices such that either controls the load and the LEDs will be in sync. Regarding the Fade Up, are you using the Fade Stop to stop the Fade Down before issuing the Fade Up?

The RL2 should have no problem controlling the SwitchLinc Relay. What is actually happening? Error when creating the ISY Scene, Scene created but RL2 does not control the SwitchLinc Relay? Can you provide more details and perhaps an Event Viewer trace with Level 3-Device communication events selected when the problem occurs.

Last time I used HL the devices had to be added to HL for it work with them, including running the comm diagnostics. If the devices have been added to the ISY, then added to HL there are link record conflicts just waiting to surface. When a device is added to the ISY it establishes links between the device and the ISY PLM such that state changes are signaled to the ISY PLM. HL does the same thing. HL established links with its PLM such that state changes are known to HL. The problem is the link records HL wrote are not known by the ISY. Any update/change to devices by the ISY that affect link records can overlay and/or erase the link records HL created. So long as no changes to link records are made after adding devices to both products things should be okay. That is a difficult requirement to maintain.

Take a look at this topic. It should cover much of what you are looking for, viewtopic.php?f=25&t=5184

Jumper 2 has no affect when Jumper 5 is in place. Jumper 5 must be in place to support the ISY setting the LED configuration. Does the Motion Sensor LED flash once when motion is detected or multiple times? If multiple times the motion sensor is having communications problems with one or more of the responders linked to the motion sensor. Blinking multiple times indicating a communications problem happens even if the LED has been turned Off.

Setting the two responders for the ISY Scene name works for when the Scene name is used in a Program or manipulated with the Admin Console. It would not affect what happens when either paddle is pressed.

The Insteon Action statement can adjust the LED backlight level. The pulldown that contains On, Off etc contains backlight levels toward the bottom of the pulldown list. All buttons are affected. Individual buttons cannot be set to a unique value. Set 'KPL Floor Dimmer 6 button' On 15 / Off 7 (Backlight Level)

Insteon hardware/firmware does not support a different Ramp Rate for On versus Off. A Fast On/Fast Off will override a slow ramp rate but it is fixed at 0.2 seconds (it is fixed for sure).

Some devices have an option to flash the LED when powerline traffic is detected, like the PLM does. Check the Properties (I think that is what HL calls them) for the SwitchLinc and see if HL shows an option for the LED to follow traffic. Did you register the Insteon devices with HL? If so there is an issue you should be aware of. HL establishes all the link records necessary for HL to detect device state changes, just like the ISY does. The ISY is not aware of these new link records and will eventually overlay and/or delete the link records HL established.

No wire connected to a standard 3-way switch, regardless of color, is Neutral. A Neutral is never switched.

The 2412S PLM is no longer being sold by Smarthome. The 2413S PLM does not provide 12V DC as the 2412S did. Therefore you will need an external power supply for the ISY in addition to the 2413S PLM..

bmarsh DO NOT run the 2.8.15 Admin Console with the 3.1.17 ISY firmware. Go to Help | About. There should be two lines, Firmware and UI just below it both of which should indicate 3.1.17. Clear the Java cache and pull the latest Admin Console for 3.1.17 (Brian indicated how). Once it is cached you should then see Help | About show the two lines described above. Lee

The White wire with the black stripe is not Neutral. The Line/Neutral feed for the outside light goes to the light fixture. The pair of wires on the switch being replaced are connected between the Line at the light fixture and light fixture itself. The advertised Smarthome solution is to install an InLineLInc at the light fixture. Rewire the two wires going to the old switch such that they carry unswitched Line and Neutral which powers an Insteon switch that does not have anything connected to the red load wire. The new Insteon switch is linked to InLineLinc for light fixture control. If an additional wire can be pulled an alternate solution is to run another wire between the new Insteon switch and the fixture that would connect to the Red load wire on the new Insteon switch.

This is an example of what you may be looking for. Assumptions can really be way off base. ISY Scene – Staircase Pair SwitchLinc – Staircase SwitchLinc – Unknown This first Program establishes the link record Responder On Level and Local On Level values based on the time of day. Note that the Ramp Rate statements have been removed completely. They were not setting any new values and can be eliminated. Set the 2 second Ramp Rate value through the Admin Console. No need for Program statements. If From Sunrise To 10:00:00PM (same day) Then In Scene 'Staircase Pair' Set 'Staircase' 100% (On Level) In Scene 'Staircase Pair' Set 'Unknown' 100% (On Level) In Scene 'Staircase' Set 'Staircase' 100% (On Level) In Scene 'Staircase' Set 'Unknown' 100% (On Level) In Scene 'Unknown' Set 'Unknown' 100% (On Level) In Scene 'Unknown' Set 'Staircase' 100% (On Level) Else In Scene 'Staircase Pair' Set 'Staircase' 30% (On Level) In Scene 'Staircase Pair' Set 'Unknown' 30% (On Level) In Scene 'Staircase' Set 'Staircase' 30% (On Level) In Scene 'Staircase' Set 'Unknown' 30% (On Level) In Scene 'Unknown' Set 'Unknown' 30% (On Level) In Scene 'Unknown' Set 'Staircase' 30% (On Level) The second Program recognizes switch activation, Waits and turns the Scene Off. If Status 'Staircase' is On Or Status 'Unkinown' is On Then Wait 30 seconds Set Scene 'Staircase Pair' Off Else - No Actions - (To add one, press 'Action')

Addressing only the KeypadLinc Secondary button H question, button H must be a Responder in a Scene and the Scene turned On or Off to turn the Secondary button LED On or Off. KeypadLinc Secondary buttons cannot be controlled directly.

First, without valid coupling, trying to make the changes in a device link record is problematic. Okay to play around with turning devices On and Off. The only failure there is the device may not respond. Here the device link records are being altered which I would not try until the system is reliable. From the wording "Staircase Pair" it suggests there are two devices in the Scene yet only one is being changed. Both switches should be changed if the Scene name is being used in another Program. Plus what is being changed is the value in one device when the Scene name is being used in a Program or manipulated through the Admin Console. Yet there is nothing in the posted Program that is using the Scene except the Adjust Scene. Also the On/Off status on one switch is being used to change link records which is not logical to begin with. Describe what the objective is. Cover the switch configuration and exactly what the results should be. Is the result of pressing the paddle on one switch or the other what is being adjusted. I do not think what is coded is addressing what the Program may be trying to accomplish.