oberkc

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.

Yes. Sorry. (I am following too many posts.) Perhaps when you upgraded to the -994 something similar happened. I still think the common denominator here is battery devices.

All wireless. More to the point, I suspect: all battery operated. Perhaps I can speculate..... New PLM has a new insteon address. Restored PLM from ISY, no problem. This, however, breaks the links in connected devices. Hard-wired devices are always in listening mode, and restoring PLM automatically fixed these broken links. Battery operated devices, however, have to be put into linking mode in order to write updates. When you restored the PLM, did you put the battery devices into linking mode? I wonder if your battery devices had a little colored icon next to them before you restored them? Again, speculation. But that is my theory and I am sticking to it.

I have to refressh my memory every time. I recall it has to do with deleting temporary files. Hopefully it will be obvious when you open the java app.

Are you trying this while at home? Static IP should not matter in this case. I remain unclear how all this plays together, but I recall such problems are often associated wih java or antivirus. Perhaps you could dig a lttle deeper into these areas? Clear java cache? Amtivirus blocking access? They oftern bring up avast antivirus as a common problem. Has anything changed in these areas?

There is a "beta" z-wave card you can add to your ISY. i dont yet use one, but it looks pretty solid to me. Read about it in the dedicated zwave section. The ISY does x10, yes.

Stranger things have happened. This is not totally unheard of, based on my time spend following these forums. No...I would not go back to the 99i. It is my experience that, sometimes, things happen for reasons that we can never discover. I agree, however, that it is a strange coincidence that it happened to all your motion sensors. My suggestion is to fix it and move on. Try restoring the motion sensors. I don't think it is overly difficult. Hopefully, that is all there is to it.

I read your post. I did not see the scene I was looking for. I believe you need to create an additional scene, with ONLY the 2 keypadlinc buttons, only as responders. Then follow LeeGs approach, using this new scene.

I would modify bsobel's suggestion as follows: From Sunset to Sunrise (next day) Then Repeat 30 times fan on wait 30 mins fan off wiat 30 minutes <<<<<<<<< add this extra wait Else Fan off

I believe you have chose the commands that set the backlight levels of a keypadlinc, rather than turning on a specific keypad button. Have you created the scene with this keypad button yet? Once created, while in your program, select a new action>>>insteon/x10, select the scene that includes this keypad button, select ON for the on level.

That program is likely (in my mind) going to cause you problems. Your THEN path causes the program condition to retrigger, possibly interrupting the fade down. I am a little concerned how that fade command is reacting when the program retriggers. Unfortunately, i have never used the fade down command so am not certain that this is the case. The other possibility is simply that your ISY is not seeing the change in status of your office lights. If so, this represents a communication problem, rathr than a programming problem. For this I dont have anything to offer that hasnt been said many times here. Check for phase coupling. Make sure your PLM is not on a noisy circuit. Filter noisy devices. Etc....

Yes, you are missing a simple, but obscure problem. It did not help that,I was not as clear and precise as I should have been. I dont believe keypad buttons can be directly turned on or off. Instead, you must create a scene that includes the keypad buttons tha you want to come on (even if only a single button) and turn on the scene. Give it a try. I suspect you will find this works.

it does exactly as you describe: triggers from an OFF command, and evaluates false when triggered. When evaluated at other times (from other conditions/triggers) it evaluates as true.

I believe the answer to this is "No". It sounds as if you want these three buttons to come on if any (but not necessarily all of the) light is left on. This generally takes a program that goes something like: if status of light A is on or status of light B is on or status of light C is on etc.... then turn on keypad buttons I would also create a scene that includes all three buttons as responders. I would configure the three keypad buttons to non-toggle-off, and make all three controllers in a scene that includes ALL basement lights.

I probably knew that, but forgot. Yes, the problem I described manifests itself only with scenes. I have confused folks enough here, so I will stop.