Lutron Caséta Smart Bridge R/W Delays

Add-ons Bindings
1

Hi, I updated to openHAB 3.0 and the current Lutron binding in hopes of a fix to a long-standing issue. As the issue is still occuring I’m now thinking this may be a hardware limitation of the Smart Bridge. Before I go out and purchase more equipment I thought I’d ask here.

Whenever I receive a Lutron event from the Smart Bridge any corresponding Lutron actions occur with a ~1-2 second delay. This has been a minor inconvenience for me but is confusing for guests and anyone who’s used to pressing a light button and receiving immediate feedback.

Simplest Examples/Test Case:
Pico button press → Turn on Caséta dimmer = Delay
Pico button press → Turn on Hue light = No Delay
Homekit Switch Item → Turn on Caséta dimmer = No delay

I thought the LEAP protocol implementation might solve this but it’s still occuring.

My assumption is the Smart Bridge can only handle 1 interrupt at a time and/or has a cycle time between polling for updates and posting updates. My proposed solution is to get a 2nd Smart Bridge, with the Pico switches on the first and dimmers/switches on the 2nd. With the LEAP support I might try this on a non-pro bridge.

Any thoughts? Anyone else experience this?

PS I am truly impressed by the 3.0 upgrade and all the work that has went into this project. I was prepared for much more of an upgrade process but it was relatively seamless on a Raspberry Pi 4 with only a couple Java and Binding changes to incorporate into my settings. Thank you!

2

Hi. That is odd. Has anyone else seen a similar problem? I agree that anything more that 500ms for a light to respond is too long. That’s one reason why I generally recommend tying controls to lights within the Lutron system, where possible, rather that bouncing it through openhab. That also reduces the number of controls that will fail if your openhab system is unavailable for some reason. Still, I would not expect to see delays of that sort in routine operation. You may want to try enabling DEBUG or TRACE level logging for the binding so you can see where the delay is coming from.

If you want to get a second bridge, you’ll need a pro version if you want to put the picos on it. The non-pro version requires the LEAP bridge, and the LEAP protocol annoyingly does not support button press notifications.

3

Yes when I use the Lutron system to match the Pico to the Dimmer there is no delay. However, I like the flexibility and customization OpenHAB affords.
e.g. Press once for half power, Press 2nd for full power/ON, Press 3rd time for OFF - or if lights are already on Press once for OFF
e.g. 4 button Pico on left as fixture selector, up/down Pico on right as dimmer

Below is the extract from DEBUG

  1. The timing does not represent the actual reaction timing when OpenHAB is executing the commands - the delay thus seems to be with the Lutron bridge.
  2. I still have the HomeKit example driving through LEAP - I could change this if it matters

HomeKit → OpenHAB → Lutron Dimmer

==> /var/log/openhab/openhab.log <==

2021-04-03 21:50:33.222 [INFO ] [hab.core.model.script.lighting.rules] - Kitchen Main Lights Half Power

2021-04-03 21:50:33.234 [TRACE] [n.internal.handler.LeapBridgeHandler] - Received request to send Lutron command: #OUTPUT,3,1,25,0.25

2021-04-03 21:50:33.236 [TRACE] [n.internal.handler.LeapBridgeHandler] - Sending command {"CommuniqueType": "CreateRequest","Header": {"Url": "/zone/1/commandprocessor"},"Body": {"Command": {"CommandType": "GoToDimmedLevel","DimmedLevelParameters": {"Level": 25, "FadeTime": "00:00:01", "DelayTime": "00:00:00"}}}}

2021-04-03 21:50:33.265 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Received message ~OUTPUT,3,1,25.00

2021-04-03 21:50:33.274 [INFO ] [hab.core.model.script.lighting.rules] - Kitchen Main Lights 25

2021-04-03 21:50:33.275 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"ReadResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"200 OK","Url":"/zone/1/status/level"},"Body":{"ZoneStatus":{"href":"/zone/1/status","Level":25,"Zone":{"href":"/zone/1"},"StatusAccuracy":"Good"}}}

2021-04-03 21:50:33.276 [DEBUG] [rnal.protocol.leap.LeapMessageParser] - Received CommuniqueType: ReadResponse

2021-04-03 21:50:33.278 [TRACE] [rnal.protocol.leap.LeapMessageParser] - MessageBodyType: OneZoneStatus

2021-04-03 21:50:33.279 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone: 1 level: 25

2021-04-03 21:50:33.280 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone 1 mapped to device id 3

2021-04-03 21:50:33.282 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"CreateResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"201 Created","Url":"/zone/1/commandprocessor"},"Body":{"ZoneStatus":{"href":"/zone/1/status","Level":25,"Zone":{"href":"/zone/1"}}}}

2021-04-03 21:50:33.283 [DEBUG] [rnal.protocol.leap.LeapMessageParser] - Received CommuniqueType: CreateResponse

==> /var/log/openhab/events.log <==

2021-04-03 21:50:33.207 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Kitchen_HomeKit' received command ON

2021-04-03 21:50:33.220 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Kitchen_HomeKit' changed from OFF to ON

2021-04-03 21:50:33.226 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'kitchen_lights_leap' received command 25

2021-04-03 21:50:33.230 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'kitchen_lights_leap' predicted to become 25

2021-04-03 21:50:33.234 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'kitchen_lights_leap' changed from 0 to 25

2021-04-03 21:50:33.268 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'kitchen_lights' changed from 0.00 to 25.00

Pico → OpenHAB → Dimmer

==> /var/log/openhab/openhab.log <==

2021-04-03 21:47:10.389 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Received message ~DEVICE,21,4,3

2021-04-03 21:47:10.391 [TRACE] [n.internal.handler.BaseKeypadHandler] - Handling command DEVICE [4, 3] from keypad 21

2021-04-03 21:47:10.415 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Sending command #OUTPUT,15,1,0,5

2021-04-03 21:47:10.416 [TRACE] [ng.lutron.internal.net.TelnetSession] - TelnetSession writeLine called with #OUTPUT,15,1,0,5

2021-04-03 21:47:10.441 [TRACE] [rnal.protocol.leap.LeapMessageParser] - Received message: {"CommuniqueType":"ReadResponse","Header":{"MessageBodyType":"OneZoneStatus","StatusCode":"200 OK","Url":"/zone/3/status/level"},"Body":{"ZoneStatus":{"href":"/zone/3/status","Level":0,"Zone":{"href":"/zone/3"},"StatusAccuracy":"Good"}}}

2021-04-03 21:47:10.442 [DEBUG] [rnal.protocol.leap.LeapMessageParser] - Received CommuniqueType: ReadResponse

2021-04-03 21:47:10.443 [TRACE] [rnal.protocol.leap.LeapMessageParser] - MessageBodyType: OneZoneStatus

2021-04-03 21:47:10.444 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone: 3 level: 0

2021-04-03 21:47:10.445 [TRACE] [n.internal.handler.LeapBridgeHandler] - Zone 3 mapped to device id 17

2021-04-03 21:47:10.446 [DEBUG] [n.internal.handler.LeapBridgeHandler] - No thing configured for integration ID 17

2021-04-03 21:47:10.467 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Received message GNET> ~OUTPUT,15,1,0.00

2021-04-03 21:47:10.628 [DEBUG] [ron.internal.handler.IPBridgeHandler] - Received message ~DEVICE,21,4,4

2021-04-03 21:47:10.629 [TRACE] [n.internal.handler.BaseKeypadHandler] - Handling command DEVICE [4, 4] from keypad 21

==> /var/log/openhab/events.log <==

2021-04-03 21:47:10.395 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'officelights_cp_off' changed from OFF to ON

2021-04-03 21:47:10.397 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'officelights_cp_off' changed from ON to OFF

2021-04-03 21:47:10.405 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'living_light' received command OFF

2021-04-03 21:47:10.407 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'living_light' predicted to become OFF

2021-04-03 21:47:10.411 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'living_light' changed from 100.00 to 0

2021-04-03 21:47:18.310 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'TerrorBattery' changed from 95 to 96