Updated external content (Jenkins build 353)
openHAB Build Server
parent
a7a18b6523
commit
fc7fc0ddc3
|
|
@ -3,7 +3,7 @@ id: automower
|
|||
label: Automower
|
||||
title: Automower - Bindings
|
||||
type: binding
|
||||
description: "This binding communicates to the Husqvarna Automower Connect API in order to send commands and query the state of Husqvarna Automower robots."
|
||||
description: "This is the binding for [Husqvarna Automower a robotic lawn mowers](https://www.husqvarna.com/uk/products/robotic-lawn-mowers/)."
|
||||
since: 3x
|
||||
install: auto
|
||||
---
|
||||
|
|
@ -14,27 +14,27 @@ install: auto
|
|||
|
||||
# Automower Binding
|
||||
|
||||
This binding communicates to the Husqvarna Automower Connect API in order to send commands and query the state of Husqvarna Automower robots.
|
||||
This is the binding for [Husqvarna Automower a robotic lawn mowers](https://www.husqvarna.com/uk/products/robotic-lawn-mowers/).
|
||||
This binding allows you to integrate, view and control Automower lawn mowers in the openHAB environment.
|
||||
|
||||
## Supported Things
|
||||
|
||||
`bridge:` The bridge needs to be configured with credentials and an application key that allows communicating with the Automower Connect Api
|
||||
`bridge:` The bridge needs to be configured with credentials and an application key that allows communicating with the Automower Connect API
|
||||
|
||||
`automower:` A single Husqvarna Automower robot
|
||||
|
||||
Basically all Husqvarna Automower models with "Automower Connect" support should be supported. It was tested only with a Husqvarna Automower 450X
|
||||
All Husqvarna Automower models with "Automower Connect" should be supported. It was tested only with a Husqvarna Automower 430X and 450X.
|
||||
|
||||
|
||||
## Discovery
|
||||
|
||||
Once the bridge is created and configured, registered automowers will be discovered automatically
|
||||
|
||||
Once the bridge is created and configured, OpenHab will automatically discover all Automowers registered on your account.
|
||||
|
||||
## Thing Configuration
|
||||
|
||||
`bridge:`
|
||||
|
||||
- appKey (mandatory): The Application Key is required to communication with the Automower Connect Api. It can be obtained by registering an Application on the Husqvarna Website. This application also needs to be connected to the "Authentication API" and the "Automower Connect API"
|
||||
- appKey (mandatory): The Application Key is required to communicate with the Automower Connect API. It can be obtained by registering an Application on [the Husqvarna Website](https://developer.husqvarnagroup.cloud/). This application also needs to be connected to the ["Authentication API" and the "Automower Connect API"](https://developer.husqvarnagroup.cloud/docs/getting-started)
|
||||
- userName (mandatory): The user name for which the application key has been issued
|
||||
- password (mandatory): The password for the given user
|
||||
- pollingInterval (optional): How often the bridge state should be queried in seconds. Default is 1h (3600s)
|
||||
|
|
@ -48,23 +48,31 @@ With the default value of 1h this would mean ~720 requests per month for the bri
|
|||
- mowerId (mandatory): The Id of an automower as used by the Automower Connect Api to identify a mower. This is automatically filled when the thing is discovered
|
||||
- pollingInterval (optional): How often the current automower state should be polled in seconds. Default is 10min (600s)
|
||||
|
||||
Keep in mind that the status of the automowers should not be queried too often.
|
||||
According to the Husqvarna documentation not more than 10000 requests per month and application key are allowed.
|
||||
With the default value of 10min this would mean ~4300 requests per month per automower
|
||||
Keep in mind that the status of the Automowers should not be queried too often.
|
||||
According to the Husqvarna documentation, no more than 10000 requests per month and application key are allowed.
|
||||
With the default value of 10min this would mean ~4300 requests per month per single Automower
|
||||
|
||||
## Channels
|
||||
|
||||
|
||||
| channel | type | description |
|
||||
|-----------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| name | String | (readonly) The name of the Automower |
|
||||
| mode | String | (readonly) The current mode (MAIN_AREA, SECONDARY_AREA, HOME, DEMO, UNKNOWN) |
|
||||
| activity | String | (readonly) The current activity (UNKNOWN, NOT_APPLICABLE, MOWING, GOING_HOME, CHARGING, LEAVING, PARKED_IN_CS, STOPPED_IN_GARDEN) |
|
||||
| state | String | (readonly) The current state (UNKNOWN, NOT_APPLICABLE, PAUSED, IN_OPERATION, WAIT_UPDATING, WAIT_POWER_UP, RESTRICTED, OFF, STOPPED, ERROR, FATAL_ERROR, ERROR_AT_POWER_UP) |
|
||||
| last-update | DateTime | (readonly) The time when the automower updated its states |
|
||||
| battery | Number | (readonly) The battery state of charge in percent |
|
||||
| error-code | Number | (readonly) The current error code |
|
||||
| error-timestamp | DateTime | (readonly) The timestamp when the current error occurred |
|
||||
| channel | type | access mode | description |
|
||||
|-------------------------|----------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| mower-status#mode | String | R | The current mode (MAIN_AREA, SECONDARY_AREA, HOME, DEMO, UNKNOWN) |
|
||||
| mower-status#activity | String | R | The current activity (UNKNOWN, NOT_APPLICABLE, MOWING, GOING_HOME, CHARGING, LEAVING, PARKED_IN_CS, STOPPED_IN_GARDEN) |
|
||||
| mower-status#state | String | R | The current state (UNKNOWN, NOT_APPLICABLE, PAUSED, IN_OPERATION, WAIT_UPDATING, WAIT_POWER_UP, RESTRICTED_NONE, RESTRICTED_WEEK_SCHEDULE, RESTRICTED_PARK_OVERRIDE, RESTRICTED_SENSOR, RESTRICTED_DAILY_LIMIT, OFF, STOPPED, ERROR, FATAL_ERROR, ERROR_AT_POWER_UP) |
|
||||
| mower-status#last-update | DateTime | R | The time when the automower updated its states |
|
||||
| mower-status#battery | Number | R | The battery state of charge in percent |
|
||||
| mower-status#error-code | Number | R | The current error code |
|
||||
| mower-status#error-timestamp | DateTime | R | The timestamp when the current error occurred |
|
||||
| mower-status#planner-next-start | DateTime | R | The time for the next auto start. If the mower is charging then the value is the estimated time when it will be leaving the charging station. If the mower is about to start now, the value is NULL. |
|
||||
| mower-status#planner-override-action | String | R | The action that overrides current planner operation. |
|
||||
| mower-status#calendar-tasks | String | R | The JSON with the information about Automower planner. |
|
||||
| mower#start | Number | W | Starts the automower for a duration |
|
||||
| mower#resume_schedule | Switch | W | Resumes the Automower schedule |
|
||||
| mower#pause | Switch | W | Pause the Automower |
|
||||
| mower#park | Number | W | Park the Automower for a duration |
|
||||
| mower#park_until_next_schedule | Switch | W | Park the Automower until next schedule |
|
||||
| mower#park_until_further_notice | Switch | W | Park the Automower until further notice. |
|
||||
|
||||
|
||||
## Actions
|
||||
|
|
@ -93,19 +101,23 @@ The following actions are available for `automower`things:
|
|||
|
||||
### automower.items
|
||||
|
||||
String Automower_Name "Name" { channel="automower:automower:mybridge:myAutomower:name" }
|
||||
String Automower_Mode "Mode" { channel="automower:automower:mybridge:myAutomower:mode" }
|
||||
String Automower_Activity "Activity" { channel="automower:automower:mybridge:myAutomower:activity" }
|
||||
String Automower_State "State" { channel="automower:automower:mybridge:myAutomower:state" }
|
||||
DateTime Automower_Last_Update "Last Update" { channel="automower:automower:mybridge:myAutomower:last-update" }
|
||||
Number Automower_Battery "Battery" { channel="automower:automower:mybridge:myAutomower:battery" }
|
||||
Number Automower_Error_Code "Error Code" { channel="automower:automower:mybridge:myAutomower:error-code" }
|
||||
DateTime Automower_Error_Time "Error Time" { channel="automower:automower:mybridge:myAutomower:error-timestamp" }
|
||||
String Automower_Mode "Mode [%s]" { channel="automower:automower:mybridge:myAutomower:mower-status#mode" }
|
||||
String Automower_Activity "Activity [%s]" { channel="automower:automower:mybridge:myAutomower:mower-status#activity" }
|
||||
String Automower_State "State [%s]" { channel="automower:automower:mybridge:myAutomower:mower-status#state" }
|
||||
DateTime Automower_Last_Update "Last Update" { channel="automower:automower:mybridge:myAutomower:mower-status#last-update" }
|
||||
Number Automower_Battery "Battery [%d %%]" { channel="automower:automower:mybridge:myAutomower:mower-status#battery" }
|
||||
Number Automower_Error_Code "Error Code [%d]" { channel="automower:automower:mybridge:myAutomower:mower-status#error-code" }
|
||||
DateTime Automower_Error_Time "Error Time" { channel="automower:automower:mybridge:myAutomower:mower-status#error-timestamp" }
|
||||
String Automower_Override_Action "Override Action [%s]" { channel="automower:automower:mybridge:myAutomower:mower-status#planner-override-action" }
|
||||
DateTime Automower_Next_Start_Time "Next Start Time" { channel="automower:automower:mybridge:myAutomower:mower-status#planner-next-start" }
|
||||
String Automower_Calendar_Tasks "Planned Tasks [%s]" { channel="automower:automower:mybridge:myAutomower:mower-status#calendar-tasks" }
|
||||
|
||||
|
||||
String Automower_Command "Command" { channel="automower:automower:mybridge:myAutomower:command" }
|
||||
Number Automower_Command_Duration "Command Duration" { channel="automower:automower:mybridge:myAutomower:command-duration" }
|
||||
String Automower_Command_Response "Command Response" { channel="automower:automower:mybridge:myAutomower:command-response" }
|
||||
Number Automower_Command_Start "Start mowing for duration [%d min]" { channel="automower:automower:mybridge:myAutomower:mower#start" }
|
||||
Switch Automower_Command_Resume "Resume the schedule" { channel="automower:automower:mybridge:myAutomower:mower#resume_schedule" }
|
||||
Switch Automower_Command_Pause "Pause the automower" { channel="automower:automower:mybridge:myAutomower:mower#pause" }
|
||||
Number Automower_Command_Park "Park for duration [%d min]" { channel="automower:automower:mybridge:myAutomower:mower#park" }
|
||||
Switch Automower_Command_Park_Next_Schedule "Park until next schedule" { channel="automower:automower:mybridge:myAutomower:mower#park_until_next_schedule" }
|
||||
Switch Automower_Command_Park_Notice "Park until further notice" { channel="automower:automower:mybridge:myAutomower:mower#park_until_further_notice" }
|
||||
|
||||
### automower.sitemap
|
||||
|
||||
|
|
@ -114,7 +126,6 @@ The following actions are available for `automower`things:
|
|||
sitemap demo label="Automower"
|
||||
{
|
||||
Frame {
|
||||
Text item=Automower_Name
|
||||
Text item=Automower_Mode
|
||||
Text item=Automower_Activity
|
||||
Text item=Automower_State
|
||||
|
|
@ -122,6 +133,9 @@ sitemap demo label="Automower"
|
|||
Text item=Automower_Battery
|
||||
Text item=Automower_Error_Code
|
||||
Text item=Automower_Error_Time
|
||||
Text item=Automower_Override_Action
|
||||
Text item=Automower_Next_Start_Time
|
||||
Text item=Automower_Calendar_Tasks
|
||||
}
|
||||
}
|
||||
```
|
||||
|
|
|
|||
|
|
@ -63,6 +63,9 @@ For the BRP072A42 and BRP072C42:
|
|||
| cmpfrequency | The compressor frequency |
|
||||
| specialmode | The special mode currently active (OFF, STREAMER, ECO, POWERFUL, POWERFUL & STREAMER, ECO & STREAMER). Not all modes might be available on the unit. |
|
||||
| specialmode-powerful | Turns the powerful mode on/off for the air conditioning unit. |
|
||||
| energyheatingtoday | The energy consumption when heating for today |
|
||||
| energyheatingthisweek | The energy consumption when heating for this week |
|
||||
| energyheatinglastweek | The energy consumption when heating for last week |
|
||||
| energyheatingcurrentyear-1 | The energy consumption when heating for current year January |
|
||||
| energyheatingcurrentyear-2 | The energy consumption when heating for current year February |
|
||||
| energyheatingcurrentyear-3 | The energy consumption when heating for current year March |
|
||||
|
|
@ -75,6 +78,9 @@ For the BRP072A42 and BRP072C42:
|
|||
| energyheatingcurrentyear-10| The energy consumption when heating for current year October |
|
||||
| energyheatingcurrentyear-11| The energy consumption when heating for current year November |
|
||||
| energyheatingcurrentyear-12| The energy consumption when heating for current year December |
|
||||
| energycoolingtoday | The energy consumption when cooling for today |
|
||||
| energycoolingthisweek | The energy consumption when cooling for this week |
|
||||
| energycoolinglastweek | The energy consumption when cooling for last week |
|
||||
| energycoolingcurrentyear-1 | The energy consumption when cooling for current year January |
|
||||
| energycoolingcurrentyear-2 | The energy consumption when cooling for current year February |
|
||||
| energycoolingcurrentyear-3 | The energy consumption when cooling for current year March |
|
||||
|
|
|
|||
|
|
@ -146,7 +146,9 @@ then
|
|||
end
|
||||
|
||||
```
|
||||
|
||||
dwdunwetter_de.map
|
||||
|
||||
```
|
||||
ON=aktiv
|
||||
OFF=inaktiv
|
||||
|
|
@ -165,8 +167,6 @@ NULL=undefiniert
|
|||
UNDEF=undefiniert
|
||||
```
|
||||
|
||||
|
||||
|
||||
dwdunwetter_urgency_de.map
|
||||
|
||||
```
|
||||
|
|
|
|||
|
|
@ -264,8 +264,6 @@ After a location message received from the tracker the log should contain these
|
|||
2018-10-05 09:27:58.794 [TRACE] [cker.internal.handler.TrackerHandler] - System uses SI measurement units. No conversion is needed.
|
||||
```
|
||||
|
||||
**Note**: If the binding was restarted or the distance channel is new (this is the first location message for the channel) only the second location update will trigger event as the binding has to know the previous state.
|
||||
|
||||
### External Region and Presence Switch
|
||||
|
||||
Assumptions:
|
||||
|
|
|
|||
|
|
@ -809,7 +809,12 @@ end
|
|||
This binding integrates with the legacy Lutron RadioRA (Classic) lighting system.
|
||||
|
||||
This binding depends on RS232 communication.
|
||||
It has only been tested using the Chronos time module but the RS232 module should work as well.
|
||||
It has only been tested using the Chronos System Bridge and Timeclock (RA-SBT-CHR) module, but Lutron's RA-RS232 or RB-RS232 module should work as well.
|
||||
|
||||
Support has been added for bridged RadioRA systems.
|
||||
A system is considered “bridged” when a Chronos System Bridge and Timeclock is used to integrate two RadioRA Systems in a single residence.
|
||||
In a bridged system, the `system` parameter of each configured ra-dimmer, ra-switch, or ra-phantomButton thing should be set to indicate which RadioRA system it is a part of (i.e. 1 or 2).
|
||||
In a non-bridged system, these parameters should be left at their default of 0.
|
||||
|
||||
## Supported Things
|
||||
|
||||
|
|
@ -823,17 +828,20 @@ This binding currently supports the following thing types:
|
|||
| ra-phantomButton | Thing | Phantom Button to control multiple controls (Scenes) |
|
||||
|
||||
|
||||
## Thing Configurations
|
||||
## Thing Configuration Parameters
|
||||
|
||||
| Thing | Config | Description |
|
||||
|------------------|--------------|-----------------------------------------------------------------------|
|
||||
| ra-rs232 | portName | The serial port to use to communicate with Chronos or RS232 module |
|
||||
| | baud | (Optional) Baud Rate (defaults to 9600) |
|
||||
| ra-dimmer | zoneNumber | Assigned Zone Number within the Lutron RadioRA system |
|
||||
| | fadeOutSec | (Optional) Time in seconds dimmer should take when lowering the level |
|
||||
| | fadeInSec | (Optional) Time in seconds dimmer should take when lowering the level |
|
||||
| ra-switch | zoneNumber | Assigned Zone Number within the Lutron RadioRA system |
|
||||
| ra-phantomButton | buttonNumber | Phantom Button Number within the Lutron RadioRA system |
|
||||
| Thing | Parameter | Description |
|
||||
|------------------|--------------|------------------------------------------------------------------------|
|
||||
| ra-rs232 | portName | The serial port to use to communicate with Chronos or RS232 module |
|
||||
| | baud | (Optional) Baud Rate (defaults to 9600) |
|
||||
| ra-dimmer | zoneNumber | Assigned Zone Number within the Lutron RadioRA system |
|
||||
| | system | (Optional) System number (1 or 2) in a bridged system. Default=0 (n/a) |
|
||||
| | fadeOutSec | (Optional) Time in seconds dimmer should take when lowering the level |
|
||||
| | fadeInSec | (Optional) Time in seconds dimmer should take when lowering the level |
|
||||
| ra-switch | zoneNumber | Assigned Zone Number within the Lutron RadioRA system |
|
||||
| | system | (Optional) System number (1 or 2) in a bridged system. Default=0 (n/a) |
|
||||
| ra-phantomButton | buttonNumber | Phantom Button Number within the Lutron RadioRA system |
|
||||
| | system | (Optional) System number (1 or 2) in a bridged system. Default=0 (n/a) |
|
||||
|
||||
## Channels
|
||||
|
||||
|
|
|
|||
|
|
@ -47,6 +47,10 @@ Currently the binding does not support any Channels.
|
|||
|
||||
All actions return a `Boolean` value to indicate if the message was sent successfully or not.
|
||||
The parameter `message` is **mandatory**, the `title` parameter defaults to whatever value you defined in the `title` related configuration parameter.
|
||||
Parameters declared as `@Nullable` are not optional.
|
||||
One has to pass a `null` value if it should be skipped or the default value for it should be used.
|
||||
|
||||
- `sendMessage(String message, @Nullable String title, @Nullable String sound, @Nullable String url, @Nullable String urlTitle, @Nullable String attachment, @Nullable String contentType, @Nullable Integer priority, @Nullable String device)` - This method is used to send a plain text message providing all available parameters.
|
||||
|
||||
- `sendMessage(String message, @Nullable String title)` - This method is used to send a plain text message.
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,186 @@
|
|||
# Shelly Manager
|
||||
|
||||
The Shelly Manager is a small extension to the binding, which provides some low level information on the Shelly Devices, but also provides some functions to manage the devices.
|
||||
|
||||
To open the Shelly Manage launch the following URL in your browser
|
||||
- http://<openHAB IP address>:8080/shelly/manager or
|
||||
- http://<openHAB IP address>:8443/shelly/manager
|
||||
|
||||
Maybe you need to change the port matching your setup.
|
||||
|
||||
Shelly Manager makes you various device insights available to get an overview of your Shellys
|
||||
- Get a quick overview that all Shellys operate like expected, statistical data will help to identify issues
|
||||
- Have some basic setting actions integrated, which help to do an easy setup of new Shellys added to openHAB
|
||||
- Make firmware updates way easier - filter 'Update available' + integrated 2-click update
|
||||
- Provide a firmware download proxy, which allows to separate your Shellys from the Internet (improved device security)
|
||||
|
||||
## Overview
|
||||
|
||||
Once the Shelly Manager is opened an overview of all Shelly devices added as a Thing are displayed.
|
||||
Things which are not discovered or still site in the Inbox will not be displayed.
|
||||
|
||||
|
||||
|
||||
You'll see a bunch of technical details, which are not available as channels or in the Thing properties.
|
||||
This includes information on the device communication stability.
|
||||
The statistic gives you a good overview if device communication is stable or a relevant number of timeouts need to be recovered.
|
||||
In this case you should verify the WiFi coverage or other options to improve stability.
|
||||
|
||||
The following information is available
|
||||
|Column |Description |
|
||||
|--------------------|---------------------------------------------------------------------------------|
|
||||
|S |Thing Status - hover over the icon to see more details |
|
||||
|Name |Device name - hover over the name to get more details |
|
||||
|Cloud Status Icon |Indicates the status of the Shelly Cloud feature: disabled/enabled/connected |
|
||||
|MQQT Status Icon |Indicates the staus of the MQTT featured disabled/enabled/connected |
|
||||
|Refresh button |Trigger a status refresh in background, maybe you need to click more than once |
|
||||
|Device IP |Assigned IP address, click to open the device’s Web UI in a separate browser tab |
|
||||
|WiFi Network |SSID of the connected WiFi network |
|
||||
|WiFi Signal |WiFi signal strength, 0=none, 4=very good |
|
||||
|Battery Level |Remaining capacity of the battery |
|
||||
|Heartbeat |Last time a response or an event was received from the device |
|
||||
|Actions |Drop down with some actions, see below |
|
||||
|Firmware |Current firmware release |
|
||||
|Update avail |yes indicates that a firmware update is available |
|
||||
|Versions |List available firmware versions: prod, beta or archived |
|
||||
|Uptime |Number of seconds since last device restart |
|
||||
|Internal Temp |Device internal temperature. Max is depending on device type. |
|
||||
|Update Period |Timeout for device refresh |
|
||||
|Remaining Watchdog |Shows number of seconds until device will go offline if no update is received |
|
||||
|Events |Increases on every event triggered by the device or the binding |
|
||||
|Last Event |Type of last event or alarm (refer README.md for details) |
|
||||
|Event Time |When was last event received |
|
||||
|Device Restarts |Number of detected restarts. This is ok on firmware updates, otherwise indicates a crash |
|
||||
|Timeout Errors |Number of API timeouts, could be an indication for an unstable connection |
|
||||
|Timeouts recovered |The binding does retries and timeouts and counts successful recoveries |
|
||||
|CoIoT Messages |Number of received CoIoT messages, must be >= 2 to indicate CoIoT working |
|
||||
|CoIoT Errors |Number of CoIoT messages, which can't be processed. >0 indicates firmware issues |
|
||||
|
||||
The column S and Name display more information when hovering with the mouse over the entries.
|
||||
|
||||
|
||||
|
||||
|
||||
### Device Filters
|
||||
|Filter |Description |
|
||||
|--------------------|---------------------------------------------------------------------------------|
|
||||
|All |Clear filter / display all devices |
|
||||
|Online only |Filter on devices with Thing Status = ONLINE |
|
||||
|Inactive only |Filter on devices, which are not initialized for in Thing Status = OFFLINE |
|
||||
|Needs Attention |Filter on devices, which need attention (setup/connectivity issues), see below |
|
||||
|Update available |Filter on devices having a new firmware version available |
|
||||
|Unprotected |Filter on devices, which are currently not password protected |
|
||||
|
||||
Beside the Device Filter box you see a refresh button.
|
||||
At the bottom right you see number of displayed devices vs. number of total devices.
|
||||
A click triggers a background status update for all devices rather only the selected one when clicking of the refresh button in the device lines.
|
||||
|
||||
Filter 'Needs Attention':
|
||||
This is a dynamic filter, which helps to identify devices having some kind of setup / connectivity or operation issues.
|
||||
The binding checks the following conditions
|
||||
- Thing status != ONLINE: Use the 'Inactive Only' filter to find those devices, check openhab.log
|
||||
- WIFISIGNAL: WiFi signal strength < 2 - this usually leads into connectivity problems, check positioning of portable devices or antenna direction.
|
||||
- LOWBATTERY: The remaining battery is < 20% (configuration in Thing Configuration), consider to replace the battery
|
||||
Watch out for bigger number of timeout errors.
|
||||
- Device RESTARTED: Indicates a firmware problem / crash if this happens without a device reboot or firmware update (timestamp is included)
|
||||
- OVERTEMP / OVERLOAD / LOADERROR: There are problems with the physical installation of the device, check specifications, wiring, housing!
|
||||
- SENSORERROR: A sensor error / malfunction was detected, check product documentation
|
||||
- NO_COIOT_DISCOVERY: The CoIoT discovery has not been completed, check IP network configuration, re-discover the device
|
||||
- NO_COIOT_MULTICAST: The CoIoT discovery could be completed, but the device is not receiving CoIoT status updates.
|
||||
You might try to switch to CoIoT Peer mode, in this case the device doesn't use IP Multicast and sends updates directly to the openHAB host.
|
||||
|
||||
The result is shown in the Device Status tooltip.
|
||||
|
||||
### Device settings & status
|
||||
|
||||
When hovering with the mouse over the status icon or the device name you'll get additional information settings and status.
|
||||
|
||||
### Device Status
|
||||
|
||||
|Status |Description |
|
||||
|--------------------|---------------------------------------------------------------------------------|
|
||||
|Status |Thing status, sub-status and description as you know it from openHAB |
|
||||
|CoIoT Status |CoIoT status: enabled or disabled |
|
||||
|CoIoT Destination |CoIoT Peer address (ip address:port) or Multicast |
|
||||
|Cloud Status |Status of the Shelly Cloud connection: disabled, enabled, connected |
|
||||
|MQTT Status |MQTT Status: disabled, enabled, connected |
|
||||
|Actions skipped |Number of actions skipped by the device, usually 0 |
|
||||
|Max Internal Temp |Maximum internal temperature, check device specification for valid range |
|
||||
|
||||
### Device Settings
|
||||
|
||||
|Setting |Description |
|
||||
|--------------------|---------------------------------------------------------------------------------|
|
||||
|Shelly Device Name |Device name according to device settings |
|
||||
|Device Hardware Rev |Hardware revision of the device |
|
||||
|Device Type |Device Type ID |
|
||||
|Device Mode |Selected mode for dual mode devices (relay/roller or white/color) |
|
||||
|Firmware Version |Current firmware version |
|
||||
|Network Name |Network name of the device used for mDNS |
|
||||
|MAC Address |Unique hardware/network address of the device |
|
||||
|Discoverable |true: the device can be discovered using mDNS, false: device is hidden |
|
||||
|WiFi Auto Recovery |enabled: the device will automatically reboot when WiFi connect fails |
|
||||
|Timezone |Configured device zone (see device settings) |
|
||||
|Time server |Configured time server (use device UI to change) |
|
||||
|
||||
### Actions
|
||||
|
||||
The Shelly Manager provides the following actions when the Thing is ONLINE.
|
||||
They are available in the dropdown list in column Actions.
|
||||
|
||||
|Action |Description |
|
||||
|---------------------|---------------------------------------------------------------------------------|
|
||||
|Reset Statistics |Resets device statistic and clear the last alarm |
|
||||
|Restart |Restart the device and reconnect to WiFi |
|
||||
|Protect |Use binding's default credentials to protect device access with user and password|
|
||||
|Set CoIoT Peer |Disable CoIoT Multicast and set openHAB system as receiver for CoIoT updates |
|
||||
|Set CoIoT Multicast |Disable CoIoT Multicast and set openHAB system as receiver for CoIoT updates |
|
||||
|Enable Cloud |Enable the Shelly Cloud connectivity |
|
||||
|Disable Cloud |Disable the Shelly Cloud connectivity (takes about 15sec to become active) |
|
||||
|Reconnect WiFi |Sensor devices only: Clears the STA/AP list and reconnects to strongest AP |
|
||||
|Enable WiFi Roaming |The device will connect to the strongest AP when roadming is enabled |
|
||||
|Disable WiFi Roaming |Disable Access Point Roaming, device will periodically search for better APs |
|
||||
|Enable WiFi Recovery |Enables auto-restart if device detects persistent WiFi connectivity issues |
|
||||
|Disable WiFi Recovery|Disables device auto-restart ion persistent WiFi connectivity issues |
|
||||
|Factory Reset |Performs a **factory reset**; Attention: The device will lose its configuration |
|
||||
|Enable Device Debug |Enables on-device debug log - activate only when requested by Allterco support |
|
||||
|Get Debug Log |Retrieve and display device debug output |
|
||||
|Get Debug Log1 |Retrieve and display 2nd device debug output |
|
||||
|Factory Reset |Performs **firmware reset**; Attention: The device will lose its configuration |
|
||||
|
||||
Note: Various actions available only for certain devices or when using a minimum firmware version.
|
||||
|
||||
|
||||
|
||||
## Firmware Update
|
||||
|
||||
The Shelly Manager simplifies the firmware update.
|
||||
You could select between different versions using the drop down list on the overview page.
|
||||
|
||||
Shelly Manager integrates different sources
|
||||
- Allterco official releases: production and beta release (like in the device UI)
|
||||
- Older firmware release from the firmware archive - this is a community service
|
||||
- You could specify any custom URL providing the firmware image (e.g. a local web server), which is accessible for the device using http
|
||||
|
||||
| | |
|
||||
|-|-|
|
||||
||All firmware releases are combined to the selection list.<br/>Click on the version you want to install and Shelly Manager will generate the requested URL to trigger the firmware upgrade.|
|
||||
|
||||
The upgrade starts if you click "Perform Update".
|
||||
|
||||
|
||||
|
||||
The device will download the firmware file, installs the update and restarts the device.
|
||||
Depending on the device type this takes between 10 and 60 seconds.
|
||||
The binding will automatically recover the device with the next status check (as usual).
|
||||
|
||||
### Connection types
|
||||
|
||||
You could choose between 3 different update types
|
||||
* Internet: This triggers the regular update; the device needs to be connected to the Internet
|
||||
* Use openHAB as a proxy: In this case the binding directs the device to request the firmware from the openHAB system.
|
||||
The binding will then download the firmware from the selected sources and passes this transparently to the device.
|
||||
This provides a security benefit: The device doesn't require Internet access, only the openHAB host, which could be filtered centrally.
|
||||
* Custom URL: In this case you could specify
|
||||
|
||||
The binding manages the download request with the proper download URL.
|
||||
|
|
@ -30,6 +30,14 @@ The binding gets in sync with the next status refresh.
|
|||
|
||||
Refer to [Advanced Users](doc/AdvancedUsers.md) for more information on openHAB Shelly integration, e.g. firmware update, network communication or log filtering.
|
||||
|
||||
Also check out the [Shelly Manager](doc/ShellyManager.md), which
|
||||
- provides detailed information on your Shellys
|
||||
- helps to diagnose WiFi issues or device instabilities
|
||||
- includes some common actions and
|
||||
- simplifies firmware updates.
|
||||
|
||||
[Shelly Manager](doc/ShellyManager.md) could also act as a firmware upgrade proxy - the device doesn't need to connect directly to the Internet, instead openHAB services as a download proxy, which improves device security.
|
||||
|
||||
## Supported Devices
|
||||
|
||||
| thing-type | Model | Vendor ID |
|
||||
|
|
@ -271,16 +279,20 @@ The following trigger types are sent:
|
|||
|
||||
|Event Type |Description |
|
||||
|-------------------|---------------------------------------------------------------------------------------------------------------|
|
||||
|SHORT_PRESSED |The button was pressed once for a short time |
|
||||
|DOUBLE_PRESSED |The button was pressed twice with short delay |
|
||||
|TRIPLE_PRESSED |The button was pressed three times with short delay |
|
||||
|LONG_PRESSED |The button was pressed for a longer time |
|
||||
|SHORT_LONG_PRESSED |A short followed by a long button push |
|
||||
|LONG_SHORT_PRESSED |A long followed by a short button push |
|
||||
|SHORT_PRESSED |The button was pressed once for a short time (lastEvent=S) |
|
||||
|DOUBLE_PRESSED |The button was pressed twice with short delay (lastEvent=SS) |
|
||||
|TRIPLE_PRESSED |The button was pressed three times with short delay (lastEvent=SSS) |
|
||||
|LONG_PRESSED |The button was pressed for a longer time (lastEvent=L) |
|
||||
|SHORT_LONG_PRESSED |A short followed by a long button push (lastEvent=SL) |
|
||||
|LONG_SHORT_PRESSED |A long followed by a short button push (lastEvent=LS) |
|
||||
|
||||
Check the channel definitions for the various devices to see if the device supports those events.
|
||||
You could use the Shelly App to set the timing for those events.
|
||||
|
||||
If you want to use those events triggering a rule:
|
||||
- If a physical switch is connected to the Shelly use the input channel(`input` or `input1`/`input2`) to trigger a rule
|
||||
- For a momentary button use the `button` trigger channel as trigger, channels `lastEvent` and `eventCount` will provide details on the event
|
||||
|
||||
### Alarms
|
||||
|
||||
The binding provides health monitoring functions for the device.
|
||||
|
|
@ -810,7 +822,8 @@ You can define 2 items (1 Switch, 1 Number) mapping to the same channel, see exa
|
|||
|
||||
Important: The Shelly Motion does only support CoIoT Unicast, which means you need to set the CoIoT peer address.
|
||||
|
||||
Use device WebUI, open COIOT settings, make sure CoIoT is enabled and enter the openHAB IP address or
|
||||
- Use device WebUI, open COIOT settings, make sure CoIoT is enabled and enter the openHAB IP address or
|
||||
- Use [Shelly Manager](doc/ShellyManager.md, select Action 'Set CoIoT peer' and the Manager will sets the openHAB IP address as peer address
|
||||
|
||||
|Group |Channel |Type |read-only|Description |
|
||||
|----------|---------------|---------|---------|---------------------------------------------------------------------|
|
||||
|
|
|
|||
|
|
@ -91,8 +91,8 @@ A `upnprenderer` has the following optional configuration parameters:
|
|||
The full syntax for manual configuration is:
|
||||
|
||||
```
|
||||
Thing upnpcontrol:upnpserver:<serverId> [udn="<udn of media server>", refresh=<polling interval>, seekStep=<step>]
|
||||
Thing upnpcontrol:upnprenderer:<rendererId> [udn="<udn of media renderer>", refresh=<polling interval>, filter=<true/false>, sortCriteria="<sort criteria string>", browseDown=<true/false>, searchfromroot=<true/false>]
|
||||
Thing upnpcontrol:upnpserver:<serverId> [udn="<udn of media server>", refresh=<polling interval>, filter=<true/false>, sortCriteria="<sort criteria string>", browseDown=<true/false>, searchFromRoot=<true/false>, responseTimeout=<UPnP timeout in milliseconds>]
|
||||
Thing upnpcontrol:upnprenderer:<rendererId> [udn="<udn of media renderer>", refresh=<polling interval>, notificationVolumeAdjustment=<signed percent>, maxNotificationDuration=<duration in seconds>, seekStep=<step>, responseTimeout=<UPnP timeout in milliseconds>]
|
||||
```
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -12,8 +12,10 @@
|
|||
<config-description>
|
||||
<parameter name="appKey" type="text" required="true">
|
||||
<label>Application Key</label>
|
||||
<description>The Application Key is required to communication with the Automower Connect Api. It can be obtained by
|
||||
registering an Application on the Husqvarna Website. This application also needs to be connected to the
|
||||
<description>The Application Key is required to communication with the Automower Connect Api at
|
||||
https://developer.husqvarnagroup.cloud/. It can be obtained by
|
||||
registering an Application on the Husqvarna Website.
|
||||
This application also needs to be connected to the
|
||||
"Authentication API" and the "Automower Connect API"</description>
|
||||
</parameter>
|
||||
<parameter name="userName" type="text" required="true">
|
||||
|
|
@ -21,7 +23,7 @@
|
|||
<description>The user name for which the application key has been issued</description>
|
||||
</parameter>
|
||||
<parameter name="password" type="text" required="true">
|
||||
<context>Password</context>
|
||||
<context>password</context>
|
||||
<description>The password for the given user</description>
|
||||
</parameter>
|
||||
<parameter name="pollingInterval" type="integer" required="false" unit="s">
|
||||
|
|
@ -48,9 +50,18 @@
|
|||
<channel id="activity" typeId="activityType"/>
|
||||
<channel id="state" typeId="stateType"/>
|
||||
<channel id="last-update" typeId="lastUpdateType"/>
|
||||
<channel id="battery" typeId="batteryType"/>
|
||||
<channel id="battery" typeId="system.battery-level"/>
|
||||
<channel id="error-code" typeId="errorCodeType"/>
|
||||
<channel id="error-timestamp" typeId="errorTimestampType"/>
|
||||
<channel id="planner-next-start" typeId="plannerNextStartTimestampType"/>
|
||||
<channel id="planner-override-action" typeId="plannerOverrideActionType"/>
|
||||
<channel id="calendar-tasks" typeId="calendarTasksType"/>
|
||||
<channel id="start" typeId="start"/>
|
||||
<channel id="resume_schedule" typeId="resumeSchedule"/>
|
||||
<channel id="pause" typeId="pause"/>
|
||||
<channel id="park" typeId="park"/>
|
||||
<channel id="park_until_next_schedule" typeId="parkUntilNextSchedule"/>
|
||||
<channel id="park_until_further_notice" typeId="parkUntilFurtherNotice"/>
|
||||
</channels>
|
||||
|
||||
<properties>
|
||||
|
|
@ -126,7 +137,11 @@
|
|||
<option value="IN_OPERATION">Working</option>
|
||||
<option value="WAIT_UPDATING">Downloading new firmware</option>
|
||||
<option value="WAIT_POWER_UP">Booting mower</option>
|
||||
<option value="RESTRICTED">Waiting</option>
|
||||
<option value="RESTRICTED_NONE">Waiting</option>
|
||||
<option value="RESTRICTED_WEEK_SCHEDULE">Restricted by week schedule</option>
|
||||
<option value="RESTRICTED_PARK_OVERRIDE">Forced to park</option>
|
||||
<option value="RESTRICTED_SENSOR">Restricted by sensor</option>
|
||||
<option value="RESTRICTED_DAILY_LIMIT">Restricted by daily limit</option>
|
||||
<option value="OFF">Off</option>
|
||||
<option value="STOPPED">Stopped- Manual intervention required</option>
|
||||
<option value="ERROR">Error</option>
|
||||
|
|
@ -164,4 +179,64 @@
|
|||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="plannerNextStartTimestampType">
|
||||
<item-type>DateTime</item-type>
|
||||
<label>Next Auto Start</label>
|
||||
<description>The channel providing the time for the next auto start. If the mower is charging then the value is the
|
||||
estimated time when it will be leaving the charging station. If the mower is about to start now, the value is NULL.</description>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="plannerOverrideActionType">
|
||||
<item-type>String</item-type>
|
||||
<label>Override Action</label>
|
||||
<description>The channel providing an action that overrides current planner operation.</description>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="calendarTasksType">
|
||||
<item-type>String</item-type>
|
||||
<label>Planner Info JSON</label>
|
||||
<description>The channel providing a JSON with the information about the planner tasks.</description>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="start">
|
||||
<item-type>Number</item-type>
|
||||
<label>Start with Duration</label>
|
||||
<description>Start for a duration in minutes</description>
|
||||
<state pattern="%d min" min="1" max="1440" step="1"/>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="resumeSchedule">
|
||||
<item-type>Switch</item-type>
|
||||
<label>Resume Schedule</label>
|
||||
<description>Resume schedule</description>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="pause">
|
||||
<item-type>Switch</item-type>
|
||||
<label>Pause</label>
|
||||
<description>Pause the mower now until manual resume</description>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="park">
|
||||
<item-type>Number</item-type>
|
||||
<label>Park with Duration</label>
|
||||
<description>Park for a duration in minutes</description>
|
||||
<state pattern="%d min" min="1" max="1440" step="1"/>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="parkUntilNextSchedule">
|
||||
<item-type>Switch</item-type>
|
||||
<label>Park Until Next Schedule</label>
|
||||
<description>Park until next schedule</description>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="parkUntilFurtherNotice">
|
||||
<item-type>Switch</item-type>
|
||||
<label>Park and Pause the Schedule</label>
|
||||
<description>Park and pause the mower schedule until manual resume</description>
|
||||
</channel-type>
|
||||
|
||||
</thing:thing-descriptions>
|
||||
|
|
|
|||
|
|
@ -21,6 +21,9 @@
|
|||
<channel id="cmpfrequency" typeId="acunit-cmpfrequency"></channel>
|
||||
<channel id="specialmode" typeId="acunit-specialmode"></channel>
|
||||
<channel id="specialmode-powerful" typeId="acunit-specialmode-powerful"></channel>
|
||||
<channel id="energyheatingtoday" typeId="acunit-energyheatingtoday"/>
|
||||
<channel id="energyheatingthisweek" typeId="acunit-energyheatingthisweek"/>
|
||||
<channel id="energyheatinglastweek" typeId="acunit-energyheatinglastweek"/>
|
||||
<channel id="energyheatingcurrentyear-1" typeId="acunit-energyheatingcurrentyear-1"></channel>
|
||||
<channel id="energyheatingcurrentyear-2" typeId="acunit-energyheatingcurrentyear-2"></channel>
|
||||
<channel id="energyheatingcurrentyear-3" typeId="acunit-energyheatingcurrentyear-3"></channel>
|
||||
|
|
@ -33,6 +36,9 @@
|
|||
<channel id="energyheatingcurrentyear-10" typeId="acunit-energyheatingcurrentyear-10"></channel>
|
||||
<channel id="energyheatingcurrentyear-11" typeId="acunit-energyheatingcurrentyear-11"></channel>
|
||||
<channel id="energyheatingcurrentyear-12" typeId="acunit-energyheatingcurrentyear-12"></channel>
|
||||
<channel id="energycoolingtoday" typeId="acunit-energycoolingtoday"/>
|
||||
<channel id="energycoolingthisweek" typeId="acunit-energycoolingthisweek"/>
|
||||
<channel id="energycoolinglastweek" typeId="acunit-energycoolinglastweek"/>
|
||||
<channel id="energycoolingcurrentyear-1" typeId="acunit-energycoolingcurrentyear-1"></channel>
|
||||
<channel id="energycoolingcurrentyear-2" typeId="acunit-energycoolingcurrentyear-2"></channel>
|
||||
<channel id="energycoolingcurrentyear-3" typeId="acunit-energycoolingcurrentyear-3"></channel>
|
||||
|
|
@ -174,6 +180,54 @@
|
|||
</state>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="acunit-energyheatingtoday" advanced="true">
|
||||
<item-type>Number:Energy</item-type>
|
||||
<label>Energy Heating Today</label>
|
||||
<description>The energy usage for heating today</description>
|
||||
<category>Energy</category>
|
||||
<state readOnly="true" pattern="%.1f %unit%"></state>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="acunit-energyheatingthisweek" advanced="true">
|
||||
<item-type>Number:Energy</item-type>
|
||||
<label>Energy Heating This Week</label>
|
||||
<description>The energy usage for heating this week</description>
|
||||
<category>Energy</category>
|
||||
<state readOnly="true" pattern="%.1f %unit%"></state>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="acunit-energyheatinglastweek" advanced="true">
|
||||
<item-type>Number:Energy</item-type>
|
||||
<label>Energy Heating Last Week</label>
|
||||
<description>The energy usage for heating last week</description>
|
||||
<category>Energy</category>
|
||||
<state readOnly="true" pattern="%.1f %unit%"></state>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="acunit-energycoolingtoday" advanced="true">
|
||||
<item-type>Number:Energy</item-type>
|
||||
<label>Energy Cooling Today</label>
|
||||
<description>The energy usage for cooling today</description>
|
||||
<category>Energy</category>
|
||||
<state readOnly="true" pattern="%.1f %unit%"></state>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="acunit-energycoolingthisweek" advanced="true">
|
||||
<item-type>Number:Energy</item-type>
|
||||
<label>Energy Cooling This Week</label>
|
||||
<description>The energy usage for cooling this week</description>
|
||||
<category>Energy</category>
|
||||
<state readOnly="true" pattern="%.1f %unit%"></state>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="acunit-energycoolinglastweek" advanced="true">
|
||||
<item-type>Number:Energy</item-type>
|
||||
<label>Energy Cooling Last Week</label>
|
||||
<description>The energy usage for cooling last week</description>
|
||||
<category>Energy</category>
|
||||
<state readOnly="true" pattern="%.1f %unit%"></state>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="acunit-cmpfrequency" advanced="true">
|
||||
<item-type>Number:Dimensionless</item-type>
|
||||
<label>Compressor Frequency</label>
|
||||
|
|
|
|||
|
|
@ -6,9 +6,9 @@
|
|||
|
||||
<thing-type id="dwdwarnings">
|
||||
<label>Weather Warnings</label>
|
||||
<description>Weather Warnings for an area</description>
|
||||
<description>Weather Warnings for an area.</description>
|
||||
<channels>
|
||||
<channel typeId="lastUpdated" id="lastUpdated"></channel>
|
||||
<channel typeId="lastUpdated" id="lastUpdated"/>
|
||||
</channels>
|
||||
<config-description>
|
||||
<parameter name="cellId" type="text" required="true">
|
||||
|
|
@ -35,7 +35,8 @@ The warnings are sorted by severity first and begin second so the first warning
|
|||
<channel-type id="lastUpdated">
|
||||
<item-type>DateTime</item-type>
|
||||
<label>Last Updated</label>
|
||||
<description>Timestamp of the last update from the endpoint</description>
|
||||
<description>Timestamp of the last update from the endpoint.</description>
|
||||
<category>Time</category>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="warning">
|
||||
|
|
@ -43,14 +44,14 @@ The warnings are sorted by severity first and begin second so the first warning
|
|||
<label>Warning</label>
|
||||
<description><![CDATA[ON if a warning is present, OFF else.
|
||||
While be switched to ON only after all other channels - except the trigger channel - are updated.
|
||||
Will be switched to OFF before all other channels are updated to NULL]]></description>
|
||||
Will be switched to OFF before all other channels are updated to UNDEF.]]></description>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="updated">
|
||||
<kind>trigger</kind>
|
||||
<label>Updated</label>
|
||||
<description><![CDATA[Triggers NEW if a warning is send the first time.
|
||||
This happens after all other channels are populated]]></description>
|
||||
This happens after all other channels are populated.]]></description>
|
||||
<event>
|
||||
<options>
|
||||
<option value="NEW">New</option>
|
||||
|
|
@ -79,49 +80,52 @@ This happens after all other channels are populated]]></description>
|
|||
<channel-type id="effective">
|
||||
<item-type>DateTime</item-type>
|
||||
<label>Issued</label>
|
||||
<description>Issued Date and Time</description>
|
||||
<description>Issued Date and Time.</description>
|
||||
<category>Time</category>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="onset">
|
||||
<item-type>DateTime</item-type>
|
||||
<label>Valid From</label>
|
||||
<description>Start Date and Time for which the warning is valid</description>
|
||||
<description>Start Date and Time for which the warning is valid.</description>
|
||||
<category>Time</category>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="expires">
|
||||
<item-type>DateTime</item-type>
|
||||
<label>Valid To</label>
|
||||
<description>End Date and Time for which the warning is valid</description>
|
||||
<description>End Date and Time for which the warning is valid.</description>
|
||||
<category>Time</category>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="headline">
|
||||
<item-type>String</item-type>
|
||||
<label>Headline</label>
|
||||
<description>Headline of the warning like "Amtliche Warnung vor FROST"</description>
|
||||
<description>Headline of the warning like "Amtliche Warnung vor FROST".</description>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="event">
|
||||
<item-type>String</item-type>
|
||||
<label>Type</label>
|
||||
<description>Type of the warning, e.g. FROST</description>
|
||||
<description>Type of the warning, e.g. FROST.</description>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="altitude">
|
||||
<item-type>Number:Length</item-type>
|
||||
<label>Height (from)</label>
|
||||
<description>Lower Height above sea level for which the warning is valid</description>
|
||||
<description>Lower Height above sea level for which the warning is valid.</description>
|
||||
<state readOnly="true" pattern="%d m"/>
|
||||
</channel-type>
|
||||
<channel-type id="ceiling">
|
||||
<item-type>Number:Length</item-type>
|
||||
<label>Height (to)</label>
|
||||
<description>Upper Height above sea level for which the warning is valid</description>
|
||||
<description>Upper Height above sea level for which the warning is valid.</description>
|
||||
<state readOnly="true" pattern="%d m"/>
|
||||
</channel-type>
|
||||
<channel-type id="instruction">
|
||||
<item-type>String</item-type>
|
||||
<label>Instruction</label>
|
||||
<description>Instructions and safety information</description>
|
||||
<description>Instructions and safety information.</description>
|
||||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
<channel-type id="urgency">
|
||||
|
|
|
|||
|
|
@ -13,11 +13,9 @@
|
|||
<parameter name="username" type="text" required="false">
|
||||
<label>Username</label>
|
||||
<description>Username as used in the GROHE ONDUS App, usually your e-mail address.</description>
|
||||
<required>true</required>
|
||||
</parameter>
|
||||
<parameter name="password" type="text" required="false">
|
||||
<label>Password</label>
|
||||
<required>true</required>
|
||||
<context>password</context>
|
||||
<description>Password as used in the GROHE ONDUS App.</description>
|
||||
</parameter>
|
||||
|
|
|
|||
|
|
@ -1203,6 +1203,11 @@
|
|||
<label>Zone Number</label>
|
||||
<description>Assigned Zone Number within the Lutron RadioRA system.</description>
|
||||
</parameter>
|
||||
<parameter name="system" type="integer" min="0" max="2" required="false">
|
||||
<label>System Number</label>
|
||||
<description>System number (bridged systems only). Set to 1 or 2. 0 = NA (default).</description>
|
||||
<default>0</default>
|
||||
</parameter>
|
||||
<parameter name="fadeOutSec" type="integer" required="false">
|
||||
<label>Fade Out (sec)</label>
|
||||
<description>Time in seconds dimmer should take when lowering the level</description>
|
||||
|
|
@ -1231,6 +1236,11 @@
|
|||
<label>Zone Number</label>
|
||||
<description>Assigned Zone Number within the Lutron RadioRA system.</description>
|
||||
</parameter>
|
||||
<parameter name="system" type="integer" min="0" max="2" required="false">
|
||||
<label>System Number</label>
|
||||
<description>System number (bridged systems only). Set to 1 or 2. 0 = NA (default).</description>
|
||||
<default>0</default>
|
||||
</parameter>
|
||||
</config-description>
|
||||
</thing-type>
|
||||
|
||||
|
|
@ -1250,6 +1260,11 @@
|
|||
<label>Phantom Button Number</label>
|
||||
<description>Phantom Button Number within the Lutron RadioRA system.</description>
|
||||
</parameter>
|
||||
<parameter name="system" type="integer" min="0" max="2" required="false">
|
||||
<label>System Number</label>
|
||||
<description>System number (bridged systems only). Set to 1 or 2. 0 = NA (default).</description>
|
||||
<default>0</default>
|
||||
</parameter>
|
||||
</config-description>
|
||||
</thing-type>
|
||||
|
||||
|
|
|
|||
|
|
@ -14,6 +14,7 @@
|
|||
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="zoneControls" id="zone1">
|
||||
<label>Zone 1</label>
|
||||
</channel-group>
|
||||
|
|
@ -44,6 +45,7 @@
|
|||
<description>Control a 2014 Pioneer AVR (SC-LX87, SC-LX77, SC-LX57, SC-2023, SC-1223, VSX-1123, VSX-923) over IP </description>
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="controls2014" id="zone1">
|
||||
<label>Zone 1</label>
|
||||
</channel-group>
|
||||
|
|
@ -80,6 +82,7 @@
|
|||
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="controls2015" id="zone1">
|
||||
<label>Zone 1</label>
|
||||
</channel-group>
|
||||
|
|
@ -116,6 +119,7 @@
|
|||
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="controls2016" id="zone1">
|
||||
<label>Zone 1</label>
|
||||
</channel-group>
|
||||
|
|
@ -152,6 +156,7 @@
|
|||
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="controls2017" id="zone1">
|
||||
<label>Zone 1</label>
|
||||
</channel-group>
|
||||
|
|
@ -186,6 +191,7 @@
|
|||
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="controls2018" id="zone1">
|
||||
<label>Zone 1</label>
|
||||
</channel-group>
|
||||
|
|
@ -220,6 +226,7 @@
|
|||
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="controls2019" id="zone1">
|
||||
<label>Zone 1</label>
|
||||
</channel-group>
|
||||
|
|
@ -254,6 +261,7 @@
|
|||
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="controls2020" id="zone1">
|
||||
<label>Zone 1</label>
|
||||
</channel-group>
|
||||
|
|
@ -290,6 +298,7 @@
|
|||
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="zoneControls" id="zone1"/>
|
||||
<channel-group typeId="zoneControls" id="zone2"/>
|
||||
<channel-group typeId="zoneControls" id="zone3"/>
|
||||
|
|
@ -316,6 +325,7 @@
|
|||
|
||||
<channel-groups>
|
||||
<channel-group typeId="displayInformationGroup" id="displayInformation"/>
|
||||
<channel-group typeId="MCACCMemoryGroup" id="MCACCMemory"/>
|
||||
<channel-group typeId="zone1Controls" id="zone1"/>
|
||||
<channel-group typeId="zone2Controls" id="zone2"/>
|
||||
<channel-group typeId="zone3Controls" id="zone3"/>
|
||||
|
|
@ -338,6 +348,13 @@
|
|||
</channels>
|
||||
</channel-group-type>
|
||||
|
||||
<channel-group-type id="MCACCMemoryGroup">
|
||||
<label>MCACC Memory</label>
|
||||
<channels>
|
||||
<channel id="MCACCMemory" typeId="setMCACCMemoryChannel"/>
|
||||
</channels>
|
||||
</channel-group-type>
|
||||
|
||||
<channel-group-type id="zoneControls">
|
||||
<label>Zone Controls</label>
|
||||
<channels>
|
||||
|
|
@ -643,7 +660,7 @@
|
|||
<label>Volume</label>
|
||||
<description>Set the volume level (dB)</description>
|
||||
<category>SoundVolume</category>
|
||||
<state min="-80" max="12" step="0.5" pattern="%.1f dB"/>
|
||||
<state min="-80" max="12" step="0.5" pattern="%.1f dB"></state>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="muteChannel">
|
||||
|
|
@ -1378,4 +1395,21 @@
|
|||
<state readOnly="true"/>
|
||||
</channel-type>
|
||||
|
||||
<channel-type id="setMCACCMemoryChannel">
|
||||
<item-type>String</item-type>
|
||||
<label>MCACC Memory</label>
|
||||
<description>Set the MCACC Memory profile</description>
|
||||
<state>
|
||||
<options>
|
||||
<option value="0000">MCACC MEMORY (cyclic)</option>
|
||||
<option value="0001">MEMORY 1</option>
|
||||
<option value="0002">MEMORY 2</option>
|
||||
<option value="0003">MEMORY 3</option>
|
||||
<option value="0004">MEMORY 4</option>
|
||||
<option value="0005">MEMORY 5</option>
|
||||
<option value="0006">MEMORY 6</option>
|
||||
</options>
|
||||
</state>
|
||||
</channel-type>
|
||||
|
||||
</thing:thing-descriptions>
|
||||
|
|
|
|||
|
|
@ -325,7 +325,7 @@ This has a few disadvantages:
|
|||
|
||||
### My voice command rule isn't run
|
||||
|
||||
Please make sure `Default Human Language Interpreter` is set to `Rule-based Interpreter` (http://openhab:8080/paperui/index.html#/configuration/system) and `Rule Voice Interpreter` => `Configure` => Select correct item (http://openhab:8080/paperui/index.html#/configuration/services?tab=voice).
|
||||
Please make sure that `Default Human Language Interpreter` is set to `Rule-based Interpreter` (http://openhab:8080/#!/settings/services/org.openhab.voice) and that the correct Item is selected at `Other Services` => `Rule Voice Interpreter` => `Voice Command Item` (http://openhab:8080/#!/settings/services/org.openhab.rulehli/select/).
|
||||
|
||||
### Chart loading is too slow
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue