Binary Sensor Component

With esphomelib you can use different types of binary sensors. They will automatically appear in the Home Assistant front-end and have several configuration options.

Base Binary Sensor Configuration

All binary sensors have a platform and an optional device class. By default, the binary will chose the appropriate device class itself, but you can always override it.

binary_sensor:
  - platform: ...
    device_class: motion

Configuration variables:

Automations:

  • on_press (Optional, Automation): An automation to perform when the button is pressed. See on_press.
  • on_release (Optional, Automation): An automation to perform when the button is released. See on_release.
  • on_click (Optional, Automation): An automation to perform when the button is held down for a specified period of time. See on_click.
  • on_double_click (Optional, Automation): An automation to perform when the button is pressed twice for specified periods of time. See on_double_click.
  • on_multi_click (Optional, Automation): An automation to perform when the button is pressed in a specific sequence. See on_multi_click.
  • All other options from MQTT Component.

Binary Sensor Filters

With binary sensor filters you can customize how esphomelib handles your binary sensor values even more. They are similar to Sensor Filters.

binary_sensor:
  - platform: ...
    # ...
    filters:
      - invert:
      - delayed_on: 100ms
      - delayed_off: 100ms
      - lambda: >-
          if (id(other_binary_sensor).state) {
            return x;
          } else {
            return {};
          }
      - heartbeat: 5s

Supported filters:

  • invert: Simple filter that just inverts every value from the binary sensor.
  • delayed_on: When a signal ON is received, wait for the specified time period until publishing an ON state. If an OFF value is received while waiting, the ON action is discarded. Or in other words: Only send an ON value if the binary sensor has stayed ON for at least the specified time period. Useful for debouncing push buttons.
  • delayed_off: When a signal OFF is received, wait for the specified time period until publishing an OFF state. If an ON value is received while waiting, the OFF action is discarded. Or in other words: Only send an OFF value if the binary sensor has stayed OFF for at least the specified time period. Useful for debouncing push buttons.
  • lambda: Specify any lambda for more complex filters. The input value from the binary sensor is x and you can return true for ON, false for OFF, and {} to stop the filter chain.
  • heartbeat: Periodically send out the last received value from the binary sensor with the given interval. All state changes are still immediately published.

Binary Sensor Automation

The triggers for binary sensors in esphomeyaml use the lingo from computer mouses. This naming might not perfectly fit every use case, but at least makes the naming consistent. For example, a press is triggered in the first moment when the button on your mouse is pushed down.

You can access the current state of the binary sensor in lambdas using id(binary_sensor_id).state.

on_press

This automation will be triggered when the button is first pressed down, or in other words on the leading edge of the signal.

binary_sensor:
  - platform: gpio
    # ...
    on_press:
      then:
        - switch.turn_on: relay_1

Configuration variables: See Automation.

on_release

This automation will be triggered when a button press ends, or in other words on the falling edge of the signal.

binary_sensor:
  - platform: gpio
    # ...
    on_release:
      then:
        - switch.turn_off: relay_1

Configuration variables: See Automation.

on_click

This automation will be triggered when a button is pressed down for a time period of length min_length to max_length. Any click longer or shorter than this will not trigger the automation. The automation is therefore also triggered on the falling edge of the signal.

binary_sensor:
  - platform: gpio
    # ...
    on_click:
      min_length: 50ms
      max_length: 350ms
      then:
        - switch.turn_off: relay_1

Configuration variables:

  • min_length (Optional, Time): The minimum duration the click should last. Defaults to 50ms.
  • max_length (Optional, Time): The maximum duration the click should last. Defaults to 350ms.
  • See Automation.

on_double_click

This automation will be triggered when a button is pressed down twice, with the first click lasting between min_length and max_length. When a second leading edge then happens within min_length and max_length, the automation is triggered.

binary_sensor:
  - platform: gpio
    # ...
    on_double_click:
      min_length: 50ms
      max_length: 350ms
      then:
        - switch.turn_off: relay_1

Configuration variables:

  • min_length (Optional, Time): The minimum duration the click should last. Defaults to 50ms.
  • max_length (Optional, Time): The maximum duration the click should last. Defaults to 350ms.
  • See Automation.

on_multi_click

This automation will be triggered when a button is pressed in a user-specified sequence.

binary_sensor:
  - platform: gpio
    # ...
    on_multi_click:
    - timing:
        - ON for at most 1s
        - OFF for at most 1s
        - ON for 0.5s to 1s
        - OFF for at least 0.2s
      then:
        - logger.log: "Double-Clicked"

Configuration variables:

  • timing (Required): The timing of the multi click. This uses a language-based grammar using these styles:
    • <ON/OFF> for <TIME> to <TIME>
    • <ON/OFF> for at least <TIME>
    • <ON/OFF> for at most <TIME>
  • invalid_cooldown (Optional, Time): If a multi click is started, but the timing set in timing does not match, a “cool down” period will be activated during which no timing will be matched. Defaults to 1s.
  • See Automation.

Note

Getting the timing right for your use-case can sometimes be a bit difficult. If you set the global log level to VERBOSE, the multi click trigger shows logs about what stopped the trigger from happening.

You can use an OFF timing at the end of the timing sequence to differentiate between different kinds of presses. For example the configuration below will differentiate between double, long and short presses.

on_multi_click:
- timing:
    - ON for at most 1s
    - OFF for at most 1s
    - ON for at most 1s
    - OFF for at least 0.2s
  then:
    - logger.log: "Double Clicked"
- timing:
    - OFF for 1s to 2s
    - ON for 1s to 2s
    - OFF for at least 0.5s
  then:
    - logger.log: "Single Long Clicked"
- timing:
    - ON for at most 1s
    - OFF for at least 0.5s
  then:
    - logger.log: "Single Short Clicked"

lambda calls

From lambdas, you can call several methods on all binary sensors to do some advanced stuff (see the full API Reference for more info).

  • publish_state(): Manually cause the binary sensor to publish and store a state from anywhere in the program.

    // Within lambda, publish an OFF state.
    id(my_binary_sensor).publish_state(false);
    
    // Within lambda, publish an ON state.
    id(my_binary_sensor).publish_state(true);
    
  • .state: Retrieve the current state of the binary sensor.

    // Within lambda, get the binary sensor state and conditionally do something
    if (id(my_binary_sensor).state) {
      // Binary sensor is ON, do something here
    } else {
      // Binary sensor is OFF, do something else here
    }