Lutron Caseta Interface

Development
151

Thanks for the help, I got everything working and scripts made as well.

My issue was I had originally followed the instructions posted for the Non Pro Hub and didn’t know this thread was different for the Pro Hub, which I have.

Thanks again.

152

@upsert Using your Caseta Pro custom component and loving it. Do you have any plans to submit it as an official component and/or add support for the new entity registry?

It’s amazing how much faster the Pro Bridge is at processing commands compared to my old Wink hub.

1 Like
153

I don’t have any immediate plans to submit it as a component. I recently moved and haven’t got back to this in a while. I’ve bought a RA2 Select hub so I plan to do some testing with it and see if it works with the component. Maybe a combined RA2 Select Caseta Pro component could be submitted.

For the entity registry, I’m not quite sure what the advantage would be. The component uses names generated from the Lutron app so you can already customize those. It may be something to add for forward compatibility reasons. I’m not seeing any readily available developer documentation or guidelines.

1 Like
154

Entity Registry allows you to customize entity id’s and guarantees that a device will always get the same entity_id. AFAIK the only thing it needs is some kind of “unique ID” for each device. I would think the IntegrationID the lutron hub gives out would work, though it would likely need to be prefixed with some kind of hash marking the hub as well. I think the hope is that most components will support it in the future to simplify UI-based configuration.

I’ve had it set up for 3 days now and my mind is still blown at how much faster it responds compared to my Wink. I had a “goodnight” automation that turned off a bunch of lights. It took the Wink over a full minute to turn everything off. This hub has everything turned off within about 1 second. WifeApprovalFactor++

3 Likes
155

Does anyone have a good way to use a pico to control some Hue bulbs? Mainly the dim up and dim down portion.

Thanks!

156

I’ve done some testing on a Ra2 Select bridge and it works exactly like Caseta Smart Bridge Pro. My custom component works without issue. Waiting for additional items to be installed for more testing.

Ra2 Select also supports occupancy/vacancy sensors now so I may order one of those as well. Judging from the Integration Protocol I think it will be like all the other pico button sensors, but with the equivalent of a button press as occupied and a button release as unoccupied.

The latest software for the bridge also shows the Ra2 Select is coming to Europe on the 868 MHz frequency band. Not sure they have many 240 V dimmers and switches to go with it, but I think they already have the shades.

157

If you are using a Caseta Smart Bridge Pro and my custom component, you can setup an automation for the pico button. Search for ‘increase brightness’ on the forum and there are a lot of ways to do it.

Here is one thread:

If you are not using a Pro bridge then you won’t get any sensor events for a pico button press and you are out of luck.

158

I’ve just ordered the Pro and going to migrate from the standard hub to the Pro hub. Nearly all of the configuration contained in your instructions make sense to me, except: integration report. When I create this, is this just a blank file? I see references on here to copy over some JSON over to the integration report, but I don’t see any documentation on that. Thanks for your help.

159

I will work on improving the instructions for first-time setup!

It goes like this:

  1. Setup the Lutron app and add all your Lutron devices through the app. Enable Telnet Support under settings menu -> Advanced -> Integration. Also enable static IP under Network Settings and write down the IP.
  2. In your Home Assistant installation, install the custom component by copying in the files as noted in the instructions.
  3. In Home Assistant configuration.yaml create a minimal configuration for the custom component using the IP address you wrote down and start Home Assistant.
  4. Once started and assuming first time setup, open Home Assistant on your mobile device and you should see a prompt to Configure Lutron Caseta Smart Bridge PRO on the front-end. Click on Configure and you’ll see a box to paste your integration report.
  5. Switch over to the Lutron app, go to settings ->Advanced -> Integration -> Send Integration Report. When prompted, select ‘Copy to clipboard’.
  6. Switch back to Home Assistant front-end and paste in the Integration Report. If your phone does not have copy and paste options, you will need to share it to yourself through email or to another app that supports copy paste.
  7. Once you submit the Integration Report the component should setup all your devices as dimmers and will save the Integration Report to your config directory as a json file.
  8. If you have switches or Lutron shades, open the Integration Report in your config directory and find their Integration IDs and edit your Home Assistant configuration as described in the instructions to tell it which devices are switches or shades. Unfortunately, the Integration Report does not contain this information so you need to do this manually if you have switches or shades. Restart Home Assistant if you change the yaml file.

You should be up and running with these instructions. If you edit your Lutron configuration by adding scenes or devices, I suggest deleting the Integration Report JSON file from the config directory, restart Home Assistant and follow the above steps to copy and paste the new Integration Report over to Home Assistant.

Also if you are switching from the non-Pro hub, you may want to go into the Lutron app and delete all your devices under your old account. It should make it easier to add them back to the new account and new hub. Lutron does not support multiple hubs in an account so you won’t have much choice but to start from scratch.

Hope that helps!

5 Likes
160

Thanks so much! This really clears everything up!

161

Yes - thanks @upsert. I also ordered a Pro after the latest non-Pro break. Any intention to submit this as official now? While it is possible the non-Pro could be fixed again, I think it is clear Lutron wants none of it for that model and it will be a continual chase that will just turn people off from HA.

No pressure! Your work is much appreciated!

162

Hi @upsert !

First, thank you for this fine bit a of work!

I already have Caseta Smart Bridge Pro, but I am near my 50 device limit. I was thinking of picking up Ra2 select bridge to start extending my system (really excited about the occupancy sensors). Would it be possible to run both bridges using your custom component? I rather not have to run the standard caseta integration and your component for the ra2 select stuff. Thanks!

163

Yes, it certainly works and I have tested that setup with two hubs.

It helped to have a spare mobile device (i.e. an old phone/tablet) to run the app on the different account required for the new hub. Delete from one, then add it to the other. The Lutron app does not have easy account switching and it is easier to keep the spare phone around to make adjustments.

One catch I encountered is that Google Assistant will only support one hub. It seems to be a limitation on the part of Google that assumes you only have one integration of each type and it won’t let you add it again.

Also, I assume you are aware that you cannot add any Caseta devices to a Ra2 Select bridge. The only hardware that works on both models are the Pico remotes and some of their shades.

164

Continuing the discussion from Lutron Caseta Interface:

Great news, and thanks for the confirmation! Yup I understand about not being caseta compatible. I only really want to add fan controls which seem to be RA2 select only, and maybe a few more switches (the RA2 stuff is so much more expensive!), but i am really excited about the occupancy/motion sensors, we use them at work for commercial lighting and they work amazingly well.

165

This component seems to offer a lot more than the Lutron component and I was wondering if it supports standard RadioRA2? Is the step of having to generate an integration report (instead of pulling from the repeater) due to a different with Caseta Pro and RadioRA2 select? Thanks!

166

The RadioRA2 integration report is in a completely different format.

If there is a developer out there with a RadioRA2 Main Repeater, I’m sure the component could be improved with additional HA platforms. Post something in the Feature Requests and it might get picked up.

167

Thanks for the reply. I figured that out after posting. While not a programmer, I have a basic understating of coding and would be happy to contribute if there’s a want for it.

168

I’ve got a good way to control Hue bulbs with pico remotes. Message me if you still haven’t figured it out.

169

So can anyone say if the newest version of HA is still working with the custom component from @upsert? Been a while since I updated and feel I should probably update now.

170

Yea, still working great with the latest release

2 Likes