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

pull/1685/head
openHAB Build Server 2021-11-13 09:14:59 +00:00
parent ba6e2b6117
commit 018a586f54
79 changed files with 2704 additions and 2306 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

149
_addons_bindings/airquality/readme.md
View File

@ -26,26 +26,32 @@ To use this binding, you first need to [register and get your API token](https:/
## Supported Things
There is exactly one supported thing type, which represents the air quality information for an observation location.
It has the `aqi` id.
Of course, you can add multiple Things, e.g. for measuring AQI for different locations.
Bridge: The binding supports a bridge to connect to the [AQIcn.org service](https://aqicn.org). A bridge uses the thing ID "api".
Station: Represents the air quality information for an observation location.
Of course, you can add multiple Stations, e.g. for measuring AQI for different locations.
## Discovery
Local Air Quality can be autodiscovered based on system location.
You will have complete default configuration with your apiKey.
You will created a Bridge with your apiKey.
## Binding Configuration
## Bridge Configuration
The binding has no configuration options, all configuration is done at Thing level.
## Thing Configuration
The thing has a few configuration parameters:
The bridge configuration only holds the api key :
| Parameter | Description |
|-----------|-------------------------------------------------------------------------|
| apiKey | Data-platform token to access the AQIcn.org service. Mandatory. |
## Thing Configuration
The 'Station' thing has a few configuration parameters:
| Parameter | Description |
|-----------|-------------------------------------------------------------------------|
| apikey | Data-platform token to access the AQIcn.org service. Mandatory. |
| location | Geo coordinates to be considered by the service. |
| stationId | Unique ID of the measuring station. |
| refresh | Refresh interval in minutes. Optional, the default value is 60 minutes. |
@ -60,59 +66,75 @@ For the location parameter, the following syntax is allowed (comma separated lat
If you always want to receive data from specific station and you know its unique ID, you can enter it instead of the coordinates.
This `stationId` can be found by using the following link:
https://api.waqi.info/search/?token=TOKEN&keyword=NAME, replacing TOKEN by your apikey and NAME by the station you are looking for.
https://api.waqi.info/search/?token=TOKEN&keyword=NAME, replacing TOKEN by your apiKey and NAME by the station you are looking for.
### Thing properties
Once created, at first execution, the station's properties will be filled with informations gathered from the web service :
- Nearest measuring station location
- Measuring station ID
- Latitude/longitude of measuring station
## Channels
The AirQuality information that is retrieved is available as these channels:
The AirQuality information that is retrieved for a given is available as these channels:
### AQI Channels Group - Global Results
| Channel ID | Item Type | Description |
|-----------------|----------------------|----------------------------------------------|
| alert-level | Number | Alert level (*) associated to AQI Index. |
| index | Number | Air Quality Index |
| timestamp | DateTime | Observation date and time |
| dominent | String | Dominent Pollutant |
| icon | Image | Pictogram associated to alert-level |
| color | Color | Color associated to alert level. |
### Weather Channels Group
| Channel ID | Item Type | Description |
|-----------------|----------------------|----------------------------------------------|
| aqiLevel | Number | Air Quality Index |
| aqiColor | Color | Color associated to given AQI Index. |
| aqiDescription | String | AQI Description |
| locationName | String | Nearest measuring station location |
| stationId | Number | Measuring station ID |
| stationLocation | Location | Latitude/longitude of measuring station |
| pm25 | Number | Fine particles pollution level (PM2.5) |
| pm10 | Number | Coarse dust particles pollution level (PM10) |
| o3 | Number | Ozone level (O3) |
| no2 | Number | Nitrogen Dioxide level (NO2) |
| co | Number | Carbon monoxide level (CO) |
| so2 | Number | Sulfur dioxide level (SO2) |
| observationTime | DateTime | Observation date and time |
| temperature | Number:Temperature | Temperature in Celsius degrees |
| pressure | Number:Pressure | Pressure level |
| humidity | Number:Dimensionless | Humidity level |
| dominentpol | String | Dominent Polutor |
| dew-point | Number:Temperature | Dew point temperature |
| wind-speed | Number:Speed | Wind speed |
`AQI Description` item provides a human-readable output that can be interpreted e.g. by MAP transformation.
### Pollutants Channels Group
For each pollutant (PM25, PM10, O3, NO2, CO, SO2) , depending upon availability of the station,
you will be provided with the following informations
| Channel ID | Item Type | Description |
|-----------------|----------------------|----------------------------------------------|
| value | Number:Density | Measured density of the pollutant |
| index | Number | AQI Index of the single pollutant |
| alert-level | Number | Alert level associate to the index |
(*) The alert level is described by a color :
| Code | Color | Description |
|------|--------|--------------------------------|
| 0 | Green | Good |
| 1 | Yellow | Moderate |
| 2 | Orange | Unhealthy for Sensitive Groups |
| 3 | Red | Unhealthy |
| 4 | Purple | Very Unhealthy |
| 5 | Maroon | Hazardous |
*Note that channels like* `pm25`, `pm10`, `o3`, `no2`, `co`, `so2` *can sometimes return* `UNDEF` *value due to the fact that some stations don't provide measurements for them.*
## Full Example
airquality.map:
```text
-=-
UNDEF=No data
NULL=No data
NO_DATA=No data
GOOD=Good
MODERATE=Moderate
UNHEALTHY_FOR_SENSITIVE=Unhealthy for sensitive groups
UNHEALTHY=Unhealthy
VERY_UNHEALTHY=Very unhealthy
HAZARDOUS=Hazardous
```
airquality.things:
```java
airquality:aqi:home "AirQuality" @ "Krakow" [ apikey="XXXXXXXXXXXX", location="50.06465,19.94498", refresh=60 ]
airquality:aqi:warsaw "AirQuality in Warsaw" [ apikey="XXXXXXXXXXXX", location="52.22,21.01", refresh=60 ]
airquality:aqi:brisbane "AirQuality in Brisbane" [ apikey="XXXXXXXXXXXX", stationId=5115 ]
Bridge airquality:api:main "Bridge" [apiKey="xxxyyyzzz"] {
station MyHouse "Krakow"[location="50.06465,19.94498", refresh=60]
}
```
airquality.items:
@ -120,24 +142,19 @@ airquality.items:
```java
Group AirQuality <flow>
Number Aqi_Level "Air Quality Index" <flow> (AirQuality) { channel="airquality:aqi:home:aqiLevel" }
String Aqi_Description "AQI Level [MAP(airquality.map):%s]" <flow> (AirQuality) { channel="airquality:aqi:home:aqiDescription" }
Number Aqi_Level "Air Quality Index" <flow> (AirQuality) { channel="airquality:station:local:aqi#index" }
Number Aqi_Pm25 "PM\u2082\u2085 Level" <line> (AirQuality) { channel="airquality:station:local:pm25#value" }
Number Aqi_Pm10 "PM\u2081\u2080 Level" <line> (AirQuality) { channel="airquality:station:local:pm10#value" }
Number Aqi_O3 "O\u2083 Level" <line> (AirQuality) { channel="airquality:station:local:o3#value" }
Number Aqi_No2 "NO\u2082 Level" <line> (AirQuality) { channel="airquality:station:local:no2#value" }
Number Aqi_Co "CO Level" <line> (AirQuality) { channel="airquality:station:local:co#value" }
Number Aqi_So2 "SO\u2082 Level" <line> (AirQuality) { channel="airquality:station:local:so2#value" }
Number Aqi_Pm25 "PM\u2082\u2085 Level" <line> (AirQuality) { channel="airquality:aqi:home:pm25" }
Number Aqi_Pm10 "PM\u2081\u2080 Level" <line> (AirQuality) { channel="airquality:aqi:home:pm10" }
Number Aqi_O3 "O\u2083 Level" <line> (AirQuality) { channel="airquality:aqi:home:o3" }
Number Aqi_No2 "NO\u2082 Level" <line> (AirQuality) { channel="airquality:aqi:home:no2" }
Number Aqi_Co "CO Level" <line> (AirQuality) { channel="airquality:aqi:home:co" }
Number Aqi_So2 "SO\u2082 Level" <line> (AirQuality) { channel="airquality:aqi:home:so2" }
DateTime Aqi_ObservationTime "Time of observation [%1$tH:%1$tM]" <clock> (AirQuality) { channel="airquality:station:local:aqi#timestamp" }
String Aqi_LocationName "Measuring Location" <settings> (AirQuality) { channel="airquality:aqi:home:locationName" }
Location Aqi_StationGeo "Station Location" <office> (AirQuality) { channel="airquality:aqi:home:stationLocation" }
Number Aqi_StationId "Station ID" <pie> (AirQuality) { channel="airquality:aqi:home:stationId" }
DateTime Aqi_ObservationTime "Time of observation [%1$tH:%1$tM]" <clock> (AirQuality) { channel="airquality:aqi:home:observationTime" }
Number:Temperature Aqi_Temperature "Temperature" <temperature> (AirQuality) { channel="airquality:aqi:home:temperature" }
Number:Pressure Aqi_Pressure "Pressure" <pressure> (AirQuality) { channel="airquality:aqi:home:pressure" }
Number:Dimensionless Aqi_Humidity "Humidity" <humidity> (AirQuality) { channel="airquality:aqi:home:humidity" }
Number:Temperature Aqi_Temperature "Temperature" <temperature> (AirQuality) { channel="airquality:station:local:weather#temperature" }
Number:Pressure Aqi_Pressure "Pressure" <pressure> (AirQuality) { channel="airquality:station:local:weather#pressure" }
Number:Dimensionless Aqi_Humidity "Humidity" <humidity> (AirQuality) { channel="airquality:station:localweather#humidity" }
```
airquality.sitemap:
@ -158,7 +175,7 @@ sitemap airquality label="Air Quality" {
Aqi_Description=="HAZARDOUS"="#7e0023",
=="VERY_UNHEALTHY"="#660099",
=="UNHEALTHY"="#cc0033",
=="UNHEALTHY_FOR_SENSITIVE"="#ff9933",
=="UNHEALTHY_FSG"="#ff9933",
=="MODERATE"="#ffde33",
=="GOOD"="#009966"
]
@ -174,16 +191,12 @@ sitemap airquality label="Air Quality" {
}
Frame {
Text item=Aqi_LocationName
Text item=Aqi_ObservationTime
Text item=Aqi_Temperature
Text item=Aqi_Pressure
Text item=Aqi_Humidity
}
Frame label="Station Location" {
Mapview item=Aqi_StationGeo height=10
}
}
```
@ -204,7 +217,7 @@ then
hsb = "280,100,60"
case "UNHEALTHY":
hsb = "345,100,80"
case "UNHEALTHY_FOR_SENSITIVE":
case "UNHEALTHY_FSG":
hsb = "30,80,100"
case "MODERATE":
hsb = "50,80,100"

BIN
_addons_bindings/nuvo/doc/nuvo_logo.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 9.1 KiB

12
_addons_bindings/nuvo/readme.md
View File

@ -3,7 +3,7 @@ id: nuvo
label: Nuvo Grand Concerto & Essentia G
title: Nuvo Grand Concerto & Essentia G - Bindings
type: binding
description: "![Nuvo logo](doc/nuvo_logo.png)"
description: "This binding can be used to control the Nuvo Grand Concerto or Essentia G whole house multi-zone amplifier."
since: 3x
install: auto
---
@ -14,8 +14,6 @@ install: auto
# Nuvo Grand Concerto & Essentia G Binding
![Nuvo logo](doc/nuvo_logo.png)
This binding can be used to control the Nuvo Grand Concerto or Essentia G whole house multi-zone amplifier.
Up to 20 keypad zones can be controlled when zone expansion modules are used (if not all zones on the amp are used they can be excluded via configuration).
@ -23,7 +21,7 @@ The binding supports three different kinds of connections:
* serial connection,
* serial over IP connection,
* direct IP connection via a Nuvo MPS4 music server (experimental)
* direct IP connection via a Nuvo MPS4 music server
For users without a serial connector on the server side, you can use a USB to serial adapter.
@ -61,8 +59,8 @@ The thing has the following configuration parameters:
Some notes:
* The direct connection to the MPS4 server has not been exhaustively tested, please report any issues found.
* The only issue with the MPS4 connection seen thus far is that the setting SxDISPINFO as seen in the advanced rules below does not work.
* If the port is set to 5006, the binding will adjust its protocol to connect to the Nuvo amplifier thing via an MPS4 IP connection.
* MPS4 connections do not support custom commands using `SxDISPINFO` including those outlined in the advanced rules section below.
* If a zone has a maximum volume limit configured by the Nuvo configurator, the volume slider will automatically drop back to that level if set above the configured limit.
* Source display_line1 thru 4 can only be updated on non NuvoNet sources.
* The track_position channel does not update continuously for NuvoNet sources. It only changes when the track changes or playback is paused/unpaused.
@ -118,7 +116,7 @@ nuvo:amplifier:myamp "Nuvo WHA" [ serialPort="COM5", numZones=6, clockSync=false
// serial over IP connection
nuvo:amplifier:myamp "Nuvo WHA" [ host="192.168.0.10", port=4444, numZones=6, clockSync=false]
// MPS4 server IP connection (experimental)
// MPS4 server IP connection
nuvo:amplifier:myamp "Nuvo WHA" [ host="192.168.0.10", port=5006, numZones=6, clockSync=false]
```

51
_addons_bindings/zigbee/org.openhab.binding.zigbee/README.md
View File

@ -141,30 +141,37 @@ Sets the Trust Centre join/rejoin mode.
| `TC_JOIN_INSECURE` | Allow all joins. | |
| `TC_JOIN_INSTALLCODE` | Only join with install code. | Devices attempting to join with the TC Link Key will be rejected. |
##### Group Registration (zigbee_groupregistration)
Some devices send commands to a group address (ie using multicast addressing). This configuration allows the user to define a list of groups that the binding will listen for commands. Multiple groups can be defined - groups are separated with a comma and must be defined as a four character hexadecimal value.
Note that this is only available for Ember coordinators.
#### Supported Coordinators
The following coordinators are known to be supported.
| Name and Link | Coordinator | Configuration | Comment |
| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Texas Instruments CC2531EMK](http://www.ti.com/tool/cc2531emk) | [CC2531](#cc2531-coordinator) | | CC2531 is not recommended for more then 15 devices due to its less powerful MCU. Also needs extra [hardware and Z-Stack Home 1.2 firmware flashed](https://www.zigbee2mqtt.io/guide/adapters/flashing/flashing_the_cc2531.html). CC2530 and CC2538 may work too with Z-Stack Home 1.2 compatible firmware. |
| [POPP ZigBee Stick](https://www.popp.eu/zb-stick/) | [Ember](#ember-ezsp-ncp-coordinator) | 115200bps<br>Hardware&nbsp;flow&nbsp;control<br>High RAM |
| [Bitron Video ZigBee USB Funkstick](https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/) | [Ember](#ember-ezsp-ncp-coordinator) | 57600bps<br>Software&nbsp;flow&nbsp;control<br>High RAM | |
| [Elelabs ELU013/ELR023](https://elelabs.com/shop/) | [Ember](#ember-ezsp-ncp-coordinator) | 115200bps<br>Hardware&nbsp;flow&nbsp;control<br>High RAM | Both the stick and the hat can be upgraded without additional hardware, firmware available [here](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility). |
| [Cortet EM358 USB Stick](https://www.cortet.com/iot-hardware/cortet-usb-sticks/em358-usb-stick) | [Ember](#ember-ezsp-ncp-coordinator) | 57600bps<br>Software&nbsp;flow&nbsp;control<br>High RAM | |
| [MeshConnect EM358 USB Stick](https://www.cortet.com/iot-hardware/cortet-usb-sticks/em358-usb-stick) | [Ember](#ember-ezsp-ncp-coordinator) | | Requires specific drivers that may not work on MacOS Monterey |
| [Nortek Security & Control HUSBZB-1](https://nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) | [Ember](#ember-ezsp-ncp-coordinator) | 57600bps<br>Software&nbsp;flow&nbsp;control<br>High RAM | Stick contains both Z-Wave and ZigBee. |
| [Telegesis ETRX357USB ZigBee® USB Stick](https://www.silabs.com/products/wireless/mesh-networking/telegesis-modules-gateways/etrx3-zigbee-usb-sticks) | [Telegesis](#telegesis-etrx3) | | |
| [Telegesis ETRX357USB ZigBee® USB Stick](https://www.silabs.com/products/wireless/mesh-networking/telegesis-modules-gateways/etrx3-zigbee-usb-sticks) | [Telegesis](#telegesis-etrx3) | | Not supported for ZigBee 3.0 |
| [QIVICON ZigBee-Funkstick](https://www.qivicon.com/de/produkte/produktinformationen/zigbee-funkstick/) | [Telegesis](#telegesis-etrx3) | | Only working on Linux devices |
| [Digi XStick](https://www.digi.com/products/xbee-rf-solutions/boxed-rf-modems-adapters/xstick) | [XBee](#digi-xbee-x-stick) | | |
| [Texas Instruments CC2531EMK](http://www.ti.com/tool/cc2531emk) | [CC2531](#cc2531-coordinator) | | CC2531 is not recommended for more then 15 devices due to its less powerful MCU. Also needs extra [hardware and Z-Stack Home 1.2 firmware flashed](https://www.zigbee2mqtt.io/guide/adapters/flashing/flashing_the_cc2531.html). CC2530 and CC2538 may work too with Z-Stack Home 1.2 compatible firmware. |
#### Ember EZSP NCP Coordinator
The Ember EZSP NCP (Network Co-Processor) supports the Silabs MightyGecko (EFR32MG) and the older EM357/8 dongles with the standard NCP firmware. The thing type is `coordinator_ember`. This dongle type is recommended due to its extensive use within both the community, and commercial systems using this dongle.
The Ember EZSP NCP (Network Co-Processor) supports the SiLabs MightyGecko (EFR32MG) and the older EM357/8 dongles with the standard NCP firmware. The thing type is `coordinator_ember`. This dongle type is recommended due to its extensive use within both the community, and commercial systems using this dongle.
Note that there are generally two versions of the Ember NCP firmware in use. One operates at a baud rate of 115200 with RTS/CTS flow control (i.e. hardware flow control), the other operates at a baud rate of 57600, and XON/XOFF flow control (i.e. software flow control). If you are programming your own stick (e.g. the CEL stick) then it should be advisable to use the hardware flow control version - many commercial sticks seem to use the lower speed and software flow control (e.g. Bitron and Nortek HUSBZB-1).
Firmware versions higher than 6.4.0.0 may be required to work with some newer devices (ie those conforming to the Zigbee 3.0 standard). If your dongle has older firmware then devices may appear to join the network, but will not work as they will leave the network if they do not receive updated security information.
Firmware versions higher than 6.4.0.0 may be required to work with some newer devices (i.e. those conforming to the Zigbee 3.0 standard). If your dongle has older firmware then devices may appear to join the network, but will not work as they will leave the network if they do not receive updated security information.
If the usb dongle is not recognized, it might be necessary to make the dongle's device id known to the CP240x driver by Silicon Labs:
If the USB dongle is not recognized, it might be necessary to make the dongle's device id known to the CP240x driver by Silicon Labs:
- Find the device id (as listed by the command `lsusb`). For the Bitron Funkstick that might be 10c4 8b34.
- Unplug the device
@ -239,7 +246,7 @@ Extract and install the TI Flash Programmer, connect the CC-Debugger trough USB,
### Devices
The following devices have been tested by openHAB users with the binding. The absence of a device in this list does not mean it will not work - if the device is a standard ZigBee device similar to ones on this list, then it should work.
The following devices have been tested by openHAB users with the binding. This list is far from exhaustive, and the absence of a device in this list does not mean it will not work - if the device is a standard ZigBee device similar to ones on this list, then it should work. It should be noted that many "new" devices (approximately newer than 2020) will require coordinators that support ZigBee 3.0. If this is not supported, then devices may briefly join the network, and then leave when they find the network does not support the newer security requirements.
| Device | Description |
| ---------------------------------------------- | ------------------------------------------------------------ |
@ -299,9 +306,9 @@ The following devices have been tested by openHAB users with the binding. The ab
## Discovery
Discovery is performed by putting the binding into join mode (by starting an inbox search), and then putting the device into join mode. Generally, it is best to reset the device to do this. Resetting the device ensures that it is no longer joined to a previous network, will ensure it is awake if it is a battery device, and will restart any channel and network search that the device may perform. Consult the manual of the device at hand to see how to reset it, this differs from device to device.
Discovery is performed by putting the binding into join mode (by starting an thing search), and then putting the device into join mode. Generally, it is best to reset the device to do this. Resetting the device ensures that it is no longer joined to a previous network, will ensure it is awake if it is a battery device, and will restart any channel and network search that the device may perform. Consult the manual of the device at hand to see how to reset it, this differs from device to device.
Once the binding is installed, and an adapter is added, it automatically reads all devices that are set up on the ZigBee controller and puts them in the Inbox. When the binding is put into discovery mode via the user interface, the network will have join enabled for 60 seconds. You can put it in discovery mode via the **Scan** button in the user interface. This can be found after you click the blue **+** button in the bottom right corder of the **Things** screen and then select the **ZigBee Binding**.
When the binding is put into discovery mode via the user interface, the network will have join enabled for 60 seconds. You can put it in discovery mode via the **Scan** button in the user interface. This can be found after you click the blue **+** button in the bottom right corder of the **Things** screen and then select the **ZigBee Binding**.
The binding will store the list of devices that have joined the network locally between restarts to allow them to be found again later. A ZigBee coordinator does not store a list of known devices, so rediscovery of devices following a restart may not be seemless if the dongle is moved to another system.
@ -339,7 +346,7 @@ The binding will attempt to automatically detect new devices, giving them a type
### Thing Types
Currently all ZigBee things have the same thing type of `zigbee_device`.
Most ZigBee things have the same thing type of `zigbee_device`. The binding will automatically discover the device features and provide channels linked to device functionality that it is able to support. A small number of devices that require a manual thing definition may be defined in the binding to support devices that have non-standard functionality, or do not support the autodiscovery functionality provided by ZigBee.
### Channel Types
@ -469,7 +476,29 @@ log:set info com.zsmartsystems.zigbee.dongle.ember.internal.ash
This will log data into the standard `openhab.log` file. There is an [online log viewer](https://opensmarthouse.org/utilities/logviewer/zigbee/) available for viewing the logs.
Note that logs can only show what is happening at a high level - it can't show all data exchanges between the device and the coordinator - just what the coordinator sends to the binding. For this reason it can be difficult to debug issues where devices are not joining the network, or other low level issues need resolving. In such cases a network sniffer log is required, which requires additional hardware and software.
Note that logs can only show what is happening at a high level - it can't show all data exchanges between the device and the coordinator - just what the coordinator sends to the binding. For this reason it can be difficult to debug issues where devices are not joining the network, or other low level issues need resolving. In such cases a network sniffer log is required, which requires additional hardware and software. Information and software required to use an Ember dongle as a sniffer can be found on the [OpenSmartHouse](https://opensmarthouse.org/blog/zigbee_network_sniffer) site.
### ZigBee Console Commands
The openHAB command line interface provides a number of commands to interact with the ZigBee framework. These can provide useful options for debugging when things aren't going as planned, and can also provide advanced users a means to make changes that are not possible directly through the binding. This section will provide information on a few common issues that users may come up against, but is not an exhaustive user manual for low level ZigBee commands.
All commands described below must be preceded by the word `zigbee` on the command line. To keep the documentation concise this is omitted in the examples below.
To list all known nodes, use the `nodes` command. This will list the nodes and endpoints of the nodes, and is often required as a first step in order to get the node ID or endpoint ID for other commands. Nodes and endpoints are often required as arguments in commands and can typically be entered in decimal or hexadecimal node number with a decimal endpoint - e.g. `0x1234/1`, or `4660/1` - both of these describe the same node/endpoint.
#### Device Information (Fingerprint)
In some instances a device may not work correctly. This could be because the binding had problems during initialisation, or possibly because the device supports features not implemented in the binding, or possibly the device may implement custom functionality. To understand this, there is a `fingerprint` command. This command will attempt to poll the device to get a list of all the commands and attributes that the device supports and create a concise list. Note that this may not work on all devices if the device doesn't support the functionality discovery commands.
#### Binding and Reporting
The binding table is used within ZigBee to configure devices to send reports to the binding when their state changes. The binding will attempt to set the required ZigBee bindings during device initialisation, but sometimes this can fail. Often this may occur on older devices that have limited memory, and only have a small number of entries in the binding table, and then manual manipulation of the table may be required.
The binding table for a node can be displayed with the `bindtable` command. It can then be updated with the `bind` command, and bindings can be removed with the `unbind` command.
A second part to the binding and reporting system is the reporting. The binding table tells the device where it should send reports, but the actual reports must be configured as well. Many attributes in a ZigBee cluster can be configured to send reports if their state changes, or at a periodical rate if there have been no state updates within a certain time. Analogue values can be configured so that they report if the value changes by a certain amount so that the reports do not flood the system. Care must be exercised when changing this configuration as it may interfere with the binding operation.
The exact command required to configure reporting can depend on whether the attribute is a binary or analogue type. The console commands `subscribe` and `unsubscribe` allow the user to manipulate the reporting of an attribute, and the `reportcfg` command can be used to display the current configuration.
## Known issues

51
_addons_bindings/zigbee/readme.md
View File

@ -156,30 +156,37 @@ Sets the Trust Centre join/rejoin mode.
| `TC_JOIN_INSECURE` | Allow all joins. | |
| `TC_JOIN_INSTALLCODE` | Only join with install code. | Devices attempting to join with the TC Link Key will be rejected. |
##### Group Registration (zigbee_groupregistration)
Some devices send commands to a group address (ie using multicast addressing). This configuration allows the user to define a list of groups that the binding will listen for commands. Multiple groups can be defined - groups are separated with a comma and must be defined as a four character hexadecimal value.
Note that this is only available for Ember coordinators.
#### Supported Coordinators
The following coordinators are known to be supported.
| Name and Link | Coordinator | Configuration | Comment |
| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Texas Instruments CC2531EMK](http://www.ti.com/tool/cc2531emk) | [CC2531](#cc2531-coordinator) | | CC2531 is not recommended for more then 15 devices due to its less powerful MCU. Also needs extra [hardware and Z-Stack Home 1.2 firmware flashed](https://www.zigbee2mqtt.io/guide/adapters/flashing/flashing_the_cc2531.html). CC2530 and CC2538 may work too with Z-Stack Home 1.2 compatible firmware. |
| [POPP ZigBee Stick](https://www.popp.eu/zb-stick/) | [Ember](#ember-ezsp-ncp-coordinator) | 115200bps<br>Hardware&nbsp;flow&nbsp;control<br>High RAM |
| [Bitron Video ZigBee USB Funkstick](https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/) | [Ember](#ember-ezsp-ncp-coordinator) | 57600bps<br>Software&nbsp;flow&nbsp;control<br>High RAM | |
| [Elelabs ELU013/ELR023](https://elelabs.com/shop/) | [Ember](#ember-ezsp-ncp-coordinator) | 115200bps<br>Hardware&nbsp;flow&nbsp;control<br>High RAM | Both the stick and the hat can be upgraded without additional hardware, firmware available [here](https://github.com/Elelabs/elelabs-zigbee-ezsp-utility). |
| [Cortet EM358 USB Stick](https://www.cortet.com/iot-hardware/cortet-usb-sticks/em358-usb-stick) | [Ember](#ember-ezsp-ncp-coordinator) | 57600bps<br>Software&nbsp;flow&nbsp;control<br>High RAM | |
| [MeshConnect EM358 USB Stick](https://www.cortet.com/iot-hardware/cortet-usb-sticks/em358-usb-stick) | [Ember](#ember-ezsp-ncp-coordinator) | | Requires specific drivers that may not work on MacOS Monterey |
| [Nortek Security & Control HUSBZB-1](https://nortekcontrol.com/products/2gig/husbzb-1-gocontrol-quickstick-combo/) | [Ember](#ember-ezsp-ncp-coordinator) | 57600bps<br>Software&nbsp;flow&nbsp;control<br>High RAM | Stick contains both Z-Wave and ZigBee. |
| [Telegesis ETRX357USB ZigBee® USB Stick](https://www.silabs.com/products/wireless/mesh-networking/telegesis-modules-gateways/etrx3-zigbee-usb-sticks) | [Telegesis](#telegesis-etrx3) | | |
| [Telegesis ETRX357USB ZigBee® USB Stick](https://www.silabs.com/products/wireless/mesh-networking/telegesis-modules-gateways/etrx3-zigbee-usb-sticks) | [Telegesis](#telegesis-etrx3) | | Not supported for ZigBee 3.0 |
| [QIVICON ZigBee-Funkstick](https://www.qivicon.com/de/produkte/produktinformationen/zigbee-funkstick/) | [Telegesis](#telegesis-etrx3) | | Only working on Linux devices |
| [Digi XStick](https://www.digi.com/products/xbee-rf-solutions/boxed-rf-modems-adapters/xstick) | [XBee](#digi-xbee-x-stick) | | |
| [Texas Instruments CC2531EMK](http://www.ti.com/tool/cc2531emk) | [CC2531](#cc2531-coordinator) | | CC2531 is not recommended for more then 15 devices due to its less powerful MCU. Also needs extra [hardware and Z-Stack Home 1.2 firmware flashed](https://www.zigbee2mqtt.io/guide/adapters/flashing/flashing_the_cc2531.html). CC2530 and CC2538 may work too with Z-Stack Home 1.2 compatible firmware. |
#### Ember EZSP NCP Coordinator
The Ember EZSP NCP (Network Co-Processor) supports the Silabs MightyGecko (EFR32MG) and the older EM357/8 dongles with the standard NCP firmware. The thing type is `coordinator_ember`. This dongle type is recommended due to its extensive use within both the community, and commercial systems using this dongle.
The Ember EZSP NCP (Network Co-Processor) supports the SiLabs MightyGecko (EFR32MG) and the older EM357/8 dongles with the standard NCP firmware. The thing type is `coordinator_ember`. This dongle type is recommended due to its extensive use within both the community, and commercial systems using this dongle.
Note that there are generally two versions of the Ember NCP firmware in use. One operates at a baud rate of 115200 with RTS/CTS flow control (i.e. hardware flow control), the other operates at a baud rate of 57600, and XON/XOFF flow control (i.e. software flow control). If you are programming your own stick (e.g. the CEL stick) then it should be advisable to use the hardware flow control version - many commercial sticks seem to use the lower speed and software flow control (e.g. Bitron and Nortek HUSBZB-1).
Firmware versions higher than 6.4.0.0 may be required to work with some newer devices (ie those conforming to the Zigbee 3.0 standard). If your dongle has older firmware then devices may appear to join the network, but will not work as they will leave the network if they do not receive updated security information.
Firmware versions higher than 6.4.0.0 may be required to work with some newer devices (i.e. those conforming to the Zigbee 3.0 standard). If your dongle has older firmware then devices may appear to join the network, but will not work as they will leave the network if they do not receive updated security information.
If the usb dongle is not recognized, it might be necessary to make the dongle's device id known to the CP240x driver by Silicon Labs:
If the USB dongle is not recognized, it might be necessary to make the dongle's device id known to the CP240x driver by Silicon Labs:
- Find the device id (as listed by the command `lsusb`). For the Bitron Funkstick that might be 10c4 8b34.
- Unplug the device
@ -254,7 +261,7 @@ Extract and install the TI Flash Programmer, connect the CC-Debugger trough USB,
### Devices
The following devices have been tested by openHAB users with the binding. The absence of a device in this list does not mean it will not work - if the device is a standard ZigBee device similar to ones on this list, then it should work.
The following devices have been tested by openHAB users with the binding. This list is far from exhaustive, and the absence of a device in this list does not mean it will not work - if the device is a standard ZigBee device similar to ones on this list, then it should work. It should be noted that many "new" devices (approximately newer than 2020) will require coordinators that support ZigBee 3.0. If this is not supported, then devices may briefly join the network, and then leave when they find the network does not support the newer security requirements.
| Device | Description |
| ---------------------------------------------- | ------------------------------------------------------------ |
@ -314,9 +321,9 @@ The following devices have been tested by openHAB users with the binding. The ab
## Discovery
Discovery is performed by putting the binding into join mode (by starting an inbox search), and then putting the device into join mode. Generally, it is best to reset the device to do this. Resetting the device ensures that it is no longer joined to a previous network, will ensure it is awake if it is a battery device, and will restart any channel and network search that the device may perform. Consult the manual of the device at hand to see how to reset it, this differs from device to device.
Discovery is performed by putting the binding into join mode (by starting an thing search), and then putting the device into join mode. Generally, it is best to reset the device to do this. Resetting the device ensures that it is no longer joined to a previous network, will ensure it is awake if it is a battery device, and will restart any channel and network search that the device may perform. Consult the manual of the device at hand to see how to reset it, this differs from device to device.
Once the binding is installed, and an adapter is added, it automatically reads all devices that are set up on the ZigBee controller and puts them in the Inbox. When the binding is put into discovery mode via the user interface, the network will have join enabled for 60 seconds. You can put it in discovery mode via the **Scan** button in the user interface. This can be found after you click the blue **+** button in the bottom right corder of the **Things** screen and then select the **ZigBee Binding**.
When the binding is put into discovery mode via the user interface, the network will have join enabled for 60 seconds. You can put it in discovery mode via the **Scan** button in the user interface. This can be found after you click the blue **+** button in the bottom right corder of the **Things** screen and then select the **ZigBee Binding**.
The binding will store the list of devices that have joined the network locally between restarts to allow them to be found again later. A ZigBee coordinator does not store a list of known devices, so rediscovery of devices following a restart may not be seemless if the dongle is moved to another system.
@ -354,7 +361,7 @@ The binding will attempt to automatically detect new devices, giving them a type
### Thing Types
Currently all ZigBee things have the same thing type of `zigbee_device`.
Most ZigBee things have the same thing type of `zigbee_device`. The binding will automatically discover the device features and provide channels linked to device functionality that it is able to support. A small number of devices that require a manual thing definition may be defined in the binding to support devices that have non-standard functionality, or do not support the autodiscovery functionality provided by ZigBee.
### Channel Types
@ -484,7 +491,29 @@ log:set info com.zsmartsystems.zigbee.dongle.ember.internal.ash
This will log data into the standard `openhab.log` file. There is an [online log viewer](https://opensmarthouse.org/utilities/logviewer/zigbee/) available for viewing the logs.
Note that logs can only show what is happening at a high level - it can't show all data exchanges between the device and the coordinator - just what the coordinator sends to the binding. For this reason it can be difficult to debug issues where devices are not joining the network, or other low level issues need resolving. In such cases a network sniffer log is required, which requires additional hardware and software.
Note that logs can only show what is happening at a high level - it can't show all data exchanges between the device and the coordinator - just what the coordinator sends to the binding. For this reason it can be difficult to debug issues where devices are not joining the network, or other low level issues need resolving. In such cases a network sniffer log is required, which requires additional hardware and software. Information and software required to use an Ember dongle as a sniffer can be found on the [OpenSmartHouse](https://opensmarthouse.org/blog/zigbee_network_sniffer) site.
### ZigBee Console Commands
The openHAB command line interface provides a number of commands to interact with the ZigBee framework. These can provide useful options for debugging when things aren't going as planned, and can also provide advanced users a means to make changes that are not possible directly through the binding. This section will provide information on a few common issues that users may come up against, but is not an exhaustive user manual for low level ZigBee commands.
All commands described below must be preceded by the word `zigbee` on the command line. To keep the documentation concise this is omitted in the examples below.
To list all known nodes, use the `nodes` command. This will list the nodes and endpoints of the nodes, and is often required as a first step in order to get the node ID or endpoint ID for other commands. Nodes and endpoints are often required as arguments in commands and can typically be entered in decimal or hexadecimal node number with a decimal endpoint - e.g. `0x1234/1`, or `4660/1` - both of these describe the same node/endpoint.
#### Device Information (Fingerprint)
In some instances a device may not work correctly. This could be because the binding had problems during initialisation, or possibly because the device supports features not implemented in the binding, or possibly the device may implement custom functionality. To understand this, there is a `fingerprint` command. This command will attempt to poll the device to get a list of all the commands and attributes that the device supports and create a concise list. Note that this may not work on all devices if the device doesn't support the functionality discovery commands.
#### Binding and Reporting
The binding table is used within ZigBee to configure devices to send reports to the binding when their state changes. The binding will attempt to set the required ZigBee bindings during device initialisation, but sometimes this can fail. Often this may occur on older devices that have limited memory, and only have a small number of entries in the binding table, and then manual manipulation of the table may be required.
The binding table for a node can be displayed with the `bindtable` command. It can then be updated with the `bind` command, and bindings can be removed with the `unbind` command.
A second part to the binding and reporting system is the reporting. The binding table tells the device where it should send reports, but the actual reports must be configured as well. Many attributes in a ZigBee cluster can be configured to send reports if their state changes, or at a periodical rate if there have been no state updates within a certain time. Analogue values can be configured so that they report if the value changes by a certain amount so that the reports do not flood the system. Care must be exercised when changing this configuration as it may interfere with the binding operation.
The exact command required to configure reporting can depend on whether the attribute is a binary or analogue type. The console commands `subscribe` and `unsubscribe` allow the user to manipulate the reporting of an attribute, and the `reportcfg` command can be used to display the current configuration.
## Known issues

17
_addons_bindings/zwave/doc/homeseer/hsfls100_0_0.md
View File

@ -140,7 +140,7 @@ Detailed information on each parameter can be found in the sections below.
|-------|-------|-------------|
| 1 | PIR Trigger Off Period | Period to send Trigger Off command after PIR is triggered. |
| 2 | Lux sensor threshold | Lux level to activate the PIR |
| 3 | Auto Report luminance interval | sets the interval of periodic lux level report to the controller |
| 3 | Auto Report luminance interval | Sets the interval of periodic lux level report to the controller |
| 4 | Basic Report | |
### Parameter 1: PIR Trigger Off Period
@ -166,7 +166,12 @@ Setting = 30~200: lighting activation by setting
Setting = 255: turn ON light upon PIR triggered
If the level is set to 0, the unit will not turn on its floodlight. The PIR will still send a notification report to the controller; if the level is set to 255, when motion is sensed, the sensor ignore the ambient brightness but just turn on the light.
Values in the range 0 to 255 may be set.
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Light is never triggered by PIR |
| 255 | Light is always triggered by PIR regardless of lux |
The manufacturer defined default value is ```50```.
@ -175,7 +180,7 @@ This parameter has the configuration ID ```config_2_2``` and is of type ```INTEG
### Parameter 3: Auto Report luminance interval
sets the interval of periodic lux level report to the controller
Sets the interval of periodic lux level report to the controller
Values in the range 0 to 1440 may be set.
@ -192,10 +197,10 @@ The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | not send Basic Report |
| 1 | send Basic Report |
| 0 | Do not send Basic Report |
| 1 | Send Basic Report (default) |
The manufacturer defined default value is ```1``` (send Basic Report).
The manufacturer defined default value is ```1``` (Send Basic Report (default)).
This parameter has the configuration ID ```config_4_1``` and is of type ```INTEGER```.

64
_addons_bindings/zwave/doc/shenzhen/naspd07z_0_0.md
View File

@ -115,10 +115,10 @@ Detailed information on each parameter can be found in the sections below.
| 11 | Basic Set Level | |
| 12 | Basic Set Off Delay Time | |
| 13 | Motion Blind Time | |
| 14 | ??? Unknown | |
| 15 | ??? Unknown | |
| 16 | Luminance Threshold for Associated | |
| 17 | Sensor Measuring Interval | |
| 14 | ??? Unknown (Luminance Threshold for Associated - Parameter #16?) | |
| 15 | Sensor Measuring Interval | |
| 16 | ??? Luminance Threshold for Associated (or Parameter #14?) | |
| 17 | ??? Unknown | |
| 18 | Light Intensity Offset Calibration | |
| 98 | ??? Binary Sensor Report Enable | |
| 99 | ??? Motion Clear Time | |
@ -126,7 +126,7 @@ Detailed information on each parameter can be found in the sections below.
### Parameter 1: Led Indicator Enable
This parameter is configured the Led light on disable or enable. '1' - Enable Led Blink when device detects a motion event. '0' - Disable Led blink. This configuration is not affect inclusion, exclusion and reset.
This parameter is configured the Led light on disable or enable. '1' - Enable Led Blink when device detects a motion event. '0' - Disable Led blink. This configuration is not affect inclusion, exclusion and reset. Default: Enable
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
@ -142,7 +142,7 @@ This parameter has the configuration ID ```config_1_1``` and is of type ```INTEG
### Parameter 2: Motion Enable
This parameter is configured the motion detected if enable or not. '0' - Motion detected disable. '1' - Motion detected enable.
This parameter is configured the motion detected if enable or not. '0' - Motion detected disable. '1' - Motion detected enable. Default: Enable
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
@ -158,7 +158,7 @@ This parameter has the configuration ID ```config_2_1``` and is of type ```INTEG
### Parameter 3: Motion Alarm Once Enable
This Parameter is configured the motion detected event report one time before motion event cleared. '0' - Motion event alarm will be reported when motion event is detected every time. '1' - Motion event alarm report only once before motion event cleared.
This Parameter is configured the motion detected event report one time before motion event cleared. '0' - Motion event alarm will be reported when motion event is detected every time. '1' - Motion event alarm report only once before motion event cleared. Default: Enable
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
@ -174,7 +174,7 @@ This parameter has the configuration ID ```config_3_1``` and is of type ```INTEG
### Parameter 4: Luminance Associated Enable
'1' - Enable current light intensity to associate the motion event, if there has a motion event detected and the current light intensity is less than the settings in Configuraton No. 16, the device will send a BASIC\_SET to nodes associated in Group 2. And if the current light intensity is larger then the setting in Configuration No. 16, the device will not send BASIC\_SET to nodes associated in Group 2. '0' - Light intensity is not associated with motion event.
'1' - Enable current light intensity to associate the motion event, if there has a motion event detected and the current light intensity is less than the settings in Configuraton No. 16, the device will send a BASIC\_SET to nodes associated in Group 2. And if the current light intensity is larger then the setting in Configuration No. 16, the device will not send BASIC\_SET to nodes associated in Group 2. '0' - Light intensity is not associated with motion event. Default: Disable
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
@ -190,10 +190,10 @@ This parameter has the configuration ID ```config_4_1``` and is of type ```INTEG
### Parameter 5: Motion Sensitivity
This parameter is configured the sensitivity that motion detect. This value is larger, the sensitivity is lower, and the distance for motion detecting is closer. Available settings: 0 ... 15
This parameter is configured the sensitivity that motion detect. This value is larger, the sensitivity is lower, and the distance for motion detecting is closer. Available settings: 0 ... 15. Default: 1
Values in the range 0 to 15 may be set.
The manufacturer defined default value is ```2```.
The manufacturer defined default value is ```1```.
This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```.
@ -201,7 +201,7 @@ This parameter has the configuration ID ```config_5_1``` and is of type ```INTEG
### Parameter 6: Temperature Offset Value
The current measuring temperature value can be add and minus a value by this setting. Temperature Offset Value = [Value] x 0.1 Degree Celsius / Fahrenheit (US). Available settings: -120 ... 120
The current measuring temperature value can be add and minus a value by this setting. Temperature Offset Value = [Value] x 0.1 Degree Celsius / Fahrenheit (US). Available settings: -120 ... 120. Default: 0
Values in the range -120 to 120 may be set.
The manufacturer defined default value is ```0```.
@ -212,7 +212,7 @@ This parameter has the configuration ID ```config_6_1``` and is of type ```INTEG
### Parameter 7: Humidity Offset Value
The current measuring humidity value can be add and minus a value by this setting. Humidity Offset Value = [Value] x 0.1 RH%. Available settings: -120 ... 120
The current measuring humidity value can be add and minus a value by this setting. Humidity Offset Value = [Value] x 0.1 RH%. Available settings: -120 ... 120. Default: 0
Values in the range -120 to 120 may be set.
The manufacturer defined default value is ```0```.
@ -223,7 +223,7 @@ This parameter has the configuration ID ```config_7_1``` and is of type ```INTEG
### Parameter 8: Temperature D-Value Setting
This configuration sets the changed value of the temperature. When the difference from the last report exceeds this setting value, the device will report current temperature value to Z-Wave Hubs. The D-Value = [Value] x 0.1 Degree Celsius / Fahrenheit (US). Available settings: 0 ... 120
This configuration sets the changed value of the temperature. When the difference from the last report exceeds this setting value, the device will report current temperature value to Z-Wave Hubs. The D-Value = [Value] x 0.1 Degree Celsius / Fahrenheit (US). Available settings: 0 ... 120. Default: 10
Values in the range 0 to 120 may be set.
The manufacturer defined default value is ```10```.
@ -234,7 +234,7 @@ This parameter has the configuration ID ```config_8_1``` and is of type ```INTEG
### Parameter 9: Humidity D-Value Setting
This configuration sets the changed value of the humidity. When the difference from the last report exceeds this setting value, the device will report current humidity value to Z-Wave Hubs. The D-Value = [Value] x 0.1 RH%. Available settings: 0 ... 120
This configuration sets the changed value of the humidity. When the difference from the last report exceeds this setting value, the device will report current humidity value to Z-Wave Hubs. The D-Value = [Value] x 0.1 RH%. Available settings: 0 ... 120. Default: 20
Values in the range 0 to 120 may be set.
The manufacturer defined default value is ```20```.
@ -245,7 +245,7 @@ This parameter has the configuration ID ```config_9_1``` and is of type ```INTEG
### Parameter 10: Luminance D-Value Setting
This configuration sets the changed value of the luminance. When the difference from the last report exceeds this setting value, the device will report current luminance value to Z-Wave Hubs. Unit: Lux. Available settings: 0 ... 120
This configuration sets the changed value of the luminance. When the difference from the last report exceeds this setting value, the device will report current luminance value to Z-Wave Hubs. Unit: Lux. Available settings: 0 ... 120. Default: 50
Values in the range 0 to 120 may be set.
The manufacturer defined default value is ```50```.
@ -256,7 +256,7 @@ This parameter has the configuration ID ```config_10_1``` and is of type ```INTE
### Parameter 11: Basic Set Level
This parameter is configured the value that BASIC\_SET for nodes that associated in Group 2. '100' - BASIC\_SET = 0xFF (ON). '0' - BASIC_SET = 0x00 (OFF). Available settings: 0 ... 100
This parameter is configured the value that BASIC\_SET for nodes that associated in Group 2. '100' - BASIC\_SET = 0xFF (ON). '0' - BASIC_SET = 0x00 (OFF). Available settings: 0 ... 100. Default: 100
Values in the range 0 to 100 may be set.
The manufacturer defined default value is ```100```.
@ -267,7 +267,7 @@ This parameter has the configuration ID ```config_11_2``` and is of type ```INTE
### Parameter 12: Basic Set Off Delay Time
This parameter is configured the time delay for device sending BASIC\_SET = 0x00 to nodes that associated in Group 2 when device detects a motion event. [0] - Not Send BASIC\_SET = 0x00 Command. [1-30000] - Time delay count. Unit: Second. Available settings: 0 ... 30000
This parameter is configured the time delay for device sending BASIC\_SET = 0x00 to nodes that associated in Group 2 when device detects a motion event. [0] - Not Send BASIC\_SET = 0x00 Command. [1-30000] - Time delay count. Unit: Second. Available settings: 0 ... 30000. Default: 30
Values in the range 0 to 30000 may be set.
The manufacturer defined default value is ```30```.
@ -286,10 +286,10 @@ The manufacturer defined default value is ```8```.
This parameter has the configuration ID ```config_13_1``` and is of type ```INTEGER```.
### Parameter 14: ??? Unknown
### Parameter 14: ??? Unknown (Luminance Threshold for Associated - Parameter #16?)
Default: 50
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
@ -297,21 +297,21 @@ The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_14_2``` and is of type ```INTEGER```.
### Parameter 15: ??? Unknown
### Parameter 15: Sensor Measuring Interval
This parameter is configured the time interval for light sensor, temperature and humidity sensor measuring. This value is larger, the battery life is longer. And the sensors values changed are not obvious. 0 - All sensors are disabled. Unit: Second. Available settings: 0 - 30000. Default: 180 (on batteries) or 10 (on USB)
Values in the range 0 to 30000 may be set.
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```0```.
The manufacturer defined default value is ```180```.
This parameter has the configuration ID ```config_15_2``` and is of type ```INTEGER```.
### Parameter 16: Luminance Threshold for Associated
### Parameter 16: ??? Luminance Threshold for Associated (or Parameter #14?)
This parameter is configured the light intensity threshold. When Ambient light intensity is less than this setting, device will consider the current environment is insufficient light. If "Configuration No. 3" is set '1' and a motion event is detected, the device will send a BASIC_SET to the nodes which associated in Group 2. Unit: 1 Lux. Available settings: 0 - 1000
This parameter is configured the light intensity threshold. When Ambient light intensity is less than this setting, device will consider the current environment is insufficient light. If "Configuration No. 3" is set '1' and a motion event is detected, the device will send a BASIC_SET to the nodes which associated in Group 2. Unit: 1 Lux. Available settings: 0 - 1000. Default: 50
Values in the range 0 to 1000 may be set.
The manufacturer defined default value is ```50```.
@ -319,13 +319,13 @@ The manufacturer defined default value is ```50```.
This parameter has the configuration ID ```config_16_2``` and is of type ```INTEGER```.
### Parameter 17: Sensor Measuring Interval
### Parameter 17: ??? Unknown
This parameter is configured the time interval for light sensor, temperature and humidity sensor measuring. This value is larger, the battery life is longer. And the sensors values changed are not obvious. 0 - All sensors are disabled. Unit: Second. Available settings: 0 - 30000, default value: 180 (on batteries) or 10 (on USB)
Values in the range 0 to 30000 may be set.
Default: 180
Values in the range 0 to 0 may be set.
The manufacturer defined default value is ```180```.
The manufacturer defined default value is ```0```.
This parameter has the configuration ID ```config_17_2``` and is of type ```INTEGER```.
@ -352,7 +352,7 @@ k = 0.11538 * 1000 = 115,38 ~ 115
The parameter should be set to 115.
Available settings: 1 ... 32767
Available settings: 1 ... 32767. Default: 5320
Values in the range 1 to 32767 may be set.
The manufacturer defined default value is ```5320```.
@ -363,7 +363,7 @@ This parameter has the configuration ID ```config_18_2``` and is of type ```INTE
### Parameter 98: ??? Binary Sensor Report Enable
'1' - Enable sensor binary report when device detects a motion event. '0' - Disable sensor binary report when device detects a motion event.
'1' - Enable sensor binary report when device detects a motion event. '0' - Disable sensor binary report when device detects a motion event. Default: Disable
The following option values may be configured, in addition to values in the range 0 to 1 -:
| Value | Description |
@ -379,7 +379,7 @@ This parameter has the configuration ID ```config_98_1``` and is of type ```INTE
### Parameter 99: ??? Motion Clear Time
This parameter is configured the time to clear motion event after a motion event detected. Time to motion clear, the device will send a clear event report to controller. Unit: Second. Available settings: 0 ... 30000
This parameter is configured the time to clear motion event after a motion event detected. Time to motion clear, the device will send a clear event report to controller. Unit: Second. Available settings: 0 ... 30000. Default: 30
Values in the range 1 to 30000 may be set.
The manufacturer defined default value is ```30```.

19
_addons_bindings/zwave/doc/vision/zd2102plus_0_0.md
View File

@ -46,6 +46,7 @@ The following table summarises the channels available for the ZD2102-5 -:
|--------------|------------|--------------|----------|-----------|
| Door Sensor | sensor_door | sensor_door | Door | Contact |
| Tamper Alarm | alarm_tamper | alarm_tamper | | Switch |
| Battery | alarm_battery | alarm_battery | LowBattery | Switch |
| Battery Level | battery-level | system.battery_level | Battery | Number |
### Door Sensor
@ -72,6 +73,18 @@ The following state translation is provided for this channel to the ```Switch```
| OFF | OK |
| ON | Alarm |
### Battery
Indicates if the low battery alarm is triggered.
The ```alarm_battery``` channel is of type ```alarm_battery``` and supports the ```Switch``` item and is in the ```LowBattery``` 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 |
### Battery Level
Represents the battery level as a percentage (0-100%). Bindings for things supporting battery level in a different format (e.g. 4 levels) should convert to a percentage to provide a consistent battery level reading.
@ -94,14 +107,14 @@ Detailed information on each parameter can be found in the sections below.
Determines if the external switch can be used.
The following option values may be configured -:
The following option values may be configured, in addition to values in the range 0 to 255 -:
| Value | Description |
|--------|-------------|
| 0 | Disable |
| 0 | Disable (default) |
| 255 | Enable |
The manufacturer defined default value is ```0``` (Disable).
The manufacturer defined default value is ```0``` (Disable (default)).
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.

51
_addons_bindings/zwave/doc/zooz/zen34v101_0_0.md
View File

@ -19,15 +19,11 @@ The zen34v1.01 does not permanently listen for messages sent from the controller
## Overview
* Control other Z-Wave devices and enable scenes with a click of a button
* Classic paddle switch look and size + magnetic base
* Install in your electrical switch box or mount anywhere on a wall with just adhesive tape
* The latest 700 chip with S2 and SmartStart support
* Powered by batteries, no wires needed
* Control other Z-Wave devices and enable scenes with a click of a button
* Classic paddle switch look and size + magnetic base
* Install in your electrical switch box or mount anywhere on a wall with just adhesive tape
* The latest 700 chip with S2 and SmartStart support
* Powered by batteries, no wires needed
### Inclusion Information
@ -52,23 +48,17 @@ The LED indication will light up any time a paddle is pressed. It will blink onc
Upper Paddle
TAP x 1 for Scene 1, pressed (or ON basic for associations)
TAP x 2, 3, 4, or 5 for Scene 1 multi-tap
HOLD for Scene 1, held (or multilevel start level change, add brightness)
RELEASE for Scene 1, released (or multilevel stop level change)
* TAP x 1 for Scene 1, pressed (or ON basic for associations)
* TAP x 2, 3, 4, or 5 for Scene 1 multi-tap
* HOLD for Scene 1, held (or multilevel start level change, add brightness)
* RELEASE for Scene 1, released (or multilevel stop level change)
Lower Paddle
TAP x 1 for Scene 2, pressed (or OFF basic for associations)
TAP x 2, 3, 4, or 5 for Scene 2 multi-tap
HOLD for Scene 2, held (or multilevel start level change, dim the light)
RELEASE for Scene 2, released (or multilevel stop level change)
* TAP x 1 for Scene 2, pressed (or OFF basic for associations)
* TAP x 2, 3, 4, or 5 for Scene 2 multi-tap
* HOLD for Scene 2, held (or multilevel start level change, dim the light)
* RELEASE for Scene 2, released (or multilevel stop level change)
## Channels
@ -124,11 +114,11 @@ The following option values may be configured, in addition to values in the rang
| Value | Description |
|--------|-------------|
| 0 | LED always OFF |
| 1 | LED ON when button pressed |
| 1 | LED ON when button pressed (default) |
| 2 | LED always ON (color from #2) |
| 3 | LED always ON (color from #3) |
The manufacturer defined default value is ```1``` (LED ON when button pressed).
The manufacturer defined default value is ```1``` (LED ON when button pressed (default)).
This parameter has the configuration ID ```config_1_1``` and is of type ```INTEGER```.
@ -142,14 +132,14 @@ The following option values may be configured, in addition to values in the rang
| Value | Description |
|--------|-------------|
| 0 | White |
| 1 | Blue |
| 1 | Blue (default) |
| 2 | Green |
| 3 | Red |
| 4 | Magenta |
| 5 | Yellow |
| 6 | Cyan |
The manufacturer defined default value is ```1``` (Blue).
The manufacturer defined default value is ```1``` (Blue (default)).
This parameter has the configuration ID ```config_2_1``` and is of type ```INTEGER```.
@ -162,7 +152,7 @@ The following option values may be configured, in addition to values in the rang
| Value | Description |
|--------|-------------|
| 0 | White |
| 0 | White (default) |
| 1 | Blue |
| 2 | Green |
| 3 | Red |
@ -170,7 +160,7 @@ The following option values may be configured, in addition to values in the rang
| 5 | Yellow |
| 6 | Cyan |
The manufacturer defined default value is ```1``` (Blue).
The manufacturer defined default value is ```0``` (White (default)).
This parameter has the configuration ID ```config_3_1``` and is of type ```INTEGER```.
@ -210,10 +200,11 @@ Association group 1 supports 1 node.
Association group 2 supports 5 nodes.
### Group 3: dimming
### Group 3: Dimming
Paddle held/released for dimming
Association group 3 supports 5 nodes.
## Technical Information

2734
_addons_ios/alexa-skill/readme.md
View File

File diff suppressed because it is too large Load Diff

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

@ -4,55 +4,58 @@
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">
<!-- Air Quality Thing -->
<thing-type id="aqi">
<label>Air Quality</label>
<description>
Provides various air quality data from the World Air Quality Project.
In order to receive the data, you
must register an account on http://aqicn.org/data-platform/token/ and get your API
token.
</description>
<channels>
<channel id="aqiLevel" typeId="aqiLevel"/>
<channel id="aqiColor" typeId="aqiColor"/>
<channel id="aqiDescription" typeId="aqiDescription"/>
<channel id="pm25" typeId="pm25"/>
<channel id="pm10" typeId="pm10"/>
<channel id="o3" typeId="o3"/>
<channel id="no2" typeId="no2"/>
<channel id="co" typeId="co"/>
<channel id="so2" typeId="so2"/>
<channel id="locationName" typeId="locationName"/>
<channel id="stationLocation" typeId="stationLocation"/>
<channel id="stationId" typeId="stationId"/>
<channel id="observationTime" typeId="observationTime"/>
<channel id="temperature" typeId="temperature"/>
<channel id="pressure" typeId="pressure"/>
<channel id="humidity" typeId="humidity"/>
<channel id="dominentpol" typeId="dominentPol"/>
</channels>
<bridge-type id="api">
<label>Air Quality API</label>
<config-description>
<parameter name="apikey" type="text" required="true">
<parameter name="apiKey" type="text" required="true">
<context>password</context>
<label>API Key</label>
<description>Data-platform token to access the AQIcn.org service</description>
</parameter>
</config-description>
</bridge-type>
<!-- Air Quality Thing -->
<thing-type id="station" extensible="sensitive-group">
<supported-bridge-type-refs>
<bridge-type-ref id="api"/>
</supported-bridge-type-refs>
<label>Air Quality Station</label>
<channel-groups>
<channel-group id="aqi" typeId="aqi"/>
<channel-group id="weather" typeId="weather"/>
<channel-group id="pm25" typeId="pollutant-density">
<label>@text/pm25ChannelGroupLabel</label>
</channel-group>
<channel-group id="pm10" typeId="pollutant-density">
<label>@text/pm10ChannelGroupLabel</label>
</channel-group>
<channel-group id="no2" typeId="pollutant-ppb">
<label>@text/no2ChannelGroupLabel</label>
</channel-group>
<channel-group id="so2" typeId="pollutant-ppb">
<label>@text/so2ChannelGroupLabel</label>
</channel-group>
<channel-group id="co" typeId="pollutant-ppb">
<label>@text/coChannelGroupLabel</label>
</channel-group>
<channel-group id="o3" typeId="pollutant-ppb">
<label>@text/o3ChannelGroupLabel</label>
</channel-group>
</channel-groups>
<config-description>
<parameter name="location" type="text" required="false"
pattern="^[-+]?([1-8]?\d(\.\d+)?|90(\.0+)?)[,]\s*[-+]?(180(\.0+)?|((1[0-7]\d)|([1-9]?\d))(\.\d+)?)$">
<label>Location</label>
<description>Your geo coordinates separated with comma (e.g. "37.8,-122.4").</description>
</parameter>
<parameter name="stationId" type="integer" required="false">
<label>Station ID</label>
<description>Fill only in case you want to receive data from the specific station</description>
<advanced>true</advanced>
</parameter>
<parameter name="refresh" type="integer" min="30" required="false" unit="min">
<label>Refresh Interval</label>
<description>Specifies the refresh interval in minutes.</description>
<advanced>true</advanced>
<default>60</default>
<unitLabel>Minutes</unitLabel>
@ -60,155 +63,172 @@
</config-description>
</thing-type>
<channel-type id="aqiLevel">
<channel-group-type id="aqi">
<label>@text/aqiChannelGroupLabel</label>
<channels>
<channel id="alert-level" typeId="alert-level"/>
<channel id="index" typeId="index"/>
<channel id="timestamp" typeId="timestamp"/>
<channel id="dominent" typeId="dominent"/>
<channel id="icon" typeId="alert-icon"/>
<channel id="color" typeId="alert-color"/>
</channels>
</channel-group-type>
<channel-group-type id="weather">
<label>@text/weatherChannelGroupLabel</label>
<channels>
<channel id="temperature" typeId="system.outdoor-temperature"/>
<channel id="pressure" typeId="system.barometric-pressure"/>
<channel id="humidity" typeId="system.atmospheric-humidity"/>
<channel id="dew-point" typeId="dew-point"/>
<channel id="wind-speed" typeId="system.wind-speed"/>
</channels>
</channel-group-type>
<channel-group-type id="pollutant-density">
<label>Pollutant</label>
<channels>
<channel id="value" typeId="density-value"/>
<channel id="index" typeId="index-adv"/>
<channel id="alert-level" typeId="alert-level"/>
</channels>
</channel-group-type>
<channel-group-type id="pollutant-ppb">
<label>Pollutant</label>
<channels>
<channel id="value" typeId="ppb-value"/>
<channel id="index" typeId="index-adv"/>
<channel id="alert-level" typeId="alert-level"/>
</channels>
</channel-group-type>
<channel-type id="index">
<item-type>Number</item-type>
<label>Air Quality Index</label>
<description></description>
<category>Air Quality Index</category>
<label>Index</label>
<tags>
<tag>Measurement</tag>
</tags>
<state readOnly="true" pattern="%d" min="0" max="500"/>
</channel-type>
<channel-type id="aqiDescription">
<item-type>String</item-type>
<label>AQI Description</label>
<description></description>
<category>AQI Description</category>
<state readOnly="true">
<options>
<option value="GOOD">Good</option>
<option value="MODERATE">Moderate</option>
<option value="UNHEALTHY_FOR_SENSITIVE">Unhealthy for Sensitive Groups</option>
<option value="UNHEALTHY">Unhealthy</option>
<option value="VERY_UNHEALTHY">Very Unhealthy</option>
<option value="HAZARDOUS">Hazardous</option>
</options>
</state>
</channel-type>
<channel-type id="pm25">
<channel-type id="index-adv" advanced="true">
<item-type>Number</item-type>
<label>PM2.5</label>
<description>Fine particles pollution level</description>
<category>PM2.5</category>
<label>Index</label>
<tags>
<tag>Measurement</tag>
</tags>
<state readOnly="true" pattern="%d" min="0" max="500"/>
</channel-type>
<channel-type id="pm10">
<item-type>Number</item-type>
<label>PM10</label>
<description>Coarse dust particles pollution level</description>
<category>PM10</category>
<state readOnly="true" pattern="%d" min="0" max="500"/>
<channel-type id="density-value">
<item-type>Number:Density</item-type>
<label>Measure</label>
<state readOnly="true" pattern="%.2f %unit%"/>
</channel-type>
<channel-type id="o3">
<item-type>Number</item-type>
<label>O3</label>
<description>Ozone level</description>
<category>O3</category>
<state readOnly="true" pattern="%.1f" min="0" max="500"/>
</channel-type>
<channel-type id="no2">
<item-type>Number</item-type>
<label>NO2</label>
<description>Nitrogen dioxide level</description>
<category>NO2</category>
<state readOnly="true" pattern="%.1f" min="0" max="500"/>
</channel-type>
<channel-type id="co">
<item-type>Number</item-type>
<label>CO</label>
<description>Carbon monoxide level</description>
<category>CO</category>
<state readOnly="true" pattern="%.1f" min="0" max="500"/>
</channel-type>
<channel-type id="so2">
<item-type>Number</item-type>
<label>SO2</label>
<description>Sulfur dioxide level</description>
<category>SO2</category>
<state readOnly="true" pattern="%.1f"/>
</channel-type>
<channel-type id="locationName" advanced="true">
<item-type>String</item-type>
<label>Location</label>
<description>Nearest measuring station location</description>
<category>Location</category>
<state readOnly="true" pattern="%s"/>
</channel-type>
<channel-type id="stationLocation" advanced="true">
<item-type>Location</item-type>
<label>Station Location</label>
<description>Location of the measuring station</description>
<category>Station Location</category>
<state readOnly="true" pattern="%2$s°N,%3$s°W"/>
</channel-type>
<channel-type id="stationId" advanced="true">
<item-type>Number</item-type>
<label>Station ID</label>
<description>Unique measuring station ID</description>
<category>Station ID</category>
<state readOnly="true" pattern="%d"/>
</channel-type>
<channel-type id="observationTime" advanced="true">
<item-type>DateTime</item-type>
<label>Observation Time</label>
<description>Observation date and time</description>
<category>Observation time</category>
<state readOnly="true"/>
</channel-type>
<channel-type id="temperature" advanced="true">
<item-type>Number:Temperature</item-type>
<label>Temperature</label>
<description>Temperature</description>
<category>Temperature</category>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="pressure" advanced="true">
<item-type>Number:Pressure</item-type>
<label>Pressure</label>
<description>Current Pressure</description>
<category>Pressure</category>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="humidity" advanced="true">
<channel-type id="ppb-value">
<item-type>Number:Dimensionless</item-type>
<label>Humidity</label>
<description>Current humidity</description>
<category>Humidity</category>
<state readOnly="true" min="0" max="100" pattern="%.2f %unit%"/>
<label>Measure</label>
<state readOnly="true" pattern="%.2f %unit%"/>
</channel-type>
<channel-type id="dominentPol">
<item-type>String</item-type>
<label>Dominent Polutor</label>
<channel-type id="alert-level">
<item-type>Number</item-type>
<label>@text/alertLevelChannelLabel</label>
<description>@text/alertLevelChannelDescription</description>
<category>error</category>
<tags>
<tag>Alarm</tag>
</tags>
<state readOnly="true">
<options>
<option value="pm25">Fine particles</option>
<option value="pm10">Coarse dust particles</option>
<option value="o3">Ozone</option>
<option value="no2">Nitrogen Dioxide</option>
<option value="co">Carbon Monoxide</option>
<option value="so2">Sulfur Dioxide</option>
<option value="0">@text/alertLevelOption0</option>
<option value="1">@text/alertLevelOption1</option>
<option value="2">@text/alertLevelOption2</option>
<option value="3">@text/alertLevelOption3</option>
<option value="4">@text/alertLevelOption4</option>
<option value="5">@text/alertLevelOption5</option>
</options>
</state>
</channel-type>
<channel-type id="aqiColor" advanced="true">
<item-type>Color</item-type>
<label>AQI Color</label>
<description>Color associated to given AQI Index.</description>
<channel-type id="timestamp" advanced="true">
<item-type>DateTime</item-type>
<label>@text/timestampChannelLabel</label>
<description>@text/timestampChannelDescription</description>
<category>time</category>
<tags>
<tag>Status</tag>
<tag>Timestamp</tag>
</tags>
<state readOnly="true"/>
</channel-type>
<channel-type id="dominent">
<item-type>String</item-type>
<label>@text/dominentChannelLabel</label>
<tags>
<tag>Status</tag>
</tags>
<state readOnly="true">
<options>
<option value="pm25">@text/pollutantPm25</option>
<option value="pm10">@text/pollutantPm10</option>
<option value="o3">@text/pollutantO3</option>
<option value="no2">@text/pollutantNO2</option>
<option value="co">@text/pollutantCO</option>
<option value="so2">@text/pollutantSO2</option>
</options>
</state>
</channel-type>
<channel-type id="dew-point" advanced="true">
<item-type>Number:Temperature</item-type>
<label>@text/dewPointLabel</label>
<description>@text/dewPointDescription</description>
<category>Temperature</category>
<tags>
<tag>Point</tag>
<tag>Temperature</tag>
</tags>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
<channel-type id="alert-color" advanced="true">
<item-type>Color</item-type>
<label>@text/colorChannelLabel</label>
<description>@text/colorChannelDescription</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="alert-icon">
<item-type>Image</item-type>
<label>@text/pictoChannelLabel</label>
<description>@text/pictoChannelDescription</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="sensitive-group">
<item-type>Switch</item-type>
<label>Sensitive Group</label>
<description>Checked if sensitive group is exposed to pollutant.</description>
<state readOnly="true"/>
<config-description>
<parameter name="group" type="text">
<label>Group</label>
<description>Defines the kind of sensitivity</description>
<options>
<option value="RESPIRATORY">People with respiratory disease.</option>
<option value="HEART">People with heart disease.</option>
<option value="ELDERLY">The elderly.</option>
<option value="CHILDREN">Children.</option>
<option value="ASTHMA">People with asthma.</option>
</options>
<default>RESPIRATORY</default>
</parameter>
</config-description>
</channel-type>
</thing:thing-descriptions>

4
_thing_types/org.openhab.binding.avmfritz/src/main/resources/OH-INF/thing/channel-types.xml
View File

@ -205,7 +205,7 @@
<label>Next Setpoint Change</label>
<description>Next change of Setpoint Temperature.</description>
<category>Time</category>
<state readOnly="true"/>
<state readOnly="true" pattern="%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS"/>
</channel-type>
<channel-type id="next_temp" advanced="true">
@ -229,7 +229,7 @@
<label>Last Change</label>
<description>States the last time the button was pressed.</description>
<category>Time</category>
<state readOnly="true"/>
<state readOnly="true" pattern="%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS"/>
</channel-type>
<channel-type id="rollershutter">

11
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/CLIPGenericFlagSensor.xml
View File

@ -19,15 +19,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="sensorId" type="text" required="true">
<label>Sensor ID</label>
<description>The identifier that is used within the hue bridge.</description>
</parameter>
<parameter name="on" type="boolean">
<label>Sensor Status</label>
<description>Enables or disables the sensor.</description>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:sensor"/>
</thing-type>
</thing:thing-descriptions>

11
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/CLIPGenericStatusSensor.xml
View File

@ -19,15 +19,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="sensorId" type="text" required="true">
<label>Sensor ID</label>
<description>The identifier that is used within the hue bridge.</description>
</parameter>
<parameter name="on" type="boolean">
<label>Sensor Status</label>
<description>Enables or disables the sensor.</description>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:sensor"/>
</thing-type>
</thing:thing-descriptions>

12
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/ColorLight.xml
View File

@ -20,16 +20,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="lightId" type="text" required="true">
<label>Light ID</label>
<description>The light identifier identifies one certain hue light.</description>
</parameter>
<parameter name="fadetime" type="integer" min="0" step="100" unit="ms">
<label>Fade Time</label>
<description>Fade time in milliseconds for changing values</description>
<default>400</default>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:light"/>
</thing-type>
</thing:thing-descriptions>

12
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/ColorTemperatureLight.xml
View File

@ -22,16 +22,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="lightId" type="text" required="true">
<label>Light ID</label>
<description>The light identifier identifies one certain hue light.</description>
</parameter>
<parameter name="fadetime" type="integer" min="0" step="100" unit="ms">
<label>Fade Time</label>
<description>Fade time in milliseconds for changing values</description>
<default>400</default>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:light"/>
</thing-type>
</thing:thing-descriptions>

12
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/DimmableLight.xml
View File

@ -19,16 +19,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="lightId" type="text" required="true">
<label>Light ID</label>
<description>The light identifier identifies one certain hue light.</description>
</parameter>
<parameter name="fadetime" type="integer" min="0" step="100" unit="ms">
<label>Fade Time</label>
<description>Fade time in milliseconds for changing values</description>
<default>400</default>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:light"/>
</thing-type>
</thing:thing-descriptions>

12
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/DimmablePlug.xml
View File

@ -18,16 +18,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="lightId" type="text" required="true">
<label>Light ID</label>
<description>The identifier that is used within the hue bridge.</description>
</parameter>
<parameter name="fadetime" type="integer" min="0" step="100" unit="ms">
<label>Fade Time</label>
<description>Fade time in milliseconds for changing values</description>
<default>400</default>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:plug"/>
</thing-type>
</thing:thing-descriptions>

11
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/DimmerSwitch.xml
View File

@ -22,15 +22,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="sensorId" type="text" required="true">
<label>Sensor ID</label>
<description>The identifier that is used within the hue bridge.</description>
</parameter>
<parameter name="on" type="boolean">
<label>Sensor Status</label>
<description>Enables or disables the sensor.</description>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:sensor"/>
</thing-type>
</thing:thing-descriptions>

12
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/ExtendedColorLight.xml
View File

@ -22,16 +22,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="lightId" type="text" required="true">
<label>Light ID</label>
<description>The light identifier identifies one certain hue light.</description>
</parameter>
<parameter name="fadetime" type="integer" min="0" step="100" unit="ms">
<label>Fade Time</label>
<description>Fade time in milliseconds for changing values</description>
<default>400</default>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:light"/>
</thing-type>
</thing:thing-descriptions>

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

@ -19,6 +19,6 @@
<representation-property>uniqueId</representation-property>
<config-description-ref uri="thing-type:hue:geofencesensor"/>
<config-description-ref uri="thing-type:hue:sensor"/>
</thing-type>
</thing:thing-descriptions>

12
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/Group.xml
View File

@ -24,16 +24,6 @@
<representation-property>groupId</representation-property>
<config-description>
<parameter name="groupId" type="text" required="true">
<label>Group ID</label>
<description>The group identifier identifies one certain hue group or room.</description>
</parameter>
<parameter name="fadetime" type="integer" min="0" step="100" unit="ms">
<label>Fade Time</label>
<description>Fade time in milliseconds for changing values</description>
<default>400</default>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:group"/>
</thing-type>
</thing:thing-descriptions>

28
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/LightLevelSensor.xml
View File

@ -24,32 +24,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="sensorId" type="text" required="true">
<label>Sensor ID</label>
<description>The identifier that is used within the hue bridge.</description>
</parameter>
<parameter name="on" type="boolean">
<label>Sensor Status</label>
<description>Enables or disables the sensor.</description>
</parameter>
<parameter name="ledindication" type="boolean">
<label>LED Indication</label>
<description>Turns device LED during normal operation on or off. Devices might still indicate exceptional operation
(Reset, SW Update, Battery Low).</description>
</parameter>
<parameter name="tholddark" type="integer" min="0" step="1">
<label>Threshold Dark</label>
<description>Threshold the user configured to be used in rules to determine insufficient light level (ie below
threshold). Default value 16000.</description>
<default>16000</default>
</parameter>
<parameter name="tholdoffset" type="integer" min="1" step="1">
<label>Threshold Offset</label>
<description>Threshold the user configured to be used in rules to determine sufficient light level (ie above
threshold). Specified as relative offset to the "dark" threshold. Shall be >=1. Default value 7000.</description>
<default>7000</default>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:lightlevelsensor"/>
</thing-type>
</thing:thing-descriptions>

7
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/OnOffLight.xml
View File

@ -19,11 +19,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="lightId" type="text" required="true">
<label>Light ID</label>
<description>The light identifier identifies one certain hue light.</description>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:lightwithoutfade"/>
</thing-type>
</thing:thing-descriptions>

7
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/OnOffPlug.xml
View File

@ -18,11 +18,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="lightId" type="text" required="true">
<label>Light ID</label>
<description>The identifier that is used within the hue bridge.</description>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:plugwithoutfade"/>
</thing-type>
</thing:thing-descriptions>

11
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/TapSwitch.xml
View File

@ -20,15 +20,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="sensorId" type="text" required="true">
<label>Sensor ID</label>
<description>The identifier that is used within the hue bridge.</description>
</parameter>
<parameter name="on" type="boolean">
<label>Sensor Status</label>
<description>Enables or disables the sensor.</description>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:sensor"/>
</thing-type>
</thing:thing-descriptions>

16
_thing_types/org.openhab.binding.hue/src/main/resources/OH-INF/thing/TemperatureSensor.xml
View File

@ -21,20 +21,6 @@
<representation-property>uniqueId</representation-property>
<config-description>
<parameter name="sensorId" type="text" required="true">
<label>Sensor ID</label>
<description>The identifier that is used within the hue bridge.</description>
</parameter>
<parameter name="on" type="boolean">
<label>Sensor Status</label>
<description>Enables or disables the sensor.</description>
</parameter>
<parameter name="ledindication" type="boolean">
<label>LED Indication</label>
<description>Turns device LED during normal operation on or off. Devices might still indicate exceptional operation
(Reset, SW Update, Battery Low).</description>
</parameter>
</config-description>
<config-description-ref uri="thing-type:hue:temperaturesensor"/>
</thing-type>
</thing:thing-descriptions>

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

@ -196,6 +196,7 @@
<channel-type id="cardinalWindDirection">
<item-type>String</item-type>
<label>Cardinal Wind Direction</label>
<description>The cardinal direction of the wind</description>
<state readOnly="true" pattern="%s">
</state>
</channel-type>
@ -212,7 +213,7 @@
<channel-type id="maxWindSpeed">
<item-type>Number:Speed</item-type>
<label>Maximum Wind Speed</label>
<description>Maximum wind speed</description>
<description>The maximum wind speed</description>
<category>Wind</category>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
@ -220,6 +221,7 @@
<channel-type id="minWindSpeed">
<item-type>Number:Speed</item-type>
<label>Minimum Wind Speed</label>
<description>The minimum wind speed</description>
<category>Wind</category>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>
@ -227,6 +229,7 @@
<channel-type id="meanWindSpeed">
<item-type>Number:Speed</item-type>
<label>Mean Wind Speed</label>
<description>The mean wind speed</description>
<category>Wind</category>
<state readOnly="true" pattern="%.1f %unit%"/>
</channel-type>

2
_thing_types/org.openhab.binding.phc/src/main/resources/OH-INF/thing/channel-types.xml
View File

@ -53,7 +53,7 @@
</channels>
</channel-group-type>
<channel-group-type id="jrmTimeChannels" advanced="true">
<channel-group-type id="jrmTimeChannels">
<label>JRM time Channels</label>
<description>Time for shutter channels in seconds with an accuracy of 1/10 seconds.</description>
<channels>

120
_thing_types/org.openhab.binding.rfxcom/src/main/resources/OH-INF/thing/RFXrec433.xml
View File

@ -10,150 +10,146 @@
<config-description>
<parameter name="bridgeId" type="text" required="true">
<label>Serial Number</label>
<description>Serial number of the RFXCOM (FTDI) device</description>
<label>@text/config.bridgeId.label</label>
<description>@text/config.bridgeId.description</description>
</parameter>
<parameter name="disableDiscovery" type="boolean" required="true">
<label>Disable Discovery of Unknown Devices</label>
<description>These RF protocols are prone to noise. If you find a lot of unknown devices showing up in your inbox
enabling this will stop devices being added to your inbox.</description>
<label>@text/config.disableDiscovery.label</label>
<description>@text/config.disableDiscovery.description</description>
<default>false</default>
</parameter>
<parameter name="ignoreConfig" type="boolean">
<label>Skip Transceiver Configuration</label>
<description>Fully skip and ignore RFXCOM transceiver configuration. Binding assume that RFXCOM transceiver is
preconfigured e.g. via RFXcom Manager. When this is enabled, both set mode command and individual message
configurations are ignored.</description>
<label>@text/config.ignoreConfig.label</label>
<description>@text/config.ignoreConfig.description</description>
<default>true</default>
</parameter>
<parameter name="setMode" type="text">
<label>RFXCOM Transceiver Mode</label>
<description>RFXCOM transceiver set mode command. Command should be in hexadecimal string format and 28 characters
(14 bytes) long. If set mode command is given, individual message configurations are ignored.</description>
<label>@text/config.setMode.label</label>
<description>@text/config.setMode.description</description>
</parameter>
<parameter name="transmitPower" type="integer" min="-18" max="10">
<label>Transmit Power</label>
<description>Transmit power in dBm, between -18dBm and +10dBm.</description>
<label>@text/config.transmitPower.label</label>
<description>@text/config.transmitPower.description</description>
<default>-18</default>
</parameter>
<parameter name="enableUndecoded" type="boolean">
<label>Undecoded Messages</label>
<description>Enable display of unencoded messages to RFXCOM transceiver.</description>
<label>@text/config.enableUndecoded.label</label>
<description>@text/config.enableUndecoded.description</description>
<default>false</default>
</parameter>
<parameter name="enableImagintronixOpus" type="boolean">
<label>Imagintronix/Opus Messages</label>
<description>Enable Imagintronix/Opus messages to RFXCOM transceiver.</description>
<label>@text/config.enableImagintronixOpus.label</label>
<description>@text/config.enableImagintronixOpus.description</description>
<default>false</default>
</parameter>
<parameter name="enableByronSX" type="boolean">
<label>Byron SX Messages</label>
<description>Enable Byron SX messages to RFXCOM transceiver.</description>
<label>@text/config.enableByronSX.label</label>
<description>@text/config.enableByronSX.description</description>
<default>false</default>
</parameter>
<parameter name="enableRSL" type="boolean">
<label>RSL Messages</label>
<description>Enable RSL messages to RFXCOM transceiver.</description>
<label>@text/config.enableRSL.label</label>
<description>@text/config.enableRSL.description</description>
<default>false</default>
</parameter>
<parameter name="enableLighting4" type="boolean">
<label>Lighting4 Messages</label>
<description>Enable Lighting4 messages to RFXCOM transceiver.</description>
<label>@text/config.enableLighting4.label</label>
<description>@text/config.enableLighting4.description</description>
<default>false</default>
</parameter>
<parameter name="enableFineOffsetViking" type="boolean">
<label>FineOffset/Viking Messages</label>
<description>Enable FineOffset/Viking messages to RFXCOM transceiver.</description>
<label>@text/config.enableFineOffsetViking.label</label>
<description>@text/config.enableFineOffsetViking.description</description>
<default>false</default>
</parameter>
<parameter name="enableRubicson" type="boolean">
<label>Rubicson Messages</label>
<description>Enable Rubicson messages to RFXCOM transceiver.</description>
<label>@text/config.enableRubicson.label</label>
<description>@text/config.enableRubicson.description</description>
<default>false</default>
</parameter>
<parameter name="enableAEBlyss" type="boolean">
<label>AE Blyss Messages</label>
<description>Enable AE Blyss messages to RFXCOM transceiver.</description>
<label>@text/config.enableAEBlyss.label</label>
<description>@text/config.enableAEBlyss.description</description>
<default>false</default>
</parameter>
<parameter name="enableBlindsT1T2T3T4" type="boolean">
<label>BlindsT1/T2/T3/T4 Messages</label>
<description>Enable BlindsT1/T2/T3/T4 messages to RFXCOM transceiver.</description>
<label>@text/config.enableBlindsT1T2T3T4.label</label>
<description>@text/config.enableBlindsT1T2T3T4.description</description>
<default>false</default>
</parameter>
<parameter name="enableBlindsT0" type="boolean">
<label>BlindsT0 Messages</label>
<description>Enable BlindsT0 messages to RFXCOM transceiver.</description>
<label>@text/config.enableBlindsT0.label</label>
<description>@text/config.enableBlindsT0.description</description>
<default>false</default>
</parameter>
<parameter name="enableFS20" type="boolean">
<label>FS20/Legrand CAD Messages</label>
<description>Enable FS20/Legrand CAD messages to RFXCOM transceiver.</description>
<label>@text/config.enableFS20.label</label>
<description>@text/config.enableFS20.description</description>
<default>false</default>
</parameter>
<parameter name="enableLaCrosse" type="boolean">
<label>La Crosse Messages</label>
<description>Enable La Crosse messages to RFXCOM transceiver.</description>
<label>@text/config.enableLaCrosse.label</label>
<description>@text/config.enableLaCrosse.description</description>
<default>false</default>
</parameter>
<parameter name="enableHidekiUPM" type="boolean">
<label>Hideki/UPM Messages</label>
<description>Enable Hideki/UPM messages to RFXCOM transceiver.</description>
<label>@text/config.enableHidekiUPM.label</label>
<description>@text/config.enableHidekiUPM.description</description>
<default>false</default>
</parameter>
<parameter name="enableADLightwaveRF" type="boolean">
<label>AD LightwaveRF Messages</label>
<description>Enable AD LightwaveRF messages to RFXCOM transceiver.</description>
<label>@text/config.enableADLightwaveRF.label</label>
<description>@text/config.enableADLightwaveRF.description</description>
<default>false</default>
</parameter>
<parameter name="enableMertik" type="boolean">
<label>Mertik Messages</label>
<description>Enable Mertik messages to RFXCOM transceiver.</description>
<label>@text/config.enableMertik.label</label>
<description>@text/config.enableMertik.description</description>
<default>false</default>
</parameter>
<parameter name="enableATI" type="boolean">
<label>ATI Messages</label>
<description>Enable ATI messages to RFXCOM transceiver.</description>
<label>@text/config.enableATI.label</label>
<description>@text/config.enableATI.description</description>
<default>false</default>
</parameter>
<parameter name="enableOregonScientific" type="boolean">
<label>Oregon Scientific Messages</label>
<description>Enable Oregon Scientific messages to RFXCOM transceiver.</description>
<label>@text/config.enableOregonScientific.label</label>
<description>@text/config.enableOregonScientific.description</description>
<default>false</default>
</parameter>
<parameter name="enableMeiantech" type="boolean">
<label>Meiantech Messages</label>
<description>Enable Meiantech messages to RFXCOM transceiver.</description>
<label>@text/config.enableMeiantech.label</label>
<description>@text/config.enableMeiantech.description</description>
<default>false</default>
</parameter>
<parameter name="enableHomeEasyEU" type="boolean">
<label>HomeEasy EU Messages</label>
<description>Enable HomeEasy EU messages to RFXCOM transceiver.</description>
<label>@text/config.enableHomeEasyEU.label</label>
<description>@text/config.enableHomeEasyEU.description</description>
<default>false</default>
</parameter>
<parameter name="enableAC" type="boolean">
<label>AC Messages</label>
<description>Enable AC messages to RFXCOM transceiver.</description>
<label>@text/config.enableAC.label</label>
<description>@text/config.enableAC.description</description>
<default>false</default>
</parameter>
<parameter name="enableARC" type="boolean">
<label>ARC Messages</label>
<description>Enable ARC messages to RFXCOM transceiver.</description>
<label>@text/config.enableARC.label</label>
<description>@text/config.enableARC.description</description>
<default>false</default>
</parameter>
<parameter name="enableX10" type="boolean">
<label>X10 Messages</label>
<description>Enable X10 messages to RFXCOM transceiver.</description>
<label>@text/config.enableX10.label</label>
<description>@text/config.enableX10.description</description>
<default>false</default>
</parameter>
<parameter name="enableHomeConfort" type="boolean">
<label>HomeConfort Messages</label>
<description>Enable HomeConfort messages to RFXCOM transceiver.</description>
<label>@text/config.enableHomeConfort.label</label>
<description>@text/config.enableHomeConfort.description</description>
<default>false</default>
</parameter>
<parameter name="enableKEELOQ" type="boolean">
<label>KEELOQ Messages</label>
<description>Enable KEELOQ messages to RFXCOM transceiver.</description>
<label>@text/config.enableKEELOQ.label</label>
<description>@text/config.enableKEELOQ.description</description>
<default>false</default>
</parameter>

44
_thing_types/org.openhab.binding.rfxcom/src/main/resources/OH-INF/thing/RFXtrx315.xml
View File

@ -10,54 +10,50 @@
<config-description>
<parameter name="bridgeId" type="text" required="true">
<label>Serial Number</label>
<description>Serial number of the RFXCOM (FTDI) device</description>
<label>@text/config.bridgeId.label</label>
<description>@text/config.bridgeId.description</description>
</parameter>
<parameter name="disableDiscovery" type="boolean" required="true">
<label>Disable Discovery of Unknown Devices</label>
<description>These RF protocols are prone to noise. If you find a lot of unknown devices showing up in your inbox
enabling this will stop devices being added to your inbox.</description>
<label>@text/config.disableDiscovery.label</label>
<description>@text/config.disableDiscovery.description</description>
<default>false</default>
</parameter>
<parameter name="ignoreConfig" type="boolean">
<label>Skip Transceiver Configuration</label>
<description>Fully skip and ignore RFXCOM transceiver configuration. Binding assume that RFXCOM transceiver is
preconfigured e.g. via RFXcom Manager. When this is enabled, both set mode command and individual message
configurations are ignored.</description>
<label>@text/config.ignoreConfig.label</label>
<description>@text/config.ignoreConfig.description</description>
<default>true</default>
</parameter>
<parameter name="setMode" type="text">
<label>RFXCOM Transceiver Mode</label>
<description>RFXCOM transceiver set mode command. Command should be in hexadecimal string format and 28 characters
(14 bytes) long. If set mode command is given, individual message configurations are ignored.</description>
<label>@text/config.setMode.label</label>
<description>@text/config.setMode.description</description>
</parameter>
<parameter name="transceiverType" type="text">
<label>RFXCOM Transceiver Type</label>
<description>RFXCOM transceiver type.</description>
<label>@text/config.transceiverType.label</label>
<description>@text/config.transceiverType.description</description>
<default>315MHz</default>
<options>
<option value="310MHz">310MHz</option>
<option value="315MHz">315MHz</option>
<option value="310MHz">@text/config.transceiverType.option.310MHz</option>
<option value="315MHz">@text/config.transceiverType.option.315MHz</option>
</options>
</parameter>
<parameter name="transmitPower" type="integer" min="-18" max="10">
<label>Transmit Power</label>
<description>Transmit power in dBm, between -18dBm and +10dBm.</description>
<label>@text/config.transmitPower.label</label>
<description>@text/config.transmitPower.description</description>
<default>-18</default>
</parameter>
<parameter name="enableUndecoded" type="boolean">
<label>Undecoded Messages</label>
<description>Enable display of unencoded messages to RFXCOM transceiver.</description>
<label>@text/config.enableUndecoded.label</label>
<description>@text/config.enableUndecoded.description</description>
<default>false</default>
</parameter>
<parameter name="enableVisonic" type="boolean">
<label>Visonic Messages</label>
<description>Enable Visonic messages to RFXCOM transceiver.</description>
<label>@text/config.enableVisonic.label</label>
<description>@text/config.enableVisonic.description</description>
<default>false</default>
</parameter>
<parameter name="enableX10" type="boolean">
<label>X10 Messages</label>
<description>Enable X10 messages to RFXCOM transceiver.</description>
<label>@text/config.enableX10.label</label>
<description>@text/config.enableX10.description</description>
<default>false</default>
</parameter>

120
_thing_types/org.openhab.binding.rfxcom/src/main/resources/OH-INF/thing/RFXtrx433.xml
View File

@ -10,150 +10,146 @@
<config-description>
<parameter name="bridgeId" type="text" required="true">
<label>Serial Number</label>
<description>Serial number of the RFXCOM (FTDI) device</description>
<label>@text/config.bridgeId.label</label>
<description>@text/config.bridgeId.description</description>
</parameter>
<parameter name="disableDiscovery" type="boolean" required="true">
<label>Disable Discovery of Unknown Devices</label>
<description>These RF protocols are prone to noise. If you find a lot of unknown devices showing up in your inbox
enabling this will stop devices being added to your inbox.</description>
<label>@text/config.disableDiscovery.label</label>
<description>@text/config.disableDiscovery.description</description>
<default>false</default>
</parameter>
<parameter name="ignoreConfig" type="boolean">
<label>Skip Transceiver Configuration</label>
<description>Fully skip and ignore RFXCOM transceiver configuration. Binding assume that RFXCOM transceiver is
preconfigured e.g. via RFXcom Manager. When this is enabled, both set mode command and individual message
configurations are ignored.</description>
<label>@text/config.ignoreConfig.label</label>
<description>@text/config.ignoreConfig.description</description>
<default>true</default>
</parameter>
<parameter name="setMode" type="text">
<label>RFXCOM Transceiver Mode</label>
<description>RFXCOM transceiver set mode command. Command should be in hexadecimal string format and 28 characters
(14 bytes) long. If set mode command is given, individual message configurations are ignored.</description>
<label>@text/config.setMode.label</label>
<description>@text/config.setMode.description</description>
</parameter>
<parameter name="transmitPower" type="integer" min="-18" max="10">
<label>Transmit Power</label>
<description>Transmit power in dBm, between -18dBm and +10dBm.</description>
<label>@text/config.transmitPower.label</label>
<description>@text/config.transmitPower.description</description>
<default>-18</default>
</parameter>
<parameter name="enableUndecoded" type="boolean">
<label>Undecoded Messages</label>
<description>Enable display of unencoded messages to RFXCOM transceiver.</description>
<label>@text/config.enableUndecoded.label</label>
<description>@text/config.enableUndecoded.description</description>
<default>false</default>
</parameter>
<parameter name="enableImagintronixOpus" type="boolean">
<label>Imagintronix/Opus Messages</label>
<description>Enable Imagintronix/Opus messages to RFXCOM transceiver.</description>
<label>@text/config.enableImagintronixOpus.label</label>
<description>@text/config.enableImagintronixOpus.description</description>
<default>false</default>
</parameter>
<parameter name="enableByronSX" type="boolean">
<label>Byron SX Messages</label>
<description>Enable Byron SX messages to RFXCOM transceiver.</description>
<label>@text/config.enableByronSX.label</label>
<description>@text/config.enableByronSX.description</description>
<default>false</default>
</parameter>
<parameter name="enableRSL" type="boolean">
<label>RSL Messages</label>
<description>Enable RSL messages to RFXCOM transceiver.</description>
<label>@text/config.enableRSL.label</label>
<description>@text/config.enableRSL.description</description>
<default>false</default>
</parameter>
<parameter name="enableLighting4" type="boolean">
<label>Lighting4 Messages</label>
<description>Enable Lighting4 messages to RFXCOM transceiver.</description>
<label>@text/config.enableLighting4.label</label>
<description>@text/config.enableLighting4.description</description>
<default>false</default>
</parameter>
<parameter name="enableFineOffsetViking" type="boolean">
<label>FineOffset/Viking Messages</label>
<description>Enable FineOffset/Viking messages to RFXCOM transceiver.</description>
<label>@text/config.enableFineOffsetViking.label</label>
<description>@text/config.enableFineOffsetViking.description</description>
<default>false</default>
</parameter>
<parameter name="enableRubicson" type="boolean">
<label>Rubicson Messages</label>
<description>Enable Rubicson messages to RFXCOM transceiver.</description>
<label>@text/config.enableRubicson.label</label>
<description>@text/config.enableRubicson.description</description>
<default>false</default>
</parameter>
<parameter name="enableAEBlyss" type="boolean">
<label>AE Blyss Messages</label>
<description>Enable AE Blyss messages to RFXCOM transceiver.</description>
<label>@text/config.enableAEBlyss.label</label>
<description>@text/config.enableAEBlyss.description</description>
<default>false</default>
</parameter>
<parameter name="enableBlindsT1T2T3T4" type="boolean">
<label>BlindsT1/T2/T3/T4 Messages</label>
<description>Enable BlindsT1/T2/T3/T4 messages to RFXCOM transceiver.</description>
<label>@text/config.enableBlindsT1T2T3T4.label</label>
<description>@text/config.enableBlindsT1T2T3T4.description</description>
<default>false</default>
</parameter>
<parameter name="enableBlindsT0" type="boolean">
<label>BlindsT0 Messages</label>
<description>Enable BlindsT0 messages to RFXCOM transceiver.</description>
<label>@text/config.enableBlindsT0.label</label>
<description>@text/config.enableBlindsT0.description</description>
<default>false</default>
</parameter>
<parameter name="enableFS20" type="boolean">
<label>FS20/Legrand CAD Messages</label>
<description>Enable FS20/Legrand CAD messages to RFXCOM transceiver.</description>
<label>@text/config.enableFS20.label</label>
<description>@text/config.enableFS20.description</description>
<default>false</default>
</parameter>
<parameter name="enableLaCrosse" type="boolean">
<label>La Crosse Messages</label>
<description>Enable La Crosse messages to RFXCOM transceiver.</description>
<label>@text/config.enableLaCrosse.label</label>
<description>@text/config.enableLaCrosse.description</description>
<default>false</default>
</parameter>
<parameter name="enableHidekiUPM" type="boolean">
<label>Hideki/UPM Messages</label>
<description>Enable Hideki/UPM messages to RFXCOM transceiver.</description>
<label>@text/config.enableHidekiUPM.label</label>
<description>@text/config.enableHidekiUPM.description</description>
<default>false</default>
</parameter>
<parameter name="enableADLightwaveRF" type="boolean">
<label>AD LightwaveRF Messages</label>
<description>Enable AD LightwaveRF messages to RFXCOM transceiver.</description>
<label>@text/config.enableADLightwaveRF.label</label>
<description>@text/config.enableADLightwaveRF.description</description>
<default>false</default>
</parameter>
<parameter name="enableMertik" type="boolean">
<label>Mertik Messages</label>
<description>Enable Mertik messages to RFXCOM transceiver.</description>
<label>@text/config.enableMertik.label</label>
<description>@text/config.enableMertik.description</description>
<default>false</default>
</parameter>
<parameter name="enableATI" type="boolean">
<label>ATI Messages</label>
<description>Enable ATI messages to RFXCOM transceiver.</description>
<label>@text/config.enableATI.label</label>
<description>@text/config.enableATI.description</description>
<default>false</default>
</parameter>
<parameter name="enableOregonScientific" type="boolean">
<label>Oregon Scientific Messages</label>
<description>Enable Oregon Scientific messages to RFXCOM transceiver.</description>
<label>@text/config.enableOregonScientific.label</label>
<description>@text/config.enableOregonScientific.description</description>
<default>false</default>
</parameter>
<parameter name="enableMeiantech" type="boolean">
<label>Meiantech Messages</label>
<description>Enable Meiantech messages to RFXCOM transceiver.</description>
<label>@text/config.enableMeiantech.label</label>
<description>@text/config.enableMeiantech.description</description>
<default>false</default>
</parameter>
<parameter name="enableHomeEasyEU" type="boolean">
<label>HomeEasy EU Messages</label>
<description>Enable HomeEasy EU messages to RFXCOM transceiver.</description>
<label>@text/config.enableHomeEasyEU.label</label>
<description>@text/config.enableHomeEasyEU.description</description>
<default>false</default>
</parameter>
<parameter name="enableAC" type="boolean">
<label>AC Messages</label>
<description>Enable AC messages to RFXCOM transceiver.</description>
<label>@text/config.enableAC.label</label>
<description>@text/config.enableAC.description</description>
<default>false</default>
</parameter>
<parameter name="enableARC" type="boolean">
<label>ARC Messages</label>
<description>Enable ARC messages to RFXCOM transceiver.</description>
<label>@text/config.enableARC.label</label>
<description>@text/config.enableARC.description</description>
<default>false</default>
</parameter>
<parameter name="enableX10" type="boolean">
<label>X10 Messages</label>
<description>Enable X10 messages to RFXCOM transceiver.</description>
<label>@text/config.enableX10.label</label>
<description>@text/config.enableX10.description</description>
<default>false</default>
</parameter>
<parameter name="enableHomeConfort" type="boolean">
<label>HomeConfort Messages</label>
<description>Enable HomeConfort messages to RFXCOM transceiver.</description>
<label>@text/config.enableHomeConfort.label</label>
<description>@text/config.enableHomeConfort.description</description>
<default>false</default>
</parameter>
<parameter name="enableKEELOQ" type="boolean">
<label>KEELOQ Messages</label>
<description>Enable KEELOQ messages to RFXCOM transceiver.</description>
<label>@text/config.enableKEELOQ.label</label>
<description>@text/config.enableKEELOQ.description</description>
<default>false</default>
</parameter>

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

@ -25,7 +25,7 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 56923</description>
</parameter>
</config-description>

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

@ -25,12 +25,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id + unit code, separated by dot. Example 23455.1</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="T0">RollerTrol, Hasta new</option>
<option value="T1">Hasta old</option>

138
_thing_types/org.openhab.binding.rfxcom/src/main/resources/OH-INF/thing/bridge.xml
View File

@ -16,169 +16,163 @@
<description>Serial port where RFXCOM transceiver is connected.</description>
</parameter>
<parameter name="disableDiscovery" type="boolean" required="true">
<label>Disable Discovery of Unknown Devices</label>
<description>These RF protocols are prone to noise. If you find a lot of unknown devices showing up in your inbox
enabling this will stop devices being added to your inbox.</description>
<label>@text/config.disableDiscovery.label</label>
<description>@text/config.disableDiscovery.description</description>
<default>false</default>
</parameter>
<parameter name="ignoreConfig" type="boolean" required="true">
<label>Skip Transceiver Configuration</label>
<description>Fully skip and ignore RFXCOM transceiver configuration. Binding assume that RFXCOM transceiver is
preconfigured e.g. via RFXcom Manager. When this is enabled, both set mode command and individual message
configurations are ignored.
</description>
<label>@text/config.ignoreConfig.label</label>
<description>@text/config.ignoreConfig.description</description>
<default>true</default>
</parameter>
<parameter name="setMode" type="text">
<label>RFXCOM Transceiver Mode</label>
<description>RFXCOM transceiver set mode command. Command should be in hexadecimal string format and 28 characters
(14 bytes) long. If set mode command is given, individual message configurations are ignored.
</description>
<label>@text/config.setMode.label</label>
<description>@text/config.setMode.description</description>
</parameter>
<parameter name="transceiverType" type="text">
<label>RFXCOM Transceiver Type</label>
<description>RFXCOM transceiver type.</description>
<label>@text/config.transceiverType.label</label>
<description>@text/config.transceiverType.description</description>
<default>433.92MHz</default>
<options>
<option value="310MHz">310MHz</option>
<option value="315MHz">315MHz</option>
<option value="433.92MHz receiver only">433.92MHz receiver only</option>
<option value="433.92MHz">433.92MHz</option>
<option value="310MHz">@text/config.transceiverType.option.310MHz</option>
<option value="315MHz">@text/config.transceiverType.option.315MHz</option>
<option value="433.92MHz receiver only">@text/config.transceiverType.option.433MHz_receiver_only</option>
<option value="433.92MHz">@text/config.transceiverType.option.433MHz</option>
</options>
</parameter>
<parameter name="transmitPower" type="integer" min="-18" max="10">
<label>Transmit Power</label>
<description>Transmit power in dBm, between -18dBm and +10dBm.</description>
<label>@text/config.transmitPower.label</label>
<description>@text/config.transmitPower.description</description>
<default>-18</default>
</parameter>
<parameter name="enableUndecoded" type="boolean">
<label>Undecoded Messages</label>
<description>Enable display of unencoded messages to RFXCOM transceiver.</description>
<label>@text/config.enableUndecoded.label</label>
<description>@text/config.enableUndecoded.description</description>
<default>false</default>
</parameter>
<parameter name="enableImagintronixOpus" type="boolean">
<label>Imagintronix/Opus Messages</label>
<description>Enable Imagintronix/Opus messages to RFXCOM transceiver.</description>
<label>@text/config.enableImagintronixOpus.label</label>
<description>@text/config.enableImagintronixOpus.description</description>
<default>false</default>
</parameter>
<parameter name="enableByronSX" type="boolean">
<label>Byron SX Messages</label>
<description>Enable Byron SX messages to RFXCOM transceiver.</description>
<label>@text/config.enableByronSX.label</label>
<description>@text/config.enableByronSX.description</description>
<default>false</default>
</parameter>
<parameter name="enableRSL" type="boolean">
<label>RSL Messages</label>
<description>Enable RSL messages to RFXCOM transceiver.</description>
<label>@text/config.enableRSL.label</label>
<description>@text/config.enableRSL.description</description>
<default>false</default>
</parameter>
<parameter name="enableLighting4" type="boolean">
<label>Lighting4 Messages</label>
<description>Enable Lighting4 messages to RFXCOM transceiver.</description>
<label>@text/config.enableLighting4.label</label>
<description>@text/config.enableLighting4.description</description>
<default>false</default>
</parameter>
<parameter name="enableFineOffsetViking" type="boolean">
<label>FineOffset/Viking Messages</label>
<description>Enable FineOffset/Viking messages to RFXCOM transceiver.</description>
<label>@text/config.enableFineOffsetViking.label</label>
<description>@text/config.enableFineOffsetViking.description</description>
<default>false</default>
</parameter>
<parameter name="enableRubicson" type="boolean">
<label>Rubicson Messages</label>
<description>Enable Rubicson messages to RFXCOM transceiver.</description>
<label>@text/config.enableRubicson.label</label>
<description>@text/config.enableRubicson.description</description>
<default>false</default>
</parameter>
<parameter name="enableAEBlyss" type="boolean">
<label>AE Blyss Messages</label>
<description>Enable AE Blyss messages to RFXCOM transceiver.</description>
<label>@text/config.enableAEBlyss.label</label>
<description>@text/config.enableAEBlyss.description</description>
<default>false</default>
</parameter>
<parameter name="enableBlindsT1T2T3T4" type="boolean">
<label>BlindsT1/T2/T3/T4 Messages</label>
<description>Enable BlindsT1/T2/T3/T4 messages to RFXCOM transceiver.</description>
<label>@text/config.enableBlindsT1T2T3T4.label</label>
<description>@text/config.enableBlindsT1T2T3T4.description</description>
<default>false</default>
</parameter>
<parameter name="enableBlindsT0" type="boolean">
<label>BlindsT0 Messages</label>
<description>Enable BlindsT0 messages to RFXCOM transceiver.</description>
<label>@text/config.enableBlindsT0.label</label>
<description>@text/config.enableBlindsT0.description</description>
<default>false</default>
</parameter>
<parameter name="enableProGuard" type="boolean">
<label>ProGuard Messages</label>
<description>Enable ProGuard messages to RFXCOM transceiver.</description>
<label>@text/config.enableProGuard.label</label>
<description>@text/config.enableProGuard.description</description>
<default>false</default>
</parameter>
<parameter name="enableFS20" type="boolean">
<label>FS20/Legrand CAD Messages</label>
<description>Enable FS20/Legrand CAD messages to RFXCOM transceiver.</description>
<label>@text/config.enableFS20.label</label>
<description>@text/config.enableFS20.description</description>
<default>false</default>
</parameter>
<parameter name="enableLaCrosse" type="boolean">
<label>La Crosse Messages</label>
<description>Enable La Crosse messages to RFXCOM transceiver.</description>
<label>@text/config.enableLaCrosse.label</label>
<description>@text/config.enableLaCrosse.description</description>
<default>false</default>
</parameter>
<parameter name="enableHidekiUPM" type="boolean">
<label>Hideki/UPM Messages</label>
<description>Enable Hideki/UPM messages to RFXCOM transceiver.</description>
<label>@text/config.enableHidekiUPM.label</label>
<description>@text/config.enableHidekiUPM.description</description>
<default>false</default>
</parameter>
<parameter name="enableADLightwaveRF" type="boolean">
<label>AD LightwaveRF Messages</label>
<description>Enable AD LightwaveRF messages to RFXCOM transceiver.</description>
<label>@text/config.enableADLightwaveRF.label</label>
<description>@text/config.enableADLightwaveRF.description</description>
<default>false</default>
</parameter>
<parameter name="enableMertik" type="boolean">
<label>Mertik Messages</label>
<description>Enable Mertik messages to RFXCOM transceiver.</description>
<label>@text/config.enableMertik.label</label>
<description>@text/config.enableMertik.description</description>
<default>false</default>
</parameter>
<parameter name="enableVisonic" type="boolean">
<label>Visonic Messages</label>
<description>Enable Visonic messages to RFXCOM transceiver.</description>
<label>@text/config.enableVisonic.label</label>
<description>@text/config.enableVisonic.description</description>
<default>false</default>
</parameter>
<parameter name="enableATI" type="boolean">
<label>ATI Messages</label>
<description>Enable ATI messages to RFXCOM transceiver.</description>
<label>@text/config.enableATI.label</label>
<description>@text/config.enableATI.description</description>
<default>false</default>
</parameter>
<parameter name="enableOregonScientific" type="boolean">
<label>Oregon Scientific Messages</label>
<description>Enable Oregon Scientific messages to RFXCOM transceiver.</description>
<label>@text/config.enableOregonScientific.label</label>
<description>@text/config.enableOregonScientific.description</description>
<default>false</default>
</parameter>
<parameter name="enableMeiantech" type="boolean">
<label>Meiantech Messages</label>
<description>Enable Meiantech messages to RFXCOM transceiver.</description>
<label>@text/config.enableMeiantech.label</label>
<description>@text/config.enableMeiantech.description</description>
<default>false</default>
</parameter>
<parameter name="enableHomeEasyEU" type="boolean">
<label>HomeEasy EU Messages</label>
<description>Enable HomeEasy EU messages to RFXCOM transceiver.</description>
<label>@text/config.enableHomeEasyEU.label</label>
<description>@text/config.enableHomeEasyEU.description</description>
<default>false</default>
</parameter>
<parameter name="enableAC" type="boolean">
<label>AC Messages</label>
<description>Enable AC messages to RFXCOM transceiver.</description>
<label>@text/config.enableAC.label</label>
<description>@text/config.enableAC.description</description>
<default>false</default>
</parameter>
<parameter name="enableARC" type="boolean">
<label>ARC Messages</label>
<description>Enable ARC messages to RFXCOM transceiver.</description>
<label>@text/config.enableARC.label</label>
<description>@text/config.enableARC.description</description>
<default>false</default>
</parameter>
<parameter name="enableX10" type="boolean">
<label>X10 Messages</label>
<description>Enable X10 messages to RFXCOM transceiver.</description>
<label>@text/config.enableX10.label</label>
<description>@text/config.enableX10.description</description>
<default>false</default>
</parameter>
<parameter name="enableHomeConfort" type="boolean">
<label>HomeConfort Messages</label>
<description>Enable HomeConfort messages to RFXCOM transceiver.</description>
<label>@text/config.enableHomeConfort.label</label>
<description>@text/config.enableHomeConfort.description</description>
<default>false</default>
</parameter>
<parameter name="enableKEELOQ" type="boolean">
<label>KEELOQ Messages</label>
<description>Enable KEELOQ messages to RFXCOM transceiver.</description>
<label>@text/config.enableKEELOQ.label</label>
<description>@text/config.enableKEELOQ.description</description>
<default>false</default>
</parameter>

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

@ -22,12 +22,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 2983</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="BYRONSX">Byron SX</option>
<option value="BYRONMP001">Byron MP001</option>

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

@ -26,12 +26,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 5693</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="ELEC1">CM113</option>
</options>

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

@ -27,12 +27,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 47104</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="ELEC4">OWL - CM180i</option>
</options>

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

@ -25,12 +25,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>House code + unit code, separated by dot. Example A.1</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="HARRISON">Harrison Curtain</option>
</options>

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

@ -24,12 +24,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Device id, example 47360</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="RTGR328N">Oregon RTGR328N</option>
</options>

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

@ -27,12 +27,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 5693</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="ELEC2">CM119/160</option>
<option value="ELEC3">CM180</option>

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

@ -24,7 +24,7 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Unit Id. Example 'B', '7' or 'D'</description>
<options>
<option value="00">0</option>
@ -46,8 +46,8 @@
</options>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="LUCCI_AIR_FAN">Lucci Air fan</option>
<option value="CASAFAN">Casafan</option>

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

@ -24,12 +24,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Unit Id. Example 1000</description>
</parameter>
<parameter name="subType" type="text">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="FALMEC">Falmec</option>
</options>

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

@ -24,12 +24,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Unit Id. Example 1000</description>
</parameter>
<parameter name="subType" type="text">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="LUCCI_AIR_DC">Lucci Air DC</option>
</options>

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

@ -25,12 +25,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Unit Id. Example 1000</description>
</parameter>
<parameter name="subType" type="text">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="LUCCI_AIR_DC_II">Lucci Air DC II</option>
</options>

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

@ -24,12 +24,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Unit Id. Example 1000</description>
</parameter>
<parameter name="subType" type="text">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="NOVY">Novy extractor fan</option>
</options>

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

@ -23,7 +23,7 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Device Id. Unit ID + house code + unit code, each separated by dot. Example 1234.A.1</description>
</parameter>
</config-description>

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

@ -25,12 +25,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 5693</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="HUM1">LaCrosse TX3</option>
<option value="HUM2">LaCrosse WS2300</option>

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

@ -25,12 +25,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Device Id. House code + unit code, separated by dot. Example A.1</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="X10">X10 lighting</option>
<option value="ARC">ARC</option>

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

@ -24,12 +24,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Remote/switch/unit Id + unit code, separated by dot. Example 8773718.10</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="AC">AC</option>
<option value="HOME_EASY_EU">HomeEasy EU</option>

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

@ -23,12 +23,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Device Id. Example 3456</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="PT2262">PT2262</option>
</options>

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

@ -26,12 +26,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Remote/switch/unit Id + unit code, separated by dot. Example 10001.1</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="AOKE">Aoke Relay</option>
<option value="AVANTEK">Avantek</option>

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

@ -23,12 +23,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Remote/switch/unit Id + group code + unit code, separated by dot. Example 100.A.1</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="BLYSS">Blyss</option>
</options>

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

@ -25,12 +25,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 56923</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="RAIN1">RGR126/682/918/928</option>
<option value="RAIN2">PCR800</option>

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

@ -24,13 +24,13 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Received raw message cannot provide a device ID, so to receive raw messages the device id must be RAW.
For transmit-only things, use any device id.</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="RAW_PACKET1">RAW_PACKET1</option>
<option value="RAW_PACKET2">RAW_PACKET2</option>

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

@ -25,7 +25,7 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 8</description>
</parameter>
</config-description>

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

@ -32,12 +32,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Unit Id + unit code, separated by dot. Example 100.1</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="RFY">RFY</option>
<option value="RFY_EXT">RFY Ext</option>

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

@ -27,12 +27,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Remote/sensor Id. Example 10001</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="X10_SECURITY">X10 security door/window sensor</option>
<option value="X10_SECURITY_MOTION">X10 security motion sensor</option>

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

@ -27,7 +27,7 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Remote/sensor Id. Example 10001</description>
</parameter>
</config-description>

136
_thing_types/org.openhab.binding.rfxcom/src/main/resources/OH-INF/thing/tcpbridge.xml
View File

@ -20,167 +20,163 @@
<default>10001</default>
</parameter>
<parameter name="disableDiscovery" type="boolean" required="true">
<label>Disable Discovery of Unknown Devices</label>
<description>These RF protocols are prone to noise. If you find a lot of unknown devices showing up in your inbox
enabling this will stop devices being added to your inbox.</description>
<label>@text/config.disableDiscovery.label</label>
<description>@text/config.disableDiscovery.description</description>
<default>false</default>
</parameter>
<parameter name="ignoreConfig" type="boolean" required="true">
<label>Skip Transceiver Configuration</label>
<description>Fully skip and ignore RFXCOM transceiver configuration. Binding assume that RFXCOM transceiver is
preconfigured e.g. via RFXcom Manager. When this is enabled, both set mode command and individual message
configurations are ignored.</description>
<label>@text/config.ignoreConfig.label</label>
<description>@text/config.ignoreConfig.description</description>
<default>true</default>
</parameter>
<parameter name="setMode" type="text">
<label>RFXCOM Transceiver Mode</label>
<description>RFXCOM transceiver set mode command. Command should be in hexadecimal string format and 28 characters
(14 bytes) long. If set mode command is given, individual message configurations are ignored.</description>
<label>@text/config.setMode.label</label>
<description>@text/config.setMode.description</description>
</parameter>
<parameter name="transceiverType" type="text">
<label>RFXCOM Transceiver Type</label>
<description>RFXCOM transceiver type.</description>
<label>@text/config.transceiverType.label</label>
<description>@text/config.transceiverType.description</description>
<default>433.92MHz</default>
<options>
<option value="310MHz">310MHz</option>
<option value="315MHz">315MHz</option>
<option value="433.92MHz receiver only">433.92MHz receiver only</option>
<option value="433.92MHz">433.92MHz</option>
<option value="310MHz">@text/config.transceiverType.option.310MHz</option>
<option value="315MHz">@text/config.transceiverType.option.315MHz</option>
<option value="433.92MHz receiver only">@text/config.transceiverType.option.433MHz_receiver_only</option>
<option value="433.92MHz">@text/config.transceiverType.option.433MHz</option>
</options>
</parameter>
<parameter name="transmitPower" type="integer" min="-18" max="10">
<label>Transmit Power</label>
<description>Transmit power in dBm, between -18dBm and +10dBm.</description>
<label>@text/config.transmitPower.label</label>
<description>@text/config.transmitPower.description</description>
<default>-18</default>
</parameter>
<parameter name="enableUndecoded" type="boolean">
<label>Undecoded Messages</label>
<description>Enable display of unencoded messages to RFXCOM transceiver.</description>
<label>@text/config.enableUndecoded.label</label>
<description>@text/config.enableUndecoded.description</description>
<default>false</default>
</parameter>
<parameter name="enableImagintronixOpus" type="boolean">
<label>Imagintronix/Opus Messages</label>
<description>Enable Imagintronix/Opus messages to RFXCOM transceiver.</description>
<label>@text/config.enableImagintronixOpus.label</label>
<description>@text/config.enableImagintronixOpus.description</description>
<default>false</default>
</parameter>
<parameter name="enableByronSX" type="boolean">
<label>Byron SX Messages</label>
<description>Enable Byron SX messages to RFXCOM transceiver.</description>
<label>@text/config.enableByronSX.label</label>
<description>@text/config.enableByronSX.description</description>
<default>false</default>
</parameter>
<parameter name="enableRSL" type="boolean">
<label>RSL Messages</label>
<description>Enable RSL messages to RFXCOM transceiver.</description>
<label>@text/config.enableRSL.label</label>
<description>@text/config.enableRSL.description</description>
<default>false</default>
</parameter>
<parameter name="enableLighting4" type="boolean">
<label>Lighting4 Messages</label>
<description>Enable Lighting4 messages to RFXCOM transceiver.</description>
<label>@text/config.enableLighting4.label</label>
<description>@text/config.enableLighting4.description</description>
<default>false</default>
</parameter>
<parameter name="enableFineOffsetViking" type="boolean">
<label>FineOffset/Viking Messages</label>
<description>Enable FineOffset/Viking messages to RFXCOM transceiver.</description>
<label>@text/config.enableFineOffsetViking.label</label>
<description>@text/config.enableFineOffsetViking.description</description>
<default>false</default>
</parameter>
<parameter name="enableRubicson" type="boolean">
<label>Rubicson Messages</label>
<description>Enable Rubicson messages to RFXCOM transceiver.</description>
<label>@text/config.enableRubicson.label</label>
<description>@text/config.enableRubicson.description</description>
<default>false</default>
</parameter>
<parameter name="enableAEBlyss" type="boolean">
<label>AE Blyss Messages</label>
<description>Enable AE Blyss messages to RFXCOM transceiver.</description>
<label>@text/config.enableAEBlyss.label</label>
<description>@text/config.enableAEBlyss.description</description>
<default>false</default>
</parameter>
<parameter name="enableBlindsT1T2T3T4" type="boolean">
<label>BlindsT1/T2/T3/T4 Messages</label>
<description>Enable BlindsT1/T2/T3/T4 messages to RFXCOM transceiver.</description>
<label>@text/config.enableBlindsT1T2T3T4.label</label>
<description>@text/config.enableBlindsT1T2T3T4.description</description>
<default>false</default>
</parameter>
<parameter name="enableBlindsT0" type="boolean">
<label>BlindsT0 Messages</label>
<description>Enable BlindsT0 messages to RFXCOM transceiver.</description>
<label>@text/config.enableBlindsT0.label</label>
<description>@text/config.enableBlindsT0.description</description>
<default>false</default>
</parameter>
<parameter name="enableProGuard" type="boolean">
<label>ProGuard Messages</label>
<description>Enable ProGuard messages to RFXCOM transceiver.</description>
<label>@text/config.enableProGuard.label</label>
<description>@text/config.enableProGuard.description</description>
<default>false</default>
</parameter>
<parameter name="enableFS20" type="boolean">
<label>FS20/Legrand CAD Messages</label>
<description>Enable FS20/Legrand CAD messages to RFXCOM transceiver.</description>
<label>@text/config.enableFS20.label</label>
<description>@text/config.enableFS20.description</description>
<default>false</default>
</parameter>
<parameter name="enableLaCrosse" type="boolean">
<label>La Crosse Messages</label>
<description>Enable La Crosse messages to RFXCOM transceiver.</description>
<label>@text/config.enableLaCrosse.label</label>
<description>@text/config.enableLaCrosse.description</description>
<default>false</default>
</parameter>
<parameter name="enableHidekiUPM" type="boolean">
<label>Hideki/UPM Messages</label>
<description>Enable Hideki/UPM messages to RFXCOM transceiver.</description>
<label>@text/config.enableHidekiUPM.label</label>
<description>@text/config.enableHidekiUPM.description</description>
<default>false</default>
</parameter>
<parameter name="enableADLightwaveRF" type="boolean">
<label>AD LightwaveRF Messages</label>
<description>Enable AD LightwaveRF messages to RFXCOM transceiver.</description>
<label>@text/config.enableADLightwaveRF.label</label>
<description>@text/config.enableADLightwaveRF.description</description>
<default>false</default>
</parameter>
<parameter name="enableMertik" type="boolean">
<label>Mertik Messages</label>
<description>Enable Mertik messages to RFXCOM transceiver.</description>
<label>@text/config.enableMertik.label</label>
<description>@text/config.enableMertik.description</description>
<default>false</default>
</parameter>
<parameter name="enableVisonic" type="boolean">
<label>Visonic Messages</label>
<description>Enable Visonic messages to RFXCOM transceiver.</description>
<label>@text/config.enableVisonic.label</label>
<description>@text/config.enableVisonic.description</description>
<default>false</default>
</parameter>
<parameter name="enableATI" type="boolean">
<label>ATI Messages</label>
<description>Enable ATI messages to RFXCOM transceiver.</description>
<label>@text/config.enableATI.label</label>
<description>@text/config.enableATI.description</description>
<default>false</default>
</parameter>
<parameter name="enableOregonScientific" type="boolean">
<label>Oregon Scientific Messages</label>
<description>Enable Oregon Scientific messages to RFXCOM transceiver.</description>
<label>@text/config.enableOregonScientific.label</label>
<description>@text/config.enableOregonScientific.description</description>
<default>false</default>
</parameter>
<parameter name="enableMeiantech" type="boolean">
<label>Meiantech Messages</label>
<description>Enable Meiantech messages to RFXCOM transceiver.</description>
<label>@text/config.enableMeiantech.label</label>
<description>@text/config.enableMeiantech.description</description>
<default>false</default>
</parameter>
<parameter name="enableHomeEasyEU" type="boolean">
<label>HomeEasy EU Messages</label>
<description>Enable HomeEasy EU messages to RFXCOM transceiver.</description>
<label>@text/config.enableHomeEasyEU.label</label>
<description>@text/config.enableHomeEasyEU.description</description>
<default>false</default>
</parameter>
<parameter name="enableAC" type="boolean">
<label>AC Messages</label>
<description>Enable AC messages to RFXCOM transceiver.</description>
<label>@text/config.enableAC.label</label>
<description>@text/config.enableAC.description</description>
<default>false</default>
</parameter>
<parameter name="enableARC" type="boolean">
<label>ARC Messages</label>
<description>Enable ARC messages to RFXCOM transceiver.</description>
<label>@text/config.enableARC.label</label>
<description>@text/config.enableARC.description</description>
<default>false</default>
</parameter>
<parameter name="enableX10" type="boolean">
<label>X10 Messages</label>
<description>Enable X10 messages to RFXCOM transceiver.</description>
<label>@text/config.enableX10.label</label>
<description>@text/config.enableX10.description</description>
<default>false</default>
</parameter>
<parameter name="enableHomeConfort" type="boolean">
<label>HomeConfort Messages</label>
<description>Enable HomeConfort messages to RFXCOM transceiver.</description>
<label>@text/config.enableHomeConfort.label</label>
<description>@text/config.enableHomeConfort.description</description>
<default>false</default>
</parameter>
<parameter name="enableKEELOQ" type="boolean">
<label>KEELOQ Messages</label>
<description>Enable KEELOQ messages to RFXCOM transceiver.</description>
<label>@text/config.enableKEELOQ.label</label>
<description>@text/config.enableKEELOQ.description</description>
<default>false</default>
</parameter>

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

@ -24,12 +24,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 56923</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="TEMP1">THR128/138, THC138</option>
<option value="TEMP2">THC238/268,THN132,THWR288,THRN122,THN122,AW129/131</option>

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

@ -26,12 +26,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 56923</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="TH1">THGN122/123, THGN132, THGR122/228/238/268</option>
<option value="TH2">THGR810, THGN800</option>

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

@ -28,12 +28,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 59648</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="THB1">BTHR918, BTHGN129</option>
<option value="THB2">BTHR918N, BTHR968</option>

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

@ -25,12 +25,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 56923</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="WS1200">WS1200</option>
</options>

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

@ -24,12 +24,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 56923</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="DIGIMAX">Digimax, TLX7506</option>
<option value="DIGIMAX_SHORT">Digimax with short format (no set point)</option>

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

@ -25,12 +25,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 106411</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="MERTIK__G6R_H4T1">Mertik (G6R H4T1)</option>
<option value="MERTIK__G6R_H4TB__G6R_H4T__G6R_H4T21_Z22">Mertik (G6R H4TB, G6R H4T, or G6R

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

@ -22,12 +22,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Undecoded items cannot provide a device ID, so this value is always UNDECODED.</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="AC">AC</option>
<option value="ARC">ARC</option>

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

@ -25,12 +25,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 56923</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="UV1">UVN128, UV138</option>
<option value="UV2">UVN800</option>

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

@ -37,12 +37,12 @@
<config-description>
<parameter name="deviceId" type="text" required="true">
<label>Device Id</label>
<label>@text/config.deviceId.label</label>
<description>Sensor Id. Example 2983</description>
</parameter>
<parameter name="subType" type="text" required="true">
<label>Sub Type</label>
<description>Specifies device sub type.</description>
<label>@text/config.subType.label</label>
<description>@text/config.subType.description</description>
<options>
<option value="WIND1">WTGR800</option>
<option value="WIND2">WGR800</option>

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

@ -1072,7 +1072,7 @@
<channels>
<channel id="counter1" typeId="counter"/>
<channel id="counter1Current" typeId="counter"/>
<channel id="counter" typeId="counter"/>
<channel id="counter2" typeId="counter"/>
<channel id="counter2Current" typeId="counter"/>
<channel id="counter3" typeId="counter"/>
<channel id="counter3Current" typeId="counter"/>

15
_thing_types/org.openhab.binding.zigbee/org.openhab.binding.zigbee.ember/src/main/resources/OH-INF/thing/controller_ember.xml
View File

@ -208,11 +208,16 @@
<advanced>true</advanced>
</parameter>
<parameter name="zigbee_installcode" type="text" groupName="network">
<label>Install Code</label>
<description>Add a temporary install key for device installation</description>
<advanced>true</advanced>
</parameter>
<parameter name="zigbee_installcode" type="text" groupName="network">
<label>Install Code</label>
<description>Add a temporary install key for device installation</description>
<advanced>true</advanced>
</parameter>
<parameter name="zigbee_groupregistration" type="text" groupName="network">
<label>Group Registrations</label>
<description>Registers the binding to receive group notifications. Groups are separated by a comma and must be defined in hexadecimal.</description>
</parameter>
<parameter name="zigbee_meshupdateperiod" type="integer" groupName="network">
<label>Mesh Update Period</label>

29
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/homeseer/hsfls100_0_0.xml
View File

@ -38,7 +38,7 @@ Floodlight Sensor<br /> <h1>Overview</h1><p>The HS-FLS100+ is a PIR module that
<property name="binding:*:DecimalType">COMMAND_CLASS_CONFIGURATION;parameter=1</property>
</properties>
</channel>
<channel id="config_decimal_param2" typeId="config_decimal">
<channel id="config_decimal_param2" typeId="homeseer_hsfls100_00_000_config_decimal_param2">
<label>Lux sensor threshold</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_CONFIGURATION;parameter=2</property>
@ -96,30 +96,41 @@ Floodlight Sensor<br /> <h1>Overview</h1><p>The HS-FLS100+ is a PIR module that
Period to send Trigger Off command after PIR is triggered.<br /> <h1>Overview</h1><p>Period to send Trigger Off command after PIR is triggered. Before this period expires, the PIR will not be able to detect any subsequent motion.</p>
]]></description>
<default>15</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_2_2" type="integer" groupName="configuration"
min="0" max="255">
<parameter name="config_2_2" type="integer" groupName="configuration">
<label>2: Lux sensor threshold</label>
<description><![CDATA[
Lux level to activate the PIR<br /> <h1>Overview</h1><p>When the lux level falls below this threshold and the PIR gets triggered, the unit emits a Basic Set Command (Value=0xFF) and turns on its floodlight. This overwrites the Lux level set by the Lux knob.</p> <p>Setting = 0: always don’t turn ON light</p> <p>Setting = 30~200: lighting activation by setting</p> <p>Setting = 255: turn ON light upon PIR triggered</p> <p>If the level is set to 0, the unit will not turn on its floodlight. The PIR will still send a notification report to the controller; if the level is set to 255, when motion is sensed, the sensor ignore the ambient brightness but just turn on the light.</p>
]]></description>
<default>50</default>
<options>
<option value="0">Light is never triggered by PIR</option>
<option value="255">Light is always triggered by PIR regardless of lux</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_2" type="integer" groupName="configuration"
min="0" max="1440">
<label>3: Auto Report luminance interval</label>
<description>sets the interval of periodic lux level report to the controller</description>
<description><![CDATA[
Sets the interval of periodic lux level report to the controller<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>10</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1" type="integer" groupName="configuration">
<label>4: Basic Report</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<options>
<option value="0">not send Basic Report</option>
<option value="1">send Basic Report</option>
<option value="0">Do not send Basic Report</option>
<option value="1">Send Basic Report (default)</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
@ -163,13 +174,17 @@ Devices in the group are controlled by the PIR sensor<br /> <h1>Overview</h1><p>
<label>Lux sensor threshold</label>
<description>Lux level to activate the PIR</description>
<state pattern="%s">
<options>
<option value="0">Light is never triggered by PIR</option>
<option value="255">Light is always triggered by PIR regardless of lux</option>
</options>
</state>
</channel-type>
<channel-type id="homeseer_hsfls100_00_000_config_decimal_param3">
<item-type>Number</item-type>
<label>Auto Report luminance interval</label>
<description>sets the interval of periodic lux level report to the controller</description>
<description>Sets the interval of periodic lux level report to the controller</description>
<state pattern="%s">
</state>
</channel-type>

303
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/nietech/mp21zp_0_0.xml
View File

@ -1,303 +0,0 @@
<?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="nietech_mp21zp_00_000" listed="false">
<label>MP21ZP Z-Wave Mini Plug with Power Meter</label>
<description><![CDATA[
Z-Wave Mini Plug with Power Meter<br /> <h1>Overview</h1><p><b>Z-Wave Plus Outlet Mini Plug with Power Meter(MP21ZP)</b><br /></p><p>Indoor use in dry location<br /></p><p>Power: 120V 60Hz</p><p>Loading: 10 Amp Max Resistive </p><p>Frequency: 908.42MHz</p><p>Temperature Range: 0°C~ 40°C / (32°F~104°F)</p><p><b>Features:</b></p><ol><li>Manual and Remote (Z-Wave) on/off control.</li><li>Z-Wave controlled AC outlet for standard incandescent lighting, CFL/LEDs, fans or small appliances(1250W Resistive Max).</li><li>Grounded 3-wire power connection for safety.</li><li>Remembers and restores on/off status after power failure.</li><li>Built-in Z-Wave Plus signal repeater to extend network range.</li><li>S2 security and 700 Z-Wave chip for reliable wireless communication.</li><li>Work with all certificated Z-Wave controllers</li></ol><p><b>Locally Button Press function:</b></p><ol><li>press 1x: turn output ON or OFF</li><li>quickly press 3x: inclusion or exclusion</li><li>quickly press 5x: change Parameter 1</li><li>quickly press 8x: change Parameter 4</li><li>quickly press 10x: Reset KWH</li><li>Factory reset: click Z-Wave button 2 twice quickly, then hold for at least 10 seconds.</li></ol> <br /> <h2>Inclusion Information</h2><p><b>Adding Device To Z-Wave Network:</b><br /></p><p>Once the controller is ready to add your device, press the Manual/Program button on the smart plug 3 times quickly. The blue LED will blink quickly.</p><p> Auto-add mode: LED will blink within 30 seconds after first plugged in.</p> <br /> <h2>Exclusion Information</h2><p><b>Removing Device To Z-Wave Network:</b></p><p>Once the controller is ready to remove your device, press the Manual/Program button on the smart plug 3 times quickly. The blue LED will blink quickly.</p><p>Auto-add mode: LED will blink within 30 seconds after first plugged in.</p> <br /> <h2>Wakeup Information</h2><p>N/A</p>
]]></description>
<category>Battery</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_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="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_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="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">NIE Technology</property>
<property name="modelId">MP21ZP</property>
<property name="manufacturerId">0312</property>
<property name="manufacturerRef">FF00:FF0E</property>
<property name="dbReference">1417</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_00000001" type="integer" groupName="configuration"
min="0" max="3">
<label>1: LED Indicator</label>
<description><![CDATA[
LED Indicator Setup<br /> <h1>Overview</h1><p>This parameter can access you to choose the led indicator to be on when the plug(light) is on/off, or LED indicator remains on/off all times<br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">LED is On when the switch is ON and LED is Off when the switch is OFF</option>
<option value="1">LED is Off when switch is On and LED is ON when the switch is OFF</option>
<option value="2">LED is always Off</option>
<option value="3">LED is always On</option>
</options>
</parameter>
<parameter name="config_2_4" type="integer" groupName="configuration">
<label>2: Auto Turn-Off Timer</label>
<description><![CDATA[
Auto Turn-Off Timer Setup<br /> <h1>Overview</h1><p>This parameter can access you to set a timer to make the switch turn off automatically after the switch turned on<br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">Disable</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_3_4_00000001" type="integer" groupName="configuration">
<label>3: Auto Turn-On Timer</label>
<description><![CDATA[
Auto Turn-On Timer Setup<br /> <h1>Overview</h1><p>This parameter can access you to set a timer to make the switch turn on automatically after the switch turned off.</p>
]]></description>
<default>0</default>
<options>
<option value="0">Disable</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_4_1_00000001" type="integer" groupName="configuration"
min="0" max="2">
<label>4: Restores state after power failure</label>
<description><![CDATA[
Restores state after power failure Setup<br /> <h1>Overview</h1><p>This parameter can access you to set the switch to be on/off after power failure.</p>
]]></description>
<default>0</default>
<options>
<option value="0">State before power failure</option>
<option value="1">The switch is off regardless of the state prior to power failure</option>
<option value="2">The switch is on regardless of the state prior to power failure</option>
</options>
</parameter>
<parameter name="config_5_1_00000001" type="integer" groupName="configuration"
min="1" max="5">
<label>5: Power Wattage(W) Report</label>
<description><![CDATA[
Power Wattage(W) Report Setup<br /> <h1>Overview</h1><p>This parameter determines the minimum change in power wattage(W) that will result in sending new power report to the main controller.</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_6_4_00000001" type="integer" groupName="configuration"
min="1" max="65535">
<label>6: Time Report</label>
<description><![CDATA[
Time Report Setup<br /> <h1>Overview</h1><p>Electricity (A) Report Frequency (Timer)<br /></p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_7_1_00000001" type="integer" groupName="configuration"
min="1" max="10">
<label>7: Current(A) Report</label>
<description><![CDATA[
Current(A) Report Setup<br /> <h1>Overview</h1><p>This parameter determines the minimum change in Current(A) that will result in sending new power report to the main controller</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_8_1_00000001" type="integer" groupName="configuration"
min="1" max="10">
<label>8: Energy(KWH) Report</label>
<description><![CDATA[
Energy(KWH) Report Setup<br /> <h1>Overview</h1><p>This parameter determines the minimum change in consumed energy that will result in sending new energy report to the main controller</p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_9_4_00000001" type="integer" groupName="configuration"
min="1" max="65535">
<label>9: Count Down Configuration</label>
<description><![CDATA[
Endpoint1 Count Down Configuration (Turn off the output by time）<br /> <h1>Overview</h1><p>Endpoint1 Count Down Configuration (Turn off the output by time）<br /></p>
]]></description>
<default>60</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_10_1_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>10: Auto Turn-ON Timer</label>
<description><![CDATA[
Endpoint1 Enable Auto Turn-ON Timer<br /> <h1>Overview</h1><p>Endpoint1 Enable Auto Turn-ON Timer<br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">Auto Turn-ON Timer Disabled (default);</option>
<option value="1">Auto Turn-ON Timer Enabled</option>
</options>
</parameter>
<parameter name="config_11_4_00000001" type="integer" groupName="configuration"
min="1" max="65535">
<label>11: Count Down Configuration</label>
<description><![CDATA[
Endpoint1 Count Down Configuration(Turn on the output by time）<br /> <h1>Overview</h1><p>Endpoint1 Count Down Configuration(Turn on the output by time）<br /></p>
]]></description>
<default>60</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_12_1_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>12: E2 Auto Turn-OFF Timer</label>
<description><![CDATA[
Endpoint2 Enable Auto Turn-OFF Timer<br /> <h1>Overview</h1><p>Endpoint2 Enable Auto Turn-OFF Timer<br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">Auto Turn-OFF Timer Disabled (default)</option>
<option value="1">Auto Turn-OFF Timer Enabled</option>
</options>
</parameter>
<parameter name="config_13_4_00000001" type="integer" groupName="configuration"
min="1" max="65535">
<label>13: E2 Count Down Configuration</label>
<description><![CDATA[
Endpoint2 Count Down Configuration(Turn off the output by time）<br /> <h1>Overview</h1><p>Endpoint2 Count Down Configuration(Turn off the output by time）<br /></p>
]]></description>
<default>60</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_14_1_00000001" type="integer" groupName="configuration">
<label>14: E2 Auto Turn-ON Timer</label>
<description><![CDATA[
Endpoint2 Enable Auto Turn-ON Timer<br /> <h1>Overview</h1><p>Endpoint2 Enable Auto Turn-ON Timer<br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">Auto Turn-ON Timer Disabled (default)</option>
<option value="1">Auto Turn-ON Timer Enabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_15_4" type="integer" groupName="configuration"
min="1" max="65535">
<label>15: E2 Count Down Configuration</label>
<description><![CDATA[
Endpoint2 Count Down Configuration(Turn on the output by time）<br /> <h1>Overview</h1><p>Endpoint2 Count Down Configuration(Turn on the output by time）<br /></p>
]]></description>
<default>60</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_16_1_00000001" type="integer" groupName="configuration"
min="0" max="1">
<label>16: Manual Control</label>
<description><![CDATA[
Enable/Disable Manual Control<br /> <h1>Overview</h1><p>Enable/Disable Manual Control<br /></p>
]]></description>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_1_00000001" type="integer" groupName="configuration"
min="0" max="3">
<label>17: Status LED Configuration</label>
<description><![CDATA[
Status LED Configuration<br /> <h1>Overview</h1><p>Status LED Configuration<br /></p>
]]></description>
<default>1</default>
<options>
<option value="0">LED indicator will display power consumption whenever the device is pl</option>
<option value="1">LED indicator will display power consumption whenever the device is ON</option>
<option value="2">LED indicator will display the level of power consumption for 5 second</option>
<option value="3">Always OFF</option>
</options>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Lifeline</label>
<description><![CDATA[
Association group 1<br /> <h1>Overview</h1><p>Association group_1 is default to associate with the primary controller (Gateway/Hub/Controller) for MP21ZP Status change report,</p><p>1. MP21ZP will trigger AUTO report function if the Switch status had been changed.</p>
]]></description>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Basic set From Endpoint1</label>
<description><![CDATA[
Send Basic Set ON / Off<br /> <h1>Overview</h1><p>When the output of the MP21ZP Enpoint1 socket is changed, On (0xFF) or Off (0x00)or Overload, The MP21ZP will automatically send out a related basic set command. On (0xFF) or Off (0x00) to its associated group.</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>

57
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/shenzhen/naspd07z_0_0.xml
View File

@ -75,7 +75,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="1">
<label>1: Led Indicator Enable</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter is configured the Led light on disable or enable. '1' - Enable Led Blink when device detects a motion event. '0' - Disable Led blink. This configuration is not affect inclusion, exclusion and reset.</p>
<br /> <h1>Overview</h1><p>This parameter is configured the Led light on disable or enable. '1' - Enable Led Blink when device detects a motion event. '0' - Disable Led blink. This configuration is not affect inclusion, exclusion and reset. Default: Enable<br /></p>
]]></description>
<default>1</default>
<options>
@ -88,7 +88,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="1">
<label>2: Motion Enable</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter is configured the motion detected if enable or not. '0' - Motion detected disable. '1' - Motion detected enable.</p>
<br /> <h1>Overview</h1><p>This parameter is configured the motion detected if enable or not. '0' - Motion detected disable. '1' - Motion detected enable. Default: Enable<br /></p>
]]></description>
<default>1</default>
<options>
@ -101,7 +101,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="1">
<label>3: Motion Alarm Once Enable</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This Parameter is configured the motion detected event report one time before motion event cleared. '0' - Motion event alarm will be reported when motion event is detected every time. '1' - Motion event alarm report only once before motion event cleared.</p>
<br /> <h1>Overview</h1><p>This Parameter is configured the motion detected event report one time before motion event cleared. '0' - Motion event alarm will be reported when motion event is detected every time. '1' - Motion event alarm report only once before motion event cleared. Default: Enable<br /></p>
]]></description>
<default>1</default>
<options>
@ -114,7 +114,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="1">
<label>4: Luminance Associated Enable</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>'1' - Enable current light intensity to associate the motion event, if there has a motion event detected and the current light intensity is less than the settings in Configuraton No. 16, the device will send a BASIC_SET to nodes associated in Group 2. And if the current light intensity is larger then the setting in Configuration No. 16, the device will not send BASIC_SET to nodes associated in Group 2. '0' - Light intensity is not associated with motion event. <br /></p>
<br /> <h1>Overview</h1><p>'1' - Enable current light intensity to associate the motion event, if there has a motion event detected and the current light intensity is less than the settings in Configuraton No. 16, the device will send a BASIC_SET to nodes associated in Group 2. And if the current light intensity is larger then the setting in Configuration No. 16, the device will not send BASIC_SET to nodes associated in Group 2. '0' - Light intensity is not associated with motion event. Default: Disable<br /></p>
]]></description>
<default>0</default>
<options>
@ -127,9 +127,9 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="15">
<label>5: Motion Sensitivity</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter is configured the sensitivity that motion detect. This value is larger, the sensitivity is lower, and the distance for motion detecting is closer. Available settings: 0 ... 15<br /></p>
<br /> <h1>Overview</h1><p>This parameter is configured the sensitivity that motion detect. This value is larger, the sensitivity is lower, and the distance for motion detecting is closer. Available settings: 0 ... 15. Default: 1<br /></p>
]]></description>
<default>2</default>
<default>1</default>
<limitToOptions>false</limitToOptions>
</parameter>
@ -137,7 +137,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="-120" max="120">
<label>6: Temperature Offset Value</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>The current measuring temperature value can be add and minus a value by this setting. Temperature Offset Value = [Value] x 0.1 Degree Celsius / Fahrenheit (US). Available settings: -120 ... 120<br /></p>
<br /> <h1>Overview</h1><p>The current measuring temperature value can be add and minus a value by this setting. Temperature Offset Value = [Value] x 0.1 Degree Celsius / Fahrenheit (US). Available settings: -120 ... 120. Default: 0<br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
@ -147,7 +147,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="-120" max="120">
<label>7: Humidity Offset Value</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>The current measuring humidity value can be add and minus a value by this setting. Humidity Offset Value = [Value] x 0.1 RH%. Available settings: -120 ... 120 <br /></p>
<br /> <h1>Overview</h1><p>The current measuring humidity value can be add and minus a value by this setting. Humidity Offset Value = [Value] x 0.1 RH%. Available settings: -120 ... 120. Default: 0 <br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
@ -157,7 +157,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="120">
<label>8: Temperature D-Value Setting</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This configuration sets the changed value of the temperature. When the difference from the last report exceeds this setting value, the device will report current temperature value to Z-Wave Hubs. The D-Value = [Value] x 0.1 Degree Celsius / Fahrenheit (US). Available settings: 0 ... 120<br /></p>
<br /> <h1>Overview</h1><p>This configuration sets the changed value of the temperature. When the difference from the last report exceeds this setting value, the device will report current temperature value to Z-Wave Hubs. The D-Value = [Value] x 0.1 Degree Celsius / Fahrenheit (US). Available settings: 0 ... 120. Default: 10<br /></p>
]]></description>
<default>10</default>
<limitToOptions>false</limitToOptions>
@ -167,7 +167,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="120">
<label>9: Humidity D-Value Setting</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This configuration sets the changed value of the humidity. When the difference from the last report exceeds this setting value, the device will report current humidity value to Z-Wave Hubs. The D-Value = [Value] x 0.1 RH%. Available settings: 0 ... 120<br /></p>
<br /> <h1>Overview</h1><p>This configuration sets the changed value of the humidity. When the difference from the last report exceeds this setting value, the device will report current humidity value to Z-Wave Hubs. The D-Value = [Value] x 0.1 RH%. Available settings: 0 ... 120. Default: 20<br /></p>
]]></description>
<default>20</default>
<limitToOptions>false</limitToOptions>
@ -177,7 +177,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="120">
<label>10: Luminance D-Value Setting</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This configuration sets the changed value of the luminance. When the difference from the last report exceeds this setting value, the device will report current luminance value to Z-Wave Hubs. Unit: Lux. Available settings: 0 ... 120<br /></p>
<br /> <h1>Overview</h1><p>This configuration sets the changed value of the luminance. When the difference from the last report exceeds this setting value, the device will report current luminance value to Z-Wave Hubs. Unit: Lux. Available settings: 0 ... 120. Default: 50<br /></p>
]]></description>
<default>50</default>
<limitToOptions>false</limitToOptions>
@ -187,7 +187,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="100">
<label>11: Basic Set Level</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter is configured the value that BASIC_SET for nodes that associated in Group 2. '100' - BASIC_SET = 0xFF (ON). '0' - BASIC_SET = 0x00 (OFF). Available settings: 0 ... 100<br /></p>
<br /> <h1>Overview</h1><p>This parameter is configured the value that BASIC_SET for nodes that associated in Group 2. '100' - BASIC_SET = 0xFF (ON). '0' - BASIC_SET = 0x00 (OFF). Available settings: 0 ... 100. Default: 100<br /></p>
]]></description>
<default>100</default>
<limitToOptions>false</limitToOptions>
@ -197,7 +197,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="30000">
<label>12: Basic Set Off Delay Time</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter is configured the time delay for device sending BASIC_SET = 0x00 to nodes that associated in Group 2 when device detects a motion event. [0] - Not Send BASIC_SET = 0x00 Command. [1-30000] - Time delay count. Unit: Second. Available settings: 0 ... 30000<br /></p>
<br /> <h1>Overview</h1><p>This parameter is configured the time delay for device sending BASIC_SET = 0x00 to nodes that associated in Group 2 when device detects a motion event. [0] - Not Send BASIC_SET = 0x00 Command. [1-30000] - Time delay count. Unit: Second. Available settings: 0 ... 30000. Default: 30<br /></p>
]]></description>
<default>30</default>
<limitToOptions>false</limitToOptions>
@ -215,38 +215,41 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
<parameter name="config_14_2" type="integer" groupName="configuration"
min="0" max="65535">
<label>14: ??? Unknown</label>
<label>14: ??? Unknown (Luminance Threshold for Associated - Parameter #16?)</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p><br /></p>
<br /> <h1>Overview</h1><p>Default: 50<br /></p>
]]></description>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_15_2" type="integer" groupName="configuration"
min="0" max="65535">
<label>15: ??? Unknown</label>
<default>0</default>
min="0" max="30000">
<label>15: Sensor Measuring Interval</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter is configured the time interval for light sensor, temperature and humidity sensor measuring. This value is larger, the battery life is longer. And the sensors values changed are not obvious. 0 - All sensors are disabled. Unit: Second. Available settings: 0 - 30000. Default: 180 (on batteries) or 10 (on USB)<br /></p>
]]></description>
<default>180</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_16_2" type="integer" groupName="configuration"
min="0" max="1000">
<label>16: Luminance Threshold for Associated</label>
<label>16: ??? Luminance Threshold for Associated (or Parameter #14?)</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter is configured the light intensity threshold. When Ambient light intensity is less than this setting, device will consider the current environment is insufficient light. If "Configuration No. 3" is set '1' and a motion event is detected, the device will send a BASIC_SET to the nodes which associated in Group 2. Unit: 1 Lux. Available settings: 0 - 1000 </p>
<br /> <h1>Overview</h1><p>This parameter is configured the light intensity threshold. When Ambient light intensity is less than this setting, device will consider the current environment is insufficient light. If "Configuration No. 3" is set '1' and a motion event is detected, the device will send a BASIC_SET to the nodes which associated in Group 2. Unit: 1 Lux. Available settings: 0 - 1000. Default: 50 </p>
]]></description>
<default>50</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_2" type="integer" groupName="configuration"
min="0" max="30000">
<label>17: Sensor Measuring Interval</label>
min="0" max="65535">
<label>17: ??? Unknown</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter is configured the time interval for light sensor, temperature and humidity sensor measuring. This value is larger, the battery life is longer. And the sensors values changed are not obvious. 0 - All sensors are disabled. Unit: Second. Available settings: 0 - 30000, default value: 180 (on batteries) or 10 (on USB)<br /></p>
<br /> <h1>Overview</h1><p>Default: 180<br /></p>
]]></description>
<default>180</default>
<default>0</default>
<limitToOptions>false</limitToOptions>
</parameter>
@ -254,7 +257,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="1" max="32767">
<label>18: Light Intensity Offset Calibration</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter defines the calibrated scale for ambient light intensity. Because the method and position that the sensor mounted and the cover of sensor will bring measurement error, user can get more real light intensity by this parameter setting. User should run the steps blows for calibrating.</p><p>1. Set this parameter value to default (Assumes the sensor has been added in a Z-Wave Network).</p><p>2. Place a digital luxmeter close to sensor and keep the same direction, monitor the light intensity values (Vm) which report to controller and record it. The same time user should record the Value (Vs) of luxmeter.</p><p>3. The scale calibration formula: k = Vm / Vs.</p><p>4. The value of k is then multiplied by 1000 and rounded to the nearest whole number.</p><p>5. Set the value getting in 5) to this parameter, calibrate finished. <br /></p><p>For example, Vm = 300, Vs = 2000 [sic], then k = 300 / 2600 = 0.11538</p><p>k = 0.11538 * 1000 = 115,38 ~ 115</p><p>The parameter should be set to 115.</p><p>Available settings: 1 ... 32767<br /></p>
<br /> <h1>Overview</h1><p>This parameter defines the calibrated scale for ambient light intensity. Because the method and position that the sensor mounted and the cover of sensor will bring measurement error, user can get more real light intensity by this parameter setting. User should run the steps blows for calibrating.</p><p>1. Set this parameter value to default (Assumes the sensor has been added in a Z-Wave Network).</p><p>2. Place a digital luxmeter close to sensor and keep the same direction, monitor the light intensity values (Vm) which report to controller and record it. The same time user should record the Value (Vs) of luxmeter.</p><p>3. The scale calibration formula: k = Vm / Vs.</p><p>4. The value of k is then multiplied by 1000 and rounded to the nearest whole number.</p><p>5. Set the value getting in 5) to this parameter, calibrate finished. <br /></p><p>For example, Vm = 300, Vs = 2000 [sic], then k = 300 / 2600 = 0.11538</p><p>k = 0.11538 * 1000 = 115,38 ~ 115</p><p>The parameter should be set to 115.</p><p>Available settings: 1 ... 32767. Default: 5320<br /></p>
]]></description>
<default>5320</default>
<limitToOptions>false</limitToOptions>
@ -264,7 +267,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="0" max="1">
<label>98: ??? Binary Sensor Report Enable</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>'1' - Enable sensor binary report when device detects a motion event. '0' - Disable sensor binary report when device detects a motion event.<br /></p>
<br /> <h1>Overview</h1><p>'1' - Enable sensor binary report when device detects a motion event. '0' - Disable sensor binary report when device detects a motion event. Default: Disable<br /></p>
]]></description>
<default>0</default>
<options>
@ -277,7 +280,7 @@ NEO Coolcam PIR 5 in 1<br /> <h1>Overview</h1><p>5 in 1 sensor: motion, temperat
min="1" max="30000">
<label>99: ??? Motion Clear Time</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p>This parameter is configured the time to clear motion event after a motion event detected. Time to motion clear, the device will send a clear event report to controller. Unit: Second. Available settings: 0 ... 30000 </p>
<br /> <h1>Overview</h1><p>This parameter is configured the time to clear motion event after a motion event detected. Time to motion clear, the device will send a clear event report to controller. Unit: Second. Available settings: 0 ... 30000. Default: 30 </p>
]]></description>
<default>30</default>
<limitToOptions>false</limitToOptions>

16
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/vision/zd2102plus_0_0.xml
View File

@ -26,6 +26,12 @@ Door Window Sensor<br /> <h1>Overview</h1><p>Wireless Door/ Window Sensor</p> <b
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=BURGLAR</property>
</properties>
</channel>
<channel id="alarm_battery" typeId="alarm_battery">
<label>Battery</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM</property>
</properties>
</channel>
<channel id="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
@ -58,15 +64,17 @@ Door Window Sensor<br /> <h1>Overview</h1><p>Wireless Door/ Window Sensor</p> <b
</parameter-group>
<!-- PARAMETER DEFINITIONS -->
<parameter name="config_1_1" type="integer" groupName="configuration">
<parameter name="config_1_1" type="integer" groupName="configuration"
min="0" max="255">
<label>1: External switch</label>
<description>Determines if the external switch can be used.</description>
<description><![CDATA[
Determines if the external switch can be used.<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">Disable</option>
<option value="0">Disable (default)</option>
<option value="255">Enable</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->

122
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/zooz/zen34_0_0.xml
View File

@ -1,122 +0,0 @@
<?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="zooz_zen34_00_000" listed="false">
<label>ZEN34 Remote switch</label>
<description><![CDATA[
Remote switch<br /> <h1>Overview</h1><p>* Control other Z-Wave devices and enable scenes with a click of a button</p><p>* Classic paddle switch look and size + magnetic base</p><p>* Install in your electrical switch box or mount anywhere on a wall with just adhesive tape</p><p>* The latest 700 chip with S2 and SmartStart support</p><p>* Powered by batteries, no wires needed<br /></p> <br /> <h2>Inclusion Information</h2><p>Put the openHAB Z-Wave binding into inclusion mode and click the upper paddle 6 times quickly. The LED indicator will blink blue during the process and light up green once added successfully. It will light up red if failed.<br /></p> <br /> <h2>Exclusion Information</h2><p>Put the openHAB Z-Wave binding into exclusion mode and click the lower paddle 6 times quickly.<br /></p> <br /> <h2>Wakeup Information</h2><p>Click the upper paddle 7 times quickly. The LED indicator will stay siolid blue during wakeup and will turn off when the device turns the Z-Wave radio off again.<br /></p>
]]></description>
<category>RemoteControl</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<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="battery-level" typeId="system.battery-level">
<properties>
<property name="binding:*:PercentType">COMMAND_CLASS_BATTERY</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Zooz</property>
<property name="modelId">ZEN34</property>
<property name="manufacturerId">027A</property>
<property name="manufacturerRef">0004:F001</property>
<property name="dbReference">1310</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"
min="0" max="2">
<label>1: LED indication mode</label>
<default>1</default>
<options>
<option value="0">LED always OFF</option>
<option value="1">LED ON when button pressed</option>
<option value="2">LED always ON (color from #2)</option>
<option value="3">LED always ON (color from #3)</option>
</options>
</parameter>
<parameter name="config_2_1" type="integer" groupName="configuration"
min="0" max="6">
<label>2: Upper paddle indicator color</label>
<default>1</default>
<options>
<option value="0">White</option>
<option value="1">Blue</option>
<option value="2">Green</option>
<option value="3">Red</option>
<option value="4">Magenta</option>
<option value="5">Yellow</option>
<option value="6">Cyan</option>
</options>
</parameter>
<parameter name="config_3_1" type="integer" groupName="configuration"
min="0" max="6">
<label>3: Lower paddle indicator color</label>
<default>0</default>
<options>
<option value="0">White</option>
<option value="1">Blue</option>
<option value="2">Green</option>
<option value="3">Red</option>
<option value="4">Magenta</option>
<option value="5">Yellow</option>
<option value="6">Cyan</option>
</options>
</parameter>
<!-- ASSOCIATION DEFINITIONS -->
<parameter name="group_1" type="text" groupName="association">
<label>1: Lifeline</label>
</parameter>
<parameter name="group_2" type="text" groupName="association" multiple="true">
<label>2: Basic Set</label>
<multipleLimit>5</multipleLimit>
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: Switch Multilevel</label>
<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>

25
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/zooz/zen34v101_0_0.xml
View File

@ -8,7 +8,7 @@
<thing-type id="zooz_zen34v101_00_000" listed="false">
<label>zen34v1.01 Remote Switch</label>
<description><![CDATA[
Remote Switch<br /> <h1>Overview</h1><p>* Control other Z-Wave devices and enable scenes with a click of a button</p><p>* Classic paddle switch look and size + magnetic base</p><p>* Install in your electrical switch box or mount anywhere on a wall with just adhesive tape</p><p>* The latest 700 chip with S2 and SmartStart support</p><p>* Powered by batteries, no wires needed</p> <br /> <h2>Inclusion Information</h2><p>Put the openHAB Z-Wave binding into inclusion mode and click the upper paddle 6 times quickly. The LED indicator will blink blue during the process and light up green once added successfully. It will light up red if failed.<br /></p> <br /> <h2>Exclusion Information</h2><p>Put the openHAB Z-Wave binding into exclusion mode and click the lower paddle 6 times quickly.<br /></p> <br /> <h2>Wakeup Information</h2><p><br /></p>
Remote Switch<br /> <h1>Overview</h1><ul><li>Control other Z-Wave devices and enable scenes with a click of a button</li><li>Classic paddle switch look and size + magnetic base</li><li>Install in your electrical switch box or mount anywhere on a wall with just adhesive tape</li><li>The latest 700 chip with S2 and SmartStart support</li><li>Powered by batteries, no wires needed</li></ul> <br /> <h2>Inclusion Information</h2><p>Put the openHAB Z-Wave binding into inclusion mode and click the upper paddle 6 times quickly. The LED indicator will blink blue during the process and light up green once added successfully. It will light up red if failed.<br /></p> <br /> <h2>Exclusion Information</h2><p>Put the openHAB Z-Wave binding into exclusion mode and click the lower paddle 6 times quickly.<br /></p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>RemoteControl</category>
@ -55,10 +55,13 @@ Remote Switch<br /> <h1>Overview</h1><p>* Control other Z-Wave devices and enabl
<parameter name="config_1_1" type="integer" groupName="configuration"
min="0" max="2">
<label>1: LED indication mode</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<options>
<option value="0">LED always OFF</option>
<option value="1">LED ON when button pressed</option>
<option value="1">LED ON when button pressed (default)</option>
<option value="2">LED always ON (color from #2)</option>
<option value="3">LED always ON (color from #3)</option>
</options>
@ -67,10 +70,13 @@ Remote Switch<br /> <h1>Overview</h1><p>* Control other Z-Wave devices and enabl
<parameter name="config_2_1" type="integer" groupName="configuration"
min="0" max="6">
<label>2: Upper paddle indicator color</label>
<description><![CDATA[
<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>1</default>
<options>
<option value="0">White</option>
<option value="1">Blue</option>
<option value="1">Blue (default)</option>
<option value="2">Green</option>
<option value="3">Red</option>
<option value="4">Magenta</option>
@ -82,9 +88,12 @@ Remote Switch<br /> <h1>Overview</h1><p>* Control other Z-Wave devices and enabl
<parameter name="config_3_1" type="integer" groupName="configuration"
min="0" max="6">
<label>3: Lower paddle indicator color</label>
<default>1</default>
<description><![CDATA[
<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<default>0</default>
<options>
<option value="0">White</option>
<option value="0">White (default)</option>
<option value="1">Blue</option>
<option value="2">Green</option>
<option value="3">Red</option>
@ -106,8 +115,10 @@ Remote Switch<br /> <h1>Overview</h1><p>* Control other Z-Wave devices and enabl
</parameter>
<parameter name="group_3" type="text" groupName="association" multiple="true">
<label>3: dimming</label>
<description>Paddle held/released for dimming</description>
<label>3: Dimming</label>
<description><![CDATA[
Paddle held/released for dimming<br /> <h1>Overview</h1><p><br /></p>
]]></description>
<multipleLimit>5</multipleLimit>
</parameter>

4
installation/openhabian.md
View File

@ -106,7 +106,7 @@ There's no genuine reason why this wouldn't work. The openHABian image is really
Let's put this first: our current recommendation is to get a RPi 4 with 2 or 4 GB of RAM, a 3A power supply and a 16 GB SD card.
Because of the higher limit of write cycles, an SD card designed for Dashcams is preferable.
Most manufacturers name them with a postfix like "Endurance" (e.g. "SanDisk MAX ENDURANCE" or "Kingston High Endurance").
Most manufacturers name them with a postfix like "Endurance" (e.g. "SanDisk MAX ENDURANCE" or "Kingston High Endurance").
Also get another 32 GB or larger SD card and a USB card reader to make use of the ["auto backup" feature](openhabian.md#auto-backup).
### Hardware support
@ -140,7 +140,7 @@ These are what we develop and test openHABian against.
We provide code that is reported "as-is" to run on Ubuntu but we do **not support Ubuntu** so please don't open issues for this (PRs then again are welcome).
Several optional components though, such as WireGuard or Homegear, are known to expose problems on Ubuntu.
We expect you to use the current stable distribution: 'buster' for Raspberry Pi OS (ARM) and Debian (x86).
We expect you to use the current stable distribution: 'bullseye' for Raspberry Pi OS (ARM) and Debian (x86).
To install openHABian on anything older or newer may work or not.
If you encounter issues, you may need to upgrade first or to live with the consequences of running an OS on the edge of software development.