stusviews

A program is true if any one of its OR conditions are true (or all of its AND conditions are true). A program runs only if its triggered. Your program has several OR conditions. Each Control is a trigger. Are the variables integer or state variables?

That's unusual. OTOH, most Insteon devices have a 2 year warranty, so if they die quickly, then there's a no-cost replacement available. But, if that's what you're experiencing, then I agree with Techman, a whole house surge suppressor is needed.

Do you mean the variety of devices (Insteon beats them all) or the variety of manufacturers (Insteon has only one)?

According to this post v92 dates back to 2010.

Tools, Diagnostics, PLM Info/Status You can restore remotely, but if the PLM is failing, you may not be successful.

Hi Todd, Just to be sure, specify the revision. What is the result if you open the HTML interface only (i.e., using the IP address)?

The tamper-resistant duplex receptacles have a firm grip. Along with cable ties you'll have a dual-band device

Bottom Left, below the message pane.

Select More Reply Options, Attach File

The program is disabled as soon as the disabling statement is executed.

If a program is disabled, then it ceases to run until such time as another program enables if or if it's manually enabled.

Program 1 If Control 'Motion Sensor' is switched On Then Send Notification to 'me' Run Program 'Program 2' (Then Path) Else - No Actions - (To add one, press 'Action') Program 2 If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Disable Program 'Program 1' Wait 1 minute Enable Program 'Program 1' Else - No Actions - (To add one, press 'Action')

Here's a list of IRIS supported devices and the protocol used.

IRIS is compatible with ZigBee, Z-Wave and WiFi. AFAIK, Sylvania Ultra IQ bulbs are ZigBee compatible.

You can copy the programs you think you'll need one-at-a-time (i.e., Copy to Clipboard).

Holdoff is the duration that must occur before a change is responded to. The recommended minimum value is 1.5 sec, but it can be adjusted from 0.5 to 38.25 sec. I use 1.5 seconds for our subwoofers. Hysteresis is the minimum change that must occur before the SynchroLinc changes state. The range 0.5 to 127.5 watts. The recommended minimum value is 1.5 watts. I chose 10% of the trigger threshold.

Which X10 module? How are you trying to control it? Do you have any other X10 modules? If so, can you control them?

There are at least four different ways to cable two 3-way switches and one 4-way switch. Each has a different Insteon solution. For example, in Diagram 1 (above), neither the middle nor the last switch nor the fixture has a line wire. In Diagram 2, none of the switch boxes have a neutral. In both diagrams, the last box has one 2-wire cable and one 3-wire cable, so viewing only that box is insufficient. If everything works as expected, there's no need to go any further. But, the OP indicated that everything is not working as expected. BTW, the schematic is constant, only the cabling varies (i.e., which of the four boxes has the source-both line and neutral).

Did you delete any older versions. Java has a tool that will do that.

Yes, describing the how many of each color is often all I need. I have nearly two decades of hands on wiring experience. There's a few ways 4-way switches can be properly wired. When something doesn't work as expected, I won't guess. Here's just two ways:

Brian, Is that with or without the X10 module?

Not so. The ISY does keep track of a device's status, unless you have a communication problem. However, the ISY does not and cannot determine that state of a scene. That's because a scene can turn some devices on, some to a specific On-level and other device off.

I agree, the schematic is correct. But how everything is cabled varies. The OP indicated an exact match without opening any other switch box, yet it's not functioning correctly. Where's the source, at the first switch, then last, the fixture? It seems that we put in more effort at a solution than has the OP.

The ISY doesn't "know" how a device was turned on (or off), but the ISY does keep track of the state of the device including the On-level if the device is a dimmer. Using Control as a condition will trigger the program only if the device was manually operated or if a direct command was sent. But, using Status will trigger the program no matter how the state of the device was changed even if the change in state was initiated via a scene. If a scene does not update the devices status, then you may have a communication difficulty.

I do just that. If any one of the three lights I'm concerned about are on, then button G is lit. One push on button G turns those lights off. Two programs and two scenes are used as follows: DR Front Off Button scene has only the button as a responder and is controlled by the programs. DR Front Off scene has the button as a controller and the lights as responders. The button is set to Non-Toggle Off and is operated manually DR Front On Program If Status 'CR / Devices / CR FanLinc-Light 80' is not Off { Or Status 'KT / Devices / KT Ceiling 50' is not Off { Status is used instead of Control, so it doesn't matter how the light was turned on Or Status 'LR / Devices / LR Ceiling Light KPL 20' is not Off { Then Set Scene 'DR / Scenes / DR Front Off Button' On <--this statement turns on the button LED if any one light is turned on Else Set Scene 'DR / Scenes / DR Front Off Button' Off DR Front Off Program If Status 'CR / Devices / CR FanLinc-Light 80' is Off And Status 'KT / Devices / KT Ceiling 50' is Off And Status 'LR / Devices / LR Ceiling Light KPL 20' is Off Then Set Scene 'DR / Scenes / DR Front Off Button' Off <--This statement turns the button LED of is all lights are turned off. Else Set Scene 'DR / Scenes / DR Front Off Button' On