oberkc

Or use an ISY-99 program to control when the light goes out after detection of motion.

How are you sending this "on" command? From the ISY-99 admin panel? From the ISY, via mobilinc? Are you choosing the relay, itelf, when you send the command, or the scene? If you are selecting the IOLinc relay, itelf, you are sending "direct" commands. It is not the mere presence of a scene that matters, but whether the IOLinc is responding to a scene command from one of the controllers in a scene. Is there a controller defined in this scene, or is it an ISY scene with one device (the IOLinc) as a responder?

I think it is almost certainly the dimmer. This sounds a lot like the problem with some of the insteon devices with "sense", where they allow a small current through in order to detect when connected devices are turned on manually. Unfortunately, I don't think the switchlinc dimmer is one that has this capability, nor would I expect an incandescent rope light to exhibit this problem. I can only guess a failed device. This sure sounds like a strange failure mode, if this turns out to be the case.

This, I suspect, is why your lights come on, rather than your program ever working. The question that you may need to resolve is the difference between this scene, and the one called "Garbage Night". When you press keypad button C, it will initiate the scene for which it is a controller. The program would also immediately initiate another (or is it the same) scene. This seems like a recipe for complications.

Indeed I should have included this change.

I suspect you have several potential problems going on here. For the reason pointed out by LeeG, this program will never evaluate as true, which suggests that the lights came on for a reason other than the program working (under the program listing, I suspect you will see a status of "false"). Is button C part of any scene as controller? I assume your other program has the sunset-to-11pm condition, correct? Does the else path of this program turn the landscape lights off? If so, then I see nothing in this first program that would distinguish between the pre- and post- 11pm time frames when the 8-minute wait period expires. As written (and given these assumptions), I would expect the landscape lights to ALWAYS turn OFF after 8 minutes, whether before or after 11pm. So...in addition to LeeGs suggestion, I would suggest that your first program might be better as: If From Sunset To Sunrise And Control "Main hallway Keypad C" is switched on Then Set Scene "Garbage Night" On Wait 8 mins Run program "Landscape Lights" (If Path) << Else -No actions- A third potential problem is what happens if you decide to take out the trash less than 8 minutes before sunrise. While this may not be a practical problem, if it ever happens, the 8 minute wait period would be interrupted, the program would turn false, and the lights would never turn off.

There are a couple of examples on the wiki. There have been many threads on this, but sometimes they are hard to sort through. Try: http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Using_Motion_Sensors_in_Bathrooms I don't know that this will do what you want, but try breaking your program into two: If Status 'Bath Master' is Off And Control '4 Bath-Sensor' is switched On Then run next program (then path) Else - No Actions - (To add one, press 'Action') Next program: if then Set Scene 'sf Bath Master / sc Bath Master 40%' On Wait 2 minutes Set Scene 'sf Bath Master / sc Bath Master 40%' Off else

It is certainly possible. This is not the simplest of tasks, but not the most complicated, either (I suspect the use of variables to offer the most efficient solution here). I have not personally felt the need for such a program. Given the cost of a keypad, I found it more economical, and equally functional, to simply use an off-the-shelf solution from Lowes or Home Depot or similar places. The only benefit is see to using an ISY program is if you prefer the look of the keypad, or unless you desire some unusual time settings (such as 8 min 23 sec) not available from a standard wall timer. I also recall threads on this topic and, perhaps, a wiki article. You may find it valuable to search for these. A lot of folks are incorporating motion sensors and lights as a trigger for turning the fan on and off.

Thos is how I do it also, then use sunrise and sunset to limit operation during daylight hours. Sometimes clouds can make it dark early, but I have found this wholly adequate. Perfect! The only question I have is why you contine to use A4? Is the switch for your stagecoach lights x-10 only, not insteon? in case you were unaware, the eagleeye uses two x-10 addresses. In your case, a-11 for motion, and one higher (a-12) to send a-12 on when dark and off when light. You may notice these commands if you watch your evevt viewer. i like the way you did it.

Good. Regarding the motion sensor program, I am hoping my earlier suggestions gave you some thoughts on how to proceed. I also hope you were able to check in the wiki and get an idea of the various considerations that on has on how to handle this. If all you want is to turn a light on for a few minutes at the sense of motion, it is relatively simple. The complexities begin when folks start realizing that such a program overrides manual control and they loose the abililty to leave the light on indefinitely. I suggest you ponder the exact details of how you want yours to work and write them down. In my opinion, it seems folks don't think enough about what they want before trying to come up with a solution, only to spend a lot of time on programs that are never used because the program did not do what they wanted because they did not know what they wanted until after the program was written and....on and on. Most of all, have fun with this stuff.

Are these not the same versions?

Unable, or did not know? My suggestion is to start with this simple program and see if you can get this to work. Then try the motion sensor program. Sure it does. It also sounds like you are still in the conceptual stage. Do you have a sensor on the garage door, wired to the EZIO6I. Have you added these to the ISY-99?? Unfortunately, my familiarity with the Mobilinc is conceptual only.

First, I suggest checking out the wiki and look at the examples for motion sensors. This is a pretty classic example for programming. Also, much electronic ink has been expended on various threads. It is worth time looking at this. Second, clarify what you WANT your programs to do. Do you want your motion programs to work based on darkness or sunrise/sunset (can be different). Do you want your garage lights to come on/off based on darkness, or sunset/sunrise? Can you change the behaviour of your motion sensor to send motion-triggered signals regardless of dark conditions? (Is you motion sensor one of those eagle-eye devices?) Third, it would help to know what devices control your various lights. Is it a single insteon switch that controls garage stagecoach lights? Is it a single insteon swtich that controls front stagecoach lights? Are all your devices added to the ISY-99? Are any of these switches part of any scenes? Assuming the most simple possibility with regard to your garage stagecoach lights, have you tried any programming at all? Would something simple work (note there is no need for any X-10 input here): if from time is sunset to sunrise (next day) then set stagecoach lights on else set stagecoach lights off The motion sensor/front lights would be typcially achieved with two programs, with logic something like: if from sunset to sunrise (next day) and x-10 motion sensor address A1 on recieved then run timer program (else path) else if then set front stagecoach lights on wait 2 minutes set front stagecoach lights off else Based on your description of your third program question, it would conceptually be little more than: If control EZIO6I is set on then set appliance module on else

Event Viewer? http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Using_the_Event_Viewer

Agreed Agreed. If not every switch, certainly all that are of interest. I believe this is consistent with the two examples suggested so far.

Much depends on what you want to do based upon the state. If you want your program to trigger at any status change, and always evaluate as true, then you may try: if status 'device A' is not off or status 'device A' is not on or status 'device B' is not off or status 'device B' is not on . . . then wait timeout period run this program (else path) <<else This program would be true if sees any activity within timeout period and false if otherwise.

What happens when you try this link: http://www.universal-devices.com/99i/ ?

I believe enabled/disabled. A folder turning true does not trigger the included programs. If a folder turns false while a program is executing, however, my instincts are to suspect the program to continue execution unless it includes a wait or repeat. I would verify to be sure.

Your lights are plug-in? If so, your options are modules, outletlincs, or inlinelincs feeding outlets. Outletlincs and inlinelincs require permanent installation into your electrical system. The problem you are experiencing has to do, I believe, with the "sense" capability of the modules and outletlincs. These devices send a small current through the load, in order to sense local control has been activated and to turn on, in response. Unfortunately, this small current is enough to cause some LEDs to glow, when off. I don't believe the inlinelinc has this local control capability. If not, then this should be a viable option for you. As an alternative, many have reported success by adding, in addition to your LEDs, a small (somwhere around 5W) load to the outlet of the module. The addition of a small nightlight or power supply can often be enough to alleviate the glow of the LEDs. Unfortunately, this partially offsets the benefits of using LED.

With the ISY-99, scene level ramp rates (and on-levels) are those that are activated when the ISY-99 (PLM as controller) activates the scene, most likely through a program. The scene controller level settings are the ramp rates and on-levels in play when activated by that specific controller. This is one of the basic features of insteon...the ability to set different scene settings based on the controlling device.

I have used non-dimmable CFLs on insteon dimmer switches. I set on levels to 100% and ramp rates to instantaneous. Interestingly, when CFLs were relatively new (and before they were dimmable), I had some cases where insteon relay devices (plug-in modules) with smaller CFLs would not respond to commands, whereas insteon dimmer modules with these same CFLs would work. Because I wanted to use CFLs and control them with insteon, this forced me to use dimmable modules with non-dimming CFLs. I have not experienced this problem with newer devices or lamps. With the introduction of LED, and my general dissatisfaction with the dimming performance of CFL, I tend to keep CFLs on relays only. Still, I think I have two cases of non-dimming CFLs on dimmer modules. Have been this way for about four years now and see no reason to change. They work. They continue to work. I have had no device or lamp failure during this period. They are controlled by ISY-99 program only, so risk of accidental dimming is minimal.

I tried to check out my morninlinc, and find it inoperable. The LED is dimly flashing. No communication appears possible. Factory reset does not restore anything. I guess it will be a few days before I can confirm my original belief: on and off devices appeared to serve no separate function. Both would lock or unlock my morning industries door lock.

That was my initial impression. However, upon installation, I found that I could put either of the two devices in a scene and lock or unlock by sending either an on or off command to the single device. In my mind, this created a bit of redundancy. Will respond again when confirmed.

I notice the same thing. Two devices. Both able to lock and unlock the door. I was just too lazy or uniterested to ask the question. That being the case, I look forward to any insight anyone cares to offer.

Apostolakkisl suggestion is quite viable and may be the easiest approach. But there are date conditions in the ISY-99 (I believe they are part of the time condition). I have two program folders for seasonal programs, winter (nov-mar) and summer (apr - oct). I use the date condition for the program folder if from 12:00 am on 1 November 2011 until 11:59 pm on 31 March 2012 then run the programs in this folder In each folder I add the programs that I want to run during the respective seasons. Each year, I simply update the conditions to reflect the new year. If I wanted to take the next step, I could create a multi-year condition: if from 12:00 am on 1 November 2011 until 11:59 pm on 31 March 2012 or from 12:00 am on 1 November 2012 until 11:59 pm on 31 March 2013 then run the programs in this folder I believe that there are even examples on the wiki where one can use a variable to reflect a date without a year, thus creating a program that would have a condition equivalent to from 1 November (any year) to 31 march (any year) But I have apparently decided that it is easier simply to change the dates each year.