Lutron Caseta Pico (Core Integration Only)

Blueprints Exchange
15

I’m not sure “restart” is the best mode for this (though I’m not sure which is tbh). Took me a few minutes to figure out, but I had a script that I was triggering off of the “favorite” button that takes several seconds to run (Sonos grouping) and it was failing to complete until I changed the mode to “queued”.

I assume “restart” was stopping the execution of the script when the “Release” event came in, as the script ran fine if I held the button down until it finished :stuck_out_tongue: . Probably only relevant for complex scripts/actions – I would assume single actions would complete before the “Release” event came in.

Anyway, with that little tweak it seems fine – this will make setting up the rest of my pico remotes much easier. Thanks!

1 Like
16

Yeah…there’s no “correct” mode as it would depend on what the Automation is designed to do (ie multiple quick actions, long extended actions with delays, etc).

I wonder if I can have the mode as a UI option now that the latest HA update allows “select” selectors. :thinking:
Will look into it.

17

I added an option to select the mode the automation will run in. The select selector worked perfectly for this use case.
:point_up: @ogiewon, @mattsheffiel (in case you wanted to update your BP’s to include this functionality).

1 Like
18

Does anyone have an example for Up/Down for dimming/increasing lights or opening/closing shades? I’m currently just setting it to say 25% but there must be some good way to jump in 5-10% increments or something any ideas?

19

@stevenpoint Can’t speak for shades but I do precisely this for lights using brightness_step.

service: light.turn_on
data:
  brightness_step: 20
entity_id: light.bedroom_lamps_group

Use negative numbers for lowering brightness.

1 Like
20

Thanks for all of the work you’ve done on this, I’ve been using it and it works great. I like the brightness increase but I really wanted to replicate the regular Caseta dimmers press and hold to increase and decrees brightness.

I followed these instructions to create an automation for smooth dimming since I use Deconz for most of my lights. Is this something that can be ammended to this blueprint or a whole new one has to be created?

21

The Automation in the link you provided is brilliant and I “think” you can replicate it as is.

Most of the magic is in the action portion ie the brightness transition and stop commands. This is specific to deconz but you can easily replicate it in the action section of the blueprint.

So essentially you could set the Up Arrow button as follows.
On press - run the actions shown in the “increase brightness” portion of the Automation.
On release - run the actions shown in the “stop brightness” portion of the Automation.

I don’t have deconz so I have no way to know if this will work, but in theory it should.

22

That’s exactly what I just did, I used your blueprint and for the “action type” I called a service, then filled out the data for dimming and stop dimming, I also used it for the top and bottom buttons, now it fades to full brightness when ON is pressed and fades out when OFF is pressed, plus continuous dimming.

P.S I also used the same blueprint for RF curtains, I did STOP on release so now I can open and close to any position in addition to Open/close all the way. I still have to figure out a “preset” position for the favorite button.

Thank you!

1 Like
23

I keep getting “unsupported url”

24

Try it now. Not sure why it stopped working all of a sudden. Haven’t changed the Import link since I initially posted it…till today anyway.

25

It works and it’s wayyyyy faster than Hubitat. Can I hold to decrease brightness like Hubitat? Thx

26

I just updated to the Core Integration, do Pico’s not show up as entities anymore? It shows as a device in integration, only my true switches show up as entities. I looked through the documentation, but I must have missed something? I used Node Red to manage automations for them when they were entities.

27

Picos were only available as entities in 3rd party integrations (eg Upsert). They are only available as devices in the core integration. I haven’t use NR in a while and unfortunately I do not remember if/how you can reference them in flows.

28

I was using a custom component that seemed to break in the last month, I was about a month behind on updates. It used to expose the Pico’s as sensor entities.

29

Is a release event when you actually let go of the button or when you push it again if the current event/scene is activated?

Basically I want to setup a system where I have the 4 buttons and each press is turn scene 1,2,3,4 respectively on and off.

30

Yes

Scenes don’t work that way. You can only activate a scene (ie turn it on). You can potentially setup a button press to cycle through scenes, but it not something that HA let’s you do natively. You would need to use something else to keep track of and activate each scene…like a an input_select. That is beyond the scope of this thread bit you can search the forum for help setting this automation up. Here’s one thread that may be of help.

31

I apologize if this question has been asked before… I did read all the comments in this thread and may have missed it. I have been using the cutom upsert component for a year or so with @MizterB Node-Red flow for multiple Pico remotes.
Does your BluePrint and the new core Lutron Caseta integration work with multiple remotes?
About to set up my new HA Blue appliance and wondered if I should just start from scratch or migrate what is already working.
Many thanks :pray:

32

This blueprint works with multiple remotes by creating an automation from the blueprint for each remote you want to configure.

I believe the primary difference between this and my Node Red flow is that the blueprint does not support double-tap actions.

2 Likes
33

Anyone get this blueprint to work with Shades? This would work well, but I can’t get it to trigger any blinds groups.

34

This blueprint is only for the remote outlined and pictured at the top of the thread. If you are using that exact model remote, then the issue is likely in the action section you have configured. Try testing your service calls in the developers tools section before adding to a button press in the blueprint.