oberkc

I suspect this can be done with a single program through brute force, but it would get ugly quick if the number of devices gets much beyond three or four. if (A and B is on) or (A or C is on) or (B or C is on) or ..... then do something As the number of devices grow, the approach proposed by bleepborp may become relatively more efficient.

That sounds right, to me also. Things have changed, it seems. The big point is to understand what ON means in programs, versus NOT OFF, OFF versus NOT ON, etc.... Is 50%/10%/90% on or off? Things like that.

If I understand correctly, I believe the status ON and OFF are limited to relay devices and percentages are for dimmer devices. "ON" would equate to 100%..."Not OFF" would equate to anything over zero....etc. It is important to pay strict attention to the way percentages work versus ON and OFF.

I am a little fuzzy as to what you are trying to achieve. Are you trying to create a program that watches for when the button is manually turned on? Then when turned on, it activates a scene and turns off the button? First thing I would check is that the ISY status is accurately showing the button status.

Yes, I do have an idea. I suspect that the lighting levevs continue to change over the morning (and evenings). Each change triggers the program. In your case it was last triggered at 12:30. The status was likely already false, so the program probably sent an OFF command to lights that were already off. That sort of thing probably happens several times each morning, and each night.

Ah! So it is actually PASSING sunrise and waiting until the light level kicks in? I can see why your program does this. BOTH conditions (time and dark) must be FALSE for the program to be false. If time is sunrise-30 while it is still dark, the program will remain TRUE. Without thinking too much about this, you may need to break into two programs If time is sunset or it is dark then turn lights on if time is sunrise or it is light then turn lights off

Our message timing makes me suspect you missed my suggestion.

How do you set your location? Lat/long?

Have you tried a different light level to see if it better matches your expectaions?

I remain a little uncertain how this all works together, but suspect your issue is a failre to use a scene command to control the IOLinc. Try creating a scene, adding the IOLinc relay as responder. From the admin panel, does issuing scene commands solve your problem?

Outstanding!

There is an additional possibility, albeit unlikely. Perhaps there was an X-10 address somehow assigned to both buttons. A factory reset and restore would take care of this, also. I was hoping the compare device links would reveal a problem. Too bad. I hope this is not a failed device.

If the main button is not shown as controller of anything, and is not a part of some program as a condition, then the likeliest cause in my mind (short of device failure or some sort of communication gremlin) is that there are links in this keypad unknown to the ISY. Right click on the device, and choose "show device links". Then choose "compare". Does it show any mismatces? If so, you may want to perform a factory reset on the keypad and restore it from the ISY.

It sounds as if you are well on your way. The only thing I would offer at this point is to further refine your thought process and requirements. What do you want to happen if you turn the switch on while the light are currently OFF? Is this different than what you want to happen if you turn the switch on while the lights are currently ON? How does this affect your program?

I am back. With regards to your second program (the one with the 30 second wait period), I continue to suspect the problem was not a programming issue, but a motion sensor configuration issue. From the ISY, select the motion sensor in question. Select "options". You may need to now put the motion sensor in linking mode. Notice there are a couple of options with regards to sensitivity and continuous ON commands. Make sure the continuous ON commands are checked, or that you select a timeout period much less than 30 seconds. Note, too, that the physical jumper 5 must be set to allow for software control of the motion sensor. (This is described in the manual for the motion sensor.) "this program" would be whatever was the name you gave for that program itself. Regardless, clearly the two programs you tried originally had no relationship to each other. One incremented and cleared the value of a variable. The other responded to a motion sensor without regards to the value of the variable. In your original post, I was under the impression that you had an idea what you wanted to do with the variable and how to do it. Your only question, I thought was simply how to clear the variable after 30 minutes. That was the question to which I was responding. If you want some thoughts on how to use a variable to vary the response to the motion sensor, I may be able to offer some ideas.

My original program suggestion was in response only to the only question that I noticed: "I'm not sure how to do it but I want to set that variable so that it gets reset to zero when the motion sensor has not sent the ON command on anything over 30 minutes." I should have been more clear as to the request to which I was responding and the limit of scope I was offering. That is exactly what that program should do, unless you get another ON signal from the motion sensor within the 30-second wait period. I don't have a lot of time right now to offer deeper suggestions, but I would start by checking the configuration of your motion sensor. In it is a setting that defines how long to wait until re-enabling the sensor. If that is higher than 30 seconds, then there is no way for the sensor to send ON commands quicker than the program wait period, thus the program will always turn off the light. If you don't get additional suggestions, I will be checking back and offer more.

This could depend on how you relate the remotelinc to the garage door. Is it via a scene? A program? Both? I do not expect that the remotelinc to be sending multiple commands. It could also be unrelated. Perhaps there is something that suddenly blocks your safety sensors. Perhaps there is some binding in the door motion. If this happens when the door is opening as well as closing, I would tend to discount this possible cause.

I have already offered a suggestion. Whether or not it is better or more efficient, I will leave to you. Certainly, it is fewer lines of code. The ISY keeps a log that would provide the clues you are looking for. I don't believe, however, that there is a native way to Email this log to anyone, however.

As you say, the grace solo can be turned on and off through the app, but the necessary amp remains unaffected by the grace app. Also, the grace does not draw enouh power to trigger one of those smart power strips (at least none that I have tried). One of these days, I may take some time to solve this problem, but we dont use music enough to make it a priority for me.

I use insteon motion sensors outside, though protected from direct exposre from rain. I am not sure if this is as bad as th humidity of a shower, though. I can think of no reason that your logic cannot be implemented.

My tmptation, from a logic standpoint, would be something like: If Control motion sensor is switched on Then Set integer variable to integer variable +1 Wait 30 minutes Run this program (else path) Else Set integer variable = 0

I use a grace music streamer, controlled by various iOS or android apps. I dont believe it can play from the cloud locations, but it can play music from a network server or your computer. It also can play from things like pandora or iheartradio.

I would problably take a different approach logically. I would not like the two-second delay when the pantry light turns off, then on. First, I would take the sensor out of any scene relationship. Second, i assume that the pantry lights are responder to the "particular" scene and will turn on and off with that scene. Then, i would create a couple of programs If Control sensor is switched on And Status pantry spots is off Then Set pantry spots to 37% Else Nothing If Control sensor is switched off And ( Status kitchen mud is not on Or status kitchen hall is not on Or status kitchen dining is not on ) Then Set pantry spots off Else Nothing Regarding your program, i am surprised that a wait would be required. What happens when you take it out completely? On first inspection, I dont see much wrong with your program, but am unclear about the scene relationships you have and wonder about the same issue raised by erick. Is the door sensor controller of a scene that includes the mud, dining, or hall lights?

I agree with xathros...I see nothing in that program that would cause an ALL LIGHTS ON result. Is it possible there is another program, based on those variables, that would cause this. I am also under the impression that these random ALL ON events can be triggered by a failing PLM.

This program would be much simpler. If all you want is to cycle your pump/heater every 20 minutes between 5am and 6am, try: if time is from 0500 to 0600 (same day) and elk is not armed then repeat turn on pump wait 20 minutes turn off pump wait 20 minutes else turn off pump