Button Controller

From Hubitat Documentation
Jump to: navigation, search
Go to the top of the page

Wireless buttons are a great way to quickly change modes, control lighting, override automations and even protect loved ones when you are not able. With Button Controller 3.1, an unlimited number of buttons can be configured to control devices, or attributes of other apps and drivers, providing the quickest and easiest way to program your buttons.

Installing the Button Controllers app

  1. From the sidebar of your hub, select Apps and press the Add Built-In App button.
    Install Built-In App 2.0.png
  2. Choose Button Controllers from the list of Hubitat Elevation built-In apps.
    Install Button Controllers 2.0.png
  3. If you haven't already, add your button device using the process found in Discovering your Devices. In the case of Lutron Pico buttons, you will use the Lutron mobile app to add them to the Lutron Smart Bridge Pro or Lutron RA2 Select Main Repeater, in combination with the Lutron Integrator app to add them to your Hubitat Elevation hub.

Configuring your buttons

  1. Open the Button Controllers app on your hub.
  2. Select Create New Button Controller 3.1
    Create new Button Controller 3.1.png
  3. Name the Button Controller 3.1 child app and select your button device.
    Prefill Button Controller 3.1 actions.png
  4. You may now choose to allow Button Controller 3.1 to automatically pre-fill selected actions for all available device buttons, or you can choose to manually add button actions for specific buttons.
    Prefill or manual add BC 3.1 actions.png
  5. Button Controller 3.1 allows maximum flexibility when adding and removing button actions. If you choose to pre-fill button actions, you will still be able to delete button actions you don't want afterward, or add additional button actions as needed. You may keep the list of button actions sorted numerically by selecting the option Keep button list sorted.
    Add - delete and sort BC 3.1 actions.png
  6. For each button action defined, select the action type you want to perform. There are a wide range of action types that can be defined and each action type will have specific options available relating to the action type.
    BC 3.1 select action type.png
    BC 3.1 define action type.png
    BC 3.1 define action type optons.png
  7. Depending on the button action type and its options, you will have specific types of devices or attributes that can be controlled.
    Define BC 3.1 action type device or attribute.png
  8. You may add additional action types for the same button actions. This can be helpful to control multiple device types with a single button press.
    BC 3.1 define released action.png
  9. It's also possible to add actions so they occur in a specific order, even if there are already existing actions defined. To do this, use the Insert Action Before drop-down menu.
    BC 3.1 insert action before.png

Configuring held and released actions

While not supported by all button devices, some do support both held and released actions. These can be used with dimmers and bulbs that support smooth dimming. It's particularly helpful when you are able to hold a button to increase, or decrease light levels, and stop the change when the button is released. The Hubitat Hue Integration is one such application where this can be used if your button device also supports held and released actions.

  1. When connected to Hubitat Elevation via the Lutron Integration, the Lutron Pico remotes are one type of button device that supports both held and released button actions. Using a Lutron Pico as the example device, define the action that should occur when the increase button is held. For a Lutron Pico remote, this will be button 2, and the action type option will be Start raising dimmers.
    BC 3.1 define held action.png
  2. If you define that a dimmer should start raising when a button is held, then you must also define what happens when the button is released. If you do not do this, the light will continue to increase until it reaches maximum brightness, even though you have released the button.
    BC 3.1 define release actions.png
  3. Define the button action for decreasing the dimmer using the same method above, but instead use the button action type option, Start lowering dimmers. For the Lutron Pico remote used in our example, this will be button 4.
    BC 3.1 define released action for lowering.png
  4. If you define that a dimmer should start lowering when a button is held, then you must also define what happens when that same button is released. If you do not do this, the light will continue to decrease until is reaches minimum brightness, even though you have released the button.
    BC 3.1 define released lowering action.png