From 3846189406ed3fd29b44a0b03119178c78e12c26 Mon Sep 17 00:00:00 2001 From: Zack Arnett Date: Wed, 17 Oct 2018 17:57:34 -0400 Subject: [PATCH 1/6] Theme documentation - Glance and Button Cards (#6914) * Adding Gauge Card * Updating Docs * Resolving Reviews * Updating documentation to show theme --- source/_lovelace/entity-button.markdown | 4 ++++ source/_lovelace/glance.markdown | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/source/_lovelace/entity-button.markdown b/source/_lovelace/entity-button.markdown index 1571da98a78..73dbc9e62d7 100644 --- a/source/_lovelace/entity-button.markdown +++ b/source/_lovelace/entity-button.markdown @@ -59,6 +59,10 @@ service_data: description: The service data to use. type: object default: "entity_id: entity_id" +theme: + required: false + description: "Set to any theme within `themes.yaml`" + type: string {% endconfiguration %} ## {% linkable_title Examples %} diff --git a/source/_lovelace/glance.markdown b/source/_lovelace/glance.markdown index 9dda1cd3eac..b56ccb437ec 100644 --- a/source/_lovelace/glance.markdown +++ b/source/_lovelace/glance.markdown @@ -45,9 +45,9 @@ column_width: description: "Column width as CSS length like `100px` or `calc(100% / 7)`. This controls how many entities appear in a row - at the default 20% you have 5 entities in a row. Use `calc(100% / 7)` for 7 entities in a row, and so on." type: string default: 20% -theming: +theme: required: false - description: "Set to `primary` to style the card with the background and text color of the header bar." + description: "Set to any theme within `themes.yaml`" type: string {% endconfiguration %} From 45674570e9488679dff6c1df59b38a616e192702 Mon Sep 17 00:00:00 2001 From: William Scanlon Date: Wed, 17 Oct 2018 17:59:55 -0400 Subject: [PATCH 2/6] Updated doc for Wink water heaters (#6842) * Updated doc for Wink water heaters * Changed wording --- source/_components/climate.wink.markdown | 3 +- source/_components/water_heater.wink.markdown | 28 +++++++++++++++++++ 2 files changed, 29 insertions(+), 2 deletions(-) create mode 100644 source/_components/water_heater.wink.markdown diff --git a/source/_components/climate.wink.markdown b/source/_components/climate.wink.markdown index be8623cb08f..2520b49fa45 100644 --- a/source/_components/climate.wink.markdown +++ b/source/_components/climate.wink.markdown @@ -14,7 +14,7 @@ ha_iot_class: "Cloud Polling" --- -The Wink climate platform allows you to get data from your [Wink](http://www.wink.com/) thermostats, Air Conditioners, and Water Heaters. +The Wink climate platform allows you to get data from your [Wink](http://www.wink.com/) thermostats and air conditioners. The requirement is that you have setup [Wink](/components/wink/). @@ -28,7 +28,6 @@ The requirement is that you have setup [Wink](/components/wink/). - Honeywell (No Wink hub required) - Generic Z-Wave - Quirky Aros window AC unit -- Rheem Econet water heaters (No Wink hub required)

The above devices are confirmed to work, but others may work as well. diff --git a/source/_components/water_heater.wink.markdown b/source/_components/water_heater.wink.markdown new file mode 100644 index 00000000000..aa648d350b9 --- /dev/null +++ b/source/_components/water_heater.wink.markdown @@ -0,0 +1,28 @@ +--- +layout: page +title: "Wink Water Heater" +description: "Instructions on how to setup the Wink water heaters within Home Assistant." +date: 2016-11-01 22:36 +sidebar: true +comments: false +sharing: true +footer: true +logo: wink.png +ha_category: water heater +ha_release: 0.32 +ha_iot_class: "Cloud Polling" +--- + +The Wink water heater platform allows you to get data from your [Wink](http://www.wink.com/) Water Heaters. + +The requirement is that you have setup [Wink](/components/wink/). + + +### {% linkable_title Supported water heaters %} + +- Rheem Econet water heaters (No Wink hub required) + + +

+Wink water heaters use to live under the `climate` platform prior to release 0.81. +

From 2ad2ca471be14b4b5649f515b16404bdeaac1506 Mon Sep 17 00:00:00 2001 From: Denver P <23412100+DrTexxOfficial@users.noreply.github.com> Date: Fri, 19 Oct 2018 01:29:38 +1100 Subject: [PATCH 3/6] fixed shield for krihelimeter (#6925) --- README.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.markdown b/README.markdown index f290a931746..728fc3c4a93 100644 --- a/README.markdown +++ b/README.markdown @@ -1,6 +1,6 @@ [![Discord](https://img.shields.io/discord/330944238910963714.svg)](https://discord.gg/CxqDrfU) [![Travis branch](https://img.shields.io/travis/home-assistant/home-assistant.github.io/next.svg)](https://travis-ci.org/home-assistant/home-assistant.github.io) -[![Krihelimeter](http://www.krihelinator.xyz/badge/home-assistant/home-assistant.github.io)](http://www.krihelinator.xyz) +[![Krihelimeter](https://img.shields.io/badge/Krihelimeter-unknown-brightgreen.svg)](http://www.krihelinator.xyz) [![License: CC BY-NC-SA 4.0](https://img.shields.io/badge/License-CC%20BY--NC--SA%204.0-lightgrey.svg)](https://creativecommons.org/licenses/by-nc-sa/4.0/) # Home Assistant website From 2b32a9480bdca6a209603d11656818795fb2859c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Thu, 18 Oct 2018 21:41:31 +0300 Subject: [PATCH 4/6] Huawei LTE sensor config updates (#6789) * huawei_lte sensor: Use new style config section * huawei_lte sensor: Update monitored_conditions default * :pencil2: Tweaks --- source/_components/sensor.huawei_lte.markdown | 53 +++++++++++++------ 1 file changed, 37 insertions(+), 16 deletions(-) diff --git a/source/_components/sensor.huawei_lte.markdown b/source/_components/sensor.huawei_lte.markdown index 682d3bc0518..82da92dd760 100644 --- a/source/_components/sensor.huawei_lte.markdown +++ b/source/_components/sensor.huawei_lte.markdown @@ -33,19 +33,40 @@ sensor: - traffic_statistics.TotalConnectTime ``` -Configuration variables: - -**monitored_conditions** array (*Optional*): Defines the data to monitor as sensors. Defaults to a few generally available data items expected to be available on most boxes. The names here are dot separated paths to information returned by the router. The data set varies by router model; to see what your router provides, set logging level to debug and watch homeassistant.components.huawei_lte debug entries. The following list contains a few example paths just to illustrate the syntax; these may not be available on all routers or their semantics may differ, and there are quite likely many more that are not listed here. - - - **device_information.SoftwareVersion**: Software version. - - **device_information.WanIPAddress**: WAN interface IP address. - - **device_information.WanIPv6Address**: WAN interface IP address. - - **device_signal.rsrq**: The signal RSRQ value. - - **device_signal.rsrp**: The signal RSRP value. - - **device_signal.rssi**: The signal RSSI value. - - **device_signal.sinr**: The signal SINR value. - - **traffic_statistics.CurrentDownloadRate**: Current download rate, bytes/sec. - - **traffic_statistics.CurrentUploadRate**: Current upload rate, bytes/sec. - - **traffic_statistics.TotalUpload**: Total bytes uploaded since last reset. - - **traffic_statistics.TotalDownload**: Total bytes downloaded since last reset. - - **traffic_statistics.TotalConnectTime**: Total time connected since last reset. +{% configuration %} +monitored_conditions: + description: Defines the data to monitor as sensors. The names here are dot-separated paths to information returned by the router. The dataset varies by router model; to see what your router provides, set logging level to debug and watch `homeassistant.components.huawei_lte` debug entries. The following list of values contains a few example paths just to illustrate the syntax; these may not be available on all routers, or their semantics may differ, and there are quite likely many more that are not listed here. + type: list + required: false + default: + - device_information.WanIPAddress + - device_signal.rsrq + - device_signal.rsrp + - device_signal.rssi + - device_signal.sinr + keys: + device_information.SoftwareVersion: + description: Software version + device_information.WanIPAddress: + description: WAN interface IP address + device_information.WanIPv6Address: + description: WAN interface IP address + device_signal.rsrq: + description: The signal RSRQ value + device_signal.rsrp: + description: The signal RSRP value + device_signal.rssi: + description: The signal RSSI value + device_signal.sinr: + description: The signal SINR value + traffic_statistics.CurrentDownloadRate: + description: Current download rate, bytes/sec + traffic_statistics.CurrentUploadRate: + description: Current upload rate, bytes/sec + traffic_statistics.TotalUpload: + description: Total bytes uploaded since last reset + traffic_statistics.TotalDownload: + description: Total bytes downloaded since last reset + traffic_statistics.TotalConnectTime: + description: Total time connected since last reset +{% endconfiguration %} From af6feacadf49e8053d176e29031b6ea244ccf89a Mon Sep 17 00:00:00 2001 From: Martin Mois Date: Thu, 18 Oct 2018 20:48:42 +0200 Subject: [PATCH 5/6] Homeatic signalgen (#6379) * Added notify.homematic_signalgen.markdown * Update notify.homematic_signalgen.markdown * Update notify.homematic_signalgen.markdown * Update notify.homematic_signalgen.markdown * Update notify.homematic_signalgen.markdown * :pencil2: Typo correction * Renamed notify.homematic_signalgen to notify.homematic and reworked according to new implementation * Added notify.homematic.markdown * Removed csv.markdown, added interface parameter * :arrow_up: ha_release * :pencil2: Tweak --- source/_components/notify.homematic.markdown | 111 +++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 source/_components/notify.homematic.markdown diff --git a/source/_components/notify.homematic.markdown b/source/_components/notify.homematic.markdown new file mode 100644 index 00000000000..5ba5dd3b362 --- /dev/null +++ b/source/_components/notify.homematic.markdown @@ -0,0 +1,111 @@ +--- +layout: page +title: "Homematic Notifications" +description: "Instructions on how to notify Homematic devices." +date: 2018-10-03 11:44 +sidebar: true +comments: false +sharing: true +footer: true +logo: homematic.png +ha_category: Notifications +ha_release: 0.81 +--- + +The `homematic` notification platform enables invoking Homematic devices. + +To use this notification platform in your installation, add the following to your `configuration.yaml` file: + +## {% linkable_title Configuration %} + +```yaml +# Example configuration.yaml entry +notify: + - name: my_hm + platform: homematic + address: NEQXXXXXXX + channel: 2 + param: "SUBMIT" + value: "1,1,108000,8" +``` + +{% configuration %} +address: + description: The address of your Homematic device. The address is the serial number of the device shown in the CCU in the `devices` section in the column `serial number`. + required: true + type: string +channel: + description: The channel of your Homematic device. + required: true + type: integer +param: + description: An additional parameter for the Homematic device. + required: true + type: string +interface: + description: Set the name of the interface from the config. + required: false + type: string +value: + description: This is the value that is set on the device. Its device specific. + required: true + type: string +{% endconfiguration %} + +### {% linkable_title Usage %} + +`homematic` is a notify platform and can be controlled by calling the notify service [as described here](/components/notify/). + +Only the `data` part of the event payload is processed. This part can specify or override the value given as configuration variable: + +```json +{ + "data": { + "address": "NEQXXXXXXX", + "channel": 2, + "param": "SUBMIT", + "value": "1,1,108000,8" + } +} +``` + +It is possible to provide a template in order to compute the value: + +{% raw %} +```json +{ + "data": { + "value": "1,1,108000{% if is_state('binary_sensor.oeqxxxxxxx_state', 'on') %},1{% endif %}{% if is_state('binary_sensor.oeqxxxxxxx_state', 'on') %},2{% endif %}" + } +} +``` +{% endraw %} + +You can also specify the event payload using a group notification (instead of specifying the value for the notify itself): + +{% raw %} +```yaml +notify: + - name: my_hm + platform: homematic + address: NEQXXXXXXX + - name: group_hm + platform: group + services: + - service: my_hm + data: + data: + value: "1,1,108000{% if is_state('binary_sensor.oeqxxxxxxx_state', 'on') %},1{% endif %}{% if is_state('binary_sensor.oeqxxxxxxx_state', 'on') %},2{% endif %}" + +alert: + temperature: + name: Temperature too high + done_message: Temperature OK + entity_id: binary_sensor.temperature_too_high + can_acknowledge: True + notifiers: + - group_hm +``` +{% endraw %} + +Please note that the first `data` element belongs to the service `my_hm`, while the second one belongs to the event payload. From 0a76f2885422a9f00df87d42fc596b5140feb2ac Mon Sep 17 00:00:00 2001 From: Nate Clark Date: Thu, 18 Oct 2018 15:43:30 -0400 Subject: [PATCH 6/6] add host, port, discovery and configuration options to Konnected component (#6493) * add host, port, discovery and configuration options to Konnected component * :pencil2: Tweak * :pencil2: Tweaks --- source/_components/konnected.markdown | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/source/_components/konnected.markdown b/source/_components/konnected.markdown index cd55944cb37..dc7104dba18 100644 --- a/source/_components/konnected.markdown +++ b/source/_components/konnected.markdown @@ -116,6 +116,25 @@ devices: repeat: description: Number of times to repeat a momentary pulse. Set to `-1` to make an infinite repeat. This is useful as an alarm or warning when used with a piezo buzzer. required: false + host: + type: string + required: false + description: Optionally specify the Konnected device's IP address or hostname to set up without discovery. + port: + type: integer + required: false + description: Optionally specify the port number for the Konnected API on the device. Note that the port is different on every device. See help.konnected.io to learn how to determine the port number. + discovery: + type: boolean + required: false + default: true + description: Enable or disable discovery for this device. When `true`, the device will respond to discovery requests on your network. When `false`, the device will not respond to discovery requests, so it's important that you set reserved IP for the device and configure the _host_ and _port_ here. + blink: + type: boolean + required: false + default: true + description: Blink the blue LED upon successful transmission of a state change. + {% endconfiguration%} #### {% linkable_title Configuration Notes %} @@ -188,6 +207,10 @@ Konnected runs on an ESP8266 board with the NodeMCU firmware. It is commonly use ### {% linkable_title Revision History %} +#### 0.80 +* Added ability to specify `host` and `port` to set up devices without relying on discovery. +* Added `discovery` and `blink` config options to enable/disable these features. + #### 0.79 * Added `inverse` configuration option for binary sensors.