fitzpatri8

Check the sticker for the device version number. Version 1.x of the thermostat adapter had one node, a responder-only device that could be queried for status. Version 2.x has one responder node and 3 controller nodes, with the controllers able to link to other Insteon devices and trigger scenes based on call for heating, cooling or fan. In order to get all four nodes, the hardware has to be v. 2 or above. You may also need to add it to the ISY using device type Auto Discover to avoid defaulting to the v1 capabilities.

What you can do is plug a low voltage power supply into a regular outlet and attach it to the sense input on an IOLinc plugged into the same UPS as your ISY and PLM. Then you'd get an OFF signal when power went out and an ON when it was restored.

It's not yet possible to schedule with a wildcard year, though U-D has put it on the wish list. For right now, you can use ORs to create rules that will run for several years.

Sounds like you've got a couple of problems there. To remove the den light from the scene, first add it to the scene, write the changes to the devices, then delete it from the scene. It also sounds like you've got communications challenges and the message retries are interfering with your program execution. There are other posts in the forum explaining scene tests so I won't go into that here. Add a Wait 10 Seconds command before sending that scene On command to get you going in the meantime.

Are you tapping the Off side of the '.Lights / Bathroom - Powder' paddle or holding it? Do you have any other programs triggered by '.Lights / Bathroom - Powder'? If you run a scene test on that scene, do all member devices pass?

If you click on the Main tab, select the scene Bathrooms - All and click On, do all the lights turn on to 50%? If so, then there's probably a typo in one of the programs. Right-click the first program, Copy to Clipboard, paste to a reply, then repeat for the second program.

No, you need both programs.

See if this works for you: Persistent 50 If From 10:00:00PM To Sunrise (next day) Then Set Scene 'Persistent 50' On Else Set Scene 'Persistent 50' Off

Exactly You didn't say how or when you wanted the program to run, so I surmised you wanted to be able to trigger it manually when you had guests. What did you have in mind?

That's pretty simple: Create a scene with all the devices at 50% Create a trigger program: Persistent 50 If Control 'Your Trigger Device.1' is switched On And Control 'Your Trigger Device.1' is not switched Off And From Sunset To Sunrise (next day) Then Set Scene 'Persistent 50' On Else Set Scene 'Persistent 50' Off Create a second program to fix any inadvertent OFFs: Fix Persistent 50 If ( Control 'Switch 1' is switched Off Or Control 'Switch 2' is switched Off ) And Program 'Persistent 50' is True Then Run Program 'Persistent 50' (Then Path) Else - No Actions - (To add one, press 'Action')

Just create multiple scenes with your desired levels: bedroom 10%, bedroom 20%, bedroom 30%--the devices will ramp smoothly from their current level to the new one at the ramp rate defined in the scene.

I'm on .16 and I also get a blank space instead of Setpoint in Program Heat mode. The Setpoint reappears when I change to Heat mode.

Is there a reason you don't want to use the Fast On (quick double-tap of the On side of the paddle) to run your delayed off program?

A double-tap of a switch sends a Fast On or Fast Off command to responder devices. In the case of a dimmer, the Fast commands override the linked dim level and ramp rate and immediately command the responder to go to 100% (FastOn) or 0%(FastOff). Relay devices immediately respond as on or off, so in theory you could link a relay to a scene with the level of OFF and an On would turn it off but a FastOn would turn it on. If the fan in question is actually powered by a different Insteon device linked to a scene controlled by your switch, you could remove it from the scene and create programs to create different behaviors for On, Off, FastOn and FastOff. Or you could create a program that instead triggered with a FastOn instead of a FastOff.

To post a program here: Go to the Administrative Console, Program Details tab Left-click the program in question from the programs list to select Right-click the program to open the menu Select Copy to Clipboard (the bottom choice on the menu) Switch windows to your browser tab and Control-V to paste. The cost of flashing a light on and off like that is that you are adding quite a bit of signal activity by transmitting a signal every 2-3 seconds. If another device is trying to send a message at the same time its message will be delayed and retried; if another device is having trouble communicating, your automated message will cause the other controller's cleanup message to be aborted.

This architecture allows a program to function as a binary variable, since the persistent true/false state can be used to trigger, permit or constrain other programs without having to leave programs looping through some make-busy task waiting for conditions to change. If you prefer, you can also choose to make the True/False state a momentary condition. Simply append Run Program '[same program]' (Else Path) Else - No Actions - (To add one, press 'Action') to the end of your program. If you do that, so long as the Then statement is executing/waiting/repeating it will display as True on the Program Summary page, then as it finishes its state will return to False.

Thanks, oberkc, for catching my oversight!

If I understand you correctly, you don't need a program at all. Each switch is its own controller, so you only need two scenes: Kitchen All scene should include Kitchen All switch as controller, Kitchen Front as a Responder and Kitchen Back as a responder. Kitchen Back scene should have Kitchen Back as a Controller and Kitchen All as a responder. Kitchen Front will be a responder to the Kitchen All scene but should not be a controller of any scene. (Edit: corrected & added Kitchen Back as controller of Kitchen Back scene.)

I'll start the ball rolling by pointing out program 1 won't ever run because two CONTROL triggers are joined by an AND. Even if you press two buttons at the same time, one signal will arrive before the other and cause the program to evaluate as FALSE.

Go to the Programs tab, select New Folder, name it Backyard Motion, then add the schedule From Sunrise to Sunset to the folder's IF trigger. Now click on New Program and name it Motion Sensed. It will place the new program within the new folder you just created. Click the Condition button, change the Status drop-down to Control, then choose the first backyard motion sensor and On. Click the Add to If button. Now, leaving everything else the same, change the device to the second motion sensor, then click Add to If. Now click the Action button, choose the scene you want to turn on, and Add to Then. Change the On to Off and click Add to Then. Now click on the Insteon drop-down and choose Wait. Select 5 minutes, then Add to Then. Now, mid-screen, click the button that says Move Line Up. That finishes the first program. Next, click on New Program and name it Off at Sunrise. Click on the Time dropdown and change it to Sunrise. Click the After dropdown and change it to Before. Click the up arrow to change it to 2 seconds, then click Add to If. Click the Actions button, select your scene and Off, then Add to Then. Click on My Programs, then click the Save button. Lastly, you'll need to delete whatever programs you previously wrote for backyard motion control to avoid any conflicts.

Two different answers, depending on what you meant by 'program.' You would need to hold down the motion sensor's set button to put it in link mode in order to change the conditions under which the motion sensor transmits a signal or to add or remove a directly linked device. In other words, to change to or from night-only mode, occupancy mode, on-only mode, or to link or unlink a device directly to the motion sensor, you would need to put the motion sensor in link mode to allow the ISY to reprogram it. You would not need to do anything with the motion sensor if you were only changing an ISY program that responded to an existing motion sensor signal or changing the dim level or ramp rate of a device already linked to the motion sensor. Once a device is linked, the ISY can change a responder device's actions by manipulating the database of the responder only.

Must've been some kind of legacy glitch. It happened consistently with old programs, but since I deleted those old programs I can't duplicate the problem with newly created ones.

Anyone else having difficulty disabling or re-enabling just the first program in the list? If I toggle its state and save, move to a different program then return to the top one, it is back in its previous state.

Couple of points here: Is the outlet in question a GFCI or standard outlet? (I ask because all the bathroom fixtures must be protected by a GFCI, but they may be standard outlets that are wired downstream of a GFCI.) If the outlets creating problems are standard, the best way to handle filters here is to semi-permanently affix a filter to the top socket of the outlet such that it covers both sockets, seal off the pass-through outlet, then plug in a power strip and mount that to the adjacent wall. Spend a little extra to get a strip that orients the sockets next to each other instead of above and below and that offers a couple of widely-spaced sockets designed to accommodate wall wart power supplies. The kids should like it, it gives them added flexibility on plug use and a single on/off switch that doesn't require they be plugging and unplugging things when they head off to school. Next, explain to them, in a loving and calm way, that their household privileges are not God-given and are subject to compliance with household rules about not unplugging filters or bypassing filters or doing other things that drive Dad crazy! (If the outlet is a GFCI, you may want to explore changing the single-gang box to a double, then mounting a wire-in signal filter in the box and covering it with a blank wall plate. Then you could plug the power strip directly into the socket.)

I created a couple of new programs to test tomorrow.