oberkc

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.

I am not so sure. I have found the logic statements to be extremely versitile.

I was concerned that someone may read your earlier suggestion to put it into one of the momentary modes (A, B, or C) and conclude it did not matter. In this case, it might.

I would expect that sending an OFF command COULD cause problems if the relay is configured to respond to both ON and OFF commands. No?

In what momentary mode do you have it? What makes you believe that it does not "automatically turn off"? Understand that the status as shown on the ISY represents the last command sent to the relay, and not necessarily the status of the device.

Does it do what you want?

Programming, at any level, is an precise and unforgiving endeavour. The good news is that it will do exactly what you tell it...every time. The bad news is that it will do exactly what you tell it, regardless of whether that is what you want.

This can be done without variables if you would rather avoid it for now. I agree it best not to try to run before being able to walk. As a reminder, i offered you a proposed solution should you care to try it. I agree with one point about variables, however...they can help make it easier to visualize what is happening. Just remember, your KPL button is more than an indicator. You have also expressed interest in using this button to turn on and off your lights. Another observation I have is that it seems you may be trying to hit a moving target. I am a fan of working through your requirements...understaning what you want....before going too deep into a solution.

Erick, upon reflection of apostolakisl's comments, I believe he found a problem with your second program that I did not catch. If you were to toggle your KPL button before midnight, it would turn off the landscape lights. I suspect you would find this less than desirable.

No, I did not include this provision to manually turn landscape lights on. If you want that, you could modify the first program such as: if time is sunset-10 minutes and control KPL button is not switched off or control KPL button is switch on then turn on landscape lights else turn off landscape lights Simple enough. I see no problems here. If all you want to do is "keep" the lights on at midnight, then you have a little duplication. There is no need to turn on lights that are already on. But I think you may have devised a way to address all your concerns in two programs rather than my three programs. Nice! As I see it, this program would trigger at three distinct events: at midnight, at sunrise-1hour, and any change in status of the KPL button. At midnight, if the KPL button is off, the lights turn off. At midnight, if the KPL button is on, the lights stay (or turn) on. At sunrise-1hour, the lights will turn off regardless of the KPL status. Additionally, between the time of midnight and sunrise-1hour, the KPL button will toggle on/off the landscape lights. The only question I have for you is whether you want anything to happen to the landscape lights when you toggle the KPL at times other than between midnight and sunrise-1hour?

Is this not what you expected?