mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 09:17:06 +00:00
its != it's 😊 (#20141)
This commit is contained in:
Pavel Skuratovich
GitHub
parent
b0bef9ea4e
commit
83e810c197
@ -187,7 +187,7 @@ If you have issues checkout `home-assistant.log` in the configuration directory
|
||||
|
||||
## Debugging configuration files
|
||||
|
||||
If you have many configuration files, Home Assistant provides a CLI that allows you to see how it interprets them, each installation type has it's own section in the common-tasks about this:
|
||||
If you have many configuration files, Home Assistant provides a CLI that allows you to see how it interprets them, each installation type has its own section in the common-tasks about this:
|
||||
|
||||
- [Operating System](/common-tasks/os/#configuration-check)
|
||||
- [Container](/common-tasks/container/#configuration-check)
|
||||
|
||||
@ -19,7 +19,7 @@ If you have incorrect entries in your configuration files you can use the config
|
||||
|
||||
One of the most common problems with Home Assistant is an invalid `configuration.yaml` or other configuration file.
|
||||
|
||||
- Home Assistant provides a CLI that allows you to see how it interprets them, each installation type has it's own section in the common-tasks about this:
|
||||
- Home Assistant provides a CLI that allows you to see how it interprets them, each installation type has its own section in the common-tasks about this:
|
||||
- [Operating System](/common-tasks/os/#configuration-check)
|
||||
- [Container](/common-tasks/container/#configuration-check)
|
||||
- [Core](/common-tasks/core/#configuration-check)
|
||||
|
||||
@ -6,7 +6,7 @@ ha_category: Configuration
|
||||
|
||||
When an integration does not show up, many different things can be the case. Before you try any of these steps, make sure to look at the `home-assistant.log` file and see if there are any errors related to your integration you are trying to set up.
|
||||
|
||||
If you have incorrect entries in your configuration files you can use the CLI script to check your configuration, each installation type has it's own section in the common-tasks about this:
|
||||
If you have incorrect entries in your configuration files you can use the CLI script to check your configuration, each installation type has its own section in the common-tasks about this:
|
||||
|
||||
- [Operating System](/common-tasks/os/#configuration-check)
|
||||
- [Container](/common-tasks/container/#configuration-check)
|
||||
|
||||
@ -93,7 +93,7 @@ automation:
|
||||
custom_field: 123
|
||||
custom_object:
|
||||
trigger_more: true
|
||||
explain: "Its starting to get dark"
|
||||
explain: "It's starting to get dark"
|
||||
```
|
||||
|
||||
The message that can be retrieved from a queue or topic subscription:
|
||||
@ -106,7 +106,7 @@ The message that can be retrieved from a queue or topic subscription:
|
||||
"custom_field": 123,
|
||||
"custom_object": {
|
||||
"trigger_more": true,
|
||||
"explain": "Its starting to get dark"
|
||||
"explain": "It's starting to get dark"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
@ -38,7 +38,7 @@ The requirement is that you have setup the [`xiaomi aqara` integration](/integra
|
||||
#### Motion
|
||||
|
||||
```yaml
|
||||
- alias: "If there is motion and its dark turn on the gateway light"
|
||||
- alias: "If there is motion and it's dark turn on the gateway light"
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: binary_sensor.motion_sensor_158d000xxxxxc2
|
||||
|
||||
@ -210,7 +210,7 @@ value_template:
|
||||
|
||||
## Discovery Example
|
||||
|
||||
You can use the discovery protocol to create a new device tracker and set it's state using the command line tool `mosquitto_pub` shipped with `mosquitto` or the `mosquitto-clients` package to send MQTT messages.
|
||||
You can use the discovery protocol to create a new device tracker and set its state using the command line tool `mosquitto_pub` shipped with `mosquitto` or the `mosquitto-clients` package to send MQTT messages.
|
||||
|
||||
To create the device_tracker:
|
||||
|
||||
|
||||
@ -46,7 +46,7 @@ The following entity types are created:
|
||||
|
||||
### Incidents Sensor
|
||||
|
||||
This is the main entity of the integration containing the incident message as it's `value`, it has several attributes which are described below.
|
||||
This is the main entity of the integration containing the incident message as its `value`, it has several attributes which are described below.
|
||||
|
||||
| Attribute | Description |
|
||||
| --------- | ----------- |
|
||||
|
||||
@ -38,7 +38,7 @@ access_token:
|
||||
required: true
|
||||
type: string
|
||||
url:
|
||||
description: If you are using a GitHub Enterprise server, add it's URL here. For example, `https://mygithubserver.com`
|
||||
description: If you are using a GitHub Enterprise server, add its URL here. For example, `https://mygithubserver.com`
|
||||
required: false
|
||||
type: string
|
||||
repositories:
|
||||
|
||||
@ -579,7 +579,7 @@ interface:
|
||||
required: false
|
||||
type: string
|
||||
value:
|
||||
description: This is the value that is set on the device. Its device specific.
|
||||
description: This is the value that is set on the device. It's device specific.
|
||||
required: true
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -15,7 +15,7 @@ Install on your smartphone:
|
||||
|
||||
- [iOS](https://apps.apple.com/us/app/locative/id725198453?ign-mpt=uo%3D4)
|
||||
|
||||
To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant instance at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on it's first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
|
||||
To configure Locative, you must set it up via the integrations panel in the configuration screen. You must set up the app to send a POST request to your Home Assistant instance at the webhook URL provided by the integration during setup. When you enter or exit a geofence, Locative will send the appropriate request to that URL, updating Home Assistant. You are not able to specify a device name in Locative. Instead, you will need to look in your `dev-state` menu for a new device that Locative will have created on its first `GET`. If you had been or are using Owntracks as well, you will need to update the device name used in the Owntracks setup with the name that Locative generated.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/locative.png'/>
|
||||
|
||||
@ -551,7 +551,7 @@ modbus:
|
||||
scan_interval: 10
|
||||
```
|
||||
|
||||
### Example: Modbus cover controlled by a coil, it's state is read from the register
|
||||
### Example: Modbus cover controlled by a coil, its state is read from the register
|
||||
|
||||
This example shows a configuration for a Modbus cover controlled using a coil. Actual cover state is read from the `status_register`. We've also specified register values to match with the states open/opening/closed/closing. The cover state is polled from Modbus every 10 seconds.
|
||||
|
||||
@ -597,7 +597,7 @@ modbus:
|
||||
state_closed: 4
|
||||
```
|
||||
|
||||
### Example: Modbus cover controlled by a holding register, it's state is read from the status register
|
||||
### Example: Modbus cover controlled by a holding register, its state is read from the status register
|
||||
|
||||
This example shows a configuration for a Modbus cover controlled using a holding register. However, cover state is read from a `status_register`. In this case, we've specified only values for `state_open` and `state_closed`, for the rest, default values are used. The cover state is polled from Modbus every 10 seconds.
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ name:
|
||||
required: false
|
||||
type: string
|
||||
max_volume:
|
||||
description: Maximum volume as a percentage. Often the maximum volume of the receiver is far too loud. Setting this will set Home Assistant's 100% volume to be this setting on the amp. i.e., if you set this to 50% when you set Home Assistant to be 100% then your receiver will be set to 50% of it's maximum volume.
|
||||
description: Maximum volume as a percentage. Often the maximum volume of the receiver is far too loud. Setting this will set Home Assistant's 100% volume to be this setting on the amp. i.e., if you set this to 50% when you set Home Assistant to be 100% then your receiver will be set to 50% of its maximum volume.
|
||||
required: false
|
||||
default: 100
|
||||
type: integer
|
||||
|
||||
@ -112,7 +112,7 @@ Here are some real-life examples of how to use the **turn_off** variable.
|
||||
Suggested recipe for letting the `turn_off` script suspend a Linux computer (the **target**)
|
||||
from Home Assistant running on another Linux computer (the **server**).
|
||||
|
||||
1. On the **server**, log in as the user account Home Assistant is running under. In this exampleit's `hass`.
|
||||
1. On the **server**, log in as the user account Home Assistant is running under. In this example it's `hass`.
|
||||
2. On the **server**, create SSH keys by running `ssh-keygen`. Just press enter on all questions.
|
||||
3. On the **target**, create a new account that Home Assistant can ssh into: `sudo adduser hass`. Just press enter on all questions except password. It's recommended using the same user name as on the server. If you do, you can leave out `hass@` in the SSH commands below.
|
||||
4. On the **server**, transfer your public SSH key by `ssh-copy-id hass@TARGET` where TARGET is your target machine's name or IP address. Enter the password you created in step 3.
|
||||
|
||||
@ -138,7 +138,7 @@ Any other [actions](/docs/automation/action/) to power on the device can be conf
|
||||
|
||||
## Sources
|
||||
|
||||
To obtain complete list of available sources currently configured on the TV, once the webOS TV is configured and linked, while its powered on head to the **Developer Tools** > **States**, find your `media_player.<name>` and use the sources listed in `source_list:` remembering to split them per line into your `sources:` configuration. If you leave the `sources:` configuration empty, the `media_player` will offer all sources of the TV. If you list a subset of sources in the configuration, only those will be displayed.
|
||||
To obtain complete list of available sources currently configured on the TV, once the webOS TV is configured and linked, while it's powered on head to the **Developer Tools** > **States**, find your `media_player.<name>` and use the sources listed in `source_list:` remembering to split them per line into your `sources:` configuration. If you leave the `sources:` configuration empty, the `media_player` will offer all sources of the TV. If you list a subset of sources in the configuration, only those will be displayed.
|
||||
|
||||
Note: it is normal and expected behavior that for a switched-off TV only the Live TV source is offered in the `media_player`, even if you have configured other sources as well. These will show up as soon as the TV is switched on.
|
||||
|
||||
|
||||
@ -37,7 +37,7 @@ api_key:
|
||||
required: true
|
||||
type: string
|
||||
zpid:
|
||||
description: Property IDs to track in the front end. Can be found in it's Zillow URL as described above. Include only the numbers, do not include the "_zpid".
|
||||
description: Property IDs to track in the front end. Can be found in its Zillow URL as described above. Include only the numbers, do not include the "_zpid".
|
||||
required: true
|
||||
type: list
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -785,7 +785,7 @@ Renaming Z-Wave entities is done with the same [customization options](/docs/con
|
||||
|
||||
#### Node Values
|
||||
|
||||
Contains a list of available values of the selected node, and it's instances.
|
||||
Contains a list of available values of the selected node, and its instances.
|
||||
|
||||
#### Node group associations
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ categories:
|
||||
- Core
|
||||
---
|
||||
|
||||
Home Assistant is now using [YAML](http://yaml.org/) for it's configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
|
||||
Home Assistant is now using [YAML](http://yaml.org/) for its configuration file. YAML allows the use of lists, which should make the configuration file a bit more flexible and useful. The new configuration file format is backwards compatible with existing components. Because of this, there is no need for component developers to update their components.
|
||||
|
||||
The new file is named configuration.yaml and if it can't be found in your config directory, Home Assistant will instead try to find the old configuration file, home-assistant.conf.
|
||||
|
||||
|
||||
@ -45,7 +45,7 @@ Another cool addition is the local file camera. This seems very basic at first b
|
||||
|
||||
### Breaking change
|
||||
|
||||
- The new Netatmo support caused us to change how Netatmo are configured. It's now done via it's own component.
|
||||
- The new Netatmo support caused us to change how Netatmo are configured. It's now done via its own component.
|
||||
|
||||
```yaml
|
||||
netatmo:
|
||||
|
||||
@ -19,7 +19,7 @@ Currently includes:
|
||||
- Install Libcec. Adds local [HDMI-CEC support][cec].
|
||||
- Install Mossquitto. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.
|
||||
- Install OpenZWave. Installs OpenZWave and prepares for using a USB or GPIO ZWave controller.
|
||||
- Install Samba. Installs the Samba packages and shares your configuration over smb to be available to edit on any computer without the need for separate file transfer software. This share is unsecured and it's usage is not recommended if your installation is publicly available.
|
||||
- Install Samba. Installs the Samba packages and shares your configuration over smb to be available to edit on any computer without the need for separate file transfer software. This share is unsecured and its usage is not recommended if your installation is publicly available.
|
||||
|
||||
All of these scripts are available in the directory `/home/pi/hassbian-scripts/`. This directory is actually a cloned git repository that's cloned on first boot and can be updated to the latest release with ease after.
|
||||
To update the hassbian-scripts directory execute the following command as the `pi` user.
|
||||
|
||||
@ -24,7 +24,7 @@ To allow you to customize your installation further, we have included a tool cal
|
||||
- Install Libcec. Adds local [HDMI-CEC support][cec].
|
||||
- Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.
|
||||
- Install Open Z-Wave. Installs Python Open Z-Wave and OZWCP from git.
|
||||
- Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and it's usage is not recommended if you share your network with others.
|
||||
- Install Samba. Allows anyone on your network to edit your configuration from any computer. This share is unsecured and its usage is not recommended if you share your network with others.
|
||||
- Install Tellstick. Installs the Tellstick package for controlling and using a connected Tellstick.
|
||||
- Install Tradfri. Installs dependencies for using IKEA Trådfri.
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ og_image: /images/blog/2018-04-0.67/components.png
|
||||
|
||||
Release 0.67 is here! In case you missed [the announcement from yesterday][ann-ubiquiti], Ubiquiti is paying me to write these release notes. Ooooooh yeah. With more time on my hands I'm going to be focusing on major improvements that we have been postponing for a while, first up will be a user system.
|
||||
|
||||
This release includes a security fix. The error log was accessible via the API without requiring authentication in previous releases. Although not a leak on it's own, combined with a faulty component that would log sensitive information to the error log could lead to that being exposed (we don't know of any component that does this). Thanks to [Matt Hamilton](https://github.com/Eriner) for disclosing this issue to us.
|
||||
This release includes a security fix. The error log was accessible via the API without requiring authentication in previous releases. Although not a leak on its own, combined with a faulty component that would log sensitive information to the error log could lead to that being exposed (we don't know of any component that does this). Thanks to [Matt Hamilton](https://github.com/Eriner) for disclosing this issue to us.
|
||||
|
||||
## New Platforms
|
||||
|
||||
|
||||
@ -124,7 +124,7 @@ is great.
|
||||
|
||||
### Why not just use the REST API's directly via curl or similar ?
|
||||
|
||||
You can most definitely use `curl` or similar to access REST API directly - its
|
||||
You can most definitely use `curl` or similar to access REST API directly - it's
|
||||
basically what `hass-cli` does behind the scenes. `hass-cli` give though a few
|
||||
advantages. Firstly that you do not need to remember the exact commands,
|
||||
`hass-cli` have contextual help and auto completion to make it super easy to
|
||||
|
||||
@ -23,7 +23,7 @@ Home Assistant has adopted a new [Python support strategy](https://github.com/ho
|
||||
|
||||
## Pimp my Sidebar
|
||||
|
||||
The sidebar has gotten an improved look! Idea started with [a mockup by @JuanMTech on Twitter](https://twitter.com/JuanMTech/status/1143757213971943424) and grew into a full blown implementation. When visiting Home Assistant on devices with big screens (tablets, laptops, desktops), the sidebar will now always be visible in a minimized mode with the ability to fully hide it via the profile page. The developer tool buttons have been collapsed into a single menu item. The dev tools will now store it's exact state when you navigate away, included the dev tool that is open. We've also taken the opportunity to make notifications accessible from the sidebar, instead of only via the Lovelace UI.
|
||||
The sidebar has gotten an improved look! Idea started with [a mockup by @JuanMTech on Twitter](https://twitter.com/JuanMTech/status/1143757213971943424) and grew into a full blown implementation. When visiting Home Assistant on devices with big screens (tablets, laptops, desktops), the sidebar will now always be visible in a minimized mode with the ability to fully hide it via the profile page. The developer tool buttons have been collapsed into a single menu item. The dev tools will now store its exact state when you navigate away, included the dev tool that is open. We've also taken the opportunity to make notifications accessible from the sidebar, instead of only via the Lovelace UI.
|
||||
|
||||
On mobile devices the sidebar will behave like it previously did. Check [the demo](https://demo.home-assistant.io) for a preview.
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ og_image: /images/blog/2019-08-home-assistant-cast/social.png
|
||||
|
||||
Home automation itself has never been a goal of Home Assistant. Instead, it's a tool that allows us to have technology improve our life, and that of the people around us. I wrote about this [3,5 years ago](https://www.home-assistant.io/blog/2016/01/19/perfect-home-automation/), and it's been our guiding principle in building out Home Assistant.
|
||||
|
||||
Today we're introducing Home Assistant Cast to help with this. With Home Assistant Cast, people in your house can have quick access to see the state of your house and it's residents, and quickly adjust the most important settings. This is achieved by running on Chromecast powered screens that you already have throughout your house: your Google Nest Hubs and TVs.
|
||||
Today we're introducing Home Assistant Cast to help with this. With Home Assistant Cast, people in your house can have quick access to see the state of your house and its residents, and quickly adjust the most important settings. This is achieved by running on Chromecast powered screens that you already have throughout your house: your Google Nest Hubs and TVs.
|
||||
|
||||
You can launch Home Assistant Cast by going to [**the Home Assistant Cast launcher website**](https://cast.home-assistant.io). It works with any version of Home Assistant released in the last year. Home Assistant Cast can show any Lovelace view, including support for custom cards and themes. Got no Lovelace configuration? Don't worry, we'll generate a view and show that instead.
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ TL;DR:
|
||||
|
||||
---
|
||||
|
||||
Voice assistants are a great way to interact with your house, ask a quick question, set a timer or control your devices. The more an assistant knows about you, your home and it's other inhabitants, the better it is able to help you.
|
||||
Voice assistants are a great way to interact with your house, ask a quick question, set a timer or control your devices. The more an assistant knows about you, your home and its other inhabitants, the better it is able to help you.
|
||||
|
||||
Today's available virtual assistants work great, but they have a big problem: They store your data in the cloud, don't provide APIs to allow other companies to build products on top and are run by companies whose core business is building profiles on their users to help serve ads and product suggestions.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ categories: Community
|
||||
og_image: /images/blog/2020-02-07-community-highlights/social.png
|
||||
---
|
||||
|
||||
Thank god, its Friday! For most of us, it means we can tinker with our Home Automation projects again 😃
|
||||
Thank god, it's Friday! For most of us, it means we can tinker with our Home Automation projects again 😃
|
||||
|
||||
The second edition of the Community Highlights is here to provide you a fresh source of inspiration this weekend. And, if that is not enough, upgrading to the latest release of [Home Assistant Core 0.105](/blog/2020/02/05/release-105/) is definitely a recommendation for your list. It introduces tons of new shiny features for you to play with.
|
||||
|
||||
|
||||
@ -203,7 +203,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
||||
|
||||
## Breaking Changes
|
||||
|
||||
- **Lovelace themes** - We discovered our theme logic was wrong, when you didn't specify a theme for a Lovelace card or view. It would default to the backend selected theme, even when your local theme was different, or your view had a different theme. To fix this we removed the options `default` and `Backend selected` from the Lovelace theme selection, and when there is not theme selected it will not set a theme. This will make sure the element has the same theme as it's parent.
|
||||
- **Lovelace themes** - We discovered our theme logic was wrong, when you didn't specify a theme for a Lovelace card or view. It would default to the backend selected theme, even when your local theme was different, or your view had a different theme. To fix this we removed the options `default` and `Backend selected` from the Lovelace theme selection, and when there is not theme selected it will not set a theme. This will make sure the element has the same theme as its parent.
|
||||
|
||||
- **Freebox** - Freebox is now available as an integration from the Integrations UI! You will need to re-authorize Home Assistant to access the Freebox router. - ([@Quentame] - [#30334]) ([freebox docs])
|
||||
|
||||
|
||||
@ -262,7 +262,7 @@ Screenshot of an ONVIF camera in Home Assistant.
|
||||
|
||||
## Supervisor
|
||||
|
||||
Have you seen the new supervisor UI? [@ludeeus] did a great job redoing it's UI!
|
||||
Have you seen the new supervisor UI? [@ludeeus] did a great job redoing its UI!
|
||||
It now uses the same tabs as the configuration panel. The add-on page is split
|
||||
into multiple tabs, the add-on store is cleaned up and you can view all logs
|
||||
in the system tab now (requires advanced mode).
|
||||
|
||||
@ -74,7 +74,7 @@ Starting with 1.8.0 we have introduced a new [Geocoded sensor](https://companion
|
||||
Screenshot of the Geocoded Sensor.
|
||||
</p>
|
||||
|
||||
The battery level sensor was split in 1.9.0 to include a [battery state sensor](https://companion.home-assistant.io/docs/core/sensors#battery-sensors) so you can see when your device is actively `charging`, `not_charging`, `discharging` and `full`. You can also distinguish whether its `wireless`, `ac` or `usb`. The state now updates immediately upon being plugged in and unplugged to allow for quicker automations.
|
||||
The battery level sensor was split in 1.9.0 to include a [battery state sensor](https://companion.home-assistant.io/docs/core/sensors#battery-sensors) so you can see when your device is actively `charging`, `not_charging`, `discharging` and `full`. You can also distinguish whether it's `wireless`, `ac` or `usb`. The state now updates immediately upon being plugged in and unplugged to allow for quicker automations.
|
||||
|
||||
|
||||
#### Biometrics
|
||||
|
||||
@ -9,7 +9,7 @@ categories: Release-Notes
|
||||
og_image: /images/blog/2020-08-28-android-230-release/Companion.png
|
||||
---
|
||||
|
||||
Hey there, its been so long since we last gave an update on our mobile apps we thought it would be time to give you more updates! This time around we will focus on whats new in the Android app. There have been a few releases so were going to cover everything new up until version 2.3.0 which was just released to the Google Play Store.
|
||||
Hey there, it's been so long since we last gave an update on our mobile apps we thought it would be time to give you more updates! This time around we will focus on whats new in the Android app. There have been a few releases so were going to cover everything new up until version 2.3.0 which was just released to the Google Play Store.
|
||||
|
||||
## Manage Sensors
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ categories:
|
||||
og_image: /images/blog/2020-09-12-android-240-release/Companion.png
|
||||
---
|
||||
|
||||
Hey there, I hope everyone has been enjoying the last release of the Android app. We have another update coming up where we felt its time to give everyone a heads up before release. There are several new changes done that you will immediately notice after installing the update to 2.4.0, so we wanted to cover what's new. You can expect this release to be available in the Google Play Store tomorrow.
|
||||
Hey there, I hope everyone has been enjoying the last release of the Android app. We have another update coming up where we felt it's time to give everyone a heads up before release. There are several new changes done that you will immediately notice after installing the update to 2.4.0, so we wanted to cover what's new. You can expect this release to be available in the Google Play Store tomorrow.
|
||||
|
||||
## Current and Future Breaking Changes
|
||||
|
||||
|
||||
@ -369,7 +369,7 @@ same type as it is in the attribute (instead of as a string).
|
||||
<summary><b>Canary</b></summary>
|
||||
<p>
|
||||
|
||||
Canary is now available for configuration via the UI. This also means its no
|
||||
Canary is now available for configuration via the UI. This also means it's no
|
||||
longer configured in YAML. Existing configurations should be automatically
|
||||
transitioned to configuration via UI. You can safely remove you Canary YAML
|
||||
configuration after ugprading. YAML support will be fully removed in
|
||||
|
||||
@ -537,7 +537,7 @@ configuration method. Please see the cast documentation on how to set this up.
|
||||
<summary><b>Cloudflare</b></summary>
|
||||
<p>
|
||||
|
||||
Cloudflare is now available exclusively via the Integrations UI. This means its
|
||||
Cloudflare is now available exclusively via the Integrations UI. This means it's
|
||||
no longer configured in YAML. Existing configurations are not imported as API
|
||||
Tokens are now used to authenticate. Refer to integration documentation on how
|
||||
to setup via UI.
|
||||
|
||||
@ -9,9 +9,9 @@ categories: Release-Notes
|
||||
og_image: /images/blog/2020-11-06-android-300-release/Companion.png
|
||||
---
|
||||
|
||||
Hey everyone its been a little while since we last spoke. We have a brand new Home Assistant Companion for Android release that we are excited to get into your hands and will roll out over the next day or so in the Google Play store.
|
||||
Hey everyone it's been a little while since we last spoke. We have a brand new Home Assistant Companion for Android release that we are excited to get into your hands and will roll out over the next day or so in the Google Play store.
|
||||
|
||||
Before we get into the release details I'd like to mention that this month marks the [1 year anniversary](https://youtu.be/tc17q1Zn0Xs?t=3487) of the Home Assistant Companion app being offered in the Google Play Store! Just to think how far along the entire app has come from its initial alpha state to what is currently being offered in today's release. Can you believe its already been a year?
|
||||
Before we get into the release details I'd like to mention that this month marks the [1 year anniversary](https://youtu.be/tc17q1Zn0Xs?t=3487) of the Home Assistant Companion app being offered in the Google Play Store! Just to think how far along the entire app has come from its initial alpha state to what is currently being offered in today's release. Can you believe it's already been a year?
|
||||
|
||||
It has been pretty busy over on the Android side of things during Hacktoberfest! We have seen a total of 84 pull requests from a wide range of contributors that we are thankful for, so thank you for all of your efforts! In case you missed it we actually had a release shortly after version 2.4.0 but as we did not have an accompanying blog post, we'll cover whats new since we last spoke in this post. All of the features listed below are already documented on the [Companion](https://companion.home-assistant.io/) site, please be sure to check in there for greater details. Before we continue with what's new lets go over the breaking changes for this release.
|
||||
|
||||
|
||||
@ -111,7 +111,7 @@ Today we introduce: Home Assistant Analytics. Opt-in, privacy-aware, public
|
||||
and open source. Just as it all should be for our project.
|
||||
|
||||
[@ludeeus] did a fantastic job writing this new integration. You decide if you
|
||||
turn it on or not; however, we guarantee its privacy-aware. Doubt it? Review it!
|
||||
turn it on or not; however, we guarantee it's privacy-aware. Doubt it? Review it!
|
||||
Everything is open source!
|
||||
|
||||
Not open enough for you? We are publishing the result for everybody to see:
|
||||
@ -1032,7 +1032,7 @@ modbus:
|
||||
The `reporting` and `include_used_components` configuration options have now
|
||||
been deprecated, the `updater` integration will no longer report any analytics.
|
||||
|
||||
The analytics has moved to it's own integration.
|
||||
The analytics has moved to its own integration.
|
||||
See the [`analytics` integration](/integrations/analytics) for more details on
|
||||
how to configure it.
|
||||
|
||||
|
||||
@ -839,7 +839,7 @@ Database migrations are now done in the background and no longer prevent
|
||||
Home Assistant from starting.
|
||||
|
||||
The migration is started shortly after the started event since they are CPU
|
||||
intensive (mostly just sqlite since its in the same process) and we do not want
|
||||
intensive (mostly just sqlite since it's in the same process) and we do not want
|
||||
to compete with startup.
|
||||
|
||||
Events created by your system are queued and processed when the migration is
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user