Lutron Caseta Pro Pico Switch

Blueprints Exchange
,
1

This blueprint will allow you to assign actions to Pico remotes if you are using the Lutron Caseta Pro Custom Component

This allows your to assign any action(s) to each of the 5 buttons on the pico remote.

600Ă—600 11.6 KB

blueprint:
  name: Pico Remote Actions
  description: "Freely customizable actions for Lutron Caseta Pico buttons. \n 
  This is for use with the Lutron Caseta Pro Custom Component \n 
  This will ADD actions to the previously applied Lutron App button controls. \n
  Each button can be assigned its own individual action(s)"
  domain: automation
  input:
    remote:
      name: Pico Remote
      description: The Pico Remote that you will be assigning actions to
      selector:
        entity:
          domain: sensor
          integration: lutron_caseta_pro
    button_top:
      name: Top Button
      description: The top (light on) button on the Pico Remote
      default: []
      selector:
        action: {}
    button_up:
      name: Up Arrow Button
      description: The arrow up (increase brightness) button on the Pico Remote
      default: []
      selector:
        action: {}
    button_middle:
      name: Middle Button
      description: The middle (favorite) button on the Pico Remote
      default: []
      selector:
        action: {}
    button_down:
      name: Down Arrow Button
      description: The arrow down (decrease brightness) button on the Pico Remote
      default: []
      selector:
        action: {}
    button_bottom:
      name: Bottom Button
      description: The bottom (light off) button on the Pico Remote
      default: []
      selector:
        action: {}
trigger:
  - platform: state
    entity_id: !input remote
condition: []
action:
  - choose:
      - conditions:
          - condition: state
            entity_id: !input remote
            state: "1"
        sequence: !input button_top
      - conditions:
          - condition: state
            entity_id: !input remote
            state: "8"
        sequence: !input button_up
      - conditions:
          - condition: state
            entity_id: !input remote
            state: "2"
        sequence: !input button_middle
      - conditions:
          - condition: state
            entity_id: !input remote
            state: "16"
        sequence: !input button_down
      - conditions:
          - condition: state
            entity_id: !input remote
            state: "4"
        sequence: !input button_bottom
    default: []
mode: restart
7 Likes
2

This is awesome! Thanks for making it. Any chance you can add the PICO two button remotes, or the 4 button Scene Remotes?

3

Should be relatively easy but I don’t have any of them. I just need to know what the state is when you press the buttons. If you let me know I can make another blueprint for them. Or perhaps make it part of this blueprint.

Do those remotes show up in the selector for this blueprint?

1 Like
4

No they don’t show up in this blueprint, just the normal picos, and the pico fan controller. The two button pico’s use: top Button (ON) State = 1 and bottom button (OFF) State = 4

I actually don’t have the 4 button scene one setup yet, but will let you know.

5

I have several of the 4 button scene switches (love them). The states are as follows:

Button 1 (Top-most) = 1
Button 2 (2nd from Top) = 2
Button 3 (3rd from Top)= 4
Button 4 (Bottom/ Off Button) = 8

Hope this helps!

1 Like
6

Are you using the custom componenet or the core integration?

7

I am using upsert’s custom component.

8

I know I’m probably missing something very obvious but I can’t see any of the Pico remotes in the blueprint selector, I’m also using upsert’s custom component.

9

It seems there is a cool off period. I can’t use another button for about 5-10 seconds after clicking one. For instance, I can’t turn a light on with the on top button but have to wait to turn it off.

10

I’m using upsert’s custom component and regular automations (haven’t converted to blueprints for that yet). The only cooldown I notice is that rarely it seems like it doesn’t want to log a second button press until the green light on the Pico remote stops flashing. I’m guessing the green light flashes while the device is actively talking to the bridge? But that’s on the order of a second or less, definitely not 5-10s.

And most of the time, I can immediately push another button as soon as I release the first one. In fact, I just tried it on one of my (Zigbee) closet lights that’s controlled through HA by a Pico - it responded to an OFF command immediately, even when pressed ~0.5s after the ON button while the light was still in the process of fading on.

1 Like
11

I wonder if its related to zigbee group. Its a group of outdoor fan lights. Its quick to turn on but will not immediately turn off. Real Strange.

12

I have not had an delays on mine. I am thinking about trying out the new default integration so I may need to rewrite this for that in the next few days

13

Yep I have zero delay issues with any Pico remotes (scene or dimmer).

They have always been extremely responsive for me; use cases include automations, Alexa binary sensor triggers (from Pico scene buttons), python scripts that loop to dim lights and to adjust receiver volume via HTTP rest commands (Pico dimmers), etc.

14

I am using the native integration now, which is wonderful but it has complicated the blueprint writing for me. I am working on it but for now I am going to be keeping the custom integration running so I can still use it for my peco lights!

Hopefully i can work through it soon and post a version for the native integration

15

Desperately waiting for the native lutron blueprint.

1 Like
16

I am goin to work on it today.

17

This is proving more difficult than I imagined. Maybe someone smarter then me can figure it out!!

Im gonna keep plugging away at it but I am not good with events in HA.

18

FYI, @stephack has posted a version that works with the core integration.

As such, I will be moving over to that blueprint. I will be removing the custom component from my system so future changes may break this blueprint.