stusviews

That's a lot of Insteon traffic. Why not use red strobes?

Is the LED labelled to be dimmable? What's the result if you use an incandescent bulb?

The Fanlinc runs slow at less than 50%. medium above 50% and less than full on and at full speed at 100%.

I have several buttons in non-Toggle On mode because that's all I ever want the button to do. In particular, each entry/exit had a "Dine Out" button that turns most lights off and a few to a preset On-level. In addition the corresponding walk path lights (e.g., walkway to street, courtyard to garages). But I don't want the button always lit. So, a program turns off the scene that contains that button only. Here's why: First, if I turn off the Dine Out scene, then all the devices in that scene will turn off (including the button) which is virtually every light in the house. I certainly don't want that. Second, when a direct command is sent to a device it affects that device only, not any of the devices links. So sending a direct command to a primary button will turn on only the wired load. But sending a direct secondary button has no function, so there is no code for that in the Insteon protocol. Including any unneeded code leaves less room for a feature. OTOH, all devices respond to scenes. That's how cross-linking buttons to create a virtual 3-way configuration works. Creating a scene with only a secondary button as a member allows you to turn the button on and off.

There is no way to connect a wired sensor to the ISY. The only way to have the ISY aware of your sensor(s) is to connect the sensors to an ISY compatible device such as Insteon or X10 or to a Z-Wave or ZigBee device if you have either module. Or you could connect the sensors to an Elk security system which is ISY compatible. Then you'll need the Elk module.

simonsez, remove power from both the ISY and PLM. Power up the PLM first, wait a few seconds and then power up the ISY.

What is the specific device with the 1101? Do you get ! after writing changes?

That's a lot easier than having to do something

What specifically is not working? Also, you don't need two programs. Move the Then statements from program 2 to Else clause of program 1.

First ensure that you have the latest version of Java installed. Clear the cache. Try again. If that doesn't solve the problem, then open the Java Control panel and select the Security tab > Edit Site List and enter the IP address of you ISY including any port you may have assigned. Any success?

If the 2486D was originally a 6-button KPL, then a factory reset will return it to 6-button mode. It that's the case, then follow the instruction to change the mode. OTOH, if it was originally 8-button, then after a factory reset it should return to 8-button.

The Micro Module needs line and neutral. One side of the warning light should connect to neutral, does it (it's difficult to tell from the image as all wires are black)? If so, then connect the other side of the warning light to the yellow (#1) sense wire of the Micro Module. Cap (tape) the purple (#2) sense wire. Link the Micro Module as a scene controller of any Insteon responder. It doesn't matter if you use an On/Off or dimmer Micro Module as it won't be connected to a load. BTW, the TEST switch is a standard SPST panel slide switch, so it'll be easy to find. You'll have to drill out the rivets and secure the switch with screws and nuts.

Which specific X10 couplers. Active X10 couplers can interfere with Insteon signals, passive X10 couplers do not.

Having a Home button and a Night button is easily and correctly accomplished using two scenes. Having a single button that exercises that control based on time of day requires the use of a program in which each device is adjusted. But, you can't just use a program to change the level of each device at, say, Sunset + 30 min. If you did, then the first time the program ran, the devices would be set to the new level and remain at that level. So, you need to use the Else clause to return the devices to the previous level. You also need an If statement that triggers the Else. That can be accomplished by using From ..., To ... . The levels change at the From time and revert at the To time.

It's not unusual for each device in a scene to be set to set to different levels. So if you set the "scene" to 20%, for example, does that mean that each device is set to 20% or that each device is set to 20% of its current setting? To avoid that confusion, each device in the scene needs to be adjusted separately. Also, the Insteon protocol has no method for adjusting the brightness level of a scene, only devices.

Nope. It doesn't matter to the scene which leg powers the device. A goal is to make sure that you have at least one pair of dual-band devices communicating on opposite legs in order to bridge Insteon signals. All Insteon signals can cross that one bridge. Also, the opposite legs alternate between adjacent breakers vertically, not left-right. A A B B A A B B . . . . . .

Post the actual program (right click, copy to clipboard).

What is the specific problem? Also, the program won't respond to the switch being turned on manually.

Micro Module inside the case. Nothing is as dependable as wired.

The line is not needed because there is no Else clause.

Yes, that it. If the device is already on and a paddle/button is pressed to turn the device on, the state of the device does not change. Status will evaluate as false. But, you are correct. Something happened. If the device is already on and the condition is Control, then the paddle/button press would trigger the program. If the condition is Status, then the program would not run. If the state of the device is off and a paddle/button is used to turn the device on, then either Status or Control will evaluate as true. The state of the device changed and/or a direct command was sent If the state of the device is off and a linked controller is used to turn the device on, then Status would evaluate as true, but Control will evaluate as false. The state of the device changed, but a direct command was not sent.

Now that I have all my 2440's linked (no 1011), the remotes closest to the PLM have the slowest responses when a button is a program trigger. Conversely, RemoteLincs furthest from the PLM are fast, even when the button triggers a program. Linked devices (scenes) are unaffected. One RemoteLinc less that 5' from the PLM takes 4-5 seconds before a response is noted, but everything does work.

Could be the 9th week of 1931 or the 31st week of 2009. In any case, the PLM is elderly

No need for a program with the original two Motion Sensors, Bathroom and Hall, but only under the specific circumstances expressed by the OP, that is, living alone. In fact, the OP found the solution, Set the Bathroom MS to On-only, as suggested by Lee. Create a scene, not a program, where the Hall MS turns on the hall light and also turns off the Bathroom light. Don't walk through the hall if a guest is in the bathroom

You'll find response time much quicker, especially meaningful if you're walking into a very dark area. A limitation is not being able to bypass the MS, but that can be accomplished bu adding a second device. And don't forget Michel's advice. I actually induced an All On by having a program where the trigger button was manipulated by the program. It occurred when I tapped the button rapidly a couple of times. Solution: a 1 second delay between each statement.