This driver offers a very different approach to Experience Buttons. There are four versions of the driver: single button, 6 buttons, 12 buttons and 24 buttons for maximum flexibility. One possible use is with PDUs (Power Distribution Units) where the buttons would show at a glance the status of each outlet. The driver may also be used to provide feedback from security zones or show the state of relays.
Experience Buttons may now be single-, double- or triple-tapped giving the user even more flexibility. Colors (states) are very customizable and the driver offers a comprehensive set of events for programming.It is also possible to generate CONTACT_SENSOR and/or RELAY bindings for connection to control bindings which would provide status to set colors. These are for INPUT only and cannot be used to control devices. Use programming on events to do this from Experience Buttons.
No posts found
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.
If you wish to have the Experience Button immediately switch to a given state when Selected, specify ‘Set State when Selected’.
If you are NOT planning to use double or triple presses with any button of THIS driver, then speficy ‘Set State when Double Tapped’ to 'Double Tap Not Supported'. 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 – see below).
If planning to use double presses but NOT planning to use triple presses with any button of THIS driver, then set ‘Set State when Triple Tapped’ to 'Triple Tap Not Supported' (property only visible when appropriate). This will allow for a more responsive control after the second press. Otherwise, the driver will wait for the MultiPress interval in case you might triple tap.
If required, use the Action 'Set Button Timings' to change the default MultiPress interval (defaults to 1500 msecs). Generally, the default will be adequate.
Use the ‘Set Button State’ Action as appropriate to force buttons to specific states. It is also possible to force buttons in ALL other instances of this driver in your project from a single Action. This could simplify installation in some cases.
Use Composer to make any or all of this driver’s Experience Buttons visible in any room of your project. When finished, Refresh Navigators.
Each Experience Button has a ‘Selected’ event. This event is triggered each time the button is pressed by the user. Hence, in the Triple Tap available with this driver, the event will be triggered three times, which could be problematic. Instead, use the new events based on ‘Single Tap’, ‘Double Tap’ and ‘Triple Tap’.