Lutron Integration @ CES?

It’s fairly far along in our testing process. It’s going well!


Well come on, I spent all that $$$ on Lutron and having to use IFTTT to turn on lights is pathetic. :smile_cat:

1 Like

@njschwartz has created a really useful implementation you can use to do the integration now if you’d like. [BETA] Lutron Caseta Integration using Raspberry Pi (Pro or Standard Bridge) [DEPRECATED--See new Release thread instead]

You don’t have to use a raspberry pi, BTW. I’ve got my running on a linux VM. It’s pretty straight forward so you might check it out if you just can’t wait for that integration.

1 Like

Would be nice if SmartThings could add-on the Lutron protocol to their hub by using the USB port on the hub with a USB dongle. This way there is no need for a Lutron Bridge:sweat_smile:

Don’t see Lutron letting that happen.

1 Like

Lutron is fine with dongles as long as they are licensed. But you don’t need one, Lutron has an open API which allows for telnet integration with the Lutron Smartbridge. Lutron generally likes integrations with systems that provide extended functionality.

Since the SmartThings hub doesn’t support telnet, Two different community members have created “man in the middle” server integrations with Lutron using the telnet options.

1 Like

Thanks for the reminder @njschwartz has created a great solution that works well based on all the feedback.

I’m going to hold out for the stock ST solution, sounds like that’s close. Also happy that we have a plan B thanks to this great community.

I’m sure folks will be able to validate differences pros/cons of ST Lutron partnership versus the community solution as soon as it gets released.

Still very happy I went Lutron Caseta for light switches. Just wish they made a multi speed fan control for switch consistency. Having to opt just for their on/off switch and just have the one speed. :slight_smile:


@Tyler - any update on progress/timing?

1 Like

I’d love to see them expand the caseta line a bit too, but they may be holding those devices for their more premium line…

I think the 4-6 weeks is about up :wink: I still have 3 switches I got through Alexa deal waiting to hook up. Installed one and using IFTTT but the delay is ridiculous

You can send me those other two so the wait isn’t as hard!

What is the delay with IFTTT?

Does anyone know what delay is expected to be from the Lutron Caseta invocation via Smart Things?

I have three weeks before I’ll have to return my Caseta Devices within the return policy if I can’t try the integration before then… Anyone (@Tyler ?) know if the integration will likely be available in the next 3 weeks?


  • I actually recently bought $2,500 worth of Caseta dimmers/remotes for my house, but I’m not going to install them until I can see if the SmartThings works well with them. (My main concern is delay time from SmartThings -> Light Reaction. I care less about swtich -> SmartThings.)
  • For reference, it’s about 1-2 seconds from the end of “alexa, bedroom 30%” to lighting response through the Lutron Caseta hub on my test dimmer. (Fast internet here, if that matters.)

The IFTTT delay varies from house to house, you just have to try it at your house and see. At my house it’s a pretty consistent eight seconds which is fine for some things, but would be too long for others. For example, “turn the lights on at sunset” doesn’t matter if it’s off by eight seconds one way or the other. But using a motion sensor to trigger a light to come on to someone walks in the room would find eight seconds unacceptably long.

Good wifi will help, but mostly it’s the round-trip to the cloud.

If you have harmony or hue bridge already set up, you can test the lag using their channels, it should be pretty similar to Lutron’ Smartbridge.

I personally have Lutron Caseta switches and like them a lot, but I’m not using them with smart things. I am using them with echo.

One more thing, which you probably already know, but just to be sure given the size of your investment: the official Lutron/smartthings integration is cloud to cloud and does not include the pico remote. So smartthings will not be aware of any button presses on a pico even with the official integration.

1 Like

Community member @njschwartz has built his own connector which is working great for a growing number of uses. I’m sure I read latency was not an issue for his solution (local connection via RasPI) so there’s a solid plan b if the native ST solution isn’t for you.

I have a growing number of Caseta switches, dimmers and Picos - love them!. They’re so nice and polished compared to other smart switches (and I’ve tried a bunch).

My vote. Keep em!

Link to post. [BETA] Lutron Caseta Integration using Raspberry Pi (Pro or Standard Bridge) [DEPRECATED--See new Release thread instead]


Here’s a completely unscientific test, at 10:00pm EST (FWIW).

Smartthings command sent via a CoRE “DO” piston to IFTTT to my Wink hub to a Lutron switch: range of 3 to 5 seconds response.

YMMV, especially based upon time of day, loads, etc.

Thanks everyone for the data. With Alexa/Echo’s delay at at about a second (including doing voice processing!) I do hope smartthings can integrated with a similar latency as opposed to the 3-5 seconds with IFTTT.

Forgive all the ignorant questions, but ignoring latency, will smartthings have programmatic access to the on/off or dimming level of a Caseta dimmer? If so, it seems to me that you can infer pico remote button presses by polling the associated dimmer for changes, no?

I was thinking that also, but you likely wouldn’t be able to differentiate the Pico button presses from the same presses made on the dimmer. Which, for many cases would be fine, but if you wanted a particular button press on the Pico to trigger a scene or state change, you likely wouldn’t be able to do that.

1 Like

@JohnMcD I feel your pain with the entire Caseta and SmartThings issue. I was in your shoes a few months ago. I love the Caseta stuff but wanted it to work with ST. I tried IFTT as well but had similar issues to you. Honestly even 3-5s might have been tolerable but occasionally I’d get one 20+s later. Not useful to me. That’s why I created the middle man solution. In mine and others experience it’s very fast (about a second or so) and reliable. The major downside is it’s a bit of a pain to set up.

I am hopeful that ST integration will be good but am not super optimistic. It’s going to be cloud to cloud not LAN which potentially will add lag. Additionally, it seems it will be pretty basic, on, of, dim, but like you I wanted pico support.

In the next couple of days I’ll be updating my solution which will allow for using Pico remotes to control anything you want in ST but ONLY if you have a pro hub. It will also add scenes to ST which you can then trigger however you like. Not trying to sell you on my creation, just letting you know there’s another decent option should you want to keep your Caseta’s and not wait for the official integration. Good luck!!


Hey, just curious why pico remotes will only work with the pro hub? Do they expose more via an API there? sadly, I’ve just got the cheap one that comes with the starter kit. (PS, I’ve mentioned it before, but your solution is great as far as control. Very responsive. Since setting it up a few weeks ago I’ve had to restart the python script once, otherwise it has been bulletproof.)

I wouldn’t get too hung up on the Caseta stuff. It’s nice, but I have both Lutron Caseta and Leviton DZC switches/dimmers in my setup, and quite frankly the standard paddle style Leviton are more user friendly. I have several Pico and BulbConnected remotes and they fill a need, but the standard paddle style are much easier to use in the dark. The Lutron devices have no “feel” to them. The buttons are small and uniform in texture. Not a good solution when you’re trying to turn a light on in the dark, especially for guests who are unfamiliar with them.

1 Like