I run “upsert” integration with a Pro bridge. It is instant here.
Very nice integration, the update for configuration changes is as easy as it gets.
Here’s a video of how long the above automation takes to fire (I did invert on/off to ensure I was testing exactly what jwelter suggested). Also, I’m not blaming the code - I’ve seen it discussed in two other forums that this is “just the way it is” so I’m trying to figure out what the difference is (I’d even suspect a difference in newer switches, but I just installed that particular switch in last month).
I’m using the Pro bridge, upsert, and I’ve tested with at least 4 switches now. It’s instant with a pico remote, but not with the switch itself, which is the same experience I had with other platforms. 
Very odd. Do you see this with the on/off switches by Lutron as well?
Are you using wifi to the pro-bridge or ethernet?
Yes, same delay with on/off switches - the one in the video is a non-dimmer, actually. I’m using the Pro bridge on the same ethernet switch as my HA server. To really confuse things, here’s the official explanation from Lutron that was posted over in the Hubitat forum:
Lutron RF dimmers always wait 3 seconds before reporting changes made locally at the dimmer. This is because the user is often fine-tuning or adjusting the dimmer with multiple back-to-back events (on/raise/lower/etc), so the dimmer waits until local activity has stopped (3 seconds after the last local activity) before reporting the final level back to the system. The level reported by the dimmer is intended for status purposes only, and is not intended to be used for triggering other events.
A better solution is to use Pico and Keypad events. These are reported immediately to the system, and will result in much faster response time, as the events from a Pico are intended to result in other devices (dimmers, for example) changing in response to the button events. If setting up automation, Lutron recommends using button events rather than level status updates if quick response time is desirable.
The only possibility I see based on that explanation is if this integration is somehow getting the “button event” from the in-wall devices (I’m not even sure if that’s possible) and those seeing instant reactions have a different rule setup. Could someone getting an instant response from an in-wall device post their automation to see if we’re taking different approaches?
What is the use case for needing the state update in less than 2 seconds? Is it to trigger other non-Lutron lights?
Upsert,
Thank you very much for this great integration !!!
I noticed that some dimmers will occasionally show status of ‘on’ and brightness of ‘0’.
There is a thread that may be related: Dimmer lights show as 'on' even when turned off
I’ve read multiple threads and there is mention of and confirmation from you on running multiple hubs. I do not see any instructions anywhere. Is the setup procedure same for two hubs. I have RA2Select and Casetta.
I use two hubs, works fine. Here is my config (MAC will be different, as well as switch, fan, and cover devices):
lutron_caseta_pro:
# Note: Configure only switches, shades, and fans, all others will be dimmers
# switch: [ 4, 6 ]
# cover: [ 11, 12 ]
# fan: [ 15 ]
bridges:
- host: 192.168.1.71
mac: xx:xx:xx:xx:xx:xx
default_transition_seconds: 2
switch: [ 4, 6 ]
- host: 192.168.1.76
mac: xx:xx:xx:xx:xx:xx
default_transition_seconds: 2
Thank you so much for the speedy response. So I tried similar fashion. I don’t see any errors. I have two occupancy sensors only set up on RA2 select and a multitude of switches of Casetta pro. I have the integration report which was requested from front end when i set up config as you show. I still cant find below entity in HA.
},
{
"ID" : 2,
"Name" : "Occupancy Sensor",
"Area" : {
"Name" : "Main Bathroom Bathroom"
}
},
{
"ID" : 3,
"Name" : "Occupancy Sensor",
"Area" : {
"Name" : "Basement Stairs"
You are working off the single Lutron folder/files in custom component folder for both hosts correct?
Well This is weird… Now I see the RA2 S come up as a homekit device. I do not see a device for the Caseta Pro hub though.
Some background. I went with Casetta Pro but already had a whole lot of sensors/maestro switches in crucial areas where I didn’t want any hubs in the mix. Since the RA2 S can monitor the occupancy/vacancy sensors and shades etc. , i wanted to see if i can utilize them for just those components and leave the Casetta pro as I have 23 switches throughout my living space on Casetta Pro. I like the round 360 deg. sensorss cellar, garage etc. where my rental unit tenants might go into as well.
Can not help with the Homekit issue, do not have/use.
Do not use Caseta or RA2 motion sensors, but is it possible they only show up as events; i.e. not as sensors?
I only use one installation/set of files in custom_components.
Good luck, this integration have been rock solid for me using both the Pro and Select hubs.
Im glad to hear you have positive results with both. Gives me motivation. I agree Lutron is THE WAY to go. I use the picos for controlling all sorts of other devices. It is rock solid for me as well.
I am in the process of converting to a standalone NUC for HA. I am currently using VM / Mac OS. I might just start the conversion and set up NUC from scratch instead of Snapshot restore. That might iron out some of my issues as my HA / VM installation is old… and somewhat behind on updates.
I added a pico to RA2s and sure enough we got the pico in HA. Figured I missed something. I read through all the threads I read before again and saw a mention by Upsert.
Upsert stated occupancy sensors do not currently report via Telnet this was back in 17’ or 18’ but there was possible effort to fix that? I guess that has not come to fruition yet.
Does this mean Casetta compatible occupancy sensors are not working either? I really rather use the round 360deg. sensors from RA2s/Maestro.
I have used many diff. occupancy sensors and they all fall short in some aspect. Lutron’s is the only one that works 100%. Thats why I went with them through out the building in areas where I did not need voice control/ advanced logic. RA2s gave me hope to hijack Lutron sensor data for all my HA needs. GRRRR.
I do have one occupancy sensor working with RA2, using the “real” RA2 hub (not Select). However, I do not like the price and the are not programmable in any way, except going to each physical sensor.
And, I am a BIG fan of Pico’s as well. Upsert’s integration handle two, three, four and five button Pico perfectly.
It appears version 112 of HA will support Caseta occupancy sensors (but not Picos). Maybe use one hub for Pico and another to get the sensors.
My whole reason for having the RA2s is for the occupancy sensors and the powerpack in wall units.
Wait, so 112 of HA will support Casetta occupancy and not pico remotes? SO i wont be able to use the PICOs on casetta.
There are two Caseta integrations: the official one with support for occupancy sensors, and Upsert’s with support for Picos. They are based on different protocols.
The RA2 integration will support occupancy and Pico’s.
I have RA2 Select. Not the Full blown RA2. I thought i can connect the occupancy sensors to HA once I saw i can connect my existing Occupancy sensors through the app to RA2 select.
I am trying to avoid using caseta for the occupancy as i would have to buy all new sensors and they don’t offer the round ones which are already recessed into the ceiling in various places. I hate the little log style sensors. Same design since 90s.
EDIT: Should have read more; I should have known about RA2 Select not sending sensor via Telnet.
RA2 Main Repeater on the way… ironically spent only $20 more for the RA2 RR-MAIN-REP-WH on ebay. 
I notice the RA2 puts out a CSV file. Anything special I have to do to load this integration report into the custom component?
currently receiving error when pasting contents from CSV file.
EDIT:
Wait, do i need the Connect Bridge for RA2 to HA integration?
EDIT#2:
I really need to start reading thoroughly before posting. I realized there is no integration report to be used. I did see my RadioRA motion sensors pop up when browsing through all devices and YESSS!!! state change detected!
Using the built in HA lutron component for RA2 and Caseta pro using Upserts component. Config as below
lutron_caseta_pro:
bridges:
- host: 192.168.1.55
mac: xxxxxxxxxxxxxxx
default_transition_seconds: 1
lutron:
host: 192.168.1.56
username: XXXX
password: xxxxxxxxxxxx
Super instant response is amazing!!!
P.S. if anyone wants to trade a CONNECT bridge for RA2select or Caseta bridge. PM me as i have both just sitting here.
1 Like
Im sure this is something i’m missing, but i don’t see the upsert/lutron-caseta-pro repository in HACS as mentioned on the git page… I have my Caseta pro bridge and 8 dimmers, 3 switches and 6 pico’s coming Monday (Note… My wife does not know how much this costs!). Trying to get a head start on the setup. Am I missing something?
1 Like