New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lutron Caseta component works at startup but eventually fails #31361
Comments
Having the same issue. Lutron works at startup, but eventually stops works within a day. After restart, it works again. |
I have had the same issue the past couple of days. I had to restart HA but I haven't tried anything else. My Lutron Android App also just updated, so it is possible it is Lutron. |
I verified that this problem is still occurring on |
still having the same issue |
I am running 0.104.0 and since I restarted HA and cold booted the Lutron Caseta bridge 7 days ago, it has not happened. It would be interesting to understand from others what they did to fix it after the symptoms and how long it took the symptoms to come back. |
Correction. It just happened and I had to cold boot the lutron box and then restart HA. |
With 0.105.4, so far, the lutron connection has been stable. I don't think anything changed in 0.105.4 that would affect this, so maybe something changed in the lutron hub. Edits:
|
I am just adding my vote to this one, I have exactly the same symptoms. My "anecdotal report" is that I never saw this before the 0.100+ series. I've been running HA since about 0.83 and was using Lutron Integration from the beginning. I never had any problems until the last couple of months and going beyond 0.100. I don't know if the Lutron hub has been updating its version in the meantime. |
I too can verify I am having this issue with the last coupe of releases. Currently on 0.105.5 |
I'm also having this issue, considering ordering a pro hub just to switch to the custom component :/ |
I would also add, that when this happens, even the Lutron app appears to stop working, in that, if you open the app and try, it will seem like it doesn't work. For example, you turn a light off, the light stays on, but then, several minutes later it turns off...Its as if the hub is being flooded by home assistant and gets behind. However, as soon as you restart home assistant, the app starts responding instantly again. |
For me, this is not the case. When HA stops working with Lutron, I can still use Alexa, Google Assistant, and the Lutron Android app and they all continue working. |
Having the same issue as well. Updated Core and HassOS to 0.106.6 and 3.12. Once the Caseta lights stop working w/ Home Assistant, they also are flaky with the iOS Lutron app. Here's my stacktrace:
|
Hi, so this is still a problem for me, even on the 108 beta -- haven't seen any updates in nearly a month, and wondering when I'll be able to stop rebooting my HomeAssistant VM multiple times per day? |
It appears, based on work happening in the pylutron-caseta base library. that the devs are attempting to have this patched for the 0.108 release. The current 0.108.4 beta does not have the fix yet from what I can tell looking at github though. |
We are waiting on pylutron-caseta 0.6.1 to be released with this and another fix. Once it is, we can bump the required version in hass and close this issue as fixed. |
Sorry to re-open this, but I'm now having this exact issue. Same error messages and everything. |
I am also having this issue, just started out of the blue |
The problem
As documented in this thread the Lutron Caseta integration fails after several hours to days and can only be reset by restarting the Home Asssistant server, after which time the services work fine for an indeterminate period but ultimately will fail within a few hours to days of server uptime.
See the linked forum thread for more examples of other people with this problem.
Environment
Home Assistant release with the issue: 0.103 - 0.107.5
Last working Home Assistant release (if known):
0.102 (or maybe 0.101, I am not completely sure when it started.)
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io 3.8 on ODroid XU4
Integration causing this issue:
lutron_caseta
Link to integration documentation on our website:
https://www.home-assistant.io/integrations/lutron_caseta/
Problem-relevant
configuration.yaml
Traceback/Error logs
At startup, everything looks good:
Eventually some strange errors occur:
Subsequent calls to lutron caseta fail:
Additional information
Note that my Lutron configuration has been working for over a year, and it will briefly work again upon each restart of HASS. Restarting the Lutron bridge has no effect that I've noticed on this problem.
The text was updated successfully, but these errors were encountered: