mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 09:17:06 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
021550a553
@ -63,7 +63,7 @@ GEM
|
||||
kramdown-parser-gfm (1.1.0)
|
||||
kramdown (~> 2.0)
|
||||
liquid (4.0.3)
|
||||
listen (3.2.1)
|
||||
listen (3.3.0)
|
||||
rb-fsevent (~> 0.10, >= 0.10.3)
|
||||
rb-inotify (~> 0.9, >= 0.9.10)
|
||||
mercenary (0.4.0)
|
||||
@ -86,7 +86,7 @@ GEM
|
||||
rb-inotify (0.10.1)
|
||||
ffi (~> 1.0)
|
||||
rexml (3.2.4)
|
||||
rouge (3.24.0)
|
||||
rouge (3.25.0)
|
||||
ruby-enum (0.8.0)
|
||||
i18n
|
||||
ruby2_keywords (0.0.2)
|
||||
|
||||
@ -50,7 +50,7 @@ $primary-color: #049cdb;
|
||||
}
|
||||
|
||||
.hero {
|
||||
background-color: #038FC7;
|
||||
background-color: #038fc7;
|
||||
padding-bottom: 0;
|
||||
|
||||
.lead {
|
||||
@ -69,14 +69,15 @@ $primary-color: #049cdb;
|
||||
.material-card {
|
||||
background-color: #fefefe;
|
||||
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);
|
||||
|
||||
h1 {
|
||||
font-family: Roboto, Noto, sans-serif;
|
||||
-webkit-font-smoothing: antialiased;
|
||||
font-size: 24px;
|
||||
font-weight: 400;
|
||||
letter-spacing: -.012em;
|
||||
letter-spacing: -0.012em;
|
||||
line-height: 40px;
|
||||
color: #212121;
|
||||
padding: 20px 16px 12px;
|
||||
@ -124,14 +125,14 @@ $primary-color: #049cdb;
|
||||
}
|
||||
|
||||
.highlight-blog-post {
|
||||
font-size: 2.0rem;
|
||||
font-size: 2rem;
|
||||
line-height: 1.15;
|
||||
padding: 15px;
|
||||
display: block;
|
||||
text-decoration: none;
|
||||
color: white;
|
||||
transition: background-color .5s;
|
||||
background-color: #038FC7;
|
||||
transition: background-color 0.5s;
|
||||
background-color: #038fc7;
|
||||
|
||||
&.large {
|
||||
font-size: 2.25rem;
|
||||
@ -139,7 +140,7 @@ $primary-color: #049cdb;
|
||||
}
|
||||
|
||||
&:hover {
|
||||
background-color: lighten(#038FC7, 10%);
|
||||
background-color: lighten(#038fc7, 10%);
|
||||
}
|
||||
}
|
||||
|
||||
@ -152,7 +153,7 @@ $primary-color: #049cdb;
|
||||
|
||||
.caption {
|
||||
padding: 16px 12px 12px;
|
||||
background-color: rgba(0, 0, 0, .54);
|
||||
background-color: rgba(0, 0, 0, 0.54);
|
||||
color: white;
|
||||
border-bottom-left-radius: 2px;
|
||||
border-bottom-right-radius: 2px;
|
||||
@ -219,7 +220,7 @@ dt:hover a.title-link {
|
||||
font-family: "FontAwesome";
|
||||
font-size: 15px;
|
||||
color: #999;
|
||||
content: "\f0c1"
|
||||
content: "\f0c1";
|
||||
}
|
||||
}
|
||||
|
||||
@ -259,13 +260,16 @@ dt:hover a.title-link {
|
||||
}
|
||||
}
|
||||
|
||||
article.post, article.page, article.listing {
|
||||
article.post,
|
||||
article.page,
|
||||
article.listing {
|
||||
font-size: 1.125em;
|
||||
line-height: 1.6;
|
||||
|
||||
img, table {
|
||||
img,
|
||||
table {
|
||||
border-radius: 3px;
|
||||
box-shadow: rgba(0,0,0,0.06) 0 0 10px;
|
||||
box-shadow: rgba(0, 0, 0, 0.06) 0 0 10px;
|
||||
vertical-align: middle;
|
||||
}
|
||||
|
||||
@ -274,17 +278,18 @@ article.post, article.page, article.listing {
|
||||
box-shadow: none;
|
||||
}
|
||||
|
||||
& > table, & > .entry-content > table {
|
||||
background-color: #F3FCF5;
|
||||
& > table,
|
||||
& > .entry-content > table {
|
||||
background-color: #f3fcf5;
|
||||
}
|
||||
|
||||
p.img {
|
||||
background-color: #FFF;
|
||||
background-color: #fff;
|
||||
border-radius: 5px;
|
||||
text-align: center;
|
||||
padding-bottom: 3px;
|
||||
font-size: .9rem;
|
||||
box-shadow: rgba(0,0,0,0.06) 0 0 10px;
|
||||
font-size: 0.9rem;
|
||||
box-shadow: rgba(0, 0, 0, 0.06) 0 0 10px;
|
||||
|
||||
img {
|
||||
display: block;
|
||||
@ -314,7 +319,6 @@ article.post, article.page, article.listing {
|
||||
}
|
||||
|
||||
h1 {
|
||||
|
||||
}
|
||||
|
||||
h2 {
|
||||
@ -352,14 +356,15 @@ article.post, article.page, article.listing {
|
||||
}
|
||||
}
|
||||
|
||||
p.note, div.note {
|
||||
p.note,
|
||||
div.note {
|
||||
position: relative;
|
||||
|
||||
background: #e7f2fa;
|
||||
|
||||
padding: 40px 12px 6px 12px;
|
||||
margin-bottom: 24px;
|
||||
box-shadow: rgba(0,0,0,0.06) 0 0 10px;
|
||||
box-shadow: rgba(0, 0, 0, 0.06) 0 0 10px;
|
||||
|
||||
p {
|
||||
margin-bottom: 0px;
|
||||
@ -367,7 +372,7 @@ p.note, div.note {
|
||||
|
||||
&::before {
|
||||
font-family: "FontAwesome", sans-serif;
|
||||
content: "\f05a" " Note " attr(data-title);
|
||||
content: "\f05a"" Note " attr(data-title);
|
||||
background-color: #6ab0de;
|
||||
color: white;
|
||||
font-weight: bold;
|
||||
@ -385,14 +390,13 @@ p.note, div.note {
|
||||
}
|
||||
|
||||
&.warning {
|
||||
background-color: #F7F9E1;
|
||||
background-color: #f7f9e1;
|
||||
|
||||
&::before {
|
||||
background-color: rgb(187, 185, 13);;
|
||||
content: "\f071" " Warning " attr(data-title);
|
||||
background-color: rgb(187, 185, 13);
|
||||
content: "\f071"" Warning " attr(data-title);
|
||||
}
|
||||
}
|
||||
|
||||
}
|
||||
|
||||
.copyright {
|
||||
@ -458,7 +462,7 @@ p.note, div.note {
|
||||
float: right;
|
||||
margin-left: 8px;
|
||||
margin-bottom: 8px;
|
||||
font-size: .8em;
|
||||
font-size: 0.8em;
|
||||
}
|
||||
|
||||
ul.sidebar-menu {
|
||||
@ -571,7 +575,7 @@ div.config-vars {
|
||||
}
|
||||
|
||||
code {
|
||||
font-family: Consolas, Monaco, 'Andale Mono', 'Ubuntu Mono', monospace;
|
||||
font-family: Consolas, Monaco, "Andale Mono", "Ubuntu Mono", monospace;
|
||||
font-size: 0.8em;
|
||||
color: #1990b8;
|
||||
word-spacing: normal;
|
||||
@ -588,12 +592,15 @@ code {
|
||||
hyphens: none;
|
||||
|
||||
background-color: #fdfdfd;
|
||||
background-image: linear-gradient(transparent 50%, rgba(69, 142, 209, 0.04) 50%);
|
||||
background-image: linear-gradient(
|
||||
transparent 50%,
|
||||
rgba(69, 142, 209, 0.04) 50%
|
||||
);
|
||||
background-size: 3em 3em;
|
||||
background-origin: content-box;
|
||||
background-attachment: local;
|
||||
|
||||
border: 1px solid #ddd;
|
||||
border-radius: 0.4em;
|
||||
padding: .1em .4em
|
||||
padding: 0.1em 0.4em;
|
||||
}
|
||||
@ -1,5 +1,9 @@
|
||||
.pull-left {float: left;}
|
||||
.pull-right {float: right;}
|
||||
.pull-left {
|
||||
float: left;
|
||||
}
|
||||
.pull-right {
|
||||
float: right;
|
||||
}
|
||||
|
||||
.clearfix {
|
||||
*zoom: 1;
|
||||
@ -14,7 +18,8 @@
|
||||
}
|
||||
}
|
||||
|
||||
ul, ol {
|
||||
ul,
|
||||
ol {
|
||||
&.unstyled {
|
||||
list-style-type: none;
|
||||
margin: 0;
|
||||
@ -23,7 +28,9 @@ ul, ol {
|
||||
&.inline {
|
||||
@extend .unstyled;
|
||||
list-style-type: none;
|
||||
> li {display: inline;}
|
||||
> li {
|
||||
display: inline;
|
||||
}
|
||||
}
|
||||
|
||||
&.divided {
|
||||
@ -37,7 +44,9 @@ ul, ol {
|
||||
border-top: none;
|
||||
padding-top: 0;
|
||||
}
|
||||
&:last-child {border-bottom: none;}
|
||||
&:last-child {
|
||||
border-bottom: none;
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@ -58,3 +67,15 @@ ul, ol {
|
||||
color: $button-text;
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
* These buttons will fill the entirety of their container.
|
||||
*
|
||||
* 1. Remove padding so that widths and paddings don’t conflict.
|
||||
*/
|
||||
.btn--full {
|
||||
width: 100%;
|
||||
padding-right: 0; /* [1] */
|
||||
padding-left: 0; /* [1] */
|
||||
text-align: center;
|
||||
}
|
||||
|
||||
@ -314,6 +314,37 @@ Although the actual amount of light depends on weather, topography and land cove
|
||||
|
||||
A very thorough explanation of this is available in the Wikipedia article about the [Twilight](https://en.wikipedia.org/wiki/Twilight).
|
||||
|
||||
### Tag trigger
|
||||
|
||||
Fires when a [tag](/integrations/tag) is scanned. For example, a NFC tag is
|
||||
scanned using the Home Assistant Companion mobile application.
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
trigger:
|
||||
platform: tag
|
||||
tag_id: A7-6B-90-5F
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
Additionally, you can also only trigger if a card is scanned by a specific
|
||||
device/scanner by setting the `device_id`:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
trigger:
|
||||
platform: tag
|
||||
tag_id: A7-6B-90-5F
|
||||
device_id: 0e19cd3cf2b311ea88f469a7512c307d
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
### Template trigger
|
||||
|
||||
Template triggers work by evaluating a [template](/docs/configuration/templating/) on every state change for all of the recognized entities. The trigger will fire if the state change caused the template to render 'true'. This is achieved by having the template result in a true boolean expression (`{% raw %}{{ is_state('device_tracker.paulus', 'home') }}{% endraw %}`) or by having the template render 'true' (example below). Being a boolean expression the template must evaluate to false (or anything other than true) before the trigger will fire again.
|
||||
|
||||
@ -4,10 +4,11 @@
|
||||
<ul class="divided sidebar-menu">
|
||||
<li>
|
||||
<b>When</b>: Sunday, December 13, 2020<br>
|
||||
<b>Time</b>: <a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=Home+Assistant+Conference&iso=20201213T19&p1=16&ah=4" target="_blank">10:00 PST / 19:00 CET</a><br>
|
||||
<b>Where</b>: online<br>
|
||||
<b>Cost</b>: free<br>
|
||||
</li>
|
||||
</ul>
|
||||
<a class="btn btn--full" href="https://hopin.to/events/home-assistant-conference">Get your ticket</a>
|
||||
</div>
|
||||
|
||||
<div class="section">
|
||||
|
||||
@ -12,16 +12,11 @@ This tracker discovers new devices on boot and in regular intervals and tracks B
|
||||
|
||||
Devices discovered are stored with 'BLE_' as the prefix for device mac addresses in `known_devices.yaml`.
|
||||
|
||||
This platform requires pybluez to be installed. On Debian based installs, run
|
||||
## Setup
|
||||
|
||||
```bash
|
||||
sudo apt install bluetooth
|
||||
```
|
||||
This platform requires pybluez to be installed, which is already the case if you're using Home Assistant OS, Supervised or Container. For Home Assistant Core installs see below on the required steps.
|
||||
|
||||
Before you get started with this platform, please note that:
|
||||
|
||||
- This platform is incompatible with Windows
|
||||
- This platform requires access to the Bluetooth stack, see [Rootless Setup section](#rootless-setup) for further information
|
||||
## Configuration
|
||||
|
||||
To use the Bluetooth tracker in your installation, add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -59,7 +54,22 @@ Some BTLE devices (e.g., fitness trackers) are only visible to the devices that
|
||||
|
||||
Enabling the battery tracking might slightly decrease the duration of the battery, but since this is only done at most once a day, this shouldn't be noticeable. Not all devices offer battery status information; if the information is not available, the integration will only try once at startup.
|
||||
|
||||
## Rootless Setup
|
||||
For additional configuration variables check the [Device tracker page](/integrations/device_tracker/).
|
||||
|
||||
## Home Assistant Core installs
|
||||
|
||||
On Debian based Home Assistant Core installations, run:
|
||||
|
||||
```bash
|
||||
sudo apt install bluetooth
|
||||
```
|
||||
|
||||
Before you get started with this platform, please note that:
|
||||
|
||||
- This platform is incompatible with Windows
|
||||
- This platform requires access to the Bluetooth stack, see [Rootless Setup section](#rootless-setup) for further information
|
||||
|
||||
### Rootless Setup on Core installs
|
||||
|
||||
Normally accessing the Bluetooth stack is reserved for root, but running programs that are networked as root is a bad security wise. To allow non-root access to the Bluetooth stack we can give Python 3 and hcitool the missing capabilities to access the Bluetooth stack. Quite like setting the setuid bit (see [Stack Exchange](https://unix.stackexchange.com/questions/96106/bluetooth-le-scan-as-non-root) for more information).
|
||||
|
||||
@ -70,5 +80,3 @@ sudo setcap 'cap_net_raw+ep' $(readlink -f $(which hcitool))
|
||||
```
|
||||
|
||||
A restart of Home Assistant is required.
|
||||
|
||||
For additional configuration variables check the [Device tracker page](/integrations/device_tracker/).
|
||||
|
||||
@ -14,6 +14,7 @@ Supported devices (tested):
|
||||
|
||||
- [DW6HD1-BZ](https://www.leviton.com/en/products/dw6hd-1bz) (Decora Smart Wi-Fi 600W Dimmer)
|
||||
- [DW15S-1BZ](https://www.leviton.com/en/products/dw15s-1bz) (Decora Smart Wi-Fi 15A Switch)
|
||||
- [DW15P-1BW](https://www.leviton.com/en/products/dw15p-1bw) (Decora Smart Wi-Fi Plug-in Outlet)
|
||||
|
||||
To enable these lights, add the following lines to your `configuration.yaml` file:
|
||||
|
||||
|
||||
@ -35,6 +35,7 @@ Known supported devices:
|
||||
- Denon AVR-X3700H
|
||||
- Denon AVR-X4100W
|
||||
- Denon AVR-X4300H
|
||||
- Denon AVR-X4400H
|
||||
- Denon AVR-X4500H
|
||||
- Denon AVR-X6500H
|
||||
- Denon AVR-1912
|
||||
|
||||
@ -636,7 +636,7 @@ Check if the domain of your entity is [supported](#supported-components). If it
|
||||
|
||||
#### HomeKit doesn't work on second Home Assistant instance
|
||||
|
||||
To use the HomeKit integration with to different Home Assistant instances on the same local network, you need to set a custom name for at least one of them. [config/name](#name)
|
||||
To use the HomeKit integration with two different Home Assistant instances on the same local network, you need to set a custom name for at least one of them. [config/name](#name)
|
||||
|
||||
#### Specific entity doesn't work
|
||||
|
||||
|
||||
@ -119,6 +119,7 @@ script:
|
||||
- TX-55FZ802B
|
||||
- TX-58DX700B
|
||||
- TX-65EXW784
|
||||
- TX-65FX720W
|
||||
- TX-L42ET50
|
||||
- TX-P42STW50
|
||||
- TX-P50GT30Y
|
||||
|
||||
@ -21,7 +21,7 @@ This integration allows you to write Python scripts that are exposed as services
|
||||
|
||||
<div class='note'>
|
||||
|
||||
It is not possible to use Python imports with this integration. If you want to do more advanced scripts, you can take a look at [AppDaemon](https://appdaemon.readthedocs.io/en/latest/)
|
||||
It is not possible to use Python imports with this integration. If you want to do more advanced scripts, you can take a look at [AppDaemon](https://appdaemon.readthedocs.io/en/latest/) or [pyscript](https://github.com/custom-components/pyscript)
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -21,6 +21,8 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
To add a Ruckus Unleashed device to your installation, go to **Configuration** -> **Integrations**, click the `+` button, then select **Ruckus** from the list of integrations.
|
||||
|
||||
It is required to configure the IP address of your **master access point**. See the section Access Points on the management web interface. And perhaps consider to set a preferred master (Admin & Services>System>System Info>Preferred master).
|
||||
|
||||
You will have to create a user on the device which is a **Monitoring Admin**. Login to the Ruckus Unleashed admin UI and follow these steps:
|
||||
|
||||
- [Create a new role](https://docs.ruckuswireless.com/unleashed/200.1.9.12/t-ConfigUserRoles.html).
|
||||
|
||||
@ -57,8 +57,9 @@ surepetcare:
|
||||
|
||||
## Getting the IDs of your flaps, feeders and pets
|
||||
|
||||
There are (at least) two ways:
|
||||
There are (at least) three ways, sorted in "descending convenience order":
|
||||
|
||||
- Use the [surepy](https://github.com/benleb/surepy) tool (uses the same library as this integration) from [@benleb](https://github.com/benleb). A Python tool to get your token simply by running a single command (check `surepy --help` for the exact command).
|
||||
- Use the [sp_cli.py](https://github.com/rcastberg/sure_petcare/blob/master/sp_cli.py) from [@rcastberg](https://github.com/rcastberg) to fetch the IDs from the Sure Petcare API. With the default setting, the IDs will be written as JSON to `~/.surepet.cache`.
|
||||
- Visit [surepetcare.io](https://surepetcare.io) and log in with your Sure Petcare credentials. Open the developer tools in Chrome/Firefox, switch to the "Network" tab and refresh the page. Now look for calls to `start` (`pets`, `<household id>` and others are also possible, but `start` shows you all information at once). Click on this call and in the JSON displayed you will find all the needed IDs.
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ This integration allows you to control [Tasmota](https://tasmota.github.io/docs/
|
||||
## Requirements
|
||||
|
||||
- MQTT server and the [MQTT integration](/integrations/mqtt/) set up in Home Assistant.
|
||||
- Tasmota devices flashed with pre-release version 9.0.0.3, or later.
|
||||
- Tasmota devices flashed with version 9.1, or later.
|
||||
- Tasmota devices configured for native discovery (`SetOption19 0`)
|
||||
|
||||
## Limitations
|
||||
|
||||
@ -52,7 +52,7 @@ after:
|
||||
required: true
|
||||
type: [string, time]
|
||||
after_offset:
|
||||
description: The time offset of the beginning time range.
|
||||
description: The time offset of the ending time range.
|
||||
type: time
|
||||
required: false
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -10,7 +10,7 @@ ha_domain: vasttrafik
|
||||
|
||||
The `vasttrafik` sensor will provide you traveling details for the larger Göteborg area in Sweden from the [Västtrafik](https://vasttrafik.se/) public transportation service.
|
||||
|
||||
You must create an application [here](https://developer.vasttrafik.se/portal/#/applications) to obtain a `key` and a `secret`.
|
||||
You must create an application [here](https://developer.vasttrafik.se/portal/#/applications) to obtain a `key` and a `secret`. Make sure to also subscribe to the API by going to `Mina prenumerationer`, selecting your newly created application and the API `Reseplaneraren V2`.
|
||||
|
||||
Add the data to your `configuration.yaml` file as shown in the example:
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ ha_config_flow: true
|
||||
|
||||
The Xbox integration allows you to control Xbox One (or newer) consoles from Home Assistant.
|
||||
|
||||
Home Assistant authenticates with Xbox Live through OAuth2 using the Home Assistant Cloud account linking service. Set up the integration through **Configuration -> Integrations -> Xbox**. Ensure you login using the Microsoft account that is linked to your Xbox consoles.
|
||||
Home Assistant authenticates with Xbox Live through OAuth2 using the Home Assistant Cloud account linking service. Set up the integration through **Configuration -> Integrations -> Xbox**. Ensure you login using the Microsoft account that is linked to your Xbox consoles. Note that for the media player and remote entities to be added your Xbox will need to have remote features enabled via Settings-Remote Features (you may need to uprade your controller firmware).
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -42,6 +42,10 @@ There is also support for grouping of lights, switches, and fans (i.e. support f
|
||||
|
||||
ZHA integration uses a hardware independent Zigbee stack implementation with modular design which means that it can support any one of the many Zigbee coordinator radio modules/adapters available from different manufacturers, as long as that module/adapter is compatible with [zigpy](https://github.com/zigpy/zigpy).
|
||||
|
||||
Note! Zigbee 3.0 support or not in zigpy, depends primarily on your Zigbee coordinator hardware and its firmware. Some Zigbee coordinator hardware supports Zigbee 3.0 but might be shipped with an older firmware which does not. In such a case you may want to upgrade the firmware manually yourself.
|
||||
|
||||
Some other Zigbee coordinator hardware may not support a firmware that is capable of Zigbee 3.0 at all but can still be fully functional and feature-complete for your needs. This is very common as many, if not most, Zigbee devices do not yet Zigbee 3.0. As a general rule, newer Zigbee coordinator hardware generally supports Zigbee 3.0 firmware and it is up to its manufacturer to make such firmware available for them.
|
||||
|
||||
### Known working Zigbee radio modules
|
||||
|
||||
- dresden elektronik deCONZ based Zigbee radios (via the [zigpy-deconz](https://github.com/zigpy/zigpy-deconz) library for zigpy)
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: "Home Assistant Companion Android App Release 3.0.0"
|
||||
description: "What's new with the Home Assistant Companion Android App in 3.0.0"
|
||||
date: 2020-11-06 00:00:00
|
||||
date_formatted: "November 06, 2020"
|
||||
date_formatted: "November 6, 2020"
|
||||
comments: true
|
||||
author: Daniel Shokouhi
|
||||
categories: Release-Notes
|
||||
|
||||
@ -221,7 +221,7 @@
|
||||
/components/camera.doorbird /integrations/doorbird#camera
|
||||
/components/camera.familyhub /integrations/familyhub
|
||||
/components/camera.foscam /integrations/foscam
|
||||
/components/camera.generic /integrations/generic_ip_camera
|
||||
/components/camera.generic /integrations/generic
|
||||
/components/camera.local_file /integrations/local_file
|
||||
/components/camera.logi_circle /integrations/logi_circle#camera
|
||||
/components/camera.mjpeg /integrations/mjpeg
|
||||
@ -384,7 +384,7 @@
|
||||
/components/fan.wink /integrations/wink#fan
|
||||
/components/fan.zha /integrations/zha
|
||||
/components/fan.zwave /integrations/zwave
|
||||
/components/generic /integrations/generic_ip_camera
|
||||
/components/generic /integrations/generic
|
||||
/components/geo_location.geo_json_events /integrations/geo_json_events
|
||||
/components/geo_location.nsw_rural_fire_service_feed /integrations/nsw_rural_fire_service_feed
|
||||
/components/geo_location.usgs_earthquakes_feed /integrations/usgs_earthquakes_feed
|
||||
@ -1367,7 +1367,7 @@
|
||||
/components/garadget /integrations/garadget
|
||||
/components/gc100 /integrations/gc100
|
||||
/components/geizhals /integrations/geizhals
|
||||
/components/generic_ip_camera /integrations/generic_ip_camera
|
||||
/components/generic_ip_camera /integrations/generic
|
||||
/components/generic_thermostat /integrations/generic_thermostat
|
||||
/components/geniushub /integrations/geniushub
|
||||
/components/geo_json_events /integrations/geo_json_events
|
||||
@ -2018,6 +2018,7 @@
|
||||
# Breaking changes
|
||||
/integrations/switch.pca /integrations/elv
|
||||
/integrations/synologydsm /integrations/synology_dsm
|
||||
/integrations/generic_ip_camera /integrations/generic
|
||||
/integrations/telegram_chatbot /integrations/telegram_bot
|
||||
|
||||
# Moved documentation
|
||||
|
||||
@ -10,18 +10,26 @@ og_image: /images/conference/social.png
|
||||
<img src='/images/conference/conference-header.png' alt='Home Assistant Conference header' class='no-shadow'>
|
||||
<br><br>
|
||||
|
||||
The Home Assistant Conference is an online event where the Home Assistant community will share their ideas, creations and major milestones. The event will take place on December 13, 2020 and will be free to participate.
|
||||
The Home Assistant Conference is an online event to celebrate the community. It’s where the Home Assistant community will share their ideas, creations and major milestones. The event will take place on December 13, 2020.
|
||||
|
||||
We're still working out the details, so check back on this page for updates.
|
||||
The conference will contain three different tracks: everyone, advanced users and developers. For each track we have 5-6 speakers to share their creations, deep-dive into certain topics or share their epic automations.
|
||||
|
||||
## Open call for speakers
|
||||
Paulus Schoutsen, the founder of Home Assistant, will give the opening and closing keynote, aided by other Home Assistant developers.
|
||||
|
||||
We're currently looking for people that want to speak at the conference. Talks will need to be either 15 or 30 minutes. You will stream them from your house during the event.
|
||||
After the talks, attendees will be able to join various sessions about different topics like automations, Lovelace and Q&A with Home Assistant developers.
|
||||
|
||||
Talks can be about things you created, like a great automation, an amazing Lovelace dashboard, or a cool new feature. It can also be about your experience with Home Assistant, like how it has improved peoples lives, how you use it for education or some other unique use case.
|
||||
## Attending
|
||||
|
||||
_The deadline for submitting a talk was October 31, 2020._
|
||||
The Home Assistant Conference will be hosted on [Hopin](https://hopin.to/events/home-assistant-conference), an online conference platform. Tickets to attend will cost $1, which will cover the cost of the platform.
|
||||
|
||||
<a class="btn" href="https://hopin.to/events/home-assistant-conference">Get your ticket</a>
|
||||
|
||||
The conference will also be available as a free YouTube live stream. The live stream will be limited to the keynotes and the "everyone" track. You won't have access to the chat and have that online conference feeling, so we recommend getting a ticket!
|
||||
|
||||
To be notified when the live stream is online, [visit YouTube](https://www.youtube.com/watch?v=xSB_MuKkgxE) and click "Set Reminder".
|
||||
|
||||
Recordings of the keynote and all tracks and sessions will be made available on YouTube after the conference.
|
||||
|
||||
## Speakers & Schedule
|
||||
|
||||
This will come soon.
|
||||
_To be announced._
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -19,7 +19,7 @@ description:
|
||||
</h1>
|
||||
Released:
|
||||
<span class="release-date"
|
||||
>{{ site.date_released | date: "%B %d, %Y" }}</span
|
||||
>{{ site.date_released | date: "%B %e, %Y" }}</span
|
||||
>
|
||||
|
||||
<div class="links">
|
||||
|
||||
@ -9,7 +9,7 @@ The Supervisor utilizes the Network Manager on the host to offer network informa
|
||||
to add-ons and to give you the option to manage the network interfaces using the UI
|
||||
or via the command-line.
|
||||
|
||||
This requires the the Network Manager to be installed, active
|
||||
This requires NetworkManager to be installed, active
|
||||
and in control of at least one network interface on the host.
|
||||
|
||||
## The solution
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user