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 2520)

final
openHAB Build Server 2025-03-03 05:50:30 +00:00
parent 39a7cdfd5c
commit 1593d99d22
34 changed files with 3214 additions and 120 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.vuepress/thing-types.json
View File

File diff suppressed because one or more lines are too long

100
_addons_bindings/casokitchen/readme.md Normal file
View File

@ -0,0 +1,100 @@
---
id: casokitchen
label: CasoKitchen
title: CasoKitchen - Bindings
type: binding
description: "Provides access towards CASO Smart Kitchen devices which are connected within the [CASO Control App](https://www.casocontrol.de/)."
since: 3x
install: auto
---
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
{% include base.html %}
# CasoKitchen Binding
Provides access towards CASO Smart Kitchen devices which are connected within the [CASO Control App](https://www.casocontrol.de/).
## Supported Things
- `winecooler-2z`: Wine cooler with two zones
## Discovery
There's no automatic discovery.
## Thing Configuration
You need a [CASO Account](https://www.casoapp.com/Account/Create) to get configuration parameters.
After register you'll get the
- API key
- Device ID
## Wine Cooler with 2 Zones
### Configuration winecooler-2z
| Name | Type | Description | Default |
|-----------------|---------|------------------------------------------------------|---------|
| apiKey | text | API obtained from thing configuration | N/A |
| deviceId | text | Device Id obtained from thing configuration | N/A |
| refreshInterval | integer | Interval the device is polled in minutes | 5 |
### Channels winecooler-2z
Channels are separated in 3 groups
- `generic` group covering states for the whole device
- `top` and `bottom` group covering states related to top or bottom zone
#### Generic Group
Group name `generic`.
| Channel | Type | Read/Write | Description |
|---------------|----------|------------|------------------------------|
| light-switch | Switch | RW | Control lights for all zones |
| last-update | DateTime | R | Date and Time of last update |
| hint | String | R | General command description |
#### Zone Groups
Group `top` and `bottom`.
The `set-temperature` channel is holding the desired temperature controlled via buttons on the wine cooler device.
Currently it cannot be changed using the API.
| Channel | Type | Read/Write | Description |
|------------------|-----------------------|------------|------------------------------|
| power | Switch | R | Zone Power |
| temperature | Number:Temperature | R | Current Zone Temperature |
| set-temperature | Number:Temperature | R | Desired Zone Temperature |
| light-switch | Switch | RW | Control lights for this zone |
## Full Example
### Thing Configuration
```java
Thing casokitchen:winecooler-2z:whiny "Whiny Wine Cooler" [ apiKey="ABC", deviceId="XYZ" ]
```
### Item Configuration
```java
Switch Whiny_Generic_LightSwitch {channel="casokitchen:winecooler-2z:whiny:generic#light-switch" }
DateTime Whiny_Generic_LastUpdate {channel="casokitchen:winecooler-2z:whiny:generic#last-update" }
String Whiny_Generic_Hint {channel="casokitchen:winecooler-2z:whiny:generic#hint" }
Switch Whiny_Top_Power {channel="casokitchen:winecooler-2z:whiny:top#power" }
Number:Temperature Whiny_Top_CurrentTemperature {channel="casokitchen:winecooler-2z:whiny:top#temperature" }
Number:Temperature Whiny_Top_DesiredTemperature {channel="casokitchen:winecooler-2z:whiny:top#set-temperature" }
Switch Whiny_Top_LightSwitch {channel="casokitchen:winecooler-2z:whiny:top#light-switch" }
Switch Whiny_Bottom_Power {channel="casokitchen:winecooler-2z:whiny:bottom#power" }
Number:Temperature Whiny_Bottom_CurrentTemperature {channel="casokitchen:winecooler-2z:whiny:bottom#temperature" }
Number:Temperature Whiny_Bottom_DesiredTemperature {channel="casokitchen:winecooler-2z:whiny:bottom#set-temperature" }
Switch Whiny_Bottom_LightSwitch {channel="casokitchen:winecooler-2z:whiny:bottom#light-switch" }
```

108
_addons_bindings/homewizard/readme.md
View File

@ -21,14 +21,21 @@ The HomeWizard binding provides access to several HomeWizard devices by using th
## Installation
There are two important points of attention: the local API of each device must be enabled and a fixed address must be configured for the devices.
There are two important points of attention:
### Local API
1. For API v1, the local API of each device must be enabled and a fixed address must be configured for the devices.
2. For API v2, a bearer token needs to be obtained from the device. See https://api-documentation.homewizard.com/ for instructions how to obtain a token.
### Local API v1
The local API of a device can be enabled from the HomeWizard app.
Go to Settings in the app, then Meters and select the device you want to enable.
On this page enable the local API.
### Local API v2
This version is still in beta. Currently hwe-p1 and hwe-bat are supported.
### Fixed Address
The devices support mDNS discovery but the binding does not support that yet.
@ -37,19 +44,24 @@ Since the devices themselves have no option to set a fixed IP address you will n
## Supported Things
The binding offers three Things, providing support for the P1 meter, the Watermeter and the Energy Socket.
The binding offers Things, providing access to all the supported HomeWizard devices.
| Thing | Device | Description |
|---------------|---------------------|-----------------------------------------------------------------------------------------------------|
| hwe-p1 | P1 Meter | Reads total and current energy usage and total gas usage (v1 and v2). |
| hwe-skt | Energy Socket | Reads total and current energy usage. Controls power switch, lock and ring brightness (v1). |
| hwe-wtr | Watermeter | Reads total and current water usage (v1). |
| hwe-kwh | kWh Meter | Reads total and current energy usage (v1). |
| hwe-bat | Plug-In Battery | Reads total and current energy usage and the current charge (v2). |
| p1_wifi_meter | Wi-Fi P1 Meter | [Deprecated] Reads total and current energy usage and total gas usage. |
| energy_socket | Wi-Fi Energy Socket | [Deprecated] Reads total and current energy usage. Controls power switch, lock and ring brightness. |
| watermeter | Wi-Fi Watermeter | [Deprecated] Reads total and current water usage. |
| Thing | Device | Description |
|---------------|---------------------|---------------------------------------------------------------------------------------------------|
| p1_wifi_meter | Wi-Fi P1 Meter | Reads total and current energy usage and total gas usage. |
| energy_socket | Wi-Fi Energy Socket | Reads total and current energy usage. Controls power switch, lock and ring brightness. |
| watermeter | Wi-Fi Watermeter | Reads total and current water usage. |
The HomeWizard kWh meters are not yet officially supported, but they can probably be added as as 'p1_wifi_meter'. However, this has not been tested.
## Discovery
Auto discovery is not yet available for this binding.
Auto discovery is not available for this binding.
## Thing Configuration
@ -59,54 +71,64 @@ All devices can be configured through the web interface.
|--------------|----------|---------|---------------------------------------------------------------------------------------------------|
| ipAddress | * | | This specifies the IP address (or host name) where the meter can be found. |
| refreshDelay | | 5 | This specifies the interval in seconds used by the binding to read updated values from the meter. |
| apiVersion | * | v1 | The API version to be used. v2 is still in beta but is already supported in this binding. |
| bearerToken | | | The bearer token to be used when using API v2. |
Note that update rate of the P1 Meter itself depends on the frequency of the telegrams it receives from the Smart Meter.
For DSMR5 meters this is generally once per second, for older versions the frequency is much lower.
## Channels
| Channel ID | Item Type | Description | Available |
|------------------------|---------------------------|--------------------------------------------------------------------------------------------|-----------|
| active_current | Number:ElectricCurrent | The combined current in A vor all phases | P,E |
| active_current_l1 | Number:ElectricCurrent | The active current in A for phase 1. | P |
| active_current_l2 | Number:ElectricCurrent | The active current in A for phase 2. | P |
| active_current_l3 | Number:ElectricCurrent | The active current in A for phase 3. | P |
| active_power | Number:Power | The current net total power in W. It will be below 0 if power is currently being exported. | P,E |
| active_power_l1 | Number:Power | The current net total power in W for phase 1. | P |
| active_power_l2 | Number:Power | The current net total power in W for phase 2. | P |
| active_power_l3 | Number:Power | The current net total power in W for phase 3. | P |
| active_voltage | Number:ElectricPotential | The active voltage in V | P |
| active_voltage_l1 | Number:ElectricPotential | The active voltage in V for phase 1. | P |
| active_voltage_l2 | Number:ElectricPotential | The active voltage in V for phase 2. | P |
| active_voltage_l3 | Number:ElectricPotential | The active voltage in V for phase 3. | P |
| total_energy_import_t1 | Number:Energy | The most recently reported total imported energy in kWh by counter 1. | P,E |
| total_energy_import_t2 | Number:Energy | The most recently reported total imported energy in kWh by counter 2. | P |
| total_energy_export_t1 | Number:Energy | The most recently reported total exported energy in kWh by counter 1. | P,E |
| total_energy_export_t2 | Number:Energy | The most recently reported total exported energy in kWh by counter 2. | P |
| total_gas | Number:Volume | The most recently reported total imported gas in m^3. | P |
| gas_timestamp | DateTime | The time stamp of the total_gas measurement. | P |
| total_water | Number:Volume | Total water used. | W |
| current_water | Number:VolumetricFlowRate | Current water usage. | W |
| power_failures | Number | The count of long power failures. | P |
| long_power_failures | Number | the count of any power failures. | P |
| power_switch | Switch | Controls the power switch of the socket. | E |
| power_lock | Switch | Controls the lock of the power switch (un/locking both the API and the physical button) | E |
| ring_brightness | Number:Dimensionless | Controls the brightness of the ring on the socket | E |
| Channel ID | Item Type | Description | Available |
|------------------------|---------------------------|--------------------------------------------------------------------------------------------|-----------------------------------|
| power | Number:Power | This channel provides the active usage in Watt. | hwe-p1, hwe-skt, hwe-kwh, hwe-bat |
| power_l1 | Number:Power | This channel provides the active usage for phase 1 in Watt. | hwe-p1, hwe-kwh |
| power_l2 | Number:Power | This channel provides the active usage for phase 2 in Watt. | hwe-p1, hwe-kwh |
| power_l3 | Number:Power | This channel provides the active usage for phase 3 in Watt. | hwe-p1, hwe-kwh |
| voltage | Number:ElectricPotential | This channel provides the active voltage in Volt. | hwe-skt |
| voltage_l1 | Number:ElectricPotential | This channel provides the active usage for phase 1 in Watt. | hwe-p1, hwe-kwh, hwe-bat |
| voltage_l2 | Number:ElectricPotential | This channel provides the active usage for phase 2 in Watt. | hwe-p1, hwe-kwh |
| voltage_l3 | Number:ElectricPotential | This channel provides the active usage for phase 3 in Watt. | hwe-p1, hwe-kwh |
| current | Number:ElectricCurrent | This channel provides the active current in Ampere. | hwe-skt, hwe-kwh, hwe-bat |
| current_l1 | Number:ElectricCurrent | This channel provides the active current for phase 1 in Ampere. | hwe-p1, hwe-kwh |
| current_l2 | Number:ElectricCurrent | This channel provides the active current for phase 2 in Ampere. | hwe-p1, hwe-kwh |
| current_l3 | Number:ElectricCurrent | This channel provides the active current for phase 3 in Ampere. | hwe-p1, hwe-kwh |
| energy_import | Number:Energy | This channel provides the total energy usage meter reading in kWh. | hwe-p1, hwe-skt, hwe-kwh, hwe-bat |
| energy_import_t1 | Number:Energy | This channel provides the energy usage meter reading for tariff 1 in kWh. | hwe-p1 |
| energy_import_t2 | Number:Energy | This channel provides the energy usage meter reading for tariff 2 in kWh. | hwe-p1 |
| energy_export | Number:Energy | This channel provides the total energy feed-in meter reading in kWh. | hwe-p1, hwe-skt, hwe-kwh, hwe-bat |
| energy_export_t1 | Number:Energy | This channel provides the energy feed-in meter reading for tarff 1 in kWh. | hwe-p1 |
| energy_export_t2 | Number:Energy | This channel provides the energy feed-in meter reading for tarff 2 in kWh. | hwe-p1 |
| reactive_power | Number | This channel provides the active reactive power in Volt-Ampere reactive. | hwe-p1, hwe-skt, hwe-kwh |
| apparent_power | Number | This channel provides the active apparent power in Volt-Ampere. | hwe-p1, hwe-skt, hwe-kwh |
| power_factor | Number:Dimensionless | This channel provides the active power factor. | hwe-p1, hwe-skt, hwe-kwh |
| frequency | Number:Frequency | This channel provides the active frequency in Hertz. | hwe-p1, hwe-skt, hwe-kwh, hwe-bat |
| total_gas | Number:Volume | This channel provides the most recently reported total imported gas in m^3. | hwe-p1 |
| gas_timestamp | DateTime | This channel provides the time stamp of the total_gas measurement. | hwe-p1 |
| power_failures | Number | This channel provides the number of power failures detected by meter. | hwe-p1 |
| long_power_failures | Number | This channel provides the number of 'long' power failures detected by meter. | hwe-p1 |
| power_switch | Switch | This channel provides access to the power switch of the Energy Socket. | hwe-skt |
| power_lock | Switch | This channel provides access to the power lock of the Energy Socket. | hwe-skt |
| ring_brightness | Number:Dimensionless | This channel provides access to the brightness of the ring of the Energy Socket. | hwe-skt |
| total_liter | Number:Volume | This channel provides total water usage in cubic meters. | hwe-wtr |
| active_liter | Number:VolumetricFlowRate | This channel provides the active water usage in liters per minute. | hwe-wtr |
| state_of_charge | Number:Dimensionless | This channel provides access to the current state of charge in percent. | hwe-bat |
| cycles | Number:Dimensionless | This channel provides access to the number of battery cycles. | hwe-bat |
## Full Example
### `homewizard.things` Example
```java
Thing homewizard:p1_wifi_meter:my_p1 [ ipAddress="192.178.1.67", refreshDelay=5 ]
Thing homewizard:energy_socket:my_socket [ ipAddress="192.178.1.61", refreshDelay=5 ]
Thing homewizard:watermeter:my_water [ ipAddress="192.178.1.27", refreshDelay=15 ]
Thing homewizard:hwe-p1:my_p1 [ ipAddress="192.178.1.67", refreshDelay=5, apiVersion=1 ]
Thing homewizard:hwe-skt:my_socket [ ipAddress="192.178.1.61", refreshDelay=5, apiVersion=1 ]
Thing homewizard:hwe-wtr:my_water [ ipAddress="192.178.1.27", refreshDelay=15, apiVersion=1 ]
```
### `homewizard.items` Example
```java
Number:Energy Energy_Import_T1 "Imported Energy T1 [%.0f kWh]" {channel="homewizard:p1_wifi_meter:my_meter:total_energy_import_t1" }
Number:Power Active_Power_L1 "Active Power Phase 1 [%.1f W]" {channel="homewizard:p1_wifi_meter:my_meter:active_power_l1" }
DateTime Gas_Update "Gas Update Time [%1$tH:%1$tM]" {channel="homewizard:p1_wifi_meter:my_meter:gas_timestamp" }
Number:Energy Energy_Import_T1 "Imported Energy T1 [%.0f kWh]" {channel="homewizard:hwe-p1:my_meter:energy#energy_import_t1" }
Number:Power Active_Power_L1 "Active Power Phase 1 [%.1f W]" {channel="homewizard:hwe-p1:my_meter:energy#power_l1" }
DateTime Gas_Update "Gas Update Time [%1$tH:%1$tM]" {channel="homewizard:hwe-p1:my_meter:energy#gas_timestamp" }
```

75
_addons_bindings/insteon/readme.md
View File

@ -594,6 +594,81 @@ Usage: openhab:insteon debug - Insteon debug commands
</details>
### Modem Commands
```shell
openhab> insteon modem
Usage: openhab:insteon modem listAll - list configured Insteon modem bridges with related channels and status
Usage: openhab:insteon modem listDatabase [--records] - list all-link database summary or records and pending changes for the Insteon modem
Usage: openhab:insteon modem listFeatures - list features for the Insteon modem
Usage: openhab:insteon modem listProductData - list product data for the Insteon modem
Usage: openhab:insteon modem reloadDatabase - reload all-link database from the Insteon modem
Usage: openhab:insteon modem backupDatabase - backup all-link database from the Insteon modem to a file
Usage: openhab:insteon modem restoreDatabase <filename> --confirm - restore all-link database to the Insteon modem from a specific file
Usage: openhab:insteon modem addDatabaseController <address> <group> [<devCat> <subCat> <firmware>] - add a controller record to all-link database for the Insteon modem
Usage: openhab:insteon modem addDatabaseResponder <address> <group> - add a responder record to all-link database for the Insteon modem
Usage: openhab:insteon modem deleteDatabaseRecord <address> <group> - delete a controller/responder record from all-link database for the Insteon modem
Usage: openhab:insteon modem applyDatabaseChanges --confirm - apply all-link database pending changes for the Insteon modem
Usage: openhab:insteon modem clearDatabaseChanges - clear all-link database pending changes for the Insteon modem
Usage: openhab:insteon modem addDevice [<address>] - add an Insteon device to the modem, optionally providing its address
Usage: openhab:insteon modem removeDevice <address> [--force] - remove an Insteon device from the modem
Usage: openhab:insteon modem reset --confirm - reset the Insteon modem to factory defaults
Usage: openhab:insteon modem switch <thingId> - switch Insteon modem bridge to use if more than one configured and enabled
```
### Device Commands
```shell
openhab> insteon device
Usage: openhab:insteon device listAll - list configured Insteon/X10 devices with related channels and status
Usage: openhab:insteon device listDatabase <thingId> - list all-link database records and pending changes for a configured Insteon device
Usage: openhab:insteon device listFeatures <thingId> - list features for a configured Insteon/X10 device
Usage: openhab:insteon device listProductData <thingId> - list product data for a configured Insteon/X10 device
Usage: openhab:insteon device listMissingLinks --all|<thingId> - list missing links for a specific or all configured Insteon devices
Usage: openhab:insteon device addMissingLinks --all|<thingId> - add missing links for a specific or all configured Insteon devices
Usage: openhab:insteon device addDatabaseController <thingId> <address> <group> <data1> <data2> <data3> - add a controller record to all-link database for a configured Insteon device
Usage: openhab:insteon device addDatabaseResponder <thingId> <address> <group> <data1> <data2> <data3> - add a responder record to all-link database for a configured Insteon device
Usage: openhab:insteon device deleteDatabaseController <thingId> <address> <group> <data3> - delete a controller record from all-link database for a configured Insteon device
Usage: openhab:insteon device deleteDatabaseResponder <thingId> <address> <group> <data3> - delete a responder record from all-link database for a configured Insteon device
Usage: openhab:insteon device applyDatabaseChanges <thingId> --confirm - apply all-link database pending changes for a configured Insteon device
Usage: openhab:insteon device clearDatabaseChanges <thingId> - clear all-link database pending changes for a configured Insteon device
Usage: openhab:insteon device setButtonRadioGroup <thingId> <button1> <button2> [<button3> ... <button7>] - set a button radio group for a configured Insteon KeypadLinc device
Usage: openhab:insteon device clearButtonRadioGroup <thingId> <button1> <button2> [<button3> ... <button7>] - clear a button radio group for a configured Insteon KeypadLinc device
Usage: openhab:insteon device refresh --all|<thingId> - refresh data for a specific or all configured Insteon devices
```
### Scene Commands
```shell
openhab> insteon scene
Usage: openhab:insteon scene listAll - list configured Insteon scenes with related channels and status
Usage: openhab:insteon scene listDetails <thingId> - list details for a configured Insteon scene
Usage: openhab:insteon scene addDevice --new|<scene> <device> <feature> <onLevel> [<rampRate>] - add an Insteon device feature to a new or configured Insteon scene
Usage: openhab:insteon scene removeDevice <scene> <device> <feature> - remove an Insteon device feature from a configured Insteon scene
```
### Channel Commands
```shell
openhab> insteon channel
Usage: openhab:insteon channel listAll - list available channel ids with configuration and link state
```
### Debug Commands
```shell
openhab> insteon debug
Usage: openhab:insteon debug listMonitored - list monitored Insteon/X10 device(s)
Usage: openhab:insteon debug startMonitoring --all|<address> - start logging message events for Insteon/X10 device(s) in separate file(s)
Usage: openhab:insteon debug stopMonitoring --all|<address> - stop logging message events for Insteon/X10 device(s) in separate file(s)
Usage: openhab:insteon debug sendBroadcastMessage <group> <cmd1> <cmd2> - send an Insteon broadcast message to a group
Usage: openhab:insteon debug sendStandardMessage <address> <cmd1> <cmd2> - send an Insteon standard message to a device
Usage: openhab:insteon debug sendExtendedMessage <address> <cmd1> <cmd2> [<data1> ... <data13>] - send an Insteon extended message with standard crc to a device
Usage: openhab:insteon debug sendExtended2Message <address> <cmd1> <cmd2> [<data1> ... <data12>] - send an Insteon extended message with a two-byte crc to a device
Usage: openhab:insteon debug sendX10Message <address> <cmd> - send an X10 message to a device
Usage: openhab:insteon debug sendIMMessage <name> [<data1> <data2> ...] - send an IM message to the modem
```
## Insteon Groups and Scenes
How do Insteon devices tell other devices on the network that their state has changed? They send out a broadcast message, labeled with a specific _group_ number.

2
_addons_bindings/jablotron/readme.md
View File

@ -66,7 +66,7 @@ Binding itself doesn't require specific configuration.
| JA-80/JA-100/JA-100F | lastEventTime | DateTime | the time of the last event |
| JA-80/JA-100/JA-100F | lastCheckTime | DateTime | the time of the last checking |
| JA-80/JA-100/JA-100F | alarm | N/A | the alarm trigger, might fire ALARM or TAMPER events |
| JA-100/JA-100F | lastEventSection | String | the section of the last event |
| JA-80/JA-100/JA-100F | lastEventSection | String | the section of the last event |
| JA-100 | state_%nr% | String | the section %nr% status/control |
| JA-100 | pgm_%nr% | Switch | the PG switch %nr% status/control |
| JA-100 | thermometer_%nr% | Number:Temperature | the thermometer %nr% value |

69
_addons_bindings/lgtvserial/readme.md
View File

@ -26,7 +26,18 @@ See below for a list of supported channels.
Supports one TV, monitor or projector per thing, also corresponding to a unique serial port.
The protocol supports daisy-chaining of serial devices.
The LG serial command set appears to be similar on many models ([1], [5]), but not all commands will work on all models.
This binding supports the following thing types:
| Thing ID | Description |
|-------------------|-------------------------------------------------------------------------------------------------------|
| lgtv | Generic LG TV thing. This thing should be used when there is no proper thing defined for your device. |
| lgtv-LV-series | This thing supports the LED LCD TV models LV and LW except *LV255C, *LV355B, *LV355C |
| lgtv-LVx55-series | This thing supports the *LV255C, *LV355B, *LV355C models |
| lgtv-LK-series | This thing supports the LCD TV models LK |
| lgtv-PW-series | This thing supports the PLASMA TV models PW |
| lgtv-M6503C | This thing supports the M6503C monitor |
The LG serial command set appears to be similar on many models ([\[1\]](#ref1), [\[5\]](#ref5)), but not all commands will work on all models.
The control port on most TVs is a male DE-9 connector that requires a "Null modem" cable to connect to a serial port or USB to serial adapter.
@ -64,7 +75,7 @@ However, the item values for the Thing with Set ID 0 will never display the righ
## Channels
The following channels are common to most TVs, taken from [4].
The following channels are common to most TVs, taken from [\[4\]](#ref4).
| Channel ID | Command | Item Type | Description |
|-----------------|---------|-----------|--------------------------------------------------|
@ -74,7 +85,7 @@ The following channels are common to most TVs, taken from [4].
| volume-mute | k e | Switch | Set mute on or off |
As for others, please refer to the documentation of your device in the section named "Controlling the multiple product", "External control" or any section that refers to RS-232.
If your device documentation doesn't give such information, you can look at the "LG protocol references" below and use the "Generic LG TV" thing which should contain all the different possible channels/commands.
If your device documentation doesn't give such information, you can refer to the [LG protocol references](#lg-protocol-references) below and use the "Generic LG TV" thing which should contain all the different possible channels/commands.
Note: Devices might not respond or return an error to some command when the device is powered off which can put items in an incorrect state until the device is turned on.
For instance, getting the volume status when the device is off makes no sense.
@ -143,30 +154,50 @@ The following commands/channels are not currently implemented in the binding but
| Channel ID | Command | Description
|--------------------|---------|------------------------------------------------------------------------------------------------------------|
| abnormal-state | k z | Used to read the power off status when in Stand-by mode |
| auto-configuration | j u | To adjust picture position and minimize image shaking automatically. it works only in RGB(PC) mode. |
| power-on-delay | f h | Set the schedule delay when the power is turned on (Unit: second) |
| remote-lock | k m | To control Remote Lock on/off to the set. Locks the remote control and the local keys. |
| reset | f k | Execute the Picture, Screen and Factory Reset functions |
| scheduled-input | f u | To select input source for TV depending on day |
| time | f a | Set the current time |
| on-timer-on-off | f b | Set days for On Timer |
| off-timer-on-off | f c | Set days for Off Timer |
| on-timer-time | f d | Set On Timer |
| off-timer-time | f e | Set Off Timer |
| h-size | f s | Set the Horizontal size, from 0 to 100 |
| v-size | f t | Set the Vertical size, from 0 to 100 |
| abnormal-state | k z | To read the power off status when in Stand-by mode |
| auto-configuration | j u | To adjust picture position and minimize image shaking automatically. Works only in RGB(PC) mode. |
| power-on-delay | f h | To set the schedule delay when the power is turned on (Unit: second) |
| remote-lock | k m | To turn the Remote Lock on or off. Locks the remote control and the local keys. |
| reset | f k | To execute the Picture, Screen and Factory Reset functions |
| scheduled-input | f u | To select input source for the TV depending on day |
| time | f a | To set the current time |
| on-timer-on-off | f b | To set the days for the On Timer |
| off-timer-on-off | f c | To set the days for the Off Timer |
| on-timer-time | f d | To set the On Timer |
| off-timer-time | f e | To set the Off Timer |
| h-size | f s | To set the Horizontal size, from 0 to 100 |
| v-size | f t | To set the Vertical size, from 0 to 100 |
### Using `raw` channel via rules Example
```java
// Rule to toggle the Remote Control Lock mode using a virtual switch item
rule "LGTV Remote Lock toggle"
when
Item LgRemoteLock received command
then
// Send raw command to toggle Remote Lock
// command: km, setId: 01, data: 01/00 (on/off)
if (receivedCommand == ON) {
Generic_LG_TV_Raw.sendCommand("km 01 01")
} else {
Generic_LG_TV_Raw.sendCommand("km 01 00")
}
end
```
## LG protocol references
[1] Manual for M6503C monitor <https://gscs-b2c.lge.com/downloadFile?fileId=KROWM000237239.pdf>
[1] Manual for M6503C monitor <https://gscs-b2c.lge.com/downloadFile?fileId=KROWM000237239.pdf><a name="ref1"/>
[2] <https://sites.google.com/site/brendanrobert/projects/bits-and-pieces/lg-tv-hacks>
[3] <https://code.google.com/archive/p/lg-tv-command/source/default/source>
[4] <https://github.com/suan/libLGTV_serial>
[4] <https://github.com/suan/libLGTV_serial><a name="ref4"/>
[5] Manual for LV series, LK series, PW series and PZ series <https://gscs-b2c.lge.com/downloadFile?fileId=ujpO8yH69djwNZzwuavqpQ>
[5] Manual for LV series, LK series, PW series and PZ series <https://gscs-b2c.lge.com/downloadFile?fileId=ujpO8yH69djwNZzwuavqpQ><a name="ref5"/>
[6] Manual for LD series, LE series, LX series and PK series <https://gscs-b2c.lge.com/downloadFile?fileId=76If0tKDLOUizuoXikllgQ>

257
_addons_bindings/senseenergy/readme.md Normal file
View File

@ -0,0 +1,257 @@
---
id: senseenergy
label: SenseEnergy
title: SenseEnergy - Bindings
type: binding
description: "This binding supports the Sense Energy monitor (sense.com) which can be used to provide accurate energy usage statistics in the home."
since: 3x
install: auto
---
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
{% include base.html %}
# SenseEnergy Binding
This binding supports the Sense Energy monitor (sense.com) which can be used to provide accurate energy usage statistics in the home.
In addition to providing real-time and historical energy production and usage data, Sense also uses machine learning to predict specific device usage.
This binding interfaces with the Sense cloud and local monitor to provide openHAB real-time energy updates for the whole house and any known devices.
Note, the binding currently assumes (and the configuration tested) that the monitor is installed in a solar enabled configuration.
If you have a device in a different configuration, feedback would be welcome and support might be added to the binding.
Sense also allows smart plugs and other devices to provide real-time usage allowing Sense to incorporate accurate usage statistics into your data.
This binding also supports creation of virtual proxy devices in openHAB which can send to Sense any energy usage for openHAB aware devices.
Here are several examples of how a virtual proxy device can be used:
- A pool pump known in openHAB can update its power when on to Sense
- A switch or dimmer where the power is known can get send to Sense when on.
- A fan / scene represented as a String can be used to notify Sense of the power usage when a particualar scene is on.
Using the openHAB follow profile with the channel(s) of the proxy device is an easy way to link these proxy devices to your openHAB setup. (see examples)
This binding builds off the following works in understanding the Sense API:
- https://github.com/scottbonline/sense
- https://github.com/cbpowell/SenseLink/
## Supported Things
| Thing Id | Label | Type | Description |
|------------------|------------------------------|--------|--------------------------------------------------------------------|
| cloud-connector | Sense Energy Cloud Connector | Bridge | This represents the cloud account to interface with the Sense Ener |
| monitor | Sense Monitor Device | Bridge | This interfaces to a specific Sense energy monitor associated with |
| proxy-device | Virtual Device Emulation | Device | This is a proxy device used to provide real-time usage to Sense. |
## Discovery
Initial configurtion involes creating a cloud-connector device with the email and password for the Sense cloud account.
Once the cloud-connector has been created and initialized, the monitor(s) associated with the account will be auto-discovered.
Virtual proxy devices are created manually attached to the monitor bridge.
## Thing Configuration
### Sense Energy Cloud Connector
The `cloud-connector` is configured with the email and password for your Sense Energy cloud account.
At present, the binding does not support multi-factor authentication which should be disabled via the Sense app settings.
| Name | Type | Description | Default | Required | Advanced |
|----------|------|--------------------------------------|---------|----------|----------|
| email | text | email for the Sense cloud account | N/A | yes | no |
| password | text | Password for the Sense cloud account | N/A | yes | no |
### Sense Monitor Device
The monitor will be auto-discovered after the `cloud-connector` bridge goes online.
The only configuration parameter is the id, however, this is not available via the Sense app or sense.com.
When supporting textual configuration, you can monitor the openhab.log in order to see the id for your monitor device.
| Name | Type | Description | Default | Required | Advanced |
|------|---------|---------------------------|---------|----------|----------|
| id | integer | ID for the monitor device | N/A | yes | no |
### Virtual Proxy Device Emulation
Virtual proxy devices can be created in order to notify Sense of specific power usage of devices in your home.
These emulate a TP-Link Kasa HS110 smart plug and will report to Sense the power usage based on on the configuration of the proxy device and the state.
In order to use, you need to enable "TP-Link HS110/HS300 Smart Plug" in the Sense app.
| Name | Type | Description | Default | Required | Advanced |
|-------------|-----------------|-----------------------------------------------|---------|----------|----------|
| powerLevels | text | Power levels for different states. | N/A | no | no |
| voltage | decimal | Voltage level for the proxy device. | 120 | yes | no |
| mac | network-address | A spoof'ed MAC address for this proxy device. | random | no | yes |
#### Power Levels
The power levels is a list representing different power levels or states of the device.
Here are several examples of how this can be configured:
| powerLevel parameter | Description | Example Device |
|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|
| 10 W | The device is a simple ON/OFF switch or Dimmer with 0 W in the OFF or 0% state, and 10 W in the full ON or 100% state. For a dimmer, the power will be linearly interpolated over the full range [0 W, 10 W] depending on current dim level. | Light |
| 800 mW,10 W | The device is a simple ON/OFF switch or Dimmer with 800 mW in the OFF or 0% state, and 10 W in the full ON or 100% state. For a dimmer, the power will be linearly interpolated over the full range [800 mW, 10 W] depending on current dim level. | TV which standby power > 0 W |
| 0 W,1 W,3 W,8 W, 15 W | A device which has non-linear power usage at different dim levels. This configuration would use 0 W at 0%, 1 W at 25%, 3 W at 50%, 8 W at 75% and 15 W at the full 100%. Other levels are linearly interpolated within the bounding points of the sub-range. | Dimmable light with non-linear usage profile |
| OFF=0 W,LOW=200 W,HIGH=400 W | A device with several power states with different power levels in state represented by a String. | A fan with OFF, LOW, HIGH states |
#### MAC
Each proxy device must be configured with a MAC address.
The virtual device creates a random MAC address which is used in identification of the device to Sense.
Note, if configuring via the textual interace, it is important to provide the MAC field, otherwise a different MAC address will be randomized whenever openHAB restarts and the proxy device will appear as a new additional device to Sense.
## Channels
### Cloud-Connector
There are no channels associated with the cloud-connector bridge.
### Monitor
The monitor channels are organized into multiple groups.
#### General Channel Group
| Channel Id | Label | Type | Read/Write | Description |
|-------------|-------------|----------------------------|------------|---------------------------------------------------------------------------------|
| frequency | Frequency | Number:Frequency | R | Electrical frequency detected by Sense. |
| grid-power | Grid Power | Number:Power | R | Power consumed from the grid (negative if supplying power to grid). |
| potential-1 | Potential 1 | Number:ElectricalPotential | R | Potential measured on first 120V branch. |
| potential-2 | Potential 2 | Number:ElectricalPotential | R | Potential measured on second 120V branch. |
| main-power | Main Power | Number:Power | R | Power detected by the main Sense clamp (only present in solar mode). |
| solar-power | Solar Power | Number:Power | R | Power detected by the solar Sense clamp (only present in solar mode). |
| leg-1-power | Leg 1 Power | Number:Power | R | Power detected by the first Sense clamp (only present when not in solar mode). |
| leg-2-power | Leg 2 Power | Number:Power | R | Power detected by the second Sense clamp (only present when not in solar mode). |
#### Discovered Devices, Self-Reporting Devices and Proxy Devices Channel Groups
- Discovered devices are those which Sense has discovered using their algorithms.
- Self-reporting devices are any devices which report their power usage to Sense (i.e. energy reporting smart plugs).
- Proxy devices are any virtual proxy devices set up in openHAB where this binding reports their power usage.
| Channel | id | Type | Read/Write | Advanced | Description |
|-------------------------|-------------------|--------------|------------|----------|------------------------------------------------------------------|
| *Label*: Power | *id*-device-power | Number:Power | R | N | Power consumed by the device. |
| *Label*: On Off Trigger | *id*-trigger | Trigger | N/A | Y | Trigger channel to notify when device has been turned ON or OFF. |
### Proxy Device
Each proxy device has several channels that can be used to notify Sense of the current power usage for the device.
These can either attached to an openHAB item, or, can be used with the system:follow profile to follow the state of another channel (see example).
| Channel | id | Type | Read/Write | Description |
|---------- |-------- |-------- |-------- |--------------- |
| Power Level | proxy-device-power | Number:Power | W | Sets a specific absolute real-time power usage for the device. |
| Device Switch | proxy-device-switch | Switch | W | Sets the power level to either the ON or OFF defined in the powerLevels parameter. |
| Device Dimmer | proxy-device-dimmer | Dimmer | W | Sets the power level to an interpolated value based on the powerLevels parameter. |
| Device State | proxy-device-state | String | W | Sets the power level to the state sepecifice in the powerLevels parameter. |
## Full Example
### `demo.things` Example
```java
Bridge senseenergy:cloud-connector:cloud [ email="xxx", password="xxx" ] {
Bridge monitor monitor1 [ id=869850 ] {
Thing proxy-device poolpump "Sense Virtual Pool Pump"
Thing proxy-device light "Sense Virtual Light" [ powerLevels="20 W" ]
Thing proxy-device fan "Sense Virtual Fan" [ powerLevels="OFF=0 W,LOW=10 W, HIGH=20 W" ]
}
}
```
### `demo.items` Example
```java
// General channels
Number:Frequency Main_Frequency "Main Frequency" { channel="senseenergy:monitor:cloud:monitor1:general#frequency" }
Number:Power To_Grid_Power "To Grid Power" { channel="senseenergy:monitor:cloud:monitor1:general#grid-power" }
Number:ElectricPotential Branch_1_Potential "Branch 1 Potential" { channel="senseenergy:monitor:cloud:monitor1:general#potential-1" }
Number:ElectricPotential Branch_2_Potential "Branch 2 Potential" { channel="senseenergy:monitor:cloud:monitor2:general#potential-2" }
Number:Power Main_Power "Main Power" { channel="senseenergy:monitor:cloud:monitor1:general#main-power" }
Number:Power Solar_Power "Solar Power" { channel="senseenergy:monitor:cloud:monitor1:general#solar-power" }
// Discovered device channels
Number:Power Sense_AlwaysOn_Power "Always-On Power" { channel="senseenergy:monitor:cloud:monitor1:discovered-devices#always_on-device-power" }
Number:Power Sense_PoolPump_Power "Pool Pump Power" { channel="senseenergy:monitor:cloud:monitor1:discovered-devices#Z0sBBkO1-device-power" }
Number:Power Sense_Other_Power "Other Power" { channel="senseenergy:monitor:cloud:monitor1:discovered-devices#unknown-device-power" }
// Virtual proxy device "follow" channels. These should be the actually controlling items for your device.
Switch LightSwitch "Light Switch" { channel="senseenergy:proxy-device:cloud:monitor1:light:proxy-device-switch"[profile="system:follow"] }
Dimmer LightDimmer "Light Dimmer" { channel="senseenergy:proxy-device:cloud:monitor1:light:proxy-device-dimmer"[profile="system:follow"] }
Number:Power PoolPump_Power "Pool Pump Power" { channel="senseenergy:proxy-device:cloud:monitor1:light:proxy-device-power"[profile="system:follow"] }
String Fan_State "Fan State" { channel="senseenergy:proxy-device:cloud:monitor1:light:proxy-device-state"[profile="system:follow"] }
```
### Rules
```java
rule "Sense Energy Discovered Device OnOff"
when
Channel 'senseenergy:monitor:cloud:monitor1:discovered-devices#XXXX-trigger' triggered or
Channel 'senseenergy:monitor:cloud:monitor1:self-reporting-devices#YYYY-trigger' triggered or
Channel 'senseenergy:monitor:cloud:monitor1:proxy-devices#ZZZZ-trigger' triggered
then
logInfo("SenseEnergy", "Sense Energy device turned ON/OFF - Event: {}", receivedEvent)
end
```
### Rule Actions
The binding also supports querying of trend totals over a periods of time.
#### Map<String, Object> queryEnergyTrend(String scale, Instant datetime)
This function will query tthe Sense cloud for usage totals for a given period of time.
##### Parameters
`scale` - the time scale for which the query should be over ("DAY", "WEEK", "MONTH", "YEAR").
`datetime` - the datetime in the period. this can be null to select the current datetime.
##### Returns
The return is a Map<String, Object> object which contains the following values:
`consumption` - a QuantityType<Energy> of the total energy (KWh) used over the scale period.
`production` - a QuantityType<Energy> of the total energy (KWh) produced over the scale period.
`fromGrid` - a QuantityType<Energy> of the total energy (KWh) from the grid over the scale period.
`toGrid` - a QuantityType<Energy> of the total energy (KWh) to the grid over the scale period.
`netProduction` - a QuantityType<Energy> of the difference in energy (KWh) between what was produced and consumed during the scale period.
`solarPowered` - a QuantityType<Dimensionless> of the percent of solar energy production that was directly consumed (not sent to grid) during the scale period.
##### Example
```java
rule "Sense Energy Update Trends"
when
Time cron "0 0/15 * ? * *"
then
logInfo("SenseEnergy", "Sense Energy Update Trends")
val monitorActions = getActions("senseenergy", "senseenergy:monitor:cloud:monitor1")
val dayTrends = monitorActions.queryEnergyTrend("DAY", null)
logInfo("SenseEnergy", "Energy DAY trends {}", dayTrends.toString())
val weekTrends = monitorActions.queryEnergyTrend("WEEK", null)
logInfo("SenseEnergy", "Energy WEEK trends {}", weekTrends.toString())
val monthTrends = monitorActions.queryEnergyTrend("MONTH", null)
logInfo("SenseEnergy", "Energy MONTH trends {}", monthTrends.toString())
val yearTrends = monitorActions.queryEnergyTrend("YEAR", null)
logInfo("SenseEnergy", "Energy YEAR trends {}", yearTrends.toString())
end
```
## Special Notes
For proxy device to work, openHAB must be on the same sub-net as the Sense monitor and be able to receive broadcast Datagram packets on port 9999.
While the binding has not been tested in a Docker configuration, there are some potential issues with being able to receive on port 9999 (see https://github.com/cbpowell/SenseLink/).
The Sense Energy Monitor can be configured in two different modes depending on whether the secondary current monitor is either attaced to the Solar circuit of another circuit in your house.
Unfortunately, the JSON format from the API is different depending on the mode and currently the binding has only been tested and will work in the Solar mode.
If there are others wanting to use the setup in a different mode, I would be interested in enabling support.

450
_addons_bindings/zwave/doc/fibaro/fgr224_0_0.md Normal file
View File

@ -0,0 +1,450 @@
---
layout: documentation
title: FGR224 - ZWave
---
{% include base.html %}
# FGR224 Roller Shutter 4
This describes the Z-Wave device *FGR224*, manufactured by *[Fibargroup](http://www.fibaro.com/)* with the thing type UID of ```fibaro_fgr224_00_000```.
The device is in the category of *Blinds*, defining Roller shutters, window blinds, etc..
![FGR224 product image](https://opensmarthouse.org/zwavedatabase/1654/image/)
The FGR224 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
FIBARO ROLLER SHUTTER 4 is designed for controlling roller blinds, awnings, blinds, curtains and pergolas.
FIBARO ROLLER SHUTTER 4 enables the precise positioning of roller blinds or blind blades. The device is equipped with energy monitoring. The device is equipped with energy monitoring. It enables you to control connected devices either through the Z-Wave® network through or a switch connected directly to it.
### Inclusion Information
Add (inclusion) – the Z-Wave device learning mode allows you to add the device to the existing Z-Wave network.
Manually adding the device to the Z-Wave network
1. Turn on the device. If the device has not been added to the Z-Wave network, the LED indicator of the device will light up red.
2. Set the main control unit to the Security/Non-Safety Additional mode (see the ECU manual for more information).
3. Quickly click the PROG button on the device three times. Alternatively, you can click on S1 or S2 three times.
4. If you add the device in Security S2 Authenticated mode, enter the PIN code specified on the device. The PIN code is also a underlined part of the device-specific key (DSK) specified at the bottom of the field.
5. Wait until the LED indicator flashes yellow.
6. Successful adding is confirmed by the reporting of the Z-Wave controller and the LED display of the device:
Green – successful (not secure, S0, S2 not authenticated)
Magenta – successful (Safety S2 authenticated)
Red – not successful
Adding the device to the Z-Wave network with SmartStart
SmartStart solution allows you to add products to the Z-Wave network by scanning the Z-Wave QR code located on the product, with a controller that enables SmartStart integration. A SmartStart product is automatically included in the network area within 10 minutes of turning it on.
iTo use SmartStart, your ECU must support Security S2 mode (see the control unit's manual for more information).
1. Enter the full DSK string code in your ECU. If your ECU supports a QR scan, scan the QR code on the label.
2. Supply the device with power (on switch on the mains voltage).
3. The LED indicator starts to flash yellow. Wait until the addition process is finished.
4. Successful adding is confirmed by the reporting of the Z-Wave controller and the LED display of the device:
Green – successful (not secure, S0, S2 not authenticated)
Magenta – successful (Safety S2 authenticated)
Red – not successful
if you have any problems adding the device, please reset it and repeat the process.
### Exclusion Information
Remove (exclude) – the Z-Wave device learning mode makes it possible to remove the device from the existing Z Wave network.
1. Make sure the device is turned on
2. Switch the main controller to the removal mode (see the controller's operating instructions for more information).
3. Quickly click the PROG button three times. Alternatively, you can click S1 or S2 three times within 10 minutes after turning on the device.
4. Wait until the removal process is finished.
5. The successful removal is confirmed by a reporting from the Z-Wave controller. The LED indicator lights red.
Removing the device from the Z-Wave network does not result in a factory reset.
### General Usage Information
## Channels
The following table summarises the channels available for the FGR224 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Blinds Control | blinds_control | blinds_control | Blinds | Rollershutter |
| Electric meter (kWh) | meter_kwh | meter_kwh | Energy | Number |
| Scene Number | scene_number | scene_number | | Number |
| Alarm (power) | alarm_power | alarm_power | Energy | Switch |
| Alarm (system) | alarm_system | alarm_system | | Switch |
### Blinds Control
Provides start / stop control of blinds.
The ```blinds_control``` channel is of type ```blinds_control``` and supports the ```Rollershutter``` item and is in the ```Blinds``` category.
### Electric meter (kWh)
Indicates the energy consumption (kWh).
The ```meter_kwh``` channel is of type ```meter_kwh``` and supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
### Scene Number
Triggers when a scene button is pressed.
The ```scene_number``` channel is of type ```scene_number``` and supports the ```Number``` item.
This channel provides the scene, and the event as a decimal value in the form ```<scene>.<event>```. The scene number is set by the device, and the event is as follows -:
| Event ID | Event Description |
|----------|--------------------|
| 0 | Single key press |
| 1 | Key released |
| 2 | Key held down |
| 3 | Double keypress |
| 4 | Tripple keypress |
| 5 | 4 x keypress |
| 6 | 5 x keypress |
### Alarm (power)
Indicates if a power alarm is triggered.
The ```alarm_power``` channel is of type ```alarm_power``` and supports the ```Switch``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the ```Switch``` item type -:
| Value | Label |
|-------|-----------|
| OFF | OK |
| ON | Alarm |
### Alarm (system)
Indicates if a system alarm is triggered.
The ```alarm_system``` channel is of type ```alarm_system``` and supports the ```Switch``` item. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the ```Switch``` item type -:
| Value | Label |
|-------|-----------|
| OFF | OK |
| ON | Alarm |
## Device Configuration
The following table provides a summary of the 13 configuration parameters available in the FGR224.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 20 | Switch type | Defines switch type |
| 24 | Buttons orientation | Defines buttons orientation |
| 25 | Outputs orientation | Defines outputs orientation |
| 40 | First button – scenes sent | Defines first button scenes sent |
| 41 | Second button – scenes sent | Defines first button scenes sent |
| 150 | Calibration | Calibration |
| 151 | Operating mode | Operating mode |
| 152 | Venetian blind - slats full turn time | Venetian blind - slats full turn time |
| 156 | Time of up movement | Time of up movement |
| 157 | Time of down movement | Time of down movement |
| 158 | Virtual limit switch. The pot protection | Virtual limit switch. The pot protection |
| 159 | Favorite position - opening level | Favorite position - opening level |
| 160 | Favorite position - slat angle | Favorite position - slat angle |
### Parameter 20: Switch type
Defines switch type
This parameter determines with which switches types and in which mode the S1 and S2 inputs operate.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Monostable switches – click to move |
| 1 | Monostable switches – hold to move |
| 2 | Single monostable switch |
| 3 | Bistable switches |
| 4 | Single bistable switch |
| 5 | Three-state switch |
The manufacturer defined default value is ```0``` (Monostable switches – click to move).
This parameter has the configuration ID ```config_20_1``` and is of type ```INTEGER```.
### Parameter 24: Buttons orientation
Defines buttons orientation
This parameter allows reversing the operation of the buttons.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | default (1st button UP, 2nd button DOWN) |
| 1 | reversed (1st button DOWN, 2nd button UP) |
The manufacturer defined default value is ```0``` (default (1st button UP, 2nd button DOWN)).
This parameter has the configuration ID ```config_24_1``` and is of type ```INTEGER```.
### Parameter 25: Outputs orientation
Defines outputs orientation
This parameter allows reversing the operation of O1 and O2 without changing the wiring (e.g. in case of invalid motor connection).
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | default (O1 – UP, O2 – DOWN) |
| 1 | reversed (O1 – DOWN, O2 – UP) |
The manufacturer defined default value is ```0``` (default (O1 – UP, O2 – DOWN)).
This parameter has the configuration ID ```config_25_1``` and is of type ```INTEGER```.
### Parameter 40: First button – scenes sent
Defines first button scenes sent
This parameter determines which actions result in sending scene IDs assigned to them. Values can be combined (e.g. 1+2=3 means that scenes for single and double click are sent). Enabling scenes for triple click disables entering the device in learn mode by triple clicking.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | No scene active |
| 1 | Key pressed 1 time |
| 2 | Key pressed 2 times |
| 4 | Key pressed 3 times |
| 8 | Key hold down and key released |
| 15 | default - All scenes active |
The manufacturer defined default value is ```15``` (default - All scenes active).
This parameter has the configuration ID ```config_40_1``` and is of type ```INTEGER```.
### Parameter 41: Second button – scenes sent
Defines first button scenes sent
This parameter determines which actions result in sending scene IDs assigned to them. Values can be combined (e.g. 1+2=3 means that scenes for single and double click are sent). Enabling scenes for triple click disables entering the device in learn mode by triple clicking.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | No scene active |
| 1 | Key pressed 1 time |
| 2 | Key pressed 2 times |
| 4 | Key pressed 3 times |
| 8 | Key hold down and key released |
| 15 | default - All scenes active |
The manufacturer defined default value is ```0``` (No scene active).
This parameter has the configuration ID ```config_41_1``` and is of type ```INTEGER```.
### Parameter 150: Calibration
Calibration
To start automatic calibration, select the value 3. When the calibration process is successful, the parameter takes the value 1. When automatic calibration fails, the parameter takes the value 2. If the transitions times for the device are changed manually in the parameter (156/157), the parameter 150 will takes the value 4.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Device is not calibrated |
| 1 | Autocalibration successful |
| 2 | Autocalibration failed |
| 3 | Calibration process |
| 4 | Manual calibration |
The manufacturer defined default value is ```0``` (Device is not calibrated).
This parameter has the configuration ID ```config_150_1``` and is of type ```INTEGER```.
### Parameter 151: Operating mode
Operating mode
This parameter allows you to adjust the operation, depending on the connected device. In the case of venetian blinds, the angle of rotation of the slats must also be selected.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Roller blind, Awning, Pergola, Curtain |
| 1 | Venetian blind 90° |
| 2 | Venetian blind 180° |
The manufacturer defined default value is ```0``` (Roller blind, Awning, Pergola, Curtain).
This parameter has the configuration ID ```config_151_1``` and is of type ```INTEGER```.
### Parameter 152: Venetian blind - slats full turn time
Venetian blind - slats full turn time
For Venetian blinds the parameter determines time of full turn cycle of the slats. The parameter is irrelevant for other modes.
Default: 15 (1.5 seconds)
Range: 0-65535 (0 - 6553.5s, every 0.1s) - time of turn
Values in the range 0 to 65535 may be set.
The manufacturer defined default value is ```15```.
This parameter has the configuration ID ```config_152_2``` and is of type ```INTEGER```.
### Parameter 156: Time of up movement
Time of up movement
This parameter determines the time it takes to reach full opening. The value is set automatically during the calibration process. It should be manually set in case of problems with the autocalibration.
Default: 600 (60 seconds)
Range: 0-65535 (0 - 6553.5s, every 0.1s) - time of turn
Values in the range 0 to 65535 may be set.
The manufacturer defined default value is ```600```.
This parameter has the configuration ID ```config_156_2``` and is of type ```INTEGER```.
### Parameter 157: Time of down movement
Time of down movement
This parameter determines the time it takes to reach full closure. The value is set automatically during the calibration process. It should be manually set in case of problems with the autocalibration.
Default: 600 (60 seconds)
Range: 0-65535 (0 - 6553.5s, every 0.1s) - time of turn
Values in the range 0 to 65535 may be set.
The manufacturer defined default value is ```600```.
This parameter has the configuration ID ```config_157_2``` and is of type ```INTEGER```.
### Parameter 158: Virtual limit switch. The pot protection
Virtual limit switch. The pot protection
This parameter allows you to set a fixed minimum level of lowering the shutter. For example, to protect a flowerpot located on a windowsill.
Values in the range 0 to 99 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_158_1``` and is of type ```INTEGER```.
### Parameter 159: Favorite position - opening level
Favorite position - opening level
This parameter allows you to define your favorite aperture level.
Range: 0-99
0xFF - Functionality disabled
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 255 | Functionality disabled |
The manufacturer defined default value is ```50```.
This parameter has the configuration ID ```config_159_1``` and is of type ```INTEGER```.
### Parameter 160: Favorite position - slat angle
Favorite position - slat angle
This parameter allows you to define your favorite position of the slat angle. The parameter is used only for venetian blinds.
Range: 0-99
0xFF - Functionality disabled
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 255 | 0xFF - Functionality disabled |
The manufacturer defined default value is ```50```.
This parameter has the configuration ID ```config_160_1``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The FGR224 supports 2 association groups.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
General: Lifeline
1st association group – “Lifeline” reports the device status and allows for assigning single device only (main controller by default).
Association group 1 supports 1 node.
### Group 2: Window Covering
Control: KEY01 (0x20: 0x01)
2nd association group – “Window Covering” is intended for curtains or blinds allowing the user to control the amount of light going through windows.
Association group 2 supports 5 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_APPLICATION_STATUS_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| Linked to BASIC|
| COMMAND_CLASS_METER_V3| |
| COMMAND_CLASS_TRANSPORT_SERVICE_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_CENTRAL_SCENE_V3| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_WINDOW_COVERING_V1| |
| COMMAND_CLASS_SUPERVISION_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_ALARM_V8| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_PROTECTION_V2| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_INDICATOR_V3| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
| COMMAND_CLASS_SECURITY_2_V1| |
### Documentation Links
* [Operating Manual (english)](https://opensmarthouse.org/zwavedatabase/1654/reference/FGR-224-EN-v2.6_26.09.24.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1654).

273
_addons_bindings/zwave/doc/nexa/zpr111_0_0.md Normal file
View File

@ -0,0 +1,273 @@
---
layout: documentation
title: ZPR-111 - ZWave
---
{% include base.html %}
# ZPR-111 Plug-in Switch with enery meter
This describes the Z-Wave device *ZPR-111*, manufactured by *Nexa* with the thing type UID of ```nexa_zpr111_00_000```.
The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there.
![ZPR-111 product image](https://opensmarthouse.org/zwavedatabase/1653/image/)
The ZPR-111 supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
Z-Wave plugin receiver (On/Off) with power consumption measurement function, LED indicator, built-in switch-off timer and on/off button.
### Inclusion Information
Press the link button three times within 1.5 seconds; the LED flashes Yellow 5 times.
### Exclusion Information
Press the link button three times within 1.5 seconds: the LED flashes Purple 5 times.
### General Usage Information
## Channels
The following table summarises the channels available for the ZPR-111 -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Switch | switch_binary | switch_binary | Switch | Switch |
| Electric meter (kWh) | meter_kwh | meter_kwh | Energy | Number |
| Electric meter (watts) | meter_watts | meter_watts | Energy | Number |
| Electric meter (volts) | meter_voltage | meter_voltage | Energy | Number |
| Electric meter (amps) | meter_current | meter_current | Energy | Number |
| Alarm (power) | alarm_power | alarm_power | Energy | Switch |
### Switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Electric meter (kWh)
Indicates the energy consumption (kWh).
The ```meter_kwh``` channel is of type ```meter_kwh``` and supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
### Electric meter (watts)
Indicates the instantaneous power consumption.
The ```meter_watts``` channel is of type ```meter_watts``` and supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
### Electric meter (volts)
Indicates the instantaneous voltage.
The ```meter_voltage``` channel is of type ```meter_voltage``` and supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
### Electric meter (amps)
Indicates the instantaneous current consumption.
The ```meter_current``` channel is of type ```meter_current``` and supports the ```Number``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
### Alarm (power)
Indicates if a power alarm is triggered.
The ```alarm_power``` channel is of type ```alarm_power``` and supports the ```Switch``` item and is in the ```Energy``` category. This is a read only channel so will only be updated following state changes from the device.
The following state translation is provided for this channel to the ```Switch``` item type -:
| Value | Label |
|-------|-----------|
| OFF | OK |
| ON | Alarm |
## Device Configuration
The following table provides a summary of the 9 configuration parameters available in the ZPR-111.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 1 | Send meter report enable | This parameter defines Enable/Disable meter report measure data to controller (default Enable). |
| 2 | Meter report interval | Defines the time interval that meter report data to main controller (default 300s). |
| 3 | Upper current threshold | Defines the maximum current before the plug will cut off power (default 13A). |
| 4 | Upper current threshold alarm | Defines the over current alarm threshold (default 12A) |
| 5 | Led display enable | Defines the LED indication function ON/OFF (default ON). |
| 6 | Power reporting setting | Defines by how much consumed power must change to be reported to the Z-Wave Controller (default 30%). |
| 7 | Remember relay status | Defines if the relay status is remembered or not after a power cut (default Remember). |
| 8 | Time switch enable/disable | Defines switch timer function Enable/Disable (default Disable). |
| 9 | Time switch period | Defines the time period before the plug is switched off (default 150m). |
### Parameter 1: Send meter report enable
This parameter defines Enable/Disable meter report measure data to controller (default Enable).
The following option values may be configured, in addition to values in the range 0 to 0 -:
| Value | Description |
|--------|-------------|
| 0 | Disable |
| 1 | Enable |
The manufacturer defined default value is ```1``` (Enable).
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
### Parameter 2: Meter report interval
Defines the time interval that meter report data to main controller (default 300s).
Values in the range 1 to 65535 may be set.
The manufacturer defined default value is ```300```.
This parameter has the configuration ID ```config_2_2``` and is of type ```INTEGER```.
### Parameter 3: Upper current threshold
Defines the maximum current before the plug will cut off power (default 13A).
This parameter defines maximum current the plug can provide to load that be connected to plug. If the current consumed by load greater than maximum current, the plug will cut off power.
Values in the range 1 to 16 may be set.
The manufacturer defined default value is ```13```.
This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```.
### Parameter 4: Upper current threshold alarm
Defines the over current alarm threshold (default 12A)
This parameter defines maximum current. If the current the plug provides to the load is greater than this parameter, the plug will send over-current notification to main controller and the LED will be turn RED. This value must be less than parameter #3.
Values in the range 1 to 16 may be set.
The manufacturer defined default value is ```12```.
This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```.
### Parameter 5: Led display enable
Defines the LED indication function ON/OFF (default ON).
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
|--------|-------------|
| 0 | Off |
| 1 | On |
The manufacturer defined default value is ```1``` (On).
This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```.
### Parameter 6: Power reporting setting
Defines by how much consumed power must change to be reported to the Z-Wave Controller (default 30%).
This parameter defines by how much power consumed must change to be reported to the Z-Wave Controller or Z-Wave Gateway, in percents.
If the rate of power consumed change ratio is greater than this parameter, the plug will report the results, voltage, current, power and energy, that plug measure to Z-Wave Controller or Z-Wave Gateway. 
Values in the range 1 to 100 may be set.
The manufacturer defined default value is ```30```.
This parameter has the configuration ID ```config_6_1``` and is of type ```INTEGER```.
### Parameter 7: Remember relay status
Defines if the relay status is remembered or not after a power cut (default Remember).
This parameter defined the relay status if remember or not. If remembered, the plug will restore the relay status last power off when the plug supply power next time.
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
|--------|-------------|
| 0 | Do not Remember |
| 1 | Remember |
The manufacturer defined default value is ```1``` (Remember).
This parameter has the configuration ID ```config_7_1``` and is of type ```INTEGER```.
### Parameter 8: Time switch enable/disable
Defines switch timer function Enable/Disable (default Disable).
This parameter defines the timer function Enable/Disable. The time period will be defined in parameter #9. If this parameter is set to 1, and when turn the plug relay on, the timer in plug start run with time period defined in parameter #9 and the plug will turn the relay off.
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
|--------|-------------|
| 0 | Disable |
| 1 | Enable |
The manufacturer defined default value is ```0``` (Disable).
This parameter has the configuration ID ```config_8_1``` and is of type ```INTEGER```.
### Parameter 9: Time switch period
Defines the time period before the plug is switched off (default 150m).
This parameter defines the time period that plug time switch off.
If Parameter #8 is set to 1, and relay is turn-on, the relay will be turn-off after delay this parameter.
Values in the range 1 to 65535 may be set.
The manufacturer defined default value is ```150```.
This parameter has the configuration ID ```config_9_2``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The ZPR-111 supports 1 association group.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Association group 1 supports 1 node.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_METER_V3| |
| COMMAND_CLASS_TRANSPORT_SERVICE_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_SUPERVISION_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_ALARM_V8| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_MULTI_CHANNEL_ASSOCIATION_V3| |
| COMMAND_CLASS_SECURITY_V1| |
| COMMAND_CLASS_SECURITY_2_V1| |
### Documentation Links
* [Configuration](https://opensmarthouse.org/zwavedatabase/1653/reference/ZPR-111_Configuration.pdf)
* [Manual](https://opensmarthouse.org/zwavedatabase/1653/reference/86813_ZPR-111_manual.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1653).

48
_addons_bindings/zwave/doc/shelly/waveplugus_0_0.md → _addons_bindings/zwave/doc/shelly/waveplug_0_0.md
View File

@ -1,23 +1,23 @@
---
layout: documentation
title: Wave Plug US - ZWave
title: Wave Plug - ZWave
---
{% include base.html %}
# Wave Plug US Plug On Off with Energy Meter
This describes the Z-Wave device *Wave Plug US*, manufactured by *Shelly* with the thing type UID of ```shelly_waveplugus_00_000```.
# Wave Plug Plug On Off with power measurement
This describes the Z-Wave device *Wave Plug*, manufactured by *Shelly* with the thing type UID of ```shelly_waveplug_00_000```.
The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there.
![Wave Plug US product image](https://opensmarthouse.org/zwavedatabase/1642/image/)
![Wave Plug product image](https://opensmarthouse.org/zwavedatabase/1642/image/)
The Wave Plug US supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
The Wave Plug supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
The Wave Plug US (Device) is a smart plug/outlet with power measurement and overheating protection, which allows remote control of electric appliances through a mobile phone, tablet, PC, or home automation system.
The Wave Plug (Device) is a smart plug/outlet with power measurement and overheating protection, which allows remote control of electric appliances through a mobile phone, tablet, PC, or home automation system.
### Inclusion Information
@ -77,7 +77,7 @@ The blue LED will be blinking in Mode 1 if the Device is successfully removed fr
## Channels
The following table summarises the channels available for the Wave Plug US -:
The following table summarises the channels available for the Wave Plug -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
@ -142,7 +142,7 @@ The following state translation is provided for this channel to the ```Switch```
## Device Configuration
The following table provides a summary of the 15 configuration parameters available in the Wave Plug US.
The following table provides a summary of the 17 configuration parameters available in the Wave Plug.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
@ -158,7 +158,9 @@ Detailed information on each parameter can be found in the sections below.
| 92 | Smoke Alarm | This parameter determines how the device should respond to the reports of alarm frames. The parameters consist of 4 bytes, the three most significant bytes are set according to the official Z-Wave protocol specification. |
| 93 | CO Alarm | This parameter determines how the device should respond to the reports of alarm frames. The parameters consist of 4 bytes, the three most significant bytes are set according to the official Z-Wave protocol specification. |
| 94 | Heat Alarm | This parameter determines how the device should respond to the reports of alarm frames. The parameters consist of 4 bytes, the three most significant bytes are set according to the official Z-Wave protocol specification. |
| 105 | LED Signalisation intensity | In Wave 1, Wave 1PM and Wave 2PM, this parameter will be implemented in 2024. This parameter determines the intensity of the LED on the Device. Some Devices have RGB LEDs and some have Blue/Red LEDs, but all are dimmable. |
| 117 | Remote Device reboot | This parameter enable restarting or rebooting the Device without physical intervention. Use this parameter only for troubleshooting scope. After device reboot value will be set to default |
| 120 | Factory Reset | Reset to factory default settings and removed from the Z-Wave network. |
| 201 | Serial Number 1 | This parameter contains a part of device’s serial number. |
| 201 | Serial Number 2 | This parameter contains a part of device’s serial number. |
| 203 | Serial Number 3 | This parameter contains a part of device’s serial number. |
@ -336,6 +338,19 @@ The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_94_4``` and is of type ```INTEGER```.
### Parameter 105: LED Signalisation intensity
In Wave 1, Wave 1PM and Wave 2PM, this parameter will be implemented in 2024. This parameter determines the intensity of the LED on the Device. Some Devices have RGB LEDs and some have Blue/Red LEDs, but all are dimmable.
Values & descriptions:
 0-100 (0-100%, every 1%)
Values in the range 0 to 100 may be set.
The manufacturer defined default value is ```100```.
This parameter has the configuration ID ```config_105_1``` and is of type ```INTEGER```.
### Parameter 117: Remote Device reboot
This parameter enable restarting or rebooting the Device without physical intervention. Use this parameter only for troubleshooting scope. After device reboot value will be set to default
@ -347,6 +362,21 @@ The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_117_1``` and is of type ```INTEGER```.
### Parameter 120: Factory Reset
Reset to factory default settings and removed from the Z-Wave network.
Values & descriptions:
0 - Don’t do Factory reset
1431655765 - Do the Factory reset (hex 0x55555555)
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_120_4``` and is of type ```INTEGER```.
### Parameter 201: Serial Number 1
This parameter contains a part of device’s serial number.
@ -387,7 +417,7 @@ This is a read only parameter.
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The Wave Plug US supports 2 association groups.
The Wave Plug supports 2 association groups.
### Group 1: Lifeline

280
_addons_bindings/zwave/doc/simontech/1000203413x_0_0.md Normal file
View File

@ -0,0 +1,280 @@
---
layout: documentation
title: 10002080-13x - ZWave
---
{% include base.html %}
# 10002080-13x Simon IO: Roller Blind
This describes the Z-Wave device *10002080-13x*, manufactured by *SimonTech S.L.U* with the thing type UID of ```simontech_1000203413x_00_000```.
The device is in the category of *Blinds*, defining Roller shutters, window blinds, etc..
![10002080-13x product image](https://opensmarthouse.org/zwavedatabase/930/image/)
The 10002080-13x supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
Roller Blind IO is ready to operate with Z-Wave controllers and configured to be managed by Simon100 IO APP using the HUB plug IO for getting a better user experience. Sending the Blind Up/Down or setting a specific position.
### Inclusion Information
When the pushbutton is released after a press of (2<T<10sec) the device will send a NIF to include from Z-Wave network or perform an association with other Z-Wave device.
Central LED will Blink with 0,3 sec period to inform that NIF can be send after release of pushbutton.
This process does not perform a default reset of configurations.
Main LED will Blink with 0,3 sec period to inform that NIF can be send after release of pushbutton.
### Exclusion Information
When the pushbutton is released after a press of (2<T<10sec) the device will send a NIF to exclude from Z-Wave network or perform an association with other Z-Wave device.
Main LED will Blink with 0,3 sec period to inform that NIF can be send after release of pushbutton.
This process does not perform a default reset of configurations.
Main LED will Blink with 0,3 sec period to inform that NIF can be send after release of pushbutton.
## Channels
The following table summarises the channels available for the 10002080-13x -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Blinds Control | blinds_control | blinds_control | Blinds | Rollershutter |
### Blinds Control
Provides start / stop control of blinds.
The ```blinds_control``` channel is of type ```blinds_control``` and supports the ```Rollershutter``` item and is in the ```Blinds``` category.
## Device Configuration
The following table provides a summary of the 9 configuration parameters available in the 10002080-13x.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 1 | Association LED | Activates the Central LED. |
| 4 | Up Time | Up Time |
| 5 | Down Time | Down Time |
| 9 | Calibration | Calibration |
| 12 | Behavior of LED in Repose | Configuration of Main LED as identification at 20%. |
| 13 | Lock Input | Unlock/lock the direct control of load. |
| 21 | Load State | Load State (Read Only) |
| 23 | Calibration Required | Calibration Required (Read Only) |
| 27 | Lock long press | 7 Lock long press |
### Parameter 1: Association LED
Activates the Central LED.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Turns the LED OFF (default) |
| 255 | Turns the LED ON |
The manufacturer defined default value is ```0``` (Turns the LED OFF (default)).
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
### Parameter 4: Up Time
Up Time
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 1 | Sets the UP time in seconds |
| 60 | Default |
The manufacturer defined default value is ```60``` (Default).
This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```.
This is a read only parameter.
### Parameter 5: Down Time
Down Time
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 1 | Sets the DOWN time in seconds |
| 60 | Default |
The manufacturer defined default value is ```60``` (Default).
This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```.
### Parameter 9: Calibration
Calibration
255 - The device will perform a calibration process in order to Set the UP and DOWN times automatically
Values in the range 255 to 255 may be set.
The manufacturer defined default value is ```255```.
This parameter has the configuration ID ```config_9_1_wo``` and is of type ```INTEGER```.
This is a write only parameter.
### Parameter 12: Behavior of LED in Repose
Configuration of Main LED as identification at 20%.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | LED OFF |
| 255 | LED ON at 20% of maximum level |
The manufacturer defined default value is ```0``` (LED OFF).
This parameter has the configuration ID ```config_12_1``` and is of type ```INTEGER```.
### Parameter 13: Lock Input
Unlock/lock the direct control of load.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Unlock the direct control of load. |
| 255 | Lock the direct control of load. |
The manufacturer defined default value is ```0``` ( Unlock the direct control of load.).
This parameter has the configuration ID ```config_13_1``` and is of type ```INTEGER```.
### Parameter 21: Load State
Load State (Read Only)
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Bit 0: Load is OFF |
| 0 | Bit 1: Sunblind position 0% |
| 1 | Bit 0: Load is going UP/DOWN |
| 99 | Bit 1: Sunblind position 99% |
The manufacturer defined default value is ```0``` (Bit 1: Sunblind position 0%).
This parameter has the configuration ID ```config_21_2``` and is of type ```INTEGER```.
This is a read only parameter.
### Parameter 23: Calibration Required
Calibration Required (Read Only)
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Calibration is not required. |
| 255 | It is necessary to calibrate the device. |
The manufacturer defined default value is ```0``` (Calibration is not required.).
This parameter has the configuration ID ```config_23_1``` and is of type ```INTEGER```.
This is a read only parameter.
### Parameter 27: Lock long press
7 Lock long press
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Long press works as default. |
| 255 | Long press works as overview. |
The manufacturer defined default value is ```0``` (Long press works as default.).
This parameter has the configuration ID ```config_27_1``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The 10002080-13x supports 2 association groups.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Lifeline
Change on Sunblind position:
* On -> CC Basic, Basic Report.
* Value 0x01 - 0x63 Report sunblind position
Calibration requirement change. (If device needs to be calibrated and is Added into a ZWave network, it will report after receive an Association Set of life line).
* Calibration required -> CC Configuration, Configuration Report, Param 23, Value 0xF
* Calibration not required -> CC Configuration, Configuration Report, Param 23, Value 0x00
Association group 1 supports 3 nodes.
### Group 2: ctrl
Control
Change on Sunblind position:
* CC Basic, Basic Report.
* Value 0x00 - 0x63 Report sunblind position
Association group 2 supports 20 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| Linked to BASIC|
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
### Documentation Links
* [Manual](https://opensmarthouse.org/zwavedatabase/930/reference/ROLLERBLIND-991025-990913.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/930).

2
_addons_bindings/zwave/doc/simontech/1000x080x_0_0.md
View File

@ -252,7 +252,7 @@ Association group 2 supports 20 nodes.
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| |
| COMMAND_CLASS_SWITCH_MULTILEVEL_V3| Linked to BASIC|
| COMMAND_CLASS_TRANSPORT_SERVICE_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V3| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |

18
_thing_types/org.openhab.binding.casokitchen/src/main/resources/OH-INF/thing/bottom-zone-group.xml Normal file
View File

@ -0,0 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="casokitchen"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<channel-group-type id="bottom-values">
<label>Bottom Zone</label>
<channels>
<channel id="power" typeId="system.power">
<label>Zone is Powered</label>
<description>Showing if zone is currently powered</description>
</channel>
<channel id="temperature" typeId="temperature"/>
<channel id="set-temperature" typeId="set-temperature"/>
<channel id="light-switch" typeId="light-switch"/>
</channels>
</channel-group-type>
</thing:thing-descriptions>

45
_thing_types/org.openhab.binding.casokitchen/src/main/resources/OH-INF/thing/channel-types.xml Normal file
View File

@ -0,0 +1,45 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="casokitchen"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<channel-type id="temperature">
<item-type>Number:Temperature</item-type>
<label>Temperature</label>
<description>Current Zone Temperature</description>
<tags>
<tag>Temperature</tag>
<tag>Measurement</tag>
</tags>
<state pattern="%.1f %unit%" readOnly="true"/>
</channel-type>
<channel-type id="set-temperature">
<item-type>Number:Temperature</item-type>
<label>Target Temperature</label>
<description>Target Zone Temperature</description>
<tags>
<tag>Temperature</tag>
<tag>SetPoint</tag>
</tags>
<state pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="light-switch">
<item-type>Switch</item-type>
<label>Light Switch</label>
<description>Switching lights on and off</description>
<autoUpdatePolicy>veto</autoUpdatePolicy>
</channel-type>
<channel-type id="hint">
<item-type>String</item-type>
<label>Hint</label>
<description>Textual hint for device status</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="last-update">
<item-type>DateTime</item-type>
<label>Last Update</label>
<description>Time stamp of latest device communication</description>
<state pattern="%1$tA, %1$td.%1$tm. %1$tH:%1$tM" readOnly="true"/>
</channel-type>
</thing:thing-descriptions>

14
_thing_types/org.openhab.binding.casokitchen/src/main/resources/OH-INF/thing/generic-group.xml Normal file
View File

@ -0,0 +1,14 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="casokitchen"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<channel-group-type id="generic-values">
<label>Generic Values</label>
<channels>
<channel id="light-switch" typeId="light-switch"/>
<channel id="hint" typeId="hint"/>
<channel id="last-update" typeId="last-update"/>
</channels>
</channel-group-type>
</thing:thing-descriptions>

33
_thing_types/org.openhab.binding.casokitchen/src/main/resources/OH-INF/thing/thing-types.xml Normal file
View File

@ -0,0 +1,33 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="casokitchen"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<thing-type id="winecooler-2z">
<label>Wine Cooler 2 Zones</label>
<description>Wine cooler with 2 cooling zones</description>
<channel-groups>
<channel-group id="top" typeId="top-values"/>
<channel-group id="bottom" typeId="bottom-values"/>
<channel-group id="generic" typeId="generic-values"/>
</channel-groups>
<config-description>
<parameter name="apiKey" type="text" required="true">
<label>API Key</label>
<description>API Key generated via CASO SMart Kitchen API</description>
</parameter>
<parameter name="deviceId" type="text" required="true">
<label>Device ID</label>
<description>Device ID from CASO connected devices</description>
</parameter>
<parameter name="refreshInterval" type="integer" unit="m" min="5">
<label>Refresh Interval</label>
<description>Interval the device is polled in minutes.</description>
<default>5</default>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

18
_thing_types/org.openhab.binding.casokitchen/src/main/resources/OH-INF/thing/top-zone-group.xml Normal file
View File

@ -0,0 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="casokitchen"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<channel-group-type id="top-values">
<label>Top Zone</label>
<channels>
<channel id="power" typeId="system.power">
<label>Zone is Powered</label>
<description>Showing if zone is currently powered</description>
</channel>
<channel id="temperature" typeId="temperature"/>
<channel id="set-temperature" typeId="set-temperature"/>
<channel id="light-switch" typeId="light-switch"/>
</channels>
</channel-group-type>
</thing:thing-descriptions>

140
_thing_types/org.openhab.binding.homewizard/src/main/resources/OH-INF/thing/channels.xml Normal file
View File

@ -0,0 +1,140 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="homewizard"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<channel-type id="hw-power">
<item-type>Number:Power</item-type>
<label>Active Power</label>
<description>
This channel provides the active usage in Watt.
</description>
<category>Energy</category>
</channel-type>
<channel-type id="hw-power-advanced" advanced="true">
<item-type>Number:Power</item-type>
<label>Active Power</label>
<description>
This channel provides the active usage in Watt.
</description>
<category>Energy</category>
</channel-type>
<channel-type id="hw-voltage">
<item-type>Number:ElectricPotential</item-type>
<label>Active Voltage</label>
<description>
This channel provides the active voltage in Volt.
</description>
<category>Energy</category>
</channel-type>
<channel-type id="hw-voltage-advanced" advanced="true">
<item-type>Number:ElectricPotential</item-type>
<label>Active Voltage</label>
<description>
This channel provides the active voltage in Volt.
</description>
<category>Energy</category>
</channel-type>
<channel-type id="hw-current">
<item-type>Number:ElectricCurrent</item-type>
<label>Active Current</label>
<description>
This channel provides the active current in Ampere.
</description>
<category>Energy</category>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="hw-current-advanced" advanced="true">
<item-type>Number:ElectricCurrent</item-type>
<label>Active Current</label>
<description>
This channel provides the active current in Ampere.
</description>
<category>Energy</category>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="hw-energy-import">
<item-type>Number:Energy</item-type>
<label>Total Energy Import</label>
<description>
This channel provides the total energy usage meter reading in kWh.
</description>
<category>Energy</category>
</channel-type>
<channel-type id="hw-energy-import-advanced" advanced="true">
<item-type>Number:Energy</item-type>
<label>Energy Import</label>
<description>
This channel provides the total energy usage meter reading in kWh.
</description>
<category>Energy</category>
</channel-type>
<channel-type id="hw-energy-export">
<item-type>Number:Energy</item-type>
<label>Total Energy Export</label>
<description>
This channel provides the total energy feed-in meter reading in kWh.
</description>
<category>Energy</category>
</channel-type>
<channel-type id="hw-energy-export-advanced" advanced="true">
<item-type>Number:Energy</item-type>
<label>Energy Export</label>
<description>
This channel provides the total energy feed-in meter reading in kWh.
</description>
<category>Energy</category>
</channel-type>
<channel-type id="hw-reactive-power" advanced="true">
<item-type>Number</item-type>
<label>Reactive Power</label>
<description>
This channel provides the active reactive power in Volt-Ampere reactive.
</description>
<category>Energy</category>
<state readOnly="true" pattern="%.1f VA"/>
</channel-type>
<channel-type id="hw-apparent-power" advanced="true">
<item-type>Number</item-type>
<label>Apparent Power</label>
<description>
This channel provides the active apparent power in Volt-Ampere.
</description>
<category>Energy</category>
<state readOnly="true" pattern="%.1f VA"/>
</channel-type>
<channel-type id="hw-power-factor" advanced="true">
<item-type>Number:Dimensionless</item-type>
<label>Power Factor</label>
<description>
This channel provides the active power factor.
</description>
<category>Energy</category>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="hw-frequency" advanced="true">
<item-type unitHint="Hz">Number:Frequency</item-type>
<label>Frequency</label>
<description>
This channel provides the active frequency in Hertz.
</description>
<category>Energy</category>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
</thing:thing-descriptions>

93
_thing_types/org.openhab.binding.homewizard/src/main/resources/OH-INF/thing/hwe-kwh.xml Normal file
View File

@ -0,0 +1,93 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="homewizard"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<thing-type id="HWE-kwh">
<label>HomeWizard kWh Meter</label>
<description>This thing provides the measurement data that is available through the API of a HomeWizard
kWh Meter.</description>
<channel-groups>
<channel-group id="energy" typeId="kwh-energy-group"/>
</channel-groups>
<properties>
<property name="thingTypeVersion">1</property>
</properties>
<config-description-ref uri="thing-type:homewizard:device"/>
</thing-type>
<channel-group-type id="kwh-energy-group">
<label>Recent Measurements</label>
<channels>
<channel id="power" typeId="hw-power"/>
<channel id="power_l1" typeId="hw-power-advanced">
<label>Active Power L1</label>
<description>
This channel provides the active usage for phase 1 in Watt.
</description>
</channel>
<channel id="power_l2" typeId="hw-power-advanced">
<label>Active Power L2</label>
<description>
This channel provides the active usage for phase 2 in Watt.
</description>
</channel>
<channel id="power_l3" typeId="hw-power-advanced">
<label>Active Power L3</label>
<description>
This channel provides the active usage for phase 3 in Watt.
</description>
</channel>
<channel id="voltage_l1" typeId="hw-voltage-advanced">
<label>Active Voltage L1</label>
<description>
This channel provides the active voltage for phase 1 in Volt.
</description>
</channel>
<channel id="voltage_l2" typeId="hw-voltage-advanced">
<label>Active Voltage L2</label>
<description>
This channel provides the active voltage for phase 2 in Volt.
</description>
</channel>
<channel id="voltage_l3" typeId="hw-voltage-advanced">
<label>Active Voltage L3</label>
<description>
This channel provides the active voltage for phase 3 in Volt.
</description>
</channel>
<channel id="current" typeId="hw-current"/>
<channel id="current_l1" typeId="hw-current-advanced">
<label>Active Current L1</label>
<description>
This channel provides the active current for phase 1 in Ampere.
</description>
</channel>
<channel id="current_l2" typeId="hw-current-advanced">
<label>Active Current L2</label>
<description>
This channel provides the active current for phase 2 in Ampere.
</description>
</channel>
<channel id="current_l3" typeId="hw-current-advanced">
<label>Active Current L3</label>
<description>
This channel provides the active current for phase 3 in Ampere.
</description>
</channel>
<channel id="energy_import" typeId="hw-energy-import"/>
<channel id="energy_export" typeId="hw-energy-export"/>
<channel id="reactive_power" typeId="hw-reactive-power"/>
<channel id="apparent_power" typeId="hw-apparent-power"/>
<channel id="frequency" typeId="hw-frequency"/>
</channels>
</channel-group-type>
</thing:thing-descriptions>

150
_thing_types/org.openhab.binding.homewizard/src/main/resources/OH-INF/thing/hwe-p1.xml Normal file
View File

@ -0,0 +1,150 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="homewizard"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<thing-type id="hwe-p1">
<label>HomeWizard P1 Meter</label>
<description>This thing provides the measurement data that is available through the API of a HomeWizard
P1 Meter.</description>
<channel-groups>
<channel-group id="energy" typeId="p1-energy-group"/>
</channel-groups>
<properties>
<property name="thingTypeVersion">1</property>
</properties>
<config-description-ref uri="thing-type:homewizard:device"/>
</thing-type>
<channel-group-type id="p1-energy-group">
<label>Recent Measurements</label>
<channels>
<channel id="power" typeId="hw-power"/>
<channel id="power_l1" typeId="hw-power-advanced">
<label>Active Power L1</label>
<description>
This channel provides the active usage for phase 1 in Watt.
</description>
</channel>
<channel id="power_l2" typeId="hw-power-advanced">
<label>Active Power L2</label>
<description>
This channel provides the active usage for phase 2 in Watt.
</description>
</channel>
<channel id="power_l3" typeId="hw-power-advanced">
<label>Active Power L3</label>
<description>
This channel provides the active usage for phase 3 in Watt.
</description>
</channel>
<channel id="voltage_l1" typeId="hw-voltage-advanced">
<label>Active Voltage L1</label>
<description>
This channel provides the active voltage for phase 1 in Volt.
</description>
</channel>
<channel id="voltage_l2" typeId="hw-voltage-advanced">
<label>Active Voltage L2</label>
<description>
This channel provides the active voltage for phase 2 in Volt.
</description>
</channel>
<channel id="voltage_l3" typeId="hw-voltage-advanced">
<label>Active Voltage L3</label>
<description>
This channel provides the active voltage for phase 3 in Volt.
</description>
</channel>
<channel id="current_l1" typeId="hw-current-advanced">
<label>Active Current L1</label>
<description>
This channel provides the active current for phase 1 in Ampere.
</description>
</channel>
<channel id="current_l2" typeId="hw-current-advanced">
<label>Active Current L2</label>
<description>
This channel provides the active current for phase 2 in Ampere.
</description>
</channel>
<channel id="current_l3" typeId="hw-current-advanced">
<label>Active Current L3</label>
<description>
This channel provides the active current for phase 3 in Ampere.
</description>
</channel>
<channel id="energy_import" typeId="hw-energy-import"/>
<channel id="energy_import_T1" typeId="hw-energy-import-advanced">
<label>Energy Import T1</label>
<description>
This channel provides the energy usage meter reading for tariff 1 in kWh.
</description>
</channel>
<channel id="energy_import_T2" typeId="hw-energy-import-advanced">
<label>Energy Import T2</label>
<description>
This channel provides the energy usage meter reading for tariff 2 in kWh.
</description>
</channel>
<channel id="energy_export" typeId="hw-energy-export"/>
<channel id="energy_export_T1" typeId="hw-energy-export-advanced">
<label>Energy Export T1</label>
<description>
This channel provides the energy feed-in meter reading for tariff 1 in kWh.
</description>
</channel>
<channel id="energy_export_T2" typeId="hw-energy-export-advanced">
<label>Energy Export T2</label>
<description>
This channel provides the energy feed-in meter reading for tarff 2 in kWh.
</description>
</channel>
<channel id="power_failures" typeId="p1-power-failures"/>
<channel id="long_power_failures" typeId="p1-power-failures">
<label>Long Power Failures</label>
<description>
This channel provides the number of 'long' power failures detected by meter.
</description>
</channel>
<channel id="total_gas" typeId="p1-total-gas"/>
<channel id="gas_timestamp" typeId="p1-gas-timestamp"/>
</channels>
</channel-group-type>
<channel-type id="p1-power-failures">
<item-type>Number</item-type>
<label>Power Failures</label>
<description>This channel provides the number of power failures detected by meter.</description>
</channel-type>
<channel-type id="p1-total-gas">
<item-type>Number:Volume</item-type>
<label>Total Imported Gas</label>
<description>
This channel provides the most recently reported total imported gas in m^3. It does not get updated as
frequently as the data in the other channels, the gas_timestamp channel provides the time stamp of the most recent
update.
</description>
</channel-type>
<channel-type id="p1-gas-timestamp">
<item-type>DateTime</item-type>
<label>Gas Update Time Stamp</label>
<description>
This channel provides the time stamp of the total_gas measurement.
</description>
</channel-type>
</thing:thing-descriptions>

72
_thing_types/org.openhab.binding.homewizard/src/main/resources/OH-INF/thing/hwe-skt.xml Normal file
View File

@ -0,0 +1,72 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="homewizard"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<thing-type id="hwe-skt">
<label>HomeWizard Energy Socket</label>
<description>This thing provides the measurement data that is available through the API of a HomeWizard
Energy Socket.</description>
<channel-groups>
<channel-group id="energy" typeId="skt-energy-group"/>
<channel-group id="control" typeId="skt-control-group"/>
</channel-groups>
<properties>
<property name="thingTypeVersion">1</property>
</properties>
<config-description-ref uri="thing-type:homewizard:device"/>
</thing-type>
<channel-group-type id="skt-energy-group">
<label>Recent Measurements</label>
<channels>
<channel id="power" typeId="hw-power"/>
<channel id="voltage" typeId="hw-voltage"/>
<channel id="current" typeId="hw-current"/>
<channel id="energy_import" typeId="hw-energy-import"/>
<channel id="energy_export" typeId="hw-energy-export"/>
<channel id="reactive_power" typeId="hw-reactive-power"/>
<channel id="apparent_power" typeId="hw-apparent-power"/>
<channel id="power_factor" typeId="hw-power-factor"/>
<channel id="frequency" typeId="hw-frequency"/>
</channels>
</channel-group-type>
<channel-group-type id="skt-control-group">
<label>Control Device State</label>
<channels>
<channel id="power_switch" typeId="skt-power-switch"/>
<channel id="power_lock" typeId="skt-power-lock"/>
<channel id="ring_brightness" typeId="skt-ring-brightness"/>
</channels>
</channel-group-type>
<channel-type id="skt-power-switch">
<item-type>Switch</item-type>
<label>Power Switch</label>
<description>
This channel provides access to the power switch of the Energy Socket.
</description>
</channel-type>
<channel-type id="skt-power-lock" advanced="true">
<item-type>Switch</item-type>
<label>Power Lock</label>
<description>
This channel provides access to the power lock of the Energy Socket.
</description>
</channel-type>
<channel-type id="skt-ring-brightness">
<item-type unitHint="%">Number:Dimensionless</item-type>
<label>Ring Brightness</label>
<description>
This channel provides access to the brightness of the ring of the Energy Socket.
</description>
<state readOnly="true" pattern="%.0f %unit%"/>
</channel-type>
</thing:thing-descriptions>

48
_thing_types/org.openhab.binding.homewizard/src/main/resources/OH-INF/thing/hwe-wtr.xml Normal file
View File

@ -0,0 +1,48 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="homewizard"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<thing-type id="hwe-wtr">
<label>HomeWizard Watermeter</label>
<description>This thing provides the measurement data that is available through the API of a HomeWizard
Watermeter.</description>
<channel-groups>
<channel-group id="water" typeId="es-water-group"/>
</channel-groups>
<properties>
<property name="thingTypeVersion">1</property>
</properties>
<config-description-ref uri="thing-type:homewizard:device"/>
</thing-type>
<channel-group-type id="es-water-group">
<label>Recent Measurements</label>
<channels>
<channel id="active_liter" typeId="es-active-liter"/>
<channel id="total_liter" typeId="es-total-liter"/>
</channels>
</channel-group-type>
<channel-type id="es-active-liter">
<item-type>Number:VolumetricFlowRate</item-type>
<label>Active Liters</label>
<description>
This channel provides the active water usage in liters per minute.
</description>
</channel-type>
<channel-type id="es-total-liter">
<item-type>Number:Volume</item-type>
<label>Total Liters</label>
<description>
This channel provides total water usage in cubic meters.
</description>
</channel-type>
</thing:thing-descriptions>

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

@ -4,7 +4,7 @@
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<thing-type id="p1_wifi_meter">
<thing-type id="p1_wifi_meter" listed="false">
<label>HomeWizard Wi-Fi P1 Meter</label>
<description>This thing provides the measurement data that is available through the http interface of the HomeWizard
Wi-Fi P1 Meter.</description>
@ -75,7 +75,8 @@
</thing-type>
<thing-type id="energy_socket">
<thing-type id="energy_socket" listed="false">
<label>HomeWizard Energysocket</label>
<description>This thing provides the measurement data that is available through the http interface of a HomeWizard
Energysocket.</description>
@ -83,8 +84,8 @@
<channels>
<channel id="total_energy_import_t1" typeId="total_energy_import_t1"/>
<channel id="total_energy_export_t1" typeId="total_energy_export_t1"/>
<channel id="active_voltage" typeId="active_voltage"/>
<channel id="active_power" typeId="active_power"/>
<channel id="power_switch" typeId="power_switch"/>
<channel id="power_lock" typeId="power_lock"/>
<channel id="ring_brightness" typeId="ring_brightness"/>
@ -106,7 +107,7 @@
</thing-type>
<thing-type id="watermeter">
<thing-type id="watermeter" listed="false">
<label>HomeWizard Wi-Fi Watermeter</label>
<description>This thing provides the measurement data that is available through the http interface of a HomeWizard
Watermeter.</description>
@ -172,6 +173,14 @@
</description>
</channel-type>
<channel-type id="active_voltage">
<item-type>Number:ElectricPotential</item-type>
<label>Current Grid Voltage</label>
<description>
This channel provides the current grid voltage.
</description>
</channel-type>
<channel-type id="active_power">
<item-type>Number:Power</item-type>
<label>Current Total Net Power</label>
@ -179,6 +188,7 @@
This channel provides the current net total power in W. It will be below 0 if power is currently being
exported.
</description>
<state readOnly="true" pattern="%.1f %unit%"></state>
</channel-type>
<channel-type id="active_power_l1">
@ -244,6 +254,7 @@
<state readOnly="true" pattern="%.0f %unit%"/>
</channel-type>
<channel-type id="power_switch">
<item-type>Switch</item-type>
<label>Power Switch</label>

6
_thing_types/org.openhab.binding.jablotron/src/main/resources/OH-INF/thing/oasis.xml
View File

@ -22,9 +22,15 @@
<channel id="lastEventClass" typeId="lastEventClass"/>
<channel id="lastEventInvoker" typeId="lastEventInvoker"/>
<channel id="lastEventTime" typeId="lastEventTime"/>
<channel id="lastEventSection" typeId="lastEventSection"/>
<channel id="lastCheckTime" typeId="lastCheckTime"/>
<channel id="alarm" typeId="alarm"/>
</channels>
<properties>
<property name="thingTypeVersion">1</property>
</properties>
<config-description-ref uri="thing-type:jablotron:device"/>
</thing-type>

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

@ -16,18 +16,6 @@
<state min="0.0" max="35.0" step="0.5" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="temperature">
<item-type>Number:Temperature</item-type>
<label>Zone Temperature</label>
<description>Gets the temperature of this zone</description>
<category>heating</category>
<tags>
<tag>Measurement</tag>
<tag>Temperature</tag>
</tags>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="offsetTemperature">
<item-type>Number:Temperature</item-type>
<label>Thermostat Temperature Offset</label>
@ -64,13 +52,6 @@
</state>
</channel-type>
<channel-type id="power">
<item-type>Switch</item-type>
<label>Power</label>
<description>Switch the Plugwise Smart plug ON or OFF</description>
<category>switch</category>
</channel-type>
<channel-type id="lock">
<item-type>Switch</item-type>
<label>Lock</label>
@ -78,16 +59,6 @@
<category>switch</category>
</channel-type>
<channel-type id="powerUsage">
<item-type>Number:Power</item-type>
<label>Power Usage</label>
<tags>
<tag>Measurement</tag>
<tag>Power</tag>
</tags>
<state pattern="%.2f %unit%" readOnly="true"></state>
</channel-type>
<channel-type id="chState">
<item-type>Switch</item-type>
<label>Central Heating Active</label>

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

@ -65,13 +65,20 @@
<channels>
<channel id="setpointTemperature" typeId="setpointTemperature"/>
<channel id="temperature" typeId="temperature"/>
<channel id="temperature" typeId="system.indoor-temperature">
<label>Zone Temperature</label>
<description>Gets the temperature of this zone</description>
</channel>
<channel id="presetScene" typeId="presetScene"/>
<channel id="preHeat" typeId="preHeat"/>
<channel id="coolingAllowed" typeId="coolingAllowed"/>
<channel id="regulationControl" typeId="regulationControl"/>
</channels>
<properties>
<property name="thingTypeVersion">1</property>
</properties>
<representation-property>id</representation-property>
<config-description-ref uri="thing-type:plugwiseha:zone"/>
@ -88,12 +95,15 @@
<channels>
<channel id="setpointTemperature" typeId="setpointTemperature"/>
<channel id="temperature" typeId="temperature"/>
<channel id="temperature" typeId="system.indoor-temperature">
<label>Zone Temperature</label>
<description>Gets the temperature of this zone</description>
</channel>
<channel id="valvePosition" typeId="valvePosition"/>
</channels>
<properties>
<property name="thingTypeVersion">1</property>
<property name="thingTypeVersion">2</property>
</properties>
<representation-property>id</representation-property>
@ -111,11 +121,20 @@
<description>A Plugwise Home Automation smart plug switch connected to a central heating pump</description>
<channels>
<channel id="power" typeId="power"/>
<channel id="power" typeId="system.power">
<label>Power</label>
<description>Switch the Plugwise Smart plug ON or OFF</description>
</channel>
<channel id="lock" typeId="lock"/>
<channel id="powerUsage" typeId="powerUsage"/>
<channel id="powerUsage" typeId="system.electric-power">
<label>Power Usage</label>
</channel>
</channels>
<properties>
<property name="thingTypeVersion">1</property>
</properties>
<representation-property>id</representation-property>
<config-description-ref uri="thing-type:plugwiseha:appliance_pump"/>
@ -132,10 +151,17 @@
<channels>
<channel id="setpointTemperature" typeId="setpointTemperature"/>
<channel id="temperature" typeId="temperature"/>
<channel id="temperature" typeId="system.indoor-temperature">
<label>Zone Temperature</label>
<description>Gets the temperature of this zone</description>
</channel>
<channel id="offsetTemperature" typeId="offsetTemperature"/>
</channels>
<properties>
<property name="thingTypeVersion">1</property>
</properties>
<representation-property>id</representation-property>
<config-description-ref uri="thing-type:plugwiseha:appliance_thermostat"/>

26
_thing_types/org.openhab.binding.senseenergy/src/main/resources/OH-INF/thing/cloud-connector.xml Normal file
View File

@ -0,0 +1,26 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="senseenergy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<bridge-type id="cloud-connector">
<label>Sense Energy Cloud Connector</label>
<description>The Sense Home cloud connector establishes connection to the Sense cloud API and services.</description>
<config-description>
<parameter name="email" type="text" required="true">
<label>Email</label>
<context>text</context>
<description>Sense account email address</description>
<required>true</required>
</parameter>
<parameter name="password" type="text" required="true">
<label>Password</label>
<context>password</context>
<description>Sense account password</description>
<required>true</required>
</parameter>
</config-description>
</bridge-type>
</thing:thing-descriptions>

163
_thing_types/org.openhab.binding.senseenergy/src/main/resources/OH-INF/thing/monitor.xml Normal file
View File

@ -0,0 +1,163 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="senseenergy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<bridge-type id="monitor">
<supported-bridge-type-refs>
<bridge-type-ref id="cloud-connector"/>
</supported-bridge-type-refs>
<label>Sense Energy Monitor</label>
<description>Sense energy monitor instance.</description>
<channel-groups>
<channel-group id="general" typeId="general"/>
<channel-group id="discovered-devices" typeId="discovered-devices"/>
<channel-group id="self-reporting-devices" typeId="self-reporting-devices"/>
<channel-group id="proxy-devices" typeId="proxy-devices"/>
</channel-groups>
<properties>
<property name="solarConfigured"></property>
<property name="ipAddress"></property>
<property name="version"></property>
<property name="serial"></property>
<property name="ssid"></property>
<property name="mac"></property>
</properties>
<representation-property>id</representation-property>
<config-description>
<parameter name="id" type="integer">
<label>ID</label>
<description>Device ID (only known from the openHAB log or when devices is discovered).</description>
<required>true</required>
</parameter>
</config-description>
</bridge-type>
<channel-group-type id="general">
<label>General Information</label>
<description>General information about the monitor</description>
<channels>
<channel id="frequency" typeId="frequency"/>
<channel id="grid-power" typeId="grid-power"/>
<channel id="potential-1" typeId="potential-1"/>
<channel id="potential-2" typeId="potential-2"/>
<channel id="leg-1-power" typeId="leg-1-power"/>
<channel id="leg-2-power" typeId="leg-2-power"/>
<channel id="main-power" typeId="main-power"/>
<channel id="solar-power" typeId="solar-power"/>
<channel id="devices-updated-trigger" typeId="devices-updated-trigger"/>
</channels>
</channel-group-type>
<channel-group-type id="discovered-devices">
<label>Discovered Devices</label>
<description>Sense discovered devices</description>
</channel-group-type>
<channel-group-type id="self-reporting-devices">
<label>Self-Reporting Devices</label>
<description>Devices that self report their power to Sense</description>
</channel-group-type>
<channel-group-type id="proxy-devices">
<label>Proxy Devices</label>
<description>Proxy devices configured in openHAB which report their power</description>
</channel-group-type>
<channel-group-type id="device-template">
<label>Device</label>
<description>Discovered devices</description>
<channels>
<channel id="device-power" typeId="device-power"/>
<channel id="trigger" typeId="device-trigger"/>
</channels>
</channel-group-type>
<channel-type id="potential-1">
<item-type unitHint="V">Number:ElectricPotential</item-type>
<label>Potential 1</label>
<description>Potential measured on first 120V branch.</description>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="potential-2">
<item-type unitHint="V">Number:ElectricPotential</item-type>
<label>Potential 2</label>
<description>Potential measured on second 120V branch.</description>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="leg-1-power">
<item-type unitHint="W">Number:Power</item-type>
<label>Leg 1 Power</label>
<description>Power detected by the first Sense clamp.</description>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="leg-2-power">
<item-type unitHint="W">Number:Power</item-type>
<label>Leg 2 Power</label>
<description>Power detected by the second Sense clamp.</description>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="main-power">
<item-type unitHint="W">Number:Power</item-type>
<label>Main Power</label>
<description>Power detected by the main Sense clamp.</description>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="solar-power">
<item-type unitHint="W">Number:Power</item-type>
<label>Solar Power</label>
<description>Power detected by the solar Sense clamp.</description>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="grid-power">
<item-type unitHint="W">Number:Power</item-type>
<label>Grid Power</label>
<description>Power consumed from the grid (negative if supplying power to grid)</description>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="devices-updated-trigger" advanced="true">
<kind>trigger</kind>
<label>Discovered Devices Updated</label>
<description>Triggered when the discovered device list has been updated</description>
</channel-type>
<channel-type id="device-power">
<item-type unitHint="W">Number:Power</item-type>
<label>Power</label>
<description>Power draw of discovered device.</description>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="device-trigger" advanced="true">
<kind>trigger</kind>
<label>On Off Trigger</label>
<description>Triggered when the discovered device turns ON and OFF.</description>
<event>
<options>
<option value="ON">ON</option>
<option value="OFF">OFF</option>
</options>
</event>
</channel-type>
<channel-type id="frequency" advanced="true">
<item-type unitHint="Hz">Number:Frequency</item-type>
<label>Frequency</label>
<description>Electrical frequency detected by Sense.</description>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
</thing:thing-descriptions>

85
_thing_types/org.openhab.binding.senseenergy/src/main/resources/OH-INF/thing/proxy-device.xml Normal file
View File

@ -0,0 +1,85 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="senseenergy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<!-- Sense Home Energy Monitor Report Thing -->
<thing-type id="proxy-device">
<supported-bridge-type-refs>
<bridge-type-ref id="monitor"/>
</supported-bridge-type-refs>
<label>Proxy Device</label>
<description>
A proxy device to notify the sense monitor of real-time power draw. All channels are "one-way" in that
they only report their settings to Sense.
</description>
<channels>
<channel id="proxy-device-power" typeId="proxy-device-power"/>
<channel id="proxy-device-switch" typeId="proxy-device-switch"/>
<channel id="proxy-device-dimmer" typeId="proxy-device-dimmer"/>
<channel id="proxy-device-state" typeId="proxy-device-state"/>
</channels>
<config-description>
<parameter name="powerLevels" type="text">
<label>Power Levels</label>
<description>Power levels for different states. Examples: "5W" (static full ON power), ".2W, 5W" (for static power
range), "OFF=.2W, LOW=2W, HIGH=5W" (for static power in different states), ".2,2W,2.5W,3W" (for non-linear dimmer
rage".</description>
</parameter>
<parameter name="voltage" type="decimal" unit="V">
<label>Voltage</label>
<description>Supply voltage for device.</description>
<unitLabel>V</unitLabel>
<default>120</default>
<required>true</required>
</parameter>
<parameter name="macAddress" type="text">
<context>network-address</context>
<label>Spoof'd MAC Address</label>
<description>A spoof'ed MAC address for this proxy device.</description>
<advanced>true</advanced>
</parameter>
<parameter name="senseName" type="text">
<label>Sense Name</label>
<description>Name of device to be used by Sense.</description>
</parameter>
</config-description>
</thing-type>
<channel-type id="proxy-device-power">
<item-type>Number:Power</item-type>
<label>Power Level</label>
<description>Realtime power to send to Sense. Note, if you are using the Switch, Dimmer or State channels, it is not
necessary to use this channel.</description>
<state pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="proxy-device-switch">
<item-type>Switch</item-type>
<label>Device Switch</label>
<description>OnOff switch to notify when device is On/Off. This will report to sense the full ON or full OFF values
specified.
</description>
</channel-type>
<channel-type id="proxy-device-dimmer">
<item-type>Dimmer</item-type>
<label>Device Dimmer</label>
<description>Dimmer to notify the current power. This will report to sense an interpolated value based on the
specified levels.</description>
</channel-type>
<channel-type id="proxy-device-state">
<item-type>String</item-type>
<label>Device State</label>
<description>Current device state. This will report to sense the specified power based on the device state.</description>
</channel-type>
</thing:thing-descriptions>

270
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/fibaro/fgr224_0_0.xml Normal file
View File

@ -0,0 +1,270 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="fibaro_fgr224_00_000" listed="false">
<label>FGR224 Roller Shutter 4</label>
<description><![CDATA[
Roller Shutter 4<br /> <h1>Overview</h1><p>FIBARO ROLLER SHUTTER 4 is designed for controlling roller blinds, awnings, blinds, curtains and pergolas.</p><p>FIBARO ROLLER SHUTTER 4 enables the precise positioning of roller blinds or blind blades. The device is equipped with energy monitoring. The device is equipped with energy monitoring. It enables you to control connected devices either through the Z-Wave® network through or a switch connected directly to it.</p> <br /> <h2>Inclusion Information</h2><p>Add (inclusion) – the Z-Wave device learning mode allows you to add the device to the existing Z-Wave network.</p><p>Manually adding the device to the Z-Wave network</p><ol><li>Turn on the device. If the device has not been added to the Z-Wave network, the LED indicator of the device will light up red.</li><li>Set the main control unit to the Security/Non-Safety Additional mode (see the ECU manual for more information).</li><li>Quickly click the PROG button on the device three times. Alternatively, you can click on S1 or S2 three times.</li><li>If you add the device in Security S2 Authenticated mode, enter the PIN code specified on the device. The PIN code is also a underlined part of the device-specific key (DSK) specified at the bottom of the field.</li><li>Wait until the LED indicator flashes yellow.</li><li>Successful adding is confirmed by the reporting of the Z-Wave controller and the LED display of the device:</li></ol><p> Green – successful (not secure, S0, S2 not authenticated)</p><p> Magenta – successful (Safety S2 authenticated)</p><p> Red – not successful</p><p><br /></p><p>Adding the device to the Z-Wave network with SmartStart</p><p>SmartStart solution allows you to add products to the Z-Wave network by scanning the Z-Wave QR code located on the product, with a controller that enables SmartStart integration. A SmartStart product is automatically included in the network area within 10 minutes of turning it on.</p><p>iTo use SmartStart, your ECU must support Security S2 mode (see the control unit's manual for more information).</p><ol><li>Enter the full DSK string code in your ECU. If your ECU supports a QR scan, scan the QR code on the label.</li><li>Supply the device with power (on switch on the mains voltage).</li><li>The LED indicator starts to flash yellow. Wait until the addition process is finished.</li><li>Successful adding is confirmed by the reporting of the Z-Wave controller and the LED display of the device:</li></ol><p> Green – successful (not secure, S0, S2 not authenticated)</p><p> Magenta – successful (Safety S2 authenticated)</p><p> Red – not successful</p><p>if you have any problems adding the device, please reset it and repeat the process.</p> <br /> <h2>Exclusion Information</h2><p>Remove (exclude) – the Z-Wave device learning mode makes it possible to remove the device from the existing Z Wave network.</p><ol><li>Make sure the device is turned on</li><li>Switch the main controller to the removal mode (see the controller's operating instructions for more information).</li><li>Quickly click the PROG button three times. Alternatively, you can click S1 or S2 three times within 10 minutes after turning on the device.</li><li>Wait until the removal process is finished.</li><li>The successful removal is confirmed by a reporting from the Z-Wave controller. The LED indicator lights red.</li></ol><p>Removing the device from the Z-Wave network does not result in a factory reset.</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>Blinds</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="blinds_control" typeId="blinds_control">
<label>Blinds Control</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
<property name="binding:Command:StopMoveType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:UpDownType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
<channel id="meter_kwh" typeId="meter_kwh">
<label>Electric meter (kWh)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_KWh</property>
</properties>
</channel>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE</property>
</properties>
</channel>
<channel id="alarm_power" typeId="alarm_power">
<label>Alarm (power)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
</properties>
</channel>
<channel id="alarm_system" typeId="alarm_system">
<label>Alarm (system)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=SYSTEM</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Fibargroup</property>
<property name="modelId">FGR224</property>
<property name="manufacturerId">010F</property>
<property name="manufacturerRef">0304:1000</property>
<property name="dbReference">1654</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_20_1" type="integer" groupName="configuration">
<label>20: Switch type</label>
<description><![CDATA[
Defines switch type<br /> <h1>Overview</h1><p>This parameter determines with which switches types and in which mode the S1 and S2 inputs operate.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Monostable switches – click to move</option>
<option value="1">Monostable switches – hold to move</option>
<option value="2">Single monostable switch</option>
<option value="3">Bistable switches</option>
<option value="4">Single bistable switch</option>
<option value="5">Three-state switch</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_24_1" type="integer" groupName="configuration">
<label>24: Buttons orientation</label>
<description><![CDATA[
Defines buttons orientation<br /> <h1>Overview</h1><p>This parameter allows reversing the operation of the buttons.</p>
]]></description>
<default>0</default>
<options>
<option value="0">default (1st button UP, 2nd button DOWN)</option>
<option value="1">reversed (1st button DOWN, 2nd button UP)</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_25_1" type="integer" groupName="configuration">
<label>25: Outputs orientation</label>
<description><![CDATA[
Defines outputs orientation<br /> <h1>Overview</h1><p>This parameter allows reversing the operation of O1 and O2 without changing the wiring (e.g. in case of invalid motor connection).</p>
]]></description>
<default>0</default>
<options>
<option value="0">default (O1 – UP, O2 – DOWN)</option>
<option value="1">reversed (O1 – DOWN, O2 – UP)</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_40_1" type="integer" groupName="configuration">
<label>40: First button – scenes sent</label>
<description><![CDATA[
Defines first button scenes sent<br /> <h1>Overview</h1><p>This parameter determines which actions result in sending scene IDs assigned to them. Values can be combined (e.g. 1+2=3 means that scenes for single and double click are sent). Enabling scenes for triple click disables entering the device in learn mode by triple clicking.</p>
]]></description>
<default>15</default>
<options>
<option value="0">No scene active</option>
<option value="1">Key pressed 1 time</option>
<option value="2">Key pressed 2 times</option>
<option value="4">Key pressed 3 times</option>
<option value="8">Key hold down and key released</option>
<option value="15">default - All scenes active</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_41_1" type="integer" groupName="configuration">
<label>41: Second button – scenes sent</label>
<description><![CDATA[
Defines first button scenes sent<br /> <h1>Overview</h1><p>This parameter determines which actions result in sending scene IDs assigned to them. Values can be combined (e.g. 1+2=3 means that scenes for single and double click are sent). Enabling scenes for triple click disables entering the device in learn mode by triple clicking.</p>
]]></description>
<default>0</default>
<options>
<option value="0">No scene active</option>
<option value="1">Key pressed 1 time</option>
<option value="2">Key pressed 2 times</option>
<option value="4">Key pressed 3 times</option>
<option value="8">Key hold down and key released</option>
<option value="15">default - All scenes active</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_150_1" type="integer" groupName="configuration">
<label>150: Calibration</label>
<description><![CDATA[
Calibration<br /> <h1>Overview</h1><p>To start automatic calibration, select the value 3. When the calibration process is successful, the parameter takes the value 1. When automatic calibration fails, the parameter takes the value 2. If the transitions times for the device are changed manually in the parameter (156/157), the parameter 150 will takes the value 4.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Device is not calibrated</option>
<option value="1">Autocalibration successful</option>
<option value="2">Autocalibration failed</option>
<option value="3">Calibration process</option>
<option value="4">Manual calibration</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_151_1" type="integer" groupName="configuration">
<label>151: Operating mode</label>
<description><![CDATA[
Operating mode<br /> <h1>Overview</h1><p>This parameter allows you to adjust the operation, depending on the connected device. In the case of venetian blinds, the angle of rotation of the slats must also be selected.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Roller blind, Awning, Pergola, Curtain</option>
<option value="1">Venetian blind 90°</option>
<option value="2">Venetian blind 180°</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_152_2" type="integer" groupName="configuration">
<label>152: Venetian blind - slats full turn time</label>
<description><![CDATA[
Venetian blind - slats full turn time<br /> <h1>Overview</h1><p>For Venetian blinds the parameter determines time of full turn cycle of the slats. The parameter is irrelevant for other modes.</p><p>Default: 15 (1.5 seconds) <br /></p><p>Range: 0-65535 (0 - 6553.5s, every 0.1s) - time of turn</p>
]]></description>
<default>15</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_156_2" type="integer" groupName="configuration">
<label>156: Time of up movement</label>
<description><![CDATA[
Time of up movement<br /> <h1>Overview</h1><p>This parameter determines the time it takes to reach full opening. The value is set automatically during the calibration process. It should be manually set in case of problems with the autocalibration.</p><p>Default: 600 (60 seconds)</p><p>Range: 0-65535 (0 - 6553.5s, every 0.1s) - time of turn</p>
]]></description>
<default>600</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_157_2" type="integer" groupName="configuration">
<label>157: Time of down movement</label>
<description><![CDATA[
Time of down movement<br /> <h1>Overview</h1><p>This parameter determines the time it takes to reach full closure. The value is set automatically during the calibration process. It should be manually set in case of problems with the autocalibration.</p><p>Default: 600 (60 seconds)</p><p>Range: 0-65535 (0 - 6553.5s, every 0.1s) - time of turn</p>
]]></description>
<default>600</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_158_1" type="integer" groupName="configuration">
<label>158: Virtual limit switch. The pot protection</label>
<description><![CDATA[
Virtual limit switch. The pot protection<br /> <h1>Overview</h1><p>This parameter allows you to set a fixed minimum level of lowering the shutter. For example, to protect a flowerpot located on a windowsill.</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_159_1" type="integer" groupName="configuration">
<label>159: Favorite position - opening level</label>
<description><![CDATA[
Favorite position - opening level<br /> <h1>Overview</h1><p>This parameter allows you to define your favorite aperture level.</p><p>Range: 0-99</p><p>0xFF - Functionality disabled</p>
]]></description>
<default>50</default>
<options>
<option value="255">Functionality disabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_160_1" type="integer" groupName="configuration">
<label>160: Favorite position - slat angle</label>
<description><![CDATA[
Favorite position - slat angle<br /> <h1>Overview</h1><p>This parameter allows you to define your favorite position of the slat angle. The parameter is used only for venetian blinds.</p><p>Range: 0-99</p><p>0xFF - Functionality disabled</p>
]]></description>
<default>50</default>
<options>
<option value="255">0xFF - Functionality disabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description><![CDATA[
General: Lifeline<br /> <h1>Overview</h1><p>1st association group – “Lifeline” reports the device status and allows for assigning single device only (main controller by default).</p>
]]></description>
<multipleLimit>1</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Window Covering</label>
<description><![CDATA[
Control: KEY01 (0x20: 0x01)<br /> <h1>Overview</h1><p>2nd association group – “Window Covering” is intended for curtains or blinds allowing the user to control the amount of light going through windows.</p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

189
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/nexa/zpr111_0_0.xml Normal file
View File

@ -0,0 +1,189 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="nexa_zpr111_00_000" listed="false">
<label>ZPR-111 Plug-in Switch with enery meter</label>
<description><![CDATA[
Plug-in Switch with enery meter<br /> <h1>Overview</h1><p>Z-Wave plugin receiver (On/Off) with power consumption measurement function, LED indicator, built-in switch-off timer and on/off button.<br /></p> <br /> <h2>Inclusion Information</h2><p>Press the link button three times within 1.5 seconds; the LED flashes Yellow 5 times.<br /></p> <br /> <h2>Exclusion Information</h2><p>Press the link button three times within 1.5 seconds: the LED flashes Purple 5 times.<br /></p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>PowerOutlet</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_binary" typeId="switch_binary">
<label>Switch</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY</property>
</properties>
</channel>
<channel id="meter_kwh" typeId="meter_kwh">
<label>Electric meter (kWh)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_KWh</property>
</properties>
</channel>
<channel id="meter_watts" typeId="meter_watts">
<label>Electric meter (watts)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_W</property>
</properties>
</channel>
<channel id="meter_voltage" typeId="meter_voltage">
<label>Electric meter (volts)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_V</property>
</properties>
</channel>
<channel id="meter_current" typeId="meter_current">
<label>Electric meter (amps)</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_METER;type=E_A</property>
</properties>
</channel>
<channel id="alarm_power" typeId="alarm_power">
<label>Alarm (power)</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=POWER_MANAGEMENT</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Nexa</property>
<property name="modelId">ZPR-111</property>
<property name="manufacturerId">0268</property>
<property name="manufacturerRef">0002:1027</property>
<property name="dbReference">1653</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration">
<label>1: Send meter report enable</label>
<description><![CDATA[
This parameter defines Enable/Disable meter report measure data to controller (default Enable).<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<options>
<option value="0">Disable</option>
<option value="1">Enable</option>
</options>
</parameter>
<parameter name="config_2_2" type="integer" groupName="configuration">
<label>2: Meter report interval</label>
<description><![CDATA[
Defines the time interval that meter report data to main controller (default 300s).<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>300</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_1" type="integer" groupName="configuration">
<label>3: Upper current threshold</label>
<description><![CDATA[
Defines the maximum current before the plug will cut off power (default 13A).<br /> <h1>Overview</h1><p>This parameter defines maximum current the plug can provide to load that be connected to plug. If the current consumed by load greater than maximum current, the plug will cut off power.<br /></p>
]]></description>
<default>13</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration">
<label>4: Upper current threshold alarm</label>
<description><![CDATA[
Defines the over current alarm threshold (default 12A)<br /> <h1>Overview</h1><p>This parameter defines maximum current. If the current the plug provides to the load is greater than this parameter, the plug will send over-current notification to main controller and the LED will be turn RED. This value must be less than parameter #3.<br /></p>
]]></description>
<default>12</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_1" type="integer" groupName="configuration">
<label>5: Led display enable</label>
<description><![CDATA[
Defines the LED indication function ON/OFF (default ON).<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<options>
<option value="0">Off</option>
<option value="1">On</option>
</options>
</parameter>
<parameter name="config_6_1" type="integer" groupName="configuration">
<label>6: Power reporting setting</label>
<description><![CDATA[
Defines by how much consumed power must change to be reported to the Z-Wave Controller (default 30%).<br /> <h1>Overview</h1><p>This parameter defines by how much power consumed must change to be reported to the Z-Wave Controller or Z-Wave Gateway, in percents.</p><p>If the rate of power consumed change ratio is greater than this parameter, the plug will report the results, voltage, current, power and energy, that plug measure to Z-Wave Controller or Z-Wave Gateway. </p>
]]></description>
<default>30</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_1" type="integer" groupName="configuration">
<label>7: Remember relay status</label>
<description><![CDATA[
Defines if the relay status is remembered or not after a power cut (default Remember).<br /> <h1>Overview</h1><p>This parameter defined the relay status if remember or not. If remembered, the plug will restore the relay status last power off when the plug supply power next time.<br /></p>
]]></description>
<default>1</default>
<options>
<option value="0">Do not Remember</option>
<option value="1">Remember</option>
</options>
</parameter>
<parameter name="config_8_1" type="integer" groupName="configuration">
<label>8: Time switch enable/disable</label>
<description><![CDATA[
Defines switch timer function Enable/Disable (default Disable).<br /> <h1>Overview</h1><p>This parameter defines the timer function Enable/Disable. The time period will be defined in parameter #9. If this parameter is set to 1, and when turn the plug relay on, the timer in plug start run with time period defined in parameter #9 and the plug will turn the relay off.<br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">Disable</option>
<option value="1">Enable</option>
</options>
</parameter>
<parameter name="config_9_2" type="integer" groupName="configuration">
<label>9: Time switch period</label>
<description><![CDATA[
Defines the time period before the plug is switched off (default 150m).<br /> <h1>Overview</h1><p>This parameter defines the time period that plug time switch off.</p><p>If Parameter #8 is set to 1, and relay is turn-on, the relay will be turn-off after delay this parameter.</p>
]]></description>
<default>150</default>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<multipleLimit>1</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

28
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/shelly/waveplugus_0_0.xml → _thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/shelly/waveplug_0_0.xml
View File

@ -5,10 +5,10 @@
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="shelly_waveplugus_00_000" listed="false">
<label>Wave Plug US Plug On Off with Energy Meter</label>
<thing-type id="shelly_waveplug_00_000" listed="false">
<label>Wave Plug Plug On Off with power measurement</label>
<description><![CDATA[
Plug On Off with Energy Meter<br /> <h1>Overview</h1><p>The Wave Plug US (Device) is a smart plug/outlet with power measurement and overheating protection, which allows remote control of electric appliances through a mobile phone, tablet, PC, or home automation system.<br /></p> <br /> <h2>Inclusion Information</h2><p>SmartStart adding (inclusion)</p><p>SmartStart enabled products can be added into a Z-Wave® network by scanning the Z-Wave® QR Code present on the Device with a gateway providing SmartStart inclusion. No further action is required, and the SmartStart device will be added automatically within 10 minutes of being switched on in the network vicinity.</p><p>With the gateway application scan the QR code on the Device label and add the Security 2 (S2) Device Specific Key (DSK) to the provisioning list in the gateway.</p><p>Connect the Device to a power supply.</p><p>Check if the blue LED is blinking in Mode 1. If so, the Device is not added to a Z-Wave® network.</p><p>Adding will be initiated automatically within a few seconds after connecting the Device to a power supply, and the Device will be added to a Z-Wave® network automatically.</p><p>The blue LED will be blinking in Mode 2 during the adding process.</p><p>The green LED will be blinking in Mode 1 if the Device is successfully added to a Z-Wave® network.</p><p>Adding (inclusion) with the S button</p><p>Connect the Device to a power supply.</p><p>Check if the blue LED is blinking in Mode 1. If so, the Device is not added to a Z-Wave® network.</p><p>Enable add/remove mode on the gateway.</p><p>To enter the Setting mode, press and hold the S button on the Device until the LED turns solid blue.</p><p>Release and then press and hold (&gt; 2s) the S button on the Device until the blue LED starts blinking in Mode 3. Releasing the S button will start the Learn mode.</p><p>The blue LED will be blinking in Mode 2 during the adding process.</p><p>The green LED will be blinking in Mode 1 if the Device is successfully added to a Z-Wave® network.</p> <br /> <h2>Exclusion Information</h2><p>Removing (exclusion) with the S button</p><p>Connect the Device to a power supply.</p><p>Check if the green LED is blinking in Mode 1. If so, the Device is added to a Z-Wave® network.</p><p>Enable add/remove mode on the gateway.</p><p>To enter the Setting mode, press and hold the S button on the Device until the LED turns solid blue.</p><p>Release and then press and hold (&gt; 2s) the S button on the Device until the blue LED starts blinking in Mode 3. Releasing the S button will start the LEARN MODE.</p><p>The blue LED will be blinking in Mode 2 during the removing process.</p><p>The blue LED will be blinking in Mode 1 if the Device is successfully removed from a Z-Wave® network.</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
Plug On Off with power measurement<br /> <h1>Overview</h1><p>The Wave Plug (Device) is a smart plug/outlet with power measurement and overheating protection, which allows remote control of electric appliances through a mobile phone, tablet, PC, or home automation system.<br /></p> <br /> <h2>Inclusion Information</h2><p>SmartStart adding (inclusion)</p><p>SmartStart enabled products can be added into a Z-Wave® network by scanning the Z-Wave® QR Code present on the Device with a gateway providing SmartStart inclusion. No further action is required, and the SmartStart device will be added automatically within 10 minutes of being switched on in the network vicinity.</p><p>With the gateway application scan the QR code on the Device label and add the Security 2 (S2) Device Specific Key (DSK) to the provisioning list in the gateway.</p><p>Connect the Device to a power supply.</p><p>Check if the blue LED is blinking in Mode 1. If so, the Device is not added to a Z-Wave® network.</p><p>Adding will be initiated automatically within a few seconds after connecting the Device to a power supply, and the Device will be added to a Z-Wave® network automatically.</p><p>The blue LED will be blinking in Mode 2 during the adding process.</p><p>The green LED will be blinking in Mode 1 if the Device is successfully added to a Z-Wave® network.</p><p>Adding (inclusion) with the S button</p><p>Connect the Device to a power supply.</p><p>Check if the blue LED is blinking in Mode 1. If so, the Device is not added to a Z-Wave® network.</p><p>Enable add/remove mode on the gateway.</p><p>To enter the Setting mode, press and hold the S button on the Device until the LED turns solid blue.</p><p>Release and then press and hold (&gt; 2s) the S button on the Device until the blue LED starts blinking in Mode 3. Releasing the S button will start the Learn mode.</p><p>The blue LED will be blinking in Mode 2 during the adding process.</p><p>The green LED will be blinking in Mode 1 if the Device is successfully added to a Z-Wave® network.</p> <br /> <h2>Exclusion Information</h2><p>Removing (exclusion) with the S button</p><p>Connect the Device to a power supply.</p><p>Check if the green LED is blinking in Mode 1. If so, the Device is added to a Z-Wave® network.</p><p>Enable add/remove mode on the gateway.</p><p>To enter the Setting mode, press and hold the S button on the Device until the LED turns solid blue.</p><p>Release and then press and hold (&gt; 2s) the S button on the Device until the blue LED starts blinking in Mode 3. Releasing the S button will start the LEARN MODE.</p><p>The blue LED will be blinking in Mode 2 during the removing process.</p><p>The blue LED will be blinking in Mode 1 if the Device is successfully removed from a Z-Wave® network.</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>PowerOutlet</category>
@ -61,9 +61,9 @@ Plug On Off with Energy Meter<br /> <h1>Overview</h1><p>The Wave Plug US (Device
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Shelly</property>
<property name="modelId">Wave Plug US</property>
<property name="modelId">Wave Plug</property>
<property name="manufacturerId">0460</property>
<property name="manufacturerRef">0002:0088</property>
<property name="manufacturerRef">0002:0088,0002:0089</property>
<property name="dbReference">1642</property>
<property name="defaultAssociations">1</property>
</properties>
@ -182,6 +182,15 @@ This parameter determines how the device should respond to the reports of alarm
<advanced>true</advanced>
</parameter>
<parameter name="config_105_1" type="integer" groupName="configuration">
<label>105: LED Signalisation intensity</label>
<description><![CDATA[
In Wave 1, Wave 1PM and Wave 2PM, this parameter will be implemented in 2024. This parameter determines the intensity of the LED on the Device. Some Devices have RGB LEDs and some have Blue/Red LEDs, but all are dimmable.<br /> <h1>Overview</h1><p>Values &amp; descriptions:</p><p> 0-100 (0-100%, every 1%)</p>
]]></description>
<default>100</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_117_1" type="integer" groupName="configuration">
<label>117: Remote Device reboot</label>
<description>This parameter enable restarting or rebooting the Device without physical intervention. Use this parameter only for troubleshooting scope. After device reboot value will be set to default</description>
@ -189,6 +198,15 @@ This parameter determines how the device should respond to the reports of alarm
<advanced>true</advanced>
</parameter>
<parameter name="config_120_4" type="integer" groupName="configuration">
<label>120: Factory Reset</label>
<description><![CDATA[
Reset to factory default settings and removed from the Z-Wave network.<br /> <h1>Overview</h1><p>Values &amp; descriptions:</p><p>0 - Don’t do Factory reset</p><p>1431655765 - Do the Factory reset (hex 0x55555555)</p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_201_4" type="integer" groupName="configuration" readOnly="true">
<label>201: Serial Number 1</label>
<description>This parameter contains a part of device’s serial number.</description>

180
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/simontech/1000203413x_0_0.xml Normal file
View File

@ -0,0 +1,180 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="zwave"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0
https://openhab.org/schemas/thing-description/v1.0.0">
<thing-type id="simontech_1000203413x_00_000" listed="false">
<label>10002080-13x Simon IO: Roller Blind</label>
<description><![CDATA[
Simon IO: Roller Blind<br /> <h1>Overview</h1><p>Roller Blind IO is ready to operate with Z-Wave controllers and configured to be managed by Simon100 IO APP using the HUB plug IO for getting a better user experience. Sending the Blind Up/Down or setting a specific position.</p> <br /> <h2>Inclusion Information</h2><p>When the pushbutton is released after a press of (2&lt;T&lt;10sec) the device will send a NIF to include from Z-Wave network or perform an association with other Z-Wave device.</p> <p>Central LED will Blink with 0,3 sec period to inform that NIF can be send after release of pushbutton.</p> <p>This process does not perform a default reset of configurations.</p> <p>Main LED will Blink with 0,3 sec period to inform that NIF can be send after release of pushbutton.</p> <br /> <h2>Exclusion Information</h2><p>When the pushbutton is released after a press of (2&lt;T&lt;10sec) the device will send a NIF to exclude from Z-Wave network or perform an association with other Z-Wave device.</p> <p>Main LED will Blink with 0,3 sec period to inform that NIF can be send after release of pushbutton.</p> <p>This process does not perform a default reset of configurations.</p> <p>Main LED will Blink with 0,3 sec period to inform that NIF can be send after release of pushbutton.</p>
]]></description>
<category>Blinds</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="blinds_control" typeId="blinds_control">
<label>Blinds Control</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
<property name="binding:Command:StopMoveType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:UpDownType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">SimonTech S.L.U</property>
<property name="modelId">10002080-13x</property>
<property name="manufacturerId">0267</property>
<property name="manufacturerRef">0004:0000,0004:0022,0004:0063,0004:0091,0004:0092,0004:0093,0004:0094,0004:0177</property>
<property name="dbReference">930</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->
<config-description>
<!-- GROUP DEFINITIONS -->
<parameter-group name="configuration">
<context>setup</context>
<label>Configuration Parameters</label>
</parameter-group>
<parameter-group name="association">
<context>link</context>
<label>Association Groups</label>
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration">
<label>1: Association LED</label>
<description>Activates the Central LED.</description>
<default>0</default>
<options>
<option value="0">Turns the LED OFF (default)</option>
<option value="255">Turns the LED ON</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration" readOnly="true">
<label>4: Up Time</label>
<description>Up Time</description>
<default>60</default>
<options>
<option value="1">Sets the UP time in seconds</option>
<option value="60">Default</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_5_1" type="integer" groupName="configuration">
<label>5: Down Time</label>
<description><![CDATA[
Down Time<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>60</default>
<options>
<option value="1">Sets the DOWN time in seconds</option>
<option value="60">Default</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_9_1_wo" type="integer" groupName="configuration">
<label>9: Calibration</label>
<description><![CDATA[
Calibration<br /> <h1>Overview</h1><p>255 - The device will perform a calibration process in order to Set the UP and DOWN times automatically</p>
]]></description>
<default>-1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_12_1" type="integer" groupName="configuration">
<label>12: Behavior of LED in Repose</label>
<description>Configuration of Main LED as identification at 20%.</description>
<default>0</default>
<options>
<option value="0">LED OFF</option>
<option value="255">LED ON at 20% of maximum level</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_13_1" type="integer" groupName="configuration">
<label>13: Lock Input</label>
<description>Unlock/lock the direct control of load.</description>
<default>0</default>
<options>
<option value="0">Unlock the direct control of load.</option>
<option value="255">Lock the direct control of load.</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_21_2" type="integer" groupName="configuration" readOnly="true">
<label>21: Load State</label>
<description>Load State (Read Only)</description>
<default>0</default>
<options>
<option value="0">Bit 0: Load is OFF</option>
<option value="0">Bit 1: Sunblind position 0%</option>
<option value="1">Bit 0: Load is going UP/DOWN</option>
<option value="99">Bit 1: Sunblind position 99%</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_23_1" type="integer" groupName="configuration" readOnly="true">
<label>23: Calibration Required</label>
<description>Calibration Required (Read Only)</description>
<default>0</default>
<options>
<option value="0">Calibration is not required.</option>
<option value="255">It is necessary to calibrate the device.</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_27_1" type="integer" groupName="configuration">
<label>27: Lock long press</label>
<description>7 Lock long press</description>
<default>0</default>
<options>
<option value="0">Long press works as default.</option>
<option value="255">Long press works as overview.</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association" multiple="true">
<label>1: Lifeline</label>
<description><![CDATA[
Lifeline<br /> <h1>Overview</h1><p>Change on Sunblind position:</p> <ul> <li>On -&gt; CC Basic, Basic Report.</li> <li>Value 0x01 - 0x63 Report sunblind position</li> </ul> <p>Calibration requirement change. (If device needs to be calibrated and is Added into a ZWave network, it will report after receive an Association Set of life line).</p> <ul> <li>Calibration required -&gt; CC Configuration, Configuration Report, Param 23, Value 0xF</li> <li>Calibration not required -&gt; CC Configuration, Configuration Report, Param 23, Value 0x00</li> </ul>
]]></description>
<multipleLimit>3</multipleLimit>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: ctrl</label>
<description><![CDATA[
Control<br /> <h1>Overview</h1><p>Change on Sunblind position:</p> <ul> <li>CC Basic, Basic Report.</li> <li>Value 0x00 - 0x63 Report sunblind position</li> </ul>
]]></description>
<multipleLimit>20</multipleLimit>
</parameter>
<!-- STATIC DEFINITIONS -->
<parameter name="node_id" type="integer" min="1" max="232" readOnly="true" required="true">
<label>Node ID</label>
<advanced>true</advanced>
</parameter>
</config-description>
</thing-type>
</thing:thing-descriptions>

4
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/simontech/1000x080x_0_0.xml
View File

@ -17,7 +17,7 @@ S100 iO Roller Blind (2023)<br /> <h1>Overview</h1><p>Roller Blind IO is ready t
<channel id="blinds_control" typeId="blinds_control">
<label>Blinds Control</label>
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:*:PercentType">COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC</property>
<property name="binding:Command:StopMoveType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
<property name="binding:Command:UpDownType">COMMAND_CLASS_SWITCH_MULTILEVEL</property>
</properties>
@ -31,7 +31,7 @@ S100 iO Roller Blind (2023)<br /> <h1>Overview</h1><p>Roller Blind IO is ready t
<property name="manufacturerId">0267</property>
<property name="manufacturerRef">0102:0000</property>
<property name="dbReference">1580</property>
<property name="defaultAssociations">2</property>
<property name="defaultAssociations">1</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->