Jump to content

Reverse on/off light in keypad buttons?


timekiller

Recommended Posts

I have a 6 button keypad (this one: http://www.smarthome.com/insteon-2334-232-keypad-dimmer-switch-dual-band-6-button-white.html)that I'm using (among other things) to control my 2 garage doors via an Insteon  74551 ( this guy: http://www.smarthome.com/insteon-74551-garage-door-control-status-kit.html)

 

I set it up following this tutorial: http://homeautomationguru.com/insteon-enabled-your-garage-doors/and everything works perfectly! I can push "A" and garage door 1 opens. Push it again and it closes, and the indicator light on the buttom lights up depending on whether the door is closed. Works the same with "B" and garage door 2.

 

The problem is, and I know this is knit-picky, when the garage doors are closed, the button light is lit. I would much rather have the buttons lit when the doors are  open. Is this possible?

Link to comment

Was hoping I could solve this in software. I know switching from a NO to a NC switch would reverse when it's lit, there's no way to tell the keypad to only light the button when the device is off? Or to tell the garage sensor that when the circuit closes, that's "off"?

Link to comment

Was hoping I could solve this in software. I know switching from a NO to a NC switch would reverse when it's lit, there's no way to tell the keypad to only light the button when the device is off? Or to tell the garage sensor that when the circuit closes, that's "off"?

 

It would be worth trying trigger reverse in the iolinc settings.

 

I do this with mine for the same reason, to have a key on a keypad in the house light up when the door is up.

 

Paul

Link to comment

Can this not all be done with logic? Do not assign the button directly but have it toggle on and off with programming in between doing the reversing.

 

To oberkc's point, its a matter of preferences and tradeoffs. As much as possible/practical, I assign switching and button updates, etc, to the Insteon network via scenes as opposed to writing additional programs to control the same thing. I have the ISY follow up or take secondary actions via programs, but primary switching is handled device-device with no middle man (PLM/ISY)

 

My primary reason for using scenes over programs for lighting and garage door control is that I travel. I don't want a down house for a week when the PLM connected to the ISY eventually dies and I am 1000 miles away.  The secondary reason is that using programs for lighting control adds additional time between button press and lights going on/off.

 

Paul

Link to comment

As others mentioned there are several software options to complete the same. But, honestly using the switch I listed will offer you bullet proof response and operations.

 

If and when the 3:00 AM Query completes you better get ready for more trouble shooting and hair loss. For me $17.XX is money well spent knowing its just going to work, forever . . . 

Link to comment

I would just switch the scene command in the program lines to reverse the LED indication.

 

Contacts do NOT need to be changed or switched from NO/NC. A better contact is not going to change the look of your LED.

This is what having  a PLC HA  = ISY is all about... not having to change hardware.

 

Coincidentally I just did this for my garage door last night. It took about 15 seconds after seeing the LED results and I decided the same thing. I want the LED to look like an unusual/alarm  situation when it is On.

 

Paul has a point about scenes vs. programs and that takes a certain type of contact but if your LED doesn't work while you are away will you notice?

 

Don't use the "reverse" option in the ISY option box. It will cause you troubles, as mentioned above by others.

 

 

To do this you need to remove the LEDs from the I/OLink scenes and create a new and separate scene for each LED. Then you need to write a program for each LED to operate that scene.

 

If

    Garage door is open

Then

    set LED scene On

Else

    set LED scene Off

Link to comment

Remove the LED from all other scenes and create a new scene for each LED.

 

Drop the KPL LED into the scene and adjust to 'ON. (Scene On = LED On)

 

This program is about as simple as ISY gets. This gives  a 1 second delay to avoid Insteon traffic collisions but on an LED indication response it shouldn't matter.

 

This does not change any other ISY logic that controls the door, just the LED indication

Note: My contact is closed when the door is closed. Either contact can work with the 'reverse' option.

 

Garage Door Open.LED - [iD 0097][Parent 0109]

If
        'Garage / Garage Door.closed' Status is Off    <----I changed from 'On' to get

                                                                                       status Off =  door open  = LED On
 
Then
        Wait  1 second
        Set Scene 'Mudroom / MudRm kpl.LED.a' On
 
Else
        Wait  1 second
        Set Scene 'Mudroom / MudRm kpl.LED.a' Off
 

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...