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

pull/764/head
CloudBees DEV@Cloud 2018-07-27 14:45:43 +02:00
parent 32ee74eb91
commit 3df3c09fb3
46 changed files with 272 additions and 159 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_addons_bindings/amazonechocontrol/readme.md
View File

@ -123,7 +123,7 @@ All Amazon devices (echo, echospot, echoshow, wha) needs the following configura
|--------------------------|----------------------------------------------------|
| serialNumber | Serial number of the amazon echo in the Alexa app |
You will find the serial number in the alexa app.
You will find the serial number in the alexa app or on the webpage YOUR_OPENHAB/amazonechocontrol/YOUR_ACCOUNT (e.g. http://openhab:8080/amazonechocontrol/account1).
### Flash Briefing Profile

2
_addons_bindings/astro1/readme.md
View File

@ -17,7 +17,7 @@ install: legacy
The Astro binding is used for calculating many `DateTime` and positional values for sun and moon and for scheduling of events.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/astro/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/astro/).
### Binding Configuration

2
_addons_bindings/autelis1/readme.md
View File

@ -23,7 +23,7 @@ The binding is fairly complete and supports the following functionality.
* Read circuit, auxiliary, temperature, pump, chemistry and system values
* Control circuit, auxiliary lighting scenes, and temperature set points
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/autelis/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/autelis/).
## Binding Configuration

51
_addons_bindings/avmfritz/readme.md
View File

@ -28,7 +28,8 @@ The Box has to run at least on firmware FRITZ!OS 6.00 and has to support the "Sm
### FRITZ!DECT 200 / FRITZ!DECT 210
This switchable outlets [FRITZ!DECT 210](https://avm.de/produkte/fritzdect/fritzdect-210/) and [FRITZ!DECT 200](https://avm.de/produkte/fritzdect/fritzdect-200/) have to be connected to a FRITZ!Box by DECT protocol.
They support switching the outlet, current power and accumulated energy consumption and temperature readings.
They support switching the outlet and reading the current power, current voltage, accumulated energy consumption and temperature.
**NOTE:** The `voltage` channel will be added to the thing during runtime - if the interface supports it (FRITZ!OS 7 or higher).
### FRITZ!DECT Repeater 100
@ -38,8 +39,9 @@ It only supports temperature readings.
### FRITZ!Powerline 546E
This [powerline adapter](http://avm.de/produkte/fritzpowerline/fritzpowerline-546e/) can be used via the bridge or in stand-alone mode.
It supports switching the outlet and current power and energy consumption readings.
It supports switching the outlet and reading the current power, current voltage and accumulated energy consumption.
This device does not contain a temperature sensor.
**NOTE:** The `voltage` channel will be added to the thing during runtime - if the interface supports it (FRITZ!OS 7 or higher).
### FRITZ!DECT 301 / FRITZ!DECT 300 / Comet DECT
@ -48,6 +50,7 @@ The FRITZ!Box can handle up to twelve heating thermostats.
The binding provides channels for reading and setting the temperature.
Additionally you can check the eco temperature, the comfort temperature and the battery level of the device.
The FRITZ!Box has to run at least on firmware FRITZ!OS 6.35.
**NOTE:** The `battery_level` channel will be added to the thing during runtime - if the interface supports it (FRITZ!OS 7 or higher).
### FRITZ! groups
@ -94,23 +97,25 @@ If correct credentials are set in the bridge configuration, connected AHA device
## Supported Channels
| Channel Type ID | Item Type | Description | Available on thing |
|-----------------|--------------------|--------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
| mode | String | States the mode of the device (MANUAL/AUTOMATIC) | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| locked | Contact | Device is locked for switching over external sources (OPEN/CLOSE) | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| device_locked | Contact | Device is locked for switching manually (OPEN/CLOSE) - FRITZ!OS 6.90 | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| temperature | Number:Temperature | Actual measured temperature | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!DECT Repeater 100, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| energy | Number:Energy | Accumulated energy consumption | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |
| power | Number:Power | Current power consumption | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |
| outlet | Switch | Switchable outlet (ON/OFF) | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |
| actual_temp | Number:Temperature | Actual Temperature of heating thermostat | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| set_temp | Number:Temperature | Set Temperature of heating thermostat | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| eco_temp | Number:Temperature | Eco Temperature of heating thermostat | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| comfort_temp | Number:Temperature | Comfort Temperature of heating thermostat | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| radiator_mode | String | Mode of heating thermostat (ON/OFF/COMFORT/ECO/BOOST) | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| next_change | DateTime | Next change of the Set Temperature if scheduler is activated in the FRITZ!Box settings - FRITZ!OS 6.80 | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| next_temp | Number:Temperature | Next Set Temperature if scheduler is activated in the FRITZ!Box settings - FRITZ!OS 6.80 | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| battery_low | Switch | Battery Level Low (ON/OFF) - FRITZ!OS 6.80 | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| Channel Type ID | Item Type | Description | Available on thing |
|-----------------|--------------------------|--------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
| mode | String | States the mode of the device (MANUAL/AUTOMATIC/VACATION) | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| locked | Contact | Device is locked for switching over external sources (OPEN/CLOSE) | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| device_locked | Contact | Device is locked for switching manually (OPEN/CLOSE) - FRITZ!OS 6.90 | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| temperature | Number:Temperature | Current measured temperature | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!DECT Repeater 100, FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| energy | Number:Energy | Accumulated energy consumption | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |
| power | Number:Power | Current power consumption | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |
| voltage | Number:ElectricPotential | Current voltage - FRITZ!OS 7 | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |
| outlet | Switch | Switchable outlet (ON/OFF) | FRITZ!DECT 210, FRITZ!DECT 200, FRITZ!Powerline 546E |
| actual_temp | Number:Temperature | Current temperature of heating thermostat | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| set_temp | Number:Temperature | Set Temperature of heating thermostat | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| eco_temp | Number:Temperature | Eco Temperature of heating thermostat | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| comfort_temp | Number:Temperature | Comfort Temperature of heating thermostat | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| radiator_mode | String | Mode of heating thermostat (ON/OFF/COMFORT/ECO/BOOST/WINDOW_OPEN) | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| next_change | DateTime | Next change of the Set Temperature if scheduler is activated in the FRITZ!Box settings - FRITZ!OS 6.80 | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| next_temp | Number:Temperature | Next Set Temperature if scheduler is activated in the FRITZ!Box settings - FRITZ!OS 6.80 | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| battery_level | Number | Battery level (in %) - FRITZ!OS 7 | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
| battery_low | Switch | Battery level low (ON/OFF) - FRITZ!OS 6.80 | FRITZ!DECT 301, FRITZ!DECT 300, Comet DECT |
## Full Example
@ -133,13 +138,15 @@ Switch Outlet1 "Switchable outlet" { channel="avmfritz:FRITZ_DECT_200:1:xxxxxxxx
Number:Temperature Temperature1 "Current measured temperature [%.1f %unit%]" { channel="avmfritz:FRITZ_DECT_200:1:xxxxxxxxxxxx:temperature" }
Number:Energy Energy1 "Accumulated energy consumption [%.3f kWh]" { channel="avmfritz:FRITZ_DECT_200:1:xxxxxxxxxxxx:energy" }
Number:Power Power1 "Current power consumption [%.2f %unit%]" { channel="avmfritz:FRITZ_DECT_200:1:xxxxxxxxxxxx:power" }
Number:ElectricPotential Voltage1 "Current voltage [%.1f %unit%]" { channel="avmfritz:FRITZ_DECT_200:1:xxxxxxxxxxxx:voltage" }
Switch Outlet2 "Switchable outlet" { channel="avmfritz:FRITZ_Powerline_546E:1:yy_yy_yy_yy_yy_yy:outlet" }
Number:Temperature COMETDECTTemperature "Current measured temperature [%.1f %unit%]" { channel="avmfritz:Comet_DECT:1:aaaaaabbbbbb:actual_temp" }
Number:Temperature COMETDECTSetTemperature "Thermostat temperature set point [%.1f %unit%]" { channel="avmfritz:Comet_DECT:1:aaaaaabbbbbb:set_temp" }
String COMETDECTRadiatorMode "Radiator mode [%s]" { channel="avmfritz:Comet_DECT:1:aaaaaabbbbbb:radiator_mode" }
Switch COMETDECTBattery "Battery low" { channel="avmfritz:Comet_DECT:1:aaaaaabbbbbb:battery_low" }
Number COMETDECTBattery "Battery level" { channel="avmfritz:Comet_DECT:1:aaaaaabbbbbb:battery_level" }
Switch COMETDECTBatteryLow "Battery low" { channel="avmfritz:Comet_DECT:1:aaaaaabbbbbb:battery_low" }
Number:Temperature FRITZ_GROUP_HEATINGSetTemperature "Group temperature set point [%.1f %unit%]" { channel="avmfritz:FRITZ_GROUP_HEATING:1:AA_AA_AA_900:set_temp" }
@ -156,6 +163,7 @@ sitemap demo label="Main Menu" {
Text item=Temperature1 icon="temperature"
Text item=Energy1 icon="energy"
Text item=Power1 icon="energy"
Text item=Voltage1 icon="energy"
}
Frame label="FRITZ!Powerline 546E switchable outlet" {
@ -166,7 +174,8 @@ sitemap demo label="Main Menu" {
Text item=COMETDECTTemperature icon="temperature"
Setpoint item=COMETDECTSetTemperature minValue=8.0 maxValue=28.0 step=0.5 icon="temperature"
Selection item=COMETDECTRadiatorMode mappings=["ON"="ON", "OFF"="OFF", "COMFORT"="COMFORT", "ECO"="ECO", "BOOST"="BOOST"] icon="heating"
Switch item=COMETDECTBattery icon="lowbattery"
Text item=COMETDECTBattery icon="battery"
Switch item=COMETDECTBatteryLow icon="lowbattery"
}
}
```

43
_addons_bindings/bluetooth.bluegiga/readme.md Normal file
View File

@ -0,0 +1,43 @@
---
id: bluetooth.bluegiga
label: Bluetooth BlueGiga Adapter
title: Bluetooth BlueGiga Adapter - Bindings
type: binding
description: "This extension supports Bluetooth access via a BlueGiga (BLED112) USB dongle."
since: 2x
install: manual
---
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
{% include base.html %}
# Bluetooth BlueGiga Adapter
This extension supports Bluetooth access via a BlueGiga (BLED112) USB dongle.
## Supported Things
It defines the following bridge type:
| Bridge Type ID | Description |
|----------------|---------------------------------------------------------------------------|
| bluegiga | A BlueGiga USB dongle using a BLED112 chip |
## Discovery
The adapter cannot be discovered; its serial port must be manually configured.
## Bridge Configuration
The bluegiga bridge requires the configuration parameter `port`, which corresponds to the serial port the dongle is connected to.
Additionally, the parameter `discovery` can be set to true/false. When set to true, any Bluetooth device of which broadcasts are received is added to the Inbox.
## Example
This is how an BlueGiga adapter can be configured textually in a *.things file:
```
Bridge bluetooth:bluegiga:1 [ port="/dev/ttyS0", discovery=false ]
```

2
_addons_bindings/cardio2e1/readme.md
View File

@ -6,7 +6,7 @@ type: binding
description: "The openHAB Cardio2e binding allows connecting to Secant Cardio IIé home automation system installations. Dimming or switching lights on and off, switching devices on and off, activating roller shutters, executing scenarios, managing HVACs or activating system security are only some examples."
source: https://github.com/openhab/openhab1-addons/blob/master/bundles/binding/org.openhab.binding.cardio2e/README.md
since: 1x
install: manual
install: auto
---
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->

2
_addons_bindings/cups1/readme.md
View File

@ -18,7 +18,7 @@ install: manual
The openHAB CUPS binding allows interaction with printers and their print queues via a CUPS server.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/ipp/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/ipp/).
## Prerequisites

9
_addons_bindings/denonmarantz/readme.md
View File

@ -72,27 +72,26 @@ The DenonMarantz AVR supports the following channels (some channels are model sp
| Channel Type ID | Item Type | Description |
|-------------------------|--------------|--------------|
| General
| *General*
| general#power | Switch (RW) | Power on/off
| general#surroundProgram | String (R) | current surround program (e.g. STEREO)
| general#artist | String (R) | artist of current track
| general#album | String (R) | album of current track
| general#track | String (R) | title of current track
| general#command | String (W) | Command to send to the AVR (for use in Rules)
|Now Playing
| Main zone
| *Main zone*
| mainZone#power | Switch (RW) | Main zone power on/off
| mainZone#volume | Dimmer (RW) | Main zone volume
| mainZone#volumeDB | Number (RW) | Main zone volume in dB (-80 offset)
| mainZone#mute | Switch (RW) | Main zone mute
| mainZone#input | String (RW) | Main zone input (e.g. TV, TUNER, ..)
| Zone 2
| *Zone 2*
| zone2#power | Switch (RW) | Zone 2 power on/off
| zone2#volume | Dimmer (RW) | Zone 2 volume
| zone2#volumeDB | Number (RW) | Zone 2 volume in dB (-80 offset)
| zone2#mute | Switch (RW) | Zone 2 mute
| zone2#input | String (RW) | Zone 2 input
| Zone 3
| *Zone 3*
| zone3#power | Switch (RW) | Zone 3 power on/off
| zone3#volume | Dimmer (RW) | Zone 3 volume
| zone3#volumeDB | Number (RW) | Zone 3 volume in dB (-80 offset)

2
_addons_bindings/digitalstrom1/readme.md
View File

@ -28,7 +28,7 @@ The openHAB digitalSTROM binding allows interaction with digitalSTROM devices.
<!-- /MarkdownTOC -->
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/digitalstrom/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/digitalstrom/).
## Prerequisites

2
_addons_bindings/dscalarm1/readme.md
View File

@ -26,7 +26,7 @@ The openHAB DSC Alarm binding provides connectivity to the DSC Alarm panel via a
Additionally there is a DSC Alarm action bundle that can be installed along with the DSC Alarm binding. The action provides the ability to send DSC Alarm commands directly to the DSC Alarm system using rules.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/oh2/dscalarm/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/dscalarm/).
## Binding Configuration

2
_addons_bindings/exec1/readme.md
View File

@ -23,7 +23,7 @@ See [examples](#examples) below.
* The user under which you are running openHAB should have the necessary permissions in order to execute your command lines.
* When using the `ssh` command, you should use private key authorization, since the password cannot be read from the command line.
* There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/exec/readme.html).
* There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/exec/).
## Binding Configuration

2
_addons_bindings/freebox1/readme.md
View File

@ -39,7 +39,7 @@ And act on:
- Windows printer sharing status (from v1.7)
- Reboot
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/freebox/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/freebox/).
## Binding Configuration

2
_addons_bindings/fritzaha1/readme.md
View File

@ -21,7 +21,7 @@ This binding provides access to AVM Home Automation devices, such as the Fritz!D
The binding interfaces with hosts using a choice of two different interfaces, the query script used in the Fritz!OS UI and a webservice designed for interfacing with external applications.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/avmfritz/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/avmfritz/).
## Binding Configuration

2
_addons_bindings/frontiersiliconradio1/readme.md
View File

@ -40,7 +40,7 @@ You can easily check if your IP radio is supported:
4. If the response is similar to `FS_OK 6836164442`, your radio is most likely compatible with this binding
5. If you radio works with this binding, please add it to the list above by [Editing this page](Frontier-Silicon-Radio-Binding/_edit)!
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/fsinternetradio/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/fsinternetradio/).
## Binding Configuration

2
_addons_bindings/gc100ir1/readme.md
View File

@ -19,7 +19,7 @@ This page describes the Global Cache IR binding (1.x), which allows openHAB item
![Global Cache Device](http://www.smarthome.com/media/catalog/product/8/1/8115big.jpg)
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/globalcache/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/globalcache/).
## Binding Configuration

2
_addons_bindings/harmonyhub1/readme.md
View File

@ -17,7 +17,7 @@ install: manual
The Harmony Hub binding is used to enable communication between openHAB and one or more Logitech Harmony Hub devices. The API exposed by the Harmony Hub is relatively limited, but it does allow for reading the current activity as well as setting the activity and sending device commands.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/harmonyhub/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/harmonyhub/).
## Binding Configuration

2
_addons_bindings/homematic1/readme.md
View File

@ -97,7 +97,7 @@ These ports are used by the binding:
The CCU firewall must be configured to 'full access' for the Remote Homematic-Script API.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/homematic/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/homematic/).
## Binding Configuration

2
_addons_bindings/hue1/readme.md
View File

@ -22,7 +22,7 @@ Click the image below for a YouTube video demonstrating setup, configuration and
[![openHAB Hue binding](http://img.youtube.com/vi/Q4_LkXIRBWc/0.jpg)](http://www.youtube.com/watch?v=Q4_LkXIRBWc)
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/hue/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/hue/).
## Prerequisites

2
_addons_bindings/kodi/readme.md
View File

@ -50,7 +50,7 @@ Auto-discovery is enabled by default.
To disable it, you can add the following line to `<openHAB-conf>/services/runtime.cfg`:
```
org.openhab.kodi:enableAutoDiscovery=false
discovery.kodi:background=false
```
## Binding Configuration

6
_addons_bindings/max/readme.md
View File

@ -86,7 +86,8 @@ max.things:
```
Bridge max:bridge:KEQ0565026 [ ipAddress="192.168.3.9", serialNumber="KEQ0565026" ] {
Thing max:thermostat:KEQ0565026:KEQ0565123 [ serialNumber="KEQ0565123" ]
Thing thermostat KEQ0565123 [ serialNumber="KEQ0565123", refreshActualRate=60 ]
Thing shuttercontact NEQ1150510 [ serialNumber="NEQ1150510" ]
}
```
@ -99,6 +100,8 @@ Switch maxBattery "Battery Low" (gMAX) {channel="max:thermostat:KEQ0565026:KEQ06
String maxMode "Thermostat Mode Setting" (gMAX) {channel="max:thermostat:KEQ0565026:KEQ0648949:mode"}
Number maxActual "Actual measured room temperature [%.1f °C]" (gMAX) {channel="max:thermostat:KEQ0565026:KEQ0648949:actual_temp"}
Number maxSetTemp "Thermostat temperature setpoint [%.1f °C]" (gMAX) {channel="max:thermostat:KEQ0565026:KEQ0648949:set_temp"}
Contact maxShuttercontactState "Contact State" (gMAX) {channel="max:shuttercontact:KEQ0565026:NEQ1150510:contact_state"}
Switch maxShuttercontactBattery "Contact Battery Low" <battery> (gMAX) {channel="max:shuttercontact:KEQ0565026:NEQ1150510:battery_low"}
```
demo.sitemap:
@ -112,7 +115,6 @@ sitemap demo label="Main Menu"
Text item=maxActual icon="temperature"
Switch item=maxBattery
}
}
```

2
_addons_bindings/maxcube1/readme.md
View File

@ -17,7 +17,7 @@ install: manual
The MAX!Cube binding allows openHAB to connect to [(ELV) MAX!Cube Lan Gateway](http://www.elv.de/max-cube-lan-gateway.html) installations. The binding allows openHAB to communicate with the MAX! devices through the MAX!Cube Lan Gateway.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/max/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/max/).
## Prerequisites

2
_addons_bindings/maxcul1/readme.md
View File

@ -19,7 +19,7 @@ The aim of this binding is to allow the connection from openHAB to MAX! devices
A lot of credit must go to the [FHEM project](http://fhem.de/fhem.html): without their implementation of the MAX interface with CUL this would be taking a lot longer to implement!
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/max/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/max/).
## Status

2
_addons_bindings/milight1/readme.md
View File

@ -19,7 +19,7 @@ The Milight binding allows openHAB to send commands to multiple Milight bridges.
[![openHAB Milight](http://img.youtube.com/vi/zNe9AkQbfmc/0.jpg)](http://www.youtube.com/watch?v=zNe9AkQbfmc)
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/milight/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/milight/).
## Binding Configuration

2
_addons_bindings/netatmo1/readme.md
View File

@ -20,7 +20,7 @@ The Netatmo binding integrates the Netatmo Personal Weather Station into openHAB
The Netatmo Welcome Camera is also supported; it is a home camera with face recognition. It notifies you when it sees someone it knows, but also when it sees a stranger. See information below to obtain the necessary informations to setup your Netatmo Gear, also see [the Netatmo website](http://www.netatmo.com/) for details on their products.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/netatmo/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/netatmo/).
> The Netatmo Binding (1.x) is considered a legacy binding and does not show up by default as an add-on in the OpenHAB 2 Paper UI. In order for the binding to show up as a add-on, you need to go to Configuration->System and enable both **Access Remote Repositories** and **Include Legacy 1.x Bindings** and save the setting. Once you have done this, you will see both **Netatmo Binding** and **Netatmo Binding (1.x)** in Add-ons, you will want to install **Netatmo Binding**.

2
_addons_bindings/networkhealth1/readme.md
View File

@ -17,7 +17,7 @@ install: legacy
This binding allows openHAB to check whether a device is currently available on the network.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/network/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/network/).
## Binding Configuration

2
_addons_bindings/ntp1/readme.md
View File

@ -17,7 +17,7 @@ install: manual
The [Network Time Protocol](https://en.wikipedia.org/wiki/Network_Time_Protocol) (NTP) Binding is used to query an NTP server you configure for the current time, within tens of milliseconds of accurary. Items in openHAB will receive these updates.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/ntp/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/ntp/).
## Binding Configuration

2
_addons_bindings/onkyo1/readme.md
View File

@ -18,7 +18,7 @@ install: legacy
This binding is compatible with Onkyo AV receivers which support ISCP (Integra Serial Control Protocol) over Ethernet (eISCP) and serial ports.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/onkyo/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/onkyo/).
## Binding Configuration

2
_addons_bindings/opensprinkler1/readme.md
View File

@ -22,7 +22,7 @@ This binding is compatible with with both the [OpenSprinkler](http://opensprinkl
The binding will sync itself with the OpenSprinkler device at intervals. This allows state of the stations to be updated if they are manually controlled from the OpenSprinkler web application directly.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/opensprinkler/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/opensprinkler/).
## Prerequisites

2
_addons_bindings/pioneeravr1/readme.md
View File

@ -20,7 +20,7 @@ This binding allows openHAB to remotely control a Pioneer AV receiver equipped w
Most common commands are supported directly, special commands can be added manually using the "advanced command" mechanism described below.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/pioneeravr/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/pioneeravr/).
## Binding configuration

2
_addons_bindings/pulseaudio1/readme.md
View File

@ -18,7 +18,7 @@ install: manual
This binding allows openHAB to monitor and control pulseaudio servers.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/pulseaudio/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/pulseaudio/).
## Prerequisites

2
_addons_bindings/rfxcom1/readme.md
View File

@ -44,7 +44,7 @@ The RFXCOM binding currently supports the following packet types:
* Transmitter
* Wind
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/rfxcom/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/rfxcom/).
## Table of Contents

2
_addons_bindings/samsungtv1/readme.md
View File

@ -24,7 +24,7 @@ This binding should be compatible with Samsung TV models which support Apple and
* The KEY_POWERON command does not switch the TV on. Tested on Samsung UE40ES5700, maybe other models are working.
* New models (H-Series TV´s like e.g. UEH5570 ) use a different (encrypted) protocol; they are not yet supported by this binding.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/samsungtv/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/samsungtv/).
## Binding Configuration

2
_addons_bindings/sonos1/readme.md
View File

@ -22,7 +22,7 @@ Sonos Players support multi-room audio. Sonos achieves this by grouping Sonos Pl
Sonos Players also support playlists, music streaming services like Spotify, Rapsody, … as well as alarm clocks that you can program to wake up with your favourite music
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/sonos/readme.html). That binding can discover your Sonos players and therefore does not need you to learn UDNs through alternate means.
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/sonos/). That binding can discover your Sonos players and therefore does not need you to learn UDNs through alternate means.
## Limitations

2
_addons_bindings/squeezebox1/readme.md
View File

@ -24,7 +24,7 @@ From the [Wikipedia entry](http://en.wikipedia.org/wiki/Squeezebox_%28network_mu
> In 2006, Slim Devices was acquired by Logitech for $20 million USD. Logitech continued the development of the player until they announced in August 2012 that it would be discontinued. Given the cross-platform nature of the server and software client, some users have ensured the continued use of the platform by utilizing the Raspberry Pi as dedicated Squeezebox device (both client and server).
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/squeezebox/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/squeezebox/).
## Table of Contents

2
_addons_bindings/systeminfo1/readme.md
View File

@ -19,7 +19,7 @@ The System Information binding provides operating system monitoring data, includ
The binding uses the Hyperic SIGAR API to access system information regardless of the underlying platform (Windows, Linux, OS X...).
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/systeminfo/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/systeminfo/).
## Table of Contents

2
_addons_bindings/tellstick1/readme.md
View File

@ -22,7 +22,7 @@ See further information from http://www.telldus.com
The binding supports sensors (temperature and humidity) and devices (switches, dimmers and dimmers without an absolute level).
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/tellstick/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/tellstick/).
## Prerequisites

2
_addons_bindings/tinkerforge1/readme.md
View File

@ -142,7 +142,7 @@ hosts=127.0.0.1:4224:1234 192.168.1.100::secret
In order to bind an item to a device, you need to provide configuration settings. The easiest way
to do so is to add binding information in your item file.
For location of the item file on a Linux based system see [File locations](http://docs.openhab.org/installation/linux.html#file-locations)
For location of the item file on a Linux based system see [File locations](https://www.openhab.org/docs/installation/linux.html#file-locations)
The configuration of the TinkerForge binding item looks like this:

2
_addons_bindings/urtsi1/readme.md
View File

@ -18,7 +18,7 @@ install: legacy
This binding communicates with Somfy URTSI II devices over a serial connection.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/urtsi/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/urtsi/).
## Binding Configuration

2
_addons_bindings/weather1/readme.md
View File

@ -19,7 +19,7 @@ The Weather binding collects current and forecast weather data from different pr
![](https://farm4.staticflickr.com/3946/15407522168_7ea34d51e1_o.png)
There is also a binding specifically openHAB 2 [here](http://docs.openhab.org/addons/bindings/yahooweather/readme.html) for Yahoo! Weather.
There is also a binding specifically openHAB 2 [here](https://www.openhab.org/addons/bindings/yahooweather/) for Yahoo! Weather.
## Table of Contents

2
_addons_bindings/wemo1/readme.md
View File

@ -18,7 +18,7 @@ install: manual
This binding integrates the [Belkin WeMo Family](http://www.belkin.com/us/Products/c/home-automation/). The integration happens either through the WeMo-Link bridge (feature still to come) which acts as an IP gateway to the ZigBee devices, or through Wi-Fi connection to standalone devices.
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/wemo/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/wemo/).
## Binding Configuration

2
_addons_bindings/xbmc1/readme.md
View File

@ -20,7 +20,7 @@ This binding allows openHAB items to receive realtime updates about information
[![openhab binding for xbmc](http://img.youtube.com/vi/N7_5phTVbo0/0.jpg)](http://www.youtube.com/watch?v=N7_5phTVbo0)
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/kodi/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/kodi/).
<!-- MarkdownTOC -->

14
_addons_bindings/yamahareceiver/docs/README.md
View File

@ -164,16 +164,20 @@ http://<Your_Yamaha_ID>/YamahaRemoteControl/UnitDesc.xml
As Yamaha introduces new models there may be variations between XML structure.
In an attempt to improve the addon maintenance and troubleshooting selected model's `desc.xml`' has been collected from community users:
* [HTR-4069](desc_HTR-4069.xml)
* [RX-A2000](desc_RX-A2000.xml)
* [RX-A3070](desc_RX-A3070.xml)
* [RX-S601D](desc_RX-S601D.xml)
* [RX-V479](desc_RX-V479.xml)
* [RX-V583](desc_RX-V583.xml)
* [RX-V675](desc_RX-V675.xml)
* [RX-V3900](desc_RX-V3900.xml)
* [HTR-4069](desc_HTR-4069.xml)
### Key differences between models
Key element | Models | Desc
---------|-----------|----
Volume | RX-V3900 | Volume command uses `Vol` element, while other models have `Volume`. There is no `Feature_Existence` element on system status.
Zone B | HTR-4069 | `Zone_2` feature does not exist, but instead there is `Zone_B` commands under `Main_Zone` with only power, mute and volume control.
| Key element | Models | Desc |
|-------------|----------|-------------------------------------------------------------------------------------------------------------------------------------|
| Volume | RX-V3900 | Volume command uses `Vol` element, while other models have `Volume`. There is no `Feature_Existence` element on system status. |
| Zone B | HTR-4069 | `Zone_2` feature does not exist, but instead there is `Zone_B` commands under `Main_Zone` with only power, mute and volume control. |
| Preset | RX-V3900 | The preset values on this model are strings `A1`, `A2`, `B1`, `B2` instead of numbers. |
| Party Mode | RX-A2000 | Has party mode support, although its XML descriptor does not mention it. |

179
_addons_bindings/yamahareceiver/readme.md
View File

@ -27,11 +27,11 @@ Initially a thing for the main zone will be created. This will trigger a zone de
When using zones feature, to manually add a receiver, use
```
Bridge yamahareceiver:yamahaAV:ReceiverID "Yamaha Receiver Bridge Name" [host="a.b.c.d"] {
Thing zone ZoneID1 "Main Zone Thing Name" @ "location" [zone="Main_Zone", volumeDbMin=-81, volumeDbMax=12]
Thing zone ZoneID2 "Zone 2 Thing Name" @ "location" [zone="Zone_2"]
Thing zone ZoneID3 "Zone 3 Thing Name" @ "location" [zone="Zone_3"]
Thing zone ZoneID4 "Zone 4 Thing Name" @ "location" [zone="Zone_4"]
Bridge yamahareceiver:yamahaAV:ReceiverID "Yamaha Receiver Bridge Name" [host="a.b.c.d", refreshInterval=20] {
Thing zone ZoneID1 "Main Zone Thing Name" @ "location" [zone="Main_Zone", volumeDbMin=-81, volumeDbMax=12]
Thing zone ZoneID2 "Zone 2 Thing Name" @ "location" [zone="Zone_2"]
Thing zone ZoneID3 "Zone 3 Thing Name" @ "location" [zone="Zone_3"]
Thing zone ZoneID4 "Zone 4 Thing Name" @ "location" [zone="Zone_4"]
}
```
@ -40,52 +40,50 @@ select radio stations from a configured menu.
## Features
### Yamaha Receiver Thing
The implemented channels for the AVR thing are:
Channel | openHAB Type | Comment
--------|------|------
`power` | `Switch` | Switches the AVR ON or OFF. Your receiver has to be in network standby for this to work.
| Channel | openHAB Type | Comment |
|---------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `power` | `Switch` | Switches the AVR ON or OFF. Your receiver has to be in network standby for this to work. |
| `party_mode` | `Switch` | Switches the party mode. May not be supported on all models. |
| `party_mode_mute` | `Switch` | Switches the mute ON or OFF when in party mode. Write only (state updates are not available). Applicable only when party mode is on. May not be supported on all models. |
| `party_mode_volume` | `Dimmer` | Increase or decrease volume when in party mode. Write only (state updates are not available). INCREASE / DECREASE commands only. Applicable only when party mode is on. May not be supported on all models. |
The implemented channels for a zone thing are grouped in three groups.
### Yamaha Zone Thing
The implemented channels for a zone thing are grouped in three groups. These are the zones supported: `Main_Zone`, `Zone_2`, `Zone_3`, `Zone_4`.
Zone control channels are:
Channel | openHAB Type | Comment
--------|------|------
`power#zone_channels` | `Switch` | Switches the zone ON or OFF. Your receiver has to be in network standby for this to work.
`mute#zone_channels` | `Switch` | Mute or Unmute the receiver.
`volume#zone_channels` | `Dimmer` | Set's the receivers volume as percentage.
`volumeDB#zone_channels` | `Number` | Set's the receivers volume in dB.
`input#zone_channels` | `String` | Set's the input selection, depends on your receiver's real inputs. Examples: HDMI1, HDMI2, AV4, TUNER, NET RADIO, etc.
`surroundProgram#zone_channels` | `String` | Set's the surround mode. Examples: 2ch Stereo, 7ch Stereo, Hall in Munic, Straight, Surround Decoder.
`dialogueLevel#zone_channels` | `Number` | Set's the receivers dialogue level.
Playback control channels are:
Channel | openHAB Type | Comment
--------|------|------
`preset#playback_channels` | `Number` | Set a preset. Not supported by Spotify.
`playback#playback_channels` | | Set a play mode or get the current play mode.
`playback_station#playback_channels` | `String` | Get the current played station (radio).
`playback_artist#playback_channels` | `String` | Get the current played artist.
`playback_album#playback_channels` | `String` | Get the current played album.
`playback_song#playback_channels` | `String` | Get the current played song.
`playback_song_image_url#playback_channels` | `String` | Get the current played song image URL (currently Spotify input only).
`tuner_band#playback_channels` | `String` | Set the band (FM or DAB) for tuner input when device supports DAB (e.g. RX-S601D).
Navigation control channels are:
Channel | openHAB Type | Comment
--------|------|------
`navigation_menu#navigation_channels` | `String` | Select or display the full or relative path to an item.
`navigation_current_item#navigation_channels` | `Number` | Get the current item of the current menu.
`navigation_total_items#navigation_channels` | `Number` | Get the total count items in the current menu.
`navigation_level#navigation_channels` | `Number` | Get the current menu level.
`navigation_updown#navigation_channels` | | Move the cursor up or down.
`navigation_leftright#navigation_channels` | | Move the cursor to the left or right.
`navigation_select#navigation_channels` | | Select the current item.
`navigation_back#navigation_channels` | | Navigate to the parent menu.
`navigation_backtoroot#navigation_channels` | | Navigate back to the root menu.
| Channel | openHAB Type | Comment |
|-----------------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `zone_channels#power` | `Switch` | Switches the zone ON or OFF. Your receiver has to be in network standby for this to work. |
| `zone_channels#mute` | `Switch` | Mute or Unmute the receiver. |
| `zone_channels#volume` | `Dimmer` | Set's the receivers volume as percentage. |
| `zone_channels#volumeDB` | `Number` | Set's the receivers volume in dB. |
| `zone_channels#input` | `String` | Set's the input selection, depends on your receiver's real inputs. Examples: HDMI1, HDMI2, AV4, TUNER, NET RADIO, etc. |
| `zone_channels#surroundProgram` | `String` | Set's the surround mode. Examples: `2ch Stereo`, `7ch Stereo`, `Hall in Munic`, `Straight`, `Surround Decoder`. |
| `zone_channels#scene` | `String` | Sets the scene. Examples: `Scene 1`, `Scene 2`, `Scene 3`, `Scene 4`. Write only (state updates are not available). May not be supported on all models (e.g. RX-V3900). |
| `zone_channels#dialogueLevel` | `Number` | Set's the receivers dialogue level. May not be supported on all models. |
| `playback_channels#preset` | `Number` | Set a preset. Not supported by `Spotify` input. For `NET RADIO` input there is no way to get current preset (tested on RX-S601D, RX-V3900), so the preset is write only. For RX-V3900 the presets are alphanumeric `A1`,`A2`,`B1`,`B2` thus you need to use numbers grater than 100 that represent these presets as follows: 101, 102, 201, 202. |
| `playback_channels#playback` | `String` | Set a play mode or get the current play mode. Values supported: `Previous`, `Play`, `Pause`, `Stop`, `Next`. Applies for inputs which support playback (`Spotify`, `SERVER`, `NET RADIO`, `Bluetooth`). Note that some values may not be supported on certain input type and AVR model combination. For `Spotify` and `Bluetooth` all values work, but for `NET RADIO` input only `Play` and `Stop` are supported (tested on RX-S601D). |
| `playback_channels#playback_station` | `String` | Get the current played station (radio). Applies to `TUNER` and `NET RADIO` inputs only. |
| `playback_channels#playback_artist` | `String` | Get the current played artist. |
| `playback_channels#playback_album` | `String` | Get the current played album. |
| `playback_channels#playback_song` | `String` | Get the current played song. |
| `playback_channels#playback_song_image_url` | `String` | Get the current played song image URL. Applies to `Spotify` and `NET RADIO` inputs only. |
| `playback_channels#tuner_band` | `String` | Set the band (FM or DAB) for tuner input when device supports DAB+ (e.g. RX-S601D). Values supported: `FM`, `DAB`. Applies to `TUNER` input only. |
| `navigation_channels#navigation_menu` | `String` | Select or display the full or relative path to an item. |
| `navigation_channels#navigation_current_item` | `Number` | Get the current item of the current menu. |
| `navigation_channels#navigation_total_items` | `Number` | Get the total count items in the current menu. |
| `navigation_channels#navigation_level` | `Number` | Get the current menu level. |
| `navigation_channels#navigation_updown` | | Move the cursor up or down. |
| `navigation_channels#navigation_leftright` | | Move the cursor to the left or right. |
| `navigation_channels#navigation_select` | | Select the current item. |
| `navigation_channels#navigation_back` | | Navigate to the parent menu. |
| `navigation_channels#navigation_backtoroot` | | Navigate back to the root menu. |
Navigation is not supported by Spotify input.
@ -100,39 +98,50 @@ Link the items to the channels of your preferred zone (here `Main_Zone`) in Pape
Items:
```
Switch Yamaha_Power "Power [%s]" <switch>
Dimmer Yamaha_Volume "Volume [%.1f %%]" <soundvolume>
Switch Yamaha_Mute "Mute [%s]" <soundvolume_mute>
Number Yamaha_Dialogue_Level "Dialogue Level [%d]" <soundvolume>
String Yamaha_Input "Input [%s]" <video>
String Yamaha_Surround "Surround [%s]" <video>
Switch Yamaha_Power "Power [%s]" <switch>
Dimmer Yamaha_Volume "Volume [%.1f %%]" <soundvolume>
Switch Yamaha_Mute "Mute [%s]" <soundvolume_mute>
String Yamaha_Input "Input [%s]" <video>
String Yamaha_Surround "Surround [%s]" <video>
String Yamaha_Scene "Scene []" <video>
Number Yamaha_Dialogue_Level "Dialogue Level [%d]" <soundvolume>
```
##### For manually linking
Replace the UPNP UDN (here: `9ab0c000_f668_11de_9976_00a0ded41bb7`) with the real UDN provided by your UPNP discovery.
Replace the UPNP UDN (here: `96a40ba9`) with the real UDN provided by your UPNP discovery.
Also replace the zone name with your preferred zone (here `Main_Zone`).
Items:
```
Switch Yamaha_Power "Power [%s]" <switch> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:zone_channels#power" }
Dimmer Yamaha_Volume "Volume [%.1f %%]" <soundvolume> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:zone_channels#volume" }
Switch Yamaha_Mute "Mute [%s]" <soundvolume_mute> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:zone_channels#mute" }
String Yamaha_Input "Input [%s]" <video> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:zone_channels#input" }
String Yamaha_Surround "Surround [%s]" <video> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:zone_channels#surroundProgram" }
Switch Yamaha_Dialogue_Level "Dialogue Level [%d]" <soundvolume> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:zone_channels#dialogueLevel" }
Switch Yamaha_Power "Power [%s]" <switch> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:zone_channels#power" }
Dimmer Yamaha_Volume "Volume [%.1f %%]" <soundvolume> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:zone_channels#volume" }
Switch Yamaha_Mute "Mute [%s]" <soundvolume_mute> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:zone_channels#mute" }
String Yamaha_Input "Input [%s]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:zone_channels#input" }
String Yamaha_Surround "Surround [%s]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:zone_channels#surroundProgram" }
String Yamaha_Scene "Scene []" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:zone_channels#scene" }
Switch Yamaha_Dialogue_Level "Dialogue Level [%d]" <soundvolume> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:zone_channels#dialogueLevel" }
Switch Yamaha_PartyMode "Party mode [%s]" <switch> { channel="yamahareceiver:yamahaAV:96a40ba9:party_mode" }
Switch Yamaha_PartyModeMute "Party mode mute [%s]" <soundvolume_mute> { channel="yamahareceiver:yamahaAV:96a40ba9:party_mode_mute" }
Dimmer Yamaha_PartyModeVolume "Party mode volume []" <soundvolume> { channel="yamahareceiver:yamahaAV:96a40ba9:party_mode_volume" }
```
Sitemap:
```
Switch item=Yamaha_Power
Switch item=Yamaha_Mute
Slider item=Yamaha_Volume
Selection item=Yamaha_Input mappings=[HDMI1="Kodi",HDMI2="PC",AUDIO1="TV",TUNER="Tuner",Spotify="Spotify",Bluetooth="Bluetooth","NET RADIO"="NetRadio",SERVER="Server",Straight="Straight"]
Selection item=Yamaha_Surround mappings=["2ch Stereo"="2ch Stereo","5ch Stereo"="5ch Stereo","Chamber"="Chamber","Sci-Fi"="Sci-Fi","Adventure"="Adventure"]
Setpoint item=Yamaha_Dialogue_Level minValue=0 maxValue=2 step=1
Switch item=Yamaha_Power
Switch item=Yamaha_Mute
Slider item=Yamaha_Volume
Selection item=Yamaha_Input mappings=[HDMI1="Kodi",HDMI2="PC",AUDIO1="TV",TUNER="Tuner",Spotify="Spotify",Bluetooth="Bluetooth","NET RADIO"="NetRadio",SERVER="Server",Straight="Straight"]
Selection item=Yamaha_Surround mappings=["2ch Stereo"="2ch Stereo","5ch Stereo"="5ch Stereo","Chamber"="Chamber","Sci-Fi"="Sci-Fi","Adventure"="Adventure"]
Switch item=Yamaha_Scene mappings=["Scene 1"="Kodi","Scene 2"="TV","Scene 3"="NET","Scene 4"="Radio"]
Setpoint item=Yamaha_Dialogue_Level minValue=0 maxValue=2 step=1
Switch item=Yamaha_PartyMode
Switch item=Yamaha_PartyModeMute
Switch item=Yamaha_PartyModeVolume mappings=[DECREASE="-", INCREASE="+"]
```
Note: Some input values for `Yamaha_Input` might not be supported on your model. Make sure to adjust these values.
@ -142,23 +151,23 @@ Note: Some input values for `Yamaha_Input` might not be supported on your model.
Items:
```
String Yamaha_Playback "[]" <video> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:playback_channels#playback" }
String Yamaha_Playback_Station "Station [%s]" <video> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:playback_channels#playback_station" }
String Yamaha_Playback_Artist "Artist [%s]" <video> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:playback_channels#playback_artist" }
String Yamaha_Playback_Album "Album [%s]" <video> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:playback_channels#playback_album" }
String Yamaha_Playback_Song "Song [%s]" <video> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:playback_channels#playback_song" }
String Yamaha_Playback_Song_Image "[]" <videp> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:playback_channels#playback_song_image_url" }
String Yamaha_Playback "[]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:playback_channels#playback" }
String Yamaha_Playback_Station "Station [%s]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:playback_channels#playback_station" }
String Yamaha_Playback_Artist "Artist [%s]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:playback_channels#playback_artist" }
String Yamaha_Playback_Album "Album [%s]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:playback_channels#playback_album" }
String Yamaha_Playback_Song "Song [%s]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:playback_channels#playback_song" }
String Yamaha_Playback_Song_Image "[]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:playback_channels#playback_song_image_url" }
```
Sitemap:
```
Switch item=Yamaha_Playback mappings=["Previous"="⏮", "Play"="►", "Pause"="⏸", "Stop"="⏹", "Next"="⏭"] visibility=[Yamaha_Input=="Spotify", Yamaha_Input=="Bluetooth"]
Text item=Yamaha_Playback_Station visibility=[Yamaha_Input=="TUNER"]
Switch item=Yamaha_Playback mappings=["Previous"="⏮", "Play"="►", "Pause"="⏸", "Stop"="⏹", "Next"="⏭"] visibility=[Yamaha_Input=="Spotify", Yamaha_Input=="NET RADIO", Yamaha_Input=="Bluetooth"]
Text item=Yamaha_Playback_Station visibility=[Yamaha_Input=="TUNER", Yamaha_Input=="NET RADIO"]
Text item=Yamaha_Playback_Artist
Text item=Yamaha_Playback_Album
Text item=Yamaha_Playback_Song
Image item=Yamaha_Playback_Song_Image visibility=[Yamaha_Input=="Spotify"]
Image item=Yamaha_Playback_Song_Image visibility=[Yamaha_Input=="Spotify", Yamaha_Input=="NET RADIO", Yamaha_Input=="Bluetooth"]
```
Note the `visiblility` rules - you may need to adjust to your particular AVR model supported inputs and features.
@ -168,8 +177,8 @@ Note the `visiblility` rules - you may need to adjust to your particular AVR mod
Items:
```
Number Yamaha_Preset "Preset [%d]" <video> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:playback_channels#preset"}
String Yamaha_Tuner_Band "Band [%s]" <video> { channel="yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0ded41bb7:Main_Zone:playback_channels#tuner_band" }
Number Yamaha_Preset "Preset [%d]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:playback_channels#preset"}
String Yamaha_Tuner_Band "Band [%s]" <video> { channel="yamahareceiver:zone:96a40ba9:Main_Zone:playback_channels#tuner_band" }
String Yamaha_Input_Ex
```
@ -182,27 +191,23 @@ when
Item Yamaha_Input changed or
Item Yamaha_Tuner_Band changed
then
var input = Yamaha_Input.state
if (input !== NULL) {
if (Yamaha_Input.state == "TUNER" && Yamaha_Tuner_Band.state !== NULL) {
input = "TUNER_" + Yamaha_Tuner_Band.state
}
} else {
input = ""
var String input = "" + Yamaha_Input.state
if (Yamaha_Input.state == "TUNER" && Yamaha_Tuner_Band.state !== NULL) {
input = input + "_" + Yamaha_Tuner_Band.state
}
Yamaha_Input_Ex.postUpdate(new StringType(input))
Yamaha_Input_Ex.postUpdate(input)
end
```
When the input is `TUNER` the `Yamaha_Input_Ex` item will have a value of either `TUNER_FM` or `TUNER_DAB` depending on the chosen tuner band,
otherwise it will be same as input (`Yamaha_Input`).
otherwise it will be the same as input (`Yamaha_Input`).
Sitemap:
```
Selection item=Yamaha_Tuner_Band mappings=[FM="FM",DAB="DAB+"] visibility=[Yamaha_Input=="TUNER"]
Selection item=Yamaha_Preset mappings=[2="Radio Krakow",3="PR Trojka",5="RadioZet",8="Radio Chillizet",12="RMF Classic",13="RMF MAXXX"] visibility=[Yamaha_Input_Ex=="TUNER_FM"]
Selection item=Yamaha_Preset mappings=[1="FM-1",2="FM-2",3="FM-3"] visibility=[Yamaha_Input_Ex=="TUNER_DAB"]
Selection item=Yamaha_Tuner_Band mappings=[FM="FM",DAB="DAB+"] visibility=[Yamaha_Input=="TUNER"]
Selection item=Yamaha_Preset mappings=[2="Radio Krakow",3="PR Trojka",5="RadioZet",8="Radio Chillizet",12="RMF Classic",13="RMF MAXXX"] visibility=[Yamaha_Input_Ex=="TUNER_FM"]
Selection item=Yamaha_Preset mappings=[1="FM-1",2="FM-2",3="FM-3"] visibility=[Yamaha_Input_Ex=="TUNER_DAB"]
```
Notice how we have two preset mappings that each is meant for FM and DAB+ bands respectively. This enables to have different channel names per band.

2
_addons_bindings/yamahareceiver1/readme.md
View File

@ -49,7 +49,7 @@ Tested Receivers:
Please add your own successfully tested receiver to this list!
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/yamahareceiver/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/yamahareceiver/).
## Binding Configuration

2
_addons_bindings/zwave1/readme.md
View File

@ -31,7 +31,7 @@ The openHAB Z-Wave binding allows you to connect to your Z-Wave wireless mesh ne
<!-- /MarkdownTOC -->
There is also a binding specifically for openHAB 2 [here](http://docs.openhab.org/addons/bindings/zwave/readme.html).
There is also a binding specifically for openHAB 2 [here](https://www.openhab.org/addons/bindings/zwave/).
## Prerequisites

51
_addons_voices/picotts/readme.md Normal file
View File

@ -0,0 +1,51 @@
---
id: picotts
label: Pico Text-to-Speech
title: Pico Text-to-Speech - Voices
type: voice
description: "The Pico Text-to-Speech (TTS) service uses the TTS binary from SVOX for producing spoken text."
since: 2x
install: auto
---
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
{% include base.html %}
# Pico Text-to-Speech
## Overview
The Pico Text-to-Speech (TTS) service uses the TTS binary from SVOX for producing spoken text.
You manually need to install the pico2wave binary in order for this service to work correctly. You can,
e.g., install it with apt-get on an Ubuntu system:
```
sudo apt-get install libttspico-utils
```
In Arch Linux the pico2wave binaries are available in an Arch User repository (AUR) under
https://aur.archlinux.org/packages/svox-pico-bin/
## Configuration
There is no need to configure anything for this service.
## Voices
The following list are the only supported languages (as these are the languages supported by
pico2wave, see also [the documentation of the debian package](https://packages.debian.org/de/wheezy/libttspico-utils)):
```
German (de-DE)
English, US (en-US)
English, GB (en-GB)
Spanish (es-ES)
French (fr-FR)
Italian (it-IT)
```
## Supported Audio Formats
The Pico service produces audio streams using WAV containers and PCM (signed) codec with 16bit depth.