mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-20 07:46:52 +00:00
Merge remote-tracking branch 'upstream/next' into next
This commit is contained in:
Zack Arnett
commit
b409ba7ebc
@ -1,6 +1,6 @@
|
||||
[](https://discord.gg/CxqDrfU)
|
||||
[](https://travis-ci.org/home-assistant/home-assistant.github.io)
|
||||
[](http://www.krihelinator.xyz)
|
||||
[](http://www.krihelinator.xyz)
|
||||
[](https://creativecommons.org/licenses/by-nc-sa/4.0/)
|
||||
|
||||
# Home Assistant website
|
||||
|
||||
@ -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)
|
||||
|
||||
<p class='note'>
|
||||
The above devices are confirmed to work, but others may work as well.
|
||||
|
||||
@ -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.
|
||||
|
||||
|
||||
111
source/_components/notify.homematic.markdown
Normal file
111
source/_components/notify.homematic.markdown
Normal file
@ -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.
|
||||
@ -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 %}
|
||||
|
||||
28
source/_components/water_heater.wink.markdown
Normal file
28
source/_components/water_heater.wink.markdown
Normal file
@ -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)
|
||||
|
||||
|
||||
<p class='note'>
|
||||
Wink water heaters use to live under the `climate` platform prior to release 0.81.
|
||||
</p>
|
||||
@ -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 %}
|
||||
|
||||
@ -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 %}
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user