johnmsch Posted August 20, 2017 Posted August 20, 2017 I have one of the buttons ( on my 8-key keypad that turns on multiple lights via a program in my ISY994i. One of those lights also has its own button on the keypad (E). I'm trying to figure out how, when button B is pressed and that button light goes on, to also turn on the LED light on button E. Also, if button E is pressed while B is on, it would turn off that light only. I used to have this setup on an older 6-button keypad in another house, but can't remember how I set it up.
stusviews Posted August 20, 2017 Posted August 20, 2017 Add button E as a responder to the scene that has button B as a controller.
johnmsch Posted August 20, 2017 Author Posted August 20, 2017 I believe I set it up correctly, but its not working. I created a new scene and added button B as a controller, with button E and some other individual switches as responders. When I hit button B, it's LED comes on, but none of the devices turn on. This got me thinking about the old setup at a different house. I now remember not using scenes in that setup, but did everything in a program, since I did some variable manipulation and some Wait delays also. The program was activated when one of the keypad buttons was pressed. It turned on some individual lights, a scene, with Wait delays between each one, and set a couple variables. I got a lot of help from you guys here to get that working, but can't find the thread. Looks like we can only go back 6 months searching for messages we posted here.
stusviews Posted August 20, 2017 Posted August 20, 2017 If you have button B as a controller, then any other device in that scene should turn on (or off). It doesn't matter if the other device are responders or controllers because all ISY scene controllers are also automatically responders. Are you sure that you added button B as a controller? Scene controllers show in red, responders in blue.
danbutter Posted August 21, 2017 Posted August 21, 2017 I have a very similar issue. Don't mean to hijack here, but maybe we can both learn something new. So in mine I aldo have an 8 button and a light (fanlinc light if it matters) controlled by button A. Now if I hit button A it will light up and the light turns on. My problem is if something else turns the light on the A button won't light up. I have a scene with the light and the button in it, but the button is a controller. I can't figure out if there is a way to change it. If there is I haven't found it.
paulbates Posted August 21, 2017 Posted August 21, 2017 (edited) I have a very similar issue. Don't mean to hijack here, but maybe we can both learn something new. So in mine I aldo have an 8 button and a light (fanlinc light if it matters) controlled by button A. Now if I hit button A it will light up and the light turns on. My problem is if something else turns the light on the A button won't light up. I have a scene with the light and the button in it, but the button is a controller. I can't figure out if there is a way to change it. If there is I haven't found it. Whatever the 'something else' is has to be a controller in the scene you are using, or, control the scene and not the device. If "something else" is a program or mobile app, have those set the scene on/off and not the device directly. Paul Sent from my iPhone using Tapatalk Edited August 21, 2017 by paulbates
johnmsch Posted August 21, 2017 Author Posted August 21, 2017 If you have button B as a controller, then any other device in that scene should turn on (or off). It doesn't matter if the other device are responders or controllers because all ISY scene controllers are also automatically responders. Are you sure that you added button B as a controller? Scene controllers show in red, responders in blue. Yes, it was setup correctly, but I believe I found the problem. When I set this up, I was using an existing scene. However, after setting everything up, I inadvertently deleted that scene and had to recreate it. Even though I used the same scene name, it appears that I would have to go back and update every place in the ISY that used that scene name and update the statement. Apparently, just because you use the same scene name as before, the ISY must keep some kind of pointer to the scene and doesn't see that scene, even with the same name as before. However, this doesn't solve my issue as I prefer to do this programmatically. I really like the effect of having a 2 second delay in between turning on each light. Gives a cascading effect as the lights come on, front to back. Additionally, I have to set two variables when the B button is pressed. Found that I do have a backup of the ISY program from the other house that I could restore to see how I had set this up back then. The question here is, can I restore a backup from a much older version of the ISY to the one I have now? Of course I would do a backup first, restore and view the old programs, then restore the current one.
Teken Posted August 21, 2017 Posted August 21, 2017 Yes, it was setup correctly, but I believe I found the problem. When I set this up, I was using an existing scene. However, after setting everything up, I inadvertently deleted that scene and had to recreate it. Even though I used the same scene name, it appears that I would have to go back and update every place in the ISY that used that scene name and update the statement. Apparently, just because you use the same scene name as before, the ISY must keep some kind of pointer to the scene and doesn't see that scene, even with the same name as before. However, this doesn't solve my issue as I prefer to do this programmatically. I really like the effect of having a 2 second delay in between turning on each light. Gives a cascading effect as the lights come on, front to back. Additionally, I have to set two variables when the B button is pressed. Found that I do have a backup of the ISY program from the other house that I could restore to see how I had set this up back then. The question here is, can I restore a backup from a much older version of the ISY to the one I have now? Of course I would do a backup first, restore and view the old programs, then restore the current one. No problem ~ Only caveat is to ensure you use the matching UI / Admin Console. Otherwise you may see odd behavior or unexpected results. Please ensure you clear out the Java cache and select all option box's if you decide to use a older Admin Console.
johnmsch Posted August 22, 2017 Author Posted August 22, 2017 Problem solved, and I didn't have to do a restore. I was driving this afternoon and the proverbial light bulb went on over my head. stusviews was trying to push me in the direction of using scenes and it finally sunk in. I created a scene for each one of the 8 buttons on the keypad. I then setup some programs that would catch buttons being pressed and run scenes for the others. So, in my original (albeit simplistic) hypothetical example, when button B is pressed, that event executes a program that sets the scene for button E to on. Now I don't have to worry about turning the individual LED's on programmatically, and I can turn E off without disturbing B. I also have the luxury to set variables in each one of the programs, cascade with delays before calling other scenes, and watching the buttons come on as those scenes are executed. Thanks again stu for the nudge!
Recommended Posts