mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-18 23:06:58 +00:00
Merge branch 'current' into next
This commit is contained in:
Franck Nijhof
commit
d185588181
13
.github/ISSUE_TEMPLATE/feedback.yml
vendored
13
.github/ISSUE_TEMPLATE/feedback.yml
vendored
@ -1,7 +1,5 @@
|
||||
name: Documentation feedback
|
||||
about: Provide feedback on a page on our website
|
||||
title: ""
|
||||
issue_body: true
|
||||
description: Provide feedback on a page on our website
|
||||
body:
|
||||
- type: markdown
|
||||
attributes:
|
||||
@ -41,13 +39,10 @@ body:
|
||||
Current version of the documentation. This usually matches the Home
|
||||
Assistant Core release version, and can be found at the bottom of the
|
||||
page.
|
||||
- type: markdown
|
||||
- type: textarea
|
||||
attributes:
|
||||
value: |
|
||||
## Additional information
|
||||
- type: markdown
|
||||
attributes:
|
||||
value: >
|
||||
label: Additional information
|
||||
description: >
|
||||
If you have any additional information for us, use the field below.
|
||||
Please note, you can attach screenshots or screen recordings here, by
|
||||
dragging and dropping files in the field below.
|
||||
|
||||
2
.github/workflows/test.yml
vendored
2
.github/workflows/test.yml
vendored
@ -57,7 +57,7 @@ jobs:
|
||||
- name: Check out files from GitHub
|
||||
uses: actions/checkout@v2
|
||||
- name: Setting up Ruby 2.6
|
||||
uses: ruby/setup-ruby@v1.68.0
|
||||
uses: ruby/setup-ruby@v1.70.0
|
||||
with:
|
||||
ruby-version: 2.6
|
||||
- name: Setup Ruby Gems cache
|
||||
|
||||
1
.gitignore
vendored
1
.gitignore
vendored
@ -6,6 +6,7 @@
|
||||
public
|
||||
source/_data/analytics_data.json
|
||||
source/_data/blueprint_exchange_data.json
|
||||
source/_data/version_data.json
|
||||
source/_stash
|
||||
source/stylesheets/screen.css
|
||||
source/.jekyll-cache/
|
||||
|
||||
14
Rakefile
14
Rakefile
@ -33,6 +33,8 @@ task :generate do
|
||||
abort("Generating CSS failed") unless success
|
||||
success = system "rake analytics_data"
|
||||
abort("Generating analytics data failed") unless success
|
||||
success = system "rake version_data"
|
||||
abort("Generating version data failed") unless success
|
||||
success = system "rake blueprint_exchange_data"
|
||||
abort("Generating blueprint exchange data failed") unless success
|
||||
success = system "jekyll build"
|
||||
@ -71,6 +73,7 @@ task :preview, :listen do |t, args|
|
||||
puts "Now listening on http://localhost:#{server_port}"
|
||||
system "compass compile --css-dir #{source_dir}/stylesheets" unless File.exist?("#{source_dir}/stylesheets/screen.css")
|
||||
system "rake analytics_data"
|
||||
system "rake version_data"
|
||||
system "rake blueprint_exchange_data"
|
||||
jekyllPid = Process.spawn({"OCTOPRESS_ENV"=>"preview"}, "jekyll build -t --watch --incremental")
|
||||
compassPid = Process.spawn("compass watch")
|
||||
@ -189,6 +192,17 @@ task :analytics_data do
|
||||
end
|
||||
end
|
||||
|
||||
desc "Download version data from version.home-assistant.io"
|
||||
task :version_data do
|
||||
uri = URI('https://version.home-assistant.io/stable.json')
|
||||
|
||||
remote_data = JSON.parse(Net::HTTP.get(uri))
|
||||
|
||||
File.open("#{source_dir}/_data/version_data.json", "w") do |file|
|
||||
file.write(JSON.generate(remote_data))
|
||||
end
|
||||
end
|
||||
|
||||
desc "Download data from the blueprint exchange @ community.home-assistant.io"
|
||||
task :blueprint_exchange_data do
|
||||
uri = URI('https://community.home-assistant.io/c/blueprints-exchange/53/l/top/all.json')
|
||||
|
||||
@ -106,8 +106,8 @@ social:
|
||||
# Home Assistant release details
|
||||
current_major_version: 2021
|
||||
current_minor_version: 4
|
||||
current_patch_version: 4
|
||||
date_released: 2021-04-13
|
||||
current_patch_version: 6
|
||||
date_released: 2021-04-19
|
||||
|
||||
# Either # or the anchor link to latest release notes in the blog post.
|
||||
# Must be prefixed with a # and have double quotes around it.
|
||||
@ -177,7 +177,6 @@ toc:
|
||||
# Configuration for installation pages
|
||||
installation:
|
||||
versions:
|
||||
os: "5.13"
|
||||
python: "3.8"
|
||||
types:
|
||||
odroid:
|
||||
|
||||
@ -45,6 +45,13 @@ The Home Assistant Community forums have a specific tag for blueprints. This tag
|
||||
|
||||
[blueprint-forums]: /get-blueprints
|
||||
|
||||
## Creating new blueprints
|
||||
|
||||
Using blueprints is nice and easy, but what if you could create that one missing
|
||||
blueprint that our community definitely needs?
|
||||
|
||||
Learn more about blueprint by [reading our tutorial on creating a blueprint](/docs/blueprint/tutorial/).
|
||||
|
||||
## Troubleshooting missing automations
|
||||
|
||||
When you're creating automations using blueprints and they don't appear in the UI, make sure that you add back `automation: !include automations.yaml` from the default configuration to your `configuration.yaml`.
|
||||
|
||||
@ -10,7 +10,7 @@ The Z-Wave control panel is available via **Configuration** → **Integration
|
||||
|
||||
<div class='note'>
|
||||
|
||||
The current Z-Wave integration will eventually be deprecated and replaced with a [new implementation based on OpenZWave Daemon](https://developers.home-assistant.io/blog/2020/02/04/new-zwave/); it's currently in beta, and you can [try it now](/integrations/ozw/).
|
||||
This Z-Wave integration is deprecated and replaced with a [new implementation based on Z-Wave JS](/integrations/zwave_js); it's currently in beta, and you can [try it now](/integrations/zwave_js/).
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -18,5 +18,3 @@
|
||||
Cache-Control: public, max-age: 1800, s-maxage=604800, must-revalidate
|
||||
/static/*
|
||||
Cache-Control: public, max-age: 1800, s-maxage=604800, must-revalidate
|
||||
/integrations.json
|
||||
Access-Control-Allow-Origin: *
|
||||
@ -22,7 +22,7 @@
|
||||
The {{ page.name | default: page.title }} integration was introduced in Home Assistant {{ page.ha_release | default: "unknown" }},
|
||||
and it's used by <a title="Open analytics.home-assistant.io" href="https://analytics.home-assistant.io" target="_blank" rel="noopener">
|
||||
{{ 100.0 | times: site.data.analytics_data.integrations[page.ha_domain] | divided_by: site.data.analytics_data.reports_integrations | round: 1 | remove: ".0" }}%</a> of the active installations.
|
||||
Its IoT class<sup><a href='/blog/2016/02/12/classifying-the-internet-of-things/#classifiers'><i class="icon-info-sign"></i></a></sup> is {{ page.ha_iot_class | default: "unknown" }}
|
||||
Its IoT class is <a href='/blog/2016/02/12/classifying-the-internet-of-things/#classifiers'>{{ page.ha_iot_class | default: "unknown" }}</a>
|
||||
|
||||
{%- if page.ha_quality_scale %}
|
||||
and scores {{page.ha_quality_scale}} on our <a href='/docs/quality_scale/'>quality scale</a>
|
||||
|
||||
@ -76,7 +76,7 @@ Start Home Assistant Core for the first time. This will complete the installatio
|
||||
hass
|
||||
```
|
||||
|
||||
You can now reach your installation on your Raspberry Pi over the web interface on `http://homeassistant.local:8123`.
|
||||
You can now reach your installation via the web interface on `http://homeassistant.local:8123`.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@ We will need a few things to get started with installing Home Assistant. Links b
|
||||
content: |
|
||||
|
||||
```text
|
||||
{{release_url}}/{{site.installation.versions.os}}/hassos_{{ variant.key }}-{{site.installation.versions.os}}.img.xz
|
||||
{{release_url}}/{{site.data.version_data.hassos[variant.key]}}/hassos_{{ variant.key }}-{{site.data.version_data.hassos[variant.key]}}.img.xz
|
||||
```
|
||||
|
||||
{% if variant.key == "odroid-n2" %}
|
||||
@ -48,7 +48,8 @@ We will need a few things to get started with installing Home Assistant. Links b
|
||||
{% else %}
|
||||
|
||||
```text
|
||||
{{release_url}}/{{site.installation.versions.os}}/hassos_{{ site.installation.types[page.installation_type].variants[0].key }}-{{site.installation.versions.os}}.img.xz
|
||||
{% assign board_key = site.installation.types[page.installation_type].variants[0].key %}
|
||||
{{release_url}}/{{site.data.version_data.hassos[board_key]}}/hassos_{{ board_key }}-{{site.data.version_data.hassos[board_key]}}.img.xz
|
||||
```
|
||||
|
||||
{% endif %}
|
||||
@ -187,9 +188,9 @@ With the Home Assistant Operating System installed and accessible you can contin
|
||||
{% include getting-started/next_step.html step="Onboarding" link="/getting-started/onboarding/" %}
|
||||
|
||||
|
||||
[intel-nuc]: {{release_url}}/{{site.installation.versions.os}}/hassos_intel-nuc-{{site.installation.versions.os}}.img.xz
|
||||
[vmdk]: {{release_url}}/{{site.installation.versions.os}}/hassos_ova-{{site.installation.versions.os}}.vmdk.xz
|
||||
[vhdx]: {{release_url}}/{{site.installation.versions.os}}/hassos_ova-{{site.installation.versions.os}}.vhdx.xz
|
||||
[vdi]: {{release_url}}/{{site.installation.versions.os}}/hassos_ova-{{site.installation.versions.os}}.vdi.xz
|
||||
[qcow2]: {{release_url}}/{{site.installation.versions.os}}/hassos_ova-{{site.installation.versions.os}}.qcow2.xz
|
||||
[Virtual Appliance]: {{release_url}}/{{site.installation.versions.os}}/hassos_ova-{{site.installation.versions.os}}.ova
|
||||
[intel-nuc]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/hassos_intel-nuc-{{site.data.version_data.hassos['ova']}}.img.xz
|
||||
[vmdk]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/hassos_ova-{{site.data.version_data.hassos['ova']}}.vmdk.xz
|
||||
[vhdx]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/hassos_ova-{{site.data.version_data.hassos['ova']}}.vhdx.xz
|
||||
[vdi]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/hassos_ova-{{site.data.version_data.hassos['ova']}}.vdi.xz
|
||||
[qcow2]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/hassos_ova-{{site.data.version_data.hassos['ova']}}.qcow2.xz
|
||||
[Virtual Appliance]: {{release_url}}/{{site.data.version_data.hassos['ova']}}/hassos_ova-{{site.data.version_data.hassos['ova']}}.ova
|
||||
|
||||
@ -7,7 +7,9 @@ ha_domain: air_quality
|
||||
ha_quality_scale: internal
|
||||
---
|
||||
|
||||
The `air_quality` gather information about the air quality and pollution details.
|
||||
The `air_quality` base platform allows other integrations to process information
|
||||
about air quality and pollution details. It is used by integrations that provide
|
||||
an `air_quality` sensor - you can find those under the `health` [integrations](/integrations/#health).
|
||||
|
||||
The platforms cover the following levels (if they are available):
|
||||
|
||||
|
||||
@ -117,7 +117,7 @@ Next you need create a Lambda function.
|
||||
- Clear the example code, copy the Python script from: [https://gist.github.com/matt2005/744b5ef548cc13d88d0569eea65f5e5b](https://gist.github.com/matt2005/744b5ef548cc13d88d0569eea65f5e5b) (modified code to support Alexa's proactive mode, see details below)
|
||||
- Click `Deploy` button to publish updated code.
|
||||
- Scroll down a little bit, you will find `Environment variables`, you need add 1 environment variable and, if required, 3 optional variables. This is done by selecting `Manage environment variables` then adding the following:
|
||||
- *(required)* Key = BASE_URL, Value = your Home Assistant instance's Internet accessible URL with port if needed. *Do not include the trailing `/`*.
|
||||
- *(required)* Key = BASE_URL, Value = your Home Assistant instance's Internet accessible URL. *Do not include the trailing `/`*.
|
||||
- *(optional)* Key = NOT_VERIFY_SSL, Value = *True*. You can set this to *True* to ignore SSL issues, for example if you don't have a valid SSL certificate or you are using a self-signed certificate.
|
||||
- *(optional)* Key = DEBUG, Value = *True*. Set this variable to log the debug message and to allow the LONG_LIVED_ACCESS_TOKEN
|
||||
- *(optional, not recommend)* Key = LONG_LIVED_ACCESS_TOKEN, Value = your Home Assistant Long-Lived Access Token. To avoid the use of a long-lived access token you will connect your Alexa Smart Home skill with your Home Assistant user account in the later steps, meaning you don't need to add it here. However, the access token you got from login flow is only valid for 30 minutes. It will be hard for you to test lambda function with the access token in test data. So for your convenience, you can remove the access token from the test data, [generate a long-lived access token][generate-long-lived-access-token] put here, then the function will fall back to read token from environment variables. (tips: You did not enable the security storage for your environment variables, so your token saved here is not that safe. You should only use it for debugging and testing purpose. You should remove and delete the long-lived access token after you finish the debugging.)
|
||||
@ -190,7 +190,7 @@ Alexa can link your Amazon account to your Home Assistant account. Therefore Hom
|
||||
- Find the skill you just created, click `Edit` link in the `Actions` column.
|
||||
- Click `ACCOUNT LINKING` in the left navigation bar of build page
|
||||
- Do not turn on the "Allow users to link their account to your skill from within your application or website" switch. This will require a Redirect URI, which won't work.
|
||||
- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL:PORT]`
|
||||
- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL]`
|
||||
- `Authorization URI`: `https://[YOUR HOME ASSISTANT URL]/auth/authorize`
|
||||
- `Access Token URI`: `https://[YOUR HOME ASSISTANT URL]/auth/token`
|
||||
- Note: you must use a valid/trusted SSL Certificate for account linking to work
|
||||
@ -600,7 +600,7 @@ The [`stream`](/integrations/stream/) integration is required to stream cameras
|
||||
|
||||
The Amazon echo device will request the camera stream from Home Assistant. The Home Assistant URL must be accessible from the network the Amazon echo device is connected to and must support HTTPS on port 443 with a certificate signed by [an Amazon approved certificate authority](https://ccadb-public.secure.force.com/mozilla/IncludedCACertificateReport). These requirements can be satisfied with Home Assistant Cloud, or LetsEncrypt/DuckDNS.
|
||||
|
||||
Enable preload stream option for cameras used with echo devices to reduce response time, and prevent timing out before the 6 second limit.
|
||||
Enable preload stream option for cameras used with echo devices to reduce response time, and prevent timing out before the 6 second limit.
|
||||
|
||||
### Climate
|
||||
|
||||
|
||||
@ -29,7 +29,8 @@ This includes:
|
||||
- Unique identifier for your system (to ensure each installation is counted once)
|
||||
- Home Assistant version
|
||||
- Home Assistant installation type
|
||||
- Your country (derived server-side from your IP-address)
|
||||
- Your country-code (derived server-side from your IP-address), example: `"NO"` for Norway.
|
||||
- If you live in the US this will also include the region (state) code, example: `"CO"` will be used if you live in Colorado.
|
||||
|
||||
If your system includes the Supervisor, this will also contain:
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@ ha_zeroconf: true
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
Support for mDNS discovery in your local network is mandatory. Make sure that your router has this feature enabled. This is even required if you entered the IP addresses of the Cast devices are manually in the configuration as mentioned below.
|
||||
Support for mDNS discovery in your local network is mandatory for automatic discovery. Make sure that your router has this feature enabled. If mDNS does not work in your network, the IP addresses of the Cast devices can be manually entered in the configuration as mentioned below.
|
||||
|
||||
{% include integrations/option_flow.md %}
|
||||
{% configuration_basic %}
|
||||
@ -182,11 +182,19 @@ data:
|
||||
- url: "https://tilos.hu/images/kockalogo.png"
|
||||
```
|
||||
|
||||
## Cast devices and Home Assistant on different subnets
|
||||
## Troubleshooting automatic discovery
|
||||
|
||||
Cast devices can only be automatically discovered if they are on the same subnet as Home Assistant.
|
||||
Setups with cast devices on a different subnet than Home Assistant are not recommended and not supported.
|
||||
If this is not possible, it's necessary to either enable mDNS forwarding between the subnets or to provide a list of known hosts.
|
||||
mDNS relies on UDP multicast, which may fail for various reasons. If none of the tips in this section helps, the recommended solution is to ensure all cast devices have static IPs assigned to them and configure a list of known hosts.
|
||||
|
||||
### Zeroconf configuration
|
||||
|
||||
The Google Cast integration relies on the [Zeroconf integration](/integrations/zeroconf) for mDNS discovery. The Zeroconf integration has some configuration options which impact mDNS routing.
|
||||
|
||||
### Cast devices and Home Assistant on different subnets
|
||||
|
||||
Cast devices can only be automatically discovered if they are on the same subnet as Home Assistant because mDNS packets are not routed across subnets.
|
||||
Automatic discovery in setups with cast devices on a different subnet than Home Assistant is not recommended and not supported.
|
||||
If it is not possible, it's necessary to either enable mDNS forwarding between the subnets or to configure a list of known hosts.
|
||||
|
||||
### Home Assistant Container
|
||||
|
||||
|
||||
@ -53,7 +53,7 @@ automation:
|
||||
|
||||
### Service `fan.set_preset_mode`
|
||||
|
||||
Sets a preset mode for fan device.
|
||||
Sets a preset mode for the fan device. Available preset modes are defined by the integration that supplies the fan entity to Home Assistant. For example, the ESPHome [Speed Fan](https://esphome.io/components/fan/speed.html) component provides by default three available presets: `Low`, `Medium` and `High`.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
|
||||
@ -110,6 +110,10 @@ fan:
|
||||
description: Defines an action to run when the fan is given a speed percentage command.
|
||||
required: false
|
||||
type: action
|
||||
set_preset_mode:
|
||||
description: Defines an action to run when the fan is given a preset command.
|
||||
required: false
|
||||
type: action
|
||||
set_oscillating:
|
||||
description: Defines an action to run when the fan is given an osc state command.
|
||||
required: false
|
||||
|
||||
@ -24,7 +24,7 @@ The `freebox` integration allows you to observe and control [Freebox router](htt
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
* [Sensor](#sensor) with traffic and temperature metrics
|
||||
* [Sensor](#sensor) with metrics for connection speed, internal temperature, free partition space and missed calls
|
||||
* [Device tracker](#presence-detection) for connected devices
|
||||
* [Switch](#switch) to control Wi-Fi
|
||||
|
||||
@ -104,7 +104,11 @@ refreshes the devices states.
|
||||
## Sensor
|
||||
|
||||
This platform offers you sensors to monitor a Freebox router.
|
||||
The monitored conditions are internal temperature and upload and download rates in KB/s.
|
||||
The monitored metrics are:
|
||||
* Internal temperature
|
||||
* Upload and download rates (in KB/s)
|
||||
* Free partition space of used disks
|
||||
* Number of missed calls
|
||||
|
||||
## Service
|
||||
|
||||
|
||||
@ -24,8 +24,8 @@ Player data: allows you to view and monitor your player data from [Habitica](htt
|
||||
- Player's name
|
||||
- Player's health points
|
||||
- Player's max health
|
||||
- Player's manna points
|
||||
- Player's max manna points
|
||||
- Player's mana points
|
||||
- Player's max mana points
|
||||
- Player's experience
|
||||
- Player's experience to the next level
|
||||
- Player's level
|
||||
|
||||
@ -13,21 +13,22 @@ ha_platforms:
|
||||
- switch
|
||||
---
|
||||
|
||||
The Home+ Control integration platform allows you to control a range of Legrand in-wall switches and power outlets that have smart home functionality thanks to their "with Netatmo" capabilities.
|
||||
The Home+ Control integration platform allows you to control a range of Legrand in-wall switches and power outlets that have smart home functionality thanks to their "with Netatmo" capabilities.
|
||||
|
||||
This integration works against the Home+ Control API, which is one of the many APIs offered through the [*Works with Legrand*](https://developer.legrand.com/) program. The API is capable of managing "Legrand/Btcino with Netatmo" devices, such as light switches, power outlets and rolling shutters.
|
||||
|
||||
The devices that this API can manage are offered in different designs across different countries. The details of these can be found [here](https://developer.legrand.com/solutions/wiring-devices-with-netatmo/).
|
||||
|
||||
This Home+ Control integration for Home Assistant currently has support for the following devices:
|
||||
This Home+ Control integration for Home Assistant currently has support for the following devices:
|
||||
|
||||
- Light switches
|
||||
- Power outlets
|
||||
|
||||
In both cases, the devices are modeled as on/off switches within Home Assistant.
|
||||
|
||||
This integration has been tested to work with the following range of Legrand products:
|
||||
- Valena Next™ with Netatmo
|
||||
This integration has been tested to work with the following range of Legrand products
|
||||
|
||||
- Valena Next™ with Netatmo
|
||||
|
||||
## Authentication
|
||||
|
||||
@ -66,26 +67,23 @@ subscription_key:
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
At this point, you are now ready to add the Home+ Control integration to your Home Assistant instance as described in the [Configuration](#configuration) section.
|
||||
|
||||
Restart Home Assistant after changing the YAML configuration. At this point, you are now ready to add the Home+ Control integration to your Home Assistant instance as described in the [Configuration](#configuration) section.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
|
||||
## API Nomenclature
|
||||
|
||||
Within the context of the Home+ Control API you may come across the following terms:
|
||||
|
||||
* *Plant*: This is the term used to represent a *home* that holds the Legrand devices. In practice, a *plant* is represented by the *Legrand Home+ Control* gateway that acts as the central hub of the rest of the devices in the home network (uses Zigbee).
|
||||
* *Module*: This is the term used to represent a generic device within the *plant*, i.e., a light, a plug, a remote, etc.
|
||||
* *Light*: This is the term used to represent a light switch (or a micro-module). It is not modeled as your usual light entity because there are no brightness, color, etc. controls. It is modeled as an on/off switch.
|
||||
* *Plug*: This is the term used to represent a power outlet.
|
||||
- *Plant*: This is the term used to represent a *home* that holds the Legrand devices. In practice, a *plant* is represented by the *Legrand Home+ Control* gateway that acts as the central hub of the rest of the devices in the home network (uses Zigbee).
|
||||
- *Module*: This is the term used to represent a generic device within the *plant*, i.e., a light, a plug, a remote, etc.
|
||||
- *Light*: This is the term used to represent a light switch (or a micro-module). It is not modeled as your usual light entity because there are no brightness, color, etc. controls. It is modeled as an on/off switch.
|
||||
- *Plug*: This is the term used to represent a power outlet.
|
||||
|
||||
Other devices that are mentioned in the API, but that are not currently supported by this integration are: *remotes* (wireless switches), *heaters* and *automations*.
|
||||
|
||||
## API Limitations
|
||||
|
||||
As described in the [authentication](#authentication) section, this integration requires you to set up a subscription in the *Works with Legrand* platform.
|
||||
As described in the [authentication](#authentication) section, this integration requires you to set up a subscription in the *Works with Legrand* platform.
|
||||
|
||||
Currently, end-users only have access to the *Starter Kit* subscription which has a major limitation in the number of allowed API requests that are allowed - only 500 API calls per day (counter is reset at 00:00 every day). If this daily quota is ever exceeded, the API will report `403 Forbidden` HTTP responses.
|
||||
|
||||
@ -34,31 +34,6 @@ In addition, there is a **Sensor** for each of CV pressure, CV temperature, and
|
||||
|
||||
Any room thermostats (there can be 0, 1 or 2) are represented as **Climate** devices. They will report the thermostat's `temperature` (setpoint, target temperature) and `current_temperature` and the setpoint can be changed.
|
||||
|
||||
## Automation
|
||||
|
||||
To send an alert if the CV pressure is too low or too high, consider the following example:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
- alias: "Low CV Pressure Alert"
|
||||
trigger:
|
||||
platform: numeric_state
|
||||
entity_id: sensor.cv_pressure
|
||||
below: 1.0
|
||||
action:
|
||||
- service: notify.pushbullet_notifier
|
||||
data:
|
||||
title: "Warning: Low CH Pressure"
|
||||
message: >-
|
||||
{{ trigger.to_state.attributes.friendly_name }}
|
||||
is low, {{ trigger.to_state.state }} bar.
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
Other properties are available via each device's attributes.
|
||||
|
||||
## Configuration
|
||||
|
||||
To set up this integration, add one of the following to your `configuration.yaml` file:
|
||||
@ -101,3 +76,28 @@ password:
|
||||
required: inclusive
|
||||
type: string
|
||||
{% endconfiguration %}
|
||||
|
||||
## Automation
|
||||
|
||||
To send an alert if the CV pressure is too low or too high, consider the following example:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
- alias: "Low CV Pressure Alert"
|
||||
trigger:
|
||||
platform: numeric_state
|
||||
entity_id: sensor.cv_pressure
|
||||
below: 1.0
|
||||
action:
|
||||
- service: notify.pushbullet_notifier
|
||||
data:
|
||||
title: "Warning: Low CH Pressure"
|
||||
message: >-
|
||||
{{ trigger.to_state.attributes.friendly_name }}
|
||||
is low, {{ trigger.to_state.state }} bar.
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
Other properties are available via each device's attributes.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Input Boolean
|
||||
description: Instructions on how to integrate the Input Boolean integration into Home Assistant.
|
||||
description: Instructions on how to use the Input Boolean helper with Home Assistant.
|
||||
ha_category:
|
||||
- Automation
|
||||
ha_release: 0.11
|
||||
@ -11,12 +11,23 @@ ha_codeowners:
|
||||
ha_domain: input_boolean
|
||||
---
|
||||
|
||||
The `input_boolean` integration allows the user to define boolean values that can be controlled via the frontend and can be used within conditions of automation. This can for example be used to disable or enable certain automations.
|
||||
The Input Boolean helper integration allows you to define boolean values that
|
||||
can be controlled via the user interface and can be used within conditions of
|
||||
automation. This can for example be used to disable or enable certain
|
||||
automations by using them in their conditions.
|
||||
|
||||
The preferred way to configure input booleans is via the user interface at **Configuration** -> **Helpers**. Click the add button and then choose the "**Toggle**" option.
|
||||
## Configuration
|
||||
|
||||
To be able to add **Helpers** via the user interface you should have `default_config:` in your `configuration.yaml`, it should already be there by default unless you removed it.
|
||||
If you removed `default_config:` from you configuration, you must add `input_boolean:` to your `configuration.yaml` first, then you can use the UI.
|
||||
The preferred way to configure input boolean helpers is via the user interface,
|
||||
in which they are known as Toggle Helpers. To add one, go to
|
||||
**{% my helpers title="Configuration -> Helpers" %}** and click the add button;
|
||||
next choose the "**Toggle**" option.
|
||||
|
||||
To be able to add **Helpers** via the user interface you should have
|
||||
`default_config:` in your `configuration.yaml`, it should already be there by
|
||||
default unless you removed it. If you removed `default_config:` from your
|
||||
configuration, you must add `input_boolean:` to your `configuration.yaml` first,
|
||||
then you can use the UI.
|
||||
|
||||
Input booleans can also be configured via `configuration.yaml`:
|
||||
|
||||
@ -49,10 +60,11 @@ input_boolean:
|
||||
type: icon
|
||||
{% endconfiguration %}
|
||||
|
||||
### Services
|
||||
## Services
|
||||
|
||||
This integration provides the following services to modify the state of the `input_boolean` and a service to reload the
|
||||
configuration without restarting Home Assistant itself.
|
||||
This integration provides the following services to modify the state of the
|
||||
`input_boolean` and a service to reload the configuration without restarting
|
||||
Home Assistant itself.
|
||||
|
||||
| Service | Data | Description |
|
||||
| ------- | ---- | ----------- |
|
||||
@ -63,34 +75,39 @@ configuration without restarting Home Assistant itself.
|
||||
|
||||
### Restore State
|
||||
|
||||
If you set a valid value for `initial` this integration will start with state set to that value. Otherwise, it will restore the state it had prior to Home Assistant stopping.
|
||||
If you set a valid value for `initial` this integration will start with state
|
||||
set to that value. Otherwise, it will restore the state it had prior to
|
||||
Home Assistant stopping.
|
||||
|
||||
## Automation Examples
|
||||
|
||||
Here's an example of an automation using the above `input_boolean`. This action will only occur if the switch is on.
|
||||
Here's an example of an automation using the above `input_boolean`. This action
|
||||
will only occur if the switch is on.
|
||||
|
||||
```yaml
|
||||
automation:
|
||||
alias: "Arriving home"
|
||||
trigger:
|
||||
platform: state
|
||||
entity_id: binary_sensor.motion_garage
|
||||
to: "on"
|
||||
- platform: state
|
||||
entity_id: binary_sensor.motion_garage
|
||||
to: "on"
|
||||
condition:
|
||||
condition: state
|
||||
entity_id: input_boolean.notify_home
|
||||
state: "on"
|
||||
- condition: state
|
||||
entity_id: input_boolean.notify_home
|
||||
state: "on"
|
||||
action:
|
||||
service: notify.pushbullet
|
||||
data:
|
||||
title: ""
|
||||
message: "Honey, I'm home!"
|
||||
- service: notify.pushbullet
|
||||
data:
|
||||
title: ""
|
||||
message: "Honey, I'm home!"
|
||||
```
|
||||
|
||||
You can also set or change the status of an `input_boolean` by using `input_boolean.turn_on`, `input_boolean.turn_off` or `input_boolean.toggle` in your automations.
|
||||
You can also set or change the status of an `input_boolean` by using
|
||||
`input_boolean.turn_on`, `input_boolean.turn_off` or `input_boolean.toggle` in
|
||||
your automations.
|
||||
|
||||
```yaml
|
||||
- service: input_boolean.turn_on
|
||||
target:
|
||||
entity_id: input_boolean.notify_home
|
||||
service: input_boolean.turn_on
|
||||
target:
|
||||
entity_id: input_boolean.notify_home
|
||||
```
|
||||
|
||||
@ -13,7 +13,11 @@ ha_quality_scale: internal
|
||||
|
||||
The Media Source integration platform allows integrations to expose media for
|
||||
use inside Home Assistant through the Media Browser panel or through supported
|
||||
media players like Google Cast. This integration is configured automatically
|
||||
media players like Google Cast.
|
||||
|
||||
## Configuration
|
||||
|
||||
This integration is configured automatically
|
||||
through `default_config` or if another integration implements a media source.
|
||||
|
||||
If your configuration does not contain any of the above, you can add the below
|
||||
@ -27,7 +31,7 @@ media_source:
|
||||
## Local Media
|
||||
|
||||
By default, the integration looks for media in a specified folder.
|
||||
If other `media_dirs` are not declared you need to use `/media/local` path for
|
||||
If other `media_dirs` are not declared you need to use `/media/local` path for
|
||||
example in companion app notification.
|
||||
|
||||
For Home Assistant OS, Supervised and Container users, this folder is by default
|
||||
@ -58,23 +62,37 @@ homeassistant:
|
||||
recording: /mnt/recordings
|
||||
```
|
||||
|
||||
Please note, that the folder must be accessible locally. Home Assistant
|
||||
cannot connect to external or remote network shares using this configuration
|
||||
option.
|
||||
|
||||
## Playing media from a Media Source
|
||||
|
||||
To play media from a media source via a service call, use the uri scheme `media-source://media_source/<media_dir>/<path>`.
|
||||
Default `media_dir`is `local`.
|
||||
To play media from a media source via a service call, use the uri
|
||||
scheme `media-source://media_source/<media_dir>/<path>`.
|
||||
Default `media_dir` is `local`.
|
||||
|
||||
<div class="note">
|
||||
Web browsers and Google Cast media players have very limited video container and codec support. The Media Source integration does not do any transcoding of media, meaning media files must be natively supported by your media player or web browser (for playing in the frontend). If a video file is not supported by your media player or web browser it will fail to play. Please check the documentation of your media player or web browser for lists of supported video formats.
|
||||
Web browsers and Google Cast media players have very limited video container
|
||||
and codec support. The Media Source integration does not do any transcoding of
|
||||
media, meaning media files must be natively supported by your media player or
|
||||
web browser (for playing in the frontend).
|
||||
|
||||
If a video file is not supported by
|
||||
your media player or web browser it will fail to play. Please check the
|
||||
documentation of your media player or web browser for lists
|
||||
of supported video formats.
|
||||
</div>
|
||||
|
||||
Example:
|
||||
|
||||
```yaml
|
||||
service: media_player.play_media
|
||||
target:
|
||||
entity_id: media_player.living_room_tv
|
||||
data:
|
||||
media_content_type: video/mp4
|
||||
media_content_id: media-source://media_source/local/videos/favourites/Epic Sax Guy 10 Hours.mp4
|
||||
media_content_type: "video/mp4"
|
||||
media_content_id: "media-source://media_source/local/videos/favourites/Epic Sax Guy 10 Hours.mp4"
|
||||
```
|
||||
|
||||
[basic-configuration]: /docs/configuration/basic/#media_dirs
|
||||
|
||||
@ -81,3 +81,13 @@ camera:
|
||||
password: BLUE_IRIS_PASSWORD
|
||||
authentication: basic
|
||||
```
|
||||
|
||||
Example of using a DCS-930L Wireless N Network Camera from D-Link:
|
||||
|
||||
```yaml
|
||||
camera:
|
||||
- platform: mjpeg
|
||||
name: "YOUR_FRIENDLY_NAME"
|
||||
still_image_url: "http://USER:PASSWORD@IP_CAM:PORT/image/jpeg.cgi"
|
||||
mjpeg_url: "http://USER:PASSWORD@IP_CAM:PORT/video/mjpg.cgi"
|
||||
```
|
||||
|
||||
@ -174,7 +174,7 @@ binary_sensors:
|
||||
description: type of adddress (holding/discrete/coil)
|
||||
required: false
|
||||
default: holding
|
||||
type: integer
|
||||
type: string
|
||||
name:
|
||||
description: Name for this binary_sensor. Must be unique.
|
||||
required: true
|
||||
@ -188,6 +188,10 @@ binary_sensors:
|
||||
description: The number of the slave.
|
||||
required: false
|
||||
type: integer
|
||||
address:
|
||||
description: Address of the Register.
|
||||
required: true
|
||||
type: integer
|
||||
{% endconfiguration %}
|
||||
|
||||
|
||||
@ -684,7 +688,7 @@ switches:
|
||||
description: type of adddress (holding/input/coil)
|
||||
required: false
|
||||
default: holding
|
||||
type: integer
|
||||
type: string
|
||||
name:
|
||||
description: Name of the switch.
|
||||
required: true
|
||||
|
||||
@ -16,14 +16,44 @@ ha_platforms:
|
||||
- cover
|
||||
---
|
||||
|
||||
The `myq` cover platform lets you control MyQ-Enabled garage doors through Home Assistant. Device names in Home Assistant are generated based on the names defined in your MyQ Device mobile app.
|
||||
The MyQ integration lets you control MyQ-Enabled garage doors through Home Assistant. Device names in Home Assistant are generated based on the names defined in your MyQ Device mobile app.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Binary Sensor
|
||||
### Binary Sensor
|
||||
|
||||
Your MyQ gateway will appear as a binary sensor that shows if the device is connected.
|
||||
|
||||
## Cover
|
||||
### Cover
|
||||
|
||||
Garage doors and gates linked to your `MyQ` account will appear as covers.
|
||||
|
||||
## Using HomeKit controller for local control - ***No Apple device required***
|
||||
|
||||
If you have a [`819LMB`](https://www.liftmaster.com/myq-home-bridge/p/G819LMB) or [`MYQ-G0303-SP`](https://www.chamberlain.com/myq-g0303-sp/p/MYQ-G0303-SP), Home Assistant can speak HomeKit Accessory Protocol and control the device over the local network without the need to access to the cloud service. As a bonus, updates are push and near-instantaneous.
|
||||
|
||||
To use HomeKit Controller:
|
||||
|
||||
### If bridge is currently paired (otherwise skip these steps)
|
||||
|
||||
- Open the Apple Home App to the Home that the MyQ device is paired with.
|
||||
- Touch the Home Icon.
|
||||
- Choose `Home Settings`.
|
||||
- Scroll down to `Hubs and Bridges`.
|
||||
- Touch the `MyQ-...` bridge.
|
||||
- Touch `Remove Bridge from Home`.
|
||||
|
||||
### Pairing with Home Assistant
|
||||
|
||||
- Go to {% my integrations title="Configuration >> Integrations" %} in the Home Assistant UI.
|
||||
- Click the button with + sign, and from the list of integrations, select ***HomeKit Controller***.
|
||||
- Select the `MyQ-...` bridge.
|
||||
- Enter the pairing code that is physically printed on a sticker on the bridge.
|
||||
- Complete the remaining steps.
|
||||
|
||||
If you want the devices to be accessible via HomeKit, create a HomeKit Bridge using the following steps:
|
||||
|
||||
- Go to {% my integrations title="Configuration >> Integrations" %} in the Home Assistant UI.
|
||||
- Click the button with + sign, and from the list of integrations, select ***HomeKit***.
|
||||
- Create a bridge for the `cover` domain.
|
||||
- Follow the instructions to pair with the bridge.
|
||||
|
||||
@ -14,7 +14,9 @@ ha_platforms:
|
||||
- sensor
|
||||
---
|
||||
|
||||
The `nut` sensor platform allows you to monitor a UPS (battery backup) by using data from a [NUT](https://networkupstools.org/) (Network UPS Tools) server.
|
||||
The Network UPS Tools (NUT) integration allows you to monitor a UPS
|
||||
(battery backup) by using data from a [NUT](https://networkupstools.org/)
|
||||
server.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
@ -59,8 +61,11 @@ output.voltage: 121.50
|
||||
output.voltage.nominal: 120
|
||||
```
|
||||
|
||||
Use the values from the left hand column. Support is included for most values with 'ups', 'battery', 'input' and 'output' prefixes.
|
||||
Use the values from the left hand column. Support is included for most
|
||||
values with 'ups', 'battery', 'input' and 'output' prefixes.
|
||||
|
||||
## UPS Status - human-readable version
|
||||
|
||||
An additional virtual sensor type `ups.status.display` is available translating the UPS status value retrieved from `ups.status` into a human-readable version.
|
||||
An additional virtual sensor type `ups.status.display` is available
|
||||
translating the UPS status value retrieved from `ups.status` into a
|
||||
human-readable version.
|
||||
|
||||
@ -112,7 +112,7 @@ Some of the known valid key values are:
|
||||
- `back`
|
||||
- `power`
|
||||
|
||||
The list with all known valid keys can be found [here](https://github.com/florianholzapfel/panasonic-viera/blob/521cefadc8e1543514ce41d3d49e9218d1c2302d/panasonic_viera/__init__.py#L35). Additionally, you can also send custom commands, such as `"NRC_HOME-ONOFF"` (which is the same as `home`).
|
||||
The list with all known valid keys can be found [here](https://github.com/florianholzapfel/panasonic-viera/blob/521cefadc8e1543514ce41d3d49e9218d1c2302d/panasonic_viera/__init__.py#L35). Additionally, you can also send custom commands, such as `"NRC_HOME-ONOFF"` (which is the same as `home`). Two further undocumented commands are `"NRC_CHG_HDMI1-ONOFF"` and `"NRC_CHG_HDMI1-ONOFF"` for selecting HDMI inputs.
|
||||
|
||||
### Currently known supported models
|
||||
|
||||
|
||||
@ -10,17 +10,8 @@ ha_platforms:
|
||||
- tts
|
||||
---
|
||||
|
||||
The `picotts` text-to-speech platform uses offline pico Text-to-Speech engine to read a text with natural sounding voices.
|
||||
This requires to install the pico TTS library on the system, typically on Debian just do `sudo apt-get install libttspico-utils`
|
||||
On some Raspbian release, this package is missing but you can just copy the arm deb package from Debian.
|
||||
|
||||
On Debian Buster, the package is missing, use the following commands to install it:
|
||||
|
||||
```bash
|
||||
wget http://ftp.us.debian.org/debian/pool/non-free/s/svox/libttspico0_1.0+git20130326-9_armhf.deb
|
||||
wget http://ftp.us.debian.org/debian/pool/non-free/s/svox/libttspico-utils_1.0+git20130326-9_armhf.deb
|
||||
sudo apt-get install -f ./libttspico0_1.0+git20130326-9_armhf.deb ./libttspico-utils_1.0+git20130326-9_armhf.deb
|
||||
```
|
||||
The `picotts` text-to-speech platform uses [Pico TTS library](https://github.com/naggety/picotts) to read out text with natural sounding voices.
|
||||
Pico TTS is a powerful open-source engine that runs locally (cloudless) so it can work even without an internet connection.
|
||||
|
||||
## Configuration
|
||||
|
||||
|
||||
@ -41,7 +41,7 @@ proxmoxve:
|
||||
|
||||
{% configuration %}
|
||||
host:
|
||||
description: IP address of the Proxmox VE instance.
|
||||
description: IP address of the Proxmox VE instance. Can include port by appending ":\<port\>".
|
||||
required: true
|
||||
type: string
|
||||
port:
|
||||
@ -55,7 +55,7 @@ verify_ssl:
|
||||
default: true
|
||||
type: boolean
|
||||
username:
|
||||
description: The username used to authenticate. Can include the realm by appending "@<realm>".
|
||||
description: The username used to authenticate. Can include the realm by appending "@\<realm\>".
|
||||
required: true
|
||||
type: string
|
||||
password:
|
||||
@ -148,3 +148,5 @@ Creating a dedicated user for Home Assistant, limited to only to the access just
|
||||
7. Select the group just created earlier (`HomeAssistant`) to grant access to Proxmox
|
||||
8. Ensure `Enabled` is checked and `Expire` is set to "never"
|
||||
9. Click `Add`
|
||||
|
||||
In your Home Assistant configuration, use `hass@pve` for the username and your chosen password for the password.
|
||||
|
||||
@ -19,13 +19,16 @@ ha_platforms:
|
||||
|
||||
This integration connects with Risco Alarms over [Risco Cloud](https://riscocloud.com/).
|
||||
|
||||
<div class='note'>
|
||||
As from January 2021, Risco have implemented charges for use of their Cloud Features.
|
||||
</div>
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
<div class='note warning'>
|
||||
It is recommended to use a regular (non-owner) account with the Risco app/website, and use a different regular account with the integration. Risco has restrictions on concurrent uses by different users, especially if they have different permission levels.
|
||||
</div>
|
||||
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
4 sensors will be created to store events, depending on the category (Status, Alarm, Trouble and Other). Each sensor
|
||||
has the event timestamp as the state, and other event information in attributes.
|
||||
|
||||
|
||||
@ -15,19 +15,14 @@ The Roon integration allows you to control [RoonLabs](https://roonlabs.com/) mus
|
||||
|
||||
This integration uses Roon Core, a Roon application that runs on a machine on your network. Via Roon Core, Home Assistant can control all the Roon music players on your network.
|
||||
|
||||
To integrate with Roon, you need to provide Home Assistant with the Hostname or IP address of the machine that runs your Roon Core, and then authorize Home Assistant in the Roon application.
|
||||
|
||||
If you use an IP address, please assign a static IP address to the machine that runs Roon Core. This ensures that it won't change IP addresses, so you won't have to change the configuration in Home Assistant if it reboots and changes IP address. See your router's manual for details on how to set this up.
|
||||
|
||||
## Configuration
|
||||
|
||||
You need the Hostname or IP address of the machine that runs your Roon Core. This might be a machine name (which can be followed by `.local`, e.g., `myserver.local`) or can be an IP address.
|
||||
|
||||
1. From the Home Assistant front-end, navigate to **Configuration** then **Integrations**. Under **Set up a new integration** locate 'Roon' and click **Configure**.
|
||||
2. Enter the `Hostname` or `IP address` for the Roon Core machine and click **Submit**.
|
||||
3. Home Assistant will then contact your Roon Core and ask to be authorized. You will need to enable this extension in the Room Application. Go to **Settings** and then **Extensions**, there you will see an entry for Home Assistant with a button next to it. Click **Enable**.
|
||||
4. Roon core will then provide Home Assistant with the details of your media players.
|
||||
5. In Home Assistant you can then pick an area for each of your music players, and add them to Home Assistant.
|
||||
2. Home Assistant will then try to find your Roon Core - if it is successful it will display `Authorize HomeAssistant in Roon`. Click **Submit** and skip to step 4
|
||||
3. If your Roon Core is not automatically found you can enter the `Hostname` or `IP address` for the Roon Core machine when requested and click **Submit**.
|
||||
4. Home Assistant will then contact your Roon Core and ask to be authorized. You will need to enable this extension in the Room Application. Go to **Settings** and then **Extensions**, there you will see an entry for Home Assistant with a button next to it. Click **Enable**.
|
||||
5. Roon core will then provide Home Assistant with the details of your media players.
|
||||
6. In Home Assistant you can then pick an area for each of your music players, and add them to Home Assistant.
|
||||
|
||||
## Services
|
||||
|
||||
|
||||
@ -17,6 +17,8 @@ Shell commands aren't allowed for a camel-case naming, please use lowercase nami
|
||||
[script]: /integrations/script/
|
||||
[automation]: /getting-started/automation/
|
||||
|
||||
## Configuration
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
# Exposes service shell_command.restart_pow
|
||||
@ -37,6 +39,28 @@ Any service data passed into the service call to activate the shell command will
|
||||
|
||||
`stdout` and `stderr` output from the command are both captured and will be logged by setting the [log level](/integrations/logger/) to debug.
|
||||
|
||||
## Examples
|
||||
|
||||
### Defining multiple shell commands
|
||||
|
||||
You can also define multiple shell commands at once. This is an example
|
||||
that defines three different (unrelated) shell commands.
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
shell_command:
|
||||
restart_pow: touch ~/.pow/restart.txt
|
||||
call_remote: curl http://example.com/ping
|
||||
my_script: bash /config/shell/script.sh
|
||||
```
|
||||
|
||||
### Automation example
|
||||
|
||||
This is a an example of an shell command used in conjunction with an input
|
||||
helper and an automation.
|
||||
|
||||
{% raw %}
|
||||
|
||||
```yaml
|
||||
# Apply value of a GUI slider to the shell_command
|
||||
automation:
|
||||
@ -55,8 +79,8 @@ input_number:
|
||||
max: 32
|
||||
step: 1
|
||||
|
||||
{% raw %}
|
||||
shell_command:
|
||||
set_ac_to_slider: 'irsend SEND_ONCE DELONGHI AC_{{ states("input_number.ac_temperature") }}_AUTO'
|
||||
{% endraw %}
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
@ -67,6 +67,10 @@ queries:
|
||||
type: template
|
||||
{% endconfiguration %}
|
||||
|
||||
There is no explicit configuration required for attributes. The integration will set all additional columns returned by the query as attributes.
|
||||
|
||||
Note that in all cases only the first row returned will be used.
|
||||
|
||||
## Examples
|
||||
|
||||
In this section, you find some real-life examples of how to use this sensor.
|
||||
|
||||
@ -13,52 +13,20 @@ ha_codeowners:
|
||||
ha_domain: stream
|
||||
---
|
||||
|
||||
The `stream` integration provides a way to proxy live streams through Home Assistant. The integration currently only supports proxying H.264 source streams to the HLS format and requires at least FFmpeg >= 4.
|
||||
The stream integration provides a way to proxy live streams through Home Assistant. Most users should not need to configure anything or interface with the component directly since it is an internal component used by the [camera integration](/integrations/camera).
|
||||
|
||||
## Configuration
|
||||
|
||||
To enable this component, add the following lines to your `configuration.yaml` file:
|
||||
The `stream` integration is automatically loaded by `default_config` and enabled by the `camera` platforms that support it. If `default_config` is used, no separate `configuration.yaml` entry is necessary. If `default_config` is not used, the `stream` integration can be activated with the entry below:
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
# Example configuration.yaml entry. There are no additional options.
|
||||
stream:
|
||||
```
|
||||
|
||||
### Services
|
||||
## Technical Details
|
||||
|
||||
Once loaded, the `stream` platform will expose services that can be called to perform various actions.
|
||||
|
||||
#### Service `record`
|
||||
|
||||
Make a `.mp4` recording from a provided stream. While this service can be called directly, it is used internally by the [`camera.record`](/integrations/camera#service-record) service.
|
||||
|
||||
Both `duration` and `lookback` options are suggestions, but should be consistent per stream. The actual length of the recording may vary. It is suggested that you tweak these settings to fit your needs.
|
||||
|
||||
| Service data attribute | Optional | Description |
|
||||
| ---------------------- | -------- | ----------- |
|
||||
| `stream_source` | no | The input source for the stream, e.g., `rtsp://my.stream.feed:554`. |
|
||||
| `filename` | no | The file name string. e.g., `/tmp/my_stream.mp4`. |
|
||||
| `duration` | yes | Target recording length (in seconds). Default: 30 |
|
||||
| `lookback` | yes | Target lookback period (in seconds) to include in addition to duration. Only available if there is currently an active HLS stream for `stream_source`. Default: 0 |
|
||||
|
||||
The path part of `filename` must be an entry in the `allowlist_external_dirs` in your [`homeassistant:`](/docs/configuration/basic/) section of your `configuration.yaml` file.
|
||||
|
||||
For example, the following action in an automation would take a recording from `rtsp://my.stream.feed:554` and save it to `/config/www`.
|
||||
|
||||
```yaml
|
||||
action:
|
||||
service: camera.record
|
||||
target:
|
||||
entity_id: camera.quintal
|
||||
data:
|
||||
filename: "/config/www/my_stream.mp4"
|
||||
duration: 30
|
||||
```
|
||||
|
||||
## Streaming in Lovelace
|
||||
|
||||
As of Home Assistant version 0.92 you can now live-stream a camera feed directly in lovelace.
|
||||
To do this add either [picture-entity](/lovelace/picture-entity/), [picture-glance](/lovelace/picture-glance/) or [picture-elements](/lovelace/picture-elements/), set `camera_image` to a stream-ready camera entity and set `camera_view` to `live` in one of your Lovelace views.
|
||||
The integration currently supports proxying H.264 and H.265 source streams to the HLS protocol and requires at least FFmpeg >= 4. Note that H.265 support is limited to Safari, iOS, and Android. The `stream` integration also provides limited support for audio. PCM codecs (e.g. G.711/G.723/G.726/G.729) are not supported. ADTS AAC audio is also currently not supported. Most other AAC and MP3 encoded audio should work.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
||||
@ -63,5 +63,6 @@ List of models known to be supported:
|
||||
|
||||
- RT1900ac
|
||||
- RT2600ac
|
||||
- MR2200ac
|
||||
|
||||
See the [device tracker integration page](/integrations/device_tracker/) for instructions on how to configure the people to be tracked.
|
||||
|
||||
@ -11,8 +11,7 @@ ha_platforms:
|
||||
---
|
||||
|
||||
The `systemmonitor` sensor platform allows you to monitor disk usage,
|
||||
memory usage, CPU usage, and running processes. This platform has superseded the
|
||||
process integration which is now considered deprecated.
|
||||
memory usage, CPU usage, and running processes.
|
||||
|
||||
To add this platform to your installation,
|
||||
add the following to your `configuration.yaml` file:
|
||||
|
||||
@ -70,7 +70,7 @@ password:
|
||||
required: true
|
||||
type: string
|
||||
home_id:
|
||||
description: The id of your home of which you want to track devices. If provided, the Tado device tracker will tack *all* devices known to Tado associated with this home. See below how to find it.
|
||||
description: The id of your home of which you want to track devices. If provided, the Tado device tracker will track *all* devices known to Tado associated with this home. See below how to find it.
|
||||
required: false
|
||||
type: integer
|
||||
{% endconfiguration %}
|
||||
|
||||
@ -74,10 +74,14 @@ To test, you can use the command line tool `mosquitto_pub` shipped with `mosquit
|
||||
|
||||
Discover the tag scanner:
|
||||
|
||||
{% raw %}
|
||||
|
||||
```bash
|
||||
mosquitto_pub -h 127.0.0.1 -t homeassistant/tag/0AFFD2/config -m '{"topic": "0AFFD2/tag_scanned", "value_template": "{{ value_json.PN532.UID }}"}'
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
Generate tag scanned event:
|
||||
|
||||
{% raw %}
|
||||
@ -87,4 +91,3 @@ mosquitto_pub -h 127.0.0.1 -t 0AFFD2/tag_scanned -m '{"Time":"2020-09-28T17:02:1
|
||||
```
|
||||
|
||||
{% endraw %}
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ The `uk_transport` sensor will display the time in minutes until the next depart
|
||||
|
||||
<div class='note warning'>
|
||||
|
||||
Additional sensors can be added but at the expense of a reduced refresh rate. 2 sensors can be updated every 2*87 = 174 seconds, and so on.
|
||||
Additional sensors can be added but at the expense of a reduced refresh rate. 2 sensors can be updated every 2*87 = 174 seconds, and so on. Calculating and setting this rate is automatically handles by the integration.
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
@ -74,6 +74,8 @@ offset:
|
||||
|
||||
## Services
|
||||
|
||||
Some of the services are only available if tariffs are configured.
|
||||
|
||||
### Service `utility_meter.reset`
|
||||
|
||||
Reset the Utility Meter. All sensors tracking tariffs will be reset to 0.
|
||||
|
||||
@ -27,7 +27,13 @@ ha_platforms:
|
||||
- switch
|
||||
---
|
||||
|
||||
The [Vera](https://getvera.com/) hub is a controller mainly for connecting to Z-Wave devices.
|
||||
The [Vera](https://getvera.com/) hub is a controller mainly for connecting to Z-Wave devices.
|
||||
|
||||
The supported Vera hubs (Edge, Plus and Secure) are no longer available and the firmware is not being actively enhanced by the vendor. New Z-Wave devices are not directly supported and so are not easy to add to the platform.
|
||||
|
||||
The newer Ezlo hubs use a different firmware and are not supported by this integration.
|
||||
|
||||
[Z-Wave JS](/integrations/zwave_js/) is a better choice for new Z-Wave users or for users wanting support for new Z-Wave devices.
|
||||
|
||||
There is currently support for the following device types within Home Assistant:
|
||||
|
||||
|
||||
@ -61,7 +61,7 @@ On macOS `python-vlc` won’t find the VLC plugin directory unless you add this
|
||||
export VLC_PLUGIN_PATH=$VLC_PLUGIN_PATH:/Applications/VLC.app/Contents/MacOS/plugins
|
||||
```
|
||||
|
||||
## Additional configuration for Raspberry Pi
|
||||
## Additional configuration on Linux
|
||||
|
||||
You need to add the `homeassistant` user to the `audio` group:
|
||||
|
||||
|
||||
@ -136,7 +136,9 @@ Any other [actions](/docs/automation/action/) to power on the device can be conf
|
||||
|
||||
## Sources
|
||||
|
||||
To obtain complete list of available sources currently configured on the TV, once the webOS TV is configured and linked, while its powered on head to the **Developer Tools** > **States**, find your `media_player.<name>` and use the sources listed in `source_list:` remembering to split them per line into your `sources:` configuration.
|
||||
To obtain complete list of available sources currently configured on the TV, once the webOS TV is configured and linked, while its powered on head to the **Developer Tools** > **States**, find your `media_player.<name>` and use the sources listed in `source_list:` remembering to split them per line into your `sources:` configuration. If you leave the `sources:` configuration empty, the `media_player` will offer all sources of the TV. If you list a subset of sources in the configuration, only those will be displayed.
|
||||
|
||||
Note: it is normal and expected behavior that for a switched-off TV only the Live TV source is offered in the `media_player`, even if you have configured other sources as well. These will show up as soon as the TV is switched on.
|
||||
|
||||
## Change channel through play_media service
|
||||
|
||||
|
||||
@ -272,11 +272,11 @@ from the same group:
|
||||
|
||||
### Service `zha.remove`
|
||||
|
||||
This service removes an existing device from the network.
|
||||
This service removes an existing device from the network. You can find the IEEE address of the device on the device card of Zigbee devices. An example of an IEEE address data parameter format is `00:0d::6f:00:05:7d:2d:34`.
|
||||
|
||||
| Data | Optional | Description |
|
||||
| ---- | ---- | ----------- |
|
||||
| `ieee` | no | IEEE address of the device to remove
|
||||
| `ieee` | no | IEEE address of the device to remove
|
||||
|
||||
### Service `zha.set_lock_user_code`
|
||||
|
||||
@ -385,16 +385,23 @@ logger:
|
||||
|
||||
### Add Philips Hue bulbs that have previously been added to another bridge
|
||||
|
||||
Philips Hue bulbs that have previously been added to another bridge won't show up during search. You have to restore your bulbs back to factory settings first. To achieve this, you basically have the following options.
|
||||
Philips Hue bulbs/lights that have previously been paired/added to another bridge/gateway will not show up during search in ZHA to pair/add a Zigbee device. That is because you have to first manually restore your bulbs/lights back to their factory default settings first, and just removing them from your old bridge/gateway is not enough to do so. Instead to achieve a proper device factory reset you can use one of these methods below.
|
||||
|
||||
Using a Philips Hue Dimmer Switch or Lutron Connected Bulb Remote is probably the easiest way to factory-reset your bulbs. For this to work, the remote does not have to be paired with your previous bridge. Also, make sure there are no other Hue bulbs nearby that have just been turned on when using this method as you otherwise risk resetting them too.
|
||||
|
||||
#### Philips Hue Dimmer Switch
|
||||
|
||||
Using a Philips Hue Dimmer Switch is probably the easiest way to factory-reset your bulbs. For this to work, the remote doesn't have to be paired with your previous bridge.
|
||||
1. Turn on your Hue bulb/light you want to reset. (It is important that the bulb has just been turned).
|
||||
2. Hold the Philips Hue Dimmer Switch near your bulb (closer than 10 centimeters / 4 inches).
|
||||
3. Press and hold the (I)/(ON) and (O)/(OFF) buttons on the Philips Hue Dimmer Switch for about 10 seconds continuously until your bulb starts to blink.
|
||||
4. Your bulb should stop blinking and eventually turn on again. At the same time, a green light on the top left of your remote indicates that your bulb has been successfully reset to factory default settings.
|
||||
|
||||
1. Turn on your Hue bulb you want to reset
|
||||
2. Hold the Dimmer Switch near your bulb (< 10 cm)
|
||||
3. Press and hold the (I)/(ON) and (O)/(OFF) buttons of the Dimmer Switch for about 10 seconds until your bulb starts to blink
|
||||
4. Your bulb should stop blinking and eventually turn on again. At the same time, a green light on the top left of your remote indicates that your bulb has been successfully reset to factory settings.
|
||||
#### Lutron Connected Bulb Remote
|
||||
|
||||
1. Turn on your Hue bulb/light you want to reset. (It is important that the bulb has just been turned).
|
||||
2. Hold the Dimmer Switch near your bulb (closer than 10 centimeters / 4 inches)
|
||||
3. Press and hold the 2nd (up arrow) and 4th (light off) buttons on the Lutron Connected Bulb Remote simultaneously for about 10 seconds continuously until your bulb starts to blink and the green LED on the remote should also start blink slowly.
|
||||
4. Continue to hold both buttons on the remote until the green LED on it stops blinking. Your bulb should also have stopped blinking and eventually turn on again indicating that your bulb has been successfully reset to factory default settings.
|
||||
|
||||
#### hue-thief
|
||||
|
||||
|
||||
@ -29,13 +29,13 @@ ha_platforms:
|
||||
- switch
|
||||
---
|
||||
|
||||
<p class='note warning'>
|
||||
<div class='note warning'>
|
||||
|
||||
This integration is deprecated. We recommend using [the Z-Wave JS integration](/integrations/zwave_js).
|
||||
|
||||
The Z-Wave integration will no longer receive any updates. It will not be removed unless it becomes incompatible with a future version of Python.
|
||||
|
||||
</p>
|
||||
</div>
|
||||
|
||||
The [Z-Wave](https://www.z-wave.com/) integration for Home Assistant allows you to observe and control connected Z-Wave devices. Please see the [Z-Wave getting started section](/docs/z-wave/) for in-depth documentation on how to use and setup the Z-Wave component.
|
||||
|
||||
|
||||
@ -390,7 +390,7 @@ entities:
|
||||
|
||||
### Buttons row
|
||||
|
||||
Above the divider are regular entity rows, below one of type `buttons`. Note that regular entity rows automatically show the entity name, whereas for buttons you have to explicitely specify a label / name.
|
||||
Above the divider are regular entity rows, below one of type `buttons`. Note that regular entity rows automatically show the entity name, whereas for buttons you have to explicitly specify a label / name.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/lovelace/lovelace_entity_row_buttons.jpg' alt='Screenshot of buttons row'>
|
||||
|
||||
@ -47,6 +47,9 @@ Enjoy the release!
|
||||
- [Release 2021.4.1 - April 8](#release-202141---april-8)
|
||||
- [Release 2021.4.2 - April 9](#release-202142---april-9)
|
||||
- [Release 2021.4.3 - April 10](#release-202143---april-10)
|
||||
- [Release 2021.4.4 - April 13](#release-202144---april-13)
|
||||
- [Release 2021.4.5 - April 16](#release-202145---april-16)
|
||||
- [Release 2021.4.6 - April 19](#release-202146---april-19)
|
||||
- [If you need help...](#if-you-need-help)
|
||||
- [Breaking Changes](#breaking-changes)
|
||||
- [Farewell to the following](#farewell-to-the-following)
|
||||
@ -550,6 +553,65 @@ The following integrations are now available via the Home Assistant UI:
|
||||
[shelly docs]: /integrations/shelly/
|
||||
[zwave_js docs]: /integrations/zwave_js/
|
||||
|
||||
## Release 2021.4.5 - April 16
|
||||
|
||||
- Bump aiodiscover to 1.3.4 ([@bdraco] - [#49142]) ([dhcp docs])
|
||||
- Fix setting up remotes that lack a supported features list in homekit ([@bdraco] - [#49152]) ([homekit docs])
|
||||
- Don't receive homeassistant_* events from MQTT eventstream ([@emontnemery] - [#49158]) ([mqtt_eventstream docs])
|
||||
- Set deprecated supported_features for MQTT JSON light ([@emontnemery] - [#49167]) ([light docs]) ([mqtt docs])
|
||||
- Upgrade spotipy to 2.18.0 ([@frenck] - [#49220]) ([spotify docs])
|
||||
- Fix race when restarting script ([@emontnemery] - [#49247])
|
||||
- Fix mysensors sensor protocol version check ([@MartinHjelmare] - [#49257]) ([mysensors docs])
|
||||
- Fix Coronavirus integration robustness ([@frenck] - [#49287]) ([coronavirus docs])
|
||||
- Mark camera as a base platform ([@ludeeus] - [#49297])
|
||||
|
||||
[#49142]: https://github.com/home-assistant/core/pull/49142
|
||||
[#49152]: https://github.com/home-assistant/core/pull/49152
|
||||
[#49158]: https://github.com/home-assistant/core/pull/49158
|
||||
[#49167]: https://github.com/home-assistant/core/pull/49167
|
||||
[#49220]: https://github.com/home-assistant/core/pull/49220
|
||||
[#49247]: https://github.com/home-assistant/core/pull/49247
|
||||
[#49257]: https://github.com/home-assistant/core/pull/49257
|
||||
[#49287]: https://github.com/home-assistant/core/pull/49287
|
||||
[#49297]: https://github.com/home-assistant/core/pull/49297
|
||||
[@MartinHjelmare]: https://github.com/MartinHjelmare
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@frenck]: https://github.com/frenck
|
||||
[@ludeeus]: https://github.com/ludeeus
|
||||
[coronavirus docs]: /integrations/coronavirus/
|
||||
[dhcp docs]: /integrations/dhcp/
|
||||
[homekit docs]: /integrations/homekit/
|
||||
[light docs]: /integrations/light/
|
||||
[mqtt docs]: /integrations/mqtt/
|
||||
[mqtt_eventstream docs]: /integrations/mqtt_eventstream/
|
||||
[mysensors docs]: /integrations/mysensors/
|
||||
[spotify docs]: /integrations/spotify/
|
||||
|
||||
## Release 2021.4.6 - April 19
|
||||
|
||||
- Apply Precision/Scale/Offset to struct in modbus sensor ([@janiversen] - [#48544]) ([modbus docs])
|
||||
- Upgrade pyMetno to 0.8.2 ([@Danielhiversen] - [#49308]) ([met docs]) ([norway_air docs])
|
||||
- Fix exception in roomba discovery when the device does not respond on the first try ([@bdraco] - [#49360]) ([roomba docs])
|
||||
- Fix deadlock when restarting scripts ([@emontnemery] - [#49410])
|
||||
- Google report state: thermostatMode should be a string, not null ([@bramkragten] - [#49342]) ([google_assistant docs])
|
||||
|
||||
[#48544]: https://github.com/home-assistant/core/pull/48544
|
||||
[#49308]: https://github.com/home-assistant/core/pull/49308
|
||||
[#49342]: https://github.com/home-assistant/core/pull/49342
|
||||
[#49360]: https://github.com/home-assistant/core/pull/49360
|
||||
[#49410]: https://github.com/home-assistant/core/pull/49410
|
||||
[@Danielhiversen]: https://github.com/Danielhiversen
|
||||
[@bdraco]: https://github.com/bdraco
|
||||
[@bramkragten]: https://github.com/bramkragten
|
||||
[@emontnemery]: https://github.com/emontnemery
|
||||
[@janiversen]: https://github.com/janiversen
|
||||
[google_assistant docs]: /integrations/google_assistant/
|
||||
[met docs]: /integrations/met/
|
||||
[modbus docs]: /integrations/modbus/
|
||||
[norway_air docs]: /integrations/norway_air/
|
||||
[roomba docs]: /integrations/roomba/
|
||||
|
||||
## 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).
|
||||
|
||||
107
source/_posts/2021-04-16-community-highlights.markdown
Normal file
107
source/_posts/2021-04-16-community-highlights.markdown
Normal file
@ -0,0 +1,107 @@
|
||||
---
|
||||
title: "Community Highlights: 17th edition"
|
||||
description: "know when your washing machine is ready with a blueprint, get started with the battery state card and bring your smart assistant to the kitchen with Holodeck"
|
||||
date: 2021-04-16 00:00:00
|
||||
date_formatted: "April 16, 2021"
|
||||
author: Klaas Schoute
|
||||
author_twitter: klaasnicolaas
|
||||
categories: Community
|
||||
og_image: /images/blog/2021-04-16-community-highlights/social.png
|
||||
---
|
||||
|
||||
For me personally a small milestone: it’s already the 10th community highlight
|
||||
that I have written. Please let me know in the comments what you think. Some
|
||||
interesting things popped up again around our community, that I 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
|
||||
|
||||
It may have happened to everyone, the washing machine has finished and you have
|
||||
completely forgotten to take it out. We could probably do something with that
|
||||
with a blueprint.
|
||||
|
||||
With the blueprint from [Sbyx](https://community.home-assistant.io/u/sbyx) you
|
||||
put a smart plug on the washing machine and you get a notification when the
|
||||
laundry is ready. Read more about it on the [community forum][week_blueprint] or
|
||||
install this automation in your instance with a click on the My button!
|
||||
|
||||
{% my blueprint_import badge blueprint_url="https://gist.github.com/sbyx/6d8344d3575c9865657ac51915684696" %}
|
||||
|
||||
Bonus side effect: if your smart plug can measure energy, you also immediately
|
||||
know what it uses and how much a wash has cost you. Give it a try!
|
||||
|
||||
|
||||
## Battery state card
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://github.com/maxwroc/battery-state-card" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-04-16-community-highlights/battery.png'
|
||||
alt="Preview from battery state card"
|
||||
style='border: 0;box-shadow: none;width:90%;margin-bottom:10px;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
Do you want to keep an eye on all your battery powered devices? Then try
|
||||
the [battery state card](https://github.com/maxwroc/battery-state-card) from
|
||||
[maxwroc](https://github.com/maxwroc), so that you can see by means of a color
|
||||
which device is almost empty and it's time for a battery replacement.
|
||||
|
||||
<object type="image/svg+xml" data="https://gh-card.dev/repos/maxwroc/battery-state-card.svg?link_target=_blank"></object>
|
||||
|
||||
## Lovelace Dashboard
|
||||
|
||||
Also this week we have a new Lovelace dashboard for the necessary portion of
|
||||
inspiration 😄 This time it has become that of [FreakLikeMe0991](https://www.reddit.com/user/FreakLikeMe0991/),
|
||||
which, like last week's dashboard, mainly focuses on the use from a mobile device.
|
||||
|
||||
<blockquote class="reddit-card" data-card-created="1618574623"><a href="https://www.reddit.com/r/homeassistant/comments/mpiqak/new_3_click_mobile_dashboard_work_in_progress/">New >3 Click Mobile Dashboard - Work in Progress</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><br>
|
||||
|
||||
Would you also like your dashboard to be in the community highlight? Drop it
|
||||
on [Reddit][reddit] and maybe I'll pick it out for the next edition.
|
||||
|
||||
## Holodeck Project
|
||||
|
||||
We also came across a very cool project on our [community forum][community] namely
|
||||
the Holodeck, made by [smowk](https://community.home-assistant.io/u/smowk): a smart
|
||||
assistant in your kitchen. It projects images (like a Lovelace dashboard or cooking
|
||||
video) onto your kitchen cupboard and could be operated by voice. You can read a lot
|
||||
more about it [here][community_project].
|
||||
|
||||
<blockquote class="imgur-embed-pub" lang="en" data-id="a/jIgBmiQ" >
|
||||
<a href="//imgur.com/a/jIgBmiQ">HOLODECK</a>
|
||||
</blockquote><script async src="//s.imgur.com/min/embed.js" charset="utf-8"></script>
|
||||
|
||||
## 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
|
||||
[community]: https://community.home-assistant.io
|
||||
[week_blueprint]: https://community.home-assistant.io/t/notify-or-do-something-when-an-appliance-like-a-dishwasher-or-washing-machine-finishes/254841
|
||||
[community_project]: https://community.home-assistant.io/t/holodeck-project-projection-based-kitchen-assistant/297148
|
||||
130
source/_posts/2021-04-23-community-highlights.markdown
Normal file
130
source/_posts/2021-04-23-community-highlights.markdown
Normal file
@ -0,0 +1,130 @@
|
||||
---
|
||||
title: "Community Highlights: 18th edition"
|
||||
description: "Pause a movie with a blueprint, get started with the EV Charger Card and an update from the internship regarding Home Assistant Energy!"
|
||||
date: 2021-04-23 00:00:00
|
||||
date_formatted: "April 23, 2021"
|
||||
author: Klaas Schoute
|
||||
author_twitter: klaasnicolaas
|
||||
categories: Community
|
||||
og_image: /images/blog/2021-04-23-community-highlights/social.png
|
||||
---
|
||||
|
||||
The 18th 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
|
||||
------
|
||||
|
||||
You probably recognize it, while watching a movie you need to go to the
|
||||
toilet and you forget to pause the movie! What if you could automate this
|
||||
with a blueprint?
|
||||
|
||||
{% my blueprint_import badge blueprint_url="https://community.home-assistant.io/t/pause-movie-when-light-is-switched-on/289882" %}
|
||||
|
||||
With the blueprint from [jfedor](https://community.home-assistant.io/u/jfedor)
|
||||
you can pause your media player by turning on a light and if you turn it off
|
||||
within a certain time, the media player will continue. Read more about it on
|
||||
the [community forum][week_blueprint] or install this automation in your instance
|
||||
with a click on the my button!
|
||||
|
||||
## Lovelace Dashboard
|
||||
------
|
||||
|
||||
Also this week we have a new Lovelace dashboard for the necessary portion of
|
||||
inspiration 😄 This time it has become that of [Crixle](https://www.reddit.com/user/Crixle/),
|
||||
what he has made in the past 5 months. Possibly this design can be used quite
|
||||
well for a tablet on the wall. Take also a look at the [original post](https://www.reddit.com/r/homeassistant/comments/mufpxw/complete_newbie_5_months_ago_and_this_is_what_my/) on Reddit
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://www.reddit.com/r/homeassistant/comments/mufpxw/complete_newbie_5_months_ago_and_this_is_what_my/" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-04-23-community-highlights/dashboard.png'
|
||||
alt="Preview from battery state card"
|
||||
style='border: 0;box-shadow: none;width:100%;margin-bottom:15px;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
Would you also like your dashboard to be in the community highlight? Drop it
|
||||
on [Reddit][reddit] and maybe I'll pick it out for the next edition.
|
||||
|
||||
## EV Charger Card
|
||||
------
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://www.reddit.com/r/homeassistant/comments/mufpxw/complete_newbie_5_months_ago_and_this_is_what_my/" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-04-23-community-highlights/charger-card.png'
|
||||
alt="Preview of the EV Charger Card"
|
||||
style='border: 0;box-shadow: none;width:60%;margin-bottom:15px;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
Looking for a way to show the charging of your electric car in a beautiful
|
||||
way in Lovelace? Then try the [EV Charger card](https://github.com/tmjo/charger-card)
|
||||
made by [tmjo](https://github.com/tmjo).
|
||||
|
||||
<a href="https://github.com/tmjo/charger-card"><img style="border: 0;" src="https://gh-card.dev/repos/tmjo/charger-card.svg"></a>
|
||||
|
||||
## Home Assistant Energy
|
||||
------
|
||||
__*Internship progress*__
|
||||
|
||||
It has been 11 weeks since I started as an intern at [Nabu Casa][nabu_casa], where
|
||||
I focus on how Home Assistant can be used to gain insight into your energy data and
|
||||
how to optimize your consumption. Time to give a brief summary of what is currently
|
||||
going on.
|
||||
|
||||
We are currently trying to design a ready-made Lovelace dashboard, in which all your
|
||||
energy data comes together. You can see a first paper prototype sketch below, if you
|
||||
have input on this topic, please share it with me via the [Twitter thread](https://twitter.com/klaasnicolaas/status/1384584214402719746)!
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<img
|
||||
src='/images/blog/2021-04-23-community-highlights/sketch.png'
|
||||
alt="Sketches that are made for Home Assistant Energy"
|
||||
style='border: 0;box-shadow: none;width:90%;margin-bottom:15px;'
|
||||
/>
|
||||
</div>
|
||||
|
||||
In addition, I’m also working on an analog pulse meter, working with [ESPHome][esphome]
|
||||
that you can use to read the pulse LED on a meter. YAML configs for power plugs from
|
||||
Blitzwolf etc.
|
||||
|
||||
More information can also be found in the twitter thread below.
|
||||
|
||||
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I'm doing an internship at <a href="https://twitter.com/NabuCasa?ref_src=twsrc%5Etfw">@NabuCasa</a> with the goal to discover how <a href="https://twitter.com/home_assistant?ref_src=twsrc%5Etfw">@home_assistant</a> can be used to gain insight in your energy usage and help optimize it.<br><br>I will be using this thread to show some of the things that I have done so far. <a href="https://t.co/0lLJxt15Nn">pic.twitter.com/0lLJxt15Nn</a></p>— Klaas Schoute (@klaasnicolaas) <a href="https://twitter.com/klaasnicolaas/status/1384584214402719746?ref_src=twsrc%5Etfw">April 20, 2021</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
|
||||
|
||||
## 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
|
||||
[community]: https://community.home-assistant.io
|
||||
[nabu_casa]: https://www.nabucasa.com
|
||||
[esphome]: https://esphome.io
|
||||
[week_blueprint]: https://community.home-assistant.io/t/pause-movie-when-light-is-switched-on/289882
|
||||
@ -28,7 +28,8 @@ regenerate: false
|
||||
</p>
|
||||
|
||||
<p class="note">
|
||||
Add-ons are only available if you've used the Home Assistant installer. If you
|
||||
Add-ons are only available if you've used the Home Assistant Operating System or
|
||||
Home Assistant Supervised <a href="/installation">installation</a> method. If you
|
||||
installed Home Assistant using any other method then you cannot use add-ons.
|
||||
Often you can achieve the same manually, refer to the documentation by the
|
||||
vendor of the application you'd like to install.
|
||||
|
||||
BIN
source/images/blog/2021-04-16-community-highlights/battery.png
Normal file
BIN
source/images/blog/2021-04-16-community-highlights/battery.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 115 KiB |
BIN
source/images/blog/2021-04-16-community-highlights/social.png
Normal file
BIN
source/images/blog/2021-04-16-community-highlights/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 201 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
BIN
source/images/blog/2021-04-23-community-highlights/dashboard.png
Normal file
BIN
source/images/blog/2021-04-23-community-highlights/dashboard.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 695 KiB |
BIN
source/images/blog/2021-04-23-community-highlights/sketch.png
Normal file
BIN
source/images/blog/2021-04-23-community-highlights/sketch.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 2.9 MiB |
BIN
source/images/blog/2021-04-23-community-highlights/social.png
Normal file
BIN
source/images/blog/2021-04-23-community-highlights/social.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 378 KiB |
Loading…
x
Reference in New Issue
Block a user