demus/openhab-addons
1
0
Fork 0
mirror of https://github.com/openhab/openhab-addons.git synced 2025-01-25 14:55:55 +01:00
Code Issues Packages Projects Releases Wiki Activity

[lutron] update instructions for LEAP authentication (#16510)

Browse Source 
* [lutron] update instructions for LEAP authentication

Signed-off-by: Cody Cutrer <cody@cutrer.us>
This commit is contained in:
Cody Cutrer 2024-04-01 01:40:43 -06:00 committed by GitHub
parent 12660f1c26
commit ed5bb7d895
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 67 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

82
bundles/org.openhab.binding.lutron/doc/leapnotes.md
View File

@ -3,34 +3,86 @@
Unlike LIP, which was designed to use a simple serial or telnet connection and authenticates using a username/password, LEAP uses a SSL connection and authenticates using certificates. Unlike LIP, which was designed to use a simple serial or telnet connection and authenticates using a username/password, LEAP uses a SSL connection and authenticates using certificates.
This necessarily makes configuration more complicated. This necessarily makes configuration more complicated.
There are several open source utilities available for generating the certificate files necessary to access your Caseta or RA2 Select hub. There are several open source utilities available for generating the certificate files necessary to access your Caseta or RA2 Select hub.
One good choice is the get_lutron_cert.py script included with the popular pylutron library which is available on Github at https://github.com/gurumitts/pylutron-caseta . One good choice is included with the popular pylutron library which is available on Github at https://github.com/gurumitts/pylutron-caseta.
On a unix-like system, you can easily retrieve it using curl with a command like: On a Unix-like system, you can easily install it via `pip`:
``` ```bash
curl https://raw.githubusercontent.com/gurumitts/pylutron-caseta/dev/get_lutron_cert.py >get_lutron_cert.py $ pip install pylutron_caseta[cli]
Defaulting to user installation because normal site-packages is not writeable
Collecting pylutron_caseta[cli]
...
Installing collected packages: pylutron_caseta
Successfully installed pylutron_caseta-0.20.0
``` ```
Remember that the get_lutron_cert.py script must be run using python3, not 2! First, you need to locate your bridge using `leap-scan`:
Also, the script will prompt you to press the button on your smart hub to authorize key generation, so you should be somewhere near the hub when you run it. ```bash
Running it will not affect your existing hub configuration or Lutron app installations. $ leap-scan
Lutron-05701a1c.local. 192.168.1.10 fe80::5a2b:aee:ed11:c6d5
<Ctrl-C>
```
Then, you can pair with the found device using the address found above:
```bash
$ lap-pair Lutron-05701a1c.local. --cert caseta.crt --key caseta.key --cacert caseta-bridge.crt
Press the small black button on the back of the bridge to complete pairing.
Successfully paired with 1.119
```
Running this will not affect your existing hub configuration or Lutron app installations.
When it has completed, it will have generated three files: caseta.crt, caseta.key, and caseta-bridge.crt. When it has completed, it will have generated three files: caseta.crt, caseta.key, and caseta-bridge.crt.
Once the key and certificate files have been generated, you will need to load them into a java keystore. Once the key and certificate files have been generated, you will need to load them into a java keystore.
You can load a keystore from the key and certificate files on a Linux system with the following commands.
You can load a keystore from the key and certificate files on a linux system with the following commands.
You’ll need access to both the java keytool and openssl. You’ll need access to both the java keytool and openssl.
``` ```bash
openssl pkcs12 -export -in caseta.crt -inkey caseta.key -out caseta.p12 -name caseta $ openssl pkcs12 -export -in caseta.crt -inkey caseta.key -out caseta.p12 -name caseta
Enter Export Password:
Verifying - Enter Export Password:
$ keytool -importkeystore -destkeystore lutron.keystore -srckeystore caseta.p12 -srcstoretype PKCS12 -alias caseta
Importing keystore caseta.p12 to lutron.keystore...
Enter destination keystore password:
Re-enter new password:
Enter source keystore password:
$ keytool -importcert -file caseta-bridge.crt -keystore lutron.keystore -alias caseta-bridge
Enter keystore password:
Owner: CN=SmartBridge572B0A11C6D5, O="Lutron Electronics Co., Inc.", L=Coopersburg, ST=Pennsylvania, C=US
Issuer: CN=SmartBridge572B0A11C6D5, O="Lutron Electronics Co., Inc.", L=Coopersburg, ST=Pennsylvania, C=US
Serial number: 1
Valid from: Fri Oct 30 18:00:00 MDT 2015 until: Thu Oct 25 18:00:00 MDT 2035
Certificate fingerprints:
SHA1: 20:BE:07:23:0D:61:E7:EE:C4:17:C5:A2:6D:AB:85:0D:64:CF:2A:51
SHA256: C3:51:D0:C0:8C:15:7D:21:34:6F:B6:91:5E:0F:03:85:AB:06:DB:74:63:2D:7B:22:F2:1C:CB:12:7E:3C:29:E2
Signature algorithm name: SHA256withECDSA
Subject Public Key Algorithm: 256-bit EC (secp256r1) key
Version: 3
keytool -importkeystore -destkeystore lutron.keystore -srckeystore caseta.p12 -srcstoretype PKCS12 -srcstorepass secret -alias caseta Extensions:
keytool -importcert -file caseta-bridge.crt -keystore lutron.keystore -alias caseta-bridge #1: ObjectId: 2.5.29.19 Criticality=true
BasicConstraints:[
CA:true
PathLen: no limit
]
#2: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
DigitalSignature
Key_Encipherment
Data_Encipherment
Key_Agreement
Key_CertSign
Crl_Sign
]
Trust this certificate? [no]: yes
Certificate was added to keystore
``` ```
Respond to the password prompt(s) with a password, and then use that password in the -srcstorepass parameter of the keytool command and in the keystorePassword parameter for leapbridge. Respond to the password prompt(s) with a password.
In the example above, the pkcs12 store password was set to “secret”, but hopefully you can think of a better one!
The lutron.keystore file that you end up with is the one you’ll need to give the binding access to. The lutron.keystore file that you end up with is the one you’ll need to give the binding access to.
The caseta.p12 file is just an intermediate file that you can delete later. The caseta.p12 file is just an intermediate file that you can delete later.