Another Blueprint for Lutron 5 button Pico with press and hold for dimming function

Blueprints Exchange
,
22

Thanks. I had not seen that. I went through all of them and enabled them and it’s all working fine now.

23

Hello. This blueprint is exactly what I’ve been looking for, however my pico is not showing as available in the pico device drop down. I have enabled all of the pico entities.

I am in the UK so my pico model number is slightly different… PK2-3BRL-TXX-X01 (Pico3ButtonRaiseLower).

I am however very new to all of this and can’t work out how to change the device model in the blueprint.

Does anybody have any advice?

24

I have done a small re-write of this blueprint to better handle the press and hold of the raise/lower buttons. I have also added inputs for the ‘step percentage’ and ‘hold time’.

25

@pevzzz did you ever find the answer? Im in the same situation and unable to takeover the blueprint to edit it.

26

The github gist with this blueprint is giving me a 404… anyone have a copy?

27

Here is the link… Lutron Pico 5 Button - Light Entity Control · GitHub

1 Like
28

I created a ‘UK’ version. No promises that it will work, but give it a try.

29

I just wanted to jump on here and say THANK YOU, Tom, for creating this excellent blueprint. It’s super easy to use, and it works great! The only suggestion I have is that it might be nice to have an option to disable the “Favorite” button. I couldn’t find any kind of “no-op” action to use.

30

I can’t figure out how to get the dim down button to stop short of turning the light off.

I’m not familiar with YAML, but I assumed the

        until:
        - condition: numeric_state
          entity_id: !input entity
          attribute: brightness
          below: 1

was the relevant portion, but nothing I changed the “below” number to had any impact in that button dimming the light all the way to off.

Changing the percentage steps also had no impact.

31

This blueprint has a few inherent limitations because it relies on the automation engine for timing-critical actions, and automations cannot always respond quickly on a busy system. To address this, I created an integration that implements the same behavior natively. More details are available here… Pico Link — A YAML-Based Controller for Lutron Pico Remotes

32

Sorry for the much delayed response. You can simply at an action like delay: 00:00:01 which would negate any default action by the automation.