Vipola

Note also that it's a older keypad: 2486D KeypadLinc Dimmer 6 Buttons v.35, maybe less guaranteed rewrite cycles..

Yes that's exactly what the code do.. sorry for the confusion, my keypad (and it's load) is named from it's A button.. The program does change the backlight level for all the button of the keypad so it is completely off at night.. So that program would reprogram the backlight level several times a day (over 10 times) for over 1 year.. now the keypad just throw error whenever I try to write to it..

I have some communication issue with my KeyPad and cannot reprogram it.. I tried to factory reset it, I'v tried to move it.. it just won't write to it anymore.. Is there a number or write you can do on a Keypad?.. I wonder if I killed it with too many write update from a little program I used to run.. http://forum.universal-devices.com/topic/14122-keypad/ My Girlfriend use to complain about the 'backlight' of the KeyPad been too bright during the night, so I wrote a program to close the backlight when the light is closed.. If Status '2nd / BedRoom / LightWhite' is Off Then Set '2nd / BedRoom / KeyPad / BedRoom A' On 15 / Off 0 (Backlight Level) Else Set '2nd / BedRoom / KeyPad / BedRoom A' On 15 / Off 7 (Backlight Level) Any Idea if this program is what killed my Keypad?..

Thanks for the update Michel

I just received my filters, work perfectly!! thanks again!!

So the question now is: what rank does this have on ISY Programmers TODO's List ?

Good to keep in mind, in that case KeyPad Led need to be out of that Scene and only controlled via Program reflecting the device they control. This is interesting, It give pretty much the same idea, and having a ALL_HOUSE_INTERIOR scene still keep it to 1 signal, not a big lag like if you turn all device off individually with the program itself.. Beside the Ease of Setup/Manipulation, Is there any other Advantage of having two Scene for 'limited' and 'all' instead of having 1 scene with some OnStatus set to 0%? I guess you can Re-use the ALL_HOUSE_INTERIOR scene ON for other Scenario ?

Now Always thinking of Improving this "All Light Scene", The Off State of the KeyPadLinc Button not doing anything is a Waste.. What if, Once all Lights are Off, it could serve something usefull? You are more than welcome to join me in this little BrainStorm here I don't like to have a Dark House and I like to have a few light All over the house so I don't feel like the house is empty when I walk around. What if that Button could be used to Light the 'main' lights of the house when it's switched on? Maybe not EVERY light, but one light in each main area to have enough light to go around the house? the "On" state of the Scene could be set to turn 'ON' the main light here in there in the main area of the house, keeping all the other ones OFF by setting the OnLevel to 0%. By Turning the KeyPadLinc Button back to Normal On/Off mode instead of ToggleOFF mode, we eliminate the '3 second flashing period' that was an inconvenient, and we can use it when every light is closed, to open just a few of them by switching it on, witch would call the scene On.. That ON Mode of the scene could also be customized to be different depending on witch KeyPadLinc is switched on (Because Scene Parameters are defined BY controler). The Set State On would only be Invoke when every light is off because our program refresh the LED State at each change. Maybe we could also use a Program to change witch light are turned on and their OnLevel% depending of the Time of the Night? What do you Think? Any Other Ideas?

Scene is a best way then program in my opinion for more discussion about that topic: http://forum.universal-devices.com/viewtopic.php?t=6293 in your case maybe you need to add a few rf access point

It could be stored via a variable, but at least just a way to trigger a program would be great, we can manage variable our self after that. to put a link to every controller and every program is a pain and don't cover every situation: example: Controlling the Scene directly with a Iphone via EK ISY

That one go back to having the ability to trigger a program based on a Scene..

LOL.. Until the last line I thought such Dummy Device existed.. Damn! lol But it's a good Idea I have a few spear LampLinc I could use for that, even better than taking two spot on a KeyPad Thanks

Thanks alot for that quick walk trough, it's exactly what I was looking for, I'll try this at home tonight

You can try it by yourself very easily by adding a new device in the 'LEDProgram' without adding it to the 'TurnOffScene'.. The keypad won't be able to turn the device off (because it's not in the scene) but it's in the program to make the LED ON, it should logically end up with the LED ON, but the KeyPad turn it OFF anyway.. If you look attentively, you see that the Program try to turn the LED ON during the flashing, the flash won't be consistent at one point.. it will flash back ON quicker than usual at one iteration.. Anyway that's what it does on mine I would be curious to compare that with other KeyPad, but I think I have one of the newest version..

I have a IRLinc that use to work correctly.. and now for any reason it's just don't react when I try to start the scenes.. I see there is many Log and Diagnostics features in the menu but what is exactly the steps to debug a device? what step should be done? is there a way to backup a device and recover it after a reset or a replacement? sorry for those newbies questions.. my Insteon System was pretty reliable and I never had big issues like this.. Thanks

the two program design only repeat it when you control directly the keypad button.. not when other device are switched on and off.. the one program design always repeat it whenever it's the local keypad that call the changes or any of the individual devices..

Absolutely.. or even if it dosn't 'remember' what is the Current one, just the ability to trigger a program when a SET event happen for a Scene.. I am controllling a IRLinc 2411T, witch "I Think" don't have a 'STATUS' like a LampLinc would have that I could work against, so I can't use the 'responder' to found when my status changed. And I call it sometime with a Program, but frequently with my IPhone via eK ISY witch "I Think" I can't program aganst either.. My main question was to know if it would be technically possible to implement that feature in the ISY.. and if it was in the plans of doing so.. And if I could find an elegant solution.. You made me think about using a Button on a KeyPad to act as a Responder (or even controller) of my IR_SEND_ON_SIGNAL Scene, that button would go ON whenever that Scene is Called, and keep the value to remember that my ir_controlled_device is ON. Now can I set a KeyPad Button LED to Turn 'OFF' when the IR_SEND_OFF_SIGNAL scene is set to ON? or I need to use a second KeyPad Button, one for when it's OFF and one for when it's ON, and Sync them via Programs? Yes I know there is a way to teach the 2411T to React to a OFF Scene, but I didn't understood how.. that device is a little obscure.. I understand I'm trying to do something un-usual here.. I leanred that with Insteon and ISY you often need to think outside the box, and I'm sure many peoples here can have wonderfull ideas to achieve what I try to do

Ohh!... I like this Last Code Example, it prevent the need of a second program without introducing any bad effect. Now would this introduce more traffic on the network? Because most of the time the LED is not set by the keypad itself but by other device been turned ON and OFF all day long.. if the Scene for the LED is called two time each time, would it double the traffic.. could that have some repercussion on a big network?

I tought I saw in an other thread that a Scene could only set device ON or OFF.. that you could not set some device ON and some device OFF.. that you could set a %level, and a OnRamp, but to CLOSE a light on a Scene ON you would need to set it brightness level to 2%.. Maybe this had change with newer device.. But when I call a Scene, or I send it a ON or I send it a OFF.. in a program I set a Scene to ON or set a Scene to OFF, this is the ON/OFF Status I would like to trigger on.. and I think most peoples would agree on this one. You turn a Scene ON, so the Scene Status would be ON.. Then Set Scene 'NameOfTheScene' On Else Set Scene 'NameOfTheScene' Off In your example you stated: So there you go.. it's ON Nothing to do with the actual 'result' of the Scene. I would like to run a program to set a variable, to remember the Status of a Scene because Insteon don't keep track of the last Status of a Scene, just like you suggest, but I would like to be able to Trigger the program when the scene as been set. a Program that could be evaluated when a Scene is set to ON, even then, my 2411T Ir only receive Scene ON signal to send the IR Signal, so I don't really care if the Scene was set ON or OFF.. I just care that the Scene was 'used'. Other case you need to Call that program each time an other Program or Device Set that Scene, witch can become a nightmare to manage and keep track, specially that I like to use "eK ISY" my Iphone to switch Scene On and Off... witch I don't think could be monitored by a program either. So I guess a Program would need to become a 'responder' for the scene to receive the signal, but I thought that the PCM was already acting as a middleman for every scene created with the ISY.. But maybe it could be a band-aid solution to add a un-used Un-used KeyPad Button LED to act as a responder of that scene and then evalute it status with a single program.

Thanks for the input, this approach is interesting.. Actually that second Program purpose is not to Switch the button LED OFF, but to re-switch it back ON if needed. In the Ideal scenario, all light turn off, the keypad blink the button for 3 seconds and turn it off, everything is all right.. This ASSUME everything went as expected. But If for any reason the Program Group.AllOffSaufChambre.LEDisOn try to put the KeyPad LED back ON, good chance are it will do so during the 3 second period that the keypad flash the button LED and will be overrided by the KeyPad display routine of "flashing 3 second" and "turn off", even if the program told it to go back ON, it will be OFF. One of the main purpose of that LED is to CONFIRM you that all the lights are closed successfully.. (or at least that the way I see it) It's all about a 3 second period where if the KeyPad LED is set it won't keep the value because it's flashing and will bet set to 'OFF' after flashing even if it received a 'GO BACK ON' during that period... Not having the KeyPad Button on 'TOGGLE OFF' mode would probably avoid all this, or if it didn't had that little 'flashing display thing' either.. Here is a few scenario where this could happen: - If a Device is NOT in the [Group.AllOffSaufChambre] Scene but is in the [Group.AllOffSaufChambre.LEDisOn] Program - If Someone Turn on a light during that 3 seconds Period - If a Program turn back on a Device for a Reason during that 3 seconds Period. - If a Device don't turn OFF successfully for unknown reason. In any of theses cases, the LED of the Keypad would remain off even if all the light are not off, and it will remain that way until at least one device status change and get the program [Group.AllOffSaufChambre.LEDisOn] to be evaluated again to refresh the keypad LED display.. Good chance are when you go to BED or LEAVE your house, it will take a while before a device change and you won't know that a device is still ON. So we could avoid having two program by putting this delay of 4 second before the SET LED SCENE ON instead of the SET LED SCENE OFF, but this will introduce a 4 second delay each time a device is set to on, and could create a scenario where you set a device on, and off right after so with the 4sec delay it actually send the SET LED SCENE OFF before the SET LED SCENE ON, introducing again a glight of accuracy.. you would need a 4 second delay on both action, witch introduce unnecessary delay in LED Response. I personnaly prefer having a second program just to 'refresh' it value where it could be problematic then introducing a unneeded delay, but some could prefer to have less program to manage and do it this way. Then Wait 4 seconds Set Scene 'Group / AllExceptChambre / Group.AllOffSaufChambre.LED' On Else Wait 4 seconds Set Scene 'Group / AllExceptChambre / Group.AllOffSaufChambre.LED' Off

I am currently looking at the best way of having a 'all light off' button on a keypad with the button led indicating if any of the light are open.. For example in my beadroom I have a Keypad with a Button, I want the LED Turn On if any light is ON in my house (except my bedroom, and outside lights) and when I press on that button it turn All those light Off if they aren't.. I Created a Scene [Group.AllOffSaufChambre] (witch mean AllOffExceptBedRoom) and I have put all the light in my house in that group as Responder (except my bedroom light and outside light), then I have added my KeyPad Button as a Controller.. you can have more than one controller here, for example, one in the BedRoom and one in the 2nd level Passage. I first tried to do this via a Program, the advantage of program was the ability to group and re-use (Group.1stlvl, Group.2ndlevel, Group.Kitchen, Group.Sched, Group.Basement, etc) so that way you can group some program if you have some button that turn off everything and other that just turn on specific level, and you don't need to rewrite them all. Another advantage of doing it with a Program was to Control different Device on the ON and OFF event, for example you press the button to turn OFF everything, but you can click the button again to turn ON just a few main light in the house. This can't be done using scenes because from what I Understood, a keypad button cannot be controller of more than one scene, and a Scene can't send the OFF command to different list of device than the ON command. That solution worked but I had the feeling it was sending one request by device to turn everything off, so it was taking many second to accomplish and sometime some device didn't turn off properly.. To do this via a Scene instead made it quicker, more reliable and smoother. Then you can go in your KeyPad setting and set the controller button 'Toggle Off' to always send 'Off' button.. this will prevent a miss-click that would light everything ON in the middle of the night.. Then we want to get that LED ON to indicate if any of those devices are ON.. For this we are going to use a Program, but first we will need a second Scene: The Scene [Group.AllOffSaufChambre.LED] with every of your keypad button as responder (the Keypad button you want the LED to light up when any of the devices are turned on, big chance it's the same devicebutton that was 'controller' in the [Group.HouseAllOffSaufChambre] scene ), This will allow us to control the LED of the KeyPad Button from our Program. Here is a PrintScreen of what the Scenes look likes: The first Program check the status of every device, and call the LEDstatusScene accordingly, sorry for the French Naming.. Group.AllOffSaufChambre.LEDisOn: If Status '2e / Haut / Haut' is On Or Status '2e / SaleDeBainHaut / SaleDeBainHaut' is On Or Status '2e / SaleDeJeu / SaledeJeu' is On Or Status '1e / Corridor / KeyPad / Cuisine Corridor' is On Or Status '1e / Cuisine / Cuisine' is On Or Status '1e / Cuisine / Cuisine Armoir' is On Or Status '1e / Cuisine / KeyPad / Cuisine A' is On Or Status '1e / Cuisine / Cuisine Hotte Lumiere' is On Or Status '1e / Cuisine / UnderCounterL' is On Or Status '1e / SaleDeBainBas / SaleDeBainBas' is On Or Status '1e / Salon / Salon' is On Or Status '1e / Entree / KeyPad / Entree A' is On Or Status 'Ext / Sched / Sched Main' is On Or Status 'Ext / Sched / Sched Petite' is On Then Set Scene 'Group / AllExceptChambre / Group.AllOffSaufChambre.LED' On Else Set Scene 'Group / AllExceptChambre / Group.AllOffSaufChambre.LED' Off This program will update the LED of our KeyPad Button each time a device is turned on or off.. Because a KeyPad button in ToggleOff Mode will blink a few time when you press it, the action of this program won't always update sucessfully the LED of your button when you Press on them.. we will create a second program to take care of this: Group.AllOffSaufChambre.LEDisOn.Update: If Control '2e / Chambre / KeyPad / Chambre G' is switched Off Or Control '2e / Haut / KeyPad / Haut H' is switched Off Then Wait 4 seconds Run Program 'Group.AllOffSaufChambre.LEDisOn' (If) Else - No Actions - (To add one, press 'Action') This Program will wait the 'Flashing preriod' of the KeyPad button and then refresh it value. This is based on my different Try in the past few weeks.. I am really aiming at improoving this the most possible, for a convenient, smooth and reliable solution. Maybe I am still very far from the ultimate solution.. but this is where I am at right now.. Please feel free to add any Suggestion and/or Comments Thanks

I saw an old thread tellign that ISY don't support to trigger a program on Scenes on/off.. Was this added since? (in the new v3 for example) or is this something that could be added eventually? or is this technically impossible? What I am trying to do is to keep the state of a IR device.. I have the InsteonToIr 2411T controlling a device by IR, the 2411T only sent IR via Scenes.. So I would like to trigger a program or a variable to remember if my device is on or off, by setting it to true when running scene 'IRsendON' and setting it to false when running scene 'IRsendOFF'.. Anyone got any suggestion how I could do this with the current ISY? Thanks

That was Quick! Once again It's a pleasure to participate in this great product

Hi Michel, don't worry.. I'm a programmer myself.. I know those kind of bug are normal, there is no way to do a perfectly bug-free program.. the ISY is honestly very nice and I'm personally very impress by it quality.. this bug wasn't that bad, i'v been able to solve it in a short time.. I am very happy If I was able to help you improove this very nice product Thanks again for your great work and support

it all look like I accidently dragged a Parent folder to it's child folder.. and it actually did it without preventing me to do that stupid thing.. I can't beleive I'm the first one who screw it up that way