mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-19 15:26:59 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
bdb8e5becd
@ -101,8 +101,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 0
|
||||
current_minor_version: 106
|
||||
current_patch_version: 4
|
||||
date_released: 2020-03-02
|
||||
current_patch_version: 5
|
||||
date_released: 2020-03-03
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -35,8 +35,8 @@
|
||||
margin-bottom: 8px;
|
||||
|
||||
&.current {
|
||||
background-color: #3A5561;
|
||||
background-image: linear-gradient(to bottom, #3A5561,#3F6B7D);
|
||||
background-color: #3a5561;
|
||||
background-image: linear-gradient(to bottom, #3a5561, #3f6b7d);
|
||||
}
|
||||
}
|
||||
}
|
||||
@ -100,18 +100,20 @@
|
||||
background-color: #fefefe;
|
||||
margin: 4px;
|
||||
border-radius: 2px;
|
||||
box-shadow: 0 2px 2px 0 rgba(0, 0, 0, 0.14), 0 1px 5px 0 rgba(0, 0, 0, 0.12), 0 3px 1px -2px rgba(0, 0, 0, 0.2);
|
||||
box-shadow: 0 2px 2px 0 rgba(0, 0, 0, 0.14), 0 1px 5px 0 rgba(0, 0, 0, 0.12),
|
||||
0 3px 1px -2px rgba(0, 0, 0, 0.2);
|
||||
padding: 8px;
|
||||
text-align: center;
|
||||
text-decoration: none;
|
||||
|
||||
.img-container {
|
||||
height: 50px;
|
||||
margin: 8px 0;
|
||||
margin: 12px 0;
|
||||
font: 0/0 a;
|
||||
|
||||
&:before { /* create a full-height inline block pseudo=element */
|
||||
content: ' ';
|
||||
&:before {
|
||||
/* create a full-height inline block pseudo=element */
|
||||
content: " ";
|
||||
display: inline-block;
|
||||
vertical-align: middle; /* vertical alignment of the inline element */
|
||||
height: 100%;
|
||||
@ -127,32 +129,36 @@
|
||||
}
|
||||
|
||||
.title {
|
||||
display: -webkit-box;
|
||||
-webkit-line-clamp: 2;
|
||||
-webkit-box-orient: vertical;
|
||||
overflow: hidden;
|
||||
|
||||
text-decoration: none;
|
||||
font-size: 18px;
|
||||
color: #000;
|
||||
line-height: 1.3em;
|
||||
height: 2.6em;
|
||||
}
|
||||
|
||||
.category {
|
||||
font-size: 14px;
|
||||
color: #AAA;
|
||||
margin-top: 20px;
|
||||
}
|
||||
}
|
||||
|
||||
// fade-in animation
|
||||
&.show-items .option-card {
|
||||
opacity: 0;
|
||||
-webkit-animation:new-item-animation .2s linear forwards;
|
||||
-o-animation:new-item-animation .2s linear forwards;
|
||||
animation:new-item-animation .2s linear forwards;
|
||||
-webkit-animation: new-item-animation 0.2s linear forwards;
|
||||
-o-animation: new-item-animation 0.2s linear forwards;
|
||||
animation: new-item-animation 0.2s linear forwards;
|
||||
}
|
||||
|
||||
// fade-out animation
|
||||
&.remove-items .option-card {
|
||||
-webkit-animation:removed-item-animation .2s cubic-bezier(.55,-0.04,.91,.94) forwards;
|
||||
-o-animation:removed-item-animation .2s cubic-bezier(.55,-0.04,.91,.94) forwards;
|
||||
animation:removed-item-animation .2s cubic-bezier(.55,-0.04,.91,.94) forwards
|
||||
-webkit-animation: removed-item-animation 0.2s
|
||||
cubic-bezier(0.55, -0.04, 0.91, 0.94) forwards;
|
||||
-o-animation: removed-item-animation 0.2s
|
||||
cubic-bezier(0.55, -0.04, 0.91, 0.94) forwards;
|
||||
animation: removed-item-animation 0.2s cubic-bezier(0.55, -0.04, 0.91, 0.94)
|
||||
forwards;
|
||||
}
|
||||
}
|
||||
|
||||
@ -163,56 +169,56 @@
|
||||
-webkit-transform: scale(0);
|
||||
-ms-transform: scale(0);
|
||||
-o-transform: scale(0);
|
||||
transform:scale(0)
|
||||
transform: scale(0);
|
||||
}
|
||||
to {
|
||||
opacity: 1;
|
||||
-webkit-transform: scale(1);
|
||||
-ms-transform: scale(1);
|
||||
-o-transform: scale(1);
|
||||
transform:scale(1)
|
||||
transform: scale(1);
|
||||
}
|
||||
}
|
||||
@-webkit-keyframes new-item-animation {
|
||||
from {
|
||||
opacity: 0;
|
||||
-webkit-transform: scale(0);
|
||||
transform:scale(0)
|
||||
transform: scale(0);
|
||||
}
|
||||
to {
|
||||
opacity: 1;
|
||||
-webkit-transform: scale(1);
|
||||
transform:scale(1)
|
||||
transform: scale(1);
|
||||
}
|
||||
}
|
||||
@-o-keyframes new-item-animation {
|
||||
from {
|
||||
opacity: 0;
|
||||
-o-transform: scale(0);
|
||||
transform:scale(0)
|
||||
transform: scale(0);
|
||||
}
|
||||
to {
|
||||
opacity: 1;
|
||||
-o-transform: scale(1);
|
||||
transform:scale(1)
|
||||
transform: scale(1);
|
||||
}
|
||||
}
|
||||
|
||||
// space blocker animation
|
||||
@keyframes openspace {
|
||||
to {
|
||||
height:auto
|
||||
height: auto;
|
||||
}
|
||||
}
|
||||
|
||||
@-webkit-keyframes openspace {
|
||||
to {
|
||||
height:auto
|
||||
height: auto;
|
||||
}
|
||||
}
|
||||
@-o-keyframes openspace {
|
||||
to {
|
||||
height:auto
|
||||
height: auto;
|
||||
}
|
||||
}
|
||||
|
||||
@ -223,37 +229,37 @@
|
||||
-webkit-transform: scale(1);
|
||||
-ms-transform: scale(1);
|
||||
-o-transform: scale(1);
|
||||
transform:scale(1)
|
||||
transform: scale(1);
|
||||
}
|
||||
to {
|
||||
-webkit-transform: scale(0);
|
||||
-ms-transform: scale(0);
|
||||
-o-transform: scale(0);
|
||||
transform: scale(0);
|
||||
opacity:0
|
||||
opacity: 0;
|
||||
}
|
||||
}
|
||||
@-webkit-keyframes removed-item-animation {
|
||||
from {
|
||||
opacity: 1;
|
||||
-webkit-transform: scale(1);
|
||||
transform:scale(1)
|
||||
transform: scale(1);
|
||||
}
|
||||
to {
|
||||
-webkit-transform: scale(0);
|
||||
transform: scale(0);
|
||||
opacity:0
|
||||
opacity: 0;
|
||||
}
|
||||
}
|
||||
@-o-keyframes removed-item-animation {
|
||||
from {
|
||||
opacity: 1;
|
||||
-o-transform: scale(1);
|
||||
transform:scale(1)
|
||||
transform: scale(1);
|
||||
}
|
||||
to {
|
||||
-o-transform: scale(0);
|
||||
transform: scale(0);
|
||||
opacity:0
|
||||
opacity: 0;
|
||||
}
|
||||
}
|
||||
|
||||
@ -362,7 +362,7 @@ https://YOUR-HA-IP:8123
|
||||
|
||||
Some cases such as this are where your router does not allow 'loopback' or where there is a problem with incoming connections due to technical failure. In these cases you can still use your internal connection and safely ignore the warnings.
|
||||
|
||||
If you were previously using a webapp on your phone/tablet to access your Home Assistant you should delete the old one and create a new one with the new address. The old one will no longer work as it is not keyed to your new, secure URL. Instructions for creating your new webapp can be found [here](/docs/frontend/mobile/).
|
||||
If you were previously using a webapp on your phone/tablet to access your Home Assistant you should delete the old one and create a new one with the new address. The old one will no longer work as it is not keyed to your new, secure URL.
|
||||
|
||||
All done? Accessing your Home Assistant from across the world with your DuckDNS URL and a lovely secure logo on your browser? Ace! Now let's clean up our port forwards so that we are only exposing the parts of our network that are absolutely necessary to the outside world.
|
||||
|
||||
|
||||
@ -23,9 +23,11 @@ Change to your Home Assistant [configuration directory](/getting-started/configu
|
||||
The certificate **must** be `.pem` extension.
|
||||
|
||||
```bash
|
||||
openssl req -sha256 -newkey rsa:4096 -nodes -keyout privkey.pem -x509 -days 730 -out fullchain.pem
|
||||
openssl req -sha256 -addext "subjectAltName = IP:X.X.X.X" -newkey rsa:4096 -nodes -keyout privkey.pem -x509 -days 730 -out fullchain.pem
|
||||
```
|
||||
|
||||
Where the `X.X.X.X` must be replaced with the IP address of your local machine running Home Assistant (e.g., `192.168.1.20`).
|
||||
|
||||
For details about the parameters, please check the OpenSSL documentation. Provide the requested information during the generation process.
|
||||
|
||||
At the end you will have two files called `privkey.pem` and `fullchain.pem`. The key and the certificate.
|
||||
|
||||
@ -1,29 +0,0 @@
|
||||
---
|
||||
title: "Getting started on Mobile"
|
||||
description: "Android/iOS instructions to add Home Assistant to your homescreen."
|
||||
redirect_from: /getting-started/mobile/
|
||||
---
|
||||
|
||||
Home Assistant has [a companion app for both Android and iOS](/docs/ecosystem/ios/).
|
||||
|
||||
As an alternative to the iOS and Android companion apps, you can add the Home Assistant "web app" to your homescreen as if it was native (Home Assistant leverages the W3C [`manifest.json`](https://w3c.github.io/manifest/) support).
|
||||
|
||||
## Android
|
||||
|
||||
1. Open Chrome
|
||||
2. Navigate to your Home Assistant instance
|
||||
3. Tap on the Menu icon (three vertical bars)
|
||||
4. Tap on Add to Homescreen
|
||||
5. A dialog will popup; tap on Add
|
||||
|
||||
<p class='img' style='max-width:500px; margin-left: auto; margin-right: auto;'>
|
||||
<img src='/images/screenshots/android-homescreen-guide.gif' />
|
||||
</p>
|
||||
|
||||
## iOS
|
||||
|
||||
1. Open Safari
|
||||
2. Navigate to your Home Assistant instance
|
||||
3. Tap on the Share icon in the middle of the bottom toolbar
|
||||
4. Tap on "Add to Home Screen"
|
||||
5. A dialog will popup; tap on Add
|
||||
@ -96,13 +96,13 @@ These guides are provided as-is. Some of these install methods are more limited
|
||||
</a>
|
||||
<a class='option-card' href='/docs/installation/macos/'>
|
||||
<div class='img-container'>
|
||||
<img src='/images/supported_brands/apple.png' />
|
||||
<img src='https://brands.home-assistant.io/ios/icon.png' />
|
||||
</div>
|
||||
<div class='title'>macOS</div>
|
||||
</a>
|
||||
<a class='option-card' href='/docs/installation/synology/'>
|
||||
<div class='img-container'>
|
||||
<img src='/images/supported_brands/synology.png' />
|
||||
<img src='https://brands.home-assistant.io/synology/logo.png' />
|
||||
</div>
|
||||
<div class='title'>Synology</div>
|
||||
</a>
|
||||
@ -114,7 +114,7 @@ These guides are provided as-is. Some of these install methods are more limited
|
||||
</a>
|
||||
<a class='option-card' href='/hassio/installation/#alternative-install-on-a-generic-linux-host'>
|
||||
<div class='img-container'>
|
||||
<img src='/images/supported_brands/home-assistant.png' />
|
||||
<img src='https://brands.home-assistant.io/homeassistant/icon.png' />
|
||||
</div>
|
||||
<div class='title'>Home Assistant Supervised <br> on generic Linux server</div>
|
||||
</a>
|
||||
|
||||
@ -4,6 +4,14 @@ description: "Instructions to install Home Assistant on a Docker."
|
||||
redirect_from: /getting-started/installation-docker/
|
||||
---
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
These below instructions are for an installation of Home Assistant Core running in your own Docker environment, which you manage yourself.
|
||||
|
||||
For an installation of Home Assistant Supervised, which includes Home Assistant's add-on ecosystem, see the instructions for installing [Home Assistant Supervised on a generic Linux host](/hassio/installation/#alternative-install-home-assistant-supervised-on-a-generic-linux-host/).
|
||||
|
||||
</div>
|
||||
|
||||
## Platform Installation
|
||||
|
||||
Installation with Docker is straightforward. Adjust the following command so that `/PATH_TO_YOUR_CONFIG` points at the folder where you want to store your configuration and run it:
|
||||
|
||||
@ -6,15 +6,15 @@ redirect_from: /getting-started/updating/
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv/#upgrading-home-assistant).
|
||||
The upgrade process differs depending on the installation you have, so please review the documentation that is specific to your install: [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv/#upgrading-home-assistant).
|
||||
|
||||
</div>
|
||||
|
||||
Check what's new in the latest version and potentially impacts your system in [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). It is good practice to review these release notes and pay close attention to the **Breaking Changes** that are listed there. If you haven't done an update for a while, you should also check previous release notes as they can also contain relevant **Breaking Changes**. **Breaking Changes** may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check the log file in the [configuration](/docs/configuration/) directory, e.g., `.homeassistant/home-assistant.log`, for details about broken components.
|
||||
Check what's new in the latest version and potentially impacts your system in the [Home Assistant release notes](https://github.com/home-assistant/home-assistant/releases). It is good practice to review these release notes and pay close attention to the **Breaking Changes** that are listed there. If you haven't done an update for a while, you should also check previous release notes as they can also contain relevant **Breaking Changes**. These **Breaking Changes** may require configuration updates for your components. If you missed this and Home Assistant refuses to start, check the log file in the [configuration](/docs/configuration/) directory, e.g., `.homeassistant/home-assistant.log`, for details about broken components.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
To avoid permission errors, the upgrade must be run as the same user as the installation was completed, again review the documentation specific to your install [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv).
|
||||
To avoid permission errors, the upgrade must be run as the same user as was used during the initial installation, again review the documentation specific to your install [Home Assistant](/hassio/) or [Home Assistant Core](/docs/installation/virtualenv).
|
||||
|
||||
</div>
|
||||
|
||||
@ -36,7 +36,7 @@ For a Raspberry Pi Docker container, simply pull the latest one:
|
||||
sudo docker pull homeassistant/raspberrypi3-homeassistant:latest
|
||||
```
|
||||
|
||||
After updating, you must start/restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take considerable amount of time (i.e., minutes) depending on your device. This is because all requirements are updated as well.
|
||||
After updating, you must start/restart Home Assistant for the changes to take effect. This means that you will have to restart `hass` itself or the [autostarting](/docs/autostart/) daemon (if applicable). Startup can take a considerable amount of time (i.e., minutes) depending on your device. This is because all requirements are updated as well.
|
||||
|
||||
[BRUH automation](https://www.bruhautomation.io/) has created [a tutorial video](https://www.youtube.com/watch?v=tuG2rs1Cl2Y) explaining how to upgrade Home Assistant.
|
||||
|
||||
@ -50,7 +50,7 @@ pip3 install homeassistant==0.XX.X
|
||||
|
||||
#### Run the beta version
|
||||
|
||||
If you would like to test next release before anyone else, you can install the beta version released every two weeks:
|
||||
If you would like to test the next release before anyone else, you can install the beta version released every two weeks:
|
||||
|
||||
```bash
|
||||
pip3 install --pre --upgrade homeassistant
|
||||
|
||||
@ -1,20 +1,18 @@
|
||||
{%- assign github_main_repo = 'https://github.com/home-assistant/home-assistant/blob/dev/homeassistant' -%}
|
||||
<section class="aside-module grid__item one-whole lap-one-half">
|
||||
{%- include edit_github.html -%}
|
||||
|
||||
<div class='brand-logo-container section'>
|
||||
{%- if page.logo -%}
|
||||
<img src='/images/supported_brands/{{ page.logo }}' />
|
||||
{%- else -%}
|
||||
<img src='https://brands.home-assistant.io/{{ page.ha_domain }}/logo.png' srcset='https://brands.home-assistant.io/{{ page.ha_domain }}/logo@2x.png 2x' />
|
||||
{%- endif -%}
|
||||
</div>
|
||||
|
||||
{%- assign file_parts = page.url | split: '/' | last | split: '.' -%}
|
||||
{%- assign imp_name = file_parts | last -%}
|
||||
{%- assign imp_url = imp_name | prepend: '/components/' | append: '/' -%}
|
||||
|
||||
{%- if page.ha_domain -%}
|
||||
<div class="section">
|
||||
<kb-alert-link integration="{{ imp_name }}"></kb-alert-link>
|
||||
<kb-alert-link integration="{{ page.ha_domain }}"></kb-alert-link>
|
||||
</div>
|
||||
{%- endif -%}
|
||||
|
||||
{%- if page.ha_iot_class -%}
|
||||
<div class='section'>
|
||||
@ -50,9 +48,11 @@
|
||||
</div>
|
||||
{%- endif -%}
|
||||
|
||||
{%- if page.ha_domain -%}
|
||||
<div class='section'>
|
||||
Source: <a href='{{github_main_repo}}{{imp_url}}'>{{imp_url}}</a>
|
||||
Source: <a href='https://github.com/home-assistant/core/tree/dev/homeassistant/components/{{ page.ha_domain }}'>View on GitHub</a>
|
||||
</div>
|
||||
{%- endif -%}
|
||||
|
||||
{%- if page.ha_category.first -%}
|
||||
<div class='section'>
|
||||
|
||||
@ -98,9 +98,6 @@
|
||||
<li>
|
||||
<b>{% active_link /docs/frontend/ Frontend %}</b>
|
||||
<ul>
|
||||
<li>
|
||||
{% active_link /docs/frontend/mobile/ Android/iOS Homescreen %}
|
||||
</li>
|
||||
<li>
|
||||
{% active_link /docs/frontend/browsers/ Browser Compatibility List
|
||||
%}
|
||||
|
||||
@ -41,9 +41,6 @@
|
||||
<a href='/integrations/arduino/'>
|
||||
<img src='/images/supported_brands/arduino.png' alt="Arduino" />
|
||||
</a>
|
||||
<!-- <a href='/integrations/wink/'>
|
||||
<img src='/images/supported_brands/wink.png' alt="Wink" />
|
||||
</a> -->
|
||||
</div>
|
||||
|
||||
<p class='pull-right'><a href='/integrations/'>Browse all »</a></p>
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Abode
|
||||
description: Instructions on integrating Abode home security with Home Assistant.
|
||||
logo: abode.jpg
|
||||
ha_category:
|
||||
- Hub
|
||||
- Alarm
|
||||
@ -17,6 +16,7 @@ ha_iot_class: Cloud Push
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@shred86'
|
||||
ha_domain: abode
|
||||
---
|
||||
|
||||
The `abode` integration will allow users to integrate their Abode Home Security systems into Home Assistant and use its alarm system and sensors to automate their homes.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Acer Projector
|
||||
description: Instructions on how to integrate Acer Projector switches into Home Assistant.
|
||||
logo: acer.png
|
||||
ha_category:
|
||||
- Multimedia
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.19
|
||||
ha_domain: acer_projector
|
||||
---
|
||||
|
||||
The `acer_projector` switch platform allows you to control the state of RS232 connected projectors from [Acer](https://www.acer.com/).
|
||||
|
||||
@ -5,6 +5,7 @@ logo: actiontec.png
|
||||
ha_category:
|
||||
- Presence Detection
|
||||
ha_release: 0.7
|
||||
ha_domain: actiontec
|
||||
---
|
||||
|
||||
This platform allows you to detect presence by looking at connected devices to an [Actiontec](https://www.actiontec.com/) device.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: AdGuard Home
|
||||
description: Instructions on how to integrate AdGuard Home with Home Assistant.
|
||||
logo: adguard.png
|
||||
ha_category:
|
||||
- Network
|
||||
- Sensor
|
||||
@ -11,6 +10,7 @@ ha_iot_class: Local Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@frenck'
|
||||
ha_domain: adguard
|
||||
---
|
||||
|
||||
AdGuard Home is a network-wide ad- and tracker-blocking DNS server with parental
|
||||
|
||||
@ -11,6 +11,7 @@ ha_category:
|
||||
- Cover
|
||||
ha_release: '0.60'
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: ads
|
||||
---
|
||||
|
||||
The ADS (automation device specification) describes a device-independent and fieldbus independent interface for communication between [Beckhoff](https://www.beckhoff.com/) automation devices running [TwinCAT](https://www.beckhoff.hu/english.asp?twincat/default.htm) and other devices implementing this interface.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: AfterShip
|
||||
description: Instructions on how to set up AfterShip sensors within Home Assistant.
|
||||
logo: aftership.png
|
||||
ha_category:
|
||||
- Postal Service
|
||||
ha_release: 0.85
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: aftership
|
||||
---
|
||||
|
||||
The `aftership` platform allows one to track deliveries by [AfterShip](https://www.aftership.com), a service that supports 490+ couriers worldwide. It is free to use up to 100 tracked packages per month, after that there is a fee.
|
||||
|
||||
@ -2,6 +2,7 @@
|
||||
title: Air Quality
|
||||
description: Instructions on how to add air quality sensors with Home Assistant
|
||||
ha_release: 0.85
|
||||
ha_domain: air_quality
|
||||
---
|
||||
|
||||
The `air_quality` gather information about the air quality and pollution details.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: "Xiaomi Air Quality Monitor"
|
||||
description: "Instructions how to integrate your Xiaomi Mi Air Quality Monitor within Home Assistant."
|
||||
logo: xiaomi.png
|
||||
ha_category:
|
||||
- Health
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.102
|
||||
ha_domain: xiaomi_miio
|
||||
---
|
||||
|
||||
The `xiaomi_miio` sensor platform is observing your Xiaomi Mi Air Quality Monitor and reporting the air quality values.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Airly
|
||||
description: Instructions on how to integrate Airly within Home Assistant.
|
||||
logo: airly.png
|
||||
ha_category:
|
||||
- Health
|
||||
ha_release: 0.101
|
||||
@ -9,6 +8,7 @@ ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@bieniu'
|
||||
ha_domain: airly
|
||||
---
|
||||
|
||||
The `airly` integration uses the [Airly](https://airly.eu/) web service as a source for air quality data for your location.
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: AirVisual
|
||||
description: Instructions on how to use AirVisual data within Home Assistant
|
||||
logo: airvisual.jpg
|
||||
ha_category:
|
||||
- Health
|
||||
ha_release: 0.53
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@bachya'
|
||||
ha_domain: airvisual
|
||||
---
|
||||
|
||||
The `airvisual` sensor platform queries the [AirVisual](https://airvisual.com/) API for air quality data. Data can be collected via latitude/longitude or by city/state/country. The resulting information creates sensors for the Air Quality Index (AQI), the human-friendly air quality level, and the main pollutant of that area. Sensors that conform to either/both the [U.S. and Chinese air quality standards](https://www.clm.com/publication.cfm?ID=366) are created.
|
||||
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
- Cover
|
||||
ha_release: 0.75
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: aladdin_connect
|
||||
---
|
||||
|
||||
The `aladdin_connect` cover platform lets you control Genie Aladdin Connect garage doors through Home Assistant.
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: "IFTTT Alarm Control Panel"
|
||||
description: "Instructions on how to integrate IFTTT-controlled security systems into Home Assistant."
|
||||
logo: ifttt.png
|
||||
ha_category:
|
||||
- Alarm
|
||||
ha_release: 0.66
|
||||
ha_domain: ifttt
|
||||
---
|
||||
|
||||
The `ifttt` platform allows you to integrate security systems that have no open API but can be controlled through [IFTTT](https://ifttt.com/discover).
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Alarm Control Panel
|
||||
description: Instructions on how to integrate Alarm Control Panels into Home Assistant.
|
||||
logo: home-assistant.png
|
||||
ha_category:
|
||||
- Alarm
|
||||
ha_release: 0.7.3
|
||||
ha_quality_scale: internal
|
||||
ha_domain: alarm_control_panel
|
||||
---
|
||||
|
||||
Home Assistant can give you an interface which is similar to a classic alarm system.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: "MQTT Alarm Control Panel"
|
||||
description: "Instructions on how to integrate MQTT capable Alarm Panels into Home Assistant."
|
||||
logo: mqtt.png
|
||||
ha_category:
|
||||
- Alarm
|
||||
ha_release: 0.7.4
|
||||
ha_iot_class: Configurable
|
||||
ha_domain: mqtt
|
||||
---
|
||||
|
||||
The `mqtt` alarm panel platform enables the possibility to control MQTT capable alarm panels. The Alarm icon will change state after receiving a new state from `state_topic`. If these messages are published with *RETAIN* flag, the MQTT alarm panel will receive an instant state update after subscription and will start with the correct state. Otherwise, the initial state will be `unknown`.
|
||||
|
||||
@ -5,8 +5,8 @@ ha_category:
|
||||
- Alarm
|
||||
ha_release: 0.105
|
||||
ha_iot_class: "Local Push"
|
||||
logo: home-assistant.png
|
||||
ha_qa_scale: internal
|
||||
ha_domain: template
|
||||
---
|
||||
|
||||
The `template` integrations creates alarm control panels that combine integrations or adds pre-processing logic to actions.
|
||||
|
||||
@ -8,6 +8,7 @@ ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.43
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: alarmdecoder
|
||||
---
|
||||
|
||||
The `alarmdecoder` integration will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and its sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Nu Tech Software Solutions, known as the AlarmDecoder. The AlarmDecoder devices provide a serial, TCP/IP socket or USB interface to the alarm panel, where it emulates an alarm keypad.
|
||||
|
||||
@ -5,6 +5,7 @@ logo: alarmdotcom.png
|
||||
ha_category:
|
||||
- Alarm
|
||||
ha_release: 0.11
|
||||
ha_domain: alarmdotcom
|
||||
---
|
||||
|
||||
The `alarmdotcom` platform is consuming the information provided by [Alarm.com](https://www.alarm.com/).
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Alert
|
||||
description: Instructions on how to setup automatic alerts within Home Assistant.
|
||||
logo: home-assistant.png
|
||||
ha_category:
|
||||
- Automation
|
||||
ha_release: 0.38
|
||||
ha_quality_scale: internal
|
||||
ha_domain: alert
|
||||
---
|
||||
|
||||
The `alert` integration is designed to notify you when problematic issues arise.
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: "Amazon Alexa Flash Briefing"
|
||||
description: "Instructions on how to create your Flash Briefing skills with Home Assistant."
|
||||
logo: amazon-alexa.png
|
||||
ha_category:
|
||||
- Voice
|
||||
ha_release: "0.31"
|
||||
ha_domain: alexa
|
||||
---
|
||||
|
||||
## Flash Briefing Skills
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: "Amazon Alexa Custom Skill"
|
||||
description: "Instructions on how to build your Alexa/Amazon Echo custom commands to connect with Home Assistant."
|
||||
logo: amazon-alexa.png
|
||||
ha_category:
|
||||
- Voice
|
||||
ha_release: "0.10"
|
||||
ha_domain: alexa
|
||||
---
|
||||
|
||||
## I want to build custom commands to use with Echo
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Amazon Alexa
|
||||
description: Instructions on how to connect Alexa/Amazon Echo to Home Assistant.
|
||||
logo: amazon-alexa.png
|
||||
ha_category:
|
||||
- Voice
|
||||
featured: true
|
||||
@ -9,6 +8,7 @@ ha_release: '0.10'
|
||||
ha_codeowners:
|
||||
- '@home-assistant/cloud'
|
||||
- '@ochlocracy'
|
||||
ha_domain: alexa
|
||||
---
|
||||
|
||||
## Automatic setup via Home Assistant Cloud
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: "Amazon Alexa Smart Home Skill"
|
||||
description: "Instructions on how to build Smart Home skill to connect Amazon Alexa with Home Assistant."
|
||||
logo: amazon-alexa.png
|
||||
ha_category:
|
||||
- Voice
|
||||
ha_release: "0.54"
|
||||
ha_codeowners:
|
||||
- '@home-assistant/cloud'
|
||||
- '@ochlocracy'
|
||||
ha_domain: alexa
|
||||
---
|
||||
|
||||
Amazon Alexa provides a Smart Home API for richer home automation control without requiring the user to say the skill name, such as:
|
||||
@ -67,7 +67,7 @@ Steps to Integrate an Amazon Alexa Smart Home Skill with Home Assistant:
|
||||
|
||||
## Create an AWS Lambda Function
|
||||
|
||||
Alexa Smart Home skill will trigger a AWS Lambda function to process the request, we will write a small piece of code hosted as an Lambda function basically redirect the request to your Home Assistant instance, then Alexa integration integration in Home Assistant will process the request and send back the response. Your Lambda function will delivery the response back to Alexa.
|
||||
Alexa Smart Home skill will trigger a AWS Lambda function to process the request, we will write a small piece of code hosted as an Lambda function basically redirect the request to your Home Assistant instance, then Alexa integration integration in Home Assistant will process the request and send back the response. Your Lambda function will deliver the response back to Alexa.
|
||||
|
||||
<div class='info'>
|
||||
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Almond
|
||||
description: Instructions on how to setup Almond within Home Assistant.
|
||||
logo: almond.png
|
||||
ha_category:
|
||||
- Voice
|
||||
ha_iot_class: Local Polling
|
||||
@ -10,6 +9,7 @@ ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@gcampax'
|
||||
- '@balloob'
|
||||
ha_domain: almond
|
||||
---
|
||||
|
||||
[Almond](https://almond.stanford.edu/) is an open, privacy-preserving virtual assistant by [Stanford Open Virtual Assistant Lab](https://oval.cs.stanford.edu/). It allows you, among other things, to control Home Assistant using natural language. Once installed, it will be available on Lovelace via the microphone icon in the top right.
|
||||
|
||||
@ -8,6 +8,7 @@ ha_iot_class: Cloud Polling
|
||||
ha_release: '0.60'
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: alpha_vantage
|
||||
---
|
||||
|
||||
The `alpha_vantage` sensor platform uses [Alpha Vantage](https://www.alphavantage.co) to monitor the stock market. This platform also provides detail about exchange rates.
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Amazon Polly
|
||||
description: Instructions on how to setup Amazon Polly with Home Assistant.
|
||||
logo: polly.png
|
||||
ha_category:
|
||||
- Text-to-speech
|
||||
ha_release: 0.37
|
||||
ha_codeowners:
|
||||
- '@robbiet480'
|
||||
ha_domain: amazon_polly
|
||||
---
|
||||
|
||||
The `amazon_polly` text-to-speech platform that works with [Amazon Polly](https://aws.amazon.com/polly/) to create the spoken output.
|
||||
|
||||
@ -8,6 +8,7 @@ ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@danielhiversen'
|
||||
ha_domain: ambiclimate
|
||||
---
|
||||
|
||||
Integrates [Ambiclimate](https://ambiclimate.com/) Air Conditioning controller into Home Assistant.
|
||||
|
||||
@ -9,6 +9,7 @@ ha_iot_class: Cloud Push
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@bachya'
|
||||
ha_domain: ambient_station
|
||||
---
|
||||
|
||||
The `Ambient Weather Station` integration retrieves local weather information
|
||||
|
||||
@ -11,6 +11,7 @@ ha_iot_class: Local Polling
|
||||
ha_release: 0.49
|
||||
ha_codeowners:
|
||||
- '@pnbruckner'
|
||||
ha_domain: amcrest
|
||||
---
|
||||
|
||||
The `amcrest` camera platform allows you to integrate your [Amcrest](https://amcrest.com/) IP camera in Home Assistant.
|
||||
|
||||
@ -7,6 +7,7 @@ ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.92
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: ampio
|
||||
---
|
||||
|
||||
The `ampio` air quality platform will query the open data API of [ampio.pl](http://smog1.ampio.pl:3050/) to monitor air quality sensor station.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Android IP Webcam
|
||||
description: Connect Android devices as an IP webcam to Home Assistant
|
||||
logo: android_ip_webcam.png
|
||||
ha_category:
|
||||
- Hub
|
||||
- Binary Sensor
|
||||
@ -10,6 +9,7 @@ ha_category:
|
||||
- Switch
|
||||
ha_release: '0.40'
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: android_ip_webcam
|
||||
---
|
||||
|
||||
The `android_ip_webcam` integration turns any Android phone or tablet into a network camera with multiple viewing options.
|
||||
|
||||
@ -8,6 +8,7 @@ ha_release: 0.7.6
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@JeffLIrion'
|
||||
ha_domain: androidtv
|
||||
---
|
||||
|
||||
The `androidtv` platform allows you to control an Android TV device or [Amazon Fire TV](https://www.amazon.com/b/?node=8521791011) device.
|
||||
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
- Switch
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: '0.30'
|
||||
ha_domain: anel_pwrctrl
|
||||
---
|
||||
|
||||
The `anel_pwrctrl` switch platform allows you to control [ANEL PwrCtrl](https://anel-elektronik.de/SITE/produkte/produkte.htm) devices.
|
||||
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
- Media Player
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.37
|
||||
ha_domain: anthemav
|
||||
---
|
||||
|
||||
Both [Anthem]'s current and last generation of A/V Receivers and Processors support IP-based, network control. This Home Assistant platform adds proper "local push" support for any of these receivers on your network.
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Apache Kafka
|
||||
description: Send data and events to Apache Kafka.
|
||||
logo: apache_kafka.png
|
||||
ha_category:
|
||||
- History
|
||||
ha_release: 0.97
|
||||
ha_codeowners:
|
||||
- '@bachya'
|
||||
ha_domain: apache_kafka
|
||||
---
|
||||
|
||||
The `apache_kafka` integration sends all state changes to a
|
||||
|
||||
@ -8,6 +8,7 @@ ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.13
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: apcupsd
|
||||
---
|
||||
|
||||
[Apcupsd](http://www.apcupsd.org/) status information can be integrated into Home Assistant when the Network Information Server (NIS) [is configured](http://www.apcupsd.org/manual/manual.html#nis-server-client-configuration-using-the-net-driver) on the APC device.
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Home Assistant API
|
||||
description: Instructions on how to setup the RESTful API within Home Assistant.
|
||||
logo: home-assistant.png
|
||||
ha_category:
|
||||
- Other
|
||||
ha_release: 0.7
|
||||
ha_quality_scale: internal
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_domain: api
|
||||
---
|
||||
|
||||
The `api` integration exposes a RESTful API and allows one to interact with a Home Assistant instance that is running headless. This integration depends on the [`http` integration](/integrations/http/).
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: Apple Push Notification Service (APNS)
|
||||
description: Instructions on how to add APNS notifications to Home Assistant.
|
||||
logo: apple.png
|
||||
ha_category:
|
||||
- Notifications
|
||||
ha_release: 0.31
|
||||
ha_domain: apns
|
||||
---
|
||||
|
||||
The `apns` platform uses the Apple Push Notification service (APNS) to deliver notifications from Home Assistant.
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Apple TV
|
||||
description: Instructions on how to integrate Apple TV devices into Home Assistant.
|
||||
logo: apple.png
|
||||
ha_category:
|
||||
- Multimedia
|
||||
- Media Player
|
||||
- Remote
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.49
|
||||
ha_domain: apple_tv
|
||||
---
|
||||
|
||||
The `apple_tv` platform allows you to control an Apple TV (3rd and 4th generation). See the [remote platform](/integrations/apple_tv#remote) if you want to send remote control buttons, e.g., arrow keys.
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Apprise
|
||||
description: Instructions on how to add Apprise notifications to Home Assistant.
|
||||
logo: apprise.png
|
||||
ha_category:
|
||||
- Notifications
|
||||
ha_release: 0.101
|
||||
ha_codeowners:
|
||||
- '@caronc'
|
||||
ha_domain: apprise
|
||||
---
|
||||
|
||||
The [Apprise service](https://github.com/caronc/apprise/) is an all-in-one solution to open up Home Assistant to _just about_ every Notification platform (such as Amazon SNS, Discord, Telegram, Slack, MSTeams, Twilio, etc.)
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: APRS
|
||||
description: Instructions on how to use APRS to track devices in Home Assistant.
|
||||
logo: aprs.png
|
||||
ha_release: 0.95
|
||||
ha_category: Presence Detection
|
||||
ha_iot_class: Cloud Push
|
||||
ha_codeowners:
|
||||
- '@PhilRW'
|
||||
ha_domain: aprs
|
||||
---
|
||||
|
||||
The `aprs` [(Automatic Packet Reporting System)](https://en.wikipedia.org/wiki/Automatic_Packet_Reporting_System) device tracker integration connects to the [APRS-IS](http://aprs-is.net/) network for tracking amateur radio devices.
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: AquaLogic
|
||||
description: Instructions on how to integrate an AquaLogic controller within Home Assistant.
|
||||
logo: hayward.png
|
||||
ha_category:
|
||||
- Hub
|
||||
- Sensor
|
||||
- Switch
|
||||
ha_release: '0.80'
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: aqualogic
|
||||
---
|
||||
|
||||
The AquaLogic integration provides connectivity to a Hayward/Goldline AquaLogic/ProLogic pool controller. Note that an RS-485 to Ethernet adapter connected to the pool controller is required.
|
||||
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
- Media Player
|
||||
ha_release: 0.35
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: aquostv
|
||||
---
|
||||
|
||||
The `aquostv` platform allows you to control a [Sharp Aquos TV](http://www.sharp-world.com/aquos/en/index.html).
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Arcam FMJ Receivers
|
||||
description: Instructions on how to integrate Arcam FMJ Receivers into Home Assistant.
|
||||
logo: arcam.svg
|
||||
ha_category: Media Player
|
||||
ha_release: 0.96
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@elupus'
|
||||
ha_domain: arcam_fmj
|
||||
---
|
||||
|
||||
The `arcam_fmj` integration allows you to control [Arcam FMJ Receveivers](https://www.arcam.co.uk/range/fmj.htm) from Home Assistant.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Arduino
|
||||
description: Instructions on how to setup an Arduino boards within Home Assistant.
|
||||
logo: arduino.png
|
||||
ha_category:
|
||||
- DIY
|
||||
- Sensor
|
||||
@ -10,6 +9,7 @@ ha_release: pre 0.7
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: arduino
|
||||
---
|
||||
|
||||
The [Arduino](https://www.arduino.cc/) device family are microcontroller boards that are often based on the ATmega328 chip. They come with digital input/output pins (some can be used as PWM outputs), analog inputs, and a USB connection.
|
||||
|
||||
@ -11,6 +11,7 @@ ha_iot_class: Local Polling
|
||||
ha_release: 0.9
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: arest
|
||||
---
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -9,6 +9,7 @@ ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.46
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: arlo
|
||||
---
|
||||
|
||||
The `arlo` implementation allows you to integrate your [Arlo](https://arlo.netgear.com/) devices in Home Assistant.
|
||||
|
||||
@ -5,6 +5,7 @@ logo: aruba.png
|
||||
ha_category:
|
||||
- Presence Detection
|
||||
ha_release: 0.7
|
||||
ha_domain: aruba
|
||||
---
|
||||
|
||||
This platform allows you to detect presence by looking at connected devices to an [Aruba Instant](https://www.arubanetworks.com/products/networking/aruba-instant/) device.
|
||||
|
||||
@ -5,6 +5,7 @@ ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.31
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: arwn
|
||||
---
|
||||
|
||||
The `arwn` sensor platform is a client for the [Ambient Radio Weather Network](https://github.com/sdague/arwn) project. This collects weather station data and makes it available in an MQTT subtree.
|
||||
|
||||
@ -5,6 +5,7 @@ logo: asterisk.png
|
||||
ha_category:
|
||||
- Mailbox
|
||||
ha_release: 0.79
|
||||
ha_domain: asterisk_cdr
|
||||
---
|
||||
|
||||
The Asterisk Call Data Recorder provides access to Asterisk call logs on the Asterisk PBX server. This mailbox is enabled automatically through the [Asterisk Voicemail integration](/integrations/asterisk_mbox/) configuration if the `asterisk_mbox_server` is configured to provide CDR data. More information on configuring the server can be found in the [Asterisk PBX configuration guide](/docs/asterisk_mbox/).
|
||||
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
- Mailbox
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.51
|
||||
ha_domain: asterisk_mbox
|
||||
---
|
||||
|
||||
The `asterisk_mbox` Asterisk Voicemail integration for Home Assistant allows you to view, listen to, and delete voicemails from an Asterisk voicemail mailbox. The integration includes a panel on the frontend that provides caller-id and speech-to-text transcription (using Google's API) of messages in addition to playback and message deletion. There is also an included sensor that indicates of the number of available messages. There is no requirement that the Asterisk PBX and Home Assistant are running on the same machine.
|
||||
|
||||
@ -10,6 +10,7 @@ ha_release: 0.83
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@kennedyshead'
|
||||
ha_domain: asuswrt
|
||||
---
|
||||
|
||||
The `asuswrt` integration is the main integration to connect to a [ASUSWRT](https://event.asus.com/2013/nw/ASUSWRT/) based router.
|
||||
|
||||
@ -7,6 +7,7 @@ ha_category:
|
||||
ha_release: 0.103
|
||||
ha_codeowners:
|
||||
- '@mtdcr'
|
||||
ha_domain: aten_pe
|
||||
---
|
||||
|
||||
The `aten_pe` integration lets you control [ATEN Rack PDUs](https://www.aten.com/eu/en/products/energy-intelligence-pduupsracks/rack-pdu/) from Home Assistant.
|
||||
|
||||
@ -9,6 +9,7 @@ ha_category:
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@baqs'
|
||||
ha_domain: atome
|
||||
---
|
||||
|
||||
The `atome` sensor platform is retrieving the consumption of your home from the [Direct Energy Atome electric meter](https://total.direct-energie.com/particuliers/electricite/compteur-linky/atome).
|
||||
|
||||
@ -13,6 +13,7 @@ ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
ha_codeowners:
|
||||
- '@bdraco'
|
||||
ha_domain: august
|
||||
---
|
||||
|
||||
The `august` integration allows you to integrate your [August](https://august.com/) devices in Home Assistant.
|
||||
|
||||
@ -4,7 +4,7 @@ description: Know when auroras might be visible at your location
|
||||
ha_category:
|
||||
- Environment
|
||||
ha_release: 0.39
|
||||
logo: noaa.png
|
||||
ha_domain: aurora
|
||||
---
|
||||
|
||||
The `aurora` platform uses the [NOAA Aurora Forecast](https://www.swpc.noaa.gov/products/aurora-30-minute-forecast) service to let you know if an aurora might be visible at your home location in the next 30 minutes, based off of current solar flare activity.
|
||||
|
||||
@ -9,6 +9,7 @@ ha_release: 0.96
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@davet2001'
|
||||
ha_domain: aurora_abb_powerone
|
||||
---
|
||||
|
||||
This implements a direct RS485 connection to a solar inverter in the
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Auth
|
||||
description: This integration is responsible for providing the authentication endpoints.
|
||||
logo: home-assistant.png
|
||||
ha_category:
|
||||
- Other
|
||||
ha_release: 0.73
|
||||
ha_quality_scale: internal
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_domain: auth
|
||||
---
|
||||
|
||||
This integration creates the endpoints for the [authentication system](/docs/authentication/) that is built into Home Assistant.
|
||||
|
||||
@ -8,6 +8,7 @@ ha_release: 0.28
|
||||
ha_iot_class: Cloud Push
|
||||
ha_codeowners:
|
||||
- '@armills'
|
||||
ha_domain: automatic
|
||||
---
|
||||
|
||||
The `automatic` device tracker platform offers presence detection by retrieving your car's information from the [Automatic](https://automatic.com/) cloud service.
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Automation
|
||||
description: Instructions on how to setup automation within Home Assistant.
|
||||
logo: home-assistant.png
|
||||
ha_category:
|
||||
- Automation
|
||||
ha_release: 0.7
|
||||
ha_quality_scale: internal
|
||||
ha_codeowners:
|
||||
- '@home-assistant/core'
|
||||
ha_domain: automation
|
||||
---
|
||||
|
||||
Please see the [docs section](/docs/automation/) for in-depth
|
||||
|
||||
@ -8,6 +8,7 @@ ha_release: 0.97
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@pattyland'
|
||||
ha_domain: avea
|
||||
---
|
||||
|
||||
[Elgato Avea](https://www.elgato.com/en/news/elgato-avea-transform-your-home) is a Bluetooth light bulb that is no longer supported by the manufacturer. The `avea` integration allows you to control all your Avea bulbs with Home Assistant.
|
||||
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
ha_iot_class: Assumed State
|
||||
logo: avi-on.png
|
||||
ha_release: 0.37
|
||||
ha_domain: avion
|
||||
---
|
||||
|
||||
Support for the Avi-on Bluetooth dimmer switch [Avi-on](https://avi-on.com/).
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Awair
|
||||
description: Instructions on how to setup Awair devices in Home Assistant.
|
||||
logo: awair.jpg
|
||||
ha_category:
|
||||
- Health
|
||||
ha_release: 0.84
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@danielsjf'
|
||||
ha_domain: awair
|
||||
---
|
||||
|
||||
The `awair` sensor platform will fetch data from your [Awair device(s)](https://getawair.com).
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: Amazon Web Services (AWS)
|
||||
description: Instructions on how to integrate Amazon Web Services with Home Assistant.
|
||||
logo: aws.png
|
||||
ha_category:
|
||||
- Notifications
|
||||
ha_release: '0.91'
|
||||
ha_codeowners:
|
||||
- '@awarecan'
|
||||
- '@robbiet480'
|
||||
ha_domain: aws
|
||||
---
|
||||
|
||||
The `aws` integration provides a single place to interact with [Amazon Web Services](https://aws.amazon.com/). Currently it provides a notification platform that can send a message to [AWS SQS](https://aws.amazon.com/sqs/), [AWS SNS](https://aws.amazon.com/sns/), or invoke [AWS Lambda](https://aws.amazon.com/lambda/) functions.
|
||||
|
||||
@ -11,6 +11,7 @@ ha_release: 0.45
|
||||
ha_iot_class: Local Push
|
||||
ha_codeowners:
|
||||
- '@kane610'
|
||||
ha_domain: axis
|
||||
---
|
||||
|
||||
[Axis Communications](https://www.axis.com/) devices are surveillance cameras, speakers, access control and other security-related network connected hardware. Event API works with firmware 5.50 and newer.
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Azure Event Hub
|
||||
description: Setup for Azure Event Hub integration
|
||||
logo: azure_event_hub.svg
|
||||
ha_category:
|
||||
- History
|
||||
ha_release: 0.94
|
||||
ha_codeowners:
|
||||
- '@eavanvalkenburg'
|
||||
ha_domain: azure_event_hub
|
||||
---
|
||||
|
||||
The `Azure Event Hub` integration allows you to hook into the Home Assistant event bus and send events to [Azure Event Hub](https://azure.microsoft.com/en-us/services/event-hubs/) or to a [Azure IoT Hub](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-read-builtin).
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Azure Service Bus
|
||||
description: Setup for Azure Service Bus integration
|
||||
logo: azure_service_bus.svg
|
||||
ha_category:
|
||||
- Notifications
|
||||
ha_release: 0.102
|
||||
ha_codeowners:
|
||||
- '@hfurubotten'
|
||||
ha_domain: azure_service_bus
|
||||
---
|
||||
|
||||
The `Azure Service Bus` integration allows you to send messages to [Azure Service Bus](https://azure.microsoft.com/en-us/services/service-bus/) from within Home Assistant.
|
||||
|
||||
@ -5,6 +5,7 @@ logo: baiducloud.png
|
||||
ha_category:
|
||||
- Text-to-speech
|
||||
ha_release: 0.59
|
||||
ha_domain: baidu
|
||||
---
|
||||
|
||||
The `baidu` text-to-speech platform uses [Baidu TTS engine](https://cloud.baidu.com/product/speech/tts) to read a text with natural sounding voices.
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Bayesian
|
||||
description: Instructions on how to integrate threshold Bayesian sensors into Home Assistant.
|
||||
logo: home-assistant.png
|
||||
ha_category:
|
||||
- Utility
|
||||
ha_iot_class: Local Polling
|
||||
ha_release: 0.53
|
||||
ha_quality_scale: internal
|
||||
ha_domain: bayesian
|
||||
---
|
||||
|
||||
The `bayesian` binary sensor platform observes the state from multiple sensors and uses [Bayes' rule](https://en.wikipedia.org/wiki/Bayes%27_theorem) to estimate the probability that an event has occurred given the state of the observed sensors. If the estimated posterior probability is above the `probability_threshold`, the sensor is `on` otherwise it is `off`.
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: BeagleBone Black GPIO
|
||||
description: Instructions on how to integrate the GPIO capability of a BeagleBone Black into Home Assistant.
|
||||
logo: beaglebone-black.png
|
||||
ha_category:
|
||||
- DIY
|
||||
- Binary Sensor
|
||||
- Switch
|
||||
ha_release: 0.36
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: bbb_gpio
|
||||
---
|
||||
|
||||
The `bbb_gpio` integration is the base for all [BeagleBone Black](https://beagleboard.org/black) related GPIO platforms in Home Assistant.
|
||||
|
||||
@ -8,6 +8,7 @@ ha_category:
|
||||
- Presence Detection
|
||||
ha_release: 0.31
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: bbox
|
||||
---
|
||||
|
||||
The `bbox` platform uses the [Bbox Modem Router](https://www.bouyguestelecom.fr/offres-internet/bbox-fit) from the French Internet provider Bouygues Telecom. Sensors are mainly bandwidth measures.
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
---
|
||||
title: BeeWi SmartClim BLE sensor
|
||||
description: Instructions on how to integrate MBeeWi SmartClim BLE sensor with Home Assistant.
|
||||
logo: beewi_by_otio.png
|
||||
ha_category:
|
||||
- Sensor
|
||||
ha_release: 0.99
|
||||
ha_iot_class: Local Polling
|
||||
ha_codeowners:
|
||||
- '@alemuro'
|
||||
ha_domain: beewi_smartclim
|
||||
---
|
||||
|
||||
The `beewi_smartclim` sensor platform allows one to monitor room or external temperature and humidity. The [BeeWi SmartClim BLE](http://www.bee-wi.com/produits/capteurs/capteur-de-temperature/) is a Bluetooth Low Energy sensor device that monitors temperature from a room or a garden from your smartphone by using an APP. Use this integration to track these metrics from any location thanks to Home Assistant, as well as to create some automation scripts based on your room's temperature.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: BH1750
|
||||
description: Instructions on how to integrate a BH1750 light sensor into Home Assistant.
|
||||
logo: raspberry-pi.png
|
||||
ha_category:
|
||||
- DIY
|
||||
ha_release: 0.48
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: bh1750
|
||||
---
|
||||
|
||||
The `bh1750` sensor platform allows you to read the ambient light level in Lux from a [BH1750FVI sensor](https://www.mouser.com/ds/2/348/bh1750fvi-e-186247.pdf) connected via [I2c](https://en.wikipedia.org/wiki/I²C) bus (SDA, SCL pins). It allows you to use all the resolution modes of the sensor described in its datasheet.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: "KNX Binary Sensor"
|
||||
description: "Instructions on how to setup the KNX binary sensors within Home Assistant."
|
||||
logo: knx.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
ha_release: 0.24
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: knx
|
||||
---
|
||||
|
||||
<div class='note'>
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Binary Sensor
|
||||
description: Instructions on how-to setup binary sensors with Home Assistant.
|
||||
logo: home-assistant.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
ha_release: 0.9
|
||||
ha_quality_scale: internal
|
||||
ha_domain: binary_sensor
|
||||
---
|
||||
|
||||
Binary sensors gather information about the state of devices which have a "digital" return value (either 1 or 0). These can be switches, contacts, pins, etc. These sensors only have two states: **0/off/low/closed/false** and **1/on/high/open/true**. Knowing that there are only two states allows Home Assistant to represent these sensors in a better way in the frontend according to their functionality.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: "Modbus Binary Sensor"
|
||||
description: "Instructions on how to set up Modbus binary sensors within Home Assistant."
|
||||
logo: modbus.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
ha_release: 0.28
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: modbus
|
||||
---
|
||||
|
||||
The `modbus` binary sensor allows you to gather data from [Modbus](http://www.modbus.org/) coils.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: "MQTT Binary Sensor"
|
||||
description: "Instructions on how to integrate MQTT binary sensors within Home Assistant."
|
||||
logo: mqtt.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
ha_release: 0.9
|
||||
ha_iot_class: Configurable
|
||||
ha_domain: mqtt
|
||||
---
|
||||
|
||||
The `mqtt` binary sensor platform uses an MQTT message payload to set the binary sensor to one of two states: `on` or `off`.
|
||||
|
||||
@ -1,12 +1,12 @@
|
||||
---
|
||||
title: "MySensors Binary Sensor"
|
||||
description: "Instructions on how to integrate MySensors binary sensors into Home Assistant."
|
||||
logo: mysensors.png
|
||||
ha_category:
|
||||
- DIY
|
||||
- Binary Sensor
|
||||
ha_release: 0.14
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: mysensors
|
||||
---
|
||||
|
||||
Integrates MySensors binary sensors into Home Assistant. See the [main integration](/integrations/mysensors/) for configuration instructions.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: "RESTful Binary Sensor"
|
||||
description: "Instructions on how to integrate REST binary sensors into Home Assistant."
|
||||
logo: restful.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
ha_release: "0.10"
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: rest
|
||||
---
|
||||
|
||||
The `rest` binary sensor platform is consuming a given endpoint which is exposed
|
||||
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
- Binary Sensor
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.81
|
||||
ha_domain: rflink
|
||||
---
|
||||
|
||||
The `rflink` integration supports devices that use [RFLink gateway firmware](http://www.nemcon.nl/blog2/), for example the [Nodo RFLink Gateway](https://www.nodo-shop.nl/nl/21-rflink-gateway). RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
---
|
||||
title: "RFXtrx Binary Sensor"
|
||||
description: "Instructions on how to integrate RFXtrx binary sensors into Home Assistant."
|
||||
logo: rfxtrx.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
ha_release: 0.48
|
||||
ha_domain: rfxtrx
|
||||
---
|
||||
|
||||
The `rfxtrx` platform support binary sensors that
|
||||
|
||||
@ -5,8 +5,8 @@ ha_category:
|
||||
- Binary Sensor
|
||||
ha_release: 0.12
|
||||
ha_iot_class: Local Push
|
||||
logo: home-assistant.png
|
||||
ha_quality_scale: internal
|
||||
ha_domain: template
|
||||
---
|
||||
|
||||
The `template` platform supports binary sensors which get their values from
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: "Xiaomi Binary Sensor"
|
||||
description: "Instructions on how to setup the Xiaomi binary sensors within Home Assistant."
|
||||
logo: xiaomi.png
|
||||
ha_category:
|
||||
- Binary Sensor
|
||||
ha_release: "0.50"
|
||||
ha_iot_class: Local Push
|
||||
ha_domain: xiaomi_aqara
|
||||
---
|
||||
|
||||
The `xiaomi aqara` binary sensor platform allows you to get data from your [Xiaomi](https://www.mi.com/en/) binary sensors.
|
||||
|
||||
@ -8,6 +8,7 @@ ha_release: pre 0.7
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@fabaff'
|
||||
ha_domain: bitcoin
|
||||
---
|
||||
|
||||
The `bitcoin` sensor platform displays various details about the [Bitcoin](https://bitcoin.org) network.
|
||||
|
||||
@ -9,6 +9,7 @@ ha_iot_class: Cloud Polling
|
||||
ha_release: 0.93
|
||||
ha_codeowners:
|
||||
- '@UgaitzEtxebarria'
|
||||
ha_domain: bizkaibus
|
||||
---
|
||||
|
||||
The `bizkaibus` sensor will give you the time until the next bus in the selected stop.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Monoprice Blackbird Matrix Switch
|
||||
description: Instructions on how to integrate Monoprice Blackbird 4k 8x8 HDBaseT Matrix Switch into Home Assistant.
|
||||
logo: monoprice.svg
|
||||
ha_category:
|
||||
- Media Player
|
||||
ha_release: 0.68
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: blackbird
|
||||
---
|
||||
|
||||
The `blackbird` platform allows you to control [Monoprice Blackbird Matrix Switch](https://www.monoprice.com/product?p_id=21819) using a serial connection.
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Blink
|
||||
description: Instructions for how to integrate Blink camera/security system within Home Assistant.
|
||||
logo: blink.png
|
||||
ha_category:
|
||||
- Hub
|
||||
- Alarm
|
||||
@ -12,6 +11,7 @@ ha_release: '0.40'
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_codeowners:
|
||||
- '@fronzbot'
|
||||
ha_domain: blink
|
||||
---
|
||||
|
||||
The `blink` integration lets you view camera images and motion events from [Blink](https://blinkforhome.com/) camera and security systems.
|
||||
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
- DIY
|
||||
ha_release: 0.7.5
|
||||
ha_iot_class: Local Polling
|
||||
ha_domain: blinksticklight
|
||||
---
|
||||
|
||||
The `blinkstick` platform lets you control your [Blinkstick](https://www.blinkstick.com/) lights from within Home Assistant.
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
---
|
||||
title: Blinkt!
|
||||
description: Instructions on how to setup Blinkt! RGB LED lights within Home Assistant.
|
||||
logo: raspberry-pi.png
|
||||
ha_category:
|
||||
- DIY
|
||||
ha_iot_class: Local Push
|
||||
ha_release: 0.44
|
||||
ha_domain: blinkt
|
||||
---
|
||||
|
||||
The `blinkt` light platform lets you control the [Blinkt!](https://shop.pimoroni.com/products/blinkt) board, featuring eight super-bright RGB LEDs.
|
||||
|
||||
@ -6,6 +6,7 @@ ha_category:
|
||||
- Finance
|
||||
ha_release: 0.47
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_domain: blockchain
|
||||
---
|
||||
|
||||
The `Blockchain` sensor platform displays Bitcoin wallet balances from [blockchain.com](https://blockchain.com).
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user