mcqwerty

Done: http://forum.universal-devices.com/topic/21925-enable-triggering-of-programs-via-scene-a-proposed-solution/?p=213566

Sorry for being late to this party but I have more to add on the subject: I am of the opinion that a Scene is not an device but a trigger such that is has no 'status' but can be 'switched' in ISY terms. Regardless of the particular levels each responder in a scene is programmed to respond at, if any controller of a given scene issues an ON, OFF, DIM or BRIGHTEN broadcast as a result of a physical press of the device then this should be able to be used as a trigger of an ISY program defined as: If Control 'myScene' is switched On/Off/Dim/Brighten If Status 'myScene' is [anything] would be invalid since a scene has no Status. Since the PLM is a controller and responder of all scenes setup by the ISY, the PLM and hence the ISY would see all 'all link broadcast' messages from all scene controllers and would also receive the cleanup messages sent to each responder from the controller so it should just be a case of how the ISY chooses to interpret this. Regarding a scene 'set' AKA triggered via REST or via an ISY program, then I think it may be breaking some 'rules' to have that count as a 'Control 'myScene...' event since it was not initiated by a physical action, however I could argue that an exception should be made for this particular case. Also, for clarity, I would still expect the ISY to raise a Control and Status event for the individual device that was pressed, but if that device is also a controller of a scene then I think a 'control' event for the scene 'item' should also be raised as detailed above. Anyway, I realise any of this would be new functionality for the ISY firmawre, but if the first step is to reach a proposal that work in all cases and is as intuitive as possible I would like to open this idea up to comment. Thanks!

I think I have answered my own question. Writing the original post helped me think it through. I think the problem is a combination of using 'Control' rather than 'Status' and also introducing the 1 second wait. I assume that while the Control will trigger the program and the wait will begin, at almost the same moment, the Status will also change which re-runs the program and cancels the wait. Since when the status changes, the Control of the other door has not changed, then neither logic path equates to TRUE and hence the 'Then' is never triggered. I changed my program to: If Status 'Main Floor / Master Closet / Family Foyer Door Sensor / Door Closed' is 100% And Status 'Main Floor / Master Closet / Master Bathroom Door Sensor / Door Closed' is 100% Then Wait 1 second Set 'Main Floor / Master Closet / Can Lights' Off Else - No Actions - (To add one, press 'Action') and all is well. Hope this helps someone else in the future

I am trying to control the lights in my closet with hidden door sensors on each of the two doors to/from the closet. 2x 2845-222 configured as two nodes each in each door 1x 2477D controlling the load on the lights ISY994ZW 4.2.18 Firmware The 2477D is between the two sensors and there is less than 5' from sensor to switch. I am trying to set up the system so the lights will come on if EITHER door is opened and only go off if BOTH doors are closed. Making the lights come on is simple with a single scene containing the two 'Door Open' nodes as controllers and the switch as a responder. Making the lights turn off has proven more of a challenge. I wrote a program to control this and is shown below: If ( Control 'Main Floor / Master Closet / Master Bathroom Door Sensor / Door Closed' is switched On And Status 'Main Floor / Master Closet / Family Foyer Door Sensor / Door Closed' is 100% ) Or ( Control 'Main Floor / Master Closet / Family Foyer Door Sensor / Door Closed' is switched On And Status 'Main Floor / Master Closet / Master Bathroom Door Sensor / Door Closed' is 100% ) Then Wait 1 second Set 'Main Floor / Master Closet / Can Lights' Off Else - No Actions - (To add one, press 'Action') This does not work as desired. But, if I copy the program above twice, and edit each as below: If ( Control 'Main Floor / Master Closet / Master Bathroom Door Sensor / Door Closed' is switched On And Status 'Main Floor / Master Closet / Family Foyer Door Sensor / Door Closed' is 100% ) Then Wait 1 second Set 'Main Floor / Master Closet / Can Lights' Off Else - No Actions - (To add one, press 'Action') and If ( Control 'Main Floor / Master Closet / Family Foyer Door Sensor / Door Closed' is switched On And Status 'Main Floor / Master Closet / Master Bathroom Door Sensor / Door Closed' is 100% ) Then Wait 1 second Set 'Main Floor / Master Closet / Can Lights' Off Else - No Actions - (To add one, press 'Action') then I get the desired behavior. I know the parentheses are not required in the two split programs, but I left them in to verify they were not causing a problem. Why does my single program not behave as I expect?