mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-06-02 16:26:50 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
a932d94e52
2
.github/workflows/stale.yml
vendored
2
.github/workflows/stale.yml
vendored
@ -8,7 +8,7 @@ jobs:
|
||||
stale:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/stale@v3.0.17
|
||||
- uses: actions/stale@v3.0.18
|
||||
with:
|
||||
repo-token: ${{ secrets.GITHUB_TOKEN }}
|
||||
days-before-stale: 60
|
||||
|
||||
4
.github/workflows/test.yml
vendored
4
.github/workflows/test.yml
vendored
@ -51,13 +51,13 @@ jobs:
|
||||
run: npm run textlint
|
||||
build:
|
||||
name: Jekyll build
|
||||
runs-on: ubuntu-latest
|
||||
runs-on: ubuntu-18.04
|
||||
needs: [markdown-lint]
|
||||
steps:
|
||||
- name: Check out files from GitHub
|
||||
uses: actions/checkout@v2
|
||||
- name: Setting up Ruby 2.6
|
||||
uses: ruby/setup-ruby@v1.65.0
|
||||
uses: ruby/setup-ruby@v1.66.0
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- name: Setup Ruby Gems cache
|
||||
|
||||
@ -25,8 +25,8 @@ GEM
|
||||
http_parser.rb (~> 0.6.0)
|
||||
eventmachine (1.2.7)
|
||||
eventmachine (1.2.7-x64-mingw32)
|
||||
ffi (1.14.2)
|
||||
ffi (1.14.2-x64-mingw32)
|
||||
ffi (1.15.0)
|
||||
ffi (1.15.0-x64-mingw32)
|
||||
forwardable-extended (2.6.0)
|
||||
http_parser.rb (0.6.0)
|
||||
i18n (1.8.9)
|
||||
|
||||
@ -106,8 +106,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 2021
|
||||
current_minor_version: 3
|
||||
current_patch_version: 0
|
||||
date_released: 2021-03-03
|
||||
current_patch_version: 4
|
||||
date_released: 2021-03-12
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
|
||||
@ -22,11 +22,11 @@ script:
|
||||
target:
|
||||
entity_id: "{{ sonos_entity }}"
|
||||
- service: media_player.volume_set
|
||||
target:
|
||||
data:
|
||||
entity_id: "{{ sonos_entity }}"
|
||||
volume_level: "{{ volume }}"
|
||||
- service: tts.voicerss_say
|
||||
target:
|
||||
data:
|
||||
entity_id: "{{ sonos_entity }}"
|
||||
message: "{{ message }}"
|
||||
- delay: "{{ delay }}"
|
||||
|
||||
@ -168,7 +168,7 @@ automation:
|
||||
|
||||
<div class='note'>
|
||||
Listing above and below together means the numeric_state has to be between the two values.
|
||||
In the example above, the trigger would fire a single time if a numeric_state goes into to 17.1-24.9 range (from 17 and below or 25 and above). It will only fire again, once it has left the defined range and enters it again.
|
||||
In the example above, the trigger would fire a single time if a numeric_state goes into the 17.1-24.9 range (from 17 and below or 25 and above). It will only fire again, once it has left the defined range and enters it again.
|
||||
</div>
|
||||
|
||||
Number helpers (`input_number` entities) can be used in the `above` and `below` thresholds, making
|
||||
|
||||
@ -7,7 +7,7 @@ When launched for the first time, Home Assistant will create a default configura
|
||||
|
||||
The web interface can be found at `http://ip.ad.dre.ss:8123/` - for example if your Home Assistant system has the IP address `192.168.0.40` then you'll find the web interface as `http://192.168.0.40:8123/`.
|
||||
|
||||
The location of the folder differs between operating systems:
|
||||
The location of the folder differs for different operating systems:
|
||||
|
||||
| OS | Path |
|
||||
| -------------- | -------------------------- |
|
||||
@ -18,13 +18,13 @@ The location of the folder differs between operating systems:
|
||||
|
||||
If you want to use a different folder for configuration, use the configuration command line parameter: `hass --config path/to/config`.
|
||||
|
||||
Inside your configuration folder is the file `configuration.yaml`. This is the main file that contains integrations to be loaded with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable functionality.
|
||||
Inside your configuration folder is the file `configuration.yaml`. This is the main file that contains integrations to be loaded along with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable specific functionality.
|
||||
|
||||
If you run into trouble while configuring Home Assistant, have a look at the [configuration troubleshooting page](/getting-started/troubleshooting-configuration/) and at the [`configuration.yaml` examples](/cookbook/#example-configurationyaml).
|
||||
If you run into trouble while configuring Home Assistant, refer the [configuration troubleshooting page](/getting-started/troubleshooting-configuration/) and at the [`configuration.yaml` examples](/cookbook/#example-configurationyaml).
|
||||
|
||||
<div class='note tip'>
|
||||
|
||||
Test any changes to your configuration files from the command line with `hass --script check_config`. This script allows you to test changes without the need to restart Home Assistant. Remember to run this as the user you run Home Assistant as. Configuration changes can also be tested using the UI by navigating to Configuration, Server Controls and clicking "Check Configuration".
|
||||
Test any changes to your configuration files from the command line with `hass --script check_config`. This script allows you to test changes without the need to restart Home Assistant. Remember to run this script as the user you logged in to Home Assistant as. Configuration changes can also be tested using the UI by navigating to Configuration, Server Controls and clicking "Check Configuration".
|
||||
|
||||
</div>
|
||||
|
||||
@ -32,9 +32,9 @@ If you run into trouble while configuring Home Assistant, have a look at the [co
|
||||
|
||||
There are many ways you can edit `configuration.yaml`. Here are three options to get you started:
|
||||
|
||||
The simplest is to use the "File Editor" add-on. This will allow you to edit your configuration from within Home Assistant itself.
|
||||
The simplest way is to use the "File Editor" add-on. This will allow you to edit your configuration from within Home Assistant itself.
|
||||
|
||||
Perhaps the most robust option is to load the Visual Studio Code add-on. VS Code offers live syntax checking and auto-fill of various Home Assistant entities.
|
||||
The most robust option is to load the Visual Studio Code add-on. VS Code offers live syntax checking and auto-fill of various Home Assistant entities.
|
||||
|
||||
You can use Samba file share (you need to install the "Samba" add-on) and your favorite file editor.
|
||||
|
||||
@ -47,7 +47,7 @@ You can load changes to the following components without restarting, by using th
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
If you've made any changes, remember to [check your configuration](/docs/configuration/troubleshooting/#problems-with-the-configuration) before trying to reload or restart.
|
||||
If you have made any changes, remember to [check your configuration](/docs/configuration/troubleshooting/#problems-with-the-configuration) before trying to reload or restart.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -495,7 +495,7 @@ automation:
|
||||
to: "on"
|
||||
action:
|
||||
- choose:
|
||||
- alias: "IF nobody home, sound the alarm!
|
||||
- alias: "IF nobody home, sound the alarm!"
|
||||
conditions:
|
||||
- condition: state
|
||||
entity_id: group.family
|
||||
|
||||
@ -53,7 +53,7 @@ Steps to Integrate an Amazon Alexa Smart Home Skill with Home Assistant:
|
||||
|
||||
## Create an Amazon Alexa Smart Home Skill
|
||||
|
||||
- Sign in [Alexa Developer Console][alexa-dev-console], you can create your free account on the sign in page.
|
||||
- Sign in [Alexa Developer Console][alexa-dev-console], you can create your free account on the sign-in page. Note this *must* be created with the same Amazon account you use on your Alexa devices and app.
|
||||
- Go to `Alexa Skills` page if you are not, click `Create Skill` button to start the process.
|
||||
- Input `Skill name` as you like, select your skill's `Default language`.
|
||||
- Select `Smart Home` and `Provision your own`, then click `Create skill` button at top right corner.
|
||||
|
||||
@ -44,5 +44,5 @@ port:
|
||||
{% endconfiguration %}
|
||||
|
||||
<div class='note warning'>
|
||||
Communication between the Asterisk PBX server and the Home Assistant server is password-protected, but the data transmission is not encrypted. It is recommended to only use this integration when communication is contained within a local area network.
|
||||
Communication between the Asterisk PBX server and Home Assistant is password-protected, but the data transmission is not encrypted. It is recommended to only use this integration when communication is contained within a local area network.
|
||||
</div>
|
||||
|
||||
@ -16,7 +16,7 @@ ha_platforms:
|
||||
- sensor
|
||||
---
|
||||
|
||||
The `asuswrt` integration is the main integration to connect to a [ASUSWRT](https://www.asus.com/ASUSWRT/) based router.
|
||||
The ASUSWRT integration can connect Home Assistant to a ASUS router that runs on ASUSWRT firmware.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
@ -57,7 +57,7 @@ It is possible to change some behaviors through the integration options. These c
|
||||
- **Dnsmasq**: The location in the router of the dnsmasq.leases files
|
||||
- **Require IP**: If devices must have IP (this option is available only for access point mode)
|
||||
|
||||
**Note**: if you don't want to automatically track new detected device, disable the integration system option `Enable new added entities`
|
||||
**Note**: if you don't want to automatically track new detected device, disable the integration system option `Enable new added entities`
|
||||
|
||||
## Padavan custom firmware (The rt-n56u project)
|
||||
|
||||
|
||||
@ -43,7 +43,7 @@ inputs:
|
||||
hub:
|
||||
description: The name of the hub.
|
||||
required: false
|
||||
default: default
|
||||
default: modbus_hub
|
||||
type: string
|
||||
slave:
|
||||
description: The number of the slave (Optional for TCP and UDP Modbus).
|
||||
|
||||
@ -14,7 +14,8 @@ ha_platforms:
|
||||
- sensor
|
||||
---
|
||||
|
||||
The `cert_expiry` integration fetches the certificate from a configured host and displays its expiration in a timestamp sensor.
|
||||
The Certificate Expiry integration fetches the certificate from a configured host and displays its expiration in a timestamp sensor.
|
||||
The sensor checks and updates the certificate information for the configured host every 12 hours.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
||||
@ -4,6 +4,7 @@ description: Enable the Home Assistant Cloud integration.
|
||||
ha_release: '0.60'
|
||||
ha_category:
|
||||
- Voice
|
||||
- Text-to-speech
|
||||
ha_iot_class: Cloud Push
|
||||
ha_codeowners:
|
||||
- '@home-assistant/cloud'
|
||||
|
||||
@ -69,7 +69,7 @@ For SSH usage (according to [this](https://blog.cloudflare.com/cloudflare-now-su
|
||||
|
||||
#### The minimum DNS record settings (if you have set up HTTPS already)
|
||||
|
||||
To redirect from your domain to the IP address of your Home Assistant server set this DNS record:
|
||||
To redirect from your domain to the IP address of your Home Assistant instance, set this DNS record:
|
||||
|
||||
```text
|
||||
Type: A
|
||||
|
||||
@ -63,9 +63,9 @@ wait:
|
||||
|
||||
Ensure if this is a public-facing server, that the port is secured. Anyone who
|
||||
is able to access the debugger port can *execute arbitrary code* on the
|
||||
Home Assistant server, which is very unsafe.
|
||||
Home Assistant instance, which is very unsafe.
|
||||
|
||||
If the Home Assistant server is behind your firewall with only the http(s) port
|
||||
If the Home Assistant instance is behind your firewall with only the http(s) port
|
||||
exposed, then this is safe from outside connections.
|
||||
|
||||
## Performance and Memory Use
|
||||
|
||||
@ -32,7 +32,7 @@ ha_platforms:
|
||||
- weather
|
||||
---
|
||||
|
||||
The `demo` platform allows you to use integrations which are providing a demo of their implementation. The demo entities are dummies but show you how the actual platform looks like. This way you can run own demonstration instance like the online [Home Assistant demo](/demo/)but combined with your own real/functional platforms.
|
||||
The `demo` platform allows you to use integrations which are providing a demo of their implementation. The demo entities are dummies but show you how the actual platform looks like. This way you can run own demonstration instance like the online [Home Assistant demo](/demo/) but combined with your own real/functional platforms.
|
||||
|
||||
Available demo platforms:
|
||||
|
||||
|
||||
@ -49,7 +49,7 @@ To get the webhook URL, go to the integrations page in the configuration screen
|
||||
- At the bottom of the page, expand "Fulfillment" and check "Use webhook".
|
||||
- Click "Save".
|
||||
- At the top right of the screen where it says "Try it now...", type, or say, the phrase you have previously defined and hit enter.
|
||||
- Dialogflow will now send a request to your Home Assistant server and display the response.
|
||||
- Dialogflow will now send a request to your Home Assistant instance and display the response.
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
|
||||
@ -128,7 +128,7 @@ proxy_set_header X-Real-IP $remote_addr;
|
||||
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
||||
```
|
||||
|
||||
This snippet should be added within your Home Assistant server configuration, so you have something like the following:
|
||||
This snippet should be added within your Home Assistant configuration, so you have something like the following:
|
||||
|
||||
```bash
|
||||
server {
|
||||
|
||||
@ -119,7 +119,7 @@ fan:
|
||||
required: false
|
||||
type: action
|
||||
preset_modes:
|
||||
description: List of preset modes the fan is capable of.
|
||||
description: List of preset modes the fan is capable of. This is an arbitrary list of strings and must not contain any speeds.
|
||||
required: false
|
||||
type: [string, list]
|
||||
default: []
|
||||
@ -129,3 +129,12 @@ fan:
|
||||
type: integer
|
||||
default: 100
|
||||
{% endconfiguration %}
|
||||
|
||||
## Converting from speeds to percentage
|
||||
|
||||
When converting a fan with 3 speeds from the old fan entity model, the following percentages can be used:
|
||||
|
||||
0 - `off`
|
||||
33 - `low`
|
||||
66 - `medium`
|
||||
100 - `high`
|
||||
|
||||
@ -191,7 +191,7 @@ This is the recommended option.
|
||||
- Polls the hub directly (so is faster, say ~1s response time).
|
||||
- You have the option of specifying a MAC address (not recommended, see above).
|
||||
|
||||
The hub does not have to be in the same subnet as your Home Assistant server.
|
||||
The hub does not have to be in the same subnet as your Home Assistant instance.
|
||||
|
||||
### Option 2: hub token only
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ This integration sets up integration with [Geofency](https://www.geofency.com/).
|
||||
|
||||
## Configuration
|
||||
|
||||
To configure Geofency, you must set it up via the integrations panel in the configuration screen. You must then configure the iOS app (via the Webhook feature) to send a POST request to your Home Assistant server at the webhook URL provided by the integration during setup. Use the default POST format. Make sure to enable the 'Update Geo-Position' functionality for mobile beacons.
|
||||
To configure Geofency, you must set it up via the integrations panel in the configuration screen. You must then configure the iOS app (via the Webhook feature) to send a POST request to your Home Assistant instance at the webhook URL provided by the integration during setup. Use the default POST format. Make sure to enable the 'Update Geo-Position' functionality for mobile beacons.
|
||||
|
||||
Geofency will automatically generate the device tracker name used for geofences, and you will find it in the integrations section after the first request. For beacons, the device name will be `beacon_<name from Geofency>`, e.g., `device_tracker.beacon_car`.
|
||||
|
||||
|
||||
@ -34,7 +34,9 @@ Once the code is obtained fill in the form with your email, password and the aut
|
||||
2. Log into your Google account normally.
|
||||
3. You should be redirected to a loading screen. Copy the `oauth_code` cookie value set by this page and paste it here.
|
||||
|
||||
To obtain the `oauth_code` cookie value using Chrome or Firefox, follow the steps below:
|
||||
To obtain the `oauth_code` cookie value, follow the steps below:
|
||||
|
||||
*Note:* If the `oauth_code` cookie is not showing in Chrome, try Firefox.
|
||||
|
||||
* Press F12 to open developer tools.
|
||||
* Select the "Application" (Chrome) or "Storage" (Firefox) tab.
|
||||
|
||||
@ -12,241 +12,255 @@ ha_codeowners:
|
||||
ha_zeroconf: true
|
||||
---
|
||||
|
||||
The HomeKit integration allows you to make your Home Assistant entities available in Apple HomeKit, so they can be controlled from Apple's Home app and Siri. Please make sure that you have read the [considerations](#considerations) listed below to save you some trouble later. However if you do encounter issues, check out the [troubleshooting](#troubleshooting) section.
|
||||
The HomeKit integration allows you to make your Home Assistant entities available in Apple HomeKit,
|
||||
so they can be controlled from Apple's Home app and Siri.
|
||||
|
||||
Please make sure that you have read the [considerations](#considerations) listed below to save you
|
||||
some trouble later. However if you do encounter issues, check out the
|
||||
[troubleshooting](#troubleshooting) section.
|
||||
|
||||
<div class="note">
|
||||
|
||||
If you want to control `HomeKit` only devices with Home Assistant, check out the [HomeKit controller](/integrations/homekit_controller/) component.
|
||||
If you want to control HomeKit only devices with Home Assistant,
|
||||
check out the [HomeKit controller](/integrations/homekit_controller/) integration.
|
||||
That one provides the possibility to pull HomeKit enabled devices into Home Assistant.
|
||||
|
||||
</div>
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
If you need to use the `entity_config`, `ip_address`, or `advertise_ip` configuration options, HomeKit Bridge must be configured via your `configuration.yaml` file:
|
||||
## Manual configuration
|
||||
|
||||
```yaml
|
||||
If you want make specific changes to the way entities are published to HomeKit, override the
|
||||
IP address the HomeKit integration uses to communicate with your network or change the
|
||||
IP address the HomeKit uses to advertise itself to the network, you'll need to configure the
|
||||
HomeKit integration using a manual YAML entry to your `configuration.yaml` file.
|
||||
|
||||
This is an example entry of how that would look:
|
||||
|
||||
```yaml test
|
||||
# Example configuration.yaml entry configuring HomeKit
|
||||
homekit:
|
||||
- filter:
|
||||
include_domains:
|
||||
- alarm_control_panel
|
||||
- light
|
||||
- media_player
|
||||
include_entity_globs:
|
||||
- binary_sensor.*_occupancy
|
||||
include_entities:
|
||||
- binary_sensor.living_room_motion
|
||||
entity_config:
|
||||
alarm_control_panel.home:
|
||||
code: 1234
|
||||
binary_sensor.living_room_motion:
|
||||
linked_battery_sensor: sensor.living_room_motion_battery
|
||||
low_battery_threshold: 31
|
||||
light.kitchen_table:
|
||||
name: Kitchen Table Light
|
||||
lock.front_door:
|
||||
code: 1234
|
||||
media_player.living_room:
|
||||
feature_list:
|
||||
- feature: on_off
|
||||
- feature: play_pause
|
||||
- feature: play_stop
|
||||
- feature: toggle_mute
|
||||
switch.bedroom_outlet:
|
||||
type: outlet
|
||||
camera.back_porch:
|
||||
support_audio: True
|
||||
- name: HASS Bridge 2
|
||||
port: 21065
|
||||
filter:
|
||||
include_domains:
|
||||
- light
|
||||
- filter:
|
||||
include_domains:
|
||||
- alarm_control_panel
|
||||
- light
|
||||
- media_player
|
||||
include_entity_globs:
|
||||
- binary_sensor.*_occupancy
|
||||
include_entities:
|
||||
- binary_sensor.living_room_motion
|
||||
entity_config:
|
||||
alarm_control_panel.home:
|
||||
code: 1234
|
||||
binary_sensor.living_room_motion:
|
||||
linked_battery_sensor: sensor.living_room_motion_battery
|
||||
low_battery_threshold: 31
|
||||
light.kitchen_table:
|
||||
name: Kitchen Table Light
|
||||
lock.front_door:
|
||||
code: 1234
|
||||
media_player.living_room:
|
||||
feature_list:
|
||||
- feature: on_off
|
||||
- feature: play_pause
|
||||
- feature: play_stop
|
||||
- feature: toggle_mute
|
||||
switch.bedroom_outlet:
|
||||
type: outlet
|
||||
camera.back_porch:
|
||||
support_audio: True
|
||||
- name: HASS Bridge 2
|
||||
port: 21065
|
||||
filter:
|
||||
include_domains:
|
||||
- light
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
homekit:
|
||||
description: HomeKit configuration.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
auto_start:
|
||||
description: Flag if the HomeKit Server should start automatically after the Home Assistant Core Setup is done. ([Disable Auto Start](#disable-auto-start))
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
port:
|
||||
description: Port for the HomeKit extension. If you are adding more than one instance they need to have different values for port.
|
||||
required: false
|
||||
type: integer
|
||||
default: 21063
|
||||
name:
|
||||
description: Need to be individual for each instance of Home Assistant using the integration on the same local network. Between `3` and `25` characters. Alphanumeric and spaces allowed.
|
||||
required: false
|
||||
type: string
|
||||
default: '`Home Assistant Bridge`'
|
||||
ip_address:
|
||||
description: The local network IP address. Only necessary if the default from Home Assistant does not work.
|
||||
required: false
|
||||
type: string
|
||||
mode:
|
||||
description: HomeKit can expose an entity via a bridge, or a single entity as an accessory which is needed for Television Media Players. ([Accessory mode](#accessory-mode))
|
||||
required: false
|
||||
type: string
|
||||
default: '`bridge`'
|
||||
advertise_ip:
|
||||
description: If you need to override the IP address used for mDNS advertisement. (For example, using network isolation in Docker and together with an mDNS forwarder like `avahi-daemon` in reflector mode)
|
||||
required: false
|
||||
type: string
|
||||
filter:
|
||||
description: Filters for entities to be included/excluded from HomeKit. ([Configure Filter](#configure-filter))
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
include_domains:
|
||||
description: Domains to be included.
|
||||
required: false
|
||||
type: list
|
||||
include_entity_globs:
|
||||
description: Include all entities matching a listed pattern (e.g., `binary_sensor.*_motion`).
|
||||
required: false
|
||||
type: list
|
||||
include_entities:
|
||||
description: Entities to be included.
|
||||
required: false
|
||||
type: list
|
||||
exclude_domains:
|
||||
description: Domains to be excluded.
|
||||
required: false
|
||||
type: list
|
||||
exclude_entity_globs:
|
||||
description: Exclude all entities matching a listed pattern (e.g., `sensor.*_motion`).
|
||||
required: false
|
||||
type: list
|
||||
exclude_entities:
|
||||
description: Entities to be excluded.
|
||||
required: false
|
||||
type: list
|
||||
entity_config:
|
||||
description: Configuration for specific entities. All subordinate keys are the corresponding entity ids to the domains, e.g., `alarm_control_panel.alarm`.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
'`ENTITY_ID`':
|
||||
description: Additional options for specific entities.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: Name of the entity to show in HomeKit. HomeKit will cache the name on the first run so the accessory must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
linked_battery_sensor:
|
||||
description: The `entity_id` of a `sensor` entity to use as the battery of the accessory. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
linked_doorbell_sensor:
|
||||
description: The `entity_id` of a `binary_sensor` entity to use as the doorbell sensor of the camera accessory to enable doorbell notifications. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
linked_motion_sensor:
|
||||
description: The `entity_id` of a `binary_sensor` entity to use as the motion sensor of the camera accessory to enable motion notifications. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
linked_obstruction_sensor:
|
||||
description: The `entity_id` of a `binary_sensor` entity to use as the obstruction sensor of the garage door (cover) accessory to enable obstruction state tracking. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
low_battery_threshold:
|
||||
description: Minimum battery level before the accessory starts reporting a low battery.
|
||||
required: false
|
||||
type: integer
|
||||
default: 20
|
||||
code:
|
||||
description: Code to `arm / disarm` an alarm or `lock / unlock` a lock. Only applicable for `alarm_control_panel` or `lock` entities.
|
||||
required: false
|
||||
type: string
|
||||
default: '`<No code>`'
|
||||
feature_list:
|
||||
description: Only for `media_player` entities. List of feature dictionaries to add for a given entity. Comparable to the platform schema.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
feature:
|
||||
description: Name of the feature to add to the entity representation. Valid features are `on_off`, `play_pause`, `play_stop` and `toggle_mute`. The media_player entity must support the feature to be valid.
|
||||
required: true
|
||||
type: string
|
||||
type:
|
||||
description: Only for `switch` entities. Type of accessory to be created within HomeKit. Valid types are `faucet`, `outlet`, `shower`, `sprinkler`, `switch` and `valve`. HomeKit will cache the type on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
default: '`switch`'
|
||||
stream_count:
|
||||
description: Only for `camera` entities. The number of simultaneous stream the camera can support.
|
||||
required: false
|
||||
type: integer
|
||||
default: 3
|
||||
stream_address:
|
||||
description: Only for `camera` entities. The source IP address to use when streaming to RTP clients. If your Home Assistant host has multiple interfaces, selecting a specific IP may be necessary.
|
||||
required: false
|
||||
type: string
|
||||
default: local IP from Home Assistant
|
||||
stream_source:
|
||||
description: Only for `camera` entities. A URL, file or other valid FFmpeg input string to use as the stream source, rather than the default camera source. Required for camera entities that do not natively support streaming (MJPEG). If `-i` is not found in the stream source, it is prepended to construct the FFmpeg input.
|
||||
required: false
|
||||
type: string
|
||||
default: stream source from camera entity
|
||||
support_audio:
|
||||
description: Only for `camera` entities. Whether the camera supports audio. Audio is disabled unless this flag is set to `True`.
|
||||
required: false
|
||||
type: boolean
|
||||
default: '`False`'
|
||||
max_width:
|
||||
description: Only for `camera` entities. Maximum width supported by camera. Used when generating advertised video resolutions.
|
||||
required: false
|
||||
type: integer
|
||||
default: 1920
|
||||
max_height:
|
||||
description: Only for `camera` entities. Maximum height supported by camera. Used when generating advertised video resolutions.
|
||||
required: false
|
||||
type: integer
|
||||
default: 1080
|
||||
max_fps:
|
||||
description: Only for `camera` entities. Maximum fps supported by camera. Used when generating advertised video resolutions.
|
||||
required: false
|
||||
type: integer
|
||||
default: 30
|
||||
audio_map:
|
||||
description: Only for `camera` entities. FFmpeg [stream selection mapping](https://ffmpeg.org/ffmpeg.html#Stream-selection) for the audio-only stream. Selects the first audio stream in the input stream by default. If your input stream has multiple audio streams, this may need to be adjusted.
|
||||
required: false
|
||||
type: string
|
||||
default: '`0:a:0`'
|
||||
video_map:
|
||||
description: Only for `camera` entities. FFmpeg [stream selection mapping](https://ffmpeg.org/ffmpeg.html#Stream-selection) for the video-only stream. Selects the first video stream in the input stream by default. If your input stream has multiple video streams, this may need to be adjusted.
|
||||
required: false
|
||||
type: string
|
||||
default: '`0:v:0`'
|
||||
audio_packet_size:
|
||||
description: Only for `camera` entities. RTP packet size used for streaming audio to HomeKit clients.
|
||||
required: false
|
||||
type: integer
|
||||
default: 188
|
||||
video_packet_size:
|
||||
description: Only for `camera` entities. RTP packet size used for streaming video to HomeKit clients.
|
||||
required: false
|
||||
type: integer
|
||||
default: 1316
|
||||
video_codec:
|
||||
description: Only for `camera` entities. FFmpeg video codec for transcoding. `copy` option reduces CPU load when video source already encoded with `H264` (MPEG4). `h264_omx` option is only available with custom FFmpeg builds and enables GPU Hardware acceleration on Raspberry Pi.
|
||||
required: false
|
||||
type: string
|
||||
default: libx264
|
||||
available options: copy, libx264, h264_omx
|
||||
audio_codec:
|
||||
description: Only for `camera` entities. FFmpeg audio codec for transcoding. `copy` option reduces CPU load when audio source already encoded with `libopus`.
|
||||
required: false
|
||||
type: string
|
||||
default: libopus
|
||||
available options: copy, libopus
|
||||
homekit:
|
||||
description: HomeKit configuration.
|
||||
required: true
|
||||
type: map
|
||||
keys:
|
||||
auto_start:
|
||||
description: Flag if the HomeKit Server should start automatically after the Home Assistant Core Setup is done. ([Disable Auto Start](#disable-auto-start))
|
||||
required: false
|
||||
type: boolean
|
||||
default: true
|
||||
port:
|
||||
description: Port for the HomeKit extension. If you are adding more than one instance they need to have different values for port.
|
||||
required: false
|
||||
type: integer
|
||||
default: 21063
|
||||
name:
|
||||
description: Need to be individual for each instance of Home Assistant using the integration on the same local network. Between `3` and `25` characters. Alphanumeric and spaces allowed.
|
||||
required: false
|
||||
type: string
|
||||
default: '`Home Assistant Bridge`'
|
||||
ip_address:
|
||||
description: The local network IP address. Only necessary if the default from Home Assistant does not work.
|
||||
required: false
|
||||
type: string
|
||||
mode:
|
||||
description: HomeKit can expose an entity via a bridge, or a single entity as an accessory which is needed for Television Media Players. ([Accessory mode](#accessory-mode))
|
||||
required: false
|
||||
type: string
|
||||
default: '`bridge`'
|
||||
advertise_ip:
|
||||
description: If you need to override the IP address used for mDNS advertisement. (For example, using network isolation in Docker and together with an mDNS forwarder like `avahi-daemon` in reflector mode)
|
||||
required: false
|
||||
type: string
|
||||
filter:
|
||||
description: Filters for entities to be included/excluded from HomeKit. ([Configure Filter](#configure-filter))
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
include_domains:
|
||||
description: Domains to be included.
|
||||
required: false
|
||||
type: list
|
||||
include_entity_globs:
|
||||
description: Include all entities matching a listed pattern (e.g., `binary_sensor.*_motion`).
|
||||
required: false
|
||||
type: list
|
||||
include_entities:
|
||||
description: Entities to be included.
|
||||
required: false
|
||||
type: list
|
||||
exclude_domains:
|
||||
description: Domains to be excluded.
|
||||
required: false
|
||||
type: list
|
||||
exclude_entity_globs:
|
||||
description: Exclude all entities matching a listed pattern (e.g., `sensor.*_motion`).
|
||||
required: false
|
||||
type: list
|
||||
exclude_entities:
|
||||
description: Entities to be excluded.
|
||||
required: false
|
||||
type: list
|
||||
entity_config:
|
||||
description: Configuration for specific entities. All subordinate keys are the corresponding entity ids to the domains, e.g., `alarm_control_panel.alarm`.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
'`ENTITY_ID`':
|
||||
description: Additional options for specific entities.
|
||||
required: false
|
||||
type: map
|
||||
keys:
|
||||
name:
|
||||
description: Name of the entity to show in HomeKit. HomeKit will cache the name on the first run so the accessory must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
linked_battery_sensor:
|
||||
description: The `entity_id` of a `sensor` entity to use as the battery of the accessory. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
linked_doorbell_sensor:
|
||||
description: The `entity_id` of a `binary_sensor` entity to use as the doorbell sensor of the camera accessory to enable doorbell notifications. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
linked_motion_sensor:
|
||||
description: The `entity_id` of a `binary_sensor` entity to use as the motion sensor of the camera accessory to enable motion notifications. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
linked_obstruction_sensor:
|
||||
description: The `entity_id` of a `binary_sensor` entity to use as the obstruction sensor of the garage door (cover) accessory to enable obstruction state tracking. HomeKit will cache an accessory's feature set on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
low_battery_threshold:
|
||||
description: Minimum battery level before the accessory starts reporting a low battery.
|
||||
required: false
|
||||
type: integer
|
||||
default: 20
|
||||
code:
|
||||
description: Code to `arm / disarm` an alarm or `lock / unlock` a lock. Only applicable for `alarm_control_panel` or `lock` entities.
|
||||
required: false
|
||||
type: string
|
||||
default: '`<No code>`'
|
||||
feature_list:
|
||||
description: Only for `media_player` entities. List of feature dictionaries to add for a given entity. Comparable to the platform schema.
|
||||
required: false
|
||||
type: list
|
||||
keys:
|
||||
feature:
|
||||
description: Name of the feature to add to the entity representation. Valid features are `on_off`, `play_pause`, `play_stop` and `toggle_mute`. The media_player entity must support the feature to be valid.
|
||||
required: true
|
||||
type: string
|
||||
type:
|
||||
description: Only for `switch` entities. Type of accessory to be created within HomeKit. Valid types are `faucet`, `outlet`, `shower`, `sprinkler`, `switch` and `valve`. HomeKit will cache the type on the first run so a device must be [reset](#resetting-accessories) for any change to take effect.
|
||||
required: false
|
||||
type: string
|
||||
default: '`switch`'
|
||||
stream_count:
|
||||
description: Only for `camera` entities. The number of simultaneous stream the camera can support.
|
||||
required: false
|
||||
type: integer
|
||||
default: 3
|
||||
stream_address:
|
||||
description: Only for `camera` entities. The source IP address to use when streaming to RTP clients. If your Home Assistant host has multiple interfaces, selecting a specific IP may be necessary.
|
||||
required: false
|
||||
type: string
|
||||
default: local IP from Home Assistant
|
||||
stream_source:
|
||||
description: Only for `camera` entities. A URL, file or other valid FFmpeg input string to use as the stream source, rather than the default camera source. Required for camera entities that do not natively support streaming (MJPEG). If `-i` is not found in the stream source, it is prepended to construct the FFmpeg input.
|
||||
required: false
|
||||
type: string
|
||||
default: stream source from camera entity
|
||||
support_audio:
|
||||
description: Only for `camera` entities. Whether the camera supports audio. Audio is disabled unless this flag is set to `True`.
|
||||
required: false
|
||||
type: boolean
|
||||
default: '`False`'
|
||||
max_width:
|
||||
description: Only for `camera` entities. Maximum width supported by camera. Used when generating advertised video resolutions.
|
||||
required: false
|
||||
type: integer
|
||||
default: 1920
|
||||
max_height:
|
||||
description: Only for `camera` entities. Maximum height supported by camera. Used when generating advertised video resolutions.
|
||||
required: false
|
||||
type: integer
|
||||
default: 1080
|
||||
max_fps:
|
||||
description: Only for `camera` entities. Maximum fps supported by camera. Used when generating advertised video resolutions.
|
||||
required: false
|
||||
type: integer
|
||||
default: 30
|
||||
audio_map:
|
||||
description: Only for `camera` entities. FFmpeg [stream selection mapping](https://ffmpeg.org/ffmpeg.html#Stream-selection) for the audio-only stream. Selects the first audio stream in the input stream by default. If your input stream has multiple audio streams, this may need to be adjusted.
|
||||
required: false
|
||||
type: string
|
||||
default: '`0:a:0`'
|
||||
video_map:
|
||||
description: Only for `camera` entities. FFmpeg [stream selection mapping](https://ffmpeg.org/ffmpeg.html#Stream-selection) for the video-only stream. Selects the first video stream in the input stream by default. If your input stream has multiple video streams, this may need to be adjusted.
|
||||
required: false
|
||||
type: string
|
||||
default: '`0:v:0`'
|
||||
audio_packet_size:
|
||||
description: Only for `camera` entities. RTP packet size used for streaming audio to HomeKit clients.
|
||||
required: false
|
||||
type: integer
|
||||
default: 188
|
||||
video_packet_size:
|
||||
description: Only for `camera` entities. RTP packet size used for streaming video to HomeKit clients.
|
||||
required: false
|
||||
type: integer
|
||||
default: 1316
|
||||
video_codec:
|
||||
description: Only for `camera` entities. FFmpeg video codec for transcoding. `copy` option reduces CPU load when video source already encoded with `H264` (MPEG4). `h264_omx` option is only available with custom FFmpeg builds and enables GPU Hardware acceleration on Raspberry Pi.
|
||||
required: false
|
||||
type: string
|
||||
default: libx264
|
||||
available options: copy, libx264, h264_omx
|
||||
audio_codec:
|
||||
description: Only for `camera` entities. FFmpeg audio codec for transcoding. `copy` option reduces CPU load when audio source already encoded with `libopus`.
|
||||
required: false
|
||||
type: string
|
||||
default: libopus
|
||||
available options: copy, libopus
|
||||
{% endconfiguration %}
|
||||
|
||||
## Setup
|
||||
@ -304,14 +318,14 @@ It is recommended to only edit a HomeKit instance in the UI that was created in
|
||||
|
||||
### Accessory mode
|
||||
|
||||
When exposing a Camera or Television media player (a `media_player` with device class `tv`) to HomeKit, `mode` must be set to `accessory`, and the include filter should be setup to only include a single entity.
|
||||
When exposing a Camera or Television media player (a `media_player` with device class `tv`) to HomeKit, `mode` must be set to `accessory`, and the include filter should be setup to only include a single entity.
|
||||
|
||||
To quickly add all accessory modes entities in the UI:
|
||||
|
||||
1. Create a new bridge via the UI (i.e., **{% my config_flow_start title="Configuration >> Integrations" domain=page.ha_domain %}**).
|
||||
2. Select `media_player` and `camera` domains.
|
||||
3. Complete the flow as normal.
|
||||
4. Additional HomeKit entries for each entity that must operate in accessory mode will be created for each entity that does not already have one.
|
||||
4. Additional HomeKit entries for each entity that must operate in accessory mode will be created for each entity that does not already have one.
|
||||
5. If you have already created another HomeKit bridge for the non-accessory mode entities, the new bridge can safely be removed.
|
||||
6. [Pair each bridge or accessory](#setup).
|
||||
|
||||
@ -383,7 +397,7 @@ Restart your Home Assistant instance. This feature requires running an mDNS forw
|
||||
If you have a firewall configured on your Home Assistant system, make sure you open the following ports:
|
||||
|
||||
- UDP: 5353
|
||||
- TCP: 51827 (or the configured/used `port` in the integration settings).
|
||||
- TCP: 21063 (or the configured/used `port` in the integration settings).
|
||||
|
||||
## Supported Components
|
||||
|
||||
@ -521,10 +535,6 @@ Pairing works fine when the filter is set to only include `demo.demo`, but fails
|
||||
1. Make sure that you don't try to add more than 150 accessories, see [device limit](#device-limit). In rare cases, one of your entities doesn't work with the HomeKit component. Use the [filter](#configure-filter) to find out which one. Feel free to open a new issue in the `home-assistant` repository, so we can resolve it.
|
||||
2. Check logs, and search for `Starting accessory Home Assistant Bridge on address`. Make sure Home Assistant Bridge hook up to a correct interface. If it did not, explicitly set `homekit.ip_address` configuration variable.
|
||||
|
||||
#### Duplicate AID found when attempting to add accessory
|
||||
|
||||
Two of your entities share the same `entity_id`. Either resolve this or configure the [filter](#configure-filter) to exclude them.
|
||||
|
||||
### Issues during normal use
|
||||
|
||||
#### Some of my devices don't show up - Z-Wave / Discovery
|
||||
@ -569,7 +579,6 @@ Media Player entities with `device_class: tv` will show up as Television accesso
|
||||
|
||||
The [Universal Media Player](/integrations/universal/#harmony-remote-example) has an example of how it can be used to wrap existing entities to enable them to be used as a Television accessory in HomeKit.
|
||||
|
||||
|
||||
#### Can't control volume of your TV media player?
|
||||
|
||||
The volume and play/pause controls will show up on the Remote app or Control Center. If your TV supports volume control through Home Assistant, you will be able to control the volume using the side volume buttons on the device while having the remote selected on screen.
|
||||
|
||||
@ -46,7 +46,7 @@ Device support is available for most of the wired and wireless devices, as well
|
||||
|
||||
<div class='note info'>
|
||||
|
||||
Since CCU Version 3, the internal firewalls are enabled by default. You have to grant full access for the `XML-RPC API` or specify the IP-address of the Home Assistant server and whitelist it, inside the CCU's security settings.
|
||||
Since CCU Version 3, the internal firewalls are enabled by default. You have to grant full access for the `XML-RPC API` or specify the IP-address of the Home Assistant instance and allowlist it, inside the CCU's security settings.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -66,7 +66,7 @@ ifttt:
|
||||
Property screen of the Maker Channel
|
||||
</p>
|
||||
|
||||
Once you have added your key to your `configuration.yaml` file, restart your Home Assistant server. This will load up the IFTTT integration and make a service available to trigger events in IFTTT.
|
||||
Once you have added your key to your `configuration.yaml` file, restart your Home Assistant instance. This will load up the IFTTT integration and make a service available to trigger events in IFTTT.
|
||||
|
||||
<div class='note'>
|
||||
After restarting the server, be sure to watch the console for any logging errors that show up in red, white or yellow.
|
||||
|
||||
@ -52,12 +52,12 @@ input_datetime:
|
||||
required: false
|
||||
type: string
|
||||
has_time:
|
||||
description: Set to `true` if the input should have a time. At least one `has_time` or `has_date` must be defined.
|
||||
description: Set to `true` if the input should have a time. At least one of `has_time` or `has_date` must be defined.
|
||||
required: false
|
||||
type: boolean
|
||||
default: false
|
||||
has_date:
|
||||
description: Set to `true` if the input should have a date. At least one `has_time` or `has_date` must be defined.
|
||||
description: Set to `true` if the input should have a date. At least one of `has_time` or `has_date` must be defined.
|
||||
required: false
|
||||
type: boolean
|
||||
default: false
|
||||
|
||||
@ -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 server 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 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.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/screenshots/locative.png'/>
|
||||
|
||||
@ -18,8 +18,8 @@ ha_platforms:
|
||||
- switch
|
||||
---
|
||||
|
||||
[Modbus](http://www.modbus.org/) is a serial communication protocol to control PLCs (Programmable logic controller).
|
||||
It currently supports sensors and switches which can be controlled over serial, TCP, and UDP connections.
|
||||
[Modbus](http://www.modbus.org/) is a serial communication protocol to control PLCs (Programmable Logic Controller).
|
||||
It supports various types of devices which can be controlled over serial, TCP, and UDP connections.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -54,7 +54,7 @@ port:
|
||||
name:
|
||||
description: Name for this hub. Must be unique, so it is required when setting up multiple instances.
|
||||
required: false
|
||||
default: default
|
||||
default: modbus_hub
|
||||
type: string
|
||||
timeout:
|
||||
description: Timeout for slave response in seconds.
|
||||
|
||||
@ -57,5 +57,5 @@ name:
|
||||
Send a mesage to Mycroft by calling `notify.mycroft` service:
|
||||
|
||||
```yaml
|
||||
message: "hey"
|
||||
message: "Hey Mycroft. Turn on the office light. "
|
||||
```
|
||||
|
||||
@ -57,5 +57,5 @@ Token: IHEDPEBEVA2WVHB7
|
||||
Copy and paste the token into your Home Assistant configuration and add it to your OTP generator. Verify that they generate the same code.
|
||||
|
||||
<div class='note warning'>
|
||||
It is vital that your system clock is correct both on your Home Assistant server and on your OTP generator device (e.g., your phone). If not, the generated codes will not match! Make sure NTP is running and syncing your time correctly before creating an issue.
|
||||
It is vital that your system clock is correct both on your Home Assistant instance and on your OTP generator device (e.g., your phone). If not, the generated codes will not match! Make sure NTP is running and syncing your time correctly before creating an issue.
|
||||
</div>
|
||||
|
||||
@ -23,18 +23,18 @@ Instructions on how to activate the API and if your model is supported can be fo
|
||||
| Feature | 1 | 5 | 6 (Android) | 6 (Saphi) |
|
||||
| ------------------ | ---------------- | --- | ------------------ | ---------------- |
|
||||
| Power On | WOL / IR Blaster | ? | Yes (if always on) | WOL / IR Blaster |
|
||||
| Volume Detect | Yes | ? | Yes (not over CEC) | ? |
|
||||
| Volume Up/Down | Yes | ? | Yes | No |
|
||||
| Volume Set | Yes | ? | Yes | ? |
|
||||
| Volume Detect | Yes | ? | Yes (not over CEC) | Yes |
|
||||
| Volume Up/Down | Yes | ? | Yes | Yes |
|
||||
| Volume Set | Yes | ? | Yes | Yes |
|
||||
| Source Select | Yes | ? | Yes | No |
|
||||
| Source Detect | Yes | ? | No | No |
|
||||
| Channel Select | Yes | ? | Yes | ? |
|
||||
| Channel Detect | Yes | ? | Yes | ? |
|
||||
| Channel Favorites | No | ? | Yes | ? |
|
||||
| Channel Select | Yes | ? | Yes | Yes |
|
||||
| Channel Detect | Yes | ? | Yes | No |
|
||||
| Channel Favorites | No | ? | Yes | Yes |
|
||||
| Application Select | No | ? | Yes | No |
|
||||
| Application Detect | No | ? | Yes | No |
|
||||
| Browse URL | No | No | No | No |
|
||||
| Send Key | No | No | No | No |
|
||||
| Send Key | No | No | No | Yes |
|
||||
| Ambilight Control | No | No | No | No |
|
||||
|
||||
### Turn on device
|
||||
|
||||
@ -62,7 +62,7 @@ variables:
|
||||
description: The value of the variable. Any YAML is valid. Templates can also be used to pass a value to the variable.
|
||||
type: any
|
||||
fields:
|
||||
description: "Information about the parameters that the script uses; see the [Passing variables to scripts](#passing-variables-to-scripts) section below. Please Note: In order for this description to be displayed in the Services tab of the Developer Tools in Lovelace, the script description must be defined as well."
|
||||
description: "Information about the parameters that the script uses; see the [Passing variables to scripts](#passing-variables-to-scripts) section below. Please note: In order for this description to be displayed in the Services tab of the Developer Tools, the script description must be defined as well."
|
||||
required: false
|
||||
default: {}
|
||||
type: map
|
||||
|
||||
@ -55,7 +55,7 @@ registers:
|
||||
hub:
|
||||
description: The name of the hub.
|
||||
required: false
|
||||
default: default
|
||||
default: modbus_hub
|
||||
type: string
|
||||
slave:
|
||||
description: The number of the slave (Optional for tcp and upd Modbus).
|
||||
|
||||
@ -190,7 +190,7 @@ sonos:
|
||||
- 192.0.2.27
|
||||
```
|
||||
|
||||
If your Home Assistant server has multiple IP addresses, you can provide the IP address that should be used for Sonos auto-discovery. This is rarely needed since all addresses should be tried by default.
|
||||
If your Home Assistant instance has multiple IP addresses, you can provide the IP address that should be used for Sonos auto-discovery. This is rarely needed since all addresses should be tried by default.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry using Sonos discovery on a specific interface
|
||||
|
||||
@ -68,7 +68,7 @@ No settings are required in the `configuration.yaml` other than `wink:`.
|
||||
After adding `wink:` to your `configuration.yaml` and restarting Home Assistant you will see a persistent notification on the frontend with a `CONFIGURE` button that will guide you through the setup via the frontend configurator.
|
||||
|
||||
<div class='note'>
|
||||
When using the configurator make sure the initial setup is performed on the same local network as the Home Assistant server, if not from the same box Home Assistant is running on. This will allow for authentication redirects to happen correctly.
|
||||
When using the configurator make sure the initial setup is performed on the same local network as the Home Assistant instance, if not from the same box Home Assistant is running on. This will allow for authentication redirects to happen correctly.
|
||||
</div>
|
||||
|
||||
```yaml
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
title: Wolf SmartSet Service
|
||||
description: Instructions on how to integrate Wolf Smart-Set cloud within Home Assistant.
|
||||
ha_category:
|
||||
- Heating
|
||||
- Climate
|
||||
ha_release: 0.114
|
||||
ha_iot_class: Cloud Polling
|
||||
ha_config_flow: true
|
||||
|
||||
@ -607,7 +607,7 @@ This model uses newer MiOT communication protocol.
|
||||
### Air Humidifier CA (zhimi.humidifier.ca4)
|
||||
|
||||
- On, Off
|
||||
- Operation modes (auto, low, mid, high)
|
||||
- Operation modes (auto, low, medium, high)
|
||||
- Buzzer (on, off)
|
||||
- Child lock (on, off)
|
||||
- LED brightness (off, dim, bright)
|
||||
|
||||
@ -52,7 +52,7 @@ There is also support for grouping of lights, switches, and fans (i.e. support f
|
||||
|
||||
## Compatible hardware
|
||||
|
||||
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).
|
||||
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.
|
||||
|
||||
@ -169,9 +169,9 @@ enable_quirks:
|
||||
|
||||
### OTA firmware updates
|
||||
|
||||
ZHA component does have the ability to automatically download and perform OTA (Over-The-Air) firmware updates of Zigbee devices if the OTA firmware provider source URL for updates is available. OTA firmware updating is set to disabled (`false`) in the configuration by default.
|
||||
ZHA component has the ability to automatically download and perform OTA (Over-The-Air) firmware updates of Zigbee devices if the OTA firmware provider source URL for updates is available. OTA firmware updating is set to disabled (`false`) in the configuration by default.
|
||||
|
||||
Currently, OTA providers for firmware updates are only available for IKEA and LEDVANCE devices. OTA updates for device of other manufactures could possible also be supported by ZHA dependencies in the future, if these manufacturers publish their firmware publicly.
|
||||
Currently, OTA providers for firmware updates are only available for IKEA and LEDVANCE devices. OTA updates for device of other manufactures could also be supported by ZHA dependencies in the future, if these manufacturers publish their firmware publicly.
|
||||
|
||||
To enable OTA firmware updates for the ZHA integration you need to add the following configuration to your `configuration.yaml` and restart Home Assistant:
|
||||
|
||||
@ -266,9 +266,9 @@ To add a new device:
|
||||
|
||||
### Using router devices
|
||||
|
||||
You use routers to increase the number of Zigbee devices that can be used in a network. The total number of Zigbee devices that you have on a Zigbee network depends on a few things, but you should know that Zigbee coordinator hardware and firmware only plays a larger role in Zigbee networks with a lot of devices. More important is how many directly connected devices ("direct children") versus how many routers are connected to your Zigbee coordinator. Zigpy library which ZHA uses has an upper limit is 32 direct children but if your Zigbee coordinator hardware is powerful enough then you can still have hundreds of Zigbee devices connected through routers.
|
||||
You use routers to increase the number of Zigbee devices that can be used in a network. The total number of Zigbee devices that you have on a Zigbee network depends on a few things, but you should know that Zigbee coordinator hardware and firmware only plays a larger role in Zigbee networks with a lot of devices. More important is how many directly connected devices ("direct children") versus how many routers are connected to your Zigbee coordinator. Zigpy library which ZHA uses has an upper limit. This is 32 direct children, but if your Zigbee coordinator hardware is powerful enough then you can still have hundreds of Zigbee devices connected through routers.
|
||||
|
||||
Even the least powerful Zigbee coordinator hardware supported by Zigpy is CC2530/2531 and its default firmware, only supports 20 devices connected directly to the coordinator. However, by having routers in your Zigbee network the mesh network size can be extended. You can assume that most, if not all mains/AC-powered devices, e.g., wall-plugs and always powered-on lightbulbs in your Zigbee network, can serve as a router. You can even use CC2530/CC2531 with router firmware, as additional routers (which in their turn have a limit of 21 devices).
|
||||
Even the least powerful Zigbee coordinator hardware supported by Zigpy is CC2530/2531 and its default firmware, only supports 20 devices connected directly to the coordinator. However, by having routers in your Zigbee network, the mesh network size can be extended. You can assume that most, if not all mains/AC-powered devices, e.g., wall-plugs and always powered-on lightbulbs in your Zigbee network can serve as a router. You can even use CC2530/CC2531 with router firmware, as additional routers (which in their turn have a limit of 21 devices).
|
||||
|
||||
An example using the default CC2531 coordinator firmware + two CC2531 routers; Your device limit will be:
|
||||
|
||||
@ -279,19 +279,19 @@ An example using the default CC2531 coordinator firmware + two CC2531 routers; Y
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
To help resolve any kinks or compatibility problems by reporting bugs as issues with debug logs. Please follow the instructions in this troubleshooting section.
|
||||
To help resolve any kinks or compatibility problems, report bugs as issues with debug logs. Please follow the instructions in this troubleshooting section.
|
||||
|
||||
### Knowing which devices are supported
|
||||
|
||||
There is no official compatibility list of supported devices for the simple reason that practically all devices Zigbee Home Automation that are fully compliant with the standards and specifications as set by the [Zigbee Alliance](https://zigbeealliance.org) the should technically be compatible with this ZHA integration. The fact however remains that some hardware manufacturers do not always fully comply with each set specification which can cause a few devices to only partially work or not work at all with ZHA, but developers can create workarounds for such issues via a solution for 'ZHA exception and deviation handling' that this implementation features, please see that section for more information.
|
||||
There is no official compatibility list of supported devices for the simple reason that practically all devices Zigbee Home Automation that are fully compliant with the standards and specifications as set by the [Zigbee Alliance](https://zigbeealliance.org) should technically be compatible with this ZHA integration. The fact remains, however, that some hardware manufacturers do not always fully comply with each set specification, which can cause a few devices to only partially work or not work at all with ZHA, but developers can create workarounds for such issues via a solution for 'ZHA exception and deviation handling' that this implementation features. See that section for more information.
|
||||
|
||||
Tip to new users is that while there is no official list of supported devices, some ZHA users take comfort that blakadder maintains an unofficial Zigbee Device Compatibility Repository which anyone can submit compatibility reports to, it can be found at [zigbee.blakadder.com](https://zigbee.blakadder.com) and currently contains independent compatibility lists and device pairing tips for several home automation gateway/bridge/hub software, including but not limited to open source Zigbee implementations such as; ZHA, Tasmota, Zigbee2MQTT, and ZiGate.
|
||||
Tip to new users is that, while there is no official list of supported devices, some ZHA users take comfort that blakadder maintains an unofficial Zigbee Device Compatibility Repository which anyone can submit compatibility reports to, it can be found at [zigbee.blakadder.com](https://zigbee.blakadder.com) and currently contains independent compatibility lists and device pairing tips for several home automation gateway/bridge/hub softwares, including but not limited to open source Zigbee implementations such as; ZHA, Tasmota, Zigbee2MQTT, and ZiGate.
|
||||
|
||||
### ZHA exception and deviation handling
|
||||
|
||||
The ZHA implementation in Home Assistant relies on a library called "[ZHA Device Handlers](https://github.com/zigpy/zha-device-handlers)" to resolve issues with Zigbee devices that do not fully conform with the Zigbee standards. The few devices that deviate from the Zigbee specifications set by the [Zigbee Alliance](https://zigbeealliance.org) may therefore require proper bug reports with debug logs from users to assistant the developers in writing custom [ZHA Device Handlers](https://github.com/zigpy/zha-device-handlers/blob/dev/README.md) for all of a device functions to work properly with the ZHA integration.
|
||||
|
||||
Such a custom "ZHA Device Handler" are Python scripts that internally is also referred to as a "quirk" because they fix "quirks" as in deviations from the standard specifications. ZHA Device Handles do this by transparently acting as a translator, translating and converting non-compliant device messages and instead present them to the application as coming from a virtual compliant device. These ZHA Device Handlers for Home Assistant can thus be used to parse custom messages to and from Zigbee devices. The ZHA Device Handlers that are made can then be reused by all users in future versions of Home Assistant.
|
||||
Such a custom "ZHA Device Handler" are Python scripts that internally are also referred to as a "quirk" because they fix "quirks", like deviations from the standard specifications. ZHA Device Handles do this by transparently, acting as a translator, translating and converting non-compliant device messages and instead present them to the application as coming from a virtual compliant device. These ZHA Device Handlers for Home Assistant can thus be used to parse custom messages to and from Zigbee devices. The ZHA Device Handlers that are made can then be reused by all users in future versions of Home Assistant.
|
||||
|
||||
The custom quirks implementations for zigpy implemented as ZHA Device Handlers for Home Assistant are a similar concept to that of [Hub-connected Device Handlers for the SmartThings Classics platform](https://docs.smartthings.com/en/latest/device-type-developers-guide/) as well as that of [Zigbee-Herdsman Converters (formerly Zigbee-Shepherd Converters) as used by Zigbee2mqtt](https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html), meaning they are each virtual representations of a physical device that expose additional functionality that is not provided out-of-the-box by the existing integration between these platforms.
|
||||
|
||||
|
||||
@ -213,7 +213,7 @@ An improvement in the battery of your device and your data cap are going to
|
||||
like:
|
||||
|
||||
When the Home Assistant UI is not visible for longer than 5 minutes, it
|
||||
disconnects from your Home Assistant server. This means you no longer get data or
|
||||
disconnects from your Home Assistant instance. This means you no longer get data or
|
||||
camera streams and your device can optimize resource and power consumption.
|
||||
|
||||
Of course, when showing the browser (or browser tab) again, it will
|
||||
|
||||
@ -13,7 +13,7 @@ Hey there, its been so long since we last gave an update on our mobile apps we t
|
||||
|
||||
## Manage Sensors
|
||||
|
||||
Starting from version 2.2.0 there is a new Manage Sensors screen that you can find under App Configuration. Users can now disable sensors they don't want while continuing to receive updates from the sensors they do care about. This includes turning off the Geocoded sensor while keeping location tracking on. Speaking of which the 2 location toggles that used to be found in App Configuration are now located in this new screen. You can expect to see the live data that was recently sent over to your Home Assistant server as well as the attributes and other sensor details.
|
||||
Starting from version 2.2.0 there is a new Manage Sensors screen that you can find under App Configuration. Users can now disable sensors they don't want while continuing to receive updates from the sensors they do care about. This includes turning off the Geocoded sensor while keeping location tracking on. Speaking of which the 2 location toggles that used to be found in App Configuration are now located in this new screen. You can expect to see the live data that was recently sent over to your Home Assistant instance as well as the attributes and other sensor details.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2020-08-28-android-230-release/manage_sensors.png' alt='Screenshot of Manage Sensors'></a>
|
||||
@ -27,7 +27,7 @@ Screenshot of Sensor Management.
|
||||
|
||||
## New Sensors
|
||||
|
||||
We have had quite a bit of sensors get added since we last spoke so here's whats new. Some of these sensors will update their state in your Home Assistant server upon certain state changes. All of the sensors listed below will also update during the normal 15 minute update interval. To get more details about what to expect from each sensor check out the [docs](https://companion.home-assistant.io/docs/core/sensors).
|
||||
We have had quite a bit of sensors get added since we last spoke so here's whats new. Some of these sensors will update their state in your Home Assistant instance upon certain state changes. All of the sensors listed below will also update during the normal 15 minute update interval. To get more details about what to expect from each sensor check out the [docs](https://companion.home-assistant.io/docs/core/sensors).
|
||||
|
||||
Available for Google Play Store version only:
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ Hey there, I hope everyone has been enjoying the last release of the Android app
|
||||
|
||||
Sometimes when we move really fast, we may move a bit too fast. While we had fun adding all the new sensors, we didn't stop to think about the new user experience and how we are making a burden on them by having non-static attributes for some of the sensors. In reality, these attributes are a state and we need to treat them as such. If we don't, there will be a need to use templates that are not user-friendly. We wanted to fix this issue and be courteous to our current users, so we have made a few changes. Some of which take place in this release and some in the following release after 2.4.0.
|
||||
|
||||
The first major change in this release is that the app will no longer send needless updates to your Home Assistant server when there is nothing new to report state-wise. This helps cut down on the amount of data that gets sent out. Some attributes attached to some sensors update outside of the state, to combat this change, we have split those attributes to become their own sensor. For example, the audio sensor had an attribute to tell if headphones were currently plugged into the device. This, by itself, is a state change and thus now a binary sensor.
|
||||
The first major change in this release is that the app will no longer send needless updates to your Home Assistant instance when there is nothing new to report state-wise. This helps cut down on the amount of data that gets sent out. Some attributes attached to some sensors update outside of the state, to combat this change, we have split those attributes to become their own sensor. For example, the audio sensor had an attribute to tell if headphones were currently plugged into the device. This, by itself, is a state change and thus now a binary sensor.
|
||||
|
||||
We have opted to keep the existing attributes where they are for this release, this way they do not break existing templates. However, they may trigger slower until you move to the new sensor. All of the new sensors are also disabled by default (with the exception of battery), so you may want to enable the ones you care for. The following sensors have had their attributes split up:
|
||||
|
||||
|
||||
@ -230,7 +230,7 @@ this means that this setting is device-based and will be cleared when you logout
|
||||
You can now upload images for a person in the frontend!
|
||||
|
||||
Select or drop an image in the input field and then crop it to a square. The
|
||||
image is stored on your Home Assistant server.
|
||||
image is stored on your Home Assistant instance.
|
||||
|
||||
<div class='videoWrapper'>
|
||||
<iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/rOlRnwaaT7Y" frameborder="0" allowfullscreen></iframe>
|
||||
|
||||
@ -55,9 +55,9 @@ Screenshot of location settings.
|
||||
</p>
|
||||
|
||||
- Next Alarm - This sensor has a setting for an allow list. This means that if you have an app that reports really odd timestamps as an actual alarm, you can now ignore them by telling the app which packages to send reports from. By default the list is blank. Tasker users are recommended to make use of this setting.
|
||||
- Last Notification - This sensor also has an allow list to let the user create a list of apps from which they want notification data from. By default all notifications are sent to your Home Assistant server. We highly recommend that you set up an allow list as soon as you can think of one to prevent a high amount of updates. You will be surprised by the amount of data that will show up in a short time period.
|
||||
- Last Notification - This sensor also has an allow list to let the user create a list of apps from which they want notification data from. By default all notifications are sent to your Home Assistant instance. We highly recommend that you set up an allow list as soon as you can think of one to prevent a high amount of updates. You will be surprised by the amount of data that will show up in a short time period.
|
||||
- Last Reboot - A bug was discovered where sometimes the timing in the calculation of the device's last reboot could be off causing an unnecessary update. There is now a deadband setting to allow you to adjust the timing to ignore updates. By default this is set to 1 minute, you most likely won't need to change this.
|
||||
- Location Sensors - All 3 location sensors now have settings to allow you to adjust the minimum accuracy required to send a update to your Home Assistant server. There is also a setting to adjust the minimum amount of time between updates. This should help a lot of users out who don't get the location results they expect. We recommend changing this setting after you evaluate all of the location fixes in 3.0.0 as location tracking may already be improved without needing to adjust these.
|
||||
- Location Sensors - All 3 location sensors now have settings to allow you to adjust the minimum accuracy required to send a update to your Home Assistant instance. There is also a setting to adjust the minimum amount of time between updates. This should help a lot of users out who don't get the location results they expect. We recommend changing this setting after you evaluate all of the location fixes in 3.0.0 as location tracking may already be improved without needing to adjust these.
|
||||
- WiFi BSSID - This sensor has a setting that will allow the user to provide an alias for the currently connected BSSID. Not everyone can remember a MAC address let alone dozens of them. This setting is designed to help out those who use this sensor to make better sense of things without the need for secrets or templates. If you live in a household with multiple access points you may find it useful to set up an alias to help with things like room presence. By default this sensor reports the connected MAC address.
|
||||
|
||||
|
||||
|
||||
@ -30,8 +30,8 @@ My oh my, enjoy this release!
|
||||
|
||||
- [My Home Assistant](#my-home-assistant)
|
||||
- [New UI for service calls](#new-ui-for-service-calls)
|
||||
- [Fan speeds: 100%](#fan-speeds-100)
|
||||
- [Suggested areas](#suggested-areas)
|
||||
- [Fan speeds: 100%](#fan-speeds-100)
|
||||
- [Z-Wave JS update](#z-wave-js-update)
|
||||
- [Flexible & variable automation triggers](#flexible--variable-automation-triggers)
|
||||
- [Oversettelser i Supervisor panelet](#oversettelser-i-supervisor-panelet)
|
||||
@ -39,6 +39,9 @@ My oh my, enjoy this release!
|
||||
- [New Integrations](#new-integrations)
|
||||
- [New Platforms](#new-platforms)
|
||||
- [Integrations now available to set up from the UI](#integrations-now-available-to-set-up-from-the-ui)
|
||||
- [Release 2021.3.1 - March 5](#release-202131---march-5)
|
||||
- [Release 2021.3.2 - March 5](#release-202132---march-5)
|
||||
- [Release 2021.3.3 - March 8](#release-202133---march-8)
|
||||
- [If you need help...](#if-you-need-help)
|
||||
- [Breaking Changes](#breaking-changes)
|
||||
- [Farewell to the following](#farewell-to-the-following)
|
||||
@ -160,7 +163,7 @@ We've introduced a protocol schema version in the Z-Wave JS server to allow
|
||||
older clients to connect and talk to a newer server. This prevents compatibility
|
||||
issues for the future!
|
||||
|
||||
Home Assistant Core 2021.3.0 will require Z-Wave JS server version 1.10.
|
||||
Home Assistant Core 2021.3.0 will require Z-Wave JS server version 1.1.0.
|
||||
If you're using the official Home Assistant add-on, the integration will
|
||||
automatically update the add-on if an older add-on and server version is
|
||||
encountered. Magic! If you're not using the Home Assistant add-on to run the
|
||||
@ -258,7 +261,7 @@ Screenshot of disabling an integration entry.
|
||||
- Thanks to [@Nixon506E], you can now set a transition time when activate Hue
|
||||
scenes.
|
||||
- In the {% my developer_states %} tab of the Developer Tools, there is now
|
||||
a small copy to clipboard button with each entity. Thanks, [@KTibow]!
|
||||
a small copy to clipboard button with each entity. Thanks, [@KTibow]!
|
||||
- [@postlund] added support for repeat, shuffle and volume stepping to the
|
||||
media player integration of the Apple TV integration.
|
||||
- [@larena1] reduced the amount of rendering history charts cause, so that
|
||||
@ -313,6 +316,202 @@ The following integrations are now available via the Home Assistant UI:
|
||||
- [Philips TV][philips_js docs], done by [@elupus]
|
||||
- [Xiaomi Miio][xiaomi_miio docs] (partially), done by [@starkillerOG]
|
||||
|
||||
## Release 2021.3.1 - March 5
|
||||
|
||||
- Fix Xiaomi Miio setup of switch entity for lumi.acpartner.v3 ([@starkillerOG] - [#47345]) ([xiaomi_miio docs])
|
||||
- Make zwave_js add-on manager more flexible ([@MartinHjelmare] - [#47356]) ([zwave_js docs])
|
||||
- Catch ConditionError in generic_thermostat climate ([@amelchio] - [#47359]) ([generic_thermostat docs])
|
||||
- Fix zwave_js manual reconfiguration of add-on managed entry ([@MartinHjelmare] - [#47364]) ([zwave_js docs])
|
||||
- Don't raise on known non-matching states in numeric state condition ([@frenck] - [#47378])
|
||||
- Fix access of missing zwave_js climate unit value ([@MartinHjelmare] - [#47380]) ([zwave_js docs])
|
||||
- Update frontend to 20210302.4 ([@bramkragten] - [#47383]) ([frontend docs])
|
||||
- Revert "Speed-up wemo discovery (#46821)" ([@esev] - [#47392]) ([wemo docs])
|
||||
- Fix RFLink TCP KeepAlive error log ([@cpainchaud] - [#47395]) ([rflink docs])
|
||||
- Map silent as a preset mode for fan backcompat ([@bdraco] - [#47396]) ([fan docs])
|
||||
- Fix measurement unit (Closes: #47390) ([@syssi] - [#47398]) ([xiaomi_miio docs])
|
||||
- Fix Climacell timezone issue with daily forecasts ([@raman325] - [#47402]) ([climacell docs])
|
||||
- Fix AirVisual exception when config entry contains old integration type ([@bachya] - [#47405]) ([airvisual docs])
|
||||
- Don't convert Climacell forecast temperatures to celsius because platform does it automatically ([@raman325] - [#47406]) ([climacell docs])
|
||||
- Bump zwave-js-server-python to 0.21.0 ([@raman325] - [#47408]) ([zwave_js docs])
|
||||
- Fix older Roborock models ([@frenck] - [#47412]) ([xiaomi_miio docs])
|
||||
- Only create snapshot if add-on update will be done ([@MartinHjelmare] - [#47424]) ([zwave_js docs])
|
||||
|
||||
[#47345]: https://github.com/home-assistant/core/pull/47345
|
||||
[#47356]: https://github.com/home-assistant/core/pull/47356
|
||||
[#47359]: https://github.com/home-assistant/core/pull/47359
|
||||
[#47364]: https://github.com/home-assistant/core/pull/47364
|
||||
[#47378]: https://github.com/home-assistant/core/pull/47378
|
||||
[#47380]: https://github.com/home-assistant/core/pull/47380
|
||||
[#47383]: https://github.com/home-assistant/core/pull/47383
|
||||
[#47392]: https://github.com/home-assistant/core/pull/47392
|
||||
[#47395]: https://github.com/home-assistant/core/pull/47395
|
||||
[#47396]: https://github.com/home-assistant/core/pull/47396
|
||||
[#47398]: https://github.com/home-assistant/core/pull/47398
|
||||
[#47402]: https://github.com/home-assistant/core/pull/47402
|
||||
[#47405]: https://github.com/home-assistant/core/pull/47405
|
||||
[#47406]: https://github.com/home-assistant/core/pull/47406
|
||||
[#47408]: https://github.com/home-assistant/core/pull/47408
|
||||
[#47412]: https://github.com/home-assistant/core/pull/47412
|
||||
[#47424]: https://github.com/home-assistant/core/pull/47424
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@amelchio]: https://github.com/amelchio
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@cpainchaud]: https://github.com/cpainchaud
|
||||
[@esev]: https://github.com/esev
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@starkillerOG]: https://github.com/starkillerOG
|
||||
[@syssi]: https://github.com/syssi
|
||||
[airvisual docs]: /integrations/airvisual/
|
||||
[climacell docs]: /integrations/climacell/
|
||||
[fan docs]: /integrations/fan/
|
||||
[frontend docs]: /integrations/frontend/
|
||||
[generic_thermostat docs]: /integrations/generic_thermostat/
|
||||
[rflink docs]: /integrations/rflink/
|
||||
[wemo docs]: /integrations/wemo/
|
||||
[xiaomi_miio docs]: /integrations/xiaomi_miio/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## Release 2021.3.2 - March 5
|
||||
|
||||
- Update pyotgw to 1.1b1 ([@mvn23] - [#47446]) ([opentherm_gw docs])
|
||||
- Fix issue at Netatmo startup ([@cgtobi] - [#47452]) ([netatmo docs])
|
||||
- Fix Hue scene overriding Hue default transition times ([@frenck] - [#47454]) ([hue docs])
|
||||
- Bump version with fix for v1 ([@elupus] - [#47458]) ([philips_js docs])
|
||||
- Update frontend to 20210302.5 ([@bramkragten] - [#47462]) ([frontend docs])
|
||||
- Use conn_made callback in MySensors ([@functionpointer] - [#47463]) ([mysensors docs])
|
||||
- Bump zwave-js-server-python to 0.21.1 ([@raman325] - [#47464]) ([zwave_js docs])
|
||||
- Raise error instead of crashing when template passed to call service target ([@balloob] - [#47467]) ([websocket_api docs])
|
||||
- Update zwave_js.refresh_value service description ([@raman325] - [#47469]) ([zwave_js docs])
|
||||
- Bump amcrest package version to 1.7.1 ([@pnbruckner] - [#47483]) ([amcrest docs])
|
||||
|
||||
[#47446]: https://github.com/home-assistant/core/pull/47446
|
||||
[#47452]: https://github.com/home-assistant/core/pull/47452
|
||||
[#47454]: https://github.com/home-assistant/core/pull/47454
|
||||
[#47458]: https://github.com/home-assistant/core/pull/47458
|
||||
[#47462]: https://github.com/home-assistant/core/pull/47462
|
||||
[#47463]: https://github.com/home-assistant/core/pull/47463
|
||||
[#47464]: https://github.com/home-assistant/core/pull/47464
|
||||
[#47467]: https://github.com/home-assistant/core/pull/47467
|
||||
[#47469]: https://github.com/home-assistant/core/pull/47469
|
||||
[#47483]: https://github.com/home-assistant/core/pull/47483
|
||||
[@balloob]: https://github.com/balloob
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@cgtobi]: https://github.com/cgtobi
|
||||
[@elupus]: https://github.com/elupus
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@functionpointer]: https://github.com/functionpointer
|
||||
[@mvn23]: https://github.com/mvn23
|
||||
[@pnbruckner]: https://github.com/pnbruckner
|
||||
[@raman325]: https://github.com/raman325
|
||||
[amcrest docs]: /integrations/amcrest/
|
||||
[frontend docs]: /integrations/frontend/
|
||||
[hue docs]: /integrations/hue/
|
||||
[mysensors docs]: /integrations/mysensors/
|
||||
[netatmo docs]: /integrations/netatmo/
|
||||
[opentherm_gw docs]: /integrations/opentherm_gw/
|
||||
[philips_js docs]: /integrations/philips_js/
|
||||
[websocket_api docs]: /integrations/websocket_api/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## Release 2021.3.3 - March 8
|
||||
|
||||
- Adjust litterrobot tests and code to match guidelines ([@natekspencer] - [#47060]) ([litterrobot docs])
|
||||
- Bump HAP-python to 3.4.0 ([@bdraco] - [#47476]) ([homekit docs])
|
||||
- Fix Sonos polling mode ([@amelchio] - [#47498]) ([sonos docs])
|
||||
- Fix mysensors notify platform ([@MartinHjelmare] - [#47517]) ([mysensors docs])
|
||||
- Fix AsusWRT wrong api call ([@ollo69] - [#47522]) ([asuswrt docs])
|
||||
- Bump pymysensors to 0.21.0 ([@MartinHjelmare] - [#47530]) ([mysensors docs])
|
||||
- Fix mysensors device tracker ([@MartinHjelmare] - [#47536]) ([mysensors docs])
|
||||
- Fix mysensors unload clean up ([@MartinHjelmare] - [#47541]) ([mysensors docs])
|
||||
- Correct weather entities forecast time ([@dgomes] - [#47565])
|
||||
- Allow running and restarting with both ozw and zwave active ([@ronytomen] - [#47566]) ([ozw docs]) ([zwave docs])
|
||||
- Add fallback zwave_js entity name using node ID ([@raman325] - [#47582]) ([zwave_js docs])
|
||||
- Ensure bond devices recover when wifi disconnects and reconnects ([@bdraco] - [#47591]) ([bond docs])
|
||||
- Update frontend to 20210302.6 ([@bramkragten] - [#47592]) ([frontend docs])
|
||||
- Fix turn on without speed in homekit controller ([@bdraco] - [#47597]) ([homekit_controller docs])
|
||||
- Ensure template fan value_template always determines on state ([@bdraco] - [#47598]) ([template docs])
|
||||
- Fix insteon fan speeds ([@bdraco] - [#47603]) ([insteon docs])
|
||||
- Fix turning off scene in homekit ([@bdraco] - [#47604]) ([homekit docs])
|
||||
- Fix Shelly logbook exception when missing COAP ([@thecode] - [#47620]) ([shelly docs])
|
||||
- Update zwave_js supported features list to be static ([@raman325] - [#47623]) ([zwave_js docs])
|
||||
|
||||
[#47060]: https://github.com/home-assistant/core/pull/47060
|
||||
[#47476]: https://github.com/home-assistant/core/pull/47476
|
||||
[#47498]: https://github.com/home-assistant/core/pull/47498
|
||||
[#47517]: https://github.com/home-assistant/core/pull/47517
|
||||
[#47522]: https://github.com/home-assistant/core/pull/47522
|
||||
[#47530]: https://github.com/home-assistant/core/pull/47530
|
||||
[#47536]: https://github.com/home-assistant/core/pull/47536
|
||||
[#47541]: https://github.com/home-assistant/core/pull/47541
|
||||
[#47565]: https://github.com/home-assistant/core/pull/47565
|
||||
[#47566]: https://github.com/home-assistant/core/pull/47566
|
||||
[#47582]: https://github.com/home-assistant/core/pull/47582
|
||||
[#47591]: https://github.com/home-assistant/core/pull/47591
|
||||
[#47592]: https://github.com/home-assistant/core/pull/47592
|
||||
[#47597]: https://github.com/home-assistant/core/pull/47597
|
||||
[#47598]: https://github.com/home-assistant/core/pull/47598
|
||||
[#47603]: https://github.com/home-assistant/core/pull/47603
|
||||
[#47604]: https://github.com/home-assistant/core/pull/47604
|
||||
[#47620]: https://github.com/home-assistant/core/pull/47620
|
||||
[#47623]: https://github.com/home-assistant/core/pull/47623
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@amelchio]: https://github.com/amelchio
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@dgomes]: https://github.com/dgomes
|
||||
[@natekspencer]: https://github.com/natekspencer
|
||||
[@ollo69]: https://github.com/ollo69
|
||||
[@raman325]: https://github.com/raman325
|
||||
[@ronytomen]: https://github.com/ronytomen
|
||||
[@thecode]: https://github.com/thecode
|
||||
[asuswrt docs]: /integrations/asuswrt/
|
||||
[bond docs]: /integrations/bond/
|
||||
[frontend docs]: /integrations/frontend/
|
||||
[homekit docs]: /integrations/homekit/
|
||||
[homekit_controller docs]: /integrations/homekit_controller/
|
||||
[insteon docs]: /integrations/insteon/
|
||||
[litterrobot docs]: /integrations/litterrobot/
|
||||
[mysensors docs]: /integrations/mysensors/
|
||||
[ozw docs]: /integrations/ozw/
|
||||
[shelly docs]: /integrations/shelly/
|
||||
[sonos docs]: /integrations/sonos/
|
||||
[template docs]: /integrations/template/
|
||||
[zwave docs]: /integrations/zwave/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
## Release 2021.3.4 - March 12
|
||||
|
||||
- Write SimpliSafe alarm control panel state after arming/disarming ([@bachya] - [#47649]) ([simplisafe docs])
|
||||
- Cover Tilt Position Bugfix ([@mtl010957] - [#47682]) ([mqtt docs])
|
||||
- Fix zwave_js target_temp_low ([@firstof9] - [#47762]) ([zwave_js docs])
|
||||
- Adjust insteon fan speed range to valid upper bound ([@bdraco] - [#47765]) ([insteon docs])
|
||||
- Bump plexapi to 4.4.1 ([@jjlawren] - [#47766]) ([plex docs])
|
||||
- Ensure homekit reset accessory service can target any entity ([@bdraco] - [#47787]) ([homekit docs])
|
||||
- Fix Netatmo event handling ([@cgtobi] - [#47792]) ([netatmo docs])
|
||||
|
||||
[#47649]: https://github.com/home-assistant/core/pull/47649
|
||||
[#47682]: https://github.com/home-assistant/core/pull/47682
|
||||
[#47762]: https://github.com/home-assistant/core/pull/47762
|
||||
[#47765]: https://github.com/home-assistant/core/pull/47765
|
||||
[#47766]: https://github.com/home-assistant/core/pull/47766
|
||||
[#47787]: https://github.com/home-assistant/core/pull/47787
|
||||
[#47792]: https://github.com/home-assistant/core/pull/47792
|
||||
[@bachya]: https://github.com/bachya
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@cgtobi]: https://github.com/cgtobi
|
||||
[@firstof9]: https://github.com/firstof9
|
||||
[@jjlawren]: https://github.com/jjlawren
|
||||
[@mtl010957]: https://github.com/mtl010957
|
||||
[homekit docs]: /integrations/homekit/
|
||||
[insteon docs]: /integrations/insteon/
|
||||
[mqtt docs]: /integrations/mqtt/
|
||||
[netatmo docs]: /integrations/netatmo/
|
||||
[plex docs]: /integrations/plex/
|
||||
[simplisafe docs]: /integrations/simplisafe/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## If you need help...
|
||||
|
||||
...don't hesitate to use our very active [forums](https://community.home-assistant.io/) or join us for a little [chat](https://discord.gg/c5DvZ4e).
|
||||
@ -670,7 +869,7 @@ Everything was still discovered in testing on a server with multiple interfaces.
|
||||
|
||||
{% details "Z-Wave JS" %}
|
||||
|
||||
Minimum required zwave-js-server version is now 1.0.0.
|
||||
Minimum required zwave-js-server version is now 1.1.0.
|
||||
You need to run this server version at mimimum for the integration to work.
|
||||
|
||||
([@marcelveldt] - [#46983]) ([zwave_js docs])
|
||||
|
||||
112
source/_posts/2021-03-05-community-highlights.markdown
Normal file
112
source/_posts/2021-03-05-community-highlights.markdown
Normal file
@ -0,0 +1,112 @@
|
||||
---
|
||||
title: "Community Highlights: 11th edition"
|
||||
description: "Automatically take snapshots of movement on your camera, build your own birdhouse with a weather station or get started with your lighting in the garden."
|
||||
date: 2021-03-05 00:00:00
|
||||
date_formatted: "March 5, 2021"
|
||||
author: Klaas Schoute
|
||||
author_twitter: klaasnicolaas
|
||||
categories: Community
|
||||
og_image: /images/blog/2021-03-05-community-highlights/social.png
|
||||
---
|
||||
|
||||
The 11th edition of the Home Assistant Community Highlights! Some interesting
|
||||
things popped up around our community, we thought was worth sharing.
|
||||
|
||||
From now on we will also highlight a cool blueprint that we encountered on the
|
||||
[Blueprint exchange][blueprints]. Do you want to share something for the next edition?
|
||||
Information on [how to share](#got-a-tip-for-the-next-edition).
|
||||
|
||||
./Klaas
|
||||
|
||||
## Blueprint of the week
|
||||
|
||||
Do you have an IP camera in Home Assistant instance and do you no longer want to miss
|
||||
who is at the door? Then you could try the camera snapshot Blueprint from
|
||||
[vorion](https://community.home-assistant.io/u/vorion). You can also indicate to which
|
||||
device you would like to receive a notification with a photo.
|
||||
[Try it out!](https://community.home-assistant.io/t/send-camera-snapshot-notification-on-motion/254565)
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://community.home-assistant.io/t/send-camera-snapshot-notification-on-motion/254565" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-03-05-community-highlights/blueprint.jpeg'
|
||||
alt="How this blueprint works"
|
||||
style='border: 0;box-shadow: none;width:70%;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
## Solar weather station in birdhouse
|
||||
|
||||
Spring is approaching, so it's a good time to start building a birdhouse 🐦, so why not
|
||||
immediately turn it into a weather station? With [the manual](https://www.martinvdm.nl/2020/08/03/solar-weather-station-in-birdhouse/)
|
||||
from Martin, you can make your own weather (birdhouse) station that works with ESPHome.
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://www.martinvdm.nl/2020/08/03/solar-weather-station-in-birdhouse/" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-03-05-community-highlights/birdhouse.png'
|
||||
alt="What the birdhouse will eventually look like"
|
||||
style='border: 0;box-shadow: none;width: 70%;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
## Outdoor pathway light
|
||||
|
||||
Do you have a garden and do you want to create lighting along the paths? Maybe the
|
||||
garden lighting tutorial from [KidA001](https://www.reddit.com/user/KidA001/) will give you some inspiration to
|
||||
[get started](https://www.reddit.com/r/homeassistant/comments/lt40gb/made_my_own_outdoor_pathway_lights_with_esphome/) with this.
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://www.reddit.com/r/homeassistant/comments/lt40gb/made_my_own_outdoor_pathway_lights_with_esphome/" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-03-05-community-highlights/garden.png'
|
||||
alt="Example of the garden pathway light"
|
||||
style='border: 0;box-shadow: none;width: 70%;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
## PoE powered stack light
|
||||
|
||||
Looking for a creative way to display the status of your Home Assistant instance?
|
||||
For example: there is a new Core update, too much RAM is being used or your instance
|
||||
is no longer online? Plenty of options to bind to each color segment.
|
||||
|
||||
So let yourself be inspired with the PoE stack light from Karl and start
|
||||
[building](https://karlquinsland.com/2021/02/poe-powered-stack-light/).
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://karlquinsland.com/2021/02/poe-powered-stack-light/" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-03-05-community-highlights/stacklight.png'
|
||||
alt="The PoE stack light in operation"
|
||||
style='border: 0;box-shadow: none;width: 70%;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
## Got a tip for the next edition?
|
||||
|
||||
Have you seen (or made) something awesome, interesting, unique, amazing,
|
||||
inspirational, unusual or funny, using Home Assistant?
|
||||
|
||||
[Click here to send us your Community Highlight suggestion](/suggest-community-highlight).
|
||||
|
||||
Also, don't forget to share your creations with us via Social Media:
|
||||
|
||||
- Twitter it! Be sure to mention [@home_assistant][twitter]
|
||||
- Share it on our [Facebook group][facebook-group]
|
||||
- Post it to our [subreddit][reddit]
|
||||
- Tag [@homeasssistant][instagram] on Instagram
|
||||
- Or via chat, drop us a line in the [#lounge at Discord][chat]
|
||||
|
||||
See you next edition!
|
||||
|
||||
[chat]: https://www.home-assistant.io/join-chat
|
||||
[facebook-group]: https://www.facebook.com/groups/HomeAssistant/
|
||||
[instagram]: https://www.instagram.com/homeassistant/
|
||||
[reddit]: https://www.reddit.com/r/homeassistant
|
||||
[twitter]: https://www.twitter.com/home_assistant
|
||||
[blueprints]: https://community.home-assistant.io/c/blueprints-exchange
|
||||
99
source/_posts/2021-03-06-android-2021-q1-releases.markdown
Normal file
99
source/_posts/2021-03-06-android-2021-q1-releases.markdown
Normal file
@ -0,0 +1,99 @@
|
||||
---
|
||||
title: "Home Assistant Companion Android App 2021 Q1 Releases"
|
||||
description: "2021 Q1 Updates for the Home Assistant Companion Android App"
|
||||
date: 2021-03-04 00:00:00
|
||||
date_formatted: "March 4, 2021"
|
||||
comments: true
|
||||
author: Daniel Shokouhi
|
||||
categories: Release-Notes
|
||||
og_image: /images/blog/2021-03-06-android-q1-releases/Companion.png
|
||||
---
|
||||
|
||||
Hey everyone! It has been quite some time since we last provided an update on all that is new with the Android app. You may have already noticed that we had changed our release versioning to match that of Home Assistant Core. In fact, we will be attempting to align our releases more closely to Core releases. This way we can start supporting brand new features quickly, like the recently released [My Home Assistant](https://my.home-assistant.io).
|
||||
|
||||
## Security Check
|
||||
|
||||
As of Home Assistant Core 2021.1.5 some [security vulnerabilities](https://www.home-assistant.io/blog/2021/01/23/security-disclosure2/) were fixed and it is very critical that all users update their instances to at least this version. The app will now do a check every 24 hours to ensure that the instance is at least on the release mentioned in the security alert. This check will be updated anytime a new security alert is issued.
|
||||
|
||||
## Location Disabled Check
|
||||
|
||||
Certain app features that depend on the connected WiFi network (SSID), require the location permission to not only be granted to the app, but also have it enabled on the device. Without this, the app is unable to read the connected SSID, impacting usage of the Internal URL and any WiFi based sensors. Previously, the application would continue to function and silently fail while showing bad data for the sensors. Although the application still worked, certain parts were found to be buggy as a result of the silent failure.
|
||||
|
||||
Starting in android-2021.1, the app was showing a prompt before a user was able to interact with the Home Assistant frontend. We received feedback that users found this pop-up to be too intrusive. Starting `android-2021.2`, this pop-up has been converted to a persistent Android notification with its own notification channel. This allows the user to fully control how it is displayed on the device, including turning the channel off. The new channel name for this notification is `Location disabled`.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-03-06-android-q1-releases/location_disabled.png' alt='Screenshot of the location disabled notification'></a>
|
||||
Screenshot of the location disabled notification.
|
||||
</p>
|
||||
|
||||
## High Accuracy Mode
|
||||
|
||||
High accuracy mode is a new feature in android-2021.2 to allow users to get much faster location updates at the cost of additional battery drain. Background location updates typically get reported every 30 seconds to a few minutes. This new feature allows the user to specify the update interval that defaults to every 5 seconds. When enabled, a persistent notification will be displayed containing some location data. This feature is an enhancement to the Background Location sensor and you can access it from the sensor settings screen. You can also control this feature via a new notification command to enable/disable it on the fly. You can learn more about this feature in the [documentation](https://companion.home-assistant.io/docs/core/location#high-accuracy-mode).
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-03-06-android-q1-releases/high_accuracy.png' alt='Screenshot of the high accuracy mode notification'></a>
|
||||
Screenshot of the high accuracy mode notification.
|
||||
</p>
|
||||
|
||||
## New Sensors
|
||||
|
||||
We have several new sensors to welcome to the app, all of which are disabled by default:
|
||||
|
||||
- [Active Notifications](https://companion.home-assistant.io/docs/core/sensors#active-notification) - The total count of active notifications visible to the user. Attributes will include all notification data.
|
||||
|
||||
- [App Data Sensors](https://companion.home-assistant.io/docs/core/sensors#app-data-sensors) - Sensors to determine how much data the app has used since the last device reboot.
|
||||
|
||||
- [App Importance Sensor](https://companion.home-assistant.io/docs/core/sensors#app-importance-sensor) - A sensor to determine if the app is in the `foreground`, `background` or any other importance level.
|
||||
|
||||
- [App Memory Sensor](https://companion.home-assistant.io/docs/core/sensors#app-memory-sensor) - A sensor to determine how much memory is used by the app.
|
||||
|
||||
- [App Usage sensors](https://companion.home-assistant.io/docs/core/sensors#app-usage-sensors) - Sensors to help users troubleshoot if the app is considered inactive and the current app standby bucket.
|
||||
|
||||
- [BLE Transmitter Sensor](https://companion.home-assistant.io/docs/core/sensors#bluetooth-sensors) - A sensor to control whether or not the app is actively sending out a beacon to provide support for services like [Room Assistant](https://www.room-assistant.io/).
|
||||
|
||||
- [Sleep Sensors](https://companion.home-assistant.io/docs/core/sensors#activity-sensors) - Sensors based on a new API provided by Google for devices running the full version. These sensors can be used to determine if the user is sleeping or not. The sensors update when we get data from Google so don't expect them to update as soon as you fall asleep.
|
||||
|
||||
|
||||
## Notification Enhancements
|
||||
|
||||
There have been several additions and improvements to notifications:
|
||||
|
||||
- Controlling Bluetooth
|
||||
- Broadcast intent command has been updated to allow the user to send intent extras
|
||||
- A command to launch activities, see [below](#intents-and-activities) for more details
|
||||
- A new command to launch the application to any dashboard or view without needing to click on anything
|
||||
- A new actionable notification type `REPLY` which will add a reply button to the notification and the response will be sent back in the `mobile_app_notification_action` event
|
||||
- A command to control whether or not the BLE transmitter sensor is enabled
|
||||
|
||||
## Intents and Activities
|
||||
|
||||
We have made several enhancements to further integrate Home Assistant into the Android ecosystem. First and foremost, the [Last Update Trigger sensor](https://companion.home-assistant.io/docs/core/sensors#last-update-trigger-sensor) was updated in 2021.2 to allow users to register for any intent that they want. [Intents](https://developer.android.com/guide/components/intents-filters) are a way for applications to communicate with another so they can send data back and forth. In fact the app itself uses many intents provided by Android, which is why certain sensors update faster than others. This means that users can now get data from apps that have an Intent API. You will need to know the intent action string that you wish to register for. Once the intent is received the application will fire an event to Home Assistant as `android.intent_received` along with the intent action and any extra data provided by the intent. Personally, I am using my Mi Band 5 with the [Notify for Mi Band](https://play.google.com/store/apps/details?id=com.mc.miband1) application that sends out intents for when I have fallen asleep, my step count or even my heart rate.
|
||||
|
||||
A new notification command was added to allow the user to launch an activity on their android device. This command requires a new permission to be granted in order to launch activities from the background, Draw Over Other Apps. The first attempt to use this notification will take the user to the permission page so the user can grant proper access. It is important to note that if the app is not considered active then this permission page will not show up due to missing permissions. Try to test this with the app open or you can grant the permission manually in your device settings. There are lots of use cases for this feature such as being able to launch Google Maps driving mode or even setting an alarm on your device.
|
||||
|
||||
Unfortunately, it is not so straightforward to determine which intents and activities are supported by applications. You really need to know what to look for and there is not much in terms of documentation here from applications. Try reaching out to the developers of your favorite apps to see if they have any intents to consume. We have provided several live examples in the [companion documentation](https://companion.home-assistant.io/docs/notifications/notification-commands#activity). I have also started a new thread in the forums to maintain a list of all that we can find [here](https://community.home-assistant.io/t/android-intents-sending-receiving-list-starting-activities-too/276192). I will be trying to keep the first post as up to date as possible.
|
||||
|
||||
## Other Enhancements
|
||||
|
||||
We have also spent time making improvements to all other areas too:
|
||||
|
||||
- Support for links from [My Home Assistant](https://my.home-assistant.io)
|
||||
- Power menu fixes and enhancements including support for vacuum entities
|
||||
- Haptic feedback support in the frontend
|
||||
- Overriding certain URL types to launch an application or an intent from the frontend
|
||||
- 3 finger swipe down gesture to trigger the [Quick Bar](https://www.home-assistant.io/docs/tools/quick-bar/)
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2021-03-06-android-q1-releases/3_finger_swipe_gesture.gif' alt='3 finger swipe gesture to trigger Quick Bar' height='550'></a>
|
||||
3 finger swipe gesture to trigger Quick Bar
|
||||
</p>
|
||||
|
||||
Big thank you to everyone involved. Please keep those bug reports and feature requests coming!
|
||||
|
||||
## Changelogs
|
||||
|
||||
- 2021.1.1 - https://github.com/home-assistant/android/releases/tag/2021.1.1
|
||||
- 2021.1.2 - https://github.com/home-assistant/android/releases/tag/2021.1.2
|
||||
- 2021.2.1 - https://github.com/home-assistant/android/releases/tag/2021.2.1
|
||||
- 2021.2.2 - https://github.com/home-assistant/android/releases/tag/2021.2.2
|
||||
- 2021.3.1 - https://github.com/home-assistant/android/releases/tag/2021.3.1
|
||||
122
source/_posts/2021-03-12-community-highlights.markdown
Normal file
122
source/_posts/2021-03-12-community-highlights.markdown
Normal file
@ -0,0 +1,122 @@
|
||||
---
|
||||
title: "Community Highlights: 12th edition"
|
||||
description: "Create your own smart pet feeder, show values of your house on an ePaper display and a delicious Home Assistant cake."
|
||||
date: 2021-03-12 00:00:00
|
||||
date_formatted: "March 12, 2021"
|
||||
author: Klaas Schoute
|
||||
author_twitter: klaasnicolaas
|
||||
categories: Community
|
||||
og_image: /images/blog/2021-03-12-community-highlights/social.png
|
||||
---
|
||||
|
||||
The 12th edition of the Home Assistant Community Highlights! Some interesting
|
||||
things popped up around our community, we thought was worth sharing.
|
||||
|
||||
Do you want to share something for the next edition?
|
||||
Information on [how to share](#got-a-tip-for-the-next-edition).
|
||||
|
||||
./Klaas
|
||||
|
||||
## Blueprint of the week
|
||||
|
||||
Do you have a number of domain names and would you like to track when an SSL
|
||||
certificate expires? Then you could try [bkbilly's](https://community.home-assistant.io/u/bkbilly)
|
||||
blueprint that automatically sends you a notification when a sensor exceeds your set threshold value.
|
||||
[Try it out!](https://community.home-assistant.io/t/certificate-expiration/280125)
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://community.home-assistant.io/t/certificate-expiration/280125" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-03-12-community-highlights/blueprint.png'
|
||||
alt="How this blueprint works"
|
||||
style='border: 0;box-shadow: none;width:90%;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
Also, take a look at the [Blueprint Exchange][blueprints] for more inspiration!
|
||||
|
||||
## Birthday cake
|
||||
|
||||
Happy birthday to [adlawton](https://www.reddit.com/user/adlawton/)! 🥳 For his birthday,
|
||||
his wife baked this great Home Assistant cake and also gave him a [Home Assistant Blue](/blue).
|
||||
|
||||
<blockquote class="reddit-card" data-card-created="1615556016"><a href="https://www.reddit.com/r/homeassistant/comments/lz5s6s/my_wife_decided_to_bake_me_a_cake_to_go_along/">My wife decided to bake me a cake to go along with my birthday present this year. Can't wait to fire this thing up!</a> from <a href="http://www.reddit.com/r/homeassistant">r/homeassistant</a></blockquote>
|
||||
<script async src="//embed.redditmedia.com/widgets/platform.js" charset="UTF-8"></script>
|
||||
|
||||
Hopefully, the cake tasted delicious and have fun with your Blue!
|
||||
|
||||
## ePaper display
|
||||
|
||||
[maxmacstn](https://github.com/maxmacstn) shared a really cool project on our
|
||||
Home Assistant [subreddit][reddit] page. It allows you to display sensor data from,
|
||||
for example, a room on an ePaper display. It works with ESPHome and you can also neatly
|
||||
finish this with a 3D printed case.
|
||||
|
||||
<object type="image/svg+xml" data="https://gh-card.dev/repos/maxmacstn/HA-ePaper-Display.svg?link_target=_blank"></object>
|
||||
|
||||
<blockquote class="reddit-card" data-card-created="1615556565"><a href="https://www.reddit.com/r/homeassistant/comments/lwp709/my_diy_epaper_sensor_display/">My DIY E-Paper Sensor Display</a> from <a href="http://www.reddit.com/r/homeassistant">r/homeassistant</a></blockquote>
|
||||
<script async src="//embed.redditmedia.com/widgets/platform.js" charset="UTF-8"></script>
|
||||
|
||||
## Hass Workstation Service
|
||||
|
||||
For those who would like to read their webcam status on a Windows machine, there is
|
||||
finally a solution! [sleevezipper](https://github.com/sleevezipper) has written a program
|
||||
that you can install on windows and that can send data to your Home Assistant instance over
|
||||
MQTT, in the background as a service.
|
||||
|
||||
<object type="image/svg+xml" data="https://gh-card.dev/repos/sleevezipper/hass-workstation-service.svg?link_target=_blank"></object>
|
||||
|
||||
<a href="https://github.com/sleevezipper" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-03-12-community-highlights/workstation.png'
|
||||
alt="UI of the workstation service program on Windows"
|
||||
style='border: 0;box-shadow: none;width:90%;'
|
||||
/>
|
||||
</a>
|
||||
|
||||
You can finally switch the lights automatically when you are in an online meeting 😉
|
||||
|
||||
_Note: If you’re on MacOS, you can achieve the same using the [Home Assistant Companion app for MacOS][companion]._
|
||||
|
||||
## Smart pet feeder
|
||||
|
||||
Would you like to automate feeding your pets? Then try the project of
|
||||
[Sokolsok](https://www.reddit.com/user/Sokolsok/), who has turned it into a very cool
|
||||
project with its own PCB and 3D printed design.
|
||||
|
||||
<p class='img'>
|
||||
<a href="https://smartsolutions4home.com/ss4h-pf-pet-feeder/" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-03-12-community-highlights/feeder.jpg'
|
||||
alt="How the smart pet feeder looks like"
|
||||
style='border: 0;box-shadow: none;'
|
||||
/>
|
||||
</a>
|
||||
You can read more about this project via <a target="_blank" href="https://smartsolutions4home.com/ss4h-pf-pet-feeder/">this website</a>.
|
||||
</p>
|
||||
|
||||
## Got a tip for the next edition?
|
||||
|
||||
Have you seen (or made) something awesome, interesting, unique, amazing,
|
||||
inspirational, unusual or funny, using Home Assistant?
|
||||
|
||||
[Click here to send us your Community Highlight suggestion](/suggest-community-highlight).
|
||||
|
||||
Also, don't forget to share your creations with us via Social Media:
|
||||
|
||||
- Tweet it! Be sure to mention [@home_assistant][twitter]
|
||||
- Share it on our [Facebook group][facebook-group]
|
||||
- Post it to our [subreddit][reddit]
|
||||
- Tag [@homeasssistant][instagram] on Instagram
|
||||
- Or via chat, drop us a line in the [#lounge at Discord][chat]
|
||||
|
||||
See you next edition!
|
||||
|
||||
[chat]: https://www.home-assistant.io/join-chat
|
||||
[facebook-group]: https://www.facebook.com/groups/HomeAssistant/
|
||||
[instagram]: https://www.instagram.com/homeassistant/
|
||||
[reddit]: https://www.reddit.com/r/homeassistant
|
||||
[twitter]: https://www.twitter.com/home_assistant
|
||||
[blueprints]: https://community.home-assistant.io/c/blueprints-exchange
|
||||
[companion]: https://companion.home-assistant.io
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Common Tasks"
|
||||
title: "Common Tasks - Container"
|
||||
description: "Common tasks for Home Assistant Container"
|
||||
installation: container
|
||||
---
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Common Tasks"
|
||||
title: "Common Tasks - Core"
|
||||
description: "Common tasks for Home Assistant Core"
|
||||
installation: core
|
||||
---
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Common Tasks"
|
||||
title: "Common Tasks - Operating System"
|
||||
description: "Common tasks for Home Assistant Operating System"
|
||||
installation: os
|
||||
installation_name: "Operating System"
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: "Common Tasks"
|
||||
title: "Common Tasks - Supervised"
|
||||
description: "Common tasks for Home Assistant Supervised"
|
||||
installation: supervised
|
||||
installation_name: Supervised
|
||||
|
||||
BIN
source/images/blog/2021-03-05-community-highlights/birdhouse.png
Normal file
BIN
source/images/blog/2021-03-05-community-highlights/birdhouse.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 776 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 229 KiB |
BIN
source/images/blog/2021-03-05-community-highlights/garden.png
Normal file
BIN
source/images/blog/2021-03-05-community-highlights/garden.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 4.2 MiB |
BIN
source/images/blog/2021-03-05-community-highlights/social.png
Normal file
BIN
source/images/blog/2021-03-05-community-highlights/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 353 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.2 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 617 KiB |
BIN
source/images/blog/2021-03-06-android-q1-releases/Companion.png
Normal file
BIN
source/images/blog/2021-03-06-android-q1-releases/Companion.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 112 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 81 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 108 KiB |
BIN
source/images/blog/2021-03-12-community-highlights/blueprint.png
Normal file
BIN
source/images/blog/2021-03-12-community-highlights/blueprint.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
BIN
source/images/blog/2021-03-12-community-highlights/feeder.jpg
Normal file
BIN
source/images/blog/2021-03-12-community-highlights/feeder.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 852 KiB |
BIN
source/images/blog/2021-03-12-community-highlights/social.png
Normal file
BIN
source/images/blog/2021-03-12-community-highlights/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 375 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
@ -9,29 +9,29 @@ toc: true
|
||||
|
||||
<div class="intro">
|
||||
<p>
|
||||
Home Assistant offers four different installation methods. We recommend one of the following two:
|
||||
Home Assistant offers four different installation methods. We recommend using one of the following two methods:
|
||||
</p>
|
||||
<ul>
|
||||
<li><b>Home Assistant Operating System</b>: Minimal Operating System optimized to power Home Assistant.
|
||||
Comes with Supervisor to manage Home Assistant Core and add-ons pre-installed. Recommended installation type.</li>
|
||||
It comes with Supervisor to manage Home Assistant Core and pre-installed add-ons. Recommended installation method.</li>
|
||||
<li><b>Home Assistant Container</b>: Standalone container-based installation of Home Assistant Core (e.g. Docker).</li>
|
||||
</ul>
|
||||
<p>In addition there are two installation methods available for experienced users:</p>
|
||||
<p>There are two alternative installation methods available for experienced users:</p>
|
||||
<ul>
|
||||
<li><b>Home Assistant Supervised</b>: Manual installation of the Supervisor.</li>
|
||||
<li><b>Home Assistant Core</b>: Manual installation using a Python virtual environment.</li>
|
||||
<li><b>Home Assistant Core</b>: Manual installation using Python virtual environment.</li>
|
||||
</ul>
|
||||
<p>
|
||||
The list below shows which installation method is available on what device or platform.
|
||||
The list below shows the installation method available based on the device and platform being used.
|
||||
</p>
|
||||
<p>
|
||||
We recommend a dedicated system to run Home Assistant. If you are unsure what to choose, using a
|
||||
We recommend a dedicated system to run Home Assistant. If you are unsure of what to choose, using a
|
||||
<b>Raspberry Pi</b> and the <b>Home Assistant Operating System</b> is a good start.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
If you are using the <a href="/blue">Home Assistant Blue</a>, the Home Assistant Operating System is
|
||||
already preinstalled. You can skip this installation step.
|
||||
already installed. So you can skip this installation step.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user