oberkc

if they are in non-toggle OFF mode, they should blink a couple of times, then turn off. If in non-toggle ON mode, they should blink a couple of times, then stay on. Is this how they are behaving? Yes, this is not surprising. If you want some buttons to turn off in response to presses of other buttons, you would have to create additional scenes, or add buttons to existing scenes. Perhaps it best to summarize everything that you want to happen when you press the various keypad buttons.

If control switch is set on Or control switch is set fast on Then Wait set time Set lights off Else Yes, a running timer will reset if the switch is turned on again.

Are you on your home network (same network as ISY) or outside?

Is it possible that both have an x-10 address assigned?

Yes, it could be a bug in one of the newer versions of software for the ISY. i do not recall any earlier problems reported like this, but perhaps nobody has yet to notice any relationship between lost links and program changes. Can you demonstrate the problem consistently? Can you recreate the scenario that resulted in your missing links? I must admit that the idea that a program change would have an affect on link records is hard for me to imagine, but my knowledge of the detailed relationship between the ISY and PLM is conceptual at best, and based on assumptions and knowledge from others around here. My sense is that the folks at universal devices would be more than happy to investigate the possibility, but that this will be a little difficult without being able to reliably demonstrate a problem.

. Not if you configure a button as NON TOGGLE OFF or NON TOGGLE ON Right click on the desired button within the scene. Is there an option to delete from the scene?

This was how I would have guessed as well, but this would have also been fine for this application. Of course, there would have been a couple of extra (and unnecessary) OFF commands transmitted, but I suspect this would have been unnoticed.

Well...thanks to the input of apostolakisl ald test of larryllix, I would conclude that the codiotion of If time is from 0800 To sunrise (same day) Would be perfect for this application.

Have you tried the simple approach of: On Mon, Tue, Wed, Thu, Fri From 5:50:00AM To Sunrise (same day) Or On Sat, Sun From 8:00:00AM To Sunrise (same day) I must admit that I am unsure what happens with a program when the FROM time is after the TO time. Perhaps you could create a temprary program as an experiment to find out? From A couple of minutes from now To A minute from now Then Else Then watch the program status as the times pass. If the program stays FALSE, you are golden with the suggested simple approach.

It appears that one of the considerations on the wiki is to minimize communication traffic over the powerlines, so they try to avoid sending an ON command to devices and scenes that are already on. I have never seen the need to be overly concerned about this in my house. My programs and needs are relatively simple.

Oooh! Three-phase power concerns me. There is a recent thread somewhere talking about whether the RF relies on the voltage sine wave crossing points as a reference. If so, I cannot help but wonder if access points are effective on phases other than 180 degrees apart. I am unsure if this was resolved, but I think I would seek smarthome advice on this.

This makes me suspect that you have at least one motion sensor as controller in you scene. Please double check that this is not the case. WRT your program, I believe the best approach is even simpler: If Control MS1 is turned on Or control MS2 is turned on Or control MS3 is turned on Them Turn on scene Wait x minutes Turn off scene Else So nothing

Is this posted program named "motion detected"? Or is "motion detected" a different program. If the former, I see nothing in this program that would ever cause it to execute the ELSE path (and turn false). If the letter, please post it as well. I am still waiting for you response to earlier questions regarding scene members, including controllers and responders.

You have a lot of things going on here, and I can think of several possibilities. You have a program AND scenes? You may need to describe both. LeeGs suggestion to post the program is a good one. Also, as LeeG suggests, one of the problems may be in motion sensor configuration. Things that are going through my mind: Is your motion sensor sending ON only or does it send ON and OFF commands? Is your program based on STATUS or CONTROL conditions? Is your motion sensor a controller in your scenes that include the lamplincs? Do you have any unsaved changes to programs or motion sensor configuration? Is your PLM seeing the motion sensor commands? Answers to questions like that will be important to isolate this problem.

I know only what I can read from the manual, but it seems to me you would use the "latching" mode. Hot and neutral to the module, switched hot (from the three-way switches) to the sense, and fixture hot to the module "load" wire. Are you familiar with three-way wiring? There are several variations, but be aware that this will likely be easiest for you if power is introduced at the fixture. If you have a configuration where power is introduced at one of the switches, you may not have enough conductors to make this work without additional cabling. If this is the case, you may want to consider putting the micromodule in the switch box that feeds the fixture.

Access points are insteon devices available from smarthome. They are relatively easy to find with your favorite search engine. Or you can go to smarthome and search for "access point". The part number is 2443. The web page is: http://www.smarthome.com/2443/Access-Po ... and/p.aspx By "properly placed", I mean in accordance with the manual for the access points. The purpose of the access points are more than one, but I suggest them as a means to provide communication between the legs of your electrical system.

This program should run, as near I can tell. I don't think you are missing anything obvious. I do not believe an accidental off is a problem. Were this me, I would watch the ISY event viewer and have someone activate the motion sensor. Does the event viewer register the detection? I suspect this is where the problem lies. If the event viewer fails to register the detection, I would be looking for are communication issues or link record errors. If it DOES register the motion, but the program fails to run, I would be looking at whether the program is disabled, or in a folder that is disabled. The fact that the motion sensor can communicate via scene to another insteon device is not conclusive evidence that it is communicating with the ISY/PLM.

While I have not yet used one, it is my understanding that this is within the capability of a micro module. If the light is a plug-in device, a syncrolinc does this, and most lamplincs have local sense capability. Regarding insteon switches on a three-way....it is either all or nothing with insteon. You cannot mix and match insteon and standard switches. I am unsure if this was your intention, but wanted to be sure that this was clear. If, however, your intention is to power the fixture from the load wire of the micromodule, perhaps you could get away with one insteon switch and one mechanical switch (another example of something I have not tried).

If your lights are turning on in ways that you dont expect from your programs, confirm by ceching last run time for the program to see if it coincides with the unexpected lighting activation. Yes, my motion sensors can be activated by cars and leaves and many things.

This tends to suggest to me that the old passive coupler was not necessarily useful for insteon. I believe you need to find a way to communicate between the legs of your electrical system. I also believe two properly-placed access points are the best way to do this.

Yes, there is sometimes a noticeable delay when using programs. This can get even more noticeable as quality of communications drop.

I am near certain that it can, but am only superficially aware of how that works. It has something to do with the ISY network module and sending the correct network commands to the hub. I understand that finding the correct commands involves observing network traffic during times when your remote or smartphone is sending commands to the hub ultimate, for the purposes of finding the correct commands. I suspect you are not the first to try. Have you searched this forum for "logitech" or "ultimate"?

Can it be fixed? Almost certainly. However, the cause could be a variety of things. Could be the program. Could be the scene definitions and on levels. I am not sure that I can positively identify the cause from what is written. It is often helpful to post the programs, and identify all relevent scenes, including controllers and responders. OK. It once worked and now does not. What changed? What originally caused the light to come on in response to motion...a program or a scene? By itself, I do not expect this to cause your light to stop responding to the motion sensor. I don't expect this to cause your light to stop responding to your motion sensor. I am curious, however, where is your six minute wait period defined. Is this in a program somewhere? Yes, I think I could come up with a program for this, but the other issues should be solved first. My suggestion is to start by posting all the programs you have that are triggered by, or impact the kitchen lights, motion sensors, or scenes that include the kitchen lights or motion sensors. Also clarify how you have the 6-minute countdown enacted, if not by one of these programs.

Is it possible that the program is disabled? I would expect a little red symbol if so. The program, itself looks correct to me.

Yes, though it has been a while since I did this. I suspect that programs can get corrupted, but that such corruption would cause a general failure rather than alternative results. But this is just speculation on my part. I would review the program status and look for any program that "last run" coincided with the uncommanded light action.