BP - Lutron Caseta Pico Paddle Remote

I recently got some new Lutron Caseta Pico Switches, but was disappointed to have a hard time finding a blueprint for automation them. I saw so many awesome 2, 4, and 5 button Pico blueprints, but none for the new Paddles.

I played around with it for wayyy to long for me to feel like I was a wiz at this, but I think I figure it out. HUGE shoutout to stephack who’s blueprint I used as a base template for tinkering with the Paddles.

I got the basics working for the remotes, but please give me feedback as to how it can be improved upon if anybody has any neat additional ideas.

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

blueprint:
  name: BP - Pico Paddle Remote
  description: "This is for the paddle remote Picos that have the following model:\n\n
    PJ2-1P-GXX (PaddleSwitchPico)\n\nSelect an action for each button listed
    below. "
  domain: automation
  input:
    pico_remote:
      name: Pico Remote
      description: 'Select the pico remote to configure:'
      selector:
        device:
          model: PJ2-1P-GXX (PaddleSwitchPico)
          multiple: false
    auto_mode:
      name: Automation Mode
      description: Mode that automation runs in (single,  restart, queued, parallel).
      default: restart
      selector:
        select:
          options:
          - single
          - restart
          - queued
          - parallel
          custom_value: false
          multiple: false
          sort: false
    mode_max:
      name: Mode Max (ignored by Single and Restart Modes)
      description: Maximum number of runs that can be executed or queued at a time.
      default: 10
      selector:
        number:
          min: 1.0
          max: 15.0
          step: 1.0
          mode: slider
    top_on:
      name: Top (On) Pressed
      description: Execute when TOP is PRESSED
      default: []
      selector:
        action: {}
    top_on_release:
      name: Top (On) Released
      description: Execute when TOP is RELEASED
      default: []
      selector:
        action: {}
    bottom_off:
      name: Bottom (Off) Pressed
      description: Execute when BOTTOM is PRESSED
      default: []
      selector:
        action: {}
    bottom_off_release:
      name: Bottom (Off) Released
      description: Execute when BOTTOM is RELEASED
      default: []
      selector:
        action: {}
trigger:
- platform: device
  device_id: !input pico_remote
  domain: lutron_caseta
  type: press
  subtype: Button 0
- platform: device
  device_id: !input pico_remote
  domain: lutron_caseta
  type: press
  subtype: Button 2
- platform: device
  device_id: !input pico_remote
  domain: lutron_caseta
  type: release
  subtype: Button 0
- platform: device
  device_id: !input pico_remote
  domain: lutron_caseta
  type: release
  subtype: Button 2
condition: []
action:
- choose:
  - conditions: '{{ trigger.event.data.action == "press" }}'
    sequence:
    - choose:
      - conditions: '{{ trigger.event.data.leap_button_number == 0 }}'
        sequence: !input top_on
      - conditions: '{{ trigger.event.data.leap_button_number == 2 }}'
        sequence: !input bottom_off
  - conditions: '{{ trigger.event.data.action == "release" }}'
    sequence:
    - choose:
      - conditions: '{{ trigger.event.data.leap_button_number == 0 }}'
        sequence: !input top_on_release
      - conditions: '{{ trigger.event.data.leap_button_number == 2 }}'
        sequence: !input bottom_off_release
  default: []
mode: !input auto_mode
max: !input mode_max

So far this BP seems to work. Well done!

Any interest in updating this such that is support long-presses? The use case would be IF the user holds down the up button for 500ms before release that it would perform an action, like slowly increasing the brighness.

Hi,

Unfortunately, I don’t have the know how of how to do this nicely. All I see in the listening of event for the Paddle are when either button is pressed and/or released. It doesn’t show me any events for double taps or for press-hold-release.

Sorry to disappoint. However if somebody more skilled than I takes a stab at it, let me know! I’m interested in using that functionility! Haha, even though I don’t know how to make it happen myself.

Update: was able to figure it out after playing with a different blueprint’s code to tailor it to the Paddle Pico

Didn’t know how to properly edit my original post to add the new blueprint without having to discard the old code, so I made a new topic for the new/modified blueprint: here

Thank you to GregTR and his work on Lutron Caséta Pico 4/5 Button Remote Advanced Actions (Core Integration)