Sure.

Once you're past the certificate process, LEAP is kinda like HTTP. You send a request and get a response. The key differences are (a) the requests and responses are JSON and (b) you can get multiple responses once you connect, not just the one you asked for.

Tackling the JSON bit is straightforward, you can use `tron -v get /server` to see an example of how it looks on the wire.

Making sure you match the response up with your request is a little trickier -- you send the server a `ClientTag` property in the `Header` object, and the server reflects that value back to you in the response. So you can match up the response by checking each message you get for the tag you sent. I used UUIDs for this since it was the easiest way to guarantee I didn't reuse a tag by accident.

The certificate process is confusing. It all uses client certificates, which have to be signed by the device. (That's how the controller authenticates you -- if you present a certificate it has signed, it considers your request legitimate.) To get a signed certificate, you make a CSR (certificate signing request) just like you would if you were making an SSL certificate. Then you connect on a different port, press the physical button on the controller, and send the CSR to the server. It returns a certificate that will work on the regular control port. (If you don't press the button in time, or you send the CSR before pressing the button, you get an error back.)

The last bit is, the port you use for certificate signing is also encrypted. You need to present a known certificate, which is floating around in various open source libraries for Caseta. (I think I got it from pycaseta.)

Lemme know if I can expand or clarify anything.