OpenHAB
/
openhab-docs
mirror of https://github.com/openhab/openhab-docs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated external content (Jenkins build 727)

pull/1839/head
openHAB Build Server 2022-01-10 15:02:31 +00:00
parent b36a6a295c
commit 7d3aa05e24
5 changed files with 51 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
_addons_bindings/nuki/readme.md
View File

@ -72,7 +72,7 @@ connected to is configured and online.
### Nuki Smart Lock
The following configuration options are available:
This is a common thing for all Nuki smart lock products - Nuki Smart Lock 1.0/2.0/3.0 (Pro) and Nuki Smart Door. The following configuration options are available:
| Parameter | Description | Comment |
|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
@ -121,14 +121,16 @@ Unfortunately the Nuki Bridge is not reporting any transition states (e.g. for L
##### Supported doorSensorState values
| State | Name |
|--------|--------------------------|
| 0 | Unavailable |
| 1 | Deactivated |
| 2 | Closed |
| 3 | Open |
| 4 | Unknown |
| 5 | Calibrating |
| State | Name |
|-------|---------------------|
| 1 | Deactivated |
| 2 | Closed |
| 3 | Open |
| 4 | Door state unknonwn |
| 5 | Calibrating |
| 16 | Uncalibrated |
| 240 | Removed |
| 255 | Unknown |
### Nuki Opener
@ -190,7 +192,7 @@ A manual setup through files could look like this:
```
Bridge nuki:bridge:NB1 [ ip="192.168.0.50", port=8080, apiToken="myS3cr3t!", manageCallbacks=true ] {
Thing smartlock SL1 [ nukiId="12AB89EF", unlatch=false ]
Thing smartlock SL1 [ nukiId="12AB89EF", deviceType=0, unlatch=false ]
}
```

17
_addons_bindings/tesla/readme.md
View File

@ -42,7 +42,10 @@ Furthermore, once an account is configured, it is automatically queried for asso
The `account` bridge requires an OAuth2 refresh token as the only parameter `refreshToken`.
There are two different ways of obtaining the token:
There are three different ways of obtaining the token.
NOTE: Tesla has introduced some captcha mechanism, which might prevent options 1 and 2 from working as expected.
In case you are only receiving error messages, please make use of option 3!
1. Use the openHAB console
@ -65,6 +68,18 @@ If you do not want to use the openHAB console, you can also manually create a "T
openHAB will use the provided credentials to retrieve and set the refresh token and automatically delete your password from the configuration afterwards for safety reasons.
3. Use external tools
There are a few 3rd party tools available that have specialized on getting hold of refresh tokens for the Tesla API.
Please note that we in general consider it dangerous to enter your credentials into some 3rd party app - you will have to trust the author not to send or store those credentials anywhere.
- [Tesla Access Token Generator (Chromium Extension](https://github.com/DoctorMcKay/chromium-tesla-token-generator)
- [Auth App for Tesla (iOS)](https://apps.apple.com/us/app/auth-app-for-tesla/id1552058613)
- [Tesla Tokens (Android)](https://play.google.com/store/apps/details?id=net.leveugle.teslatokens)
When using one of such apps, simply copy and paste the received refresh token into the account configuration.
## Thing Configuration
The vehicle Thing requires the vehicle's VIN as a configuration parameter `vin`.

23
_thing_types/org.openhab.binding.nuki/src/main/resources/OH-INF/thing/thing-types.xml
View File

@ -92,6 +92,23 @@
<label>Nuki ID</label>
<description>The decimal string that identifies the Nuki Smart Lock.</description>
</parameter>
<parameter name="deviceType" type="integer" required="true" readOnly="true">
<label>Device Type</label>
<default>0</default>
<options>
<option value="0">Nuki Smart Lock 1.0/2.0</option>
<option value="3">Nuki Smart Door</option>
<option value="4">Nuki Smart Lock 3.0 (Pro)</option>
</options>
<description>
Numeric device type as specified by bridge HTTP API - 0 = Nuki Smart Lock 1.0/2.0, 3 = Nuki Smart Door,
4 = Nuki Smart Lock 3.0 (Pro).
Sent with each API request. Its purpose is not documented, seems to only be used for
distinguishing between opener and smartlock actions.
There does not seem to be any (documented or observable)
differences between different smart lock device types.
</description>
</parameter>
</config-description>
</thing-type>
@ -191,12 +208,14 @@
<category>Door</category>
<state readOnly="true">
<options>
<option value="0">Unavailable</option>
<option value="1">Deactivated</option>
<option value="2">Closed</option>
<option value="3">Open</option>
<option value="4">Unknown</option>
<option value="4">Door state unknown</option>
<option value="5">Calibrating</option>
<option value="16">Uncalibrated</option>
<option value="240">Removed</option>
<option value="255">Unknown</option>
</options>
</state>
<autoUpdatePolicy>veto</autoUpdatePolicy>

2
_thing_types/org.openhab.binding.tesla/src/main/resources/OH-INF/thing/account.xml
View File

@ -11,7 +11,7 @@
<config-description>
<parameter name="refreshToken" type="text" required="false">
<label>Refresh Token</label>
<description>Refresh token for account authentication. Use "smarthome:tesla" to retrieve it.</description>
<description>Refresh token for account authentication. Use "openhab:tesla" to retrieve it.</description>
</parameter>
<parameter name="username" type="text" required="false">
<advanced>true</advanced>

2
_thing_types/org.openhab.binding.tesla/src/main/resources/OH-INF/thing/channels.xml
View File

@ -119,7 +119,7 @@
<channel-type id="chargelimitsocstandard" advanced="true">
<item-type>Dimmer</item-type>
<label>Charge Limit SOC Standard</label>
<description>Standard charging limity of the vehicle, in %</description>
<description>Standard charging limit of the vehicle, in %</description>
<state pattern="%.1f %%" readOnly="true"></state>
</channel-type>
<channel-type id="chargeidealdistanceadded" advanced="true">