mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 09:17:06 +00:00
Merge branch 'rc' into current
This commit is contained in:
Franck Nijhof
commit
8853965292
@ -100,9 +100,9 @@ social:
|
||||
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 108
|
||||
current_patch_version: 9
|
||||
date_released: 2020-04-24
|
||||
current_minor_version: 109
|
||||
current_patch_version: 0
|
||||
date_released: 2020-04-29
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -155,6 +155,7 @@ Supported abbreviations:
|
||||
'pl': 'payload',
|
||||
'pl_arm_away': 'payload_arm_away',
|
||||
'pl_arm_home': 'payload_arm_home',
|
||||
'pl_arm_custom_b': 'payload_arm_custom_bypass',
|
||||
'pl_arm_nite': 'payload_arm_night',
|
||||
'pl_avail': 'payload_available',
|
||||
'pl_cln_sp': 'payload_clean_spot',
|
||||
|
||||
@ -83,6 +83,33 @@ automation:
|
||||
source: HDMI 1
|
||||
```
|
||||
|
||||
## Using scene transitions
|
||||
|
||||
Both the `scene.apply` and `scene.turn_on` services support setting a transition,
|
||||
which enables you to smoothen the transition to the scene.
|
||||
|
||||
This is an example of an automation that sets a romantic scene, in which the
|
||||
light will transition to the scene in 2.5 seconds.
|
||||
|
||||
```yaml
|
||||
# Example automation
|
||||
automation:
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: device_tracker.sweetheart
|
||||
from: "not_home"
|
||||
to: "home"
|
||||
action:
|
||||
service: scene.turn_on
|
||||
data:
|
||||
entity_id: scene.romantic
|
||||
transition: 2.5
|
||||
```
|
||||
|
||||
Transitions are currently only support by lights, which in their turn, have
|
||||
to support it as well. However, the scene itself does not have to consist of
|
||||
only lights to have a transition set.
|
||||
|
||||
## Reloading scenes
|
||||
|
||||
Whenever you make a change to your scene configuration, you can call the `scene.reload` service to reload the scenes.
|
||||
|
||||
@ -16,8 +16,11 @@ The integration will accept the following states from your Alarm Panel (in lower
|
||||
- `armed_home`
|
||||
- `armed_away`
|
||||
- `armed_night`
|
||||
- `armed_custom_bypass`
|
||||
- `pending`
|
||||
- `triggered`
|
||||
- `arming`
|
||||
- `disarming`
|
||||
|
||||
The integration can control your Alarm Panel by publishing to the `command_topic` when a user interacts with the Home Assistant frontend.
|
||||
|
||||
@ -122,6 +125,11 @@ payload_arm_night:
|
||||
required: false
|
||||
type: string
|
||||
default: ARM_NIGHT
|
||||
payload_arm_custom_bypass:
|
||||
description: The payload to set armed-custom-bypass mode on your Alarm Panel.
|
||||
required: false
|
||||
type: string
|
||||
default: ARM_CUSTOM_BYPASS
|
||||
payload_available:
|
||||
description: The payload that represents the available state.
|
||||
required: false
|
||||
|
||||
@ -77,7 +77,7 @@ get_sources:
|
||||
default: true
|
||||
type: boolean
|
||||
apps:
|
||||
description: A dictionary where the keys are app IDs and the values are app names that will be displayed in the UI; see example below. If a name is not provided, the app will never be shown in the sources list. ([These app names](https://github.com/JeffLIrion/python-androidtv/blob/5c39196ade3f88ab453b205fd15b32472d3e0482/androidtv/constants.py#L267-L283) are configured in the backend package and do not need to be included in your configuration.)
|
||||
description: A dictionary where the keys are app IDs and the values are app names that will be displayed in the UI; see example below. If a name is not provided, the app will never be shown in the sources list. ([These app names](https://github.com/JeffLIrion/python-androidtv/blob/748d6b71cad611c624ef7526d9928431167531a3/androidtv/constants.py#L290-L308) are configured in the backend package and do not need to be included in your configuration.)
|
||||
required: false
|
||||
default: {}
|
||||
type: map
|
||||
@ -104,6 +104,11 @@ turn_off_command:
|
||||
description: An ADB shell command that will override the default `turn_off` command.
|
||||
required: false
|
||||
type: string
|
||||
screencap:
|
||||
description: Determines if album art should be pulled from what is shown onscreen.
|
||||
required: false
|
||||
default: true
|
||||
type: boolean
|
||||
{% endconfiguration %}
|
||||
|
||||
### Full Configuration
|
||||
@ -254,7 +259,7 @@ Available key commands include:
|
||||
- `BACK`
|
||||
- `MENU`
|
||||
|
||||
The full list of key commands can be found [here](https://github.com/JeffLIrion/python-androidtv/blob/bf1058a2f746535921b3f5247801469c4567e51a/androidtv/constants.py#L143-L186).
|
||||
The full list of key commands can be found [here](https://github.com/JeffLIrion/python-androidtv/blob/748d6b71cad611c624ef7526d9928431167531a3/androidtv/constants.py#L189-L233).
|
||||
|
||||
You can also use the command `GET_PROPERTIES` to retrieve the properties used by Home Assistant to update the device's state. These will be stored in the media player's `'adb_response'` attribute and logged at the INFO level. This information can be used to help improve state detection in the backend [androidtv](https://github.com/JeffLIrion/python-androidtv) package, and also to define your own [custom state detection](#custom-state-detection) rules.
|
||||
|
||||
|
||||
40
source/_integrations/arris_tg2492lg.markdown
Normal file
40
source/_integrations/arris_tg2492lg.markdown
Normal file
@ -0,0 +1,40 @@
|
||||
---
|
||||
title: Arris TG2492LG
|
||||
description: Instructions on how to integrate Arris TG2492LG routers into Home Assistant.
|
||||
logo: arris.jpg
|
||||
ha_category:
|
||||
- Presence Detection
|
||||
ha_release: 0.109
|
||||
---
|
||||
|
||||
This platform allows you to detect presence by looking at connected devices to an Arris TG2492LG router.
|
||||
|
||||
This is one of the routers provided by:
|
||||
* [Ziggo](https://www.ziggo.nl/), a cable operator in the Netherlands, to their customers as the Ziggo Connectbox.
|
||||
* [Virgin Media](https://www.virginmedia.com/), a cable operator in the United Kingdom, to their customers as the Hub 3.
|
||||
|
||||
<div class='note warning'>
|
||||
The router prevents the admin user from logging in twice. This can cause problems with accessing the router's configuration pages while this platform is active.
|
||||
</div>
|
||||
|
||||
To use this device tracker in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
device_tracker:
|
||||
- platform: arris_tg2492lg
|
||||
password: YOUR_ADMIN_PASSWORD
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The IP address of your router. The default value is `192.168.178.1`.
|
||||
required: false
|
||||
type: string
|
||||
password:
|
||||
description: The password for your admin account.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
See the [device tracker integration page](/integrations/device_tracker/) for instructions how to configure the people to be tracked.
|
||||
@ -82,6 +82,8 @@ sensors:
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
"devices":
|
||||
description: Connected devices sensor
|
||||
"upload":
|
||||
description: TX upload sensor
|
||||
"download":
|
||||
@ -109,6 +111,7 @@ asuswrt:
|
||||
username: YOUR_ADMIN_USERNAME
|
||||
ssh_key: /config/id_rsa
|
||||
sensors:
|
||||
- devices
|
||||
- upload
|
||||
- download
|
||||
- upload_speed
|
||||
@ -117,6 +120,7 @@ asuswrt:
|
||||
|
||||
The example above, creates the following sensors:
|
||||
|
||||
- sensor.asuswrt_devices_connected
|
||||
- sensor.asuswrt_download (unit_of_measurement: Gigabyte - *Daily accumulation*)
|
||||
- sensor.asuswrt_download_speed (unit_of_measurement: Mbit/s)
|
||||
- sensor.asuswrt_upload (unit_of_measurement: Gigabyte - *Daily accumulation*)
|
||||
|
||||
78
source/_integrations/atag.markdown
Normal file
78
source/_integrations/atag.markdown
Normal file
@ -0,0 +1,78 @@
|
||||
---
|
||||
title: Atag
|
||||
description: Instructions on how to setup Atag integration.
|
||||
ha_category:
|
||||
- Climate
|
||||
- Water heater
|
||||
- Sensor
|
||||
ha_release: 0.109
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: atag
|
||||
---
|
||||
|
||||
The `Atag` integration allows Home Assistant to connect to [Atag One](https://atag-one.com) thermostats, reporting and setting its status.
|
||||
The integration implements the following platforms:
|
||||
|
||||
- Climate
|
||||
- Water Heater
|
||||
- Sensor
|
||||
|
||||
## Configuration
|
||||
|
||||
The Atag integration can be enabled directly from Home Assistant. Navigate to `configuration`, then `integrations` and click `add`. Click `Atag` to initiate the configuration.
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: Atag hostname or IP address.
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: API Port. Only change if you are connecting indirectly (e.g. through reverse proxy)
|
||||
required: false
|
||||
type: integer
|
||||
{% endconfiguration %}
|
||||
|
||||
## Climate
|
||||
|
||||
The `Atag` climate platform provides current and target temperature information for the heating system, boiler status and HVAC mode.
|
||||
|
||||
### Integration services
|
||||
|
||||
This integration supports the following services (see [Climate](/integrations/climate/)).
|
||||
|
||||
- [`set_temperature`](/integrations/climate/#service-climateset_temperature)
|
||||
- [`set_hvac_mode`](/integrations/climate/#service-climateset_hvac_mode)
|
||||
- `heat` for thermostat mode
|
||||
- `auto` for weather-based mode
|
||||
- [`set_preset_mode`](/integrations/climate/#service-climateset_preset_mode)
|
||||
- `Manual` enable manual operation
|
||||
- `Auto` enable schedule based operation
|
||||
- `Extend` delay the next scheduled temperature update by the default extend period
|
||||
- `away` enable the vacation mode for 1 day or until another preset is activated
|
||||
- `boost` enable fireplace mode
|
||||
|
||||
<div class='note'>
|
||||
`HVAC mode Auto` (Weather based) should not be confused with `Preset mode Auto` (Sheduled, thermostat mode).
|
||||
Currently selection of custom timeframes in Extend, Away and boost modes is not supported. The default settings can be changed on the device.
|
||||
</div>
|
||||
|
||||
## Water Heater
|
||||
|
||||
The Water Heater reports current and target temperature for Domestic Hot Water demand, as well as boiler status (heating or idle). This can be used to detect hot water demand, such as a running shower or tap water.
|
||||
Setting target values is currently not supported.
|
||||
|
||||
## Sensor
|
||||
|
||||
Not all metrics reported by the One are part of either the Water-Heater or Climate platform. Additional sensors are added to Home Assistant to monitor these metrics, which can be disabled in the UI if preferred. Navigate to `Configuration`, `Entities` and select the entity you wish to disable.
|
||||
The following sensors will be added to Home Assistant:
|
||||
|
||||
### Sensors enabled by default
|
||||
|
||||
- `average_outside_temperature`
|
||||
- `burning_hours`
|
||||
- `ch_return_temperature`
|
||||
- `ch_water_pressure`
|
||||
- `ch_water_temperature`
|
||||
- `flame`
|
||||
- `outside_temperature`
|
||||
- `weather_status`
|
||||
@ -16,6 +16,7 @@ The way these sensors are displayed in the frontend can be modified in the [cust
|
||||
|
||||
- **None**: Generic on/off. This is the default and doesn't need to be set.
|
||||
- **battery**: `on` means low, `off` means normal
|
||||
- **battery_charging**: `on` means charging, `off` means not charging
|
||||
- **cold**: `on` means cold, `off` means normal
|
||||
- **connectivity**: `on` means connected, `off` means disconnected
|
||||
- **door**: `on` means open, `off` means closed
|
||||
|
||||
@ -7,6 +7,7 @@ ha_category:
|
||||
- Presence Detection
|
||||
- Lock
|
||||
- Sensor
|
||||
- Notifications
|
||||
ha_release: 0.64
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
@ -26,6 +27,7 @@ This integration provides the following platforms:
|
||||
- Device tracker: The location of your car.
|
||||
- Lock: Control the lock of your car.
|
||||
- Sensors: Mileage, remaining range, remaining fuel, charging time remaining (electric cars), charging status (electric cars), remaining range electric (electric cars).
|
||||
- Notifications: Send messages or Points of Interest (POI) to your car.
|
||||
- Services: Turn on air condition, sound the horn, flash the lights and update the state. More details can be found [here](/integrations/bmw_connected_drive/#services).
|
||||
|
||||
## Configuration
|
||||
@ -71,6 +73,44 @@ bmw_connected_drive:
|
||||
default: false
|
||||
{% endconfiguration %}
|
||||
|
||||
## Notifications
|
||||
|
||||
The `bmw_connected_drive` integration offers a notification service. Using this service you can send messages or Points of Interest (POI) to your vehicle. In your vehicle you can select this POI and the navigation will automatically start using the POI as a destination.
|
||||
The name of the service is `notify.bmw_connected_drive_<your_vehicle>`.
|
||||
|
||||
### Examples
|
||||
|
||||
A few examples on how to use the notification service.
|
||||
|
||||
#### Send a text message to your vehicle
|
||||
|
||||
```yaml
|
||||
...
|
||||
action:
|
||||
service: notify.bmw_connected_drive_<your_vehicle>
|
||||
data:
|
||||
title: Message from Home Assistant # optional, will default to "Home Assistant" when left empty
|
||||
message: The text of the message you want to send to your vehicle
|
||||
```
|
||||
|
||||
#### Send a Point of Interest to your vehicle
|
||||
|
||||
```yaml
|
||||
...
|
||||
action:
|
||||
service: notify.bmw_connected_drive_<your_vehicle>
|
||||
data:
|
||||
message: The name of the POI # this is shown on the iDrive dashboard
|
||||
data:
|
||||
location:
|
||||
latitude: 48.177024
|
||||
longitude: 11.559107
|
||||
street: Street name # Optional
|
||||
city: City name # Optional
|
||||
postal_code: Postal Code # Optional
|
||||
country: Country # Optional
|
||||
```
|
||||
|
||||
## Services
|
||||
|
||||
The `bmw_connected_drive` integration offers several services. In case you need to provide the vehicle identification number (VIN) as a parameter, you can see the VIN in the attributes of the device tracker for the vehicle. The VIN is a 17 digit alphanumeric string, e.g., `WBANXXXXXX1234567`.
|
||||
|
||||
@ -7,16 +7,18 @@ ha_release: 0.23
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@robbiet480'
|
||||
- '@bieniu'
|
||||
ha_domain: braviatv
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
The `braviatv` platform allows you to control a [Sony Bravia TV](https://www.sony.com/).
|
||||
|
||||
Almost all [Sony Bravia TV 2013 and newer](https://info.tvsideview.sony.net/en_ww/home_device.html#bravia) are supported. A more generic method for older TVs connected to a Raspberry Pi with HDMI-CEC is explained further below.
|
||||
|
||||
You will need to configure your TV to allow the Home Assistant for remote usage. To do that, ensure that your TV is turned on. Open the configuration popup on Home Assistant and enter a random PIN (for example 0000). After that, the TV will show you a PIN and Home Assistant will allow you to re-enter that PIN. Enter the PIN shown on your TV and Home Assistant will be able to control your Sony Bravia TV.
|
||||
You can setup the Sony Bravia TV via **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select Sony Bravia TV.
|
||||
|
||||
To add a TV to your installation, add the following to your `configuration.yaml` file:
|
||||
If you have following configuration in your `configuration.yaml` file it will be imported to the Integrations:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
@ -37,11 +39,11 @@ name:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
You are also able to configure the TV manually by placing a `bravia.conf` file in your [configuration directory](/docs/configuration/) with the following information - please update the details to match your setup:
|
||||
A new setup via `configuration.yaml` file is not possible.
|
||||
|
||||
```json
|
||||
{"192.168.0.10": {"pin": "7745", "mac": "ac:1e:0a:e1:0c:01"}}
|
||||
```
|
||||
## Extra configuration for the integration
|
||||
|
||||
The integration allows you to change ignored TV sources from the front end. Enter which Sony Bravia TV integration you want to change options on and press the cog wheel.
|
||||
|
||||
## For TVs older than 2013
|
||||
|
||||
|
||||
@ -44,6 +44,10 @@ mac:
|
||||
description: Device MAC address.
|
||||
required: true
|
||||
type: string
|
||||
type:
|
||||
description: "Device type. Choose one from: `rm`, `rm2`, `rm_mini`, `rm_pro_phicomm`, `rm2_home_plus`, `rm2_home_plus_gdt`, `rm2_pro_plus`, `rm2_pro_plus2`, `rm2_pro_plus_bl`, `rm_mini_shate`, `rm_mini3_newblackbean`, `rm_mini3_redbean`, `rm4_mini`, `rm4_pro`, `rm4c_mini`, `rm4c_pro`."
|
||||
required: false
|
||||
type: string
|
||||
timeout:
|
||||
description: Timeout in seconds for the connection to the device.
|
||||
required: false
|
||||
@ -174,9 +178,58 @@ script:
|
||||
- turn off display
|
||||
```
|
||||
|
||||
### Troubleshooting
|
||||
|
||||
Many users are experiencing problems with the new Broadlink RM Mini 3 and the entire RM4 series.
|
||||
|
||||
Once connected to the cloud, these devices lose their local capabilities and can no longer be controlled by Home Assistant.
|
||||
|
||||
To fix the problem, you need to follow these steps:
|
||||
- Remove the device from Broadlink App
|
||||
- Factory reset the device
|
||||
- Add the device to your local network using the app
|
||||
- Do not set up a cloud (not now, not ever)
|
||||
- Specify the correct device type in the configuration file
|
||||
|
||||
Example 1: Set up the new RM Mini 3 using remote platform
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
remote:
|
||||
- platform: broadlink
|
||||
host: IP_ADDRESS
|
||||
mac: MAC_ADDRESS
|
||||
type: rm_mini3_redbean
|
||||
```
|
||||
|
||||
Example 2: Set up RM4C Mini using switch platform
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
- platform: broadlink
|
||||
host: IP_ADDRESS
|
||||
mac: MAC_ADDRESS
|
||||
type: rm4c_mini
|
||||
```
|
||||
|
||||
Example 3: Set up RM4 Pro using sensor platform
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: broadlink
|
||||
host: IP_ADDRESS
|
||||
mac: MAC_ADDRESS
|
||||
type: rm4_pro
|
||||
monitored_conditions:
|
||||
- temperature
|
||||
- humidity
|
||||
```
|
||||
|
||||
## Sensor
|
||||
|
||||
The `broadlink` sensor platform let you monitor data from an RM2 and A1 E-air. There is currently no support for the cloud API.
|
||||
The `broadlink` sensor platform let you monitor data from an RM2, RM4 and A1 E-air. There is currently no support for the cloud API.
|
||||
|
||||
To enable it, add the following lines to your `configuration.yaml`:
|
||||
|
||||
@ -204,6 +257,10 @@ name:
|
||||
required: false
|
||||
default: Broadlink sensor
|
||||
type: string
|
||||
type:
|
||||
description: "Device type. Choose one from: `a1`, `rm`, `rm2`, `rm_pro_phicomm`, `rm2_home_plus`, `rm2_home_plus_gdt`, `rm2_pro_plus`, `rm2_pro_plus2`, `rm2_pro_plus_bl`, `rm4_mini`, `rm4_pro`, `rm4c_mini`, `rm4c_pro`."
|
||||
required: false
|
||||
type: string
|
||||
scan_interval:
|
||||
description: Time in seconds to fetch data from sensors.
|
||||
required: false
|
||||
@ -316,8 +373,8 @@ friendly_name:
|
||||
required: false
|
||||
type: string
|
||||
type:
|
||||
description: "Switch type. Choose one from: `rm`, `rm2`, `rm_mini`, `rm_pro_phicomm`, `rm2_home_plus`, `rm2_home_plus_gdt`, `rm2_pro_plus`, `rm2_pro_plus2`, `rm2_pro_plus_bl`, `rm_mini_shate`, `sp1`, `sp2`, `honeywell_sp2`, `sp3`, `spmini2`, `spminiplus` or `mp1`. `SC1` devices can be registered as `sp2`."
|
||||
required: true
|
||||
description: "Device type. Choose one from: `rm`, `rm2`, `rm_mini`, `rm_pro_phicomm`, `rm2_home_plus`, `rm2_home_plus_gdt`, `rm2_pro_plus`, `rm2_pro_plus2`, `rm2_pro_plus_bl`, `rm_mini_shate`, `rm_mini3_newblackbean`, `rm_mini3_redbean`, `rm4_mini`, `rm4_pro`, `rm4c_mini`, `rm4c_pro`, `sp1`, `sp2`, `honeywell_sp2`, `sp3`, `spmini2`, `spminiplus` or `mp1`. `SC1` devices can be registered as `sp2`."
|
||||
required: false
|
||||
type: string
|
||||
switches:
|
||||
description: The array that contains all switches.
|
||||
|
||||
@ -29,6 +29,10 @@ host:
|
||||
default: 192.168.1.254
|
||||
required: false
|
||||
type: string
|
||||
smarthub_model:
|
||||
description: The model of your BT Smarthub 1 or 2. If this option is omitted, it will attempt to detect the hub model.
|
||||
required: false
|
||||
type: integer
|
||||
{% endconfiguration %}
|
||||
|
||||
See the [device tracker integration page](/integrations/device_tracker/) for instructions on how to configure the people to be tracked.
|
||||
|
||||
@ -165,7 +165,7 @@ operation_mode_comfort_address:
|
||||
required: false
|
||||
type: string
|
||||
operation_modes:
|
||||
description: Overrides the supported operation modes.
|
||||
description: Overrides the supported operation modes. Provide the supported `hvac_mode` and `preset_mode` values for your device.
|
||||
required: false
|
||||
type: list
|
||||
on_off_address:
|
||||
|
||||
@ -273,6 +273,10 @@ temperature_state_topic:
|
||||
description: The MQTT topic to subscribe for changes in the target temperature. If this is not set, the target temperature works in optimistic mode (see below).
|
||||
required: false
|
||||
type: string
|
||||
temperature_unit:
|
||||
description: Defines the temperature unit of the device, `C` or `F`. If this is not set, the temperature unit is set to the system temperature unit.
|
||||
required: false
|
||||
type: string
|
||||
temp_step:
|
||||
description: Step size for temperature set point.
|
||||
type: float
|
||||
|
||||
@ -8,9 +8,13 @@ ha_release: 0.32
|
||||
ha_domain: currencylayer
|
||||
---
|
||||
|
||||
The `currencylayer` sensor will show you the current exchange rate from [Currencylayer](https://currencylayer.com/) that provides real-time exchange rates for [170 currencies](https://currencylayer.com/currencies). The free account is limited to only USD as a base currency, allows 250 requests per month, and updates daily.
|
||||
The `currencylayer` sensor will show you the current exchange rate from [Currencylayer](https://currencylayer.com/) that provides real-time exchange rates for [170 currencies](https://currencylayer.com/currencies). The free account is limited to only USD as a base currency, allows 250 requests per month and updates daily.
|
||||
|
||||
Obtain your API key [here](https://currencylayer.com/product)
|
||||
## Setup
|
||||
|
||||
Obtain your API key from [here](https://currencylayer.com/product).
|
||||
|
||||
## Configuration
|
||||
|
||||
To enable this sensor, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -3,6 +3,7 @@ title: DirecTV
|
||||
description: Instructions on how to integrate DirecTV receivers into Home Assistant.
|
||||
ha_category:
|
||||
- Media Player
|
||||
- Remote
|
||||
ha_release: 0.25
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: directv
|
||||
@ -60,3 +61,66 @@ Available services: turn_on, turn_off, media_play, media_pause, media_stop, medi
|
||||
| `entity_id` | yes | Target a specific media player. Defaults to all. |
|
||||
| `media_content_id` | no | The channel number to change to. |
|
||||
| `media_content_type` | no | A media type. Has to be `channel`.
|
||||
|
||||
## Remote
|
||||
|
||||
The DirecTV remote platform allows you to send remote control buttons to a DirecTV receiver. It is automatically set up when a DirecTV receiver is configured.
|
||||
|
||||
At the moment, the following buttons are supported:
|
||||
|
||||
- `power`
|
||||
- `poweron`
|
||||
- `poweroff`
|
||||
- `format`
|
||||
- `pause`
|
||||
- `rew`
|
||||
- `replay`
|
||||
- `stop`
|
||||
- `advance`
|
||||
- `ffwd`
|
||||
- `record`
|
||||
- `play`
|
||||
- `guide`
|
||||
- `active`
|
||||
- `list`
|
||||
- `exit`
|
||||
- `back`
|
||||
- `menu`
|
||||
- `info`
|
||||
- `up`
|
||||
- `down`
|
||||
- `left`
|
||||
- `right`
|
||||
- `select`
|
||||
- `red`
|
||||
- `green`
|
||||
- `yellow`
|
||||
- `blue`
|
||||
- `chanup`
|
||||
- `chandown`
|
||||
- `prev`
|
||||
- `0`
|
||||
- `1`
|
||||
- `2`
|
||||
- `3`
|
||||
- `4`
|
||||
- `5`
|
||||
- `6`
|
||||
- `7`
|
||||
- `8`
|
||||
- `9`
|
||||
- `dash`
|
||||
- `enter`
|
||||
|
||||
A typical service call for press several buttons looks like this.
|
||||
|
||||
```yaml
|
||||
service: remote.send_command
|
||||
data:
|
||||
entity_id: remote.directv_entity
|
||||
command:
|
||||
- left
|
||||
- left
|
||||
- menu
|
||||
- select
|
||||
```
|
||||
|
||||
@ -38,7 +38,7 @@ token:
|
||||
|
||||
### Setting up the bot
|
||||
|
||||
Bots can only send messages to servers or attach local available images. To add the bot to a server you are an admin on, get the details of the bot from the [Discord My Apps page](https://discordapp.com/developers/applications/me).
|
||||
Bots can send messages to servers and users or attach local available images. To add the bot to a server you are an admin on, get the details of the bot from the [Discord My Apps page](https://discordapp.com/developers/applications/me).
|
||||
|
||||
<p class='img'>
|
||||
<img src='{{site_root}}/images/screenshots/discord-bot.png' />
|
||||
@ -62,7 +62,7 @@ Once the bot has been added to your server, get the channel ID of the channel yo
|
||||
|
||||
Right click channel name and copy the channel ID (**Copy ID**).
|
||||
|
||||
This channel ID has to be used as the target when calling the notification service. Multiple channel IDs can be specified, across multiple servers.
|
||||
This channel or user ID has to be used as the target when calling the notification service. Multiple channel or user IDs can be specified, across multiple servers or direct messages.
|
||||
|
||||
#### Example service call
|
||||
|
||||
|
||||
@ -57,6 +57,7 @@ name:
|
||||
| `region_state` | State (Bundesland) in abriviated form the requested region is located, e.g., "HE" for "Hessen". |
|
||||
| `region_id` | Region ID assigned by DWD. |
|
||||
| `warning_count` | *(int)* Number of issued warnings. There can be more than one warning issued at once. |
|
||||
| `warning_<x>` | The warning as a whole JSON object containing the following attributes as nested attributes. |
|
||||
| `warning_<x>_level` | *(int)* Issued warning level between 0 and 4. <br/>0: Keine Warnungen <br/>1: Wetterwarnungen <br/>2: Warnungen vor markantem Wetter<br/>3: Unwetterwarnungen<br/>4: Warnungen vor extremem Unwetter |
|
||||
| `warning_<x>_type` | *(int)* Issued warning type. <br/>0: Gewitter, Starkes Gewitter<br/>1: Windböen, Sturmböen<br/>2: ?<br/>3: Schneefall<br/>4: Nebel<br/>5: Frost <br/>6: Glätte, Glatteis<br/>8: Hitze (always level 10)<br/>9: UV-Index (always level 20)<br/>Please be aware that the type numbers represent more like a category than an exact number-to-string match. For example Type `6` can mean `GLÄTTE` or `GLATTEIS` or similar. |
|
||||
| `warning_<x>_name` | This name correlates with the warning type and indicates it in short as a string. |
|
||||
|
||||
@ -5,6 +5,7 @@ ha_category:
|
||||
- Hub
|
||||
- Light
|
||||
- Switch
|
||||
- Cover
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.106
|
||||
ha_codeowners:
|
||||
@ -13,12 +14,13 @@ ha_config_flow: true
|
||||
ha_domain: dynalite
|
||||
---
|
||||
|
||||
Philips Dynalite support is integrated into Home Assistant as a hub that can drive the light and switch platforms.
|
||||
Philips Dynalite support is integrated into Home Assistant as a hub that can drive the light, switch, and cover platforms.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
- Lights
|
||||
- Switches
|
||||
- Covers
|
||||
|
||||
A Philips Dynalite hub connects to the Dynet network, which is composed of areas, channels, and preset.
|
||||
|
||||
@ -92,6 +94,16 @@ area:
|
||||
description: Name of the area.
|
||||
required: true
|
||||
type: string
|
||||
template:
|
||||
description: "Type of template to use for the area. Supported values are: `room` and `time_cover`. They are described in detail below in the **template** section. If the template parameters are different than defaults, they can be overridden in this section as well."
|
||||
require: false
|
||||
type: string
|
||||
default: No template
|
||||
TEMPLATE_PARAMS:
|
||||
description: "This can be any of the settings of the template. For example, for template `room`: `room_on` and `room_off` are possible options."
|
||||
required: false
|
||||
type: [integer, float]
|
||||
default: Value from **template** section or system defaults
|
||||
fade:
|
||||
description: Fade time for the area, in seconds.
|
||||
required: false
|
||||
@ -138,7 +150,7 @@ area:
|
||||
type: string
|
||||
default: AREA_NAME Channel CHANNEL_NUMBER
|
||||
type:
|
||||
description: "Type of entity this should appear as. Can be either `light` or if this is a device that is not a light (e.g., water heater), can be `switch`."
|
||||
description: "Type of entity this channel should appear as. Can be either `light` or if this is a device that is not a light (e.g., water heater), can be `switch`."
|
||||
require: false
|
||||
type: string
|
||||
default: light
|
||||
@ -167,6 +179,66 @@ preset:
|
||||
required: false
|
||||
type: float
|
||||
default: 2.0
|
||||
template:
|
||||
description: Set the default parameters for the templates.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
room:
|
||||
description: This is used to define a room that has a preset to turn on all the channels in the area and a preset to turn off.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
room_on:
|
||||
description: Preset to turn area on.
|
||||
required: false
|
||||
type: integer
|
||||
default: 1
|
||||
room_off:
|
||||
description: Preset to turn area off.
|
||||
required: false
|
||||
type: integer
|
||||
default: 4
|
||||
time_cover:
|
||||
description: "This is used to define a cover that has 3 presets: `open`, `close`, and `stop`. Potentially can also use a channel that some systems (e.g., Control4) use to also send commands to open and close the cover. It uses the duration it takes to open or close to determine position. In addition, many times, these covers include tilt by opening or closing for a short time, so this can be defined as well."
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
open:
|
||||
description: Preset to open the cover.
|
||||
required: false
|
||||
type: integer
|
||||
default: 1
|
||||
close:
|
||||
description: Preset to close the cover.
|
||||
required: false
|
||||
type: integer
|
||||
default: 2
|
||||
stop:
|
||||
description: Preset to stop the cover.
|
||||
required: false
|
||||
type: integer
|
||||
default: 4
|
||||
channel_cover:
|
||||
description: Channel that monitors the cover.
|
||||
required: false
|
||||
type: integer
|
||||
default: No channel
|
||||
duration:
|
||||
description: Time in seconds it takes to open or close the cover.
|
||||
required: false
|
||||
type: integer
|
||||
default: 60
|
||||
tilt:
|
||||
description: "Time in seconds it takes to open or close the cover tilt. `0` means that the cover does not support tilt."
|
||||
require: false
|
||||
type: integer
|
||||
default: 0
|
||||
class:
|
||||
description: "Type of cover for Home Assistant. Any of the possible [cover classes](/integrations/cover/#device-class) (e.g. `blind`, `garage`, `shutter`) are possible."
|
||||
require: false
|
||||
type: string
|
||||
default: shutter
|
||||
{% endconfiguration %}
|
||||
|
||||
## Examples
|
||||
@ -182,9 +254,13 @@ dynalite:
|
||||
area:
|
||||
'1':
|
||||
name: Office
|
||||
template: room
|
||||
'2':
|
||||
name: Living Room
|
||||
template: room
|
||||
nodefault: true
|
||||
room_on: 2
|
||||
room_off: 5
|
||||
channel:
|
||||
'2':
|
||||
name: Entrance Spot
|
||||
@ -197,11 +273,18 @@ dynalite:
|
||||
'6':
|
||||
name: All Off
|
||||
fade: 3.0
|
||||
'4':
|
||||
name: Curtain
|
||||
template: time_cover
|
||||
preset:
|
||||
'1':
|
||||
name: 'On'
|
||||
'4':
|
||||
name: 'Off'
|
||||
template:
|
||||
room:
|
||||
room_on: 1
|
||||
room_off: 4
|
||||
```
|
||||
|
||||
## Initial configuration and discovery
|
||||
|
||||
@ -12,25 +12,27 @@ The `xiaomi_miio` fan platform allows you to control the Xiaomi Air Purifier, Ai
|
||||
|
||||
Supported devices:
|
||||
|
||||
| Name | Model | Model no. |
|
||||
| ------------------- | ---------------------- | --------- |
|
||||
Air Purifier | zhimi.airpurifier.v1 | |
|
||||
Air Purifier 2 | zhimi.airpurifier.v2 | FJY4006CN |
|
||||
Air Purifier V3 | zhimi.airpurifier.v3 | |
|
||||
Air Purifier V5 | zhimi.airpurifier.v5 | |
|
||||
Air Purifier Pro | zhimi.airpurifier.v6 | |
|
||||
Air Purifier Pro V7 | zhimi.airpurifier.v7 | |
|
||||
Air Purifier 2 (mini) | zhimi.airpurifier.m1 | |
|
||||
Air Purifier (mini) | zhimi.airpurifier.m2 | |
|
||||
Air Purifier MA1 | zhimi.airpurifier.ma1 | |
|
||||
Air Purifier 2S | zhimi.airpurifier.ma2 | |
|
||||
Air Purifier 2S | zhimi.airpurifier.mc1 | |
|
||||
Air Purifier Super | zhimi.airpurifier.sa1 | |
|
||||
Air Purifier Super 2 | zhimi.airpurifier.sa2 | |
|
||||
Air Humidifier | zhimi.humidifier.v1 | |
|
||||
Air Humidifier CA1 | zhimi.humidifier.ca1 | |
|
||||
Air Humidifier CB1 | zhimi.humidifier.cb1 | |
|
||||
Air Fresh VA2 | zhimi.airfresh.va2 | |
|
||||
| Name | Model | Model no. |
|
||||
| ---------------------- | ---------------------- | --------- |
|
||||
| Air Purifier | zhimi.airpurifier.v1 | |
|
||||
| Air Purifier 2 | zhimi.airpurifier.v2 | FJY4006CN |
|
||||
| Air Purifier V3 | zhimi.airpurifier.v3 | |
|
||||
| Air Purifier V5 | zhimi.airpurifier.v5 | |
|
||||
| Air Purifier Pro | zhimi.airpurifier.v6 | |
|
||||
| Air Purifier Pro V7 | zhimi.airpurifier.v7 | |
|
||||
| Air Purifier 2 (mini) | zhimi.airpurifier.m1 | |
|
||||
| Air Purifier (mini) | zhimi.airpurifier.m2 | |
|
||||
| Air Purifier MA1 | zhimi.airpurifier.ma1 | |
|
||||
| Air Purifier 2S | zhimi.airpurifier.ma2 | |
|
||||
| Air Purifier 2S | zhimi.airpurifier.mc1 | |
|
||||
| Air Purifier Super | zhimi.airpurifier.sa1 | |
|
||||
| Air Purifier Super 2 | zhimi.airpurifier.sa2 | |
|
||||
| Air Purifier 3 (2019) | zhimi.airpurifier.ma4 | |
|
||||
| Air Purifier 3H (2019) | zhimi.airpurifier.mb3 | |
|
||||
| Air Humidifier | zhimi.humidifier.v1 | |
|
||||
| Air Humidifier CA1 | zhimi.humidifier.ca1 | |
|
||||
| Air Humidifier CB1 | zhimi.humidifier.cb1 | |
|
||||
| Air Fresh VA2 | zhimi.airfresh.va2 | |
|
||||
|
||||
|
||||
## Features
|
||||
@ -167,6 +169,39 @@ Air Fresh VA2 | zhimi.airfresh.va2 | |
|
||||
- `illuminance`
|
||||
- `buzzer`
|
||||
|
||||
### Air Purifier 3/3H (2019) (zhimi.airpurifier.ma4/zhimi.airpurifier.mb3)
|
||||
|
||||
This model uses newer MiOT communication protocol.
|
||||
|
||||
- Power (on, off)
|
||||
- Operation modes (auto, silent, favorite, fan)
|
||||
- Buzzer (on, off)
|
||||
- Child lock (on, off)
|
||||
- LED (on, off)
|
||||
- Favorite Level (0...16)
|
||||
- Fan Level (1...3)
|
||||
- Attributes
|
||||
- `model`
|
||||
- `temperature`
|
||||
- `humidity`
|
||||
- `aqi`
|
||||
- `mode`
|
||||
- `filter_hours_used`
|
||||
- `filter_life_remaining`
|
||||
- `favorite_level`
|
||||
- `child_lock`
|
||||
- `led`
|
||||
- `motor_speed`
|
||||
- `average_aqi`
|
||||
- `purify_volume`
|
||||
- `use_time`
|
||||
- `buzzer`
|
||||
- `led_brightness`
|
||||
- `filter_rfid_product_id`
|
||||
- `filter_rfid_tag`
|
||||
- `filter_type`
|
||||
- `fan_level`
|
||||
|
||||
### Air Purifier V3 (zhimi.airpurifier.v3)
|
||||
|
||||
- Power (on, off)
|
||||
@ -408,6 +443,15 @@ Set the favorite level of the operation mode "favorite".
|
||||
| `entity_id` | no | Only act on a specific Xiaomi miIO fan entity. |
|
||||
| `level` | no | Level, between 0 and 16. |
|
||||
|
||||
### Service `xiaomi_miio.fan_set_fan_level` (Air Purifiers only)
|
||||
|
||||
Set the fan level for "fan" operation mode.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
|---------------------------|----------|---------------------------------------------------------|
|
||||
| `entity_id` | no | Only act on a specific Xiaomi MiOT fan entity. |
|
||||
| `level` | no | Level, between 1 and 3. |
|
||||
|
||||
### Service `xiaomi_miio.fan_set_auto_detect_on` (Air Purifier 2S and Air Purifier Pro only)
|
||||
|
||||
Turn the auto detect on.
|
||||
|
||||
@ -5,8 +5,10 @@ ha_category:
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.103
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@ChrisMandich'
|
||||
- '@bdraco'
|
||||
ha_domain: flume
|
||||
---
|
||||
|
||||
@ -18,7 +20,9 @@ Flume monitors the real-time status of your home water meter. Allowing the end-u
|
||||
|
||||
You can find your Client ID and Client Secret under "API Access" on the [settings page](https://portal.flumetech.com/#settings).
|
||||
|
||||
To enable the flume sensor, add the following lines to your `configuration.yaml` file:
|
||||
To add `Flume` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Flume**.
|
||||
|
||||
Alternatively, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
|
||||
@ -30,31 +30,38 @@ There is currently support for the following device types within Home Assistant:
|
||||
- [FRITZ!DECT 301](https://en.avm.de/products/fritzdect/fritzdect-301/)
|
||||
- [Eurotronic Comet DECT](https://eurotronic.org/produkte/elektronische-heizkoerperthermostate/sparmatic-comet/)
|
||||
|
||||
## Setup
|
||||
## Configuration
|
||||
|
||||
To add the AVM FRITZ!Box integration to your installation, go to **Configuration** -> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **AVM FRITZ!Box**.
|
||||
|
||||
If you have enabled SSDP discovery, it’s likely that you just have to confirm the detected device with username and password.
|
||||
|
||||
### Configuration via YAML
|
||||
|
||||
YAML configuration is still around for people that prefer YAML, but it's deprecated and you should not use it anymore.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
fritzbox:
|
||||
devices:
|
||||
- host: fritz.box
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
- password: YOUR_PASSWORD
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
devices:
|
||||
description: A list of FRITZ!Box devices.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
host:
|
||||
description: The hostname or IP address of the FRITZ!Box.
|
||||
required: true
|
||||
required: false
|
||||
type: string
|
||||
default: fritz.box
|
||||
username:
|
||||
description: The username for Smart Home access.
|
||||
required: true
|
||||
required: false
|
||||
type: string
|
||||
default: admin
|
||||
password:
|
||||
description: The password of the user.
|
||||
required: true
|
||||
|
||||
@ -86,6 +86,11 @@ homekit:
|
||||
required: false
|
||||
type: boolean
|
||||
default: false
|
||||
zeroconf_default_interface:
|
||||
description: By default, zeroconf will attempt to bind to all interfaces. For systems running using network isolation or similar, this may result HomeKit not being seen on the network. Change this option to `true` if HomeKit cannot be discovered.
|
||||
required: true
|
||||
type: boolean
|
||||
default: false
|
||||
advertise_ip:
|
||||
description: If you need to override the IP address used for mDNS advertisement. (For example, using network isolation in Docker and together with an mDNS forwarder like `avahi-daemon` in reflector mode)
|
||||
required: false
|
||||
@ -167,16 +172,20 @@ homekit:
|
||||
|
||||
After Home Assistant has started, the entities specified by the filter are exposed to HomeKit if they are [supported](#supported-components). To add them:
|
||||
|
||||
1. Open the Home Assistant frontend. A new card will display the `pin code`. Note: If pin code is not displayed, check "Notifications" (the bell icon) in the lower-left of the Home Assistant UI.
|
||||
1. Open the Home Assistant frontend. A new card will display the pairing QR code and the `pin code` as seen in the example below. Note: If pin code is not displayed, check "Notifications" (the bell icon) in the lower-left of the Home Assistant UI.
|
||||
2. Open the `Home` app.
|
||||
3. Click `Add Accessory`, then select `Don't Have a Code or Can't Scan?` and choose the `Home Assistant Bridge`.
|
||||
3. Click `Add Accessory`, then scan the QR code or select `Don't Have a Code or Can't Scan?` and choose the `Home Assistant Bridge`.
|
||||
4. Confirm that you are adding an `Uncertified Accessory` by clicking on `Add Anyway`.
|
||||
5. Enter the `PIN` code.
|
||||
5. Enter the `PIN` code (skip this step if you scanned the QR code).
|
||||
6. Follow the setup by clicking on `Next` and lastly `Done` in the top right-hand corner.
|
||||
7. The `Home Assistant` Bridge and the Accessories should now be listed in the `Home` app.
|
||||
|
||||
After the setup is completed, you should be able to control your Home Assistant integrations through Apple's Home and Siri.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/homekit_pairing_example.png' />
|
||||
</p>
|
||||
|
||||
## Move Home Assistant install
|
||||
|
||||
If you like to retain your HomeKit pairing through a move to a new Home Assistant device or installation, besides copying the configurations files you need to copy the `.homekit.state` file inside your configurations directory. Keep in mind though that the file is usually hidden by default, depending on your operating system.
|
||||
@ -191,7 +200,7 @@ Currently, this integration uses the `entity_id` to generate a unique `accessory
|
||||
|
||||
### Device Limit
|
||||
|
||||
The HomeKit guidelines only allow a maximum of 100 unique accessories (`aid`) per bridge. Be mindful of this when configuring the filter(s).
|
||||
The HomeKit Accessory Protocol Specification only allow a maximum of 150 unique accessories (`aid`) per bridge. Be mindful of this when configuring the filter(s).
|
||||
|
||||
### Persistence Storage
|
||||
|
||||
@ -336,15 +345,18 @@ To avoid any errors, after you have successfully paired your Home Assistant Brid
|
||||
|
||||
The `advertise_ip` option can be used to run this integration even inside an ephemeral Docker container with network isolation enabled, e.g., not using the host network.
|
||||
|
||||
You may also need to set `zeroconf_default_interface` to `true`.
|
||||
|
||||
To use `advertise_ip`, add the option to your `homekit` configuration:
|
||||
|
||||
```yaml
|
||||
homekit:
|
||||
advertise_ip: "STATIC_IP_OF_YOUR_DOCKER_HOST"
|
||||
zeroconf_default_interface: true
|
||||
```
|
||||
|
||||
Restart your Home Assistant instance. This feature requires running an mDNS forwarder on your Docker host, e.g., `avahi-daemon` in reflector mode. This kind of setup most likely requires `safe_mode` during the bridge setup.
|
||||
|
||||
|
||||
## Supported Components
|
||||
|
||||
The following integrations are currently supported:
|
||||
@ -352,7 +364,7 @@ The following integrations are currently supported:
|
||||
| Component | Type Name | Description |
|
||||
| --------- | --------- | ----------- |
|
||||
| alarm_control_panel | SecuritySystem | All security systems. |
|
||||
| automation / input_boolean / remote / scene / script | Switch | All represented as switches. |
|
||||
| automation / input_boolean / remote / scene / script / vacuum | Switch | All represented as switches. |
|
||||
| binary_sensor | Sensor | Support for `co2`, `door`, `garage_door`, `gas`, `moisture`, `motion`, `occupancy`, `opening`, `smoke` and `window` device classes. Defaults to the `occupancy` device class for everything else. |
|
||||
| climate | Thermostat | All climate devices. |
|
||||
| cover | GarageDoorOpener | All covers that support `open` and `close` and have `garage` or `gate` as their `device_class`. |
|
||||
@ -422,7 +434,7 @@ Remember that the iOS device needs to be in the same local network as the Home A
|
||||
|
||||
#### `Home Assistant Bridge` doesn't appear in the Home App (for pairing) - Docker
|
||||
|
||||
Set `network_mode: host`. If you have further problems this [issue](https://github.com/home-assistant/home-assistant/issues/15692) might help.
|
||||
Set `network_mode: host` in your `docker-compose.yaml`. If you have further problems this [issue](https://github.com/home-assistant/home-assistant/issues/15692) might help.
|
||||
|
||||
You can also try to use `avahi-daemon` in reflector mode together with the option `advertise_ip`, see above.
|
||||
|
||||
@ -434,6 +446,10 @@ Configure the network mode as `networkbridge`. Otherwise the Home Assistant Brid
|
||||
|
||||
Pairing eventually fails, you might see and an error message `NonUniqueNameException`. Add the `safe_mode` option to your configuration, see [safe_mode](#safe-mode).
|
||||
|
||||
If [safe_mode](#safe-mode) is not successful, you likely need to enable `zeroconf_default_interface: true` and set a unique name such as `name: MyHASS42`.
|
||||
|
||||
If you had previously paired (even unsuccessfully), you may need to delete your `.homekit.state` file in order to able to successfully pair again. See [Errors during pairing](#errors-during-pairing).
|
||||
|
||||
#### Pairing hangs - only works with debug configuration
|
||||
|
||||
Pairing works fine when the filter is set to only include `demo.demo`, but fails with normal configuration. See [specific entity doesn't work](#specific-entity-doesnt-work)
|
||||
|
||||
@ -1,14 +1,15 @@
|
||||
---
|
||||
title: Islamic Prayer Times
|
||||
description: Instructions on how to integrate the Islamic Prayer Times sensor within Home Assistant.
|
||||
description: Instructions on how to integrate the Islamic Prayer Times integration within Home Assistant.
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_release: 0.85
|
||||
ha_config_flow: true
|
||||
ha_domain: islamic_prayer_times
|
||||
---
|
||||
|
||||
The Islamic Prayer Times (`islamic_prayer_times`) sensor platform displays the various prayer times for Muslims as sensors.
|
||||
The Islamic Prayer Times (`islamic_prayer_times`) integration displays the various prayer times for Muslims as sensors.
|
||||
|
||||
This platform calculates prayer times using the following calculation methods:
|
||||
|
||||
@ -19,35 +20,15 @@ This platform calculates prayer times using the following calculation methods:
|
||||
|
||||
## Configuration
|
||||
|
||||
To enable this sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
Set up the integration through **Configuration -> Integrations -> Islamic Prayer Times**. To import the configuration from `configuration.yaml` remove any previously configured sensors with platform type `islamic_prayer_times` and add the following lines:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: islamic_prayer_times
|
||||
islamic_prayer_times:
|
||||
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
sensors:
|
||||
required: false
|
||||
default: "['fajr', 'dhuhr', 'asr', 'maghrib', 'isha']"
|
||||
type: list
|
||||
description: List of available sensors.
|
||||
keys:
|
||||
fajr:
|
||||
description: Show the fajr prayer time for today.
|
||||
sunrise:
|
||||
description: Show the sunrise for today which is the end of fajr prayer. This is a calculated field and may not necessarily be the same as the astronomical sunrise.
|
||||
dhuhr:
|
||||
description: Show the dhuhr prayer time for today.
|
||||
asr:
|
||||
description: Show the asr prayer time for today.
|
||||
maghrib:
|
||||
description: Show the maghrib prayer time for today.
|
||||
isha:
|
||||
description: Show the isha prayer time for today.
|
||||
midnight:
|
||||
description: Show the midnight for today which is the end of isha prayer. This is a calculated field and is not the same as 12AM.
|
||||
calculation_method:
|
||||
required: false
|
||||
default: 'isna'
|
||||
@ -55,17 +36,22 @@ calculation_method:
|
||||
description: "The calculation method used for prayer times. Must be one of: `karachi`, `isna`, `mwl`, `makkah`."
|
||||
{% endconfiguration %}
|
||||
|
||||
## Integration Sensors
|
||||
|
||||
The following sensors are added by the integration:
|
||||
|
||||
sensors:
|
||||
- fajr: Show the fajr prayer time for today.
|
||||
- sunrise: Show the sunrise for today which is the end of fajr prayer. This is a calculated field and may not necessarily be the same as the astronomical sunrise.
|
||||
- dhuhr: Show the dhuhr prayer time for today.
|
||||
- asr: Show the asr prayer time for today.
|
||||
- maghrib: Show the maghrib prayer time for today.
|
||||
- isha: Show the isha prayer time for today.
|
||||
- midnight: Show the midnight for today which is the end of isha prayer. This is a calculated field and is not the same as 12AM.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry for all available sensors using a non-default calculation method
|
||||
sensor:
|
||||
- platform: islamic_prayer_times
|
||||
# Example configuration.yaml using a non-default calculation method
|
||||
islamic_prayer_times:
|
||||
calculation_method: makkah
|
||||
sensors:
|
||||
- fajr
|
||||
- sunrise
|
||||
- dhuhr
|
||||
- asr
|
||||
- maghrib
|
||||
- isha
|
||||
- midnight
|
||||
|
||||
```
|
||||
|
||||
@ -42,6 +42,11 @@ light:
|
||||
data_template:
|
||||
value: "{{ color_temp }}"
|
||||
entity_id: input_number.temperature_input
|
||||
set_white_value:
|
||||
service: input_number.set_value
|
||||
data_template:
|
||||
value: "{{ white_value }}"
|
||||
entity_id: input_number.white_value_input
|
||||
set_color:
|
||||
- service: input_number.set_value
|
||||
data_template:
|
||||
@ -84,6 +89,11 @@ light:
|
||||
required: false
|
||||
type: template
|
||||
default: optimistic
|
||||
white_value_template:
|
||||
description: Defines a template to get the white value of the light.
|
||||
required: false
|
||||
type: template
|
||||
default: optimistic
|
||||
color_template:
|
||||
description: Defines a template to get the color of the light. Must render a tuple (hue, saturation)
|
||||
required: false
|
||||
@ -114,6 +124,10 @@ light:
|
||||
description: Defines an action to run when the light is given a color temperature command.
|
||||
required: false
|
||||
type: action
|
||||
set_white_value:
|
||||
description: Defines an action to run when the light is given a white value command.
|
||||
required: false
|
||||
type: action
|
||||
set_color:
|
||||
description: Defines an action to run when the light is given a color command.
|
||||
required: false
|
||||
|
||||
@ -11,7 +11,7 @@ ha_iot_class: Assumed State
|
||||
ha_domain: lightwave
|
||||
---
|
||||
|
||||
The `lightwave` integration links Home Assistant with your Lightwave WiFi link for controlling Lightwave lights and switches.
|
||||
The `lightwave` integration links Home Assistant with your Lightwave WiFi link for controlling Lightwave lights, switches and TRVs.
|
||||
|
||||
This integration uses the official API published by Lightwave on their website [https://api.lightwaverf.com/](https://api.lightwaverf.com/).
|
||||
To add your Lightwave devices into your Home Assistant installation, add the following to your `configuration.yaml` file:
|
||||
@ -19,7 +19,7 @@ To add your Lightwave devices into your Home Assistant installation, add the fol
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
lightwave:
|
||||
host: 192.168.1.2
|
||||
host: IP_ADDRESS
|
||||
lights:
|
||||
R1D3:
|
||||
name: Wall lights
|
||||
@ -38,14 +38,84 @@ lightwave:
|
||||
name: Torch socket
|
||||
```
|
||||
|
||||
Where `192.168.1.2` is the IP address of your Lightwave hub.
|
||||
{% configuration %}
|
||||
host:
|
||||
description: IP address of your Lightwave hub
|
||||
required: true
|
||||
type: string
|
||||
lights:
|
||||
description: List of lights you wish to configure
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: Name of the Light
|
||||
required: true
|
||||
type: string
|
||||
switches:
|
||||
description: List of switches you wish to configure
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: Name of the Switch
|
||||
required: true
|
||||
type: string
|
||||
trv:
|
||||
description: TRV configuration
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
trv_proxy_ip:
|
||||
description: IP address of a proxy for TRV integration.
|
||||
required: false
|
||||
type: string
|
||||
default: "127.0.0.1"
|
||||
trv_proxy_port:
|
||||
description: IP port address of a proxy for TRV integration.
|
||||
required: false
|
||||
type: integer
|
||||
default: 7878
|
||||
trvs:
|
||||
description: List of TRVs you wish to configure
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: Name of the TRV
|
||||
required: true
|
||||
type: string
|
||||
serial:
|
||||
description: Serial Number of the TRV
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
Where IP_ADDRESS is the IP address of your Lightwave hub.
|
||||
Each `switch` or `light` requires an `id` and a `name`. The `id` takes the form `R#D#` where `R#` is the room number and `D#` is the device number.
|
||||
|
||||
`lights` and `switches` are optional but one of these must be present.
|
||||
|
||||
The first use of a light or switch will try to register with your Lightwave WiFi Link hub. If the hub has not been registered a message on your hub will be displayed asking you to pair the device. You have 12 seconds to push the button on your hub to accept this. Once done, you should be able to control your lights and switches via Home Assistant. This only needs to be done if the hub has not been registered.
|
||||
|
||||
The Lightwave Home Assistant integration currently supports the following Lightwave devices:
|
||||
# TRVs
|
||||
|
||||
- Lightwave lights
|
||||
- Lightwave switches
|
||||
Lightwave Thermostatic Radiator Values (TRV) are supported but require an additional proxy to capture the current TRV temperature.
|
||||
See [LWProxy](https://github.com/ColinRobbins/Homeassistant-Lightwave-TRV)
|
||||
|
||||
```yaml
|
||||
# Example TRV configuration.yaml for TRVs
|
||||
lightwave:
|
||||
host: IP_ADDRESS
|
||||
lights:
|
||||
R99D1:
|
||||
name: Bedroom Light
|
||||
trv:
|
||||
trv_proxy_ip: 127.0.0.1 # Proxy address, do not change unless running on a different server
|
||||
trv_proxy_port: 7878 # Do not change, unless a port clash
|
||||
trvs:
|
||||
R1Dh: # The ID of the TRV.
|
||||
name: Bedroom TRV
|
||||
serial: E84902 # Serial number of the TRV - found in the Lightwave App, or web site
|
||||
```
|
||||
|
||||
@ -21,11 +21,3 @@ local_ip:
|
||||
```
|
||||
|
||||
To configure via the user interface, select the `Local IP Address` integration.
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: Friendly name of the sensor.
|
||||
required: false
|
||||
type: string
|
||||
default: local_ip
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -65,6 +65,14 @@ For raise/lower buttons (dimmer buttons, shade controls, etc.) there will be two
|
||||
|
||||
For single-action buttons (scene selection, etc.), `action` will be `single`, and there will only be one event fired. This is a limitation of the Lutron controller which doesn't give Home Assistant any way of knowing when a single-action button is released.
|
||||
|
||||
## Keypad LEDs
|
||||
|
||||
Each full-width button on a Lutron SeeTouch, Hybrid SeeTouch, and Tabletop SeeTouch Keypad has an LED that can be controlled by Home Assistant. A service call of switch.turn_off or switch.turn_on against the appropriate LED entity will control the keypad LED.
|
||||
|
||||
Keep in mind that the Lutron system will also control the LED state independent of Home Assistant, according to the programming of the RadioRA2 system. This also means you can query LED states to determine if a certain scene is active, since the LED will have been illuminated by the RadioRA2 repeaters. This includes the "phantom" LEDs of Main Repeater Keypad buttons; even though there is no physical button or LED, the RadioRA2 system tracks the scenes and will "light" the LED that can be queried.
|
||||
|
||||
If a button is not programmed to control any lights or other devices in the RadioRA2 system but is given a name in the programming software, it will be available to fire events in Home Assistant. However, since there is no way to have a scene "active" on a button with no devices associated, the Main Repeater will automatically extinguish the keypad LED a few seconds after the button press. If you wish to have Home Assistant light the keypad LED after a button press, you will need to delay your service call to light the LED for several seconds, so it arrives after the Main Repeater has sent the command to turn it off.
|
||||
|
||||
## Scene
|
||||
|
||||
This integration uses keypad programming to identify scenes. Currently, it works with seeTouch, hybrid seeTouch, main repeater, homeowner, Pico, and seeTouch RF tabletop keypads.
|
||||
|
||||
@ -57,6 +57,22 @@ The following parameters can be controlled for the `climate` platform entities:
|
||||
- Target temperature
|
||||
- Operation mode (HVAC mode)
|
||||
- Fan speed
|
||||
- Horizontal and vertical vane positions
|
||||
|
||||
#### State attributes
|
||||
|
||||
|Attribute|Description|Example|
|
||||
|---------|-----------|-------|
|
||||
|`vane_horizontal` |Current horizontal vane position or mode|`auto`|
|
||||
|`vane_horizontal_positions` |Available horizontal vane positions and modes|`auto, split, swing`|
|
||||
|`vane_vertical` |Current vertical vane position or mode|`auto`|
|
||||
|`vane_vertical_positions` |Available vertical vane positions and modes|`auto, split, swing`|
|
||||
|
||||
#### Controlling vanes
|
||||
|
||||
The horizontal and vertical vane positions can be controlled using the corresponding `melcloud.set_vane_horizontal` and `melcloud.set_vane_vertical` services.
|
||||
|
||||
Swing mode can also be used to control vertical vane position.
|
||||
|
||||
### Sensor
|
||||
|
||||
|
||||
@ -153,6 +153,34 @@ modbus:
|
||||
| address | Address of the Register (e.g., 138) |
|
||||
| value | A single value or an array of 16-bit values. Single value will call modbus function code 6. Array will call modbus function code 16. Array might need reverse ordering. E.g., to set 0x0004 you might need to set `[4,0]` |
|
||||
|
||||
## Log warning (v1.0.8 and onwards)
|
||||
|
||||
Pymodbus (which is the implementation library) was updated and issues a warning:
|
||||
|
||||
- "Not Importing deprecated clients. Dependency Twisted is not Installed"
|
||||
|
||||
This warning can be safely ignored, and have no influence on how the integration
|
||||
works!
|
||||
|
||||
## Opening an issue
|
||||
|
||||
When opening an issue, please add your current configuration (or a scaled down version), with at least:
|
||||
|
||||
- the Modbus configuration lines
|
||||
- the entity (sensor, etc.) lines
|
||||
|
||||
In order for the developers better to identify the problem, please add the
|
||||
following lines to configuration.yaml:
|
||||
|
||||
```yaml
|
||||
logger:
|
||||
logs:
|
||||
homeassistant.components.modbus: debug
|
||||
pymodbus.client: debug
|
||||
```
|
||||
|
||||
and restart Home Assistant, reproduce the problem, and include the log in the issue.
|
||||
|
||||
## Building on top of Modbus
|
||||
|
||||
- [Modbus Binary Sensor](/integrations/binary_sensor.modbus/)
|
||||
|
||||
@ -31,11 +31,6 @@ sensor:
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: Name prefix for defined sensors.
|
||||
required: false
|
||||
default: 'NUT UPS'
|
||||
type: string
|
||||
host:
|
||||
description: The host name or IP address of the device that is running NUT.
|
||||
required: false
|
||||
|
||||
@ -13,61 +13,12 @@ The `nws` platform uses the [National Weather Service](https://www.weather.gov)
|
||||
|
||||
## Configuration
|
||||
|
||||
To add `nws` to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **National Weather Service (NWS)**. Multiple entries can be configured, but a unique set of latitude and longitude must be supplied for each.
|
||||
|
||||
According to the [API documentation](https://www.weather.gov/documentation/services-web-api/), a string is required for the API key, and an email address is suggested to be included within the string.
|
||||
|
||||
To add NWS to your installation using the closest station, add the following to your `configuration.yaml` file:
|
||||
Providing a METAR station code is optional, and if not supplied, the closest station to the latitude and longitude will be chosen. A list of nearby stations is printed to the log with level `DEBUG` if no station is supplied. Stations can also be found on the [NOAA website](https://www.cnrfc.noaa.gov/metar.php). Codes with only three characters, for example, `ADW` should be prefixed with the letter K, `KADW`.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
weather:
|
||||
- platform: nws
|
||||
api_key: YOUR_API_KEY
|
||||
```
|
||||
|
||||
To specify a station, for example, KADW (Andrews Air Force Base), use the following:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
weather:
|
||||
- platform: nws
|
||||
api_key: YOUR_API_KEY
|
||||
station: KADW
|
||||
```
|
||||
|
||||
A list of nearby stations is printed to the log with level `DEBUG` if no station is supplied. Stations can also be found on the [NOAA website](https://www.cnrfc.noaa.gov/metar.php). Codes with only three characters, for example, `ADW` should be prefixed with the letter K, `KADW`.
|
||||
|
||||
The default forecast is day and night, `mode: daynight`, while `mode: hourly` gives the forecast hourly. The forecast is obtained from the latitude and longitude value, not the station.
|
||||
|
||||
{% configuration %}
|
||||
api_key:
|
||||
description: "Your API key. Any string, but an email address is suggested to be included."
|
||||
required: true
|
||||
type: string
|
||||
latitude:
|
||||
description: "Manually specify latitude. By default, the value will be taken from the Home Assistant configuration."
|
||||
required: false
|
||||
type: float
|
||||
default: "Provided by Home Assistant configuration."
|
||||
longitude:
|
||||
description: Manually specify longitude. By default, the value will be taken from the Home Assistant configuration.
|
||||
required: false
|
||||
type: float
|
||||
default: "Provided by Home Assistant configuration."
|
||||
name:
|
||||
description: "Name to use in the frontend."
|
||||
required: false
|
||||
type: string
|
||||
default: "Station name."
|
||||
mode:
|
||||
description: "The forecast type. Can be `daynight` or `hourly`."
|
||||
required: false
|
||||
type: string
|
||||
default: daynight
|
||||
station:
|
||||
description: "METAR station code."
|
||||
required: false
|
||||
type: string
|
||||
default: "Closest station to `latitude` and `longitude` as returned by NWS API."
|
||||
{% endconfiguration %}
|
||||
Two weather entities are created for each entry in the configuration: one for hourly forecasts and one for day and night forecasts. The time supplied for each forecast is the start time for the forecast.
|
||||
|
||||
Details about the API are available in the [NWS API documentation](https://www.weather.gov/documentation/services-web-api). The [pynws](https://github.com/MatthewFlamm/pynws) library is used to retrieve data.
|
||||
|
||||
41
source/_integrations/openerz.markdown
Normal file
41
source/_integrations/openerz.markdown
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: "OpenERZ Sensor"
|
||||
description: "Instructions on how to integrate a OpenERZ API for Zurich city waste disposal with Home Assistant"
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.109
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: openerz
|
||||
---
|
||||
|
||||
This `openerz` sensor platform uses [OpenERZ](http://openerz.metaodi.ch/) API to access data from Entsorgung und Recycling Zürich (ERZ). It reports the next pickup date for the specified zip and waste type.
|
||||
|
||||
## Configuration
|
||||
|
||||
To enable this sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: openerz
|
||||
zip: 8001
|
||||
waste_type: cardboard
|
||||
```
|
||||
|
||||
Available (and tested) waste types are: `paper`, `cardboard`, `waste`, `cargotram`, `etram`, `organic` and `textile`.
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: The name to be used when displaying this sensor.
|
||||
required: false
|
||||
type: string
|
||||
zip:
|
||||
description: Postcode of the pickup location.
|
||||
required: true
|
||||
type: string
|
||||
waste_type:
|
||||
description: Type of waste to be collected.
|
||||
required: true
|
||||
type: string
|
||||
default: waste
|
||||
{% endconfiguration %}
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Panasonic Viera TV
|
||||
description: Instructions on how to integrate a Panasonic Viera TV into Home Assistant.
|
||||
title: Panasonic Viera
|
||||
description: Instructions on how to integrate a Panasonic Viera TV with Home Assistant.
|
||||
ha_category:
|
||||
- Media Player
|
||||
ha_release: 0.17
|
||||
@ -10,7 +10,86 @@ ha_domain: panasonic_viera
|
||||
|
||||
The `panasonic_viera` platform allows you to control a Panasonic Viera TV.
|
||||
|
||||
Currently known supported models:
|
||||
## Configuration
|
||||
|
||||
To configure your Panasonic Viera TV, head to the **Configuration > Integrations** page. Click on the plus (+) button to add a new integration.
|
||||
|
||||
Once the integration is loaded, with your TV turned on and connected to your local network, enter the IP address of your TV and a name of your choice.
|
||||
|
||||
If your TV needs to be paired, you will be prompted to type the PIN code that will be displayed on it.
|
||||
|
||||
## Manual configuration
|
||||
|
||||
If you prefer to use YAML to set up your Panasonic Viera TV, you can still do it. It also allows for some extra settings.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
panasonic_viera:
|
||||
host: YOUR_TV_IP
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The IP address of your Panasonic Viera TV, e.g., `192.168.1.10`.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: The name you would like to give to the TV entity.
|
||||
required: false
|
||||
default: Panasonic Viera TV
|
||||
type: string
|
||||
port:
|
||||
description: The port number of your Panasonic Viera TV.
|
||||
required: false
|
||||
default: 55000
|
||||
type: integer
|
||||
turn_on_action:
|
||||
description: Defines an action to turn the TV on. If not specified, a power key signal will try to be sent to the TV. Be aware that it might not work properly with some models.
|
||||
required: false
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
When you restart Home Assistant, make sure the TV is turned on and connected to your local network. If your TV needs to be paired, you'll need to go to **Configuration > Integrations** to type the PIN code that will be displayed on it and finish the setup.
|
||||
|
||||
### Example `turn_on_action`
|
||||
|
||||
```yaml
|
||||
# Example turn_on_action configuration.yaml entry with Wake-on-LAN
|
||||
panasonic_viera:
|
||||
host: YOUR_TV_IP
|
||||
name: Living Room TV
|
||||
turn_on_action:
|
||||
- service: wake_on_lan.send_magic_packet
|
||||
data:
|
||||
mac: "AA:BB:CC:DD:99:1A"
|
||||
```
|
||||
|
||||
### Example `play_media` script
|
||||
|
||||
The `play_media` function can be used to open web pages and other media types (images, movies) via URLs in the TV web browser.
|
||||
|
||||
```yaml
|
||||
# Example play_media script
|
||||
script:
|
||||
front_door_camera:
|
||||
alias: "Show who's at the door"
|
||||
sequence:
|
||||
- service: media_player.turn_on
|
||||
data:
|
||||
entity_id: media_player.living_room_tv
|
||||
- service: media_player.play_media
|
||||
data:
|
||||
entity_id: media_player.living_room_tv
|
||||
media_content_type: "url"
|
||||
media_content_id: YOUR_URL
|
||||
- delay:
|
||||
seconds: 5
|
||||
- service: media_player.media_stop
|
||||
data:
|
||||
entity_id: media_player.living_room_tv
|
||||
```
|
||||
|
||||
### Currently known supported models
|
||||
|
||||
- TC-P50ST50
|
||||
- TC-P60S60
|
||||
@ -31,74 +110,4 @@ Currently known supported models:
|
||||
- TX-42AS650
|
||||
- TX55ASW654
|
||||
|
||||
If your model is not on the list then give it a test, if everything works correctly then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/panasonic_viera.markdown).
|
||||
|
||||
Some Panasonic Viera TVs allow Home Assistant to turn them on, if you specify the MAC address with `mac:`.
|
||||
|
||||
Note that your TV has to reside in the same network as your Home Assistant instance for this platform to work. If you have multiple network interfaces on your Home Assistant instance, you may need to specify the `broadcast_address`.
|
||||
|
||||
To add a TV to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
media_player:
|
||||
- platform: panasonic_viera
|
||||
host: 192.168.0.10
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The IP of the Panasonic Viera TV, e.g., `192.168.0.10`.
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: The port number of your Panasonic Viera TV.
|
||||
required: false
|
||||
default: 55000
|
||||
type: integer
|
||||
mac:
|
||||
description: The MAC address of your Panasonic Viera TV, e.g., `AA:BB:CC:DD:99:1A`.
|
||||
required: false
|
||||
type: string
|
||||
broadcast_address:
|
||||
description: The broadcast address on which to send the Wake-On-Lan packet.
|
||||
required: false
|
||||
default: 255.255.255.255
|
||||
type: string
|
||||
app_power:
|
||||
description: Set to `true` if your Panasonic Viera TV supports "Turn on via App".
|
||||
required: false
|
||||
default: false
|
||||
type: boolean
|
||||
name:
|
||||
description: The name you would like to give to the Panasonic Viera TV.
|
||||
required: false
|
||||
default: Panasonic Viera TV
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
### Example `play_media` script
|
||||
|
||||
The `play_media` function can be used to open web pages and other media types (images, movies) in the TV web browser.
|
||||
|
||||
```yaml
|
||||
# Example play_media script that can be triggered when someone is detected at the door
|
||||
#
|
||||
script:
|
||||
front_door_camera:
|
||||
alias: "Show who's at the door"
|
||||
sequence:
|
||||
- service: media_player.turn_on
|
||||
data:
|
||||
entity_id: media_player.living_room_tv
|
||||
- service: media_player.play_media
|
||||
data:
|
||||
entity_id: media_player.living_room_tv
|
||||
media_content_type: "url"
|
||||
media_content_id: "http://google.com"
|
||||
- delay:
|
||||
seconds: 5
|
||||
- service: media_player.media_stop
|
||||
data:
|
||||
entity_id: media_player.living_room_tv
|
||||
```
|
||||
If your model is not on the list, give it a test. If everything works correctly, then add it to the list on [GitHub](https://github.com/home-assistant/home-assistant.io/blob/current/source/_integrations/panasonic_viera.markdown).
|
||||
|
||||
135
source/_integrations/pi4ioe5v9xxxx.markdown
Normal file
135
source/_integrations/pi4ioe5v9xxxx.markdown
Normal file
@ -0,0 +1,135 @@
|
||||
---
|
||||
title: "pi4ioe5v9xxxx IO Expander"
|
||||
description: "Instructions on how to integrate the pi4ioe5v9xxxx IO pin expander with I2C interface into Home Assistant."
|
||||
logo: diodes.png
|
||||
ha_category:
|
||||
- DIY
|
||||
- Binary Sensor
|
||||
- Switch
|
||||
ha_release: 0.109
|
||||
ha_iot_class: Local Polling
|
||||
---
|
||||
|
||||
The `pi4ioe5v9xxxx` integration provides support for the quasi-bidirectional devices PI4IOE5V9570, PI4IOE5V9674, PI4IOE5V9673, PI4IOE5V96224 and PI4IOE5V96248 from digital.com.
|
||||
|
||||
For more details about the pi4ioe5v9xxxx I2C I/O port expander you can find the datasheets here:
|
||||
- [PI4IOE5V9570](https://www.diodes.com/assets/Datasheets/PI4IOE5V9570.pdf)
|
||||
- [PI4IOE5V9674](https://www.diodes.com/assets/Datasheets/PI4IOE5V9674.pdf)
|
||||
- [PI4IOE5V9673](https://www.diodes.com/assets/Datasheets/PI4IOE5V9673.pdf)
|
||||
- [PI4IOE5V96224](https://www.diodes.com/assets/Datasheets/PI4IOE5V96224.pdf)
|
||||
- [PI4IOE5V96248](https://www.diodes.com/assets/Datasheets/PI4IOE5V96248.pdf).
|
||||
|
||||
## Binary Sensor
|
||||
|
||||
The `pi4ioe5v9xxxx` binary sensor platform allows you to read sensor values from the I/O pins of your I/O expander.
|
||||
|
||||
The pin numbers are from 1 to X where: 1-8 correspond to port 0 (00-07) and 9-16 to port 1, etc.
|
||||
|
||||
### Configuration
|
||||
|
||||
To use the I/O pins of an pi4ioe5v9xxxx connected to an I2C bus of your Raspberry Pi as binary sensors, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
binary_sensor:
|
||||
- platform: pi4ioe5v9xxxx
|
||||
pins:
|
||||
1: Pin_01/PI0_0
|
||||
2: Pin_02/PI0_1
|
||||
3: Pin_03/PI0_2
|
||||
4: Pin_04/PI0_3
|
||||
5: Pin_05/PI0_4
|
||||
6: Pin_06/PI0_5
|
||||
7: Pin_07/PI0_6
|
||||
8: Pin_08/PI0_7
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
pins:
|
||||
description: List of used pins.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
"pin: name":
|
||||
description: The pin numbers (from 1 to X) and corresponding names.
|
||||
required: true
|
||||
type: [integer, string]
|
||||
i2c_bus:
|
||||
description: i2c bus containing the pi4ioe5v9xxxx chip.
|
||||
required: false
|
||||
type: integer
|
||||
default: "`1`"
|
||||
i2c_address:
|
||||
description: i2c address of pi4ioe5v9xxxx chip.
|
||||
required: false
|
||||
type: integer
|
||||
default: "`0x20`"
|
||||
bits:
|
||||
description: number of bits of pi4ioe5v9xxxx chip, see particular datasheet for your device for the right number.
|
||||
required: false
|
||||
type: integer
|
||||
default: "`24`"
|
||||
invert_logic:
|
||||
description: If `true`, inverts the input logic to ACTIVE LOW.
|
||||
required: false
|
||||
type: boolean
|
||||
default: "`false` (ACTIVE HIGH)"
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
## Switch
|
||||
|
||||
The `pi4ioe5v9xxxx` switch platform allows you to write to the I/O pins of your I2C I/O expander.
|
||||
|
||||
The pin numbers are from 1 to X, where 1-8 correspond to port A (A1-A8) and 9-16 to port B (B1-B8), etc.
|
||||
|
||||
### Configuration
|
||||
|
||||
To use the I/O pins of an pi4ioe5v9xxxx connected to an I2C bus as switches, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
switch:
|
||||
- platform: pi4ioe5v9xxxx
|
||||
pins:
|
||||
1: Pin_01/PI0_0
|
||||
2: Pin_02/PI0_1
|
||||
3: Pin_03/PI0_2
|
||||
4: Pin_04/PI0_3
|
||||
5: Pin_05/PI0_4
|
||||
6: Pin_06/PI0_5
|
||||
7: Pin_07/PI0_6
|
||||
8: Pin_08/PI0_7
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
pins:
|
||||
description: List of used pins.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
"pin: name":
|
||||
description: The pin numbers (from 1 to X) and corresponding names.
|
||||
required: true
|
||||
type: [integer, string]
|
||||
i2c_bus:
|
||||
description: i2c bus containing the pi4ioe5v9xxxx chip.
|
||||
required: false
|
||||
type: integer
|
||||
default: "`1`"
|
||||
i2c_address:
|
||||
description: i2c address of pi4ioe5v9xxxx chip.
|
||||
required: false
|
||||
type: integer
|
||||
default: "`0x20`"
|
||||
bits:
|
||||
description: number of bits of pi4ioe5v9xxxx chip, see particular datasheet for your device for the right number.
|
||||
required: false
|
||||
type: integer
|
||||
default: "`24`"
|
||||
invert_logic:
|
||||
description: If `true`, inverts the output logic to ACTIVE LOW.
|
||||
required: false
|
||||
type: boolean
|
||||
default: "`false` (ACTIVE HIGH)"
|
||||
{% endconfiguration %}
|
||||
@ -1,58 +0,0 @@
|
||||
---
|
||||
title: Pushetta
|
||||
description: Instructions on how to add Pushetta notifications to Home Assistant.
|
||||
ha_category:
|
||||
- Notifications
|
||||
ha_release: pre 0.7
|
||||
ha_domain: pushetta
|
||||
---
|
||||
|
||||
The `pushetta` notify platform uses [Pushetta](http://www.pushetta.com) to delivery notifications from Home Assistant to your devices.
|
||||
|
||||
To retrieve the API token, log into your account at [http://www.pushetta.com](http://www.pushetta.com) and go to your **Dashboard**. Create a new channel by clicking on **Channels** and then **Add a Channel**.
|
||||
|
||||
To enable Pushetta notifications in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
notify:
|
||||
- name: NOTIFIER_NAME
|
||||
platform: pushetta
|
||||
api_key: YOUR_API_KEY
|
||||
channel_name: YOUR_CHANNEL_NAME
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: Setting the optional parameter `name` allows multiple notifiers to be created. The notifier will bind to the service `notify.NOTIFIER_NAME`.
|
||||
required: false
|
||||
default: notify
|
||||
type: string
|
||||
api_key:
|
||||
description: Your API key for Pushetta.
|
||||
required: true
|
||||
type: string
|
||||
channel_name:
|
||||
description: The name of your channel.
|
||||
required: true
|
||||
type: string
|
||||
send_test_msg:
|
||||
description: Disable/enable the test message send on Home Assistant's startup to test the API key and the existence of the channel.
|
||||
required: false
|
||||
default: false
|
||||
type: boolean
|
||||
{% endconfiguration %}
|
||||
|
||||
It's easy to test your Pushetta setup outside of Home Assistant. Assuming you have a channel `home-assistant`, just fire a request and check the channel page in the dashboard for a new message.
|
||||
|
||||
```bash
|
||||
curl -X POST \
|
||||
-H "Authorization: Token YOUR_API_KEY" \
|
||||
-H "Content-Type: application/json" \
|
||||
-d "{ \"body\" : \"Hello World\", \"message_type\" : \"text/plain\" }" \
|
||||
http://api.pushetta.com/api/pushes/home-assistant/
|
||||
```
|
||||
|
||||
For further details, please check the [API](http://www.pushetta.com/pushetta-api/).
|
||||
|
||||
To use notifications, please see the [getting started with automation page](/getting-started/automation/).
|
||||
@ -45,6 +45,7 @@ password:
|
||||
port:
|
||||
description: The port where QVR accepts connections.
|
||||
required: false
|
||||
default: 8080
|
||||
type: integer
|
||||
exclude_channels:
|
||||
description: Comma separated list of channel numbers to be excluded.
|
||||
|
||||
@ -46,10 +46,6 @@ api_key:
|
||||
description: The API key for the Rachio account.
|
||||
required: true
|
||||
type: string
|
||||
hass_url_override:
|
||||
description: If your instance is unaware of its actual web location (`base_url`).
|
||||
required: false
|
||||
type: string
|
||||
manual_run_mins:
|
||||
description: For how long, in minutes, to turn on a station when the switch is enabled.
|
||||
required: false
|
||||
@ -78,9 +74,9 @@ panel_iframe:
|
||||
|
||||
## Switch
|
||||
|
||||
The `rachio` switch platform allows you to toggle zones connected to your [Rachio irrigation system](https://rachio.com/) on and off.
|
||||
The `rachio` switch platform allows you to toggle zones and schedules connected to your [Rachio irrigation system](https://rachio.com/) on and off.
|
||||
|
||||
Once configured, a switch will be added for every zone that is enabled on every controller in the account provided, as well as a switch to toggle each controller's standby mode.
|
||||
Once configured, a switch will be added for every zone that is enabled on every controller in the account provided, a switch to start or stop every schedule on a controller, as well as a switch to toggle each controller's standby mode.
|
||||
|
||||
## Examples
|
||||
|
||||
@ -97,6 +93,7 @@ irrigation:
|
||||
- group.zones_front
|
||||
- group.zones_back
|
||||
- switch.side_yard
|
||||
- switch.every_day_6am
|
||||
|
||||
zones_front:
|
||||
name: Front Yard
|
||||
|
||||
@ -47,16 +47,16 @@ recorder:
|
||||
required: false
|
||||
default: 3
|
||||
type: integer
|
||||
auto_purge:
|
||||
description: Automatically purge the database every night at 04:12 local time. Purging keeps the database from growing indefinitely, which takes up disk space and can make Home Assistant slow. If you disable `auto_purge` it is recommended that you create an automation to call the [`recorder.purge`](#service-purge) periodically.
|
||||
required: false
|
||||
default: true
|
||||
type: boolean
|
||||
purge_keep_days:
|
||||
description: Specify the number of history days to keep in recorder database after a purge.
|
||||
required: false
|
||||
default: 10
|
||||
type: integer
|
||||
purge_interval:
|
||||
description: How often (in days) the purge task runs. If a scheduled purge is missed (e.g., if Home Assistant was not running), the schedule will resume soon after Home Assistant restarts. You can use the [service](#service-purge) call `purge` when required without impacting the purge schedule. If this is set to `0` (zero), automatic purging is disabled.
|
||||
required: false
|
||||
default: 1
|
||||
type: integer
|
||||
commit_interval:
|
||||
description: How often (in seconds) the events and state changes are committed to the database. The default of `1` allows events to be committed almost right away without trashing the disk when an event storm happens. Increasing this will reduce disk I/O and may prolong disk (SD card) lifetime with the trade-off being that the logbook and history will lag. If this is set to `0` (zero), commit are made as soon as possible after an event is processed.
|
||||
required: false
|
||||
@ -94,7 +94,7 @@ recorder:
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
Defining domains and entities to `exclude` (aka. blacklist) is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains. Usually, these are entities/domains that do not change or rarely change (like `updater` or `automation`).
|
||||
Defining domains and entities to `exclude` (i.e. blacklist) is convenient when you are basically happy with the information recorded, but just want to remove some entities or domains.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with exclude
|
||||
@ -113,7 +113,7 @@ recorder:
|
||||
- call_service # Don't record service calls
|
||||
```
|
||||
|
||||
define domains and entities to record by using the `include` configuration (aka. whitelist) is convenient if you have a lot of entities in your system and your `exclude` lists possibly get very large, so it might be better just to define the entities or domains to record.
|
||||
Defining domains and entities to record by using the `include` configuration (i.e. whitelist) is convenient if you have a lot of entities in your system and your `exclude` lists possibly get very large, so it might be better just to define the entities or domains to record.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with include
|
||||
@ -146,11 +146,12 @@ If you only want to hide events from your history, take a look at the [`history`
|
||||
### Service `purge`
|
||||
|
||||
Call the service `recorder.purge` to start a purge task which deletes events and states older than x days, according to `keep_days` service data.
|
||||
Note that purging will not immediately decrease disk space usage but it will significantly slow down further growth.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `keep_days` | yes | The number of history days to keep in recorder database (defaults to the integration `purge_keep_days` configuration) |
|
||||
| `repack` | yes | Rewrite the entire database, possibly saving some disk space. Only supported for SQLite and requires at least as much disk space free as the database currently uses. |
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `keep_days` | yes | The number of history days to keep in recorder database (defaults to the integration `purge_keep_days` configuration) |
|
||||
| `repack` | yes | Rewrite the entire database, possibly saving some disk space. This is a heavy operation that can cause slowdowns and increased disk space usage while it runs. Only supported for SQLite and PostgreSQL. |
|
||||
|
||||
## Custom database engines
|
||||
|
||||
|
||||
@ -116,3 +116,14 @@ action:
|
||||
source: 20197
|
||||
service: media_player.select_source
|
||||
```
|
||||
|
||||
It is also possible to tune directly to specific channels if you have a Roku TV and use an OTA antenna. This service only supports `media_channel_type` of 'channel'. `media_content_id` corresponds to the TV channel, which you should see when navigating to these on your TV UI.
|
||||
|
||||
```yaml
|
||||
action:
|
||||
- data:
|
||||
entity_id: media_player.roku
|
||||
media_content_id: 5.1
|
||||
media_content_type: channel
|
||||
service: media_player.play_media
|
||||
```
|
||||
|
||||
@ -1,34 +1,39 @@
|
||||
---
|
||||
title: iRobot Roomba
|
||||
description: Instructions on how to integrate your Wi-Fi enabled Roomba within Home Assistant.
|
||||
description: Instructions on how to integrate your Wi-Fi enabled Roomba and Braava within Home Assistant.
|
||||
ha_category:
|
||||
- Vacuum
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.51
|
||||
ha_conflig_flow: true
|
||||
ha_codeowners:
|
||||
- '@pschmitt'
|
||||
- '@cyr-ius'
|
||||
- '@shenxn'
|
||||
ha_domain: roomba
|
||||
---
|
||||
|
||||
The `roomba` integration allows you to control your [iRobot Roomba](https://www.irobot.com/For-the-Home/Vacuuming/Roomba.aspx) vacuum.
|
||||
The `roomba` integration allows you to control your [iRobot Roomba](https://www.irobot.com/roomba) vacuum or [iRobot Braava](https://www.irobot.com/braava) m-series mop.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/more-info-dialog-roomba.png' />
|
||||
</p>
|
||||
|
||||
<div class='note'>
|
||||
This platform has been tested and is confirmed to be working with the iRobot Roomba 980 and 890 models, but should also work fine with any Wi-Fi enabled Roomba like the 690 or the 960.
|
||||
This platform has been tested and is confirmed to be working with the iRobot Roomba s9+, Roomba 980, Roomba 890, and Braava jet m6 models, but should also work fine with any Wi-Fi enabled Roomba or Braava like the 690 or the 960.
|
||||
</div>
|
||||
|
||||
## Configuration
|
||||
|
||||
To add your Roomba to your installation, go to **Configuration** >> **Integrations** in the UI, click the button with + sign and from the list of integrations select iRobot Roomba.
|
||||
|
||||
To add your Roomba vacuum to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
vacuum:
|
||||
- platform: roomba
|
||||
host: IP_ADDRESS_OR_HOSTNAME
|
||||
username: BLID
|
||||
roomba:
|
||||
- host: IP_ADDRESS_OR_HOSTNAME
|
||||
blid: BLID
|
||||
password: PASSWORD
|
||||
```
|
||||
|
||||
@ -37,7 +42,7 @@ host:
|
||||
description: The hostname or IP address of the Roomba.
|
||||
required: true
|
||||
type: string
|
||||
username:
|
||||
blid:
|
||||
description: The username (BLID) for your device.
|
||||
required: true
|
||||
type: string
|
||||
@ -45,11 +50,6 @@ password:
|
||||
description: The password for your device.
|
||||
required: true
|
||||
type: string
|
||||
name:
|
||||
description: The name of the vacuum.
|
||||
required: false
|
||||
type: string
|
||||
default: Roomba
|
||||
certificate:
|
||||
description: Path to your certificate store.
|
||||
required: false
|
||||
@ -73,6 +73,29 @@ The Roomba's MQTT server only allows a single connection. Enabling continuous mo
|
||||
|
||||
</div>
|
||||
|
||||
## Integration Entities
|
||||
|
||||
The Roomba Integration will add the following sensors.
|
||||
|
||||
Sensors:
|
||||
- roomba_battery_level : The status of your battery
|
||||
- roomba_bin_full (if Roomba has the capacity to do) : Bin Full status
|
||||
|
||||
### Multiple Roomba vacuums
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
roomba:
|
||||
- host: IP_ADDRESS_OR_HOSTNAME_1
|
||||
blid: BLID_1
|
||||
password: PASSWORD_1
|
||||
- host: IP_ADDRESS_OR_HOSTNAME_2
|
||||
blid: BLID_2
|
||||
password: PASSWORD_2
|
||||
continuous: false
|
||||
delay: 5
|
||||
```
|
||||
|
||||
### Retrieving your credentials
|
||||
|
||||
Please refer to [here](https://github.com/NickWaterton/Roomba980-Python#how-to-get-your-usernameblid-and-password) or [here](https://github.com/koalazak/dorita980#how-to-get-your-usernameblid-and-password) to retrieve both the BLID (username) and the password.
|
||||
|
||||
@ -95,6 +95,33 @@ automation:
|
||||
source: HDMI 1
|
||||
```
|
||||
|
||||
## Using scene transitions
|
||||
|
||||
Both the `scene.apply` and `scene.turn_on` services support setting a transition,
|
||||
which enables you to smoothen the transition to the scene.
|
||||
|
||||
This is an example of an automation that sets a romantic scene, in which the
|
||||
light will transition to the scene in 2.5 seconds.
|
||||
|
||||
```yaml
|
||||
# Example automation
|
||||
automation:
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: device_tracker.sweetheart
|
||||
from: "not_home"
|
||||
to: "home"
|
||||
action:
|
||||
service: scene.turn_on
|
||||
data:
|
||||
entity_id: scene.romantic
|
||||
transition: 2.5
|
||||
```
|
||||
|
||||
Transitions are currently only support by lights, which in their turn, have
|
||||
to support it as well. However, the scene itself does not have to consist of
|
||||
only lights to have a transition set.
|
||||
|
||||
## Reloading scenes
|
||||
|
||||
Whenever you make a change to your scene configuration, you can call the `scene.reload` service to reload the scenes.
|
||||
|
||||
@ -36,4 +36,9 @@ scan_interval:
|
||||
required: false
|
||||
default: 30 seconds
|
||||
type: integer
|
||||
invert_position:
|
||||
description: Invert position percentage.
|
||||
required: false
|
||||
default: false
|
||||
type: boolean
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Smartthings
|
||||
description: Instructions on setting up Samsung SmartThings within Home Assistant.
|
||||
title: SmartThings
|
||||
description: Instructions on setting up SmartThings within Home Assistant.
|
||||
featured: true
|
||||
ha_category:
|
||||
- Hub
|
||||
@ -21,74 +21,63 @@ ha_codeowners:
|
||||
ha_domain: smartthings
|
||||
---
|
||||
|
||||
Samsung SmartThings is integrated into Home Assistant through the SmartThings Cloud API. The SmartThings integration is the main integration to integrate all SmartThings related platforms. The basic features of this integration include:
|
||||
SmartThings is integrated into Home Assistant through the SmartThings Cloud API. The features of this integration include:
|
||||
|
||||
1. Controlling SmartThings devices with pushed state updates from SmartThings.
|
||||
2. Entities automatically added, removed, or updated when changed in SmartThings (upon Home Assistant restart).
|
||||
3. Support for multiple SmartThings accounts and locations, each represented as a unique integration in the front-end configuration.
|
||||
4. No brokers, bridges, or additional dependencies.
|
||||
1. Controlling SmartThings devices as Home Assistant entities ([see platforms for supported devices and capabilities](#platforms)).
|
||||
1. Entities automatically synchronized upon restart of Home Assistant when changed in SmartThings.
|
||||
1. Support for multiple SmartThings accounts and locations with each represented as an integration instance in Home Assistant.
|
||||
1. No brokers, bridges, or additional dependencies.
|
||||
|
||||
See it in action, with a step-by-step setup guide, thanks to a fan! (v0.87 featured):
|
||||
## Prerequisites
|
||||
|
||||
<div class='videoWrapper'>
|
||||
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/QZHlhQ7fqrA" frameborder="0" allowfullscreen></iframe>
|
||||
</div>
|
||||
1. A SmartThings [personal access token](https://account.smartthings.com/tokens).
|
||||
1. An internet accessible incoming webhook or active Home Assistant Cloud subscription.
|
||||
|
||||
## Basic requirements
|
||||
### Personal Access Token (PAT)
|
||||
|
||||
The SmartThings integration utilizes a webhook to receive push updates from the SmartThings cloud through either a cloudhook or an internet accessible webhook based on whether Home Assistant Cloud is configured and logged in with a non-expired subscription (this is not configurable at this time).
|
||||
|
||||
### Cloudhook via Nabu Casa
|
||||
|
||||
If you are using Home Assistant Cloud (Nabu Casa) the integration will create a cloudhook automatically. This greatly simplifies the basic requirements and does not require Home Assistant to be exposed to the internet. **If you have previously setup the integration prior to meeting the requirements for a cloudhook or prior to v0.90.0, you must remove all prior integrations and run through the configuration again.**
|
||||
|
||||
1. A [personal access token](https://account.smartthings.com/tokens) tied to a Samsung or SmartThings account (see below for instructions).
|
||||
2. Home Assistant Cloud is configured and logged-in with a non-expired subscription.
|
||||
|
||||
### Webhook
|
||||
|
||||
1. A [personal access token](https://account.smartthings.com/tokens) tied to a Samsung or SmartThings account (see below for instructions).
|
||||
2. Home Assistant setup for [remote access](/docs/configuration/remote/) via a domain name secured with SSL. *Self-signed SSL certificates are not supported by the SmartThings Cloud API.*
|
||||
3. [`base_url` of the HTTP integration](/integrations/http#base_url) set the URL that Home Assistant is available on the internet. SmartThings requires the `base_url` and Home Assistant to use the standard HTTPS port (443).
|
||||
|
||||
## Setup instructions
|
||||
|
||||
### Create personal access token
|
||||
The PAT is used to create a Home Assistant SmartApp in your SmartThings account during setup of the integration.
|
||||
|
||||
1. Log into the [personal access tokens page](https://account.smartthings.com/tokens) and click '[Generate new token](https://account.smartthings.com/tokens/new)'
|
||||
2. Enter a token name (can be whatever you want), for example, 'Home Assistant' and select the following authorized scopes:
|
||||
1. Enter a token name (can be whatever you want), for example, 'Home Assistant' and select the following authorized scopes:
|
||||
- Devices (all)
|
||||
- Installed Apps (all)
|
||||
- Locations (all)
|
||||
- Apps (all)
|
||||
- Schedules (all)
|
||||
- Scenes (all)
|
||||
3. Click 'Generate token'. When the token is displayed, copy and save it somewhere safe (such as your keystore) as you will not be able to retrieve it again.
|
||||
1. Click 'Generate token'. When the token is displayed copy and save it somewhere safe (such as your keystore) as you will not be able to retrieve it again.
|
||||
|
||||
### Configure Home Assistant
|
||||
### Webhook
|
||||
|
||||
This integration requires an internet accessible incoming webhook to receive push updates from SmartThings. The preferred approach is to subscribe to [Home Assistant Cloud (Nabu Casa)](https://www.nabucasa.com/) and the integration will configure and use a cloudhook automatically. Alternatively, you will have to configure and setup a internet accessible webhook in Home Assistant as described below:
|
||||
|
||||
1. Setup [remote access](/docs/configuration/remote/) via a domain name secured with SSL. *Self-signed SSL certificates are not supported by the SmartThings Cloud API.*
|
||||
1. Set [`base_url` of the HTTP integration](/integrations/http#base_url) to the URL that Home Assistant is available on the internet (this must start with `https://`).
|
||||
|
||||
## Setup instructions
|
||||
|
||||
After completing the prerequisite steps above you are ready to setup the integration! See [troubleshooting](#troubleshooting) if you are having issues setting up the integration.
|
||||
|
||||
1. From Home Assistant, navigate to 'Configuration' then 'Integrations'. Click the plus icon and type/select 'SmartThings'.
|
||||
1. Confirm the callback URL is correct. If using Home Assistant Cloud it will start with `https://hooks.nabuca.casa`. If the URL is not correct, update your Home Assistant configuration, restart, and try again.
|
||||
1. Enter your Personal Access Token.
|
||||
1. Select the SmartThings Location to add to Home Assistant.
|
||||
1. On the window that opens:
|
||||
1. Login with your SmartThings account (if not already logged in).
|
||||
1. Optionally change the display name and click 'Done' on the upper right of the screen.
|
||||
1. Authorize the integration by clicking 'Allow' on the bottom right of the screen.
|
||||
1. Click 'Close Window' or close it manually if necessary.
|
||||
1. Back in Home Assistant click 'Finish'.
|
||||
|
||||
<div class='note info'>
|
||||
|
||||
The SmartThings integration is configured exclusively through the front-end. Manual setup through `configuration.yaml` is not available at this time.
|
||||
If you want to integrate additional SmartThings accounts or locations, repeat the steps above.
|
||||
|
||||
</div>
|
||||
|
||||
1. From the Home Assistant front-end, navigate to 'Configuration' then 'Integrations'. Under 'Set up a new integration' locate 'SmartThings' and click 'Configure'.
|
||||
2. Enter the personal access token created above and click 'Submit'
|
||||
3. When prompted, install the SmartApp:
|
||||
1. Open the SmartThings Classic mobile app. Navigate to 'Automation' and select the 'SmartApps' tab.
|
||||
2. Click 'Add a SmartApp', scroll to the bottom, and select 'My Apps', then choose 'Home Assistant'.
|
||||
3. Optionally change the display name and press 'Done'
|
||||
4. Authorize the app by pressing 'Allow'
|
||||
4. Return to Home Assistant and click 'Submit'.
|
||||
## Removal instructions
|
||||
|
||||
<div class='note info'>
|
||||
|
||||
Advanced: If you have multiple locations in SmartThings, each can be integrated into Home Assistant. Follow the steps above, then for each subsequent location, install the SmartApp and it will automatically add to Home Assistant. This can be completed during step 3 (install SmartApp) above or at any time after that.
|
||||
|
||||
</div>
|
||||
|
||||
See the [troubleshooting](#troubleshooting) if you are having issues setting up the integration.
|
||||
To remove the integration from Home Assistant, select the instance from the Home Assistant Integrations page and click the trash icon on the upper right corner. Alternatively, you can remove the SmartApp from the location within the SmartThings application. If the Home Assistant instance that setup the integration is no longer running or functioning, you will need to use this [utility to remove the orphaned SmartApps in your SmartThings account](https://pypi.org/project/hass-smartthings-remove/).
|
||||
|
||||
## Events
|
||||
|
||||
@ -291,12 +280,31 @@ The SmartThings Switch platform lets you control devices that have the [`switch`
|
||||
|
||||
### Setup
|
||||
|
||||
Perform the following steps if you receive one of the following error messages while attempting to setup the integration (this does not apply when integrated through Home Assistant Cloud):
|
||||
#### Aborted: Home Assistant is not configured correctly to receive updates from SmartThings
|
||||
|
||||
- "SmartThings could not validate the endpoint configured in base_url. Please review the integration requirements."
|
||||
- "Unable to setup the SmartApp. Please try again."
|
||||
This error message occurs when you do not have an active Home Assistant Cloud (Nabu Casa) subscription and the `base_url` is not configured correctly (it must start with `https`). Update your Home Assistant configuration per the prerequisites above, restart, and try again.
|
||||
|
||||
#### Checklist
|
||||
#### Error: The token must be in the UID/GUID format
|
||||
|
||||
The personal access token does not match the expected format. Make sure you are copying the entire token and that there are no extraneous characters (such as trailing whitespace) and try again.
|
||||
|
||||
#### Error: The token is invalid or no longer authorized
|
||||
|
||||
The personal access token entered is not valid or has been deleted. Create a new token per the instructions in the prerequisites and try again.
|
||||
|
||||
#### Error: The token does not have the required OAuth scopes
|
||||
|
||||
The personal access token entered is valid but does not have the required scopes as outlined in the prerequisites. Create a new token per the instructions in the prerequisites and try again.
|
||||
|
||||
#### Error: SmartThings could not validate the webhook URL
|
||||
|
||||
SmartThings was unable to reach your Home Assistant instance using the webhook URL. Enable debug logging to see the specific issue and follow the webhook troubleshooting checklist below.
|
||||
|
||||
#### Aborted: There are no available SmartThings Locations
|
||||
|
||||
This error message occurs when all of the SmartThings locations under the account linked to the personal access token are already setup in Home Assistant. Ensure you are using the correct personal access token or create an additional location in SmartThings to integrate and try again.
|
||||
|
||||
#### Webhook Troubleshooting Checklist
|
||||
|
||||
1. Ensure `base_url` is properly set to the _external address_ that Home Assistant is available to the internet. SmartThings must be able to reach this address.
|
||||
1. Validate there are no problems with your certificate or SSL configuration by using an online checker, such as [https://www.digicert.com/help/](https://www.digicert.com/help/).
|
||||
|
||||
@ -67,3 +67,12 @@ Remove one or more speakers from their group of speakers.
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | no | String or list of `entity_id`s to separate from their coordinator speaker.
|
||||
|
||||
### Service `snapcast.set_latency`
|
||||
|
||||
Set the latency of a speaker.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `entity_id` | yes | String or list of `entity_id`s for which latency will be adjusted.
|
||||
| `latency` | yes | Latency in ms.
|
||||
|
||||
118
source/_integrations/synology_dsm.markdown
Normal file
118
source/_integrations/synology_dsm.markdown
Normal file
@ -0,0 +1,118 @@
|
||||
---
|
||||
title: Synology DSM
|
||||
description: Instructions on how to integrate the Synology DSM sensor within Home Assistant.
|
||||
ha_category:
|
||||
- System Monitor
|
||||
ha_release: 0.32
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: synology_dsm
|
||||
---
|
||||
|
||||
The `synology_dsm` sensor platform allows getting various statistics from your [Synology NAS](https://www.synology.com).
|
||||
|
||||
## Configuration
|
||||
|
||||
There are two ways to integrate Synology DSM in Home Assistant.
|
||||
|
||||
### Via the frontend
|
||||
|
||||
Menu: *Configuration* -> *Integrations*. Search for "Synology DSM", fill the configuration form, click submit.
|
||||
|
||||
### Via the configuration file
|
||||
|
||||
Add the following section to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
synology_dsm:
|
||||
- host: IP_ADDRESS_OR_DNS_OF_SYNOLOGY_NAS
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: The IP address or DNS of the Synology NAS to monitor.
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: The port number on which the Synology NAS is reachable.
|
||||
required: false
|
||||
default: 5001 if `ssl` is true, 5000 if `ssl` is false
|
||||
type: integer
|
||||
ssl:
|
||||
description: Determine if HTTPS should be used.
|
||||
required: false
|
||||
default: true
|
||||
type: boolean
|
||||
username:
|
||||
description: An user to connect to the Synology NAS (a separate account is advised, see the (Separate User Configuration)[#separate-user-configuration] section below for details).
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: The password of the user to connect to the Synology NAS.
|
||||
required: true
|
||||
type: string
|
||||
volumes:
|
||||
description: "Array of volumes to monitor. Defaults to all volumes. Replace any spaces in the volume name with underscores, e.g., `volume 1` with `volume_1`."
|
||||
required: false
|
||||
type: list
|
||||
disks:
|
||||
description: "Array of disks to monitor. Defaults to all disks. Use only disk names like `sda`, `sdb`, etc."
|
||||
required: false
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
This sensor will wake up your Synology NAS if it's in hibernation mode.
|
||||
|
||||
</div>
|
||||
|
||||
## Separate User Configuration
|
||||
|
||||
Due to the nature of the Synology DSM API, it is required to grant the user admin rights. This is related to the fact that utilization information is stored in the core module.
|
||||
|
||||
When creating the user, it is possible to deny access to all locations and applications. By doing this, the user will not be able to login to the web interface or view any of the files on the Synology NAS. It is still able to read the utilization and storage information using the API.
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
Using two-factor authentication is not supported. Please use a strong, randomly generated password.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
## Created sensors
|
||||
|
||||
Sensors are :
|
||||
- `cpu_other_load`: Displays unspecified load in percentage.
|
||||
- `cpu_user_load`: Displays user load in percentage.
|
||||
- `cpu_system_load`: Displays system load in percentage.
|
||||
- `cpu_total_load`: Displays combined load in percentage.
|
||||
- `cpu_1min_load`: Displays maximum load in past minute.
|
||||
- `cpu_5min_load`: Displays maximum load in past 5 minutes.
|
||||
- `cpu_15min_load`: Displays maximum load in past 15 minutes.
|
||||
- `memory_real_usage`: Displays percentage of memory used.
|
||||
- `memory_size`: Displays total size of memory in MB.
|
||||
- `memory_cached`: Displays total size of cache in MB.
|
||||
- `memory_available_swap`: Displays total size of available swap in MB.
|
||||
- `memory_available_real`: Displays total size of memory used (based on real memory) in MB.
|
||||
- `memory_total_swap`: Displays total size of actual memory in MB.
|
||||
- `memory_total_real`: Displays total size of real memory in MB.
|
||||
- `network_up`: Displays total up speed of network interfaces (combines all interfaces).
|
||||
- `network_down`: Displays total down speed of network interfaces (combines all interfaces).
|
||||
- `disk_name`: Displays the name of the hard disk (creates a new entry for each disk).
|
||||
- `disk_device`: Displays the path of the hard disk (creates a new entry for each disk).
|
||||
- `disk_smart_status`: Displays the S.M.A.R.T status of the hard disk (creates a new entry for each disk).
|
||||
- `disk_status`: Displays the status of the hard disk (creates a new entry for each disk).
|
||||
- `disk_exceed_bad_sector_thr`: Displays true / false to indicate if the hard disk exceeded the maximum bad sector threshold (creates a new entry for each disk). (Does not work with DSM 5.x)
|
||||
- `disk_below_remain_life_thr`: Displays true / false to indicate if the hard disk dropped below the remain life threshold (creates a new entry for each disk). (Does not work with DSM 5.x)
|
||||
- `disk_temp`: Displays the temperature of the hard disk (creates a new entry for each disk, uses the unit_system to display in C or F).
|
||||
- `volume_status`: Displays the status of the volume (creates a new entry for each volume).
|
||||
- `volume_device_type`: Displays the volume type (RAID, etc) (creates a new entry for each volume).
|
||||
- `volume_size_total`: Displays the total size of the volume in GB's (creates a new entry for each volume).
|
||||
- `volume_size_used`: Displays the used space on this volume in GB's (creates a new entry for each volume).
|
||||
- `volume_percentage_used`: Displays the percentage used for this volume in GB's (creates a new entry for each volume).
|
||||
- `volume_disk_temp_avg`: Displays the average temperature of all disks in the volume (creates a new entry for each volume).
|
||||
- `volume_disk_temp_max`: Displays the maximum temperature of all disks in the volume (creates a new entry for each volume).
|
||||
@ -1,152 +0,0 @@
|
||||
---
|
||||
title: SynologyDSM
|
||||
description: Instructions on how to integrate the SynologyDSM sensor within Home Assistant.
|
||||
ha_category:
|
||||
- System Monitor
|
||||
ha_release: 0.32
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: synologydsm
|
||||
---
|
||||
|
||||
The `synologydsm` sensor platform allows getting various statistics from your [Synology NAS](https://www.synology.com).
|
||||
|
||||
## Configuration
|
||||
|
||||
To use the `synologydsm` sensor in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: synologydsm
|
||||
host: IP_ADDRESS_OF_SYNOLOGY_NAS
|
||||
username: YOUR_USERNAME
|
||||
password: YOUR_PASSWORD
|
||||
monitored_conditions:
|
||||
- cpu_total_load
|
||||
- memory_real_usage
|
||||
- network_up
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: The name to use in the frontend for your Synology device.
|
||||
required: false
|
||||
default: Synology DSM
|
||||
type: string
|
||||
host:
|
||||
description: The IP address of the Synology NAS to monitor.
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
description: The port number on which the Synology NAS is reachable.
|
||||
required: false
|
||||
default: 5001
|
||||
type: integer
|
||||
username:
|
||||
description: An user to connect to the Synology NAS (a separate account is advised, see the Separate User Configuration section below for details).
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
description: The password of the user to connect to the Synology NAS.
|
||||
required: true
|
||||
type: string
|
||||
api_version:
|
||||
description: Define DSM version to allow backward compatibility with 5.x. Value can be `5` for DSM 5.x or `6` for DSM 6.x or later.
|
||||
type: integer
|
||||
required: false
|
||||
ssl:
|
||||
description: Determine if HTTPS should be used.
|
||||
required: false
|
||||
default: true
|
||||
type: boolean
|
||||
volumes:
|
||||
description: "Array of volumes to monitor. Defaults to all volumes. Replace any spaces in the volume name with underscores, e.g., `volume 1` with `volume_1`."
|
||||
required: false
|
||||
type: list
|
||||
disks:
|
||||
description: "Array of disks to monitor. Defaults to all disks. Use only disk names like `sda`, `sdb`, etc."
|
||||
required: false
|
||||
type: list
|
||||
monitored_conditions:
|
||||
description: Defines a [template](/topics/templating/) to extract a value from the payload.
|
||||
required: true
|
||||
type: list
|
||||
keys:
|
||||
cpu_other_load:
|
||||
description: Displays unspecified load in percentage.
|
||||
cpu_user_load:
|
||||
description: Displays user load in percentage.
|
||||
cpu_system_load:
|
||||
description: Displays system load in percentage.
|
||||
cpu_total_load:
|
||||
description: Displays combined load in percentage.
|
||||
cpu_1min_load:
|
||||
description: Displays maximum load in past minute.
|
||||
cpu_5min_load:
|
||||
description: Displays maximum load in past 5 minutes.
|
||||
cpu_15min_load:
|
||||
description: Displays maximum load in past 15 minutes.
|
||||
memory_real_usage:
|
||||
description: Displays percentage of memory used.
|
||||
memory_size:
|
||||
description: Displays total size of memory in MB.
|
||||
memory_cached:
|
||||
description: Displays total size of cache in MB.
|
||||
memory_available_swap:
|
||||
description: Displays total size of available swap in MB.
|
||||
memory_available_real:
|
||||
description: Displays total size of memory used (based on real memory) in MB.
|
||||
memory_total_swap:
|
||||
description: Displays total size of actual memory in MB.
|
||||
memory_total_real:
|
||||
description: Displays total size of real memory in MB.
|
||||
network_up:
|
||||
description: Displays total up speed of network interfaces (combines all interfaces).
|
||||
network_down:
|
||||
description: Displays total down speed of network interfaces (combines all interfaces).
|
||||
disk_name:
|
||||
description: Displays the name of the hard disk (creates a new entry for each disk).
|
||||
disk_device:
|
||||
description: Displays the path of the hard disk (creates a new entry for each disk).
|
||||
disk_smart_status:
|
||||
description: Displays the S.M.A.R.T status of the hard disk (creates a new entry for each disk).
|
||||
disk_status:
|
||||
description: Displays the status of the hard disk (creates a new entry for each disk).
|
||||
disk_exceed_bad_sector_thr:
|
||||
description: Displays true / false to indicate if the hard disk exceeded the maximum bad sector threshold (creates a new entry for each disk). (Does not work with DSM 5.x)
|
||||
disk_below_remain_life_thr:
|
||||
description: Displays true / false to indicate if the hard disk dropped below the remain life threshold (creates a new entry for each disk). (Does not work with DSM 5.x)
|
||||
disk_temp:
|
||||
description: Displays the temperature of the hard disk (creates a new entry for each disk, uses the unit_system to display in C or F).
|
||||
volume_status:
|
||||
description: Displays the status of the volume (creates a new entry for each volume).
|
||||
volume_device_type:
|
||||
description: Displays the volume type (RAID, etc) (creates a new entry for each volume).
|
||||
volume_size_total:
|
||||
description: Displays the total size of the volume in GB's (creates a new entry for each volume).
|
||||
volume_size_used:
|
||||
description: Displays the used space on this volume in GB's (creates a new entry for each volume).
|
||||
volume_percentage_used:
|
||||
description: Displays the percentage used for this volume in GB's (creates a new entry for each volume).
|
||||
volume_disk_temp_avg:
|
||||
description: Displays the average temperature of all disks in the volume (creates a new entry for each volume).
|
||||
volume_disk_temp_max:
|
||||
description: Displays the maximum temperature of all disks in the volume (creates a new entry for each volume).
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
<div class='note warning'>
|
||||
This sensor will wake up your Synology NAS if it's in hibernation mode.
|
||||
</div>
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
If you set `ssl:` to `False`, you *have* to also explicitly set `port:` to **5000**.
|
||||
|
||||
</div>
|
||||
|
||||
## Separate User Configuration
|
||||
|
||||
Due to the nature of the Synology DSM API it is required to grant the user admin rights. This is related to the fact that utilization information is stored in the core module.
|
||||
|
||||
When creating the user it is possible to deny access to all locations and applications. By doing this the user will not be able to login to the web interface or view any of the files on the Synology NAS. It is still able to read the utilization and storage information using the API.
|
||||
@ -13,6 +13,7 @@ ha_codeowners:
|
||||
- '@michaelarnauts'
|
||||
- '@bdraco'
|
||||
ha_domain: tado
|
||||
ha_config_flow: true
|
||||
---
|
||||
|
||||
The `tado` integration platform is used as an interface to the [my.tado.com](https://my.tado.com/) website.
|
||||
@ -26,7 +27,9 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
## Configuration
|
||||
|
||||
To use your Tado thermostats in your installation, add the following to your `configuration.yaml` file:
|
||||
To use your Tado thermostats in your installation, go to **Configuration** >> **Integrations** in the UI, click the button with `+` sign and from the list of integrations select **Tado**.
|
||||
|
||||
Alternatively, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry with multiple accounts
|
||||
|
||||
@ -69,6 +69,11 @@ stations:
|
||||
description: List of additional fuel stations to create entities for.
|
||||
required: false
|
||||
type: list
|
||||
show_on_map:
|
||||
description: Display all gas stations on map.
|
||||
default: true
|
||||
required: false
|
||||
type: boolean
|
||||
{% endconfiguration %}
|
||||
|
||||
## Full example
|
||||
@ -87,6 +92,7 @@ tankerkoenig:
|
||||
scan_interval: "0:10:01"
|
||||
stations:
|
||||
- 8531b393-1e42-423b-cb4d-e4b98cff8a0c
|
||||
show_on_map: false
|
||||
```
|
||||
|
||||
Assuming there are only two fuel stations within the specified range and location, you would get six sensor entities:
|
||||
|
||||
@ -25,8 +25,8 @@ This integration provides the following platforms:
|
||||
- Binary sensors - such as parking and charger connection.
|
||||
- Sensors - such as Battery level, Inside/Outside temperature, odometer, estimated range, and charging rate.
|
||||
- Device tracker - to track location of your car
|
||||
- Lock - Door lock and charger door lock. Enables you to control Tesla's door and charger door lock
|
||||
- Climate - HVAC control. Allow you to control (turn on/off, set target temperature) your Tesla's HVAC system.
|
||||
- Lock - Door lock, rear trunk lock, front trunk (frunk) lock and charger door lock. Enables you to control Tesla's door, trunks and charger door lock
|
||||
- Climate - HVAC control. Allow you to control (turn on/off, set target temperature) your Tesla's HVAC system. Also enables preset modes to enable or disable max defrost mode `defrost` or `normal` operation mode.
|
||||
- Switch - Charger and max range switch to allow you to start/stop charging and set max range charging. Update switch to allow you to disable polling of vehicles to conserve battery. Sentry mode switch to enable or disable Sentry mode.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -5,6 +5,7 @@ ha_category:
|
||||
- Alarm
|
||||
- Binary Sensor
|
||||
ha_release: 0.42
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@austinmroczek'
|
||||
ha_domain: totalconnect
|
||||
@ -12,28 +13,11 @@ ha_domain: totalconnect
|
||||
|
||||
The `totalconnect` integration provides connectivity with the Honeywell TotalConnect alarm systems used by many alarm companies.
|
||||
|
||||
If you have issues running this component, you may require `libxml2-dev` and `libxmlsec1-dev` packages. To install these on Raspbian, run the command `apt install libxml2-dev libxmlsec1-dev` with sudo.
|
||||
|
||||
## Alarm Control Panel
|
||||
|
||||
The integration provides an Alarm Control Panel for each TotalConnect location. It uses the name of your location from TotalConnect. For example, if your location name in TotalConnect is "Home", then you will get `alarm_control_panel.home` in Home Assistant.
|
||||
|
||||
The alarm control panel supports the following services: `alarm_arm_away`, `alarm_arm_home`, `alarm_arm_night` and `alarm_disarm`.
|
||||
|
||||
The `triggered` state also provides a state attribute called `triggered_source` giving more detail on what triggered the alarm:
|
||||
- `Police/Medical` is when sensors detected a burglar and/or a person pushed the Police or Medical button
|
||||
- `Fire/Smoke` is when fire or smoke is detected, or a person pushed the Fire button
|
||||
- `Carbon Monoxide` is when carbon monoxide is detected
|
||||
|
||||
## Binary Sensor
|
||||
|
||||
The integration provides a Binary Sensor for each TotalConnect zone. To see zones in TotalConnect "fault" status, your TotalConnect account must have "Sensor Events" enabled. Your alarm monitoring company may charge an extra fee to enable this.
|
||||
|
||||
The TotalConnect API has limited zone type information. Home Assistant device class `door` is assigned to TotalConnect door, window, perimeter, motion sensor, and most alarm panel buttons. The sensor will appear as `True` if the door is open (either fault or triggered in TotalConnect) and `False` otherwise. Device class `smoke` is assigned to TotalConnect smoke detectors and buttons with physical alarm panel "Response Type" setting of "Fire No Verification". The sensor will appear as `True` if smoke is detected. Device class `gas` is assigned to TotalConnect carbon monoxide detectors. The sensor will appear as `True` if gas is detected.
|
||||
|
||||
## Configuration
|
||||
|
||||
To enable TotalConnect, add the following lines to your `configuration.yaml`:
|
||||
To enable TotalConnect via the user interface, go to **Configuration** > **Integrations** > the "plus" button > Total Connect.
|
||||
|
||||
To enable TotalConnect via `configuration.yaml` add the following lines:
|
||||
|
||||
```yaml
|
||||
totalconnect:
|
||||
@ -42,10 +26,6 @@ totalconnect:
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
name:
|
||||
description: Name of device in Home Assistant.
|
||||
required: false
|
||||
type: string
|
||||
username:
|
||||
description: Username used to sign into the TotalConnect app/web client.
|
||||
required: true
|
||||
@ -59,7 +39,6 @@ password:
|
||||
You are highly encouraged to create a Total Connect user account specifically for Home Assistant. It should not have full administrative privileges.
|
||||
|
||||
## Automation example
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
- alias: "Alarm: Disarmed Daytime"
|
||||
@ -82,3 +61,23 @@ automation:
|
||||
service: scene.turn_on
|
||||
entity_id: scene.OnArmedAway
|
||||
```
|
||||
|
||||
If you have issues running this component, you may require `libxml2-dev` and `libxmlsec1-dev` packages. To install these on Raspbian, run the command `apt install libxml2-dev libxmlsec1-dev` with sudo.
|
||||
|
||||
## Alarm Control Panel
|
||||
|
||||
The integration provides an Alarm Control Panel for each TotalConnect location. It uses the name of your location from TotalConnect. For example, if your location name in TotalConnect is "Home", then you will get `alarm_control_panel.home` in Home Assistant.
|
||||
|
||||
The alarm control panel supports the following services: `alarm_arm_away`, `alarm_arm_home`, `alarm_arm_night` and `alarm_disarm`.
|
||||
|
||||
The `triggered` state also provides a state attribute called `triggered_source` giving more detail on what triggered the alarm:
|
||||
|
||||
- `Police/Medical` is when sensors detected a burglar and/or a person pushed the Police or Medical button
|
||||
- `Fire/Smoke` is when fire or smoke is detected, or a person pushed the Fire button
|
||||
- `Carbon Monoxide` is when carbon monoxide is detected
|
||||
|
||||
## Binary Sensor
|
||||
|
||||
The integration provides a Binary Sensor for each TotalConnect zone. To see zones in TotalConnect "fault" status, your TotalConnect account must have "Sensor Events" enabled. Your alarm monitoring company may charge an extra fee to enable this.
|
||||
|
||||
The TotalConnect API has limited zone type information. Home Assistant device class `door` is assigned to TotalConnect door, window, perimeter, motion sensor, and most alarm panel buttons. The sensor will appear as `True` if the door is open (either fault or triggered in TotalConnect) and `False` otherwise. Device class `smoke` is assigned to TotalConnect smoke detectors and buttons with physical alarm panel "Response Type" setting of "Fire No Verification". The sensor will appear as `True` if smoke is detected. Device class `gas` is assigned to TotalConnect carbon monoxide detectors. The sensor will appear as `True` if gas is detected.
|
||||
|
||||
@ -43,7 +43,7 @@ transmission:
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: "This is the IP address of your Transmission daemon, e.g., `192.168.1.1`."
|
||||
description: "This is the IP address of your Transmission daemon, e.g., `192.168.1.1` or `https://example.com/transmission/rpc`."
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
@ -96,6 +96,7 @@ Possible events are:
|
||||
|
||||
- transmission_downloaded_torrent
|
||||
- transmission_started_torrent
|
||||
- transmission_removed_torrent
|
||||
|
||||
Inside of the event, there is the name of the torrent that is started or completed, as it is seen in the Transmission User Interface.
|
||||
|
||||
@ -123,20 +124,30 @@ Adds a new torrent to download. It can either be a URL (HTTP, HTTPS or FTP), mag
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `name` | no | Name of the configured instance
|
||||
| `name` | yes | Name of the configured instance (Default: "Transmission")
|
||||
| `torrent` | no | Torrent to download
|
||||
|
||||
### Service `remove_torrent`
|
||||
|
||||
Removes a torrent from the client.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `name` | no | Name of the configured instance (Default: "Transmission")
|
||||
| `id` | no | ID of the torrent, can be found in the `torrent_info` attribute of the `*_torrents` sensors
|
||||
| `delete_data` | yes | Delete torrent data (Default: false)
|
||||
|
||||
|
||||
## Templating
|
||||
|
||||
### Sensor `started_torrents`
|
||||
### Attribute `torrent_info`
|
||||
|
||||
The state attribute `torrent_info` contains information about the torrents that are currently downloading. You can see this information in **Developer Tools** -> **States** -> `sensor.transmission_started_torrents` -> **Attributes**, or by adding a Markdown Card to Lovelace.
|
||||
All `*_torrents` sensors e.g. `sensor.transmission_total_torrents` or `sensor.transmission_started_torrents` have a state attribute `torrent_info` that contains information about the torrents that are currently in a corresponding state. You can see this information in **Developer Tools** -> **States** -> `sensor.transmission_total_torrents` -> **Attributes**, or by adding a Markdown Card to Lovelace.
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
content: >
|
||||
{% set payload = state_attr('sensor.transmission_started_torrents', 'torrent_info') %}
|
||||
{% set payload = state_attr('sensor.transmission_total_torrents', 'torrent_info') %}
|
||||
|
||||
{% for torrent in payload.items() %} {% set name = torrent[0] %} {% set data = torrent[1] %}
|
||||
|
||||
|
||||
@ -12,6 +12,7 @@ ha_category:
|
||||
- Switch
|
||||
- Climate
|
||||
ha_release: pre 0.7
|
||||
ha_config_flow: true
|
||||
ha_domain: vera
|
||||
---
|
||||
|
||||
@ -32,43 +33,23 @@ and will be automatically added when HA connects to your Vera controller.
|
||||
|
||||
## Configuration
|
||||
|
||||
To use Vera devices in your installation, add the following to your `configuration.yaml` file using the IP and port number of your Vera controller:
|
||||
|
||||
```yaml
|
||||
vera:
|
||||
vera_controller_url: http://192.168.1.161:3480/
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
vera_controller_url:
|
||||
description: The URL for your Vera device.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
<div class='note'>
|
||||
|
||||
It is recommended to assign a static IP address to your Vera Controller. This ensures that it won't change IP addresses, so you won't have to change the `vera_controller_url` if it reboots and comes up with a different IP address. See your router's manual for details on how to set this up. If you need the MAC address of your Vera, check the label on the bottom.
|
||||
|
||||
</div>
|
||||
|
||||
### Configure devices
|
||||
1. From the Home Assistant front-end, navigate to 'Configuration' then 'Integrations'. Under 'Set up a new integration' locate 'Vera' and click 'Configure'.
|
||||
2. Enter the URL for the controller and click 'Submit'.
|
||||
|
||||
By default your switches will be added to Home Assistant as switches, however, if some of them are light switches, you can tell Home Assistant this using the optional `lights` parameter as shown below.
|
||||
## Options
|
||||
Once the Vera integration is configured, you can set additional options in the integration, click the gear icon.
|
||||
|
||||
Vera imports detailed Z-Wave devices into Home Assistant. This can include system devices and other devices that you don't use; you can tell Home Assistant not to load these devices using the `exclude:` parameter as shown below.
|
||||
- Vera switch device - By default your switches will be added to Home Assistant as switches, however, if some of them are light switches, you can tell Home Assistant this by providing a list of light ids.
|
||||
- Vera device ids to exclude - Vera imports detailed Z-Wave devices into Home Assistant. This can include system devices and other devices that you don't use; you can tell Home Assistant not to load these devices by providing a list of device ids.
|
||||
|
||||
You can find the Vera device id either via the advanced properties of the device in the Vera UI or by checking the `Vera Device Id` attribute on each device imported into Home Assistant (under the developer tools).
|
||||
|
||||
```yaml
|
||||
vera:
|
||||
vera_controller_url: http://192.168.1.161:3480/
|
||||
# Optional to exclude devices - this is a list of vera device ids
|
||||
exclude: [ 13, 14, 16, 20, 23, 72, 73, 74, 75, 76, 77, 78, 88, 89, 99]
|
||||
# Optional to import switches as lights - this is a list of vera device ids
|
||||
lights: [15, 17, 19, 21, 22, 24, 26, 43, 64, 70, 87]
|
||||
```
|
||||
|
||||
### Using Z-Wave devices in automation
|
||||
|
||||
If you want to use a Z-Wave device from the Vera controller in Home Assistant automation, you'll need the entity id. In the Home Assistant UI you'll find all entities listed under the <img src='/images/screenshots/developer-tool-states-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> icon of the Developer Tools section. Look for entities that contain 'Vera Device Id' in their attributes, and you'll find the entity id on the left.
|
||||
|
||||
@ -1,113 +0,0 @@
|
||||
---
|
||||
title: Yahoo Weather
|
||||
description: Instructions on how to integrate Yahoo Weather within Home Assistant.
|
||||
ha_category:
|
||||
- Weather
|
||||
- Sensor
|
||||
ha_release: 0.24
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: yweather
|
||||
---
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
The Yahoo Weather API is being [retired](https://developer.yahoo.com/weather/?guccounter=1). A replacement is the [`OpenWeatherMap` integration](/integrations/openweathermap).
|
||||
|
||||
</div>
|
||||
|
||||
The `yweather` platform uses [Yahoo Weather](https://www.yahoo.com/news/weather/) as a source for current meteorological data. The `forecast` will show you the condition for 5 days, 0 is the current day. You can use only `weather`, `temp_min`, and `temp_max` with forecast. It's important to note that a yweather sensor will only show ONE days forecast at a time so to show multiple days forecasts, you will need to use the 'name:' option and give each sensor a unique name.
|
||||
|
||||
<div class='note warning'>
|
||||
Use of the Yahoo Weather API should not exceed reasonable request volume. Access is limited to 2000 signed calls per day.
|
||||
</div>
|
||||
|
||||
The `woeid` (Where On Earth ID) for your location, as shown in the example below. You can find your WOEID by copying the numeric digits at the end of the URL for your location at [Yahoo Weather](https://www.yahoo.com/news/weather/). If you don't add a WOEID it is generated from Home Assistant's latitude and longitude.
|
||||
|
||||
To add Yahoo Weather to your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: yweather
|
||||
monitored_conditions:
|
||||
- weather
|
||||
- weather_current
|
||||
- temp_min
|
||||
- temp_max
|
||||
- wind_speed
|
||||
- pressure
|
||||
- visibility
|
||||
- humidity
|
||||
- temperature
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
woeid:
|
||||
required: false
|
||||
description: See above.
|
||||
type: string
|
||||
default: "Defaults to a WOEID generated from coordinates defined in your `configuration.yaml` file."
|
||||
forecast:
|
||||
required: false
|
||||
description: Day of forecast. The default is the current day to display conditions.
|
||||
type: integer
|
||||
default: 0
|
||||
name:
|
||||
required: false
|
||||
description: "The name of the sensor. To easily recognize each sensor when adding more than one Yahoo weather sensor, it is recommended to use the name option."
|
||||
type: string
|
||||
default: "`Yweather`"
|
||||
monitored_conditions:
|
||||
required: true
|
||||
description: Conditions to display in the frontend.
|
||||
type: list
|
||||
keys:
|
||||
weather:
|
||||
description: A human-readable text summary with picture from yahoo.
|
||||
weather_current:
|
||||
description: A human-readable text summary with picture from yahoo from current condition.
|
||||
temperature:
|
||||
description: The current temperature.
|
||||
temp_min:
|
||||
description: The minimal temperature of this day.
|
||||
temp_max:
|
||||
description: The maximum temperature of this day.
|
||||
wind_speed:
|
||||
description: The wind speed.
|
||||
humidity:
|
||||
description: The relative humidity.
|
||||
pressure:
|
||||
description: The sea-level air pressure in millibars.
|
||||
visibility:
|
||||
description: The average visibility.
|
||||
{% endconfiguration %}
|
||||
|
||||
Example of forecast using multiple days. In example, first sensor shows tomorrow's forecast, second sensor shows the next day and so on:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
sensor:
|
||||
- platform: yweather
|
||||
forecast: 1
|
||||
name: yw_day1
|
||||
monitored_conditions:
|
||||
- weather
|
||||
- temp_min
|
||||
- temp_max
|
||||
- platform: yweather
|
||||
forecast: 2
|
||||
name: yw_day2
|
||||
monitored_conditions:
|
||||
- weather
|
||||
- temp_min
|
||||
- temp_max
|
||||
- platform: yweather
|
||||
forecast: 3
|
||||
name: yw_day3
|
||||
monitored_conditions:
|
||||
- weather
|
||||
- temp_min
|
||||
- temp_max
|
||||
```
|
||||
|
||||
Details about the API are available in the [Yahoo! Developer Network](https://developer.yahoo.com/weather/).
|
||||
@ -74,7 +74,7 @@ image:
|
||||
type: string
|
||||
secondary_info:
|
||||
required: false
|
||||
description: "Show additional info. Values: `entity-id`, `last-changed`, `last-triggered` (only for automations and scripts)."
|
||||
description: "Show additional info. Values: `entity-id`, `last-changed`, `last-triggered` (only for automations and scripts), `position` or `tilt-position` (only for supported covers)."
|
||||
type: string
|
||||
format:
|
||||
required: false
|
||||
@ -113,34 +113,33 @@ double_tap_action:
|
||||
|
||||
## Special Row Elements
|
||||
|
||||
### Call Service
|
||||
### Button
|
||||
|
||||
{% configuration %}
|
||||
type:
|
||||
required: true
|
||||
description: call-service
|
||||
description: button
|
||||
type: string
|
||||
name:
|
||||
required: true
|
||||
description: Main Label.
|
||||
type: string
|
||||
service:
|
||||
required: true
|
||||
description: "Service like `media_player.media_play_pause`"
|
||||
type: string
|
||||
icon:
|
||||
required: false
|
||||
description: "Icon to display (e.g., `mdi:home`)"
|
||||
type: string
|
||||
default: "`mdi:remote`"
|
||||
action_name:
|
||||
required: false
|
||||
description: Button label.
|
||||
type: string
|
||||
default: "`Run`"
|
||||
service_data:
|
||||
tap_action:
|
||||
required: true
|
||||
description: Action taken on card tap. See [action documentation](/lovelace/actions/#tap-action).
|
||||
type: map
|
||||
hold_action:
|
||||
required: false
|
||||
description: The service data to use.
|
||||
description: Action taken on card tap and hold. See [action documentation](/lovelace/actions/#hold-action).
|
||||
type: map
|
||||
double_tap_action:
|
||||
required: false
|
||||
description: Action taken on card double tap. See [action documentation](/lovelace/actions/#double-tap-action).
|
||||
type: map
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
@ -24,12 +24,12 @@ homeassistant:
|
||||
|
||||
#### Changes
|
||||
|
||||
<img src='/images/supported_brands/honeywell.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' /><img src='/images/supported_brands/orvibo.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' /><img src='/images/supported_brands/pushetta.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' />
|
||||
<img src='/images/supported_brands/honeywell.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' /><img src='/images/supported_brands/orvibo.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 16px;' height='50' />
|
||||
|
||||
* Thermostat: [Honeywell](/integrations/honeywell/) now supported ([@sander76])
|
||||
* Switch: [Orvibo](/integrations/orvibo) now supported ([@happyleavesaoc])
|
||||
* Camera: [mjpeg camera's](/integrations/mjpeg) now supported ([@ryanturner])
|
||||
* Notify: [Pushetta](/integrations/pushetta) now supported ([@fabaff])
|
||||
* Notify: Pushetta now supported ([@fabaff])
|
||||
* Light: [MQTT](/integrations/light.mqtt/) now supported ([@hexxter])
|
||||
* Light: [Z-Wave](/integrations/zwave/) now supported ([@leoc])
|
||||
* Switch: [Z-Wave](/integrations/zwave/) now supported ([@leoc])
|
||||
|
||||
@ -21,10 +21,10 @@ hass --script db_migrator --config /path/to/config
|
||||
|
||||
You can omit the `--config` option if you use the default configuration directory. Run the script with `--help` to get more options.
|
||||
|
||||
<img src='/images/supported_brands/yahooweather.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/joaoapps_join.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='https://brands.home-assistant.io/knx/logo.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/tp-link.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
|
||||
<img src='/images/supported_brands/joaoapps_join.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='https://brands.home-assistant.io/knx/logo.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' /><img src='/images/supported_brands/tp-link.png' style='clear: right; margin-left: 5px; border:none; box-shadow: none; float: right; margin-bottom: 16px;' width='150' />
|
||||
|
||||
- Config: Improved support for storing [secrets][secrets] ([@kellerza])
|
||||
- Sensor: Support for [Yahoo! Weather][yahoo-weather] ([@pvizeli])
|
||||
- Sensor: Support for Yahoo! Weather ([@pvizeli])
|
||||
- Add scripts to command line to expose advanced options ([@balloob])
|
||||
- Alarm: [SimpliSafe][simplisafe] is now supported ([@w1ll1am23])
|
||||
- Core: Switch to SQLAlchemy for the Recorder component ([@rhooper])
|
||||
@ -92,6 +92,5 @@ Quick hot fix after we found a bug in the migrator where it wouldn't work with a
|
||||
[Telegram]: /integrations/telegram
|
||||
[TPLink]: /integrations/tplink
|
||||
[Verisure]: /integrations/verisure
|
||||
[yahoo-weather]: /integrations/yweather
|
||||
[Z-Wave]: /integrations/zwave/
|
||||
[RFXtrx]: /integrations/rfxtrx/
|
||||
|
||||
@ -90,7 +90,7 @@ sensor
|
||||
- Wink: Support for Wink Smoke and CO detectors ([@w1ll1am23])
|
||||
- Sensor: [TED5000][ted5000] sensor was included ([@gwendalg])
|
||||
- Sensor: Support for [Västtrafik][vasttrafik] public transport ([@persandstrom])
|
||||
- Notify: [Pushetta][pushetta] no longer sends message on start up ([@Danielhiversen])
|
||||
- Notify: Pushetta no longer sends message on start up ([@Danielhiversen])
|
||||
- Sensor: [Forecast.io][forecast] sensor was replaced by [Dark Sky][darksky] ([@fabaff])
|
||||
- Device Tracker: The `known_device.yaml` file is now validated ([@kellerza])
|
||||
- Minor features and bug fixes by [@tchellomello], [@pavoni], [@fabaff], [@pvizeli], [@lwis], [@turbokongen], [@Danielhiversen], [@persandstrom], [@balloob], [@robbiet480], [@sam-io], [@bbangert], and you if you are missing here.
|
||||
@ -170,7 +170,6 @@ sensor
|
||||
[mysensors-cover]: /integrations/cover.mysensors/
|
||||
[notebook]: http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb
|
||||
[pi-image]: /blog/2016/10/01/we-have-raspberry-image-now/
|
||||
[pushetta]: /integrations/pushetta
|
||||
[pwrctrl-switch]: /integrations/anel_pwrctrl
|
||||
[rest-sensor]: /integrations/rest
|
||||
[stats-sensor]: /integrations/statistics
|
||||
|
||||
@ -197,7 +197,7 @@ automation:
|
||||
- update to pywebpush 1.0.4 which allows install on system with openssl-1.1.0 (cryptography dep) ([@perosb] - [#7915]) ([notify.html5 docs])
|
||||
- Do not call update() in constructor ([@fabaff] - [#7917]) ([sensor.dte_energy_bridge docs]) ([sensor.dublin_bus_transport docs]) ([sensor.dweet docs]) ([sensor.ebox docs]) ([sensor.ecobee docs]) ([sensor.hddtemp docs]) ([sensor.mold_indicator docs]) ([sensor.pi_hole docs]) (sensor.yahoo_finance docs)
|
||||
- Fix changes introduced with #7917 ([@fabaff] - [#7930]) ([sensor.waqi docs])
|
||||
- Do not call update() in constructor ([@fabaff] - [#7931]) ([sensor.yweather docs])
|
||||
- Do not call update() in constructor ([@fabaff] - [#7931])
|
||||
- Add service_url config option to volvooncall ([@palp] - [#7919]) ([volvooncall docs])
|
||||
- Added 'change' field to statistics sensor ([@jminn] - [#7820]) ([sensor.statistics docs])
|
||||
- add ripple sensor ([@nkgilley] - [#7935]) ([sensor.ripple docs]) (new-platform)
|
||||
@ -540,7 +540,6 @@ automation:
|
||||
[sensor.template docs]: /integrations/template
|
||||
[sensor.waqi docs]: /integrations/waqi
|
||||
[sensor.wunderground docs]: /integrations/wunderground
|
||||
[sensor.yweather docs]: /integrations/yweather
|
||||
[spc docs]: /integrations/spc/
|
||||
[splunk docs]: /integrations/splunk/
|
||||
[switch.homematic docs]: /integrations/homematic
|
||||
|
||||
@ -127,7 +127,7 @@ amcrest:
|
||||
- Fix pylint issue ([@fabaff] - [#8325]) ([snips docs])
|
||||
- vsure 1.3.7 ([@persandstrom] - [#8321]) ([verisure docs])
|
||||
- Update pyEmby to fix media images ([@mezz64] - [#8331]) ([media_player.emby docs])
|
||||
- Partially revert #7931 ([@fabaff] - [#8326]) ([sensor.yweather docs])
|
||||
- Partially revert #7931 ([@fabaff] - [#8326])
|
||||
- Only allow 'tls_insecure_set()' if cert is present (fixes #8329) ([@fabaff] - [#8337]) ([mqtt docs])
|
||||
- Fix issue #8285 ([@Sabesto] - [#8340]) ([modbus docs]) ([binary_sensor.modbus docs]) ([climate.flexit docs]) ([sensor.modbus docs]) ([switch.modbus docs])
|
||||
- Bump dlib face_recognition to 0.2.0 ([@pvizeli] - [#8345]) ([image_processing.dlib_face_detect docs]) ([image_processing.dlib_face_identify docs])
|
||||
@ -449,7 +449,6 @@ amcrest:
|
||||
[sensor.otp docs]: /integrations/otp
|
||||
[sensor.rflink docs]: /integrations/sensor.rflink/
|
||||
[sensor.waqi docs]: /integrations/waqi
|
||||
[sensor.yweather docs]: /integrations/yweather
|
||||
[sensor.zha docs]: /integrations/zha
|
||||
[snips docs]: /integrations/snips/
|
||||
[switch.broadlink docs]: /integrations/broadlink#switch
|
||||
|
||||
@ -120,7 +120,7 @@ conversation:
|
||||
```
|
||||
|
||||
- Switch fritzdect: attributes have been renamed to use underscores and no capital letters ([@thomasklingbeil] - [#8436]) (breaking change)
|
||||
- Yahoo Weather: no longer allow configuring forecasts but include all instead. ([@fanthos] - [#8626]) ([weather.yweather docs]) (breaking change)
|
||||
- Yahoo Weather: no longer allow configuring forecasts but include all instead. ([@fanthos] - [#8626]) (breaking change)
|
||||
- The Home Assistant Z-Wave Cover implementation has been updated to support the latest development version of OpenZWave. If you are currently applying a workaround to your OpenZWave installation to support the barrier command class, you'll need to make sure you update your workaround to the latest development version of OpenZWave. ([@firstof9] - [#8574]) ([cover docs]) ([cover.zwave docs]) (breaking change)
|
||||
|
||||
## All changes
|
||||
@ -188,7 +188,7 @@ conversation:
|
||||
- Fixes Fitbit sensor to report battery level with the expected device ([@tchellomello] - [#8647]) ([sensor.fitbit docs])
|
||||
- Upgrade aiolifx ([@amelchio] - [#8648]) ([light.lifx docs])
|
||||
- Velbus ([@thomasdelaet] - [#8076]) ([velbus docs]) ([binary_sensor.velbus docs]) ([light.velbus docs]) (new-platform)
|
||||
- Yahoo Weather update, supports forecast for more days ([@fanthos] - [#8626]) ([weather.yweather docs]) (breaking change)
|
||||
- Yahoo Weather update, supports forecast for more days ([@fanthos] - [#8626]) (breaking change)
|
||||
- History performance improvements for single-entity requests ([@OverloadUT] - [#8632]) ([history docs])
|
||||
- Add transition support to light.zha ([@jawilson] - [#8548]) ([light.zha docs])
|
||||
- Add uk_transport component. ([@robmarkcole] - [#8600]) ([sensor.uk_transport docs]) (new-platform)
|
||||
@ -396,7 +396,6 @@ conversation:
|
||||
[switch.xiaomi docs]: /integrations/switch.xiaomi_aqara/
|
||||
[switch.xiaomi_vacuum docs]: /integrations/vacuum.xiaomi_miio/
|
||||
[velbus docs]: /integrations/velbus/
|
||||
[weather.yweather docs]: /integrations/yweather
|
||||
[wink docs]: /integrations/wink/
|
||||
[xiaomi docs]: /integrations/xiaomi_aqara
|
||||
[forum]: https://community.home-assistant.io/
|
||||
|
||||
@ -136,7 +136,7 @@ vacuum:
|
||||
- Polymer 2 ([@balloob] - [#8815]) ([group docs])
|
||||
- geizhals sensor component ([@JulianKahnert] - [#8458]) ([sensor.geizhals docs]) (new-platform)
|
||||
- Xiaomi vacuum as platform of new `vacuum` component derived from ToggleEntity, and services ([@azogue] - [#8623]) (breaking change) (new-platform)
|
||||
- Update yweather.py ([@fanthos] - [#8820]) ([weather.yweather docs])
|
||||
- Update yweather.py ([@fanthos] - [#8820])
|
||||
- Make HA discover sabnzbd and add it to the Configurator ([@Hellowlol] - [#8634]) ([sensor.sabnzbd docs])
|
||||
- Fix Dyson sensors if devices are configured without standby monitoring. Fixes #8569 ([@CharlesBlonde] - [#8826]) ([dyson docs]) ([fan.dyson docs]) ([sensor.dyson docs])
|
||||
- Block dependencies that depend on enum34 ([@balloob] - [#8698])
|
||||
@ -450,7 +450,6 @@ vacuum:
|
||||
[vacuum.roomba docs]: /integrations/roomba
|
||||
[vacuum.xiaomi docs]: /integrations/vacuum.xiaomi_miio/
|
||||
[weather.buienradar docs]: /integrations/buienradar
|
||||
[weather.yweather docs]: /integrations/yweather
|
||||
[weather.zamg docs]: /integrations/zamg#weather
|
||||
[wink docs]: /integrations/wink/
|
||||
[zwave docs]: /integrations/zwave/
|
||||
|
||||
@ -62,7 +62,7 @@ Our about screen that shows the error logs has gained a nice upgrade by [@postlu
|
||||
|
||||
## Release 0.58.1 - November 21
|
||||
|
||||
- Fix yweather ([@tinloaf] - [#10661]) ([weather.yweather docs])
|
||||
- Fix yweather ([@tinloaf] - [#10661])
|
||||
- Properly initialize Harmony remote ([@amelchio] - [#10665]) ([remote.harmony docs])
|
||||
- Handle the new version of HydroQuebec website ([@titilambert] - [#10682])
|
||||
- Fix for time_date sensor ([@etsinko] - [#10694]) ([sensor.time_date docs])
|
||||
@ -168,7 +168,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- Add panel build type ([@balloob] - [#10589])
|
||||
- Cloud updates ([@balloob] - [#10567])
|
||||
- Upgrade youtube_dl to 2017.11.15 ([@fabaff] - [#10592]) ([media_extractor docs])
|
||||
- Fix Yahoo Weather icons over SSL ([@OnFreund] - [#10602]) ([sensor.yweather docs])
|
||||
- Fix Yahoo Weather icons over SSL ([@OnFreund] - [#10602])
|
||||
- Arlo - Fixes for updated library ([@jwillaz] - [#9892]) ([arlo docs]) ([camera.arlo docs]) ([sensor.arlo docs])
|
||||
- Do not add panel from system_log ([@postlund] - [#10600]) ([system_log docs])
|
||||
- Fix ValueError exception ([@ziotibia81] - [#10596]) ([sensor.modbus docs])
|
||||
@ -459,7 +459,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[sensor.viaggiatreno docs]: /integrations/viaggiatreno
|
||||
[sensor.vultr docs]: /integrations/vultr#sensor
|
||||
[sensor.wunderground docs]: /integrations/wunderground
|
||||
[sensor.yweather docs]: /integrations/yweather
|
||||
[sensor.zamg docs]: /integrations/zamg#sensor
|
||||
[spc docs]: /integrations/spc/
|
||||
[switch.broadlink docs]: /integrations/broadlink#switch
|
||||
@ -493,4 +492,3 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[@titilambert]: https://github.com/titilambert
|
||||
[remote.harmony docs]: /integrations/harmony
|
||||
[sensor.time_date docs]: /integrations/time_date
|
||||
[weather.yweather docs]: /integrations/yweather
|
||||
|
||||
@ -119,7 +119,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- Use new DoorBirdPy (v0.1.0) ([@Klikini] - [#10734]) ([doorbird docs])
|
||||
- Add fan and reduce I/O calls in radiotherm ([@TD22057] - [#10437]) ([climate.radiotherm docs])
|
||||
- New Hive Component / Platforms ([@Rendili] - [#9804]) ([hive docs]) ([climate.hive docs]) ([light.hive docs]) ([sensor.hive docs]) ([switch.hive docs]) (new-platform)
|
||||
- Temporarily fix yahoo weather API issue and add unit test. ([@cgtobi] - [#10737]) ([sensor.yweather docs])
|
||||
- Temporarily fix yahoo weather API issue and add unit test. ([@cgtobi] - [#10737])
|
||||
- Google assistant climate mode fix ([@braddparker] - [#10726]) ([google_assistant.smart_home docs])
|
||||
- Protect sensitive information for Amcrest cameras ([@tchellomello] - [#10569]) ([amcrest docs]) ([camera.amcrest docs]) ([sensor.amcrest docs])
|
||||
- InfluxDB send retry after IOError ([@janLo] - [#10263]) ([influxdb docs])
|
||||
@ -384,7 +384,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[sensor.tellstick docs]: /integrations/tellstick#sensor
|
||||
[sensor.whois docs]: /integrations/whois
|
||||
[sensor.wunderground docs]: /integrations/wunderground
|
||||
[sensor.yweather docs]: /integrations/yweather
|
||||
[shell_command docs]: /integrations/shell_command/
|
||||
[shopping_list docs]: /integrations/shopping_list/
|
||||
[switch.hive docs]: /integrations/hive#switch
|
||||
|
||||
@ -196,7 +196,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
|
||||
- Upgrade aiohttp_cors to 0.6.0 ([@fabaff] - [#11310]) ([http docs])
|
||||
- Upgrade pysnmp to 4.4.3 ([@fabaff] - [#11317]) ([device_tracker.snmp docs]) ([sensor.snmp docs]) ([switch.snmp docs])
|
||||
- Upgrade luftdaten to 0.1.3 ([@fabaff] - [#11316]) ([sensor.luftdaten docs])
|
||||
- Upgrade yahooweather to 0.10 ([@fabaff] - [#11309]) ([weather.yweather docs])
|
||||
- Upgrade yahooweather to 0.10 ([@fabaff] - [#11309])
|
||||
- Upgrade distro to 1.2.0 ([@fabaff] - [#11312]) ([updater docs])
|
||||
- Upgrade python-digitalocean to 1.13.2 ([@fabaff] - [#11311]) ([digital_ocean docs])
|
||||
- Upgrade youtube_dl to 2017.12.23 ([@fabaff] - [#11308]) ([media_extractor docs])
|
||||
@ -325,7 +325,7 @@ Note however, that this feature was replaced by a new ignore_string config optio
|
||||
- Changed device type of media player and cover to switch ([@Laqoore] - [#11483]) ([google_assistant.smart_home docs])
|
||||
- Control ordering of display in history component ([@rwa] - [#11340]) ([history docs])
|
||||
- Pr/11430 ([@balloob] - [#11587])
|
||||
- Cast return values and add unit tests for the yahoo weather component. ([@cgtobi] - [#10699]) ([weather.yweather docs])
|
||||
- Cast return values and add unit tests for the yahoo weather component. ([@cgtobi] - [#10699])
|
||||
- add velux roller shutter to tahoma ([@thijsdejong] - [#11586]) ([tahoma docs])
|
||||
- Added support for enable/disable motion detection ([@abjorshammar] - [#11583]) ([camera.uvc docs])
|
||||
- Avoid returning empty media_image_url string ([@JackWindows] - [#11557]) ([media_player.cast docs])
|
||||
@ -768,7 +768,6 @@ Note however, that this feature was replaced by a new ignore_string config optio
|
||||
[vacuum.xiaomi_miio docs]: /integrations/vacuum.xiaomi_miio/
|
||||
[weather.darksky docs]: /integrations/weather.darksky/
|
||||
[weather.openweathermap docs]: /integrations/openweathermap#weather
|
||||
[weather.yweather docs]: /integrations/yweather
|
||||
[websocket_api docs]: /integrations/websocket_api/
|
||||
[wemo docs]: /integrations/wemo/
|
||||
[zigbee docs]: /integrations/zigbee/
|
||||
|
||||
@ -114,7 +114,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- Fix bad metrics format for short metrics. ([@michaelkuty] - [#13778]) ([prometheus docs])
|
||||
- Update bellows to 0.5.2 ([@rcloran] - [#13800]) ([zha docs])
|
||||
- device_tracker.ubus: Handle devices not running DHCP ([@tobygray] - [#13579]) ([device_tracker docs])
|
||||
- Update yweather.py ([@wiuwiu] - [#13802]) ([weather.yweather docs])
|
||||
- Update yweather.py ([@wiuwiu] - [#13802])
|
||||
- Tibber lib update ([@Danielhiversen] - [#13811]) ([sensor.tibber docs])
|
||||
- Update pyhomematic to 0.1.41 ([@danielperna84] - [#13814]) ([homematic docs])
|
||||
- Add support for Eufy bulbs and switches ([@mjg59] - [#13773]) ([eufy docs]) ([light.eufy docs]) ([switch.eufy docs]) (new-platform)
|
||||
@ -135,14 +135,14 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- Adding USCIS component ([@meauxt] - [#13764]) ([sensor.uscis docs]) (new-platform)
|
||||
- Avoid unnecessary cast state updates ([@dersger] - [#13770]) ([media_player.cast docs])
|
||||
- Prevent vesync doing I/O in event loop ([@balloob] - [#13862]) ([switch.vesync docs]) (beta fix)
|
||||
- Update yweather.py ([@TheCellMC] - [#13851]) ([weather.yweather docs])
|
||||
- Update yweather.py ([@TheCellMC] - [#13851])
|
||||
- add support for Kodi discovery ([@escoand] - [#13790]) ([media_player.kodi docs])
|
||||
- Further untangle data entry flow ([@balloob] - [#13855])
|
||||
- Missing property decorator added ([@syssi] - [#13889]) ([fan.xiaomi_miio docs]) (beta fix)
|
||||
- Fix race condition for component loaded before listening ([@balloob] - [#13887]) ([config docs]) (beta fix)
|
||||
- Added snips service descriptions ([@tschmidty69] - [#13883])
|
||||
- Add unique_id for BMW ConnectedDrive ([@gerard33] - [#13888]) ([binary_sensor.bmw_connected_drive docs]) ([lock.bmw_connected_drive docs]) ([sensor.bmw_connected_drive docs])
|
||||
- Revert "Update yweather.py" ([@pvizeli] - [#13900]) ([weather.yweather docs])
|
||||
- Revert "Update yweather.py" ([@pvizeli] - [#13900])
|
||||
- Eufy colour bulb updates ([@mjg59] - [#13895]) ([eufy docs]) ([light.eufy docs])
|
||||
- Fix #13846 Double underscore in bluetooth address ([@aav7fl] - [#13884]) ([device_tracker docs]) (beta fix)
|
||||
- Import operation modes from air humidifier ([@syssi] - [#13908]) ([fan.xiaomi_miio docs]) (beta fix)
|
||||
@ -506,7 +506,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[vacuum.neato docs]: /integrations/neato#vacuum
|
||||
[vacuum.roomba docs]: /integrations/roomba
|
||||
[vacuum.xiaomi_miio docs]: /integrations/vacuum.xiaomi_miio/
|
||||
[weather.yweather docs]: /integrations/yweather
|
||||
[zha docs]: /integrations/zha/
|
||||
[#14108]: https://github.com/home-assistant/home-assistant/pull/14108
|
||||
[#14113]: https://github.com/home-assistant/home-assistant/pull/14113
|
||||
|
||||
@ -69,7 +69,7 @@ rainmachine:
|
||||
## All changes
|
||||
|
||||
- Pollen.com: Added attributes on top 3 allergens ([@bachya] - [#14018]) ([sensor.pollen docs]) (breaking change)
|
||||
- Expose the condition code on condition sensors ([@maddox] - [#14011]) ([sensor.yweather docs])
|
||||
- Expose the condition code on condition sensors ([@maddox] - [#14011])
|
||||
- upgrade rfxtrx lib, dimming support for Lighting3 ([@Danielhiversen] - [#14026]) ([rfxtrx docs])
|
||||
- Add Accuracy to Google Location Sharing ([@rdbahm] - [#14039]) ([device_tracker docs])
|
||||
- bump gogogate2 version ([@dlbroadfoot] - [#14044]) ([cover.gogogate2 docs])
|
||||
@ -461,7 +461,6 @@ rainmachine:
|
||||
[sensor.uscis docs]: /integrations/uscis
|
||||
[sensor.wunderground docs]: /integrations/wunderground
|
||||
[sensor.xiaomi_aqara docs]: /integrations/sensor.xiaomi_aqara/
|
||||
[sensor.yweather docs]: /integrations/yweather
|
||||
[switch.deluge docs]: /integrations/deluge#switch
|
||||
[switch.fritzbox docs]: /integrations/fritzbox
|
||||
[switch.insteon_plm docs]: /integrations/insteon/
|
||||
|
||||
@ -295,7 +295,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- Fire an event when timer gets out of sync ([@amelchio] - [#17398])
|
||||
- Add context to scripts run by template entities ([@balloob] - [#17329]) ([cover.template docs]) ([fan.template docs]) ([light.template docs]) ([lock.template docs]) ([switch.template docs])
|
||||
- State is set to UNKNOWN rather than ON in order to make UI have an play/pause button ([@kennedyshead] - [#17357]) ([media_player.samsungtv docs])
|
||||
- Re-assign conditions ([@SilvrrGIT] - [#17364]) ([weather.yweather docs])
|
||||
- Re-assign conditions ([@SilvrrGIT] - [#17364])
|
||||
- Switched to async_fire ([@Julius2342] - [#17472]) ([knx docs])
|
||||
- Fix rangefilter ([@nielstron] - [#17473]) ([sensor.filter docs])
|
||||
- Cleanup HM Notify platform ([@pvizeli] - [#17355]) ([notify docs])
|
||||
@ -857,7 +857,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[weather.demo docs]: /integrations/weather.demo/
|
||||
[weather.met docs]: /integrations/met
|
||||
[weather.smhi docs]: /integrations/smhi
|
||||
[weather.yweather docs]: /integrations/yweather
|
||||
[websocket_api docs]: /integrations/websocket_api/
|
||||
[wink docs]: /integrations/wink/
|
||||
[xiaomi_aqara docs]: /integrations/xiaomi_aqara/
|
||||
|
||||
@ -614,7 +614,7 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
|
||||
- Add service description for route53 integration ([@tefinger] - [#27774])
|
||||
- Move imports in openweathermap component ([@Quentame] - [#27779]) ([openweathermap docs])
|
||||
- Move imports in apns component ([@Bouni] - [#27804]) ([apns docs])
|
||||
- Move imports in yweather ([@Misiu] - [#27842]) ([yweather docs])
|
||||
- Move imports in yweather ([@Misiu] - [#27842])
|
||||
- Move imports in brunt component ([@Bouni] - [#27856]) ([brunt docs])
|
||||
- Move imports in blockchain component ([@Bouni] - [#27852]) ([blockchain docs])
|
||||
- Move blackbird imports ([@Bouni] - [#27849]) ([blackbird docs])
|
||||
@ -1901,7 +1901,6 @@ The **holiday name** sensor has been renamed to **holiday**. ([@tsvi] - [#27654]
|
||||
[yeelight docs]: /integrations/yeelight/
|
||||
[yeelightsunflower docs]: /integrations/yeelightsunflower/
|
||||
[yr docs]: /integrations/yr/
|
||||
[yweather docs]: /integrations/yweather/
|
||||
[zengge docs]: /integrations/zengge/
|
||||
[zeroconf docs]: /integrations/zeroconf/
|
||||
[zestimate docs]: /integrations/zestimate/
|
||||
|
||||
@ -734,7 +734,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
- Report unavailable entities to google ([@elupus] - [#28501]) ([google_assistant docs])
|
||||
- Add initial test suite for arcam_fmj integration ([@elupus] - [#29335])
|
||||
- Fix uvloop warning ([@pvizeli] - [#29341]) ([stream docs])
|
||||
- Move imports to top for pushetta ([@springstan] - [#29332]) ([pushetta docs])
|
||||
- Move imports to top for pushetta ([@springstan] - [#29332])
|
||||
- Move imports to top for pencom ([@springstan] - [#29348]) ([pencom docs])
|
||||
- Include telegram_bot message id for all messages ([@luca-angemi] - [#29315]) ([telegram_bot docs])
|
||||
- Ignore state of climate entities in prometheus ([@springstan] - [#29346]) ([prometheus docs])
|
||||
@ -1677,7 +1677,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
[proxmoxve docs]: /integrations/proxmoxve/
|
||||
[ps4 docs]: /integrations/ps4/
|
||||
[pulseaudio_loopback docs]: /integrations/pulseaudio_loopback/
|
||||
[pushetta docs]: /integrations/pushetta/
|
||||
[python_script docs]: /integrations/python_script/
|
||||
[qbittorrent docs]: /integrations/qbittorrent/
|
||||
[qnap docs]: /integrations/qnap/
|
||||
|
||||
1685
source/_posts/2020-04-29-release-109.markdown
Normal file
1685
source/_posts/2020-04-29-release-109.markdown
Normal file
File diff suppressed because it is too large
Load Diff
@ -585,7 +585,6 @@
|
||||
/components/notify.nfandroidtv /integrations/nfandroidtv
|
||||
/components/notify.prowl /integrations/prowl
|
||||
/components/notify.pushbullet /integrations/pushbullet
|
||||
/components/notify.pushetta /integrations/pushetta
|
||||
/components/notify.pushover /integrations/pushover
|
||||
/components/notify.pushsafer /integrations/pushsafer
|
||||
/components/notify.rocketchat /integrations/rocketchat
|
||||
@ -872,7 +871,7 @@
|
||||
/components/sensor.swiss_hydrological_data /integrations/swiss_hydrological_data
|
||||
/components/sensor.swiss_public_transport /integrations/swiss_public_transport
|
||||
/components/sensor.syncthru /integrations/syncthru
|
||||
/components/sensor.synologydsm /integrations/synologydsm
|
||||
/components/sensor.synologydsm /integrations/synology_dsm
|
||||
/components/sensor.systemmonitor /integrations/systemmonitor
|
||||
/components/sensor.sytadin /integrations/sytadin
|
||||
/components/sensor.tado /integrations/tado
|
||||
@ -928,7 +927,6 @@
|
||||
/components/sensor.xbox_live /integrations/xbox_live
|
||||
/components/sensor.xs1 /integrations/xs1#sensors
|
||||
/components/sensor.yr /integrations/yr
|
||||
/components/sensor.yweather /integrations/yweather
|
||||
/components/sensor.zabbix /integrations/zabbix#sensor
|
||||
/components/sensor.zamg /integrations/zamg#sensor
|
||||
/components/sensor.zestimate /integrations/zestimate
|
||||
@ -1078,7 +1076,6 @@
|
||||
/components/weather.metoffice /integrations/metoffice
|
||||
/components/weather.openweathermap /integrations/openweathermap#weather
|
||||
/components/weather.smhi /integrations/smhi
|
||||
/components/weather.yweather /integrations/yweather
|
||||
/components/weather.zamg /integrations/zamg#weather
|
||||
/components/xiaomi /integrations/xiaomi_aqara
|
||||
|
||||
@ -1695,7 +1692,6 @@
|
||||
/components/pulseaudio_loopback /integrations/pulseaudio_loopback
|
||||
/components/push /integrations/push
|
||||
/components/pushbullet /integrations/pushbullet
|
||||
/components/pushetta /integrations/pushetta
|
||||
/components/pushover /integrations/pushover
|
||||
/components/pushsafer /integrations/pushsafer
|
||||
/components/pvoutput /integrations/pvoutput
|
||||
@ -1865,7 +1861,7 @@
|
||||
/components/synology /integrations/synology
|
||||
/components/synology_chat /integrations/synology_chat
|
||||
/components/synology_srm /integrations/synology_srm
|
||||
/components/synologydsm /integrations/synologydsm
|
||||
/components/synologydsm /integrations/synology_dsm
|
||||
/components/syslog /integrations/syslog
|
||||
/components/system_health /integrations/system_health
|
||||
/components/system_log /integrations/system_log
|
||||
@ -2014,7 +2010,6 @@
|
||||
/components/yessssms /integrations/yessssms
|
||||
/components/yi /integrations/yi
|
||||
/components/yr /integrations/yr
|
||||
/components/yweather /integrations/yweather
|
||||
/components/zabbix /integrations/zabbix
|
||||
/components/zamg /integrations/zamg
|
||||
/components/zengge /integrations/zengge
|
||||
@ -2030,6 +2025,7 @@
|
||||
|
||||
# Breaking changes
|
||||
/integrations/switch.pca /integrations/elv
|
||||
/integrations/synologydsm /integrations/synology_dsm
|
||||
/integrations/telegram_chatbot /integrations/telegram_bot
|
||||
|
||||
# Moved documentation
|
||||
|
||||
BIN
source/images/blog/2020-04-0.109/components.png
Normal file
BIN
source/images/blog/2020-04-0.109/components.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
BIN
source/images/blog/2020-04-0.109/integration-page.png
Normal file
BIN
source/images/blog/2020-04-0.109/integration-page.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 315 KiB |
BIN
source/images/blog/2020-04-0.109/io.png
Normal file
BIN
source/images/blog/2020-04-0.109/io.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
BIN
source/images/blog/2020-04-0.109/search.png
Normal file
BIN
source/images/blog/2020-04-0.109/search.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 122 KiB |
BIN
source/images/blog/2020-04-0.109/social.png
Normal file
BIN
source/images/blog/2020-04-0.109/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 143 KiB |
BIN
source/images/blog/2020-04-0.109/weather-card.png
Normal file
BIN
source/images/blog/2020-04-0.109/weather-card.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 14 KiB |
BIN
source/images/screenshots/homekit_pairing_example.png
Normal file
BIN
source/images/screenshots/homekit_pairing_example.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 72 KiB |
BIN
source/images/supported_brands/arris.jpg
Normal file
BIN
source/images/supported_brands/arris.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
BIN
source/images/supported_brands/diodes.png
Normal file
BIN
source/images/supported_brands/diodes.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 3.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.9 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 3.6 KiB |
Loading…
x
Reference in New Issue
Block a user