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

2.4-patch
openhab-bot 2018-11-12 03:47:32 +00:00
parent 19a8091e34
commit dfa88744c7
3 changed files with 48 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_addons_bindings/pilight1/readme.md
View File

@ -19,7 +19,7 @@ The pilight binding allows openHAB to communicate with a [pilight](http://www.pi
> pilight is a free open source full fledge domotica solution that runs on a Raspberry Pi, HummingBoard, BananaPi, Radxa, but also on *BSD and various linuxes (tested on Arch, Ubuntu and Debian). It's open source and freely available for anyone. pilight works with a great deal of devices and is frequency independent. Therefor, it can control devices working at 315Mhz, 433Mhz, 868Mhz etc. Support for these devices are dependent on community, because we as developers don't own them all.
pilight is a cheap way to control 'Click On Click Off' devices. It started as an application for the Raspberry Pi (using the GPIO interface) but it's also possible now to connect it to any other PC using an Arduino Nano. You will need a cheap 433Mhz transceiver in both cases. See the [Pilight manual](http://manual.pilight.org/en/electronics-wiring) for more information.
pilight is a cheap way to control 'Click On Click Off' devices. It started as an application for the Raspberry Pi (using the GPIO interface) but it's also possible now to connect it to any other PC using an Arduino Nano. You will need a cheap 433Mhz transceiver in both cases. See the [Pilight manual](https://manual.pilight.org/electronics/wiring.html) for more information.
The binding supports Switch, Dimmer, Contact, String, and Number items.

75
_addons_bindings/tellstick/readme.md
View File

@ -40,12 +40,10 @@ Additionally the binding have two types of bridge things which correspond to ava
* *Telldus Core Bridge* - Oldest API, used by USB devices. `telldus-core`
* *Telldus Live Bridge* - Telldus Cloud service, all devices with online access. `telldus-live`
The attentive reader discovers that there is many missing sensor types; `UV`, `Luminance`, `Dew point`, `Barometic pressure` `Rainrate`, `Raintotal`, `Winddirection`, `Windaverage` and `Windgust` which is supported by the Tellstick devices.
Support have not been implemented on the openhab side yet, contributions are welcome.
***Switchbased sensors workaround*** <br>
* Some 433MHz magnetic & PIR sensors, for example, magnetic door sensors, are detected as regular `switch` Things instead of type `contact`. There is technically no way of distinguish them apart from regulur `switch` Things.
For using them as sensors only (not paired to a lamp) please consult the workaround in the channel section.
***Switchbased sensors workaround***
* Some 433MHz magnetic & PIR sensors, for example, magnetic door sensors, are detected as regular `switch` Things instead of type `contact`. There is technically no way of distinguish them apart from regulur `switch` Things. For using them as sensors only (not paired to a lamp) please consult the workaround in the channel section.
## Discovery
@ -73,7 +71,7 @@ Use the option `repeat` for that. Default resend count is 2.
### Bridges
Depending on your tellstick device type there is different ways of using this binding.
The binding implements two different API:
The binding implements two different API:
**1)** *Telldus Core* which is a local only interface supported by USB based device. <br>
**2)** *Telldus Live* which is a REST based cloud service maintained by Telldus. <br>
@ -82,15 +80,14 @@ The binding implements two different API:
Depending on your Tellstick model, different bridge-types are available:
<table>
<tr><td><b>Model</b></td> <td><b>Telldus Core</b></td> <td><b>Telldus Live</b></td> <td>Local REST API</td> <td><b>Verified working with openHAB</b></td></tr>
<tr><td>Tellstick Basic</td><td>X</td><td>X</td><td></td><td></td></tr>
<tr><td>Tellstick Duo</td><td>X</td><td>X</td><td></td><td>X</td></tr>
<tr><td>Tellstick Net v.1</td><td></td><td>X</td><td></td><td></td></tr>
<tr><td>Tellstick Net v.2</td><td></td><td>X</td><td>X</td><td></td></tr>
<tr><td>Tellstick ZNet Lite v.1</td><td></td><td>X</td><td>X</td><td>X</td></tr>
<tr><td>Tellstick ZNet Lite v.2</td><td></td><td>X</td><td>X</td><td></td></tr>
</table>
| Model | Telldus Core | Telldus Live | Local REST API | Verified working with openHAB |
|-------------------------|:------------:|:------------:|:--------------:|:-----------------------------:|
| Tellstick Basic | X | X | | X |
| Tellstick Duo | X | X | | X |
| Tellstick Net v.1 | | X | | |
| Tellstick Net v.2 | | X | X | |
| Tellstick ZNet Lite v.1 | | X | X | X |
| Tellstick ZNet Lite v.2 | | X | X | |
#### Telldus Core Bridge
@ -133,28 +130,48 @@ Optional:
Actuators (dimmer/switch) support the following channels:
<table>
<tr><td><b>Channel Type ID</b></td> <td><b>Item Type</b></td> <td><b>Description</b></td> </tr>
<tr><td>dimmer</td><td>Number</td><td>This channel indicates the current dim level</td></tr>
<tr><td>state</td><td>Switch</td><td>This channel indicates whether a device is turned on or off.</td></tr>
<tr><td>timestamp</td><td>DateTime</td><td>This channel reports the last time this device state changed.</td></tr>
</table>
| Channel Type ID | Item Type | Description |
|-----------------|-----------|---------------------------------------------------------------|
| dimmer | Number | This channel indicates the current dim level |
| state | Switch | This channel indicates whether a device is turned on or off. |
| timestamp | DateTime | This channel reports the last time this device state changed. |
Sensors (sensor) support the following channels:
<table>
<tr><td><b>Channel Type ID</b></td> <td><b>Item Type</b></td> <td><b>Description</b></td> </tr>
<tr><td>humidity</td><td>Number</td><td>This channel reports the current humidity in percentage.</td></tr>
<tr><td>temperature</td><td>Number</td><td>This channel reports the current temperature in celsius.</td></tr>
<tr><td>timestamp</td><td>DateTime</td><td> This channel reports the last time this sensor was updates.</td></tr>
</table>
| Channel Type ID | Item Type | Description |
|-----------------|-----------|-------------------------------------------------------------|
| humidity | Number | This channel reports the current humidity in percentage. |
| temperature | Number | This channel reports the current temperature in celsius. |
| timestamp | DateTime | This channel reports the last time this sensor was updates. |
PowerSensors ([powersensor]) support the following channels:
| Channel Type ID | Item Type | Description |
|-----------------|-----------|-------------------------------------------------------------|
| watt | Number | This channel reports the current watt. |
| ampere | Number | This channel reports the current ampere. |
| timestamp | DateTime | This channel reports the last time this sensor was updates. |
WindSensors ([windsensor]) support the following channels:
| Channel Type ID | Item Type | Description |
|-----------------|-----------|------------------------------|
| windgust | Number | This current peak wind gust. |
| winddirection | Number | The current wind direction. |
| windaverage | DateTime | The current wind avarage. |
RainSensors ([rainsensor]) support the following channels:
| Channel Type ID | Item Type | Description |
|-----------------|-----------|----------------------------|
| rainrate | Number | This current rate of rain. |
| raintotal | Number | The total rain. |
### Switchbased sensor workaround
All switchbased sensors are binary and the goal is to represent them as a `contact` item in openhab. Eg. a door is open or closed and can't be altered by sending a radio signal.
All switchbased sensors are binary and the goal is to represent them as a `contact` item in openHAB. Eg. a door is open or closed and can't be altered by sending a radio signal.
To achive that we will create a proxy item which is updated by a rule.
First create another proxy item for every sensor:
```

1
_addons_voices/googletts/readme.md
View File

@ -60,6 +60,7 @@ Using your favourite configuration UI (e.g. PaperUI) edit **Services/Voice/Googl
* **Pitch** - The pitch of selected voice, up to 20 semitones
* **Volume Gain** - The volume of the output between 16dB and -96dB
* **Speaking Rate** - The speaking rate can be 4x faster or slower than the normal rate
* **Purge Cache** - Purges the cache e.g. after testing different voice configuration parameters. When enabled the cache is purged once. Make sure to disable this setting again so the cache is maintained after restarts.
## Voice Configuration