oberkc

I was questioning the second "condition": Status 'alanas bedroom' is not off. I don't see the value in this condition.

While I suspect this is not part of the problem, why not remove the second condition? It seems unecessary, but could be triggering a second evaluation when the then path runs. It also makes the proper execution contingent upon accurate communication of device status. Otherwise the program appears fine to me. Regardless, it is my impressions that programs dont simply stop working. Something else has changed. In what way is you program not working? Is the light not going off? Failure to notify? Keypad button.? All?

I use only conductor, but I like the widgets that are available. If widgets are important to you, make sure that the app you select has them.

I wonder if changing your KPL button mode to non-toggle ON would be one part of the solution. The second part would be to crate the mentioned keypad-controlling scene, then add a program step to the "fan off" and "hi-off" programs to turn the keypad scene off when the fan is off.

It has been my experience that the http://procedureof editing, or the fact that a program was edited, is not a cause of program failure. In other words, I do not believe that it is possible to create an otherwise-functioning program that fails because the wrong editing "procedure" was used. Rather, the failure of a program to behave as one expects is generally the result of the way program conditions and commands work being different that what one believes they do, or should, work. I second LeeGs suggestion to post your program and, perhaps, the fine folks around here could help identify the problem.

Insteon has the ability to set different on-levels and ramp rates, based upon which controller is activating the scene. From the ISY admin panel, my lighting, find the scene in question and expand (showing included devices). With the scene highlighted, notice the on-levels and ramp rates. Picking a controller device within the scene, do you notice the on-levels and ramp rates being any different? If so, adjust as you would like them to be. Notice the option to copy scene attributes. This option is good if you want the same on-levels and ramp rates as defined at the overall scene level, even when the scene is applied by a local controller device.

I think I, too, would break this into two programs: If Control 'Other / Krista's Keypad - G' is switched On Or Control 'Other / Mike's Keypad - G' is switched On Then Run Program 'time' (if Path) Else time program If Time is from Sunset To 10:30:00PM (same day) Then Run Program 'G - All Off Night' (Then Path) Else Run Program 'G - All Off Day' (Then Path) The time program must be disabled.

Update instructions are included with each announcement. Perhaps you have not noticed the "Announcements" forums? Try: http://forum.universal-devices.com/viewforum.php?f=25 So you already use an ISY-99? Are all the fixtures you want to control by motion already controlled by an insteon device (switch, module, etc)? Do you already have insteon RF devices (access points, dual-band modules, etc)? If so, then all you would need would be insteon motion sensors.

I installed 3.2.0 and experienced no problems. My existing shortcuts to the ISY continued to work. I did not have to use the posted link to find my ISY. I installed two fanlincs. Both appear to be working fine. I am in the process of creating scenes. So far...so good. I added them manually, choosing fanlinc from the menu. I have not tried an automatic or auto discover linking proces. I have one more fanlinc to install (both physically and into the ISY). Perhaps I will try an automatic installation here, just for fun. Thanks, again, for the fine support. I would not want to rely on manual linking for fan modules, given the difficulty of access. I believe this represents another strong example of the ISY-99 saving insteon.

. Yes, it is required in order to turn the light off at 735. It sounds, in your case, that you may have had a program with a condition including the switch status rather than just time. A lot of folks seem to use (overruse, in my mind) the following construct: If Time is from 0600 To 0900 And status light is not on. <<< this is the extra line I often question Then Set light on Else Set light off A program such as this could cause problems that you describe.

"offline"? Please elaborate. Last I checked, fanlink was not supported. You will have to wait a bit longer for this.

One does not actually type the commands...they are created for you when you create a new program and use the choices and options provided. No, you need not set it to run. Have you checked out the user manual? The wiki?

I don't know whether this will help with the broader question of helping understand the terminology, but try: If Time is from 0645am To 0735am Then Set family room light on Else Set family room light off Code verbage is approximate, but I hope this communicates the program logic.

The Linking order you describe is backwards...first put the isy into linking mode. Then put the rsponder device into linking mode. Hopefully, your device will now show up.

Alternatively, you could create a program folder, with condition: Program C1 status is true Then run the programs in this folder In the folder, put a program such as: If Time is Sunset Then Set 'Entry Light On' Set Living room.....etc Else -No Actions-

You may check out the wiki: http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Tools_Menu I suspect that this feature is not the most used of the ISY tools.

Probably not, but it will be solved soon. We waited years for the fanlinc, itself. A few more weeks or months is not gonna kill us.

I dont use smartlinc, but.... i understand that the smartlink has no, or very limited, conditional logic built in. Also, I would expect limited integration with other systems, such as weather, security, etc... I am sure there are other differences that I am missing

Not too difficult. You will enjoy it.

It seems to me that the answer to this would be based partly on the level of "access" that one desires. For example, there is some level of access using the default browser. There is also some level of "access" using the apps "conductor" and "mobilinc".

Which is the reason that I suspect that the wiring is other than how described. An alternative possibility is that I misunderstand your description. i suspect LeeG has correctly identified the problem. The white wire is a return from the other three-way switch and is not a neutral. This makes me suspect that the WB and gray supply the entry hall light fixtures. To be more certain (at least in my mind) would require a volt meter and opening of the fixture boxes to confirm routing of wires. On your three way switch, is there a black screw (indicates common). Which wire is connected to that? Are you stating that the neutral wire is connected to the single pole switch somehow? In addition to the blue and purple wire?

I agree with LeeG. I suspect some of the wires are other than you describe. Otherwise, blue wire (line) would go to insteon black, purple (load) would go to insteon red, white/gray bundle (neutral) would go to insteon white and all would work.

For what it is worth, I suspect you do have a loop. In your conditions, you have a condiotion for staircase status. In your then and else statements, you fade down the stairase lights. This forces a re-evaluation of your program.

I have not been bollowing too close, but I recal. That you manually added the newly reconfigured. Is this correct. i have never understanded the advantage of doing it this way, and have read of ocaasional problems. If you are out of ideas, I suggest removing the device, performing a factory reset, and adding it back using the "start linking" button. perhaps things would work better.

First, it seems to me that this program should partly work. The fact that your lihgt does not come on is, in my estimation, not. Program problem. Having said this, I would use control rather than status. Can you control the front bedroom light from the isy? Does the monkey light status track accurately in the isy?