fitzpatri8

You need to 'sync' MobiLinc to your ISY after adding any devices. BTW, a LampLinc is designed to control dimmable lights, not a motorized device. You risk overheating and damaging your pump by using it that way. The appropriate control for that application would be a non-dimming, relay device like an ApplianceLinc, or an InLineLinc Relay or SwitchLinc Relay mounted in a tabletop enclosure or project box and wired using approved cords & technique.

That's the correct behavior. Insteon devices use the same buttons to send on and bright messages and the same buttons to send off and dim messages. If you press and release a controller button you send the ON or OFF; if you hold a controller button, you send sequential BRIGHT or DIM messages. If you tap a button quickly twice, you send a FAST ON or FAST OFF message. If you hold it down for ten seconds, you enter Linking or Unlinking mode. These features are standard across the Insteon line, if you create scenes with an Insteon device linked as controller that's how it will behave. That said, you *could* remove the button as the scene controller and emulate the behavior you want using ISY programs. IF (keypadlinc button) control becomes BRIGHT or (keypadlinc button) control becomes ON then turn on scene x else no action; IF (keypadlinc button) control becomes DIM or (keypadlinc button) control becomes OFF then turn off scene x else no action.

That's not necessary--when you added all four to the scene as Controllers, the ISY took care of cross-linking the buttons for you.

How about using 2 programs. "MS Dark" If Motion-Sensor - Dusk/Dawn' is switched On And Motion-Sensor-Dusk/Dawn' is not switched Off Then Set 'Porch Light' 40% Else Wait 4 minutes Set 'Porch Light' Off and "Outside Motion After Dark" If Control 'Sensors / Bedroom Motion-Sensor' is switched On And Program 'MS Dark' is True Then Set 'Porch Light' On Wait 3 minutes Set 'Porch Light' 40% Else - No Actions - (To add one, press 'Action')

A single device can be part of hundreds of different scenes. Just create a new scene for the On using a faster ramp rate.

Neither the ISY nor the SmartLinc will mess with each others' links in normal operation, so you should be good. If you restore a device for some reason using the ISY, only the ISY's links will be restored so you'd need to manually re-link the SmartLinc scenes to that restored device.

You could turn on power to dedicated radios tuned to NWS forecasts or even strobe lights. Turning off all power could too easily be mistaken for a normal power outage, would cut off access to news sources, and would just delay your correct response to the threat.

Yes, you can simply cap off the red wire and just use the sense to detect when the motion turns on and off.

Hi Chris, welcome! Disable your programs attached to buttons G & H until you get your scenes set up. Create a button G Scene with button G as the only Controller. Add buttons A through F as Responders. Then add all the devices linked to buttons A-F as Responders as well. Create a button H Scene with button H as the only Controller. Add buttons A-F as Responders. Then add the devices linked to buttons A-F as Responders as well. Now click on the button H scene. In the lower right adjust the sliders for your sink dimmer to 0% and the other dimmers to 40%. The ISY will pause while it updates the device link databases. Now, on the left, click on the red button H Controller within the button H scene. Mid-screen, click the button that says "Copy scene attributes from button H scene" to copy those 0% and 40% settings over. The ISY will then update those links as well. Lastly, you'll need programs to send out your x10 commands. One program should run when either the Control button G or Control button H is turned ON but not off, waiting 2 seconds for the Insteon commands to finish then sending the x10 on commands, else waiting 2 seconds then sending the x10 off commands.

Yes, that's part of the Load Sensing circuitry built into the controlled outlet on the OutletLinc. It provides voltage but very restricted current, not enough to power the load but enough to detect when the load is switched off then on. From the product page: "Load Sensing allows you to manually turn on the lamp or appliance you plugged into OutletLinc by using the switch on the lamp or appliance itself, without sending a command from an INSTEON or X10 controller. When the controlled lamp or appliance is in the off state (with Load Sensing enabled), OutletLinc will "sense" that you are trying to turn on your lamp or appliance with its built-in switch. When OutletLinc "senses" this, it will turn on the controlled lamp or appliance automatically." This circuitry is built into LampLincs, ApplianceLincs and OutletLincs.

You can create a program that runs when the control-motion sensor turns on. Just leave the Then and Else sections blank. Once the program runs the first time, the ISY will provide a timestamp for when the program was last executed.

There's nothing wrong with what you posted, must be a problem with another part of the program. Can you post the program in its entirety?

You do that by clicking on the LampLinc in the device tree and changing the On Level (Applied Locally). Local=the settings used when the actual device button is pushed or, for plug-in modules, the controlled load is switched off then on.

All Insteon dimmers, no matter the version, have a 'local' setting. You could set the local setting to something low or with a long ramp rate (1%/8 minute ramp rate), then use ISY programs to detect the ON command and send an overriding command, but doing so would take the "instant" out of Insteon--you'd be in the dark while the switch signaled the ISY, the ISY detected the change, then the ISY sent the new command. Depending on how busy the ISY was with other tasks, I suspect it could potentially take 4-5 seconds.

I haven't had time to play with this myself. Does the IO Linc have to be programmed to momentary mode for it to respond with sensor device status instead of relay status, or does that not matter?

The issue is that you are manually running the Else path of the Flag Away program. If I understand the ISY logic correctly, folder conditions and "enabled" status only determine if the ISY is going to evaluate the 'If' part of the program as part of its routine chores. Directing it to go to the Else path of a program bypasses that restriction.

Whoops, neglected to mention that my second program has to be disabled to prevent the same problem from happening when the climate module says the light level is NOT 0! Thanks, Markens, for pointing that out.

I suspect you are either getting dark cloud cover or someone is setting something on or over the light sensor of the weather station you are using. That's causing the light level to reach 0, which triggers evaluation of your program. Since the result is False (because it isn't Sunset), it executes the Else statement. Easily solved by splitting this into multiple programs: Sunset timer If Time is Sunset Then Run Program 'Landscape Lights' (If) Else - No Actions - (To add one, press 'Action') Landscape Lights If Module 'Climate' Light is 0 Then Set Scene 'Landscape Lights' On Else Wait 10 minutes Set Scene 'Landscape Lights' On

Every change in trigger events causes a re-evaluation of the IF statement, so by turning the light off you are aborting the program. To accomplish that, you'd want to use another program: If Time is 11:00:00PM And Status 'Icon Switch' is On Then Run Program 'Blink' (Then Path) Else - No Actions - (To add one, press 'Action') and 'Blink' program: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Icon Switch' Off Wait 1 second Set 'Icon Switch' On Wait 1 minute Set 'Icon Switch' Off Else - No Actions - (To add one, press 'Action')

How about: If Control 'Icon Switch' is switched On And Control 'Icon Switch' is not switched Fast On And Control 'Icon Switch' is not switched Off Then Wait 5 minutes Set 'Icon Switch' Off Else - No Actions - (To add one, press 'Action') and If Time is 11:00:00PM And Status 'Icon Switch' is On Then Set 'Icon Switch' Off Else - No Actions - (To add one, press 'Action')

No, the KeypadLinc buttons are simple on/off devices. For conditional logic like that, you need an ISY or an automation application like HAL or Girder.

No, if you use Repeat Every xx:xx:xx, it'll continue to repeat at that interval until the trigger condition is no longer true. Instead, use something like this: If Control 'Motion Sensor Entry' is switched On Then Repeat 3 times Set 'Dimmer A' On Set Scene 'Scene A' On Wait 2 minutes Repeat 1 times Set 'Dimmer A' Off Set Scene 'Scene A' Off Else - No Actions - (To add one, press 'Action') In this example, the program would send a direct command to 'Dimmer A' On, would set Scene A On, would wait 2 minutes, send the commands again, wait 2 minutes, send the commands again, wait 2 minutes, then turn every thing off and end the program.

The ISY actually has a Repeat command. From the Wiki: So you could say Repeat 3 times, then turn a device or scene on, then wait 3 or 4 minutes, and the ISY would execute the action and the wait time 3 times.

That's because you can't send direct commands to control secondary buttons, the Insteon protocol doesn't provide a way to do it. Instead, create a Scene, add that button D to the scene as a responder, then turn the scene off.

For the program to work as-is, you need to remove the keypadlinc button g from being a controller of any scenes.