It appears that the Lutron Bridge Lutron Caseta L-BDGPRO2 is no longer available for purchase.
I purchased some in the past but now it appears that only the Lutron Caseta L-BDG2 is available and marketed as a “Hub” instead of “Bridge”, and does not have telnet support.
So is Caseta no longer compatible with Hubitat? Or is there another way to connect Hubitat with Caseta?
Thanks! I found and purchased two From City Electric supply. I was concerned because they do not appear as readily available as in the past and it appeared as though they are no longer being manufactured. I have a large home with two pro bridges now, and was needing to add a third for an accessory dwelling we built on the property. I wonder if it would be wise to keep a couple spares in the event of failure? I’m just confused about Lutron’s intentions….
They've always been harder to find than the "regular" Bridge, FWIW. Lutron considers it a "pro" product, per the name, and restricts sale to authorized dealers and distributors, not unlike RA2 Select. At a big box store, online or in person, you're more likely to find only regular Caséta, and even online, you'll normally have to look at a bit harder for that reason.
I wouldn't worry just yet. (But I am worried about the direction they're heading with Radio RA3 and where we might be years from now if this does get discontinued or replaced and they do something similar...)
According to ChatGPT the technical issue holding a Hubitat integration back is wss support. I understand why Hubitat the company doesn't want to create a reverse engineered integration, but that wouldn't be an issue for independent developers.
Secure Web Sockets. LEAP requires them. Here is what ChatGPT says about Hubitat's support:
Hubitat's support for secure WebSocket (WSS) connections is limited. While the platform provides methods to establish WebSocket connections, users have reported challenges when attempting to connect to secure WebSocket endpoints. Specifically, attempts to connect using wss:// URLs often result in errors, such as PKIX path building failures due to certificate validation issues.
In one instance, a user attempting to connect to a Samsung TV via a secure WebSocket encountered a PKIX exception, indicating difficulties with certificate validation. Another user reported being able to connect using ws:// (non-secure WebSocket) but faced issues with wss:// (secure WebSocket), even though the secure connection was verified using other tools.
These experiences suggest that while Hubitat's WebSocket interface is functional for non-secure connections, establishing secure WebSocket connections may not be fully supported or may require additional configuration to handle certificate validation properly. If you need to connect to a secure WebSocket endpoint, you might need to explore alternative methods or consult the Hubitat community for potential workarounds.
As I've come to understand it, it boils down to the fact that Lutron still has yet to officially bless LEAP as an openly supported protocol... Currently, it can be reverse-engineered (as Home Assistant is doing), and perhaps there was a time that Hubitat would've considered doing the same...
I realize it's maybe not quite apple-to-apples, but Hubitat did natively support Life360's not-really-fully-open API for a while. But between how that unfolded and the MyQ debacle (and other similar examples), I completely understand why Hubitat wants to keep native support all "above board" going forward.
It's very possible I've gotten all/some of these contentions wrong though -- I'm just a mope with no insider info or developer experience.
Right, as I said I understand the reasons for Hubitat not building an integration. I think the Life360 issue is exactly apples to apples. I'd love to see a 3rd party developer do it for Hubitat. There are working open source LEAP integrations in at least Home Assistant, Homebridge, OpenHAB.