search

gurumitts / pylutron-caseta

Apache License 2.0
153 stars 98 forks source link

Delay in state change for Caseta wall switch/dimmer #134

Open jerrm opened 1 year ago

jerrm commented 1 year ago

Posted this in HA core github (https://github.com/home-assistant/core/issues/82546), but it could be a problem here, or maybe just a Caseta limitation.

I have automations where actions are triggered by state change of a wired Caseta switch/dimmer.

There is about a 2 second delay for the HA state change when operated from the wired switch/dimmer.

The state change is virtually instant when the Caseta lights are turned on/off via a directly linked Pico or another automation.

sleepovr commented 1 year ago

I believe this is an intended function of the Lutron system. The light switch does not update it status until two or three seconds after the last press. I have been fighting this issue for awhile now and I have found no solution around it. Two test you can do to show that's it's on the Lutron side,

  1. Watch the state of the light in the Lutron app, when you turn a switch on the state in the app will not change for three seconds.
  2. If you turn the switch on fron the app your automation will run right away. ( You have actually proven this by using a pico) I am trying to get my hands on the RTI programming software to see if the Lutron approved driver has the same issue, but I believe it will based on how the app shows the delay.
dbaq commented 1 year ago

Any luck on that issue? is it a Caeta limitation? and if so, is there a way to submit feedback to the Lutron devs? it is a long shot but I don't mind trying.

sleepovr commented 1 year ago

It's not a Caseta limitation as I have the same issue in Ra3. I have gone around and around in circles with Lutron support for them to say Ra3 isn't designed for conditional programing. Their solution was to remove any programming that uses a switch state change for an automation trigger. If I wanted that capability I should have bought a Homeworks system.