oberkc

I fail to see why your second program (including parentheses) does not work. Have you confirmed that the isy is seeing the correct status for the various devices? Check to see when the second program was last run...what is the current program status (true or false)? Given that your first program is triggered by many of the same variables as the second, is it possible that they are conflicting with each other?

You are partly correct, I was not fully understanding your problem. It now sounds as if you have two problems? One, you have a scene defined which has devices (not keypad D) that don't respond. Two, you cannot add a particular keypad button (Keypad D) to that scene. When you select the scene at the admin panel, and it shows the included devices, which of those does not turn off? Furthermore, you confirm that keypad button D is not listed in the included devices, correct? If you find keypad D in the admin panel device listing, and select it, you should notice (at the right extreme of the admin panel) a list showing "controls" and "is controlled by". Is there any indication here that keypad D is controlled by the device that is controller of your "all off" scene? I still suspect communication issues.

Thus the suggestion to first REMOVE it from the scene, then to add it back.

I believe LeeG was suggesting removing the offending keypad button(s) from the scene, then readding. If you do this, confirming that all desired devices and buttons are in the "All Off" scene, identified as controllers and responders as you desire, and still have problems, then I generally suspect communication errors. This assume there are no device failures. How are you turning the scene off? What do you mean by "load is off"? Is the device controlling the load defined as a controller of the "all off" scene?

I have no recommendations on utilities. I began to suspect my port conflict when I tried to remotely log into my ISY and got the stora instead. So far, so good.

The short (and flippant) answer is: because this is the way you have it programmed. I believe that your second program is the culprit here, and that it has to do with the priority of "and" versus "or". Without knowing your intentions regarding these programs, allow me to offer a suggested change to your second program that I hope clarifies the priorities between "and" and "or": If Time is 10:21:00PM And ( Status 'Fam Rm Table' is On Or Status 'Kitchen Ceiling Keypad - A' is On Or Status 'Kitchen Ceiling Keypad - A / Kitchen Cabinets Upper - B' is On Or Status 'Kitchen Pool' is On ) Then - No Actions - (To add one, press 'Action') Else Set 'Fam Rm Key - Ceiling' Off As a further point that I hope is instructive, I DON'T believe the parentheses you have in your first program are necessary.

Yes. Or by a time-based condition.

Yes. Or by a time-based condition.

I believe one of my problems turned out that another network device (netgear stora) was also using port 443. I changed the ISY port to 555, and set the port forwarding the same. This seems to work, for now. I am no longer using the "enable internet access" option from the admin panel.

The first "then" statement changes the Rear BR Can lights to 70%, which triggers an evaluation of the "if" condition, which is now false. This happens before the program "then" statement is completed, which means that the Rear BR Can lights are never turned off.

I am going to try the sticky instructions under the "how to" section: http://forum.universal-devices.com/viewtopic.php?f=26&t=635

Ah. Those 'little more details" left unspoken get you every time.

My router is on a UPS, but I suppose that does not guarantee rebooting. I will look further into manual configuration.

Is the "little more detail" the same as "all the rest of the detail"? Perhaps it best to describe, in english (as opposed to a program example) what you want to accomplish. For example: a. table lamp to come on at 0540 on mondays, wednesdays, and fridays. b. table lamp to remain on until garage door is open, or 2 hours after sunset, whichever comes first. Is this it? Assuming so, change your first program to: If On Mon, Wed, Thu Time is 5:40:00AM Then Set 'LR Table Lamp' On Else - No Actions - (To add one, press 'Action') Create a second program...as I suggested earlier, modified: If control garage door sensor is set on or time is sunrise + 2 hours Then Set 'LR Table Lamp' Off Else - No Actions - (To add one, press 'Action')

I believe I have the same problem, and have never gotten ambitous enough to figure it out. I enable internet access through the admin panel (I have never made any attempt to handle through the router settings). I get a pop-up showing internet (LAN and WAN) addresses. At this point, I can access from android cell phone, both using web browser and conductor app. Sometime later (usually days or weeks), with no changes made by me, I can no longer access the ISY from my android cell phone, using either the web browser of conductor app. At that point, I can go in, disable, then re-enable internet access. It gives me another pop-up window showing the same addresses as before. Access via android cell phone is restored again, for a period of time, after which it stops, and the cycle repeats. Perhaps I am having the same issue as you.

I would do this via program: if control "garage door sensor" is set on then turn "light in the house" off else Actual code wording may vary, but I trust the logic is clear.

my understanding is that battery-operated motion sensors do not listen for communication...they are one-way transmitters. This is to ensure longest battery life. Given this, I don't believe that there is anything a device such as the ISY can do to accomplish your goals. Pending a change in the design of the motion sensor, it will always be necessary to press the set button to perform linking and programming.

Yes

On this, I think we agree. This was my understanding of what he wanted. I perceived that the OP wanted the family room ceiling to act as a night light sort-of thing, coming on during the night-time whenever the other two lights were off. But re-reading the original post, I am no longer confident of this understanding. If, as you understand, the purpose is to turn one light on at a single point of time of the day, and only if the other two lights happened to be off at that single time, then I think we are in violent agreement that the correct program would be: If Time is sunset + 15 And Status 'Kitchen Ceiling Keypad - A' is Off And Status 'Fam Rm Table' is Off Then Set Scene 'Fam Rm Ceiling' On

There are couple of assumptions here. First, I assumed that he wanted the family room light to be automatically on generally during periods of darkness, and not 24 hours per day. Second, given the second program (which turns the lights out at 10:21pm), that he originally wanted the program to operate only between those two time periods. Of course, this period is configurable. I also don't believe the simple condition: time is sunset + 15 minutes, will accomplish the goal. This condition will be true only for an infintessimal time (at sunset +15) and false the rest of the 24 hours. I believe it to be necessary to make this true over a measurable period of time, whether that be from sunset to 10:21, sunset to sunrise, or some other period of time.

I would think this would be relatively straight-forward. There are issues with motion sensor programs near the end of the daily operating period, but I suggest looking at the wiki articles (search motion sensor) and previous forum post to get a sense of those. For your specific example, I am thinking about two programs. One: if from sunset to sunrise (next day) then set coach lights to 35% else set coach lights off Two: if from sunset to sunrise (next day) and control motion sensor is set on then set coach lights to 100% wait set time set coach lights to 35% else I am sure there are other options that would work as well, or better.

I assume your "other lights" are 'Kitchen Ceiling Keypad - A' and 'Fam Rm Table'. Correct? Yes, I have some ideas. Your family room ceiling turns itself back on because it is a condition in your first program. Turning this device off triggers an evaluation, which turns it back on. I don't see why it needs to be there. My suspicion is that it is going to be very easy to get complicated quick with your approach (folders and such). Why not a single, simple program something like: If Time is from sunset + 15 minutes to 10:21pm And Status 'Kitchen Ceiling Keypad - A' is Off And Status 'Fam Rm Table' is Off Then Set Scene 'Fam Rm Ceiling' On No folders. No second program. If the family room light was already on, it will stay on. If it was off, it will turn on. But only between sunset and 10:21pm (adjust to suit your needs).

I don't believe there is anything necessary to save scene settings. I fear that the device failure to stay on zero to be an indication that this is one of the devices that cannot have zero for the "on" level. Ugh. I hesitate to mention this option, because I really don't know how a device will react with two, potentially conflicting, commands. But you may be up for it, so here goes: Try a mutually exclusive relationship between buttons A and B. I understand that, in such a relationship, only one button may be on at any given time (though both may be off). The potential problem that I see is how button B will react when you press button A...does it turn off (mutually exclusive relationship), does it turn on (as commanded by being part of a scene) or does it just go nuts trying to make up its mind from conflicting guidance. Perhaps two scenes will end up being your best bet.

I forget which devices allow this capability, but it may be worth an experiment. Before you create two scenes, select the "A" button from your current, single scene. When selected, you should see all devices in the scene to the right, with "on" levels. Can you set the on level for button B as "off"? If you can do this, then turning on button A will turn off button B.

I own the revue and ISY, but not a Roku. For meager users such as you and I, I don't believe there is any capability for the ISY-99 to send commands directly to either. There may exist options through the ISY-99 network module, but this goes beyond the capability of meager users, as far as I am concerned. If you are willing to fool around with IR, I would expect to be able to achieve some level of coummunication between these devices using IR. I don't recall the level of IR capability in the revue, but you could, concievably, use the smarthome IRlinc transmitter to send commands to the revue and roku.