Minimum changes to get Caseta Pro bridge working #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Lutron has a midrange system called Caseta Wireless that uses the same Clear Connect RF technology as RadioRA2, but it's dumbed down and sold directly to consumers. It uses the same Pico remotes, but the other system components are not interchangeable. The "Pro" version of the Caseta Bridge supports a subset of the Lutron integration protocol. Exactly what is supported isn't clear, as Lutron hasn't indicated any willingness to share specifications except with their partners. Regardless, simple device control and monitoring is possible.
This PR has the minimum changes required to get the Caseta Pro bridge working. Namely:
The Caseta Pro Bridge takes a very long time to present the login prompt after it accepts a TCP connection. (This could be cleaned up further by using a different timeout for the login sequence.)
The #MONITORING command is not supported: The GNET> prompt cannot be disabled, and network updates are always sent. Thus, upon startup there are five ~ERROR,6 messages.
Beyond these gotchas, basic functionality seems to work.
I'm willing to accept that you're likely not interested in compatibility with the Caseta system, but if you are, I'd be happy to submit further PR's as I work out more differences. Thanks!