parent
b38a50448d
commit
1d1550d865
|
@ -142,7 +142,7 @@ oh1,binding,wago,false,WAGO,"The WAGO Binding provides an interface to Ethernet-
|
|||
oh1,binding,weather,false,Weather,"The Weather binding collects current and forecast weather data from different providers with a free weather API. You can also display weather data with highly customizable html layouts and icons."
|
||||
oh1,binding,wemo,true,Wemo,"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."
|
||||
oh1,binding,withings,false,Withings,"The Withings binding allows openHAB to synchronize data from the official Withings API to items. The following body measure types are supported: diastolic blood pressure, fat free mass, fat mass weight, fat ratio, heart pulse, height, systolic blood pressure, weight."
|
||||
oh1,binding,wol,false,Wake-on-LAN,"For Windows computers not in a domain, the firewall must be configured properly (allow remote shutdowns) and the DWORD-Regkey `LocalAccountTokenFilterPolicy` in `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System` must be set to 1."
|
||||
oh1,binding,wol,false,Wake-on-LAN,"The Wake-on-LAN binding allows you to turn on or wake up a computer by sending it a [network message](https://en.wikipedia.org/wiki/Wake-on-LAN)."
|
||||
oh1,binding,xbmc,true,XBMC binding (for KODI) (1.x),"This binding allows openHAB items to receive realtime updates about information like player state and running media from one or more instances of KODI (formerly known as XBMC)."
|
||||
oh1,binding,xpl,false,xPL,"The xPL binding grabs xPL message values in items and sends xPL commands."
|
||||
oh1,binding,yamahareceiver,true,Yamaha Receiver (1.x),"This binding connects openHAB with various Yamaha Receivers."
|
||||
|
@ -179,7 +179,7 @@ oh2,binding,homematic,true,Homematic,"This is the binding for the [eQ-3 Homemati
|
|||
oh2,binding,ipp,false,IPP,"This binding integrates printers, which implement the Internet Printing protocol (IPP). This is the successor of the CUPS binding."
|
||||
oh2,binding,keba,true,Keba,"This binding integrates the [Keba KeContact EV Charging Stations](http://www.keba.com)."
|
||||
oh2,binding,kodi,true,Kodi,"[Kodi](https://kodi.tv) (formerly known as XBMC) is an free and open source (GPL) software media center for playing videos, music, pictures, games, and more."
|
||||
oh2,binding,kostalinverter,true,Kostal inverter,"Scrapes the web interface of the inverter for the metrics of the supported channels below."
|
||||
oh2,binding,kostalinverter,true,Kostal Inverter,"Scrapes the web interface of the inverter for the metrics of the supported channels below."
|
||||
oh2,binding,lgtvserial,false,LG TV control using serial protocol,"This binding can send some commands typically used by LG LCD TVs (and some used by projectors)."
|
||||
oh2,binding,lutron,true,Lutron,"This binding integrates with [Lutron](http://www.lutron.com) light control systems."
|
||||
oh2,binding,max,true,MAX!,"This is the binding for the [eQ-3 MAX! Home Solution](http://www.eq-3.de/)."
|
||||
|
@ -266,5 +266,5 @@ oh2,iconset,classic,false,Classic Icon Set,"This is a modernized version of the
|
|||
oh2,ui,basic,false,Basic UI,"The Basic UI is a web interface based on Material Design Lite from Google."
|
||||
oh2,ui,classic,false,Classic UI,"The Classic UI is the original web user interface of openHAB 1 and thus is the most stable and widely used UI as of today."
|
||||
oh2,ui,paper,false,Paper UI,"The Paper UI is an HTML5 web application. The Paper UI implements Google's Material Design and is responsive, so that it smoothly renders on different screen sizes. All modern browsers (Safari, Chrome, Firefox) besides the Internet Explorer are supported in their newest version. The Internet Explorer is mainly lacking support for SSE."
|
||||
oh2,ui,habmin,false,habmin,""
|
||||
oh2,ui,habmin,false,HABmin,"HABmin is a modern, professional and portable user interface for openHAB, providing both user and administrative functions (e.g., sitemaps for users, and configuration utilities to aid setup)."
|
||||
oh2,ui,habpanel,false,Configuration,"Unlike Basic UI and other interfaces, HABPanel doesn't use pre-configured sitemaps."
|
||||
|
|
|
|
@ -1,7 +1,11 @@
|
|||
---
|
||||
layout: documentation
|
||||
title: Air Quality - Bindings
|
||||
source: external
|
||||
---
|
||||
|
||||
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
|
||||
|
||||
{% include base.html %}
|
||||
|
||||
# Air Quality Binding
|
||||
|
|
|
@ -92,6 +92,7 @@ An complementary altitude (optional) configuration item can also be specified to
|
|||
* `azimuth, elevation` (Number)
|
||||
|
||||
### Trigger Channels
|
||||
|
||||
* **thing** `sun`
|
||||
* **group** `rise, set, noon, night, morningNight, astroDawn, nauticDawn, civilDawn, astroDusk, nauticDusk, civilDusk, eveningNight, daylight`
|
||||
* **event** `START, END`
|
||||
|
@ -111,10 +112,22 @@ An complementary altitude (optional) configuration item can also be specified to
|
|||
* **group** `apogee`
|
||||
* **event**: `APOGEE`
|
||||
|
||||
**Offsets:** For each event group you can optionally configure an offset in minutes.
|
||||
The offset must be configured in the channel properties for the corresponding thing.
|
||||
### Channel config
|
||||
|
||||
**Offsets:** For each event group you can optionally configure an `offset` in minutes. The `offset` must be configured in the channel properties for the corresponding thing.
|
||||
|
||||
The minimum allowed offset is -1440 and the maximum allowed offset is 1440.
|
||||
|
||||
**Earliest/Latest:** For each trigger channel and `start`, `end` datetime value, you can optionally configure the `earliest` and `latest` time of the day.
|
||||
|
||||
e.g `sun#rise earliest=18:00, latest=20:00`
|
||||
|
||||
sunrise is 17:40, but `earliest` is set to 18:00 so the event/datetime value is moved to 18:00.
|
||||
|
||||
OR
|
||||
|
||||
sunrise is 22:10 but `latest` is set to 20:00 so the event/datetime value is moved 20:00.
|
||||
|
||||
## Full Example
|
||||
|
||||
Things:
|
||||
|
|
|
@ -9,11 +9,13 @@ source: external
|
|||
{% include base.html %}
|
||||
|
||||
# Hunter Douglas PowerView Binding
|
||||
|
||||
This is an openHAB binding for the [Hunter Douglas PowerView Motorized Shades](http://www.hunterdouglas.com/operating-systems/powerview-motorization/support) via the PowerView Hub.
|
||||
|
||||
PowerView shades have motorization control for their vertical position, as well as vane controls on the shade's slats. Make sure your Shades are visible in the dedicated PowerView app before attempting discovery. This binding also supports Scenes that are defined via the PowerView app. This helps to work around a limitation of the Hub - commands are executed serially with a several second delay between executions. By using a Scene to control multiple shades at once, the shades will all begin moving at the same time.
|
||||
|
||||
## Supported Things
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td><b>Thing</b></td>
|
||||
|
@ -33,10 +35,13 @@ PowerView shades have motorization control for their vertical position, as well
|
|||
</table>
|
||||
|
||||
## Discovery
|
||||
|
||||
The PowerView Hub is discovered via a NetBios query. This is the same method used by the dedicated PowerView app. After the Hub is added, Shades and Scenes will be discovered by querying the Hub.
|
||||
|
||||
## Thing Configuration
|
||||
|
||||
PowerView things should be configured via discovery - it would be difficult to configure manually as the IDs of the shades and scenes are not exposed via the dedicated app. However, the configuration parameters are described below:
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td><b>Thing</b></td>
|
||||
|
@ -62,7 +67,9 @@ PowerView things should be configured via discovery - it would be difficult to c
|
|||
</table>
|
||||
|
||||
## Channels
|
||||
|
||||
### PowerView Shade
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td><b>Channel</b></td>
|
||||
|
@ -88,7 +95,9 @@ PowerView things should be configured via discovery - it would be difficult to c
|
|||
|
||||
|
||||
### PowerView Scene
|
||||
|
||||
Scenes channels are added to the Hub as they are discovered.
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td><b>Channel</b></td>
|
||||
|
|
|
@ -72,7 +72,7 @@ The Kodi thing supports the following channels:
|
|||
| mute | Switch | Mute/unmute your playback |
|
||||
| volume | Dimmer | Read or control the volume of your playback |
|
||||
| control | Player | Control the Kodi player, e.g. `PLAY`, `PAUSE`, `NEXT`, `PREVIOUS`, `FASTFORWARD`, `REWIND` |
|
||||
| stop | Switch | Stops the Kodi player |
|
||||
| stop | Switch | Write `ON` to this channel: Stops the Kodi player. If this channel is `ON`, the player is stopped, otherwise kodi is in another state (see control channel) |
|
||||
| title | String | Title of the currently played song/movie/tv episode |
|
||||
| showtitle | String | Title of the currently played tv-show; empty for other types |
|
||||
| album | String | Album name of the currently played song |
|
||||
|
@ -113,20 +113,20 @@ demo.sitemap
|
|||
sitemap demo label="myKodi"
|
||||
{
|
||||
Frame label="myKodi" {
|
||||
Switch item=HTPC_mute
|
||||
Slider item=HTPC_volume
|
||||
Selection item=HTPC_control mappings=[PLAY='Play', PAUSE='Pause', NEXT='Next', PREVIOUSE'Previous', FFWARD='Fastforward', REWIND='Rewind']
|
||||
Switch item=HTPC_stop
|
||||
Text item=HTPC_title
|
||||
Text item=HTPC_showtitle
|
||||
Text item=HTPC_album
|
||||
Text item=HTPC_artist
|
||||
Text item=HTPC_playuri
|
||||
Text item=HTPC_notification
|
||||
Text item=HTPC_input
|
||||
Text item=HTPC_inputtext
|
||||
Text item=HTPC_systemcommand
|
||||
Text item=HTPC_mediatype
|
||||
Switch item=myKodi_mute
|
||||
Slider item=myKodi_volume
|
||||
Selection item=myKodi_control mappings=[PLAY='Play', PAUSE='Pause', NEXT='Next', PREVIOUSE'Previous', FFWARD='Fastforward', REWIND='Rewind']
|
||||
Switch item=myKodi_stop
|
||||
Text item=myKodi_title
|
||||
Text item=myKodi_showtitle
|
||||
Text item=myKodi_album
|
||||
Text item=myKodi_artist
|
||||
Text item=myKodi_playuri
|
||||
Text item=myKodi_notification
|
||||
Text item=myKodi_input
|
||||
Text item=myKodi_inputtext
|
||||
Selection item=myKodi_systemcommand mappings=[Shutdown='Herunterfahren', Suspend='Bereitschaft', Reboot='Neustart']
|
||||
Text item=myKodi_mediatype
|
||||
}
|
||||
}
|
||||
```
|
||||
|
|
|
@ -1,10 +1,14 @@
|
|||
---
|
||||
layout: documentation
|
||||
title: Kostal Inverter - Bindings
|
||||
source: external
|
||||
---
|
||||
|
||||
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
|
||||
|
||||
{% include base.html %}
|
||||
|
||||
# Kostal inverter Binding
|
||||
# Kostal Inverter Binding
|
||||
|
||||
Scrapes the web interface of the inverter for the metrics of the supported channels below.
|
||||
|
||||
|
|
|
@ -1,7 +1,11 @@
|
|||
---
|
||||
layout: documentation
|
||||
title: Miele@home - Bindings
|
||||
source: external
|
||||
---
|
||||
|
||||
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
|
||||
|
||||
{% include base.html %}
|
||||
|
||||
# Miele@home Binding
|
||||
|
|
|
@ -9,14 +9,17 @@ source: external
|
|||
{% include base.html %}
|
||||
|
||||
# Milight Binding
|
||||
|
||||
The openHAB2 Milight binding allows to send commands to multiple Milight bridges.
|
||||
|
||||
[](http://www.youtube.com/watch?v=zNe9AkQbfmc)
|
||||
|
||||
## Supported Things
|
||||
|
||||
The Milight Binding supports White, and RGB(W) bulbs.
|
||||
|
||||
## Discovery
|
||||
|
||||
Version 3+ bridges can be discovered by triggering a search in openHAB's inbox. Found bridges
|
||||
will show up an can easily be added as things.
|
||||
After a bridge has been added, all possible bridge supported devices will appear
|
||||
|
@ -25,10 +28,12 @@ no real auto detection for single milight leds but only for the briges possible.
|
|||
Add the leds you actually configured and hide the rest of the detected things.
|
||||
|
||||
## Binding Configuration
|
||||
|
||||
When manually adding an older bridge Type (3-), you have to add configuration information for
|
||||
the bridge IP-Address and the listening port.
|
||||
|
||||
## Thing Configuration
|
||||
|
||||
Besides adding bridges through Paper-UI, you can also add them manually in your Thing
|
||||
configuration file.
|
||||
|
||||
|
@ -54,6 +59,7 @@ The group number corresponds to the bulbs/channels on your bridge, where 0 refle
|
|||
1-4 white bulb channels and 5 all rgb bulbs.
|
||||
|
||||
## Features
|
||||
|
||||
For white bulbs these channels are supported:
|
||||
|
||||
ledbrightness controls the brightness of your bulbs
|
||||
|
@ -145,6 +151,7 @@ The rgb bulbs do not support changing their saturation, so the colorpicker will
|
|||
end
|
||||
|
||||
## Authors
|
||||
|
||||
* David Gräff <david.graeff@tu-dortmund.de>, 2016
|
||||
* Hans-Joerg Merk
|
||||
* Kai Kreuzer
|
||||
|
|
|
@ -92,7 +92,8 @@ Valid slave parameters are
|
|||
| type | mandatory | object type. Dictates the function codes used for read and write. See below for more information. Can be either `coil`, `discrete`, `holding`, or `input`. |
|
||||
| start | optional | address of first coil/discrete input/register to read. Default is 0. The address is directly passed to the corresponding Modbus request, and thus is zero-based. See below for more information on the addressing. |
|
||||
| length | mandatory | number of _data items_ to read. _Data items_ here refers to registers, coils or discrete inputs depending on the slave type. For example, if the goal is to read one item with `valuetype=int32`, one needs to read two registers (2 * 16bit = 32bit), thus `length = 2`. If three coils are of interest, one should specify `length = 3` |
|
||||
| valuetype | optional | tells how interpret the register data. For details, consult [Register interpretation (valuetype) on read & write](#register-interpretation-valuetype-on-read--write). | updateunchangeditems | optional | **Since 1.9.0*. `true` or `false`. Controls whether the binding sends an update event on every successful poll (`true`) or only if the state of the item actually changes (`false`). Default is `false`. When polling many items with high poll frequency, setting this parameter to `true` may cause significant CPU usage. |
|
||||
| valuetype | optional | tells how interpret the register data. For details, consult [Register interpretation (valuetype) on read & write](#register-interpretation-valuetype-on-read--write).
|
||||
| updateunchangeditems | optional | **Since 1.9.0*. `true` or `false`. Controls whether the binding sends an update event on every successful poll (`true`) or only if the state of the item actually changes (`false`). Default is `false`. When polling many items with high poll frequency, setting this parameter to `true` may cause significant CPU usage. |
|
||||
| postundefinedonreaderror | optional | **Since 1.9.0**. `true` or `false`. Controls whether the binding sends `Undefined` (`UnDefType.UNDEF`) to the items associated with this slave when a read error occurs. Here read error refers to connection issues (cannot establish connection), I/O error (e.g. uninterrupted connection, unexpected EOF), [modbus protocol exceptions](http://www.simplymodbus.ca/exceptions.htm) (e.g. "Illegal data address"), or response transaction id not matching the request. Note that when `updateunchangeditems` is enabled, the `Undefined` is sent only once on errors, unless the slave recovers from the error. |
|
||||
|
||||
### Advanced connection parameters
|
||||
|
@ -570,4 +571,4 @@ To summarize, here are the recommended steps in case of errors
|
|||
|
||||
1. Update to latest development version; especially if you are using modbus binding version before 1.9.0
|
||||
2. isolate the issue using minimal configuration, and enable verbose logging (see above)
|
||||
3. record logs and configuration to [pastebin.com](http://pastebin.com/). The page contains examples for use with the [[Modbus binding|Modbus-Binding]].
|
||||
3. record logs and configuration to [pastebin.com](http://pastebin.com/).
|
||||
|
|
|
@ -18,43 +18,79 @@ This binding can be configured in the file `services/myq.cfg`.
|
|||
|
||||
The Chamberlain MyQ Binding only requires your Chamberlain MyQ Username and Password.
|
||||
|
||||
| Property | Default | Required | Description |
|
||||
|----------|---------|:--------:|-------------|
|
||||
| username | | Yes | Chamberlain MyQ Username |
|
||||
| password | | Yes | Chamberlain MyQ Password |
|
||||
| refresh | 60000 | No | Data refresh interval in milliseconds (60000 is one minute) |
|
||||
| timeout | 5000 | No | Timeout for HTTP requests in milliseconds |
|
||||
| appId | see description | No | Application ID for the MyQ API (only recommended if existing id ceases to work). It is recommended you do not supply your own appId unless you understand how the binding internal logic works and how/what could stop working. |
|
||||
| Property | Default | Required | Description |
|
||||
|--------------|---------|:--------:|-------------|
|
||||
| username | | Yes | Chamberlain MyQ Username |
|
||||
| password | | Yes | Chamberlain MyQ Password |
|
||||
| refresh | 60000 | No | Data refresh interval in milliseconds (60000 is one minute) |
|
||||
| quickrefresh | 2000 | No | Data refresh interval after Event is trigger in milliseconds |
|
||||
| timeout | 5000 | No | Timeout for HTTP requests in milliseconds |
|
||||
| appId | see description | No | Application ID for the MyQ API (only recommended if existing id ceases to work). It is recommended you do not supply your own appId unless you understand how the binding internal logic works and how/what could stop working. |
|
||||
|
||||
## Item configuration
|
||||
|
||||
Three Item Types are supported with this binding. Contact type will display if you garage door is open or closed. String type will display the state from the MYQ API "Open|Closed|Opening|Closing|Partially Open/Closed". Switch type will will "ON" state for open or partially open/closed and "OFF" state for closed. Turning the switch ON will open the door and turning the switch OFF will close the door.
|
||||
Both Garage Door Openers and Light Switch Module are supported. For Garage Door Openers multiple Item Types are supported.
|
||||
|
||||
Contact type will display if you garage door is open or closed. String type will display the state from the MYQ API "Open,Closed,Opening,Closing,Partially Open/Closed". Switch type will display "ON" state for open or partially open/closed and "OFF" state for closed. Turning the switch ON will open the door and turning the switch OFF will close the door.
|
||||
|
||||
Light Switch Module only support Switch Item types.
|
||||
|
||||
The device index is needed to config the items. For people with only one garage door opener the value needs to be set to "0". If you have multiple garage door openers and/or lights, the device index is based on the order the garage door opener/light's were added to the MyQ App. Starting openHAB in debug mode will display your MyQ Devices and the order they are listed in the API. This order is how you determine the device indexes.
|
||||
|
||||
```
|
||||
[DEBUG] [o.b.myq.internal.MyqDeviceData:44 ] - Chamberlain MyQ Devices:
|
||||
[DEBUG] [binding.myq.internal.MyqDevice:40 ] - Lamp DeviceID: 1234567 DeviceType: LampModule Lightstate : 0
|
||||
[DEBUG] [binding.myq.internal.MyqDevice:38 ] - GarageDoorOpener DeviceID: 1234568 DeviceType: GarageDoorOpener Doorstate : 2
|
||||
```
|
||||
|
||||
Both Devices also support parameter values. The parameters values are other information supplied by the API that cannot be changed by the binding.
|
||||
|
||||
## Examples
|
||||
|
||||
### Items
|
||||
|
||||
```
|
||||
Switch GarageDoorSwitch "Garage Door Open" {myq="0"}
|
||||
Contact GarageDoorContact "Garage Door [%s]" <contact> {myq="0"}
|
||||
String GarageDoorString "Garage Door [%s]" {myq="0"}
|
||||
Rollershutter GarageDoorShutter "Garage Door Open" {myq="0"}
|
||||
Switch LampModule "Lamp Module On" {myq="0" autoupdate="false"}
|
||||
String LampModuleCustomerName "Lamp Module Name [%s]" {myq="0#customerName"}
|
||||
String LampModuleDesc "Lamp Module Desc [%s]" {myq="0#desc"}
|
||||
String LampModuleOnline "Lamp Module Online [%s]" {myq="0#online"}
|
||||
String LampModuleDeviceId "Lamp Module Device Id [%s]" {myq="0#MyQDeviceId"}
|
||||
String LampModuleDeviceType "Lamp Module DeviceType [%s]" {myq="0#MyQDeviceTypeName"}
|
||||
String LampModuleSerialNumber "Lamp Module SerialNumber [%s]" {myq="0#SerialNumber"}
|
||||
|
||||
Switch GarageDoorSwitch "Garage Door Open" {myq="1"}
|
||||
Contact GarageDoorContact "Garage Door [%s]" <contact> {myq="1"}
|
||||
String GarageDoorString "Garage Door [%s]" {myq="1"}
|
||||
Rollershutter GarageDoorShutter "Garage Door Open" {myq="1"}
|
||||
String GarageDoorCustomerName "Garage Door Name [%s]" {myq="1#customerName"}
|
||||
String GarageDoorDesc "Garage Door Desc [%s]" {myq="1#desc"}
|
||||
String GarageDoorOnline "Garage Door Online [%s]" {myq="1#online"}
|
||||
String GarageDoorDeviceId "Garage Door Device Id [%s]" {myq="1#MyQDeviceId"}
|
||||
String GarageDoorDeviceType "Garage Door DeviceType [%s]" {myq="1#MyQDeviceTypeName"}
|
||||
String GarageDoorSerialNumber "Garage Door SerialNumber [%s]" {myq="1#SerialNumber"}
|
||||
```
|
||||
|
||||
### Sitemap
|
||||
|
||||
```
|
||||
Switch item=LampModule
|
||||
Text item=LampModuleCustomerName
|
||||
Text item=LampModuleDesc
|
||||
Text item=LampModuleOnline
|
||||
Text item=LampModuleDeviceId
|
||||
Text item=LampModuleDeviceType
|
||||
Text item=LampModuleSerialNumber
|
||||
|
||||
Switch item=GarageDoorSwitch
|
||||
Text item=GarageDoorString
|
||||
Text item=GarageDoorContact
|
||||
Switch item=GarageDoorShutter
|
||||
```
|
||||
|
||||
The device index is needed to config the items. For people with only one garage door opener the value needs to be set to "0". If you have multiple garage door openers, the device index is based on the order the garage door opener's were added to the MyQ App.
|
||||
|
||||
```
|
||||
[INFO ] [.b.myq.internal.GarageDoorData] - Chamberlain MyQ Devices:
|
||||
[INFO ] [.b.myq.internal.GarageDoorData] - DeviceID: 1810905 DeviceName: CG0810243E7F DeviceType: GarageDoorOpener
|
||||
Text item=GarageDoorCustomerName
|
||||
Text item=GarageDoorDesc
|
||||
Text item=GarageDoorOnline
|
||||
Text item=GarageDoorDeviceId
|
||||
Text item=GarageDoorDeviceType
|
||||
Text item=GarageDoorSerialNumber
|
||||
```
|
||||
|
||||
## Known Working Hardware
|
||||
|
@ -64,3 +100,5 @@ The device index is needed to config the items. For people with only one garage
|
|||
| HD950WF | Chamberlain 1.25 hps Wi-Fi Garage Door Opener |
|
||||
| WD850KEVG | Chamberlain 1 hps Garage Door Opener with MyQ Internet Gateway |
|
||||
| WD832KEV | Chamberlain 1/2 hps MyQ Garage Door Opener |
|
||||
| 825LM | Liftmaster 825LM Remote Light Module |
|
||||
| 823LM | Liftmaster 823LM Remote Light Switch |
|
||||
|
|
|
@ -1,7 +1,11 @@
|
|||
---
|
||||
layout: documentation
|
||||
title: Netatmo - Bindings
|
||||
source: external
|
||||
---
|
||||
|
||||
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
|
||||
|
||||
{% include base.html %}
|
||||
|
||||
# Netatmo Binding
|
||||
|
@ -83,9 +87,11 @@ Number Netatmo_Indoor_CO2 "CO2" <carbondioxide> { channel = "netatmo:NAMain:home
|
|||
**Supported types for the indoor module:**
|
||||
|
||||
* Temperature
|
||||
* TemperatureTrend
|
||||
* Humidity
|
||||
* Co2
|
||||
* Pressure
|
||||
* PressureTrend
|
||||
* AbsolutePressure
|
||||
* Noise
|
||||
* WifiStatus
|
||||
|
@ -109,6 +115,7 @@ Number Netatmo_Outdoor_Temperature "Temperature" { channel = "netatmo:NAModule1:
|
|||
**Supported types for the outdoor module:**
|
||||
|
||||
* Temperature
|
||||
* TemperatureTrend
|
||||
* Humidity
|
||||
* RfStatus
|
||||
* BatteryVP
|
||||
|
@ -154,6 +161,8 @@ Number Netatmo_Rain_Current "Rain [%.1f mm]" { channel = "netatmo:NAModule3:home
|
|||
**Supported types for the rain guage:**
|
||||
|
||||
* Rain
|
||||
* Rain1
|
||||
* Rain24
|
||||
* RfStatus
|
||||
* BatteryVP
|
||||
* LastMessage
|
||||
|
|
|
@ -32,8 +32,8 @@ network:device:devicename [ hostname="192.168.0.64", port="0", retry="1", timeou
|
|||
- **hostname:** IP address or hostname of the device
|
||||
- **port:** "0" to use ICMP ping or the number of an open TCP port on the device
|
||||
- **retry:** After how many ping retries shall the device be assumed as offline
|
||||
- **timeout:** How long shall the ping wait for an answer (in milliseconds, `60000` = one minute)
|
||||
- **refresh_interval:** How often shall the device be checked (in milliseconds, `5000` = 5 seconds)
|
||||
- **timeout:** How long shall the ping wait for an answer (in milliseconds, `5000` = 5 seconds)
|
||||
- **refresh_interval:** How often shall the device be checked (in milliseconds, `60000` = one minute)
|
||||
- **use\_system\_ping:** Use the real ICMP ping program of the operating system, instead of the Java ping. Useful if the devices cannot be reached by Java ping. **Beware**: By setting this option to `true`, the **port option is ignored**.
|
||||
- **dhcplisten:** Listen for DHCP Request messages.
|
||||
If devices leave and reenter a network, they usually request their last IP address by a UDP broadcast message (DHCP, Message type Request).
|
||||
|
|
|
@ -26,7 +26,7 @@ This binding allows allows basic control of the OpenSprinkler and OpenSprinkler
|
|||
OpenSprinkler
|
||||
|
||||
```
|
||||
opensprinkler:http:1 [ hostname="127.0.0.1", port="80", password="opendoor", refresh="60" ]
|
||||
opensprinkler:http:1 [ hostname="127.0.0.1", port=80, password="opendoor", refresh=60 ]
|
||||
```
|
||||
|
||||
- hostname: Hostname or IP address of the OpenSprinkler HTTP API.
|
||||
|
@ -37,7 +37,7 @@ opensprinkler:http:1 [ hostname="127.0.0.1", port="80", password="opendoor", ref
|
|||
OpenSprinkler PI
|
||||
|
||||
```
|
||||
opensprinkler:pi:1 [ stations="8", refresh="60" ]
|
||||
opensprinkler:pi:1 [ stations=8, refresh=60 ]
|
||||
```
|
||||
|
||||
- stations: Number of stations to control.
|
||||
|
|
|
@ -110,9 +110,9 @@ The binding introduces the following channels:
|
|||
| Channel ID | Channel Description | Supported item type | Default priority | Advanced |
|
||||
| ------------- | ------------- |------------|----------|----------|
|
||||
| load | Recent load in percents | Number | High | False |
|
||||
| load1 | Load in percents for the last 1 minutes | Number | Medium | True |
|
||||
| load1 | Load in percents for the last 1 minute | Number | Medium | True |
|
||||
| load5 | Load in percents for the last 5 minutes | Number | Medium | True |
|
||||
| load15 | Load in percents for the last 1 minutes | Number | Medium | True |
|
||||
| load15 | Load in percents for the last 15 minutes | Number | Medium | True |
|
||||
| threads | Number of threads currently running | Number | Medium | True |
|
||||
| uptime | System uptime (time after start) in minutes | Number | Medium | True |
|
||||
| name | Name of the device | String | Low | False |
|
||||
|
@ -132,7 +132,7 @@ The binding introduces the following channels:
|
|||
| information | Product, manufacturer, SN, width and height of the display in cm | String | Low | True |
|
||||
| ip | Host IP address of the network | String | Low | False |
|
||||
| mac | MAC address | String | Low | True |
|
||||
| networkName | The name of the network. | String | Low | False |
|
||||
| networkName | The name of the network | String | Low | False |
|
||||
| networkDisplayName | The display name of the network | String | Low | False |
|
||||
| packagesSent | Number of packages sent | Number | Medium | True |
|
||||
| packagesReceived | Number of packages received | Number | Medium | True |
|
||||
|
@ -204,7 +204,6 @@ Number CPU_Load { channel="systeminfo:computer:work:cpu#load
|
|||
Number CPU_Load1 { channel="systeminfo:computer:work:cpu#load1" }
|
||||
Number CPU_Load5 { channel="systeminfo:computer:work:cpu#load5" }
|
||||
Number CPU_Load15 { channel="systeminfo:computer:work:cpu#load15" }
|
||||
Number CPU_Load1 { channel="systeminfo:computer:work:cpu#load1" }
|
||||
Number CPU_Threads { channel="systeminfo:computer:work:cpu#threads" }
|
||||
Number CPU_Uptime { channel="systeminfo:computer:work:cpu#uptime" }
|
||||
|
||||
|
|
|
@ -1,14 +1,18 @@
|
|||
---
|
||||
layout: documentation
|
||||
title: Toon - Bindings
|
||||
source: external
|
||||
---
|
||||
|
||||
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
|
||||
|
||||
{% include base.html %}
|
||||
|
||||
# Toon Binding
|
||||
|
||||
The Toon bindings shows among others current room temperature, setpoint, energy and gas usage information.
|
||||
It can control the setpoint and current program. Connected smart plugs can also be controlled.
|
||||
|
||||
|
||||
## Supported Things
|
||||
|
||||
### Toon Webaccount
|
||||
|
|
|
@ -10,6 +10,8 @@ source: https://github.com/openhab/openhab1-addons/blob/master/bundles/binding/o
|
|||
|
||||
# Wake-on-LAN Binding
|
||||
|
||||
The Wake-on-LAN binding allows you to turn on or wake up a computer by sending it a [network message](https://en.wikipedia.org/wiki/Wake-on-LAN).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
For Windows computers not in a domain, the firewall must be configured properly (allow remote shutdowns) and the DWORD-Regkey `LocalAccountTokenFilterPolicy` in `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System` must be set to 1.
|
||||
|
|
|
@ -124,7 +124,6 @@ The following channels are currently supported.
|
|||
|
||||
Currently unsupported Z-Way probe types:
|
||||
|
||||
- SwitchMultilevel: motor (selection criterion for rollershutter - will be implemented soon)
|
||||
- SensorBinary: cooling, all alarm types (resulting from Z-Wave command class AlarmSensor(deprecated) and Alarm)
|
||||
- SensorMultilevel: meterElectric_pulse_count, meterElectric_voltage, meterElectric_ampere, meterElectric_power_factor
|
||||
|
||||
|
|
|
@ -22,7 +22,7 @@ The generic design makes it relatively easy for developers to integrate other da
|
|||
| [MariaDB](https://mariadb.org/) | [mariadb-java-client-1.4.6.jar](http://mvnrepository.com/artifact/org.mariadb.jdbc/mariadb-java-client) |
|
||||
| [MySQL](https://www.mysql.com/) | [mysql-connector-java-5.1.39.jar](http://mvnrepository.com/artifact/mysql/mysql-connector-java) |
|
||||
| [PostgreSQL](http://www.postgresql.org/) | [postgresql-9.4.1209.jre7.jar](http://mvnrepository.com/artifact/org.postgresql/postgresql) |
|
||||
| [SQLite](https://www.sqlite.org/) | [sqlite-jdbc-3.8.11.2.jar](http://mvnrepository.com/artifact/org.xerial/sqlite-jdbc) |
|
||||
| [SQLite](https://www.sqlite.org/) | [sqlite-jdbc-3.16.1.jar](http://mvnrepository.com/artifact/org.xerial/sqlite-jdbc) |
|
||||
|
||||
## Table of Contents
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
layout: documentation
|
||||
title: habmin - UI
|
||||
title: HABmin - UI
|
||||
source: external
|
||||
---
|
||||
|
||||
|
@ -8,17 +8,13 @@ source: external
|
|||
|
||||
{% include base.html %}
|
||||
|
||||
HABmin
|
||||
======
|
||||
# HABmin
|
||||
|
||||
HABmin is a modern, professional and portable user interface for openHAB,
|
||||
providing both user and administrative functions (eg sitemaps for users, and configuration utilities
|
||||
to aid setup).
|
||||
HABmin is a modern, professional and portable user interface for openHAB, providing both user and administrative functions (e.g., sitemaps for users, and configuration utilities to aid setup).
|
||||
|
||||
Features
|
||||
========
|
||||
## Features
|
||||
|
||||
* **Responsive**. Should work well on all devices. Of course some functions may be removed or be difficult to use on small devices (eg the graphical rule editor).
|
||||
* **Responsive**. Should work well on all devices. Of course some functions may be removed or be difficult to use on small devices (e.g., the graphical rule editor).
|
||||
* **Theme-able**. Multiple themes are available - take your pick (currently 3 themes). If you want a different look, we're using [bootswatch](http://www.bootswatch.com) themes - vote for your favourite by [raising an issue](https://github.com/openhab/org.openhab.ui.habmin/issues/new).
|
||||
* **Charting**. Modern, fast charting of historical data.
|
||||
* **Graphical rule editor**. No need to learn rule syntax.
|
||||
|
@ -26,8 +22,7 @@ Features
|
|||
* Available as native app for **Android**.
|
||||
|
||||
|
||||
Screenshots
|
||||
===========
|
||||
## Screenshots
|
||||
|
||||
The following images show a selection of screenshots. Note that the theme is user selectable, although most images are shown with a dark (*slate*) theme (except the mobile sitemap image).
|
||||
|
||||
|
@ -68,4 +63,4 @@ ZWave network routing diagram...
|
|||
|
||||
Sitemaps (mobile view using *yeti* theme)...
|
||||
|
||||

|
||||

|
||||
|
|
|
@ -1,7 +1,11 @@
|
|||
---
|
||||
layout: documentation
|
||||
title: Mary Text-to-Speech - Voice
|
||||
source: external
|
||||
---
|
||||
|
||||
<!-- Attention authors: Do not edit directly. Please add your changes to the appropriate source repository -->
|
||||
|
||||
{% include base.html %}
|
||||
|
||||
# Mary Text-to-Speech
|
||||
|
|
|
@ -18,7 +18,7 @@ Note that this list also serves as a checklist for code reviews on pull requests
|
|||
1. Every class, interface and enumeration should have JavaDoc describing its purpose and usage.
|
||||
1. Every class, interface and enumeration must have an @author tag in its JavaDoc for every author that wrote a substantial part of the file.
|
||||
1. Every constant, field and method with default, protected or public visibility should have JavaDoc (optional, but encouraged for private visibility as well).
|
||||
1. Code must be formatted using the provided code formatter and clean up settings. They are set up automatically by the official [IDE setup]({{base}}/developers/development/ide.html).
|
||||
1. Code must be formatted using the provided code formatter and clean up settings. They are set up automatically by the official [IDE setup](ide.html).
|
||||
1. Generics must be used where applicable.
|
||||
1. Code should not show any warnings. Warnings that cannot be circumvented should be suppressed by using the @SuppressWarnings annotation.
|
||||
1. For dependency injection, OSGi Declarative Services should be used.
|
||||
|
|
Loading…
Reference in New Issue