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

pull/1698/head
openHAB Build Server 2021-12-05 03:38:33 +00:00
parent eadf5015fe
commit 31998f1a41
21 changed files with 911 additions and 64 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

1
_addons_bindings/ahawastecollection/readme.md
View File

@ -5,6 +5,7 @@ title: aha Waste Collection - Bindings
type: binding
description: "This binding provides information about the upcoming waste collection dates for places, that are served by aha, the waste collection company for the region of Hannover. The values are retrieved from the online aha waste collection schedule available at: [aha Abfuhrkalender](https://www.aha-region.de/abholtermine/abfuhrkalender)."
since: 3x
logo: images/addons/ahawastecollection.png
install: manual
---

10
_addons_bindings/chromecast/readme.md
View File

@ -43,15 +43,21 @@ Configure a Callback URL when the Chromecast cannot connect using the Primary Ad
## Discovery
Chromecast devices are discovered on the network using UPnP.
Chromecast devices are discovered on the network using mDNS.
No authentication is required for accessing the devices on the network.
Auto-discovery is enabled by default.
To disable it, you can add the following line to `<openHAB-conf>/services/runtime.cfg`:
```
discovery.chromecast:background=false
```
## Thing Configuration
Chromecast devices can also be manually added.
The only configuration parameter is the `ipAddress`.
For an audio group also the port is necessary.
The autodiscovery process finds the port automatically.
The auto-discovery process finds the port automatically.
With manual thing configuration the parameter `port` must be determined manually.
Example for audio group:

49
_addons_bindings/miio/readme.md
View File

@ -1,7 +1,7 @@
---
id: miio
label: Xiaomi Mi IO
title: Xiaomi Mi IO - Bindings
label: Xiaomi Wifi devices (Mi IO)
title: Xiaomi Wifi devices (Mi IO) - Bindings
type: binding
description: "This binding is used to control Xiaomi products implementing the Mi IO protocol."
since: 3x
@ -13,10 +13,11 @@ install: auto
{% include base.html %}
# Xiaomi Mi IO Binding
# Xiaomi Wifi devices (Mi IO) Binding
This binding is used to control Xiaomi products implementing the Mi IO protocol.
This is a set of wifi devices from Xiaomi that are part of the Mi Ecosystem which is branded as MiJia.
This protocol is used for most of Xiaomi Mi Ecosystem wifi devices which is branded as MiJia.
If your Xiaomi wifi device is controlled by the mihome app, most likely it communicates using the Mi IO protocol and can communicate with openHAB using this binding.
![MIIO logo](doc/miio.png)
@ -27,9 +28,9 @@ The following things types are available:
| ThingType | Description |
|------------------|--------------------------------------------------------------------------------------------------------------------------|
| miio:generic | Generic type for discovered devices. Once the token is available and the device model is determined, this ThingType will automatically change to the appropriate ThingType |
| miio:vacuum | For Xiaomi Robot Vacuum products |
| miio:basic | For several basic devices like yeelights, airpurifiers. Channels and commands are determined by database configuration |
| miio:unsupported | For experimenting with other devices which use the Mi IO protocol |
| miio:vacuum | For Xiaomi/RoboRock Robot Vacuum products |
| miio:basic | For most other devices like yeelights, airpurifiers. Channels and commands are determined by database configuration |
| miio:unsupported | For experimenting with other devices which use the Mi IO protocol or to build experimental support |
# Discovery
@ -221,6 +222,7 @@ Currently the miio binding supports more than 300 different models.
| Mi Smart Antibacterial Humidifier | miio:basic | [deerma.humidifier.jsq](#deerma-humidifier-jsq) | Yes | |
| Mi S Smart Humidifer | miio:basic | [deerma.humidifier.jsq1](#deerma-humidifier-jsq1) | Yes | |
| Mi Smart Antibacterial Humidifier | miio:basic | [deerma.humidifier.jsq5](#deerma-humidifier-jsq5) | Yes | |
| Mi Smart Humidifer S | miio:basic | [deerma.humidifier.jsqs](#deerma-humidifier-jsqs) | Yes | |
| Mi Smart Humidifier | miio:basic | [deerma.humidifier.mjjsq](#deerma-humidifier-mjjsq) | Yes | |
| Mi Fresh Air Ventilator A1-150 | miio:basic | [dmaker.airfresh.a1](#dmaker-airfresh-a1) | Yes | |
| Mi Fresh Air Ventilator | miio:basic | [dmaker.airfresh.t2017](#dmaker-airfresh-t2017) | Yes | |
@ -827,6 +829,21 @@ Note, not all the values need to be in the json file, e.g. a subset of the param
| water_shortage_fault | Switch | Custom - Water Shortage Fault | |
| the_tank_filed | Switch | Custom - The Tank Filed | |
### Mi Smart Humidifer S (<a name="deerma-humidifier-jsqs">deerma.humidifier.jsqs</a>) Channels
| Channel | Type | Description | Comment |
|----------------------|----------------------|------------------------------------------|------------|
| on | Switch | Humidifier - Switch Status | |
| fault | Number | Humidifier - Device Fault | Value mapping `["0"="No Faults","1"="Insufficient Water","2"="Water Separation"]` |
| fan_level | Number | Humidifier - Fan Level | Value mapping `["1"="Level1","2"="Level2","3"="Level3","4"="Humidity"]` |
| target_humidity | Number:Dimensionless | Humidifier - Target Humidity | |
| relative_humidity | Number:Dimensionless | Environment - Relative Humidity | |
| temperature | Number:Temperature | Environment - Temperature | |
| alarm | Switch | Alarm - Alarm | |
| on1 | Switch | Indicator Light - Switch Status | |
| water_shortage_fault | Switch | Custom - Water Shortage Fault | |
| the_tank_filed | Switch | Custom - The Tank Filed | |
### Mi Smart Humidifier (<a name="deerma-humidifier-mjjsq">deerma.humidifier.mjjsq</a>) Channels
| Channel | Type | Description | Comment |
@ -5659,6 +5676,24 @@ Switch water_shortage_fault "Custom - Water Shortage Fault" (G_humidifier) {chan
Switch the_tank_filed "Custom - The Tank Filed" (G_humidifier) {channel="miio:basic:humidifier:the_tank_filed"}
```
### Mi Smart Humidifer S (deerma.humidifier.jsqs) item file lines
note: Autogenerated example. Replace the id (humidifier) in the channel with your own. Replace `basic` with `generic` in the thing UID depending on how your thing was discovered.
```
Group G_humidifier "Mi Smart Humidifer S" <status>
Switch on "Humidifier - Switch Status" (G_humidifier) {channel="miio:basic:humidifier:on"}
Number fault "Humidifier - Device Fault" (G_humidifier) {channel="miio:basic:humidifier:fault"}
Number fan_level "Humidifier - Fan Level" (G_humidifier) {channel="miio:basic:humidifier:fan_level"}
Number:Dimensionless target_humidity "Humidifier - Target Humidity" (G_humidifier) {channel="miio:basic:humidifier:target_humidity"}
Number:Dimensionless relative_humidity "Environment - Relative Humidity" (G_humidifier) {channel="miio:basic:humidifier:relative_humidity"}
Number:Temperature temperature "Environment - Temperature" (G_humidifier) {channel="miio:basic:humidifier:temperature"}
Switch alarm "Alarm - Alarm" (G_humidifier) {channel="miio:basic:humidifier:alarm"}
Switch on1 "Indicator Light - Switch Status" (G_humidifier) {channel="miio:basic:humidifier:on1"}
Switch water_shortage_fault "Custom - Water Shortage Fault" (G_humidifier) {channel="miio:basic:humidifier:water_shortage_fault"}
Switch the_tank_filed "Custom - The Tank Filed" (G_humidifier) {channel="miio:basic:humidifier:the_tank_filed"}
```
### Mi Smart Humidifier (deerma.humidifier.mjjsq) item file lines
note: Autogenerated example. Replace the id (humidifier) in the channel with your own. Replace `basic` with `generic` in the thing UID depending on how your thing was discovered.

9
_addons_bindings/sagercaster/readme.md
View File

@ -20,7 +20,8 @@ The Sager Weathercaster is a scientific instrument for accurate prediction of th
* To operate, this binding will need to use channel values provided by other means (e.g. Weather Binding, Netatmo, a 1-Wire personal weather station...)
* This binding buffers readings for some hours before producing weather forecasts(wind direction and sea level pressure). SagerWeatherCaster needs an observation period of minimum 6 hours.
* This binding buffers readings for some hours before producing weather forecasts(wind direction and sea level pressure).
SagerWeatherCaster needs an observation period of minimum 6 hours.
For these reasons, this binding is not a binding in the usual sense.
@ -38,9 +39,11 @@ The binding itself does not require any configuration.
| Name | Type | Description |
|--------------------|----------|--------------------------------------------------------------------------|
| location | Location | Latitude and longitude of the desired weather forecast. |
| location (*) | Location | Latitude and longitude of the desired weather forecast. |
| observation-period | int | Minimum delay (in hours) before producing forecasts. Defaulted to 6. |
(*) Only latitude is used by the algorithm.
## Channels
The binding will use some input channels, that can be configured directly with profiles (sample below).
@ -55,6 +58,8 @@ The binding will use some input channels, that can be configured directly with p
| wind-speed-beaufort | input |Number | Wind speed expressed using the Beaufort scale |
| pressure | input |Number:Pressure | Sea level pressure |
| wind-angle | input |Number:Angle | Wind direction |
| temperature | input |Number:Temperature | Outside temperature |
| timestamp | output |DateTime | Timestamp of the last forecast update |
| forecast | output |String | Description of the weather forecast |
| velocity | output |String | Description of the expected wind evolution |
| velocity-beaufort | output |Number | Expected wind evolution using the Beaufort scale |

101
_addons_bindings/sncf/readme.md Normal file
View File

@ -0,0 +1,101 @@
---
id: sncf
label: SNCF
title: SNCF - Bindings
type: binding
description: "The SNCF binding provides real-time data(*) for each train, bus, tramway... station in France."
since: 3x
install: manual
---
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
{% include base.html %}
# SNCF Binding
The SNCF binding provides real-time data(*) for each train, bus, tramway... station in France.
This is based on live API provided by DIGITALSNCF.
Get your API key on [DIGITALSNCF web site](https://www.digital.sncf.com/startup/api/token-developpeur)
Note : SNCF Api is based on the open [API Navitia](https://doc.navitia.io/#getting-started).
This binding uses a very small subset of it, restricted to its primary purpose.
(*) According to DIGITALSNCF Transilien may only be available for schedule, maybe not real-time.
## Supported Things
Bridge: The binding supports a bridge to connect to the [DIGITALSNCF service](https://www.digital.sncf.com/startup/api/token developpeur).
A bridge uses the thing ID "api".
Station: Represents a given bus, train station.
Of course, you can add as many stations as needed.
## Discovery
This binding takes care of auto discovery. This method is strongly recommended as it is the only way to get proper station ID depending upon transportation type.
To enable auto-discovery, your location system setting must be defined.
Once done, at first launch, discovery will search every station in a radius of 2000 m around the system, extending it by step of 500 m until it finds a first set of results.
Every following manual successive launch will extend this radius by 500 m, increasing the number of stations discovered.
## Binding Configuration
The binding has no configuration options, all configuration is done at Thing level.
## Bridge Configuration
The bridge configuration only holds the api key :
| Parameter | Description |
|-----------|----------------------------------------------------------------|
| apiID | API ID provided by the DIGITALSNCF service. Mandatory. |
## Thing Configuration
The 'Station' thing has only one configuration parameter:
| Parameter | Description |
|-------------|--------------------------------------------------------------|
| stopPointId | Identifier of the station in the DIGITALSNCF network. |
The thing will auto-update depending on the timestamp of the earliest event detected to trigger (arrival or departure).
## Channels
The Station thing holds two groups of channels (arrivals and departures) containing these channels:
| Channel ID | Item Type | Description |
|-----------------------|-----------|--------------------------------------------------|
| direction | String | The direction of the route |
| lineName | String | Commercial name of the line |
| name | String | Name of the line |
| network | String | Name of the network ruling the line |
| timestamp | DateTime | Timestamp of the event (departure, arrival) |
## Full Example
sncf.things:
```
Bridge sncf:api:8901d44a68 "Bridge" [apiID="xxx-yyy-zzz"] {
station MyHouse "Krakow"[stopPointId="stop_point:SNCF:87561951:Bus"]
}
```
sncf.items:
```
String Arrival_Direction { channel="sncf:station:8901d44a68:87381475_RapidTransit:arrivals#direction" }
String Arrival_Line { channel="sncf:station:8901d44a68:87381475_RapidTransit:arrivals#lineName" }
DateTime Arrival_Time { channel="sncf:station:8901d44a68:87381475_RapidTransit:arrivals#timestamp" }
String Departure_Direction { channel="sncf:station:8901d44a68:87381475_RapidTransit:departures#direction" }
String Departure_Line { channel="sncf:station:8901d44a68:87381475_RapidTransit:departures#lineName" }
DateTime Departure_Time { channel="sncf:station:8901d44a68:87381475_RapidTransit:departures#timestamp" }
```

100
_addons_bindings/venstarthermostat/readme.md
View File

@ -55,21 +55,64 @@ After adding the Inbox item, enter the user name and password from the physical
### Channels
| Channel | Type | Description | Notes |
|--------------------|--------------------|------------------------------|--------------------------------------------------------|
| awayMode | String | Home or Away Mode | |
| awayModeRaw | Number | Away Mode Raw (Read Only) | 0 (Home) 1 (Away) |
| systemMode | String | System Mode | |
| systemModeRaw | Number | System Mode Raw (Read Only) | 0 (Off) 1 (Heat) 2 (Cool) 3 (Auto) |
| systemState | String | System State (Read Only) | |
| systemStateRaw | Number | System State Raw (Read Only) | 0 (Idle) 1 (Heating) 2 (Cooling) 3 (Lockout) 4 (Error) |
| heatingSetpoint | Number:Temperature | Heating Set Point | |
| coolingSetpoint | Number:Temperature | Cooling Set Point | |
| temperature | Number:Temperature | Current Temperature | |
| outdoorTemperature | Number:Temperature | Outdoor Temperature | |
| humidity | Number | Humidity | |
| Channel | Type | Description | Notes |
|--------------------|--------------------|---------------------------------------|--------------------------------------------------------|
| awayMode | String | Home or Away Mode | |
| awayModeRaw | Number | Away Mode Raw (Read Only) | 0 (Home) 1 (Away) |
| systemMode | String | System Mode | |
| systemModeRaw | Number | System Mode Raw (Read Only) | 0 (Off) 1 (Heat) 2 (Cool) 3 (Auto) |
| systemState | String | System State (Read Only) | |
| systemStateRaw | Number | System State Raw (Read Only) | 0 (Idle) 1 (Heating) 2 (Cooling) 3 (Lockout) 4 (Error) |
| heatingSetpoint | Number:Temperature | Heating Set Point | |
| coolingSetpoint | Number:Temperature | Cooling Set Point | |
| temperature | Number:Temperature | Current Temperature | |
| outdoorTemperature | Number:Temperature | Outdoor Temperature | |
| humidity | Number | Humidity | |
| fanMode | String | Fan Mode | |
| fanModeRaw | Number | Fan Mode Raw (Read Only) | 0 (Auto) 1 (On) |
| fanState | String | Fan State (Read Only) | |
| fanStateRaw | Number | Fan State Raw (Read Only) | 0 (Off) 1 (On) |
| scheduleMode | String | Current Schedule Mode | |
| scheduleModeRaw | Number | Current Schedule mode Raw (Read Only) | 0(Disabled) 1(Enabled) |
| schedulePart | String | Current Schedule Part | |
| schedulePartRaw | Number | Schedule Part Raw (Read Only) | 0(Morning) 1(Day) 2(Evening) 3 (Night) 255 (Inactive) |
### Runtime data
The Venstar thermostat provides data about how many minutes the system has been running in each of the different modes (heat1, heat2, cool1, cool2, aux1, aux2, free cool) every day for the last 7 days.
A time stamp is provided with each runtime data set which represents the end of each day.
The binding reads the runtime data and time stamps and provides them all as separate channels.
| Channel | Type | Description | Notes |
|------------------------|----------------------|----------------------------------------------|------------------------------------------------------------|
| timestampDay0 | DateTime | Time Stamp of last runtime update | This is always the current time today |
| timestampDay1 | DateTime | Time Stamp of 00:00, end of yesterday | This represents the end of 1 day ago |
| timestampDay2 | DateTime | Time Stamp of 00:00 end of 2 days ago | This represents the end of 2 days ago |
| timestampDay3 | DateTime | Time Stamp of 00:00, end of 3 days ago | This represents the end of 3 days ago |
| timestampDay4 | DateTime | Time Stamp of 00:00, end of 4 days ago | This represents the end of 4 days ago |
| timestampDay5 | DateTime | Time Stamp of 00:00, end of 5 days ago | This represents the end of 5 days ago |
| timestampDay6 | DateTime | Time Stamp of 00:00, end of 6 days ago | This represents the end of 6 days ago |
| heat1RuntimeDay0 | Number:Dimensionless | Runtime in heat1 mode (minutes) today | This is the runtime between the Day 1 and Day 0 timestamps |
| heat1RuntimeDay1 | Number:Dimensionless | Runtime in heat1 mode (minutes) yesterday | This is the runtime between the Day 2 and Day 1 timestamps |
| heat1RuntimeDay2 | Number:Dimensionless | Runtime in heat1 mode (minutes) 2 days ago | This is the runtime between the Day 3 and Day 2 timestamps |
| heat1RuntimeDay3 | Number:Dimensionless | Runtime in heat1 mode (minutes) 3 days ago | This is the runtime between the Day 4 and Day 3 timestamps |
| heat1RuntimeDay4 | Number:Dimensionless | Runtime in heat1 mode (minutes) 4 days ago | This is the runtime between the Day 5 and Day 4 timestamps |
| heat1RuntimeDay5 | Number:Dimensionless | Runtime in heat1 mode (minutes) 5 days ago | This is the runtime between the Day 6 and Day 5 timestamps |
| heat1RuntimeDay6 | Number:Dimensionless | Runtime in heat1 mode (minutes) 6 days ago | This is the runtime in the 24hrs up to the Day 6 timestamp |
| | | | |
| heat2RuntimeDay0..6 | Number:Dimensionless | Similar Runtimes in heat2 mode (minutes) | |
| | | | |
| cool1RuntimeDay0..6 | Number:Dimensionless | Similar Runtimes in cool1 mode (minutes) | |
| | | | |
| cool2RuntimeDay0..6 | Number:Dimensionless | Similar Runtimes in cool2 mode (minutes) | |
| | | | |
| aux1RuntimeDay0..6 | Number:Dimensionless | Similar Runtimes in aux1 mode (minutes) | |
| | | | |
| aux2RuntimeDay0..6 | Number:Dimensionless | Similar Runtimes in aux2 mode (minutes) | |
| | | | |
| freeCoolRuntimeDay0..6 | Number:Dimensionless | Similar Runtimes in free cool mode (minutes) | |
## Example
### thermostat.things
@ -85,10 +128,22 @@ Thing venstarthermostat:colorTouchThermostat:001122334455 "Venstar Thermostat (G
Number:Temperature Guest_HVAC_Temperature "Temperature [%d °F]" {channel="venstarthermostat:colorTouchThermostat:001122334455:temperature"}
Number:Temperature Guest_HVAC_HeatSetpoint "Heat Setpoint [%d °F]" {channel="venstarthermostat:colorTouchThermostat:001122334455:heatingSetpoint"}
Number:Temperature Guest_HVAC_CoolSetpoint "Cool Setpoint [%d °F]" {channel="venstarthermostat:colorTouchThermostat:001122334455:coolingSetpoint"}
Number Guest_HVAC_Mode "Mode [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:systemMode"}
String Guest_HVAC_Mode "System Mode [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:systemMode"}
Number Guest_HVAC_Humidity "Humidity [%d %%]" {channel="venstarthermostat:colorTouchThermostat:001122334455:humidity"}
Number Guest_HVAC_State "State [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:systemState"}
Number Guest_Away_Mode "Mode [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:awayMode"}
String Guest_HVAC_State "State [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:systemState"}
String Guest_Away_Mode "Away Mode [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:awayMode"}
String Guest_Fan_Mode "Fan Mode [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:fanMode"}
String Guest_Fan_State "Fan State [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:fanState"}
String Guest_Schedule_Mode "Schedule Mode [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:scheduleMode"}
String Guest_Schedule_Part "Schedule Part [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:schedulePart"}
DateTime Guest_timestampDay0 "Date/Time Last Update [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:timestampDay0"}
Number Guest_heat1RuntimeDay0 "Heat1 Day0 Run Time [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:heat1RuntimeDay0"}
Number Guest_heat2RuntimeDay0 "Heat2 Day 0 Run Time [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:heat2RuntimeDay0"}
Number Guest_cool1RuntimeDay0 "Cool1 Day 0 Run Time [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:cool1RuntimeDay0"}
Number Guest_cool2RuntimeDay0 "Cool2 Day 0 Run Time [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:cool2RuntimeDay0"}
Number Guest_aux1RuntimeDay0 "Aux1 Day 0 Run Time [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:aux1RuntimeDay0"}
Number Guest_aux2RuntimeDay0 "Aux2 Day 0 Run Time [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:aux2RuntimeDay0"}
Number Guest_freeCoolRuntimeDay0 "Free Cool Day 0 Run Time [%s]" {channel="venstarthermostat:colorTouchThermostat:001122334455:freeCoolRuntimeDay0"}
```
### thermostat.sitemap
@ -102,6 +157,19 @@ sitemap demo label="Venstar Color Thermostat Demo"
Switch item=Guest_HVAC_Mode mappings=[off=Off,heat=Heat,cool=Cool,auto=Auto]
Switch item=Guest_Away_Mode mappings=[home=Home,away=Away]
Text item=Guest_HVAC_State
Switch item=Guest_Fan_Mode mappings=[auto=Auto, on=On]
Text item=Guest_Fan_State
Switch item=Guest_Schedule_Mode mappings=[enabled=Enabled,disabled=Disabled]
Text item=Guest_Schedule_Part
Text item=Guest_timestampDay0
Text item=Guest_heat1RuntimeDay0
Text item=Guest_heat2RuntimeDay0
Text item=Guest_cool1RuntimeDay0
Text item=Guest_cool2RuntimeDay0
Text item=Guest_aux1RuntimeDay0
Text item=Guest_aux2RuntimeDay0
Text item=Guest_freeCoolRuntimeDay0
}
}
```

14
_addons_bindings/zwave/doc/aeotec/zwa012_0_0.md
View File

@ -64,7 +64,7 @@ The following table summarises the channels available for the ZWA012 -:
|--------------|------------|--------------|----------|-----------|
| Binary Sensor | sensor_binary | sensor_binary | | Switch |
| Scene Number | scene_number | scene_number | | Number |
| Alarm (access) | alarm_access | alarm_access | Door | Switch |
| Door Sensor | sensor_door | sensor_door | Door | Contact |
| Alarm (burglar) | alarm_burglar | alarm_burglar | Door | Switch |
| Battery Level | battery-level | system.battery_level | Battery | Number |
@ -96,17 +96,17 @@ This channel provides the scene, and the event as a decimal value in the form ``
| 5 | 4 x keypress |
| 6 | 5 x keypress |
### Alarm (access)
Indicates if the access control alarm is triggered.
### Door Sensor
Indicates if the door/window is open or closed.
The ```alarm_access``` channel is of type ```alarm_access``` and supports the ```Switch``` item and is in the ```Door``` category. This is a read only channel so will only be updated following state changes from the device.
The ```sensor_door``` channel is of type ```sensor_door``` and supports the ```Contact``` item and is in the ```Door``` 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 -:
The following state translation is provided for this channel to the ```Contact``` item type -:
| Value | Label |
|-------|-----------|
| OFF | OK |
| ON | Alarm |
| OPEN | Open |
| CLOSED | Closed |
### Alarm (burglar)
Indicates if the burglar alarm is triggered.

216
_addons_bindings/zwave/doc/remotec/zds220na_0_0.md Normal file
View File

@ -0,0 +1,216 @@
---
layout: documentation
title: ZDS-220NA - ZWave
---
{% include base.html %}
# ZDS-220NA Dimming Switch Module (Dual Mode)
This describes the Z-Wave device *ZDS-220NA*, manufactured by *Remotec* with the thing type UID of ```remotec_zds220na_00_000```.
The device is in the category of *Power Outlet*, defining Small devices to be plugged into a power socket in a wall which stick there.
![ZDS-220NA product image](https://opensmarthouse.org/zwavedatabase/1442/image/)
The ZDS-220NA supports routing. This allows the device to communicate using other routing enabled devices as intermediate routers. This device is also able to participate in the routing of data between other devices in the mesh network.
## Overview
Thank you for choosing the ZDS-220 (Dimming Switch Module) Z-Wave control product. ZDS-220 enabled product allows users to remotely control lighting, home appliance, and make home control easy with low installation and maintenance costs.
Thank you for choosing the ZDS-210 (Dimming Switch Module) Z-Wave control product. ZDS-210 enabled product allows users to remotely control lighting, home appliance, and make home control easy with low installation and maintenance costs.
### Inclusion Information
ZDS-220 can be configured as either a "DIMMER" or a "SWITCH" device, and it will detect the operation mode using the position of the slide switch when powering on. The ZDS-220 will stay in the selected operation mode after the inclusion process, and it will not respond to the slide switch selection after removing and re-adding power.
If the user needs to change the operation mode, the user must first perform an exclusion process. The user will then switch to the target operation mode (Dimmer or Switch), and re-include the ZDS-220 afterwards.
When prompted by your primary controller, triple-click the PROG button within 1 second.
# Note:
ZDS-210 can be configured as either a "DIMMER" or a "SWITCH" device, and it will detect the operation mode using the position of the slide switch when powering on. The ZDS-210 will stay in the selected operation mode after inclusion process, and it will not respond to the slide switch selection after removing and re-adding power.
If the user needs to change the operation mode, the user must first perform an exclusion process. The user will then switch to the target operation mode (Dimmer or Switch), and re-include the ZDS-210 afterwards.
When prompted by your primary controller, triple click the PROG button within 1 second.
### Exclusion Information
When prompted by your primary controller, triple-click the PROG button within 1 second.
# Note:
ZDS-210 can be configured as either a "DIMMER" or a "SWITCH" device, and it will detect the operation mode using the position of the slide switch when powering on. The ZDS-210 will stay in the selected operation mode after inclusion process, and it will not respond to the slide switch selection after removing and re-adding power.
If the user needs to change the operation mode, the user must first perform an exclusion process. The user will then switch to the target operation mode (Dimmer or Switch), and re-include the ZDS-210 afterwards.
When prompted by your primary controller, triple click the PROG button within 1 second.
### General Usage Information
## Channels
The following table summarises the channels available for the ZDS-220NA -:
| Channel Name | Channel ID | Channel Type | Category | Item Type |
|--------------|------------|--------------|----------|-----------|
| Switch | switch_binary | switch_binary | Switch | Switch |
| Scene Number | scene_number | scene_number | | Number |
### Switch
Switch the power on and off.
The ```switch_binary``` channel is of type ```switch_binary``` and supports the ```Switch``` item and is in the ```Switch``` category.
### Scene Number
Triggers when a scene button is pressed.
The ```scene_number``` channel is of type ```scene_number``` and supports the ```Number``` item.
## Device Configuration
The following table provides a summary of the 5 configuration parameters available in the ZDS-220NA.
Detailed information on each parameter can be found in the sections below.
| Param | Name | Description |
|-------|-------|-------------|
| 5 | State after power failure | State after power failure |
| 13 | Double click option | Double click option |
| 17 | Dimmer time from 0% to max. | Dimmer time from 0% to max. |
| 18 | Maximum Dimmer level control | Maximum Dimmer level control |
| 19 | Minimum Dimmer level control | Minimum Dimmer level control |
### Parameter 5: State after power failure
State after power failure
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Switch OFF |
| 1 | Switch saves its state before power failure |
The manufacturer defined default value is ```1``` (Switch saves its state before power failure).
This parameter has the configuration ID ```config_5_1``` and is of type ```INTEGER```.
### Parameter 13: Double click option
Double click option
Double click option (set to max. brightness)
The following option values may be configured -:
| Value | Description |
|--------|-------------|
| 0 | Disabled |
| 1 | Enabled |
The manufacturer defined default value is ```1``` (Enabled).
This parameter has the configuration ID ```config_13_1``` and is of type ```INTEGER```.
### Parameter 17: Dimmer time from 0% to max.
Dimmer time from 0% to max.
Time to move the Dimmer from 0% to max. dimming values.
(The ZDS-210 will implement the dimming duration if received this parameter value from controller/gateway.Otherwise, the ZDS-210 will implement the local parameter value)
Values in the range 0 to 5 may be set.
The manufacturer defined default value is ```3```.
This parameter has the configuration ID ```config_17_1``` and is of type ```INTEGER```.
### Parameter 18: Maximum Dimmer level control
Maximum Dimmer level control
Values in the range 2 to 99 may be set.
The manufacturer defined default value is ```99```.
This parameter has the configuration ID ```config_18_1``` and is of type ```INTEGER```.
### Parameter 19: Minimum Dimmer level control
Minimum Dimmer level control
Values in the range 1 to 98 may be set.
The manufacturer defined default value is ```13```.
This parameter has the configuration ID ```config_19_1``` and is of type ```INTEGER```.
## Association Groups
Association groups allow the device to send unsolicited reports to the controller, or other devices in the network. Using association groups can allow you to eliminate polling, providing instant feedback of a device state change without unnecessary network traffic.
The ZDS-220NA supports 2 association groups.
### Group 1: Lifeline
The Lifeline association group reports device status to a hub and is not designed to control other devices directly. When using the Lineline group with a hub, in most cases, only the lifeline group will need to be configured and normally the hub will perform this automatically during the device initialisation.
Association group 1 supports 1 node.
### Group 2: Group 2
# Dimmer mode:
After receiving a dimming command from a local switch or gateway (e.g. 50%), the ZDS-210 will automatically send out a related basic set command (e.g. 50%) to its associated group.
# Switch mode:
After receiving a basic set command from a local switch or gateway, On (0xFF) or Off (0x00), the ZDS-210 will automatically send out a related basic set command, On (0xFF) or Off (0x00) to its associated group.
Association group 2 supports 4 nodes.
## Technical Information
### Endpoints
#### Endpoint 0
| Command Class | Comment |
|---------------|---------|
| COMMAND_CLASS_NO_OPERATION_V1| |
| COMMAND_CLASS_BASIC_V1| |
| COMMAND_CLASS_SWITCH_BINARY_V1| |
| COMMAND_CLASS_SCENE_ACTIVATION_V1| |
| COMMAND_CLASS_SCENE_ACTUATOR_CONF_V1| |
| COMMAND_CLASS_TRANSPORT_SERVICE_V1| |
| COMMAND_CLASS_ASSOCIATION_GRP_INFO_V1| |
| COMMAND_CLASS_DEVICE_RESET_LOCALLY_V1| |
| COMMAND_CLASS_ZWAVEPLUS_INFO_V1| |
| COMMAND_CLASS_SUPERVISION_V1| |
| COMMAND_CLASS_CONFIGURATION_V1| |
| COMMAND_CLASS_MANUFACTURER_SPECIFIC_V1| |
| COMMAND_CLASS_POWERLEVEL_V1| |
| COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1| |
| COMMAND_CLASS_ASSOCIATION_V2| |
| COMMAND_CLASS_VERSION_V2| |
| COMMAND_CLASS_SECURITY_V1| |
| COMMAND_CLASS_SECURITY_2_V1| |
### Documentation Links
* [Manual](https://opensmarthouse.org/zwavedatabase/1442/reference/F820-8131-0000_USER_Manual_20170816_1.pdf)
---
Did you spot an error in the above definition or want to improve the content?
You can [contribute to the database here](https://opensmarthouse.org/zwavedatabase/1442).

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

@ -244,7 +244,8 @@
<item-type>DateTime</item-type>
<label>Broadcast Date</label>
<description>The broadcast date of the currently playing media</description>
<state readOnly="true"/>
<category>Calendar</category>
<state readOnly="true" pattern="%1$tY-%1$tm-%1$td"/>
</channel-type>
<channel-type id="composer" advanced="true">
@ -258,7 +259,8 @@
<item-type>DateTime</item-type>
<label>Creation Date</label>
<description>The creation date of the currently playing media</description>
<state readOnly="true"/>
<category>Calendar</category>
<state readOnly="true" pattern="%1$tY-%1$tm-%1$td"/>
</channel-type>
<channel-type id="discNumber" advanced="true">
@ -300,7 +302,8 @@
<item-type>DateTime</item-type>
<label>Release Date</label>
<description>The release date of the currently playing media</description>
<state readOnly="true"/>
<category>Calendar</category>
<state readOnly="true" pattern="%1$tY-%1$tm-%1$td"/>
</channel-type>
<channel-type id="seasonNumber" advanced="true">

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

@ -8,62 +8,60 @@
<item-type>String</item-type>
<label>Last Error Event</label>
<description>Displays contents of last [ERROR] event</description>
<state readOnly="true"></state>
<state readOnly="true"/>
</channel-type>
<channel-type id="lastWarningEvent">
<item-type>String</item-type>
<label>Last Warning Event</label>
<description>Displays contents of last [WARN] event</description>
<state readOnly="true"></state>
<state readOnly="true"/>
</channel-type>
<channel-type id="lastCustomEvent" advanced="true">
<item-type>String</item-type>
<label>Last Custom Event</label>
<description>Displays contents of last custom event</description>
<state readOnly="true"></state>
<state readOnly="true"/>
</channel-type>
<channel-type id="warningEvents">
<item-type>Number</item-type>
<label>Warning Events Matched</label>
<description>Displays number of [WARN] lines matched to search pattern</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="errorEvents">
<item-type>Number</item-type>
<label>Error Events Matched</label>
<description>Displays number of [ERROR] lines matched to search pattern</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="customEvents" advanced="true">
<item-type>Number</item-type>
<label>Custom Events Matched</label>
<description>Displays number of custom lines matched to search pattern</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="logRotated" advanced="true">
<item-type>DateTime</item-type>
<label>Log Rotated</label>
<description>Last time when log rotated recognized</description>
<state readOnly="true"></state>
<category>Time</category>
<state readOnly="true" pattern="%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS"/>
</channel-type>
<channel-type id="newErrorEvent">
<kind>trigger</kind>
<label>New Error Event</label>
<description>Fires when a new [ERROR] appears in the log</description>
<event>
</event>
</channel-type>
<channel-type id="newWarningEvent">
<kind>trigger</kind>
<label>New Warning Event</label>
<description>Fires when a new [WARN] appears in the log</description>
<event>
</event>
</channel-type>
<channel-type id="newCustomEvent" advanced="true">
<kind>trigger</kind>
<label>New Custom Event</label>
<description>Fires when a new [CUSTOM] appears in the log</description>
<event>
</event>
</channel-type>
</thing:thing-descriptions>

4
_thing_types/org.openhab.binding.miio/src/main/resources/OH-INF/thing/vacuumThing.xml
View File

@ -347,14 +347,14 @@
<item-type>DateTime</item-type>
<label>Cleaning Start</label>
<description>Last Cleaning Start Time</description>
<category>Date</category>
<category>Time</category>
<state readOnly="true"/>
</channel-type>
<channel-type id="last_clean_end_time">
<item-type>DateTime</item-type>
<label>Cleaning End</label>
<description>Last Cleaning End Time</description>
<category>Date</category>
<category>Time</category>
<state readOnly="true"/>
</channel-type>
<channel-type id="last_clean_duration">

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

@ -46,14 +46,14 @@
<item-type>DateTime</item-type>
<label>Date</label>
<description>NTP refreshed date &amp; time</description>
<category>Date</category>
<category>Time</category>
<state readOnly="true"/>
</channel-type>
<channel-type id="string-channel">
<item-type>String</item-type>
<label>Date</label>
<description>NTP refreshed date &amp; time</description>
<category>Date</category>
<category>Time</category>
<state readOnly="true"/>
<config-description>
<parameter name="DateTimeFormat" type="text" required="false">

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

@ -72,6 +72,7 @@
<label>@text/tempTrendLabel</label>
<description>@text/tempTrendDescription</description>
</channel>
<channel id="timestamp" typeId="timestamp"/>
</channels>
</channel-group-type>
@ -163,6 +164,7 @@
<item-type>String</item-type>
<label>@text/trendLabel</label>
<description>@text/trendDescription</description>
<category>Line</category>
<state readOnly="true" pattern="%s">
<options>
<option value="1">@text/trend1</option>
@ -174,19 +176,23 @@
</state>
</channel-type>
<channel-type id="timestamp" advanced="true">
<channel-type id="timestamp">
<item-type>DateTime</item-type>
<label>@text/timestampLabel</label>
<description>@text/timestampDescription</description>
<category>Observation time</category>
<state readOnly="true"></state>
<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="cloudiness">
<item-type>Number:Dimensionless</item-type>
<label>@text/cloudinessLabel</label>
<description>@text/cloudinessDescription</description>
<category>Clouds</category>
<category>Sun_Clouds</category>
<state min="0" max="100" pattern="%d %%"/>
</channel-type>

12
_thing_types/org.openhab.binding.sncf/src/main/resources/OH-INF/thing/bridge.xml Normal file
View File

@ -0,0 +1,12 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="sncf"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<bridge-type id="api">
<label>SNCF API</label>
<config-description-ref uri="thing-type:sncf:api"/>
</bridge-type>
</thing:thing-descriptions>

74
_thing_types/org.openhab.binding.sncf/src/main/resources/OH-INF/thing/station.xml Normal file
View File

@ -0,0 +1,74 @@
<?xml version="1.0" encoding="UTF-8"?>
<thing:thing-descriptions bindingId="sncf"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:thing="https://openhab.org/schemas/thing-description/v1.0.0"
xsi:schemaLocation="https://openhab.org/schemas/thing-description/v1.0.0 https://openhab.org/schemas/thing-description-1.0.0.xsd">
<thing-type id="station">
<supported-bridge-type-refs>
<bridge-type-ref id="api"/>
</supported-bridge-type-refs>
<label>Station</label>
<channel-groups>
<channel-group id="arrivals" typeId="passage">
<label>Next Arrival</label>
</channel-group>
<channel-group id="departures" typeId="passage">
<label>Next Departure</label>
</channel-group>
</channel-groups>
<representation-property>stopPointId</representation-property>
<config-description>
<parameter name="stopPointId" type="text" required="true">
<label>Station ID</label>
</parameter>
</config-description>
</thing-type>
<channel-group-type id="passage">
<label>Other</label>
<channels>
<channel id="direction" typeId="direction"/>
<channel id="lineName" typeId="lineName"/>
<channel id="name" typeId="name"/>
<channel id="network" typeId="network"/>
<channel id="timestamp" typeId="timestamp"/>
</channels>
</channel-group-type>
<channel-type id="direction">
<item-type>String</item-type>
<label>Direction</label>
<state readOnly="true"></state>
</channel-type>
<channel-type id="lineName">
<item-type>String</item-type>
<label>Line</label>
<state readOnly="true"></state>
</channel-type>
<channel-type id="name" advanced="true">
<item-type>String</item-type>
<label>Name</label>
<state readOnly="true"></state>
</channel-type>
<channel-type id="network" advanced="true">
<item-type>String</item-type>
<label>Network</label>
<state readOnly="true"></state>
</channel-type>
<channel-type id="timestamp">
<item-type>DateTime</item-type>
<label>Timestamp</label>
<category>time</category>
<state readOnly="true" pattern="%1$tH:%1$tM:%1$tS"/>
</channel-type>
</thing:thing-descriptions>

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

@ -21,6 +21,69 @@
<channel id="systemStateRaw" typeId="systemStateRaw"/>
<channel id="awayMode" typeId="awayMode"/>
<channel id="awayModeRaw" typeId="awayModeRaw"/>
<channel id="fanMode" typeId="fanMode"/>
<channel id="fanModeRaw" typeId="fanModeRaw"/>
<channel id="fanState" typeId="fanState"/>
<channel id="fanStateRaw" typeId="fanStateRaw"/>
<channel id="scheduleMode" typeId="scheduleMode"/>
<channel id="scheduleModeRaw" typeId="scheduleModeRaw"/>
<channel id="schedulePart" typeId="schedulePart"/>
<channel id="timestampDay0" typeId="timestampRuntime"/>
<channel id="timestampDay1" typeId="timestampRuntime"/>
<channel id="timestampDay2" typeId="timestampRuntime"/>
<channel id="timestampDay3" typeId="timestampRuntime"/>
<channel id="timestampDay4" typeId="timestampRuntime"/>
<channel id="timestampDay5" typeId="timestampRuntime"/>
<channel id="timestampDay6" typeId="timestampRuntime"/>
<channel id="heat1RuntimeDay0" typeId="heat1Runtime"/>
<channel id="heat1RuntimeDay1" typeId="heat1Runtime"/>
<channel id="heat1RuntimeDay2" typeId="heat1Runtime"/>
<channel id="heat1RuntimeDay3" typeId="heat1Runtime"/>
<channel id="heat1RuntimeDay4" typeId="heat1Runtime"/>
<channel id="heat1RuntimeDay5" typeId="heat1Runtime"/>
<channel id="heat1RuntimeDay6" typeId="heat1Runtime"/>
<channel id="heat2RuntimeDay0" typeId="heat2Runtime"/>
<channel id="heat2RuntimeDay1" typeId="heat2Runtime"/>
<channel id="heat2RuntimeDay2" typeId="heat2Runtime"/>
<channel id="heat2RuntimeDay3" typeId="heat2Runtime"/>
<channel id="heat2RuntimeDay4" typeId="heat2Runtime"/>
<channel id="heat2RuntimeDay5" typeId="heat2Runtime"/>
<channel id="heat2RuntimeDay6" typeId="heat2Runtime"/>
<channel id="cool1RuntimeDay0" typeId="cool1Runtime"/>
<channel id="cool1RuntimeDay1" typeId="cool1Runtime"/>
<channel id="cool1RuntimeDay2" typeId="cool1Runtime"/>
<channel id="cool1RuntimeDay3" typeId="cool1Runtime"/>
<channel id="cool1RuntimeDay4" typeId="cool1Runtime"/>
<channel id="cool1RuntimeDay5" typeId="cool1Runtime"/>
<channel id="cool1RuntimeDay6" typeId="cool1Runtime"/>
<channel id="cool2RuntimeDay0" typeId="cool2Runtime"/>
<channel id="cool2RuntimeDay1" typeId="cool2Runtime"/>
<channel id="cool2RuntimeDay2" typeId="cool2Runtime"/>
<channel id="cool2RuntimeDay3" typeId="cool2Runtime"/>
<channel id="cool2RuntimeDay4" typeId="cool2Runtime"/>
<channel id="cool2RuntimeDay5" typeId="cool2Runtime"/>
<channel id="cool2RuntimeDay6" typeId="cool2Runtime"/>
<channel id="aux1RuntimeDay0" typeId="aux1Runtime"/>
<channel id="aux1RuntimeDay1" typeId="aux1Runtime"/>
<channel id="aux1RuntimeDay2" typeId="aux1Runtime"/>
<channel id="aux1RuntimeDay3" typeId="aux1Runtime"/>
<channel id="aux1RuntimeDay4" typeId="aux1Runtime"/>
<channel id="aux1RuntimeDay5" typeId="aux1Runtime"/>
<channel id="aux1RuntimeDay6" typeId="aux1Runtime"/>
<channel id="aux2RuntimeDay0" typeId="aux2Runtime"/>
<channel id="aux2RuntimeDay1" typeId="aux2Runtime"/>
<channel id="aux2RuntimeDay2" typeId="aux2Runtime"/>
<channel id="aux2RuntimeDay3" typeId="aux2Runtime"/>
<channel id="aux2RuntimeDay4" typeId="aux2Runtime"/>
<channel id="aux2RuntimeDay5" typeId="aux2Runtime"/>
<channel id="aux2RuntimeDay6" typeId="aux2Runtime"/>
<channel id="freeCoolRuntimeDay0" typeId="freeCoolRuntime"/>
<channel id="freeCoolRuntimeDay1" typeId="freeCoolRuntime"/>
<channel id="freeCoolRuntimeDay2" typeId="freeCoolRuntime"/>
<channel id="freeCoolRuntimeDay3" typeId="freeCoolRuntime"/>
<channel id="freeCoolRuntimeDay4" typeId="freeCoolRuntime"/>
<channel id="freeCoolRuntimeDay5" typeId="freeCoolRuntime"/>
<channel id="freeCoolRuntimeDay6" typeId="freeCoolRuntime"/>
</channels>
<properties>
@ -89,6 +152,136 @@
<state readOnly="true"/>
</channel-type>
<channel-type id="fanMode">
<item-type>String</item-type>
<label>Fan Mode</label>
<description>Current Fan Mode</description>
<state readOnly="false">
<options>
<option value="auto">Auto</option>
<option value="on">On</option>
</options>
</state>
</channel-type>
<channel-type id="fanModeRaw" advanced="true">
<item-type>Number</item-type>
<label>Fan Mode (Raw)</label>
<description>Current Fan Mode, as an integer number</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="fanState">
<item-type>Switch</item-type>
<label>Fan State</label>
<description>Current Fan State</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="fanStateRaw" advanced="true">
<item-type>Number</item-type>
<label>Fan State (Raw)</label>
<description>Current Fan State, as an integer number</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="scheduleMode">
<item-type>String</item-type>
<label>Schedule Mode</label>
<description>Current Schedule Mode</description>
<state readOnly="false">
<options>
<option value="disabled">Disabled</option>
<option value="enabled">Enabled</option>
</options>
</state>
</channel-type>
<channel-type id="scheduleModeRaw" advanced="true">
<item-type>Number</item-type>
<label>Schedule Mode (Raw)</label>
<description>Current Schedule Mode, as an integer number</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="schedulePart">
<item-type>String</item-type>
<label>Schedule Part</label>
<description>Current Schedule Part</description>
<state readOnly="true">
<options>
<option value="morning">Morning</option>
<option value="day">Day</option>
<option value="evening">Evening</option>
<option value="night">Night</option>
<option value="inactive">Inactive</option>
</options>
</state>
</channel-type>
<channel-type id="schedulePartRaw" advanced="true">
<item-type>Number</item-type>
<label>Schedule Part (Raw)</label>
<description>Current Schedule Part, as an integer number</description>
<state readOnly="true"/>
</channel-type>
<channel-type id="timestampRuntime" advanced="true">
<item-type>DateTime</item-type>
<label>Runtime Record Timestamp</label>
<description>Time stamp of Runtime Update (Day 0 = TODAY, Day 6 = 6 days ago)</description>
<state readOnly="true" pattern="%1$tY-%1$tm-%1$td %1$tH:%1$tM"/>
</channel-type>
<channel-type id="heat1Runtime" advanced="true">
<item-type>Number</item-type>
<label>Heat1 Runtime Minutes</label>
<description>Run time in heat1 mode in minutes (Day 0 = TODAY, Day 6 = 6 days ago)</description>
<state readOnly="true" pattern="%d min"/>
</channel-type>
<channel-type id="heat2Runtime" advanced="true">
<item-type>Number</item-type>
<label>Heat2 Runtime Minutes</label>
<description>Run time in heat2 mode in minutes (Day 0 = TODAY, Day 6 = 6 days ago)</description>
<state readOnly="true" pattern="%d min"/>
</channel-type>
<channel-type id="cool1Runtime" advanced="true">
<item-type>Number</item-type>
<label>Cool1 Runtime Minutes</label>
<description>Run time in cool1 mode in minutes (Day 0 = TODAY, Day 6 = 6 days ago)</description>
<state readOnly="true" pattern="%d min"/>
</channel-type>
<channel-type id="cool2Runtime" advanced="true">
<item-type>Number</item-type>
<label>Cool2 Runtime Minutes</label>
<description>Run time in cool2 mode in minutes (Day 0 = TODAY, Day 6 = 6 days ago)</description>
<state readOnly="true" pattern="%d min"/>
</channel-type>
<channel-type id="aux1Runtime" advanced="true">
<item-type>Number</item-type>
<label>Aux1 Runtime Minutes</label>
<description>Run time in aux1 mode in minutes (Day 0 = TODAY, Day 6 = 6 days ago)</description>
<state readOnly="true" pattern="%d min"/>
</channel-type>
<channel-type id="aux2Runtime" advanced="true">
<item-type>Number</item-type>
<label>Aux2 Runtime Minutes</label>
<description>Run time in aux2 mode in minutes (Day 0 = TODAY, Day 6 = 6 days ago)</description>
<state readOnly="true" pattern="%d min"/>
</channel-type>
<channel-type id="freeCoolRuntime" advanced="true">
<item-type>Number</item-type>
<label>Free Cool Runtime Minutes</label>
<description>Run time in Free Cool mode in minutes (Day 0 = TODAY, Day 6 = 6 days ago)</description>
<state readOnly="true" pattern="%d min"/>
</channel-type>
<channel-type id="systemState">
<item-type>String</item-type>
<label>System State</label>

6
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/aeotec/zwa012_0_0.xml
View File

@ -26,10 +26,10 @@ Door/Window Sensor 7 Pro<br /> <h1>Overview</h1><p>Aeotec Door / Window Sensor 7
<property name="binding:*:DecimalType">COMMAND_CLASS_CENTRAL_SCENE</property>
</properties>
</channel>
<channel id="alarm_access" typeId="alarm_access">
<label>Alarm (access)</label>
<channel id="sensor_door" typeId="sensor_door">
<label>Door Sensor</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_ALARM;type=ACCESS_CONTROL</property>
<property name="binding:*:OpenClosedType">COMMAND_CLASS_ALARM</property>
</properties>
</channel>
<channel id="alarm_burglar" typeId="alarm_burglar">

129
_thing_types/org.openhab.binding.zwave/src/main/resources/OH-INF/thing/remotec/zds220na_0_0.xml Normal file
View File

@ -0,0 +1,129 @@
<?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="remotec_zds220na_00_000" listed="false">
<label>ZDS-220NA Dimming Switch Module (Dual Mode)</label>
<description><![CDATA[
Dimming Switch Module (Dual Mode)<br /> <h1>Overview</h1><p>Thank you for choosing the ZDS-220 (Dimming Switch Module) Z-Wave control product. ZDS-220 enabled product allows users to remotely control lighting, home appliance, and make home control easy with low installation and maintenance costs.<br /></p><p>Thank you for choosing the ZDS-210 (Dimming Switch Module) Z-Wave control product. ZDS-210 enabled product allows users to remotely control lighting, home appliance, and make home control easy with low installation and maintenance costs.</p> <br /> <h2>Inclusion Information</h2><p>ZDS-220 can be configured as either a "DIMMER" or a "SWITCH" device, and it will detect the operation mode using the position of the slide switch when powering on. The ZDS-220 will stay in the selected operation mode after the inclusion process, and it will not respond to the slide switch selection after removing and re-adding power.</p><p>If the user needs to change the operation mode, the user must first perform an exclusion process. The user will then switch to the target operation mode (Dimmer or Switch), and re-include the ZDS-220 afterwards.</p><p>When prompted by your primary controller, triple-click the PROG button within 1 second.</p><h1>Note:</h1> <p>ZDS-210 can be configured as either a "DIMMER" or a "SWITCH" device, and it will detect the operation mode using the position of the slide switch when powering on. The ZDS-210 will stay in the selected operation mode after inclusion process, and it will not respond to the slide switch selection after removing and re-adding power.</p> <p>If the user needs to change the operation mode, the user must first perform an exclusion process. The user will then switch to the target operation mode (Dimmer or Switch), and re-include the ZDS-210 afterwards.</p> <p>When prompted by your primary controller, triple click the PROG button within 1 second.</p> <br /> <h2>Exclusion Information</h2><p>When prompted by your primary controller, triple-click the PROG button within 1 second.</p><h1>Note:</h1> <p>ZDS-210 can be configured as either a "DIMMER" or a "SWITCH" device, and it will detect the operation mode using the position of the slide switch when powering on. The ZDS-210 will stay in the selected operation mode after inclusion process, and it will not respond to the slide switch selection after removing and re-adding power.</p> <p>If the user needs to change the operation mode, the user must first perform an exclusion process. The user will then switch to the target operation mode (Dimmer or Switch), and re-include the ZDS-210 afterwards.</p> <p>When prompted by your primary controller, triple click the PROG button within 1 second.</p> <br /> <h2>Wakeup Information</h2><p><br /></p>
]]></description>
<category>PowerOutlet</category>
<!-- CHANNEL DEFINITIONS -->
<channels>
<channel id="switch_binary" typeId="switch_binary">
<label>Switch</label>
<properties>
<property name="binding:*:OnOffType">COMMAND_CLASS_SWITCH_BINARY</property>
</properties>
</channel>
<channel id="scene_number" typeId="scene_number">
<label>Scene Number</label>
<properties>
<property name="binding:*:DecimalType">COMMAND_CLASS_SCENE_ACTIVATION</property>
</properties>
</channel>
</channels>
<!-- DEVICE PROPERTY DEFINITIONS -->
<properties>
<property name="vendor">Remotec</property>
<property name="modelId">ZDS-220NA</property>
<property name="manufacturerId">5254</property>
<property name="manufacturerRef">8200:8131</property>
<property name="dbReference">1442</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_5_1" type="integer" groupName="configuration">
<label>5: State after power failure</label>
<description>State after power failure</description>
<default>1</default>
<options>
<option value="0">Switch OFF</option>
<option value="1">Switch saves its state before power failure</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_13_1" type="integer" groupName="configuration">
<label>13: Double click option</label>
<description><![CDATA[
Double click option<br /> <h1>Overview</h1><p>Double click option (set to max. brightness)</p>
]]></description>
<default>1</default>
<options>
<option value="0">Disabled</option>
<option value="1">Enabled</option>
</options>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_17_1" type="integer" groupName="configuration"
min="0" max="5">
<label>17: Dimmer time from 0% to max.</label>
<description><![CDATA[
Dimmer time from 0% to max.<br /> <h1>Overview</h1><p>Time to move the Dimmer from 0% to max. dimming values.</p> <p>(The ZDS-210 will implement the dimming duration if received this parameter value from controller/gateway.Otherwise, the ZDS-210 will implement the local parameter value)</p>
]]></description>
<default>3</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_18_1" type="integer" groupName="configuration"
min="2" max="99">
<label>18: Maximum Dimmer level control</label>
<description>Maximum Dimmer level control</description>
<default>99</default>
<limitToOptions>false</limitToOptions>
</parameter>
<parameter name="config_19_1" type="integer" groupName="configuration"
min="1" max="98">
<label>19: Minimum Dimmer level control</label>
<description>Minimum Dimmer level control</description>
<default>13</default>
<limitToOptions>false</limitToOptions>
</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: Group 2</label>
<description><![CDATA[
<br /> <h1>Overview</h1><h1>Dimmer mode:</h1> <p>After receiving a dimming command from a local switch or gateway (e.g. 50%), the ZDS-210 will automatically send out a related basic set command (e.g. 50%) to its associated group.</p> <h1>Switch mode:</h1> <p>After receiving a basic set command from a local switch or gateway, On (0xFF) or Off (0x00), the ZDS-210 will automatically send out a related basic set command, On (0xFF) or Off (0x00) to its associated group.</p>
]]></description>
<multipleLimit>4</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>

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

@ -40,7 +40,7 @@ Contact Sensor<br /> <h1>Overview</h1><ul><li><b>Door / window monitoring</b>: f
<property name="manufacturerId">027A</property>
<property name="manufacturerRef">7000:E001</property>
<property name="dbReference">1411</property>
<property name="defaultAssociations">1</property>
<property name="defaultAssociations">1,2</property>
</properties>
<!-- CONFIGURATION DESCRIPTIONS -->

4
installation/openhabian.md
View File

@ -83,8 +83,8 @@ Be aware that it isn't the [answer to the ultimate question](https://en.wikipedi
Take an openHAB config backup BEFORE you upgrade from openHAB v2 to v3. You should also take a system level backup!
:::
Menu option 42 can also do the downgrade and change the _environment_ back to match openHAB 2 **BUT** it'll ONLY exchange the binary packages.
There is no migration to change your configuration back to a openHAB 2 compatible one.
Menu option 42 can also do the downgrade and change the _environment_ back to match openHAB 2 but ATTENTION it'll only exchange the OS setup and the openHAB packages.
It will NOT migrate your configuration back to a openHAB 2 compatible one. There is no software that can do this for you.
So it is essential that you take a backup before you upgrade.
You will have to restore your setup from that backup after a downgrade using menu option 51 or by manually using `openhab-cli restore <archive file>`.
Note option 42 will also not downgrade Java.