Can Hubitat initiate a Pico button press?

I have a number of Lutron Caseta devices hooked up to a pro Lutron hub, and controllable by Hubitat via the Integrator app. All of the Cesata switches work great.

I also have a few pico remotes (love these things). Using the Button Controller app, I am able to receive any pico button presses and do something if I wanted to.

But what if I want to initiate, or simulate a pico remote button press to the Lutron Hub? This all works fine for Caseta switches - Hubitat can send the command to the Lutron hub to turn the switch on, off, etc.? But I want Hubitat to tell the Lutron hub to react as if someone pushed a pico remote. Can this be done?

It seems like this should work. The pico device driver has a button press and release button where you can put in the button number. They just don't appear to do anything.

Here's my use case. I can have several Serena Shades (about to order) paired with my pro Lutron hub, and have a single pico programmed to move them up and down all together. The Lutron side of things keeps them all operating seamlessly as single unit. So I would want to be able to have Hubitat tell the Lutron hub to do the same thing by simulation the pico button press.

Unfortunately, as I understand it, the pico button presses only go one way (from Caseta hub to hubitat) but not the other way.

Yes, Picos are just button controllers. Hubitat can press a button in any app that allows button presses.

Also know that Hubitat can "press the button" for Lutron scenes. Your bridge has 100 scenes that you can set in the Lutron app. In Hubitat your bridge is a giant button controller with 100 buttons. Using those scenes are a good way of avoiding popcorning where lights go off sequentially rather than all at the same time. They're a good way to synchronize shades as well.

1 Like

I could be mistaken, but I don’t think that the command will go back to the bridge. I never did try it myself…

That’s pretty cool!

Hubitat has no problem pushing a Pico button. It all occurs over the Telnet interface.

Technical details on page 124

And note. If one uses Hubitat to push a Pico button then one needs to keep the logic straight - it's pretty easy to create an infinite loop of buttons pushing buttons.

1 Like

You are mistaken. This works just fine.

For that matter, it works with any button device used in Hubitat.

2 Likes

Thanks to both of you @bill.d and @bravenel! I learned something new today.

1 Like

Thanks everyone. So then I guess my next question is, what could I be doing wrong? In my device that is using the fast pico driver, I can see the events of button pushes from the actual device, as well as from a rule I have to push the button. But while the light goes on when the physical button is pressed, it does not when the button press comes from Hubitat.

It would help if you could show some logs, using screenshots.

I just tested this, and it works as expected.

That works for me with both Lutron Pico driver and Lutron Fast Pico driver.

Here are some logs from the device page Events. The last 4 entries are from using the rule above.

I have something very similar set up to test. I also see the similar log. It shows button 1 was pressed - type digital. Just that nothing happens.

I took a look at the system log. What is below is the log from two different Lutron devices in Hubitat. The top one is the pico device. The second set is a Lutron switch being turned on via Hubitat. I notice that the Lutron App event is missing from the Pico button hubitat press.

[dev:249]2021-10-20 08:20:19.837 pm [info]Kitchen Remote button 1 was pushed

[dev:1]2021-10-20 08:27:00.934 pm [info]China Cabinet was turned on [digital]
[dev:2]2021-10-20 08:27:00.903 pm [info]rcvd: OUTPUT,2,1,100.00

I also just tried it also and although Hubitat recognizes the press of button 5 on my pico remote, the switch to which the remote is connected via the Lutron Hub is not recognizing the “Off” (Button 5) command - the Lutron Light switch is not getting turned off.

Works for me. Set up a Button Controller app for 'Test Pico'. Button 1 turns on kitchen table lights to 50%. Button 5 turns them off. Button 3 pushes button 1 of the 'Test Pico'.

Logs from pushing button 1 on the Pico:

Logs from pushing button 3 on the Pico:

So if I do the same thing, use button controller for button 3 push to push button 1. It does work when I physically push button 3 on the remote.

[dev:11]2021-10-20 09:25:34.460 pm [info]Kitchen Lights was turned on [physical]
[dev:2]2021-10-20 09:25:34.436 pm [info]rcvd: OUTPUT,10,1,50.50
[dev:249]2021-10-20 09:25:34.427 pm [info]Kitchen Remote button 3 was released
[dev:2]2021-10-20 09:25:34.409 pm [info]rcvd: DEVICE,3,3,4
[dev:249]2021-10-20 09:25:34.352 pm [info]Kitchen Remote button 1 was pushed
[dev:249]2021-10-20 09:25:34.315 pm [info]Kitchen Remote button 3 was pushed
[dev:2]2021-10-20 09:25:34.293 pm [info]rcvd: DEVICE,3,3,3

But if I use Rule Machine to push button 3, this is all I get in the log, and nothing physically happens.

[dev:249]2021-10-20 09:30:35.471 pm [info]Kitchen Remote button 1 was pushed
[dev:249]2021-10-20 09:30:35.384 pm [info]Kitchen Remote button 3 was pushed

@scott13, is Kitchen Remote linked directly to the Lutron dimmer via the Lutron Hub? (IE not going through Hubitat to send on/off/dim commands to the dimmer)

@bill.d, from what I see, the difference between the test you performed and the one I performed is that the button I tested has no commands in RM’s button controller. It is directly linked to the dimmer via the Lutron Hub / direct link.

1 Like

Kitchen Remote is a device of type Lutron Fast Pico, Device Name is the Lutron Integration ID. I see the events there from the physical button presses. And pushing one of the buttons from a button controller seems to work. But doing so from Rule Machine does not. Im sure I have just set something up incorrectly, but I just can’t work out what.

FWIW, when I use the Hubitat commands on a Pico device (things like push(1)), I do not get any logs for the Lutron Telnet device (all logging is enabled) or the Lutron Pico device on Hubitat besides the generation of the Hubitat event. I don't have any other way to test this, but nothing here suggests that the event makes it back to Lutron. This is an RA2 system with the "regular" Pico driver, and the Picos are not "associated" with any real devices (switches/dimmers) on the Lutron side--they just exist in a room/location.

1 Like

Ah, yes, that is correct. Hubitat does not push the Lutron button via Telnet even from the device page. So I was not correct in my understanding. I'm not sure why, but I think it could end up creating a loop.

If you want to layer Lutron native functionality on multiple buttons, use the scene on the bridge functionality that I described in my post above. Assign that scene to both Pico buttons in Hubitat and add any other settings to whichever button you need.

1 Like

Ok, thanks. Guess I was hoping that the push and release buttons being on the pico device driver, that you could initiate the pico button clicks on the Lutron hub. Sounds like that’s not the case. But the scene method would work in a number of cases, so I’ll give that a whirl. Thanks everyone !!!

OK, with some moderate effort you can have Hubitat push the actual button via Telnet. You'll need to learn a little of the Lutron Integration Protocol I posted above and you'll need to learn Hubitat's Custom Actions in Rule Machine or Button Controller.

In RM/BC you have an action that runs a Custom Action. That custom action is based on the Actuator device type and the Lutron Telnet device. You send the message in the Lutron Telnet format. For a button push you need to send both push and release events. Here is the setup from BC for pushing button 2 on the Pico:

1 Like

No, this is not the case. The uses I've talked about involve the Pico having no connections at all on the Lutron side, and it is being used as a Hubitat button device, not as a Lutron device. As such, it can control other Lutron devices -- as Hubitat devices -- but not within the Lutron system. As I recall, a Pico tied to a Caséta device doesn't even send Telnet commands to Hubitat at all.

Sorry, I missed the true question you asked in the original post.

1 Like