public/openhab-addons
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[nuki] Support for SmartLock 3.0 and SmartDoor (#12005)

Browse Source 
Signed-off-by: Jan Vybíral <jan.vybiral1@gmail.com>
This commit is contained in:
Jan Vybíral
2022-01-10 09:36:28 +01:00
committed by GitHub
parent bcb7b73191
commit dc0a974a98
8 changed files with 77 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
bundles/org.openhab.binding.nuki/src/main/resources/OH-INF/i18n/nuki.properties
View File

@@ -26,6 +26,8 @@ thing-type.config.nuki.bridge.secureToken.label = Secure Token
thing-type.config.nuki.bridge.secureToken.description = Use hashed token when communicating with bridge. This increases security and prevents sniffing of access token and replay attacks, since communication with bridge is not encrypted. For this feature to work, both device running openHAB and Nuki Bridge must have synchronized time. When disabled, token is sent in plain text with each bridge request. It is recommended that this is turned on unless there are problems with synchronizing time between openHAB and Nuki Bridge.
thing-type.config.nuki.opener.nukiId.label = Nuki ID
thing-type.config.nuki.opener.nukiId.description = The decimal string that identifies the Nuki Opener.
thing-type.config.nuki.smartlock.deviceType.label = Device Type
thing-type.config.nuki.smartlock.deviceType.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.
thing-type.config.nuki.smartlock.nukiId.label = Nuki ID
thing-type.config.nuki.smartlock.nukiId.description = The decimal string that identifies the Nuki Smart Lock.
thing-type.config.nuki.smartlock.unlatch.label = Unlatch
@@ -61,12 +63,14 @@ channel-type.nuki.smartLockBatteryCharging.state.option.OFF = Battery is not cha
channel-type.nuki.smartLockBatteryCharging.state.option.ON = Battery is charging
channel-type.nuki.smartlockDoorState.label = Door State
channel-type.nuki.smartlockDoorState.description = Use this channel to display the current state of the door sensor
channel-type.nuki.smartlockDoorState.state.option.0 = Unavailable
channel-type.nuki.smartlockDoorState.state.option.1 = Deactivated
channel-type.nuki.smartlockDoorState.state.option.2 = Closed
channel-type.nuki.smartlockDoorState.state.option.3 = Open
channel-type.nuki.smartlockDoorState.state.option.4 = Unknown
channel-type.nuki.smartlockDoorState.state.option.4 = Door state unknown
channel-type.nuki.smartlockDoorState.state.option.5 = Calibrating
channel-type.nuki.smartlockDoorState.state.option.16 = Uncalibrated
channel-type.nuki.smartlockDoorState.state.option.240 = Removed
channel-type.nuki.smartlockDoorState.state.option.255 = Unknown
channel-type.nuki.smartlockLock.label = Lock
channel-type.nuki.smartlockLock.description = Use this channel with a Switch Item to unlock and lock the door. Configure "Unlatch" to true if your Nuki Smart Lock is mounted on a door lock with a knob on the outside.
channel-type.nuki.smartlockLock.state.option.OFF = Unlocks the door

23
bundles/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>