FWIW, I do NOT have a Pro Bridge.
Iām having the exact same issues. I reset Lutron bridge to factory default, uninstalled/reinstalled certs via add-on, and even migrated from RP3 to VM, thinking it might be a RP3 issues. Nope, nothing fixes it. Iām about to do a fresh install, just to see if that fixes itā¦purely out of curiosity. At this point, I am beginning to think itās a Lutron issue.
Iām also suspicious that it has something to do with Lutron. Its infuriating because Iām all in on Casetaā¦ my entire house. I have no idea how to go about troubleshooting thisā¦ nothing shows up in the HA logs. Really hoping this gets addressed soon.
Hereās an update. I had the standard Caseta bridge, but purchased a Pro bridge last week so I can expose my PICO remotes to HomeKit using HomeBridge. I tried connecting the Pro bridge to Home Assistant, and it does correctly retain the device state. Granted, I have only migrated a couple of switches over to the Pro bridge. If I encounter the problem again after migrating more switches, Iāll post an update here.
Where did you buy the Pro bridge from? I was looking at the one on Amazon but saw reviews stating some were outdated.
I ordered through the Walmart website, but it was fulfilled through Energy Avenue: https://www.energyavenue.com/Lutron/L-BDGPRO2-WH
Interestingly, there was no shipping fee when I ordered through Walmart. But ordering directly through Energy Avenue I think youāll have to pay shipping. But still, cheapest price I could find. Good luck!
I am brand new to home assistant. Lutron Caseta was the second connection I made to my install and i am have the same issue. I have been a homekit user but started looking at HA for more automation and UI control. I have a standard install on a raspberry pi and a non pro hub.
Same problem here. Iāve manged to get things working for now through the SmartThings integration, but itās a bit of a kludge, plus the HA is local (I think) which I prefer. I am going to try a Pro Bridge and report back the results.
I bought a pro hub and it works perfectly now.
I bought a pro hub with high hopes, but unfortunately I am seeing the same behavior. The state is not maintained.
Soā¦ As I stated previously, my original problem was with the standard bridge. I purchased the Pro bridge and everything was great. I have been slowly migrating switches over to the Pro, and tonight I noticed that it stopped working with HA. I wonder if it has something to do with the number of devices attached to the bridge?
Could it be a Lutron firmware issue? Iād imagine that at some point the bridge, whether standard or pro, gets updates from Lutron and those updates are causing the breakage. The Pros that several people are getting are using older versions of the firmware and when yours updated, itās caused the break. Maybe the standard bridges got the push first. Just a wild a guess.
@Phillip_Sperry @BigMal and others with the same issueā¦ Do you happen to have the new Caseta fan controller switch? I realized that it stopped working after I added the fan controller. I disconnected the fan controller and it started working again. Might just be a coincidence, so I am wondering if the same is true for you.
Indeed! Iāll give that a shot and see what happens.
1 Like
Mike, I think you nailed it. I saw your comment and immediately removed the fan switch from the Caseta app. Restarted home assistant and states are reporting correctly. Thank you!
1 Like
Glad itās working! Lucky for me, I still have my standard bridge. So I will keep my fan controllers on there and everything else on the Pro until they fix the component.
Are you using the built-in Lutron Caseta component or the custom component?
Either way I would encourage you to submit a bug report for the component that you are using.
I know that the custom component has code for the new fan switch. I donāt know about the built-in component.
@MikeA Thanks for the suggestion. I actually did submit a bug report, but it seems to have been completely ignored by the devs. I am on the built-in component. What functionality does the custom component add? And dumb question - Why is there a separate custom component rather than adding the new functionality into the built in one?
On the custom componentās github page it says:
This component differs from the Lutron Caseta component in that it only works with the PRO model and uses the relatively well-documented (although still not officially supported) Telnet interface and the [Lutron Integration Protocol].
I do. Let me disconnect and I will report back.