When installed between the actual keypad driver and Lights/Advanced Lighting Scenes(ALS), this driver allows you to set the LED colors on the keypad, to blink LEDs using programming commands and to disable the keypad altogether (for parties, etc.). You may even re-enable the keypad locally with a "secret" button sequence.
If Up and Down keys are used on the keypad, the driver is able to simulate an 8th key, achieved when both Up and Down are pressed simultaneously. Only Single Tap is available for simultaneous press.
The driver provides three sets of output connections (passthrough) which enable control of three sets of Lights/ALS, including full dimming capability. Simply use Single, Double and Triple taps on a keypad button.
An additional method is provided: 'Press and Hold', including 'Single Press and Hold', 'Double Press and Hold' and 'Triple Press and Hold'.
The driver also offers a new mode to select which action will occur when Up and/or Down keys are pressed: Selector Mode. Up to 5 of the top keys may become Selector keys which determine how the Up/Down keys will behave (via new Connections). A use case for this would be to have up to 5 top keys to select one of five blinds to operate (for example) and have the Up/Down keys operate the selected blind and being able to stop blind movement when both Up and Down are pressed simultaneously.
**NEW** The driver has a new set of Contact Sensor inputs which may be used instead of a real keypad button. When such a sensor is connected, properties allow the installer to select the contact type (NC or NO) as well as its effect (always Single Tap or Fully mirroring a real keypad button).. Debouncing is also available if desired. A connection to a real keypad button overrides a connection to a Contact sensor for a specific input.
If none of the outputs for a given keypad button are connected, the driver will force that keypad button’s LED to Off state and the color associated with that state for the button. This may also be achieved via Programming.
A large number of events are provided as well as variables containing the status of up to 6 keypad LEDs.
Since many instances of this driver may be installed in a project (typically one per keypad), the driver provides Actions to broadcast selected colors to other instances as well as stopping blinking across all instances. This can simplify installation and programming.
No posts found
INSTRUCTIONS
- Use the free trial period or activate the driver at any time by assigning to this project the license you purchased from the driverCentral website (requires the driverCentral cloud driver). You may use multiple copies of this driver in your project.
- Connect up to seven Control Output BUTTON_LINK connections to the real physical keypad's connections. Note that if your physical keypad is configured with double or triple buttons, there is no need to connect the unused bindings. The same is true when your keypad has a full length 6th button (not up/down arrows) – IN THIS CASE, DO NOT CONNECT THE DOWN BUTTON. If you are using an older 3-button keypad, simply connect the first three bindings. Instead of connecting to a real physical keypad button, any input may be connected to a Contact Sensor to simulate a physical keypad button. In this case, review the properties and set accordingly.
- Connect Control Input BUTTON_LINK connections to Lights and/or Advanced Lighting Scenes as appropriate. Connecting to their Toggle connection is usually best.
- **NEW** If you are not planning to use the virtual 8th button (simultaneous pressing of Up and Down), set the property ‘Virtual 8th Button Used) to ‘No’. This will enable all events related to the Up and Down buttons. If the virtual 8th button is used (this property set to ‘Yes’), some events are not functional for Up and Down, such as all Holds and Release.
- If you are NOT planning to use double or triple presses with any button of THIS keypad, then set ‘MultiPress Used’ to 'Single press only'. This will allow for a more responsive control when pressing a key. Otherwise, the driver will wait for the MultiPress interval in case you might double tap or triple tap. Connecting something to one of the driver's Double Tap or Triple Tap bindings will force this Property to the right value. Even if MultiPress is used, it is possible to exclude the Up/Down buttons from its processing for more responsive feedback from these buttons (the virtual 8th button remains available).
- If required, use the Action 'Set Button Timings' to change the default MultiPress interval (defaults to 1500 msecs) and/or the default Hold interval (defaults to 1000 msecs). Generally, the defaults will be adequate.
- Optionally specify up to 5 button numbers (1 to 5) which will act as selector buttons for the Up/Down buttons (Example: 1,2,3). You may use ‘All’ (which is equivalent to 1,2,3,4,5 or 1-5) or ‘None’ which disables this capability. Buttons designated as selector buttons may also be used for normal duties but their LED will only indicate their selected status.
- **NEW** Optionally specify a 1- or 2-button sequence which may be used locally to enable a disabled keypad. You may leave empty or use ‘None’ if this feature is not desired. If one button number (1 to 7 with 7 being the ‘Down’ button) is specified, then the keypad is enabled when this button is pressed. If two buttons are specified (separated by a comma), then these buttons must be pressed in the same sequence on the keypad and within a 2-second interval for the keypad to be enabled.
- Specify the Off and On colors for each LED of the keypad. This is a pair of letters for each LED. The letters refer to the color selectors below (A to J) and may also include 'K' for Black and 'N' for the connected Light/ALS's native Off and/or On Colors.
- The defaults are: AB,AB,AB,AB,AB,AB - this means the Off color for each key is Color A and the On color is Color B.
- Example: AB,GH,KC,KD,KN,NN - key 1 has colors AB, key 2 uses GH, key 3 uses color C for On and Black for Off, key 4 uses Color D for On and Black for Off, key 5 uses the Light's native On color with Black for Off and key 6 uses the Light's native colors for both Off and On.
- **NEW** If you wish the driver to turn Off the LED of any connected real keypad button which is unused (none of its outputs are connected), specify K (Black) as the Off color. If necessary, Force the state to Off using Actions. Another ‘Off’ color may also be used, if desired.
- Specify the color to be used when the keypad is disabled.
- You may assign this keypad to one of 10 groups, arbitrarily. This is used when you broadcast colors or enable/disable keypad in other (“peer”) instances of this driver. This allows you to limit which keypad will respond to the broadcasted commands.
- Once you have entered Colors A to J for one driver, you may use the Action 'Broadcast Colors to Other Instances' to simplify your installation tasks.
----------------------------------
PROGRAMMING
- A programming command allows you to change the Off and On colors associated with each keypad LED. This overrides what you have specified in the 'Button 1-6 Off/On Colors' Property.
- Some output drivers/devices do not return their state so the driver can properly set the LED state of connected real keypad buttons. A programming command allows you for force the state of the keypad LED to one of the two specified colors (Off or On). An Action is also available to do this.
- A programming command allows you blink a keypad LED. Normal blinking (once every second) and slow blinking (once every two seconds) are available. Blinking for a button stays on until stopped via programming from this or another instance of the driver.
- Programming commands allow you to disable/enable this keypad and/or, optionally, keypads connected to other instances of this driver in your project. It is important to note that the driver will disable only the real keypad buttons it is connected to.
- The UP_DOWN_SELECTOR variable contains the current selector for Up/Down buttons (1 to 5) or 0 when not selected.
- A comprehensive set of events are available. Experiment to see which ones match your requirements. The event ‘1P-Hold in Progress’ is triggered as soon as the driver detects a hold (the button has been pressed beyond the hold delay) and the event ‘Press and Hold’ is triggered when the button is actually released. This is also valid for ‘2P-Hold In Progress’ vs. ‘Double Press and Hold’ as well as for ‘3P-Hold in Progress’ vs. ‘Triple Press and Hold’.
10.0.0 January 6, 2018 - Initial Release
10.1.0 January 22, 2018 - Added Keypad Disable (Lock-out), 2 more Colors, Keypad Groups, enhanced Actions and Commands
11.0.0 February 8, 2018 - Added 8th button (Up/Down simultaneously) and Selector capability for Up and Down buttons
11.1.0 October 14, 2018 - Option to exclude Up/Down buttons from multipress (quicker response) and new 'Hold in Progress' events; issues fixed
11.2.0 November 5, 2018 - Added new command to force button LED state
12.0.0 January 3, 2019 - Added Contact Sensor inputs, ability to specify blink color, improved resilience to Cloud Driver updates
12.1.0 March 18, 2019 - All taps available for selector buttons and new property to disable Virtual (8th) button
12.2.0 April 2, 2019 - Added property to specify keypad enabling button sequence
12.3.0 May 3, 2019 - Infrastructure update
