@_Mike I only tested my code mods with a standard smart bridge and not the pro, so I am not sure what might be happening with the pro. My guess is that it is something similar: the responses from the pro smart bridge have probably changed in such a way that the underlying program (pylutron_caseta) is failing silently. It’s expecting a particular status response and receiving something entirely different. The fact that initial status is reported and that you can toggle it on/off means that you can make a communication and can send messages successfully. The problem, then, is still with the status updates.
I’m happy to to take a look at some logs. Someone with a pro bridge would just have to enable debug on the lutron_caseta component. The underlying program should debug the responses it receives from status requests. Those would tell you what’s up. Though it sounds like you might have this sorted with the cust component.
One of the problems we may encounter here is pylutron_caseta is not managed by HA bit was a separate library that it relied on. I don’t see any one really supporting that anymore (what’s published is really old). So even if we get to the bottom of this, we may still need to create a custom component. The HA models is built by using separate libraries so it’s unlikely that they take ownership.