Updated external content (Jenkins build 173)

pull/1472/head
openHAB Build Server 2021-01-07 05:22:27 +00:00
parent f0f4273c9d
commit 7ccd4f10c4
12 changed files with 392 additions and 51 deletions

View File

@ -63,10 +63,16 @@ _Note that it is planned to generate some part of this based on the XML files wi
| commCtrlVersion | String | R | Communication Controller Firmware Version
| remoteCtrlVersion | String | R | Remote Controller Firmware Version
| operationMode | String | R/W | The operation mode of the AC unit. Currently supported values: HEAT, COOL.
| fanSpeed | Number | R/W | This is a "virtual channel" : its value is calculated depending on current operation mode. It is the channel to be used to change the fan speed, whatever the current mode is. Fan speed are from 1 to 5. On BRC1H, the device supports 3 speeds: LOW (1), MEDIUM (2-4), MAX (5).
| fanSpeed | Number | R/W | This is a "virtual channel" : its value is calculated depending on current operation mode. It is the channel to be used to change the fan speed, whatever the current mode is. Fan speed are from 1 to 5. On BRC1H, the device supports 3 speeds: LOW (1), MEDIUM (2-4), MAX (5). Some BRC1H also support an AUTO (0) mode - but not all of them support it (depending on internal unit).
| setpoint | Number:Temperature | R/W | This is a "virtual channel" : its value is calculated depending on current operation mode. It is the channel to be used to change the setpoint, whatever the current mode is.
| homekitCurrentHeatingCoolingMode | String | R | This channel is a "virtual channel" to be used with the HomeKit add-on to implement Thermostat thing. Values supported are the HomeKit addon ones: Off, CoolOn, HeatOn, Auto.
| homekitTargetHeatingCoolingMode | String | R/W | This channel is a "virtual channel" to be used with the HomeKit add-on to implement Thermostat thing. Values supported are the HomeKit addon ones: Off, CoolOn, HeatOn, Auto.
| homebridgeMode | String | R/W | This channel is a "virtual channel" to be used with external HomeBridge. Values are: Off, Heating, Cooling, Auto.
| eyeBrightness | Dimmer | R/W | This channel allows to manipulate the Blue "Eye" indicator Brightness. Values are between 0 and 100.
| indoorPowerHours | Number:Time | R | This channel indicates the number of hours the indoor unit has been powered (operating or not).
| indoorOperationHours | Number:Time | R | This channel indicates the number of hours the indoor unit has been operating.
| indoorFanHours | Number:Time | R | This channel indicates the number of hours the fan has been blowing.
| cleanFilterIndicator | Switch | R/W | This channel indicates if the filter needs cleaning. The indicator can be reset by writing "OFF" to the channel.
## Full Example

View File

@ -125,11 +125,13 @@ The `awaySetPoint` defines the temperature in degrees Celsius that will be sent
#### Smart Plug
| Channel | Item Type | Description |
|---------------------|-----------|------------------------------------|
| `currentSignalRSSI` | Number | Relative Signal Strength Indicator |
| `currentSignalLQI` | Number | Link Quality Indicator |
| `zigbeeConnected` | Switch | Is the TRV joined to network |
| Channel | Item Type | Description |
|--------------------------|---------------|--------------------------------------------|
| `currentSignalRSSI` | Number | Relative Signal Strength Indicator |
| `currentSignalLQI` | Number | Link Quality Indicator |
| `zigbeeConnected` | Switch | Is the TRV joined to network |
| `plugInstantaneousPower` | Number:Power | Current Power being drawn through the plug |
| `plugEnergyDelivered` | Number:Energy | Cumulative energy drawn through the plug |
### Command Channels

View File

@ -116,6 +116,16 @@ All values that are not `onValue`, `offValue`, `increaseValue`, `decreaseValue`
All values that are not `onValue`, `offValue`, `increaseValue`, `decreaseValue` are interpreted as brightness 0-100% and need to be numeric only.
### `number`
| parameter | optional | default | description |
|-------------------------|----------|-------------|-------------|
| `unit` | yes | - | The unit label for this channel |
`number` channels can be used for `DecimalType` or `QuantityType` values.
If a unit is given in the `unit` parameter, the binding tries to create a `QuantityType` state before updating the channel, if no unit is present, it creates a `DecimalType`.
Please note that incompatible units (e.g. `°C` for a `Number:Density` item) will fail silently, i.e. no error message is logged even if the state update fails.
### `player`
| parameter | optional | default | description |

View File

@ -113,15 +113,15 @@ rule "LogReader"
end
```
Use the rules with your Telegram Bot (need openHAB Telegram Action installed and configured)
Use the rules with your Telegram Bot (need openHAB Telegram Binding installed and configured)
```xtend
rule "LogReader"
when
Channel 'logreader:reader:openhablog:newErrorEvent' triggered
then
// do something
sendTelegram("bot3", "*ERROR* LogReader Event!\n%s Errors are in the log! Here is the last row of it:\n`%s`", logreaderErrors.state.toString, logreaderLastError.state.toString)
val telegramAction = getActions("telegram","telegram:telegramBot:myBot")
telegramAction.sendTelegram("*ERROR* LogReader Event!\n%s Errors are in the log! Here is the last row of it:\n`%s`", logreaderErrors.state.toString, logreaderLastError.state.toString)
end
```

View File

@ -23,15 +23,15 @@ Through this mapping, in your rules (local server), you can take actions based u
One use of this binding is to distribute your home automation system on multiple openHAB servers.
Another use is for users to interact with older versions of openHAB that may support old openHAB v1 bindings that were not migrated to openHAB v2 or openHAB v3.
They can keep an openHAB v2 server to run their old openHAB v1 bindings and setup a new openHAB v3 server for everything else.
The Remote openHAB binding installed on the openHAB v3 server will then allow to use the openHAB v1 bindings through communication with the openHAB v2 server.
Another use is for users to interact with older versions of openHAB that may support old openHAB v1 bindings that were not migrated to openHAB v2 or openHAB v3.
They can keep an openHAB v2 server to run their old openHAB v1 bindings and setup a new openHAB v3 server for everything else.
The Remote openHAB binding installed on the openHAB v3 server will then allow to use the openHAB v1 bindings through communication with the openHAB v2 server.
A third usage is for users that would like to keep unchanged an existing openHAB v2 server but would like to use the new UI from openHAB v3; they can simply setup a new openHAB v3 server with the Remote openHAB binding linked to their openHAB v2 server.
A third usage is for users that would like to keep unchanged an existing openHAB v2 server but would like to use the new UI from openHAB v3; they can simply setup a new openHAB v3 server with the Remote openHAB binding linked to their openHAB v2 server.
## Supported Things
There is two supported things : the `server` bridge thing representing a remote openHAB server and the `thing` thing representing a thing from the remote openHAB server.
There is two supported things: the `server` bridge thing representing a remote openHAB server and the `thing` thing representing a thing from the remote openHAB server.
## Discovery
@ -44,7 +44,7 @@ Once a bridge thing representing a remote openHAB server is created, all things
## Binding Configuration
The binding has no configuration options, all configuration is done at Thing level.
The binding has no configuration options, all configuration is done at thing level.
## Thing Configuration
@ -68,9 +68,9 @@ The `thing` thing has the following configuration parameters:
| thingUID | yes | The thing UID in the remote openHAB server. |
| buildTriggerChannels | no | If set to true, a trigger channel will be automatically created and linked to each trigger channel from the remote thing. Default is true. |
Please note that if your remote server is an openHAB v3 server, you will need to define a valid token on your bridge thing to have your things correctly initialized.
Please note that if your remote server is an openHAB v3 server, you will need to define a valid token on your bridge thing to have your things correctly initialized.
Setting the `buildTriggerChannels` parameter to false is for the main following advanced usages :
Setting the `buildTriggerChannels` parameter to false is for the main following advanced usages:
* you don't care about the trigger channels of this remote thing and you don't want the binding to create them locally,
* you want to define the trigger channels in your configuration file, and only the channels that you will finally need,
@ -99,7 +99,7 @@ For example, if your remote thing provides a trigger channel with this UID `astr
## Limitations
* The binding will not try to communicate with an openHAB v1 server.
* The binding will not try to communicate with an openHAB v1 server.
## Example

View File

@ -138,11 +138,11 @@ Number:Power TibberAPILiveMaxPower "Max Power Cons
Number:ElectricPotential TibberAPILiveVoltage1 "Live Voltage Phase 1 [V]" {channel="tibber:tibberapi:7cfae492:live_voltage1"}
Number:ElectricPotential TibberAPILiveVoltage2 "Live Voltage Phase 2 [V]" {channel="tibber:tibberapi:7cfae492:live_voltage2"}
Number:ElectricPotential TibberAPILiveVoltage3 "Live Voltage Phase 3 [V]" {channel="tibber:tibberapi:7cfae492:live_voltage3"}
Number:ElectricCurrent TibberAPILiveCurrent1 "Live Current Phase 1 [V]" {channel="tibber:tibberapi:7cfae492:live_current1"}
Number:ElectricCurrent TibberAPILiveCurrent2 "Live Current Phase 2 [V]" {channel="tibber:tibberapi:7cfae492:live_current2"}
Number:ElectricCurrent TibberAPILiveCurrent3 "Live Current Phase 3 [V]" {channel="tibber:tibberapi:7cfae492:live_current3"}
Number:ElectricCurrent TibberAPILiveCurrent1 "Live Current Phase 1 [A]" {channel="tibber:tibberapi:7cfae492:live_current1"}
Number:ElectricCurrent TibberAPILiveCurrent2 "Live Current Phase 2 [A]" {channel="tibber:tibberapi:7cfae492:live_current2"}
Number:ElectricCurrent TibberAPILiveCurrent3 "Live Current Phase 3 [A]" {channel="tibber:tibberapi:7cfae492:live_current3"}
Number:Power TibberAPILivePowerProduction "Live Power Production [W]" {channel="tibber:tibberapi:7cfae492:live_powerProduction"}
Number:Power TibberAPILiveMinPowerproduction "Min Power Production [W]" {channel="tibber:tibberapi:7cfae492:live_minPowerproduction"}
Number:Power TibberAPILiveMaxPowerproduction "Power consumption/production" {channel="tibber:tibberapi:7cfae492:live_maxPowerproduction"}
Number:Power TibberAPILiveMaxPowerproduction "Max Power Production [W]" {channel="tibber:tibberapi:7cfae492:live_maxPowerproduction"}
Number:Energy TibberAPILiveAccumulatedProduction "Accumulated Production [%.2f kWh]" {channel="tibber:tibberapi:7cfae492:live_accumulatedProduction"}
```

View File

@ -78,9 +78,12 @@ Values need to be IPv4 addresses in the format `a.b.c.d`.
This is an optional parameter and multiple values are allowed: add one value per line in the Main User Interface.
If the `PHONEBOOK` profile shall be used, it is necessary to retrieve the phonebooks from the FritzBox.
The `phonebookInterval` is uses to set the refresh cycle for phonebooks. It defaults to 600 seconds,
and it can be set to 0 if phoneooks are not to be used.
The `phonebookInterval` is used to set the refresh cycle for phonebooks.
It defaults to 600 seconds, and it can be set to 0 if phonebooks are not used.
Parameters that accept lists (e.g. `macOnline`, `wanBlockIPs`) can contain comments.
Comments are separated from the value with a '#' (e.g. `192.168.0.77 # Daughter's iPhone`).
The full string is used for the channel label.
### `subdevice`, `subdeviceLan`
@ -92,16 +95,13 @@ by examining the SCPD of the root device, the simplest way to obtain it is throu
Auto discovery may find several sub-devices, each one holding channels as described in the following.
The LAN sub-device, in particular, is also used for presence detection.
It therefore optionally contains
a channel for each MAC address (in a format 11:11:11:11:11:11, different than the old v1 version of this binding),
defined by the parameter `macOnline`.
This is an optional parameter and multiple values are allowed: add one value per line in the Main User Interface.
It therefore optionally contains a channel for each MAC address (in a format 11:11:11:11:11:11, different than the old v1 version of this binding), defined by the parameter `macOnline`.
## Channels
Channels are grouped according to the subdevice they belong to.
### fritzbox Bridge channels
### `fritzbox` bridge channels
Advanced channels appear only if the corresponding parameters are set in the Thing definition.
@ -120,7 +120,11 @@ Advanced channels appear only if the corresponding parameters are set in the Thi
| `tamNewMessages` | `Number` | x | The number of new messages of the given answering machine. |
| `uptime` | `Number:Time` | | Uptime of the device |
### LAN subdeviceLan channels
Call lists are provided via the `callList` channel for one or more days (as configured) as JSON.
The JSON consists of an array of individual calls with the fields `date`, `type`, `localNumber`, `remoteNumber`, `duration`.
The call-types are the same as provided by the FritzBox, i.e. `1` (inbound), `2` (missed), `3` (outbound), `10` (rejected).
### LAN `subdeviceLan` channels
| channel | item-type | advanced | description |
|----------------------------|---------------------------|:--------:|----------------------------------------------------------------|
@ -129,7 +133,10 @@ Advanced channels appear only if the corresponding parameters are set in the Thi
| `wifiGuestEnable` | `Switch` | | Enable/Disable the guest WiFi. |
| `macOnline` | `Switch` | x | Online status of the device with the given MAC |
### WANConnection subdevice channels
Older FritzBox devices may not support 5 GHz WiFi.
In this case you have to use the `wifi5GHzEnable` channel for switching the guest WiFi.
### WANConnection `subdevice` channels
| channel | item-type | advanced | description |
|----------------------------|---------------------------|:--------:|----------------------------------------------------------------|
@ -140,7 +147,7 @@ Advanced channels appear only if the corresponding parameters are set in the Thi
| `wanIpAddress` | `String` | x | WAN IP Address |
| `wanPppIpAddress` | `String` | x | WAN IP Address (if using PPP) |
### WAN subdevice channels
### WAN `subdevice` channels
| channel | item-type | advanced | description |
|----------------------------|---------------------------|:--------:|----------------------------------------------------------------|
@ -163,17 +170,6 @@ Advanced channels appear only if the corresponding parameters are set in the Thi
| `wanPhysicalLinkStatus` | `String` | x | Link Status |
| `wanTotalBytesReceived` | `Number:DataAmount` | x | Total Bytes Received |
| `wanTotalBytesSent` | `Number:DataAmount` | x | Total Bytes Sent |
Parameters that accept lists (e.g. `macOnline`, `wanBlockIPs`) can contain comments.
Comments are separated from the value with a '#' (e.g. `192.168.0.77 # Daughter's iPhone`).
The full string is used for the channel label.
### Channel `callList`
Call lists are provided for one or more days (as configured) as JSON.
The JSON consists of an array of individual calls with the fields `date`, `type`, `localNumber`, `remoteNumber`, `duration`.
The call-types are the same as provided by the FritzBox, i.e. `1` (inbound), `2` (missed), `3` (outbound), `10` (rejected).
## `PHONEBOOK` Profile

View File

@ -98,7 +98,284 @@ Thing wifiled:wifiled:F0FE6B19CB2A [ ip="192.168.178.91", port=5577, pollingPeri
wifiled.items:
```
Switch MyWiFiLight_power "Power" (Light) {channel="wifiled:wifiled:F0FE6B19CB2A:power"}
Dimmer MyWiFiLight_white "White" (Light) {channel="wifiled:wifiled:F0FE6B19CB2A:white"}
Color MyWiFiLight_color "Color" (Light) {channel="wifiled:wifiled:F0FE6B19CB2A:color"}
Switch MyWiFiLight_power "Power" (Light) {channel="wifiled:wifiled:F0FE6B19CB2A:power"}
Dimmer MyWiFiLight_white "White" (Light) {channel="wifiled:wifiled:F0FE6B19CB2A:white"}
Color MyWiFiLight_color "Color" (Light) {channel="wifiled:wifiled:F0FE6B19CB2A:color"}
Dimmer MyWiFiLight_speed "Speed_LED" (Light) {channel="wifiled:wifiled:F0FE6B19CB2A:programSpeed"}
String LED_1_program "LED 1 Preset [MAP(led_program.map):%s]" <menu> {channel="wifiled:wifiled:F0FE6B19CB2A:program"}
Switch LED_1_preset_0 "Strobe" <smoke> (LEDPresets1) // Mode: 48
Switch LED_1_preset_1 "Strobe - Custom 1" <smoke> (LEDPresets1) // Mode: 96
Switch LED_1_preset_2 "Strobe - Red" <smoke> (LEDPresets1) // Mode: 49
Switch LED_1_preset_3 "Strobe - Green" <smoke> (LEDPresets1) // Mode: 50
Switch LED_1_preset_4 "Strobe - Blue" <smoke> (LEDPresets1) // Mode: 51
Switch LED_1_preset_5 "Strobe - Cyan" <smoke> (LEDPresets1) // Mode: 53
Switch LED_1_preset_6 "Strobe - Purple" <smoke> (LEDPresets1) // Mode: 54
Switch LED_1_preset_7 "Strobe - Yellow" <smoke> (LEDPresets1) // Mode: 52
Switch LED_1_preset_8 "Strobe - White" <smoke> (LEDPresets1) // Mode: 55
Switch LED_1_preset_9 "Strobe - R/G/B" <smoke> (LEDPresets1) // Mode: 57
Switch LED_1_preset_10 "CrossFade - Red/Green" <flow> (LEDPresets1) // Mode: 45
Switch LED_1_preset_11 "CrossFade - Red/Blue" <flow> (LEDPresets1) // Mode: 46
Switch LED_1_preset_12 "CrossFade - Blue/Green" <flow> (LEDPresets1) // Mode: 47
Switch LED_1_preset_13 "Fade" <colorlight> (LEDPresets1) // Mode: 37
Switch LED_1_preset_14 "Fade - White" <colorlight> (LEDPresets1) // Mode: 44
Switch LED_1_preset_15 "Fade - Green" <colorlight> (LEDPresets1) // Mode: 39
Switch LED_1_preset_16 "Fade - DarkBlue" <colorlight> (LEDPresets1) // Mode: 40
Switch LED_1_preset_17 "Fade - Giallo" <colorlight> (LEDPresets1) // Mode: 41
Switch LED_1_preset_18 "Fade - Red" <colorlight> (LEDPresets1) // Mode: 38
Switch LED_1_preset_19 "Fade - LightBlue" <colorlight> (LEDPresets1) // Mode: 42
Switch LED_1_preset_20 "Fade - Purple" <colorlight> (LEDPresets1) // Mode: 43
Switch LED_1_preset_21 "Fade - R/G/B" <colorlight> (LEDPresets1) // Mode: 45
Switch LED_1_preset_22 "Jump" <chart> (LEDPresets1) // Mode: 56
Switch LED_1_preset_23 "Jump - R/G/B" <chart> (LEDPresets1) // Mode: 99
```
wifiled.sitemap
```
sitemap wifiled label="LED Sitemap"
{
Frame {
Switch item=MyWiFiLight_power
Colorpicker item=MyWiFiLight_color visibility=[MyWiFiLight_power==ON]
Slider item=MyWiFiLight_white visibility=[MyWiFiLight_power==ON]
Slider item=MyWiFiLight_speed visibility=[MyWiFiLight_power==ON]
Selection item=LED_1_program visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_0 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_1 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_2 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_3 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_4 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_5 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_6 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_7 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_8 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_9 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_10 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_11 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_12 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_13 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_14 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_15 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_16 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_17 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_18 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_19 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_20 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_21 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_22 visibility=[MyWiFiLight_power==ON]
Switch item=LED_1_preset_23 visibility=[MyWiFiLight_power==ON]
}
}
```
led_program.map
```
-=Undefined
NULL=Undefined
48=Strobe
49=Strobe - Red
50=Strobe - Green
51=Strobe - Blue
52=Strobe - Yellow
53=Strobe - Cyan
54=Strobe - Purple
55=Strobe - White
57=Strobe - R/G/B
96=Strobe - Custom 1
45=CrossFade - Red/Green
46=CrossFade - Red/Blue
47=CrossFade - Blue/Green
37=Fade
38=Fade - Red
39=Fade - Green
40=Fade - DarkBlue
41=Fade - Yellow
42=Fade - LightBlue
43=Fade - Purple
44=Fade - White
45=Fade - R/G/B
56=Jump
99=Jump - R/G/B
97=Color (no preset selected)
```
wifiled.rules
```
rule "Program - Strobe"
when Item LED_1_preset_0 received command ON
then
LED_1_program.sendCommand(48)
LED_1_preset_0.sendCommand(OFF)
end
rule "Program - Strobe - Custom 1"
when Item LED_1_preset_1 received command ON
then
LED_1_program.sendCommand(96)
LED_1_preset_1.sendCommand(OFF)
end
rule "Program - Strobe - Red"
when Item LED_1_preset_2 received command ON
then
LED_1_program.sendCommand(49)
LED_1_preset_2.sendCommand(OFF)
end
rule "Program - Strobe - Green"
when Item LED_1_preset_3 received command ON
then
LED_1_program.sendCommand(50)
LED_1_preset_3.sendCommand(OFF)
end
rule "Program - Strobe - Blue"
when Item LED_1_preset_4 received command ON
then
LED_1_program.sendCommand(51)
LED_1_preset_4.sendCommand(OFF)
end
rule "Program - Strobe - Cyan"
when Item LED_1_preset_5 received command ON
then
LED_1_program.sendCommand(53)
LED_1_preset_5.sendCommand(OFF)
end
rule "Program - Strobe - Purple"
when Item LED_1_preset_6 received command ON
then
LED_1_program.sendCommand(54)
LED_1_preset_6.sendCommand(OFF)
end
rule "Program - Strobe - Yellow"
when Item LED_1_preset_7 received command ON
then
LED_1_program.sendCommand(52)
LED_1_preset_7.sendCommand(OFF)
end
rule "Program - Strobe - White"
when Item LED_1_preset_8 received command ON
then
LED_1_program.sendCommand(55)
LED_1_preset_8.sendCommand(OFF)
end
rule "Program - Strobe - R/G/B"
when Item LED_1_preset_9 received command ON
then
LED_1_program.sendCommand(57)
LED_1_preset_9.sendCommand(OFF)
end
rule "Program - CrossFade - Red/Green"
when Item LED_1_preset_10 received command ON
then
LED_1_program.sendCommand(45)
LED_1_preset_10.sendCommand(OFF)
end
rule "Program - CrossFade - Red/Blue"
when Item LED_1_preset_11 received command ON
then
LED_1_program.sendCommand(46)
LED_1_preset_11.sendCommand(OFF)
end
rule "Program - CrossFade - Blue/Green"
when Item LED_1_preset_12 received command ON
then
LED_1_program.sendCommand(47)
LED_1_preset_12.sendCommand(OFF)
end
rule "Program - Fade"
when Item LED_1_preset_13 received command ON
then
LED_1_program.sendCommand(37)
LED_1_preset_13.sendCommand(OFF)
end
rule "Program - Fade - White"
when Item LED_1_preset_14 received command ON
then
LED_1_program.sendCommand(44)
LED_1_preset_14.sendCommand(OFF)
end
rule "Program - Fade - Green"
when Item LED_1_preset_15 received command ON
then
LED_1_program.sendCommand(39)
LED_1_preset_15.sendCommand(OFF)
end
rule "Program - Fade - DarkBlue"
when Item LED_1_preset_16 received command ON
then
LED_1_program.sendCommand(40)
LED_1_preset_16.sendCommand(OFF)
end
rule "Program - Fade - Yellow"
when Item LED_1_preset_17 received command ON
then
LED_1_program.sendCommand(41)
LED_1_preset_17.sendCommand(OFF)
end
rule "Program - Fade - Red"
when Item LED_1_preset_18 received command ON
then
LED_1_program.sendCommand(38)
LED_1_preset_18.sendCommand(OFF)
end
rule "Program - Fade - LightBlue"
when Item LED_1_preset_19 received command ON
then
LED_1_program.sendCommand(42)
LED_1_preset_19.sendCommand(OFF)
end
rule "Program - Fade - Purple"
when Item LED_1_preset_20 received command ON
then
LED_1_program.sendCommand(43)
LED_1_preset_20.sendCommand(OFF)
end
rule "Program - Fade - R/G/B"
when Item LED_1_preset_21 received command ON
then
LED_1_program.sendCommand(45)
LED_1_preset_21.sendCommand(OFF)
end
rule "Program - Jump"
when Item LED_1_preset_22 received command ON
then
LED_1_program.sendCommand(56)
LED_1_preset_22.sendCommand(OFF)
end
rule "Program - Jump - R/G/B"
when Item LED_1_preset_23 received command ON
then
LED_1_program.sendCommand(99)
LED_1_preset_23.sendCommand(OFF)
end
```

View File

@ -67,7 +67,7 @@ when
Item Xi_Leak changed
then
if(Xi_Leak.state == ON) {
val actions = getActions("xmpp","xmppclient:xmppBridge:xmpp")
val actions = getActions("xmppclient","xmppclient:xmppBridge:xmpp")
actions.publishXMPP("pavel@example.com","Warning! Leak detected!")
}
end
@ -80,7 +80,7 @@ rule "Turn off all lights without separator"
when
Channel "xmppclient:xmppBridge:xmpp:xmpp_command" triggered
then
var actionName = receivedEvent.getEvent()
var actionName = receivedEvent
if(actionName.toLowerCase() == "turn off lights") {
Group_Light_Home_All.sendCommand(OFF)
}
@ -90,11 +90,11 @@ rule "Turn off all lights with separator and reply"
when
Channel "xmppclient:xmppBridge:xmpp:xmpp_command" triggered
then
var actionName = receivedEvent.getEvent().split("##")
var actionName = receivedEvent.split("##")
if(actionName.get(1).toLowerCase() == "turn off lights") {
Group_Light_Home_All.sendCommand(OFF)
val actions = getActions("xmpp","xmppclient:xmppBridge:xmpp")
val actions = getActions("xmppclient","xmppclient:xmppBridge:xmpp")
actions.publishXMPP(actionName.get(0),"All lights was turned off")
}
end

View File

@ -24,6 +24,11 @@
<channel id="homekitCurrentHeatingCoolingMode" typeId="brc1h_homekitCurrentHeatingCoolingMode"/>
<channel id="homekitTargetHeatingCoolingMode" typeId="brc1h_homekitTargetHeatingCoolingMode"/>
<channel id="homebridgeMode" typeId="brc1h_homebridgeMode"/>
<channel id="eyeBrightness" typeId="brc1h_eyeBrightness"/>
<channel id="indoorPowerHours" typeId="brc1h_indoorPowerHours"/>
<channel id="indoorOperationHours" typeId="brc1h_indoorOperationHours"/>
<channel id="indoorFanHours" typeId="brc1h_indoorFanHours"/>
<channel id="cleanFilterIndicator" typeId="brc1h_cleanFilter"/>
</channels>
<config-description>
@ -52,6 +57,11 @@
<label>Unit Power Status</label>
</channel-type>
<channel-type id="brc1h_cleanFilter">
<item-type>Switch</item-type>
<label>Clean Filter Indicator</label>
</channel-type>
<channel-type id="brc1h_indoorTemperature">
<item-type>Number:Temperature</item-type>
<label>Indoor Temperature</label>
@ -129,4 +139,28 @@
</command>
</channel-type>
<channel-type id="brc1h_eyeBrightness">
<item-type>Dimmer</item-type>
<label>Eye Illumination Brightness</label>
<state min="0" max="100" step="1" readOnly="false"/>
</channel-type>
<channel-type id="brc1h_indoorPowerHours">
<item-type>Number:Time</item-type>
<label>Number of hours system has been powered up</label>
<state readOnly="true"/>
</channel-type>
<channel-type id="brc1h_indoorOperationHours">
<item-type>Number:Time</item-type>
<label>Number of hours system has been operating</label>
<state readOnly="true"/>
</channel-type>
<channel-type id="brc1h_indoorFanHours">
<item-type>Number:Time</item-type>
<label>Number of hours fan has been operating</label>
<state readOnly="true"/>
</channel-type>
</thing:thing-descriptions>

View File

@ -219,6 +219,8 @@
<channel id="zigbeeConnected" typeId="zigbeeConnected-channel"/>
<channel id="deviceLocked" typeId="deviceLocked-channel"/>
<channel id="manualModeState" typeId="manualModeState-channel"/>
<channel id="plugInstantaneousPower" typeId="plugInstantaneousPower-channel"/>
<channel id="plugEnergyDelivered" typeId="plugEnergyDelivered-channel"/>
</channels>
<representation-property>serialNumber</representation-property>
@ -429,4 +431,18 @@
<description>Should the room pre-heat to achieve the desired temperature</description>
</channel-type>
<channel-type id="plugInstantaneousPower-channel">
<item-type>Number:Power</item-type>
<label>Plug Instantaneous Power</label>
<description>Current Power being drawn through the plug</description>
<state readOnly="true" pattern="%d %unit%"/>
</channel-type>
<channel-type id="plugEnergyDelivered-channel">
<item-type>Number:Energy</item-type>
<label>Plug Energy Delivered</label>
<description>Cumulative energy drawn through the plug</description>
<state readOnly="true" pattern="%d %unit%"/>
</channel-type>
</thing:thing-descriptions>

View File

@ -142,7 +142,7 @@
<channel-type id="number">
<item-type>Number</item-type>
<label>Number Channel</label>
<config-description-ref uri="channel-type:http:channel-config"/>
<config-description-ref uri="channel-type:http:channel-config-number"/>
</channel-type>
<channel-type id="player">