Kai Kreuzer
parent
2504f2018d
commit
fb8728aeb2
|
|
@ -19,14 +19,16 @@ keba,Keba,"This binding integrates the [Keba KeContact EV Charging Stations](htt
|
|||
kostalinverter,Kostal inverter,"Scrapes the web interface of the inverter for the metrics of the supported channels below."
|
||||
lutron,Lutron,"This binding integrates with [Lutron](http://www.lutron.com) light control systems."
|
||||
max,MAX!,"This is the binding for the [eQ-3 MAX! Home Solution](http://www.eq-3.de/)."
|
||||
meteostick,Meteostick,"This is the binding for the [Meteostick](http://www.smartbedded.com/wiki/index.php/Meteostick) weather receiver dongle. This is an RF receiver that can receive data directly from Davis weather devices (and others)"
|
||||
milight,Milight,"The openHAB2 Milight binding allows to send commands to multiple Milight bridges."
|
||||
netatmo,Netatmo,"The Netatmo binding integrates the following Netatmo products :"
|
||||
network,Network,"This binding integrates a way to check whether a device is currently available on the network and the required ping time."
|
||||
onkyo,Onkyo,"This binding integrates the Onkyo AV receivers."
|
||||
opensprinkler,OpenSprinkler,"This binding allows allows basic control of the OpenSprinkler and OpenSprinkler PI (Plus) devices. Stations can be controlled to be turned on or off and rain sensor state can be read."
|
||||
orvibo,Orvibo,"This binding integrates Orvibo devices that communicate using UDP. Primarily this was designed for S20 Wifi Sockets but other products using the same protocol may be implemented in future."
|
||||
pioneeravr,PioneerAVR Configuration,"The binding can auto-discover the Pioneer AVRs present on your local network. The auto-discovery is enabled by default. To disable it, you can create a file in the services directory called pioneeravr.cfg with the following content:"
|
||||
pulseaudio,Pulseaudio,"This binding integrates pulseaudio devices."
|
||||
rfxcom,RFXCOM,"This binding integrates large number of sensors and actuators from several different manufactures throug the [RFXCOM transceivers](http://www.rfxcom.com)."
|
||||
rfxcom,RFXCOM,"This binding integrates large number of sensors and actuators from several different manufactures through [RFXCOM transceivers](http://www.rfxcom.com)."
|
||||
rme,RME,"This binding integrates the RME RainManager rain water pump and management system"
|
||||
samsungtv,Samsung TV,"This binding integrates the [Samsung TV's](http://www.samsung.com)."
|
||||
smaenergymeter,SMA Energy Meter,"This Binding is used to display the measured values of a SMA Energy Meter device. It shows purchased and grid feed-in power and energy."
|
||||
|
|
|
|||
|
|
|
@ -1 +1 @@
|
|||
Subproject commit 3f794c6b455678bbab89f85ecae2a22357eb2608
|
||||
Subproject commit c98df168c5cd7fc258397fc3ae9f1f85d14a877d
|
||||
|
|
@ -1 +1 @@
|
|||
Subproject commit 6187457d8a846459f60f5604e1881ac3a4d8d551
|
||||
Subproject commit 438ac348e5b1aa4d09e6dea4caa86941ccbfc82d
|
||||
|
|
@ -1 +1 @@
|
|||
Subproject commit 894a0e185f99c8ca238ff0b00192472e86f27e54
|
||||
Subproject commit 53c5318bb9c80890ac91fc889cd0f8e28f87b898
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 22 KiB |
|
|
@ -12,12 +12,15 @@ The integration happens through the digitalSTROM-Server, which acts as a gateway
|
|||
**Note:** All was tested with digitalSTROM-Server firmware version 1.9.3 to 1.10.3.
|
||||
|
||||
|
||||
|
||||
## Supported Things
|
||||
|
||||
### digitalSTROM-Server
|
||||
|
||||
The digitalSTROM-Server is required for accessing any other digitalSTROM-Devices. It acts like a *"bridge"*.
|
||||
|
||||
### digitalSTROM-Devices
|
||||
|
||||
At this point almost all available **GE**, **SW** and **GR** digitalSTROM-Devices with an set output-mode, unequal *disabled* or *PWM*, are supported by this binding.
|
||||
For that there are identically named thing types. Only the *GR* type has a channel (shade), which cannot be changed. The other two types adds their channels dynamically affected by the set color-group and output-mode. They also automatically change or add the channels, if the color-group or output-mode has changed through the dSS-web-configuration or the configured sensor priorities of the thing has changed.
|
||||
|
||||
|
|
@ -38,6 +41,7 @@ The following table shows all tested digitalSTROM-Devices with their output-mode
|
|||
| SW-ZWS200 | switch, powersave, wipe | black, yellow |
|
||||
|
||||
### digitalSTROM-Scenes
|
||||
|
||||
Furthermore the digitalSTROM-Scene concept is part of the digitalSTROM-Binding. This scenes are implemented as virtual things. The difference scene thing types are list in the following table.
|
||||
|
||||
| Thing-Type-ID | Label | Description |
|
||||
|
|
@ -58,21 +62,26 @@ Furthermore the digitalSTROM-Scene concept is part of the digitalSTROM-Binding.
|
|||
If you only want to discover one of the thing types, you can start a discovery scan on the thing type you wish have discovered. You can use the command line command, e.g.: ``smarthome:discovery start digitalstrom:namedScene`` to start the scan. What thing types this binding supports please have a look at **Supported Things**.
|
||||
|
||||
## digitalSTROM-Scenes
|
||||
|
||||
### General
|
||||
|
||||
The device scene configuration will be saved persistently to the things to update the device state faster. For that each scene configuration of each device has to read out first, because of the digitalSTROM-rule 9 that requires a waiting period of one minute, that take some time so that at the first start a scene call can be take some time to read it out and update the device state. To read it out faster only the discovered or called scenes will be red out.
|
||||
|
||||
**Note:**
|
||||
Because the digitalSTROM-Server can't inform the binding about save scene events at this time, the persistently saved scene configurations can't be updated. The current troubleshooting to read out the new scene configuration after a save scene action at the digitalSTROM-Server is the following:
|
||||
|
||||
1. delete the thing to delete the persistently saved scene configuration
|
||||
2. restart the server to delete the temporary saved scene configuration
|
||||
3. add the thing again to red out the scene configuration again.
|
||||
|
||||
## Thing Configuration
|
||||
|
||||
### digitalSTROM-Server:
|
||||
### digitalSTROM-Server
|
||||
|
||||
The digitalSTROM-Server thing has the following configuration parameter groups *Connection configuration*, *Server information* and *General configurations*.
|
||||
|
||||
#### Connection configuration:
|
||||
#### Connection configuration
|
||||
|
||||
If the digitalSTROM-Server isn’t found automatically, e.g. because the server isn’t placed at the local network or the mDNS-service is deactivated, you have to insert the network address or URL and the authentication data manually through the graphical user interface or type it into the \*.thing with textual configuration.
|
||||
|
||||
| Parameter Label | Parameter ID | Description | Required | Advanced
|
||||
|
|
@ -82,7 +91,7 @@ The digitalSTROM-Server thing has the following configuration parameter groups *
|
|||
| Password | password | Password of a registered user to authenticate to the digitalSTROM-Server. | user name and password or Application-Token | false |
|
||||
| Application-Token | applicationToken | The Application-Token to authenticate to the digitalSTROM-Server. | user name and password or Application-Token| false |
|
||||
|
||||
#### Server information:
|
||||
#### Server information
|
||||
|
||||
The group parameters *Server information* only includes informative parameters, which have no special functionality.
|
||||
|
||||
|
|
@ -92,9 +101,8 @@ The digitalSTROM-Server thing has the following configuration parameter groups *
|
|||
| dSID | dSID | The unique identifier of a digitalSTOM-server. | false| false |
|
||||
| digitalSTROM-Installation name | dsName | The user defined name of the digitalSTROM-Installation. | false | false | false |
|
||||
|
||||
|
||||
|
||||
#### General configuration:
|
||||
|
||||
Here you can set general binding configuration parameters, which shown in following table:
|
||||
|
||||
| Parameter Label | Parameter ID| Description | Required | Advanced | default
|
||||
|
|
@ -105,14 +113,17 @@ The digitalSTROM-Server thing has the following configuration parameter groups *
|
|||
| Wait time sensor reading | sensorWaitTime| Waiting time between the evaluation of the sensor values and the reading of the scenes in seconds. **ATTENTION:** digitalSTROM rule 8 and 9 require a waiting period of 1 minute. Values less than 60 seconds could affect the digitalSTROM system. | false | true | 60 |
|
||||
|
||||
At the thing file, a manual configuration looks e.g. like
|
||||
|
||||
```
|
||||
Bridge digitalstrom:dssBridge:dssBridge1 [ ipAddress="dss.local.", userName="dssadmin", password=“dssadmin", sensorDataUpdateIntervall="180"]
|
||||
```
|
||||
|
||||
### digitalSTROM-Devices:
|
||||
### digitalSTROM-Devices
|
||||
|
||||
The digitalSTROM-Device things have the following configuration parameter groups *Device information* and *Sensor setup*.
|
||||
|
||||
#### Device information
|
||||
|
||||
Each digitalSTROM-Device needs the device ID named dSID as configuration parameter. The device ID is printed as serial number at the digitalSTOM-Device and can also be found within the web-interface of the digitalSTROM-Server.
|
||||
Furthermore a supported digitalSTROM-Device has only informative parameter at this point.
|
||||
The following table shows all parameters:
|
||||
|
|
@ -130,6 +141,7 @@ The following table shows all parameters:
|
|||
| Functional color group | funcColorGroup | The current digitalSTROM-Device functional color group e.g. yellow = light. | false | false |
|
||||
|
||||
#### Sensor setup
|
||||
|
||||
The GE and SW digitalSTROM-Devices have usually sensors to capture power consumption data. So these devices have the following parameters to read them out.
|
||||
|
||||
| Parameter Label | Parameter ID| Description | Required | Advanced | Default |
|
||||
|
|
@ -139,6 +151,7 @@ The GE and SW digitalSTROM-Devices have usually sensors to capture power consump
|
|||
| Output current refresh priority | outputCurrentRefreshPriority | Sets the refresh priority for the output current sensor value. Can be never, low priority, medium priority or high priority. | false | false | never |
|
||||
|
||||
### digitalSTROM-Scenes
|
||||
|
||||
The digitalSTROM-Scenes can be defined with following parameters.
|
||||
|
||||
| Parameter Label | Parameter ID| Description | Required | Advanced |
|
||||
|
|
@ -184,10 +197,13 @@ All devices support some of the following channels:
|
|||
| scene | Switch | The scene channel allows to call or undo a scene from digitalSTROM. | Scene |
|
||||
|
||||
**Notes:**
|
||||
|
||||
*Channels with accepted command type increase and decrease:*
|
||||
|
||||
* digitalSTROM will only evaluate increase and decrease commands, if a scene was called before which turn the device on.
|
||||
|
||||
*Blinds:*
|
||||
|
||||
* Increase, decrease and up, down commands of the shade channel changes the angle in digitalSTROM, too. If you want to set only the position, you have to set the value directly.
|
||||
* To protect the slats digitalSTROM changes the position by setting the angle, too, if the position is very high or low. So if you want to see the correct position, you have to send a refresh or stop command, if the blind is ready.
|
||||
|
||||
|
|
|
|||
|
|
@ -35,9 +35,7 @@ The _server_ bridge thing requires the following configuration parameters:
|
|||
|
||||
| Parameter Label | Parameter ID | Description | Required | Default |
|
||||
|--------------------------|-----------------|---------------------------------------------------------|----------|---------|
|
||||
| Freebox Network Address | ipAddress | The IP address / FQDN of the Freebox Server (can include port number).| false | mafreebox.freebox.fr |
|
||||
| API base URL | apiBaseUrl | The base URL to use the Freebox Server API. | false | /api/ |
|
||||
| API version | apiVersion | The Freebox Server API version. | false | 3.0 |
|
||||
| Freebox Network Address | fqdn | The IP address / FQDN of the Freebox Server (can include port number).| false | mafreebox.freebox.fr |
|
||||
| Application token | appToken | Token generated by the Freebox Server. | false | |
|
||||
| Refresh Interval | refreshInterval | The refresh interval in seconds which is used to poll given Freebox Server.| false | 30 |
|
||||
|
||||
|
|
@ -160,7 +158,7 @@ Bridge freebox:server:fb "Freebox Revolution" [ appToken="xxxxxxxxxxxxxxxxxxxxxx
|
|||
Here is another example overwritting default configuration parameters:
|
||||
|
||||
```
|
||||
Bridge freebox:server:fb "Freebox Revolution" [ ipAddress="192.168.0.254", appToken="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", refreshInterval=20 ] {
|
||||
Bridge freebox:server:fb "Freebox Revolution" [ fqdn="192.168.0.254", appToken="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", refreshInterval=20 ] {
|
||||
Thing phone Phone "Phone" [ refreshPhoneInterval=10, refreshPhoneCallsInterval=120 ]
|
||||
Thing net_device tv1 "TV living room" [ macAddress="XX:XX:XX:XX:XX:XX" ]
|
||||
Thing net_interface tv2 "TV bedroom" [ ipAddress="192.168.0.100" ]
|
||||
|
|
|
|||
|
|
@ -0,0 +1,81 @@
|
|||
---
|
||||
layout: documentation
|
||||
---
|
||||
|
||||
{% include base.html %}
|
||||
|
||||
# Meteostick Binding
|
||||
|
||||
This is the binding for the [Meteostick](http://www.smartbedded.com/wiki/index.php/Meteostick) weather receiver dongle. This is an RF receiver that can receive data directly from Davis weather devices (and others)
|
||||
|
||||
## Supported Things
|
||||
|
||||
This binding support 2 different things types
|
||||
|
||||
| Thing | Type | Description |
|
||||
|----------------------|--------|-----------------------------------|
|
||||
| meteostick_bridge | Bridge | This is the Meteostick USB stick |
|
||||
| meteostick_davis_iss | Thing | This is the Davis Vue ISS |
|
||||
|
||||
|
||||
## Binding Configuration
|
||||
|
||||
The Meteostick things need to be manually added - there is no discovery in the Meteostick binding.
|
||||
|
||||
First add and configure the Meteostick bridge - the port and frequency band for your region need to be set.
|
||||
Next add the sensor and configure the channel number.
|
||||
|
||||
## Thing Configuration
|
||||
|
||||
### meteostick_bridge Configuration Options
|
||||
|
||||
| Option | Description |
|
||||
|--------|----------------------------------------------------------------------------|
|
||||
| port | Sets the serial port to be used for the stick |
|
||||
| mode | Sets the operating mode 0 = USA, 1 = Europe, 2 = Australia. 3 = FineOffset |
|
||||
|
||||
|
||||
### meteostick_davis_iss Configuration Options
|
||||
|
||||
| Option | Description |
|
||||
|---------|-------------------------------------------|
|
||||
| channel | Sets the RF channel used for this sensor |
|
||||
|
||||
## Channels
|
||||
|
||||
### Meteostick
|
||||
|
||||
| Channel Type ID | Item Type | Description |
|
||||
|------------------|------------------------|--------------|
|
||||
| pressure | Number | Air pressure |
|
||||
| indoor-temperature | Number | Indoor temperature |
|
||||
|
||||
### Davis ISS
|
||||
|
||||
| Channel Type ID | Item Type | Description |
|
||||
|------------------|------------------------|--------------|
|
||||
| outdoor-temperature | Number | Outside temperature |
|
||||
| humidity | Number | Humidity |
|
||||
| wind-direction | Number | Wind direction |
|
||||
| wind-speed | Number | Wind speed |
|
||||
| rain-raw | Number | Raw rain counter from the tipping bucket sensor |
|
||||
| rain-currenthour | Number | The rainfall in the last 60 minutes |
|
||||
| rain-lasthour | Number | The rainfall in the previous hour |
|
||||
| solar-power | Number | Solar power from the sensor station |
|
||||
| signal-strength | Number | Received signal strength |
|
||||
| low-battery | Number | Low battery warning |
|
||||
|
||||
#### Rainfall
|
||||
|
||||
There are three channels associated with rainfall. The raw counter from the tipping bucket is provided, the rainfall
|
||||
in the last 60 minutes is updated on each received rainfall and provides the past 60 minutes of rainfall. The rainfall
|
||||
in the previous hour is the rainfall for each hour of the day and is updated on the hour.
|
||||
|
||||
## Full Example
|
||||
|
||||
Things can be defined in the .thing file as follows
|
||||
|
||||
```
|
||||
meteostick:meteostick_bridge:receiver [ port="/dev/tty.usbserial-AI02XA60" mode="1" ]
|
||||
meteostick:meteostick_davis_iss:iss (meteostick:meteostick_bridge:receiver) [ channel=1 ]
|
||||
```
|
||||
|
|
@ -0,0 +1,88 @@
|
|||
---
|
||||
layout: documentation
|
||||
---
|
||||
|
||||
{% include base.html %}
|
||||
|
||||
# Onkyo Binding
|
||||
|
||||
This binding integrates the Onkyo AV receivers.
|
||||
|
||||
## Introduction
|
||||
|
||||
Binding should be compatible with Onkyo AV receivers which support ISCP (Integra Serial Control Protocol) over Ethernet (eISCP).
|
||||
|
||||
## Supported Things
|
||||
|
||||
This binding supports only one thing: The Onkyo AV Receiver
|
||||
|
||||
|
||||
## Discovery
|
||||
|
||||
This binding can discover the supported Onkyo AV Receivers. At the moment only the following models are supported:
|
||||
|
||||
* TX-NR535
|
||||
|
||||
## Binding Configuration
|
||||
|
||||
The binding can auto-discover the Onkyo AVRs present on your local network. The auto-discovery is enabled by default. To disable it, you can create a file in the services directory called onkyo.cfg with the following content:
|
||||
|
||||
```
|
||||
org.openhab.onkyo:enableAutoDiscovery=false
|
||||
```
|
||||
|
||||
This configuration parameter only controls the Onkyo AVR auto-discovery process, not the openHAB auto-discovery. Moreover, if the openHAB auto-discovery is disabled, the Onkyo AVR auto-discovery is disabled too.
|
||||
|
||||
|
||||
## Thing Configuration
|
||||
|
||||
The Onkyo AVR thing requires the ip address and the port to access it on.
|
||||
In the thing file, this looks e.g. like
|
||||
```
|
||||
onkyo:onkyoAV:myOnkyo [ipAddress="192.168.1.100", port="60128"]
|
||||
|
||||
|
||||
##Channels
|
||||
|
||||
The Onkyo AVR supports the following channels:
|
||||
|
||||
| Channel Type ID | Item Type | Description |
|
||||
|-------------------------|--------------|--------------|
|
||||
| power | Switch | Power on/off your device |
|
||||
| mute | Switch | Mute/unmute your device |
|
||||
| input | Number | The input for the AVR |
|
||||
| volume | Dimmer | Volume of your device |
|
||||
| control | Player | Control the Zone Player, e.g. play/pause/next/previous/ffward/rewind (available if playing from Network or USB)|
|
||||
| title | String | Title of the current song (available if playing from Network or USB)|
|
||||
| album | String | Album name of the current song (available if playing from Network or USB)|
|
||||
| artist | String | Artist name of the current song (available if playing from Network or USB)|
|
||||
| currentPlayingTime | String | Current playing time of the current song (available if playing from Network or USB)|
|
||||
| listenmode | Number | Current listening mode e.g. Stero, 5.1ch Surround,..|
|
||||
|
||||
##Input Source Mapping
|
||||
|
||||
Here after are the ID values of the input sources:
|
||||
|
||||
* 00: DVR/VCR
|
||||
* 01: SATELLITE/CABLE
|
||||
* 02: GAME
|
||||
* 03: AUX
|
||||
* 04: GAME
|
||||
* 05: PC
|
||||
* 16: BLURAY/DVD
|
||||
* 32: TAPE1
|
||||
* 33: TAPE2
|
||||
* 34: PHONO
|
||||
* 35: CD
|
||||
* 36: FM
|
||||
* 37: AM
|
||||
* 38: TUNER
|
||||
* 39: MUSICSERVER
|
||||
* 40: INTERETRADIO
|
||||
* 41: USB
|
||||
* 42: USB_BACK
|
||||
* 43: NETWORK
|
||||
* 45: AIRPLAY
|
||||
* 48: MULTICH
|
||||
* 50: SIRIUS
|
||||
|
||||
|
|
@ -6,9 +6,9 @@ layout: documentation
|
|||
|
||||
# RFXCOM Binding
|
||||
|
||||
This binding integrates large number of sensors and actuators from several different manufactures throug the [RFXCOM transceivers](http://www.rfxcom.com).
|
||||
This binding integrates large number of sensors and actuators from several different manufactures through [RFXCOM transceivers](http://www.rfxcom.com).
|
||||
|
||||
RFXCOM transceivers supports RF 433 Mhz protocols like:
|
||||
RFXCOM transceivers support RF 433 Mhz protocols like:
|
||||
* HomeEasy
|
||||
* Cresta
|
||||
* X10
|
||||
|
|
@ -18,14 +18,14 @@ RFXCOM transceivers supports RF 433 Mhz protocols like:
|
|||
* PT2262
|
||||
* Oregon etc.
|
||||
|
||||
See RFXtrx User Guide for the complete list of supported sensors and devices from [RFXCOM](http://www.rfxcom.com) and firmware update announcements.
|
||||
See the RFXtrx User Guide from [RFXCOM](http://www.rfxcom.com) for the complete list of supported sensors and devices as well as firmware update announcements.
|
||||
|
||||
|
||||
## Supported Things
|
||||
|
||||
Binding should support RFXtrx433E and RFXtrx315 transceivers and RFXrec433 receiver as bridge for accessing different sensors and actuators.
|
||||
This binding supports the RFXtrx433E and RFXtrx315 transceivers and the RFXrec433 receiver as bridges for accessing different sensors and actuators.
|
||||
|
||||
RFXCOM binding currently supports following packet types:
|
||||
This binding currently supports following packet types:
|
||||
|
||||
* Blinds1
|
||||
* Curtain1
|
||||
|
|
@ -65,11 +65,11 @@ FTDI driver can be enabled by the following command
|
|||
sudo kextunload -b com.apple.driver.AppleUSBFTDI
|
||||
```
|
||||
|
||||
If you meet any problems with JD2XX or you don't want to disable FTDI driver on OS X, you can also configure RFXCOM transceivers/receivers manually.
|
||||
If you have any problems with JD2XX or you don't want to disable FTDI driver on OS X, you can also configure RFXCOM transceivers/receivers manually.
|
||||
|
||||
After bridge is configured and transceiver receives message from any sensor and actuator, device is put in the Inbox. Because RFXCOM communication is one way protocol, receiver actuators can't be discovered automatically.
|
||||
After the bridge is configured and the transceiver receives a message from any sensor or actuator, the device is put in the Inbox. Because RFXCOM communication is a one way protocol, receiver actuators can't be discovered automatically.
|
||||
|
||||
Both bridges and sensor/actuators are easy to configure from the Paper UI. However, a manual configuration looks (thing file) e.g. like
|
||||
Both bridges and sensor/actuators are easy to configure from the Paper UI. However, you can configure things manually in the thing file, for example:
|
||||
|
||||
```
|
||||
Bridge rfxcom:bridge:usb0 [ serialPort="/dev/tty.usbserial-06VVEG1Y" ] {
|
||||
|
|
@ -79,28 +79,28 @@ Bridge rfxcom:bridge:usb0 [ serialPort="/dev/tty.usbserial-06VVEG1Y" ] {
|
|||
|
||||
## Channels
|
||||
|
||||
Currently supported channels:
|
||||
This binding currently supports following channels:
|
||||
|
||||
| Channel Type ID | Item Type | Description |
|
||||
|-----------------|------------------------|--------------|
|
||||
| batterylevel | Number | Battery level. |
|
||||
| command | Switch | Command channel. |
|
||||
| contact | Contact | Contact channel. |
|
||||
| dimminglevel | Dimmer | Dimming level channel. |
|
||||
| mood | Number | Mood channel. |
|
||||
| humidity | Number | Relative humidity level in percentages. |
|
||||
| humiditystatus | String | Current humidity status. |
|
||||
| instantamp | Number | Instant current in Amperes. |
|
||||
| instantpower | Number | Instant power consumption in Watts. |
|
||||
| status | String | Status channel. |
|
||||
| setpoint | Number | Requested temperature. |
|
||||
| mood | Number | Mood channel. |
|
||||
| motion | Switch | Motion detection sensor state. |
|
||||
| rainrate | Number | Rain fall rate in millimeters per hour. |
|
||||
| raintotal | Number | Total rain in millimeters. |
|
||||
| shutter | Rollershutter | Shutter channel. |
|
||||
| instantpower | Number | Instant power consumption in Watts. |
|
||||
| totalusage | Number | Used energy in Watt hours. |
|
||||
| instantamp | Number | Instant current in Amperes. |
|
||||
| totalamphours | Number | Used "energy" in ampere-hours. |
|
||||
| temperature | Number | Current temperature in degree Celsius. |
|
||||
| humidity | Number | Relative humidity level in percentages. |
|
||||
| humiditystatus | String | Current humidity status. |
|
||||
| signallevel | Number | Received signal strength level. |
|
||||
| batterylevel | Number | Battery level. |
|
||||
| windspeed | Number | Average wind speed in meters per second. |
|
||||
| temperature | Number | Current temperature in degree Celsius. |
|
||||
| totalusage | Number | Used energy in Watt hours. |
|
||||
| totalamphours | Number | Used "energy" in ampere-hours. |
|
||||
| winddirection | Number | Wind direction in degrees. |
|
||||
| windspeed | Number | Average wind speed in meters per second. |
|
||||
|
|
|
|||
|
|
@ -8,379 +8,379 @@ layout: documentation
|
|||
|
||||
This is a modernized version of the original icon set of openHAB 1.<br/><br/>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Note that this list also serves as a checklist for code reviews on pull requests
|
|||
|
||||
## D. Runtime Behavior
|
||||
|
||||
14. Overridden methods from abstract classes or interfaces are expected to return fast unless otherwise stated in their JavaDoc. Expensive operations should therefore rather be scheduled as a job.
|
||||
1. Creation of threads must be avoided. Instead, resort into using existing schedulers which use pre-configured thread pools. If there is no suitable scheduler available, start a discussion in the forum about it rather than creating a thread by yourself.
|
||||
1. Overridden methods from abstract classes or interfaces are expected to return fast unless otherwise stated in their JavaDoc. Expensive operations should therefore rather be scheduled as a job.
|
||||
1. Creation of threads must be avoided. Instead, resort into using existing schedulers which use pre-configured thread pools. If there is no suitable scheduler available, start a discussion in the forum about it rather than creating a thread by yourself. For periodically executed jobs that do not require a fixed rate [scheduleWithFixedDelay](http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ScheduledExecutorService.html#scheduleWithFixedDelay(java.lang.Runnable,%20long,%20long,%20java.util.concurrent.TimeUnit)) should be preferred over [scheduleAtFixedRate](http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ScheduledExecutorService.html#scheduleAtFixedRate(java.lang.Runnable,%20long,%20long,%20java.util.concurrent.TimeUnit)).
|
||||
1. Bundles need to cleanly start and stop without throwing exceptions or malfunctioning. This can be tested by manually starting and stopping the bundle from the console (```stop <bundle-id>``` resp. ```start <bundle-id>```).
|
||||
1. Bundles must not require any substantial CPU time. Test this e.g. using "top" or VisualVM and compare CPU utilization with your bundle stopped vs. started.
|
||||
|
|
|
|||
Loading…
Reference in New Issue