mirror of
https://github.com/home-assistant/home-assistant.io.git
synced 2025-07-23 09:17:06 +00:00
Merge branch 'current' into next
This commit is contained in:
commit
8ff0f1770c
@ -25,8 +25,8 @@ GEM
|
||||
http_parser.rb (~> 0.6.0)
|
||||
eventmachine (1.2.7)
|
||||
eventmachine (1.2.7-x64-mingw32)
|
||||
ffi (1.15.0)
|
||||
ffi (1.15.0-x64-mingw32)
|
||||
ffi (1.15.1)
|
||||
ffi (1.15.1-x64-mingw32)
|
||||
forwardable-extended (2.6.0)
|
||||
http_parser.rb (0.6.0)
|
||||
i18n (1.8.10)
|
||||
|
806
package-lock.json
generated
806
package-lock.json
generated
File diff suppressed because it is too large
Load Diff
@ -10,7 +10,7 @@
|
||||
"remark-lint-fenced-code-flag": "^2.0.1",
|
||||
"remark-lint-no-shell-dollars": "^2.0.2",
|
||||
"remark-stringify": "^9.0.1",
|
||||
"textlint": "^11.9.1",
|
||||
"textlint": "^12.0.0",
|
||||
"textlint-rule-common-misspellings": "^1.0.1",
|
||||
"textlint-rule-terminology": "^2.1.5"
|
||||
},
|
||||
|
@ -29,8 +29,7 @@ As "Service Data" we want a simple text that is shown as part of the notificatio
|
||||
message: Sensor value greater than 10
|
||||
```
|
||||
|
||||
Automation created or edited via the user interface, are activated immediately
|
||||
after save the automation.
|
||||
Automations created or edited via the user interface are activated immediately after saving the automation.
|
||||
|
||||
## Troubleshooting missing automations
|
||||
|
||||
|
@ -653,6 +653,12 @@ Webhook endpoints don't require authentication, other than knowing a valid webho
|
||||
|
||||
Note that a given webhook can only be used in one automation at a time. That is, only one automation trigger can use a specific webhook ID.
|
||||
|
||||
In order to reference `trigger.json`, the `Content-Type` header must be specified with a value of `application/json`, e.g.:
|
||||
|
||||
```bash
|
||||
curl -X POST -H "Content-Type: application/json" https://your-home-assistant:8123/api/webhook/some_hook_id
|
||||
```
|
||||
|
||||
## Zone trigger
|
||||
|
||||
Zone trigger fires when an entity is entering or leaving the zone. The entity can be either a person, or a device_tracker. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/integrations/gpslogger/), the [OwnTracks platform](/integrations/owntracks/) and the [iCloud platform](/integrations/icloud/).
|
||||
|
@ -45,14 +45,6 @@ Event `call_service` is fired to call a service.
|
||||
| `service_data` | Dictionary with the service call parameters. Example: `{ 'brightness': 120 }`. |
|
||||
| `service_call_id` | String with a unique call id. Example: `23123-4`. |
|
||||
|
||||
## Event `service_executed`
|
||||
|
||||
Event `service_executed` is fired by the service handler to indicate the service is done.
|
||||
|
||||
| Field | Description |
|
||||
| ----------------- | ----------------------------------------------------------------------------------------- |
|
||||
| `service_call_id` | String with the unique call id of the service call that was executed. Example: `23123-4`. |
|
||||
|
||||
## Event `automation_reloaded`
|
||||
|
||||
Event `automation_reloaded` is fired when automations have been reloaded and thus might have changed.
|
||||
|
@ -18,11 +18,11 @@ Templating is a powerful feature that allows you to control information going in
|
||||
|
||||
Templating in Home Assistant is powered by the [Jinja2](https://palletsprojects.com/p/jinja) templating engine. This means that we are using their syntax and make some custom Home Assistant variables available to templates during rendering. Jinja2 supports a wide variety of operations:
|
||||
|
||||
- [Mathematical operation](https://jinja.palletsprojects.com/en/master/templates/#math)
|
||||
- [Comparisons](https://jinja.palletsprojects.com/en/master/templates/#comparisons)
|
||||
- [Logic](https://jinja.palletsprojects.com/en/master/templates/#logic)
|
||||
- [Mathematical operation](https://jinja.palletsprojects.com/en/latest/templates/#math)
|
||||
- [Comparisons](https://jinja.palletsprojects.com/en/latest/templates/#comparisons)
|
||||
- [Logic](https://jinja.palletsprojects.com/en/latest/templates/#logic)
|
||||
|
||||
We will not go over the basics of the syntax, as Jinja2 does a great job of this in their [templates documentation](https://jinja.palletsprojects.com/en/master/templates/).
|
||||
We will not go over the basics of the syntax, as Jinja2 does a great job of this in their [templates documentation](https://jinja.palletsprojects.com/en/latest/templates/).
|
||||
|
||||
The frontend has a {% my developer_templates title="template editor tool" %} to help develop and debug templates. Navigate to {% my developer_templates title="Developer Tools > Template" %}, create your template in the _Template editor_ and check the results on the right.
|
||||
|
||||
@ -51,9 +51,9 @@ script:
|
||||
There are a few very important rules to remember when adding templates to YAML:
|
||||
|
||||
1. You **must** surround single-line templates with double quotes (`"`) or single quotes (`'`).
|
||||
1. It is advised that you prepare for undefined variables by using `if ... is not none` or the [`default` filter](http://jinja.pocoo.org/docs/dev/templates/#default), or both.
|
||||
1. It is advised that when comparing numbers, you convert the number(s) to a [`float`](http://jinja.pocoo.org/docs/dev/templates/#float) or an [`int`](http://jinja.pocoo.org/docs/dev/templates/#int) by using the respective [filter](http://jinja.pocoo.org/docs/dev/templates/#list-of-builtin-filters).
|
||||
1. While the [`float`](http://jinja.pocoo.org/docs/dev/templates/#float) and [`int`](http://jinja.pocoo.org/docs/dev/templates/#int) filters do allow a default fallback value if the conversion is unsuccessful, they do not provide the ability to catch undefined variables.
|
||||
1. It is advised that you prepare for undefined variables by using `if ... is not none` or the [`default` filter](https://jinja.palletsprojects.com/en/latest/templates/#default), or both.
|
||||
1. It is advised that when comparing numbers, you convert the number(s) to a [`float`](https://jinja.palletsprojects.com/en/latest/templates/#float) or an [`int`](https://jinja.palletsprojects.com/en/latest/templates/#int) by using the respective [filter](https://jinja.palletsprojects.com/en/latest/templates/#list-of-builtin-filters).
|
||||
1. While the [`float`](https://jinja.palletsprojects.com/en/latest/templates/#float) and [`int`](https://jinja.palletsprojects.com/en/latest/templates/#int) filters do allow a default fallback value if the conversion is unsuccessful, they do not provide the ability to catch undefined variables.
|
||||
|
||||
Remembering these simple rules will help save you from many headaches and endless hours of frustration when using automation templates.
|
||||
|
||||
@ -422,7 +422,7 @@ Closest to some entity:
|
||||
|
||||
### Numeric functions and filters
|
||||
|
||||
Some of these functions can also be used in a [filter](https://jinja.palletsprojects.com/en/master/templates/#id11). This means they can act as a normal function like this `sqrt(2)`, or as part of a filter like this `2|sqrt`.
|
||||
Some of these functions can also be used in a [filter](https://jinja.palletsprojects.com/en/latest/templates/#id11). This means they can act as a normal function like this `sqrt(2)`, or as part of a filter like this `2|sqrt`.
|
||||
|
||||
- `log(value, base)` will take the logarithm of the input. When the base is omitted, it defaults to `e` - the natural logarithm. Can also be used as a filter.
|
||||
- `sin(value)` will return the sine of the input. Can be used as a filter.
|
||||
|
@ -13,7 +13,7 @@ Choose a meaningful name for your scene.
|
||||
<img src='/images/docs/scenes/editor.png' />
|
||||
</p>
|
||||
|
||||
Select all the devices (and/or entities when in advanced mode) you want to include in your scene.
|
||||
Select all the devices (or entities when advanced mode is enabled on your user profile) you want to include in your scene.
|
||||
The state of your devices will be saved, so it can be restored when you are finished creating your scene.
|
||||
Set the state of the devices to how you want them to be in your scene, this can be done by clicking on it and edit the state from the popup, or any other method that changes the state.
|
||||
On the moment you save the scene, all the states of your devices are stored in the scene.
|
||||
|
@ -96,8 +96,8 @@ While executing a script you can add a condition to stop further execution. When
|
||||
|
||||
```yaml
|
||||
# If paulus is home, continue to execute the script below these lines
|
||||
alias: "Check if Paulus is home"
|
||||
- condition: state
|
||||
- alias: "Check if Paulus is home"
|
||||
condition: state
|
||||
entity_id: device_tracker.paulus
|
||||
state: "home"
|
||||
```
|
||||
|
@ -15,7 +15,7 @@ You need to have a compatible Z-Wave stick or module installed. This needs to be
|
||||
|
||||
<div class='note'>
|
||||
|
||||
There are [known compatability issues](https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245031#p1502030) with older hardware versions of the Aeotec stick not working on the Raspberry Pi 4. Aeotec has released a 2020 hardware revision ZW090-A/B/C Gen5+ with Pi 4 compatibility. Both hardware revisions are still being sold, make informed purchasing decisions if using paired with a Pi 4.
|
||||
There are [known compatibility issues](https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245031#p1502030) with older hardware versions of the Aeotec stick not working on the Raspberry Pi 4. Aeotec has released a 2020 hardware revision ZW090-A/B/C Gen5+ with Pi 4 compatibility. Both hardware revisions are still being sold, make informed purchasing decisions if using paired with a Pi 4.
|
||||
|
||||
</div>
|
||||
|
||||
|
@ -32,6 +32,7 @@ This integration is a meta-component and configures a default set of integration
|
||||
- [Scene](/integrations/scene/) (`scene`)
|
||||
- [Scripts](/integrations/script/) (`script`)
|
||||
- [Simple Service Discovery Protocol (SSDP)](/integrations/ssdp/) (`ssdp`)
|
||||
- [Stream](/integrations/stream/) (`stream`)
|
||||
- [Sun](/integrations/sun/) (`sun`)
|
||||
- [System Health](/integrations/system_health/) (`system_health`)
|
||||
- [Tag](/integrations/tag/) (`tag`)
|
||||
|
@ -30,6 +30,8 @@ devolo Home Control is a Z-Wave ecosystem with a Z-Wave to IP gateway in the cen
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
Please do not change the URL provided in the advanced mode unless you know what you are doing.
|
||||
|
||||
## Switches
|
||||
|
||||
The integration provides support for the following Z-Wave devices:
|
||||
|
@ -30,7 +30,7 @@ Add the following to your `configuration.yaml` file:
|
||||
sensor:
|
||||
platform: dht
|
||||
sensor: DHT22
|
||||
pin: D23
|
||||
pin: 23
|
||||
monitored_conditions:
|
||||
- temperature
|
||||
- humidity
|
||||
@ -71,7 +71,7 @@ humidity_offset:
|
||||
type: [integer, float]
|
||||
{% endconfiguration %}
|
||||
|
||||
The name of the pin to which the sensor is connected has different names on different platforms. 'P8_11' for Beaglebone, 'D23' for Raspberry Pi.
|
||||
The name of the pin to which the sensor is connected has different names on different platforms. 'P8_11' for Beaglebone, '23' for Raspberry Pi.
|
||||
|
||||
### Example
|
||||
|
||||
@ -81,7 +81,7 @@ An example for a Raspberry Pi 3 with a DHT22 sensor connected to GPIO4 (pin 7):
|
||||
sensor:
|
||||
- platform: dht
|
||||
sensor: DHT22
|
||||
pin: D4
|
||||
pin: 4
|
||||
temperature_offset: 2.1
|
||||
humidity_offset: -3.2
|
||||
monitored_conditions:
|
||||
|
@ -42,6 +42,10 @@ There is currently support for the following device types within Home Assistant:
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
<div class='note'>
|
||||
The configuration in the UI asks for a username. Starting from FRITZ!OS 7.24 the FRITZ!Box creates a random username for the admin user if you didn't set one yourself. This can be found after logging into the FRITZ!Box and visiting System -> FRITZ!Box Users -> Users. The username starts with "fritz" followed by four random numbers. Under properties on the right it says "created automatically". Prior to FRITZ!OS 7.24 the default username was "admin".
|
||||
</div>
|
||||
|
||||
## Switches & Thermostats
|
||||
|
||||
To get AVM FRITZ!DECT switches (e.g. FRITZ!DECT 400/440) or thermostats (e.g. FRITZ!DECT 301) follow the [configuration instructions](#configuration) above.
|
||||
|
@ -23,7 +23,22 @@ You need two Google accounts. Account A is the account that has to be set up to
|
||||
|
||||
### Note for existing location sharing users
|
||||
|
||||
If you already have other people sharing their location to your existing Account A and do not wish to ask them to also share their location with a new Account B. Create the new Google account (account B) and share the location of Account B back to Account A. Follow the steps listed, substituting the instructions stating “Account B” for “Account A” (i.e., a cookie file is from Account A, slugified username of Account A), then ensure both Account A and Account B are logged in on your mobile device.
|
||||
If you already have other people sharing their location with your existing Account A and do not wish to ask them to also share their location with a new Account B. Simply repeat the steps above to obtain a valid cookie from Google for Account A. Then add both accounts to the device tracker configuration (don’t forget to include the multiple cookie files, one for each account being added to the integration).
|
||||
|
||||
```yaml
|
||||
# Example configuration.yaml entry
|
||||
device_tracker:
|
||||
- platform: google_maps
|
||||
username: "ACCOUNT_A_EMAIL"
|
||||
- platform: google_maps
|
||||
username: "ACCOUNT_B_EMAIL"
|
||||
```
|
||||
|
||||
<div class='note'>
|
||||
If using more than one account, your own device may show twice, however, the parameters returned from Account A will not include a value for battery_level or entity_picture. These parameters will be present in your device tracker entity from Account B. Therefore, disregard the device tracker entity with is missing those parameters.
|
||||
</div>
|
||||
|
||||
|
||||
|
||||
|
||||
## Configuration
|
||||
|
@ -10,7 +10,7 @@ ha_platforms:
|
||||
- tts
|
||||
---
|
||||
|
||||
The `google_translate` text-to-speech platform uses the unofficial [Google Translate Text-to-Speech engine](https://translate.google.com/) to read a text with natural sounding voices.
|
||||
The `google_translate` text-to-speech platform uses the unofficial [Google Translate Text-to-Speech engine](https://translate.google.com/) to read a text with natural sounding voices. Contrary to what the name suggests, the integration only does text-to-speech and does not translate messages sent to it.
|
||||
|
||||
## Configuration
|
||||
|
||||
@ -24,7 +24,7 @@ tts:
|
||||
|
||||
{% configuration %}
|
||||
language:
|
||||
description: "The language to use."
|
||||
description: "The default speech language to use."
|
||||
required: false
|
||||
type: string
|
||||
default: "`en`"
|
||||
@ -33,6 +33,8 @@ language:
|
||||
Check the [complete list of supported languages](https://translate.google.com/intl/en_ALL/about/languages/) (languages where "Talk" feature is enabled in Google Translate) for allowed values.
|
||||
Use the 2 digit language code which you can find at the end of URL when you click on Language name.
|
||||
|
||||
For more information about using text-to-speech with Home Assistant and more details on all the options it provides, see the [TTS documentation](/integrations/tts/).
|
||||
|
||||
## Full configuration example
|
||||
|
||||
A full configuration sample including optional variables:
|
||||
|
@ -15,6 +15,7 @@ ha_platforms:
|
||||
---
|
||||
|
||||
The iAlarm integration provides connectivity with the [Antifurto365](https://www.antifurtocasa365.it/) iAlarm alarm systems and has also been confirmed to work with the alarm system brands Meian and Emooluxr.
|
||||
Please note that the latest iAlarm-XR alarm system is not supported.
|
||||
|
||||
This platform supports the following services:
|
||||
|
||||
|
@ -27,10 +27,6 @@ It does require that your devices are registered with the [Find My](https://www.
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
<div class='note warning'>
|
||||
Low `max_interval` may cause battery drainage as it wakes up your device to get the current location.
|
||||
</div>
|
||||
|
||||
<div class='note warning'>
|
||||
You may receive an email and a notification from Apple saying that someone has logged into your account.
|
||||
|
||||
@ -61,7 +57,7 @@ The iCloud integration will add a battery sensor for each iCloud devices availab
|
||||
|
||||
### Service `icloud.update`
|
||||
|
||||
This service can be used to ask an update of a certain iDevice or all devices linked to an iCloud account. Request will result in new Home Assistant [state_changed](/docs/configuration/events/#event-state_changed) event describing current iPhone location. It can be used in automations when a manual location update is needed, e.g., to check if anyone is home when a door been opened.
|
||||
This service can be used to ask an update of a certain iDevice or all devices linked to an iCloud account. Request will result in new Home Assistant [state_changed](/docs/configuration/events/#event-state_changed) event describing current iPhone location. It can be used in automations when a manual location update is needed, e.g., to check if anyone is home when a door has been opened.
|
||||
|
||||
### Service `icloud.play_sound`
|
||||
|
||||
|
@ -64,7 +64,9 @@ method:
|
||||
default: trapezoidal
|
||||
{% endconfiguration %}
|
||||
|
||||
In case you have an appliance which produces spikey consumption (like an on/off electrical boiler) you should opt for the `left` method to get accurate readings. If `unit` is set then `unit_prefix` and `unit_time` are ignored.
|
||||
In case you have an appliance which produces spikey consumption (like an on/off electrical boiler) you should opt for the `left` method to get accurate readings.
|
||||
|
||||
The unit of `source` together with `unit_prefix` and `unit_time` is used to generate a unit for the integral product (e.g. a source in `W` with prefix `k` and time `h` would result in `kWh`). You can override this behavior by providing a custom value for `unit`. Note that `unit_prefix` and `unit_time` are _also_ relevant to the Riemann sum calculation. Even if you provide a custom value for `unit`, ensure prefix and time accurately reflect the properties of your source data.
|
||||
|
||||
## Energy
|
||||
|
||||
|
@ -171,12 +171,12 @@ automation:
|
||||
to: "open"
|
||||
condition:
|
||||
- condition: state
|
||||
entity_id: alarm_control_panel.ha_alarm
|
||||
entity_id: alarm_control_panel.home_alarm
|
||||
state: armed_away
|
||||
action:
|
||||
service: alarm_control_panel.alarm_trigger
|
||||
target:
|
||||
entity_id: alarm_control_panel.ha_alarm
|
||||
entity_id: alarm_control_panel.home_alarm
|
||||
```
|
||||
|
||||
Sending a notification when the alarm is triggered.
|
||||
@ -186,7 +186,7 @@ automation:
|
||||
- alias: 'Send notification when alarm triggered'
|
||||
trigger:
|
||||
- platform: state
|
||||
entity_id: alarm_control_panel.ha_alarm
|
||||
entity_id: alarm_control_panel.home_alarm
|
||||
to: "triggered"
|
||||
action:
|
||||
- service: notify.notify
|
||||
@ -207,7 +207,7 @@ automation:
|
||||
action:
|
||||
- service: alarm_control_panel.alarm_disarm
|
||||
target:
|
||||
entity_id: alarm_control_panel.house_alarm
|
||||
entity_id: alarm_control_panel.home_alarm
|
||||
```
|
||||
|
||||
Sending a Notification when the Alarm is Armed (Away/Home), Disarmed and in Pending Status
|
||||
|
@ -16,6 +16,12 @@ ha_platforms:
|
||||
|
||||
The integration allows you to control [Motion Blinds](https://motion-blinds.com) from [Coulisse B.V.](https://coulisse.com/products/motion).
|
||||
|
||||
Additionally the following brands have been reported to also work with this integration:
|
||||
|
||||
- [Motion Blinds](https://motion-blinds.com)
|
||||
- [Dooya](http://www.dooya.com/)
|
||||
- [Bloc Blinds](https://www.blocblinds.com/)
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
## Retrieving the API Key
|
||||
|
@ -29,6 +29,10 @@ If a Plex server has been claimed by a Plex account via the [claim interface](ht
|
||||
|
||||
{% include integrations/config_flow.md %}
|
||||
|
||||
During setup, the integration will check all possible ways to connect to your Plex server(s) - i.e., local or public addresses, HTTP or HTTPS, by IP or using a subdomain of `plex.direct`, or by using a Plex relay if all other methods fail. The integration will prefer local over public and secure over insecure, in that order. The selected address is shown on the Plex card on the Integrations page.
|
||||
|
||||
If your router enforces DNS rebind protection, connections to the local `plex.direct` hostname may fail (see [Plex documentation](https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/#dnsrebinding)). To avoid this, configure your router to allow DNS rebinding for `plex.direct` by following the instructions in the documentation link.
|
||||
|
||||
### Integration Options
|
||||
|
||||
Several options are provided to adjust the behavior of `media_player` entities. These can be changed at **Plex** -> **Options** on the Integrations page.
|
||||
|
@ -70,9 +70,44 @@ Shelly device relays are added to the Home Assistant by default as `switch` enti
|
||||
|
||||
## Events
|
||||
|
||||
If the **BUTTON TYPE** of the switch connected to the device is set to `momentary` or `detached switch`, integration fires events when the switch is used. You can use these events in your automations.
|
||||
If the **BUTTON TYPE** of the switch connected to the device is set to `momentary` or `detached switch`, integration fires events under the type `shelly.click` when the switch is used. You can use these events in your automations.
|
||||
|
||||
### Automation examples
|
||||
Also, some devices do not add an entity for the button/switch. For example, the Shelly Button1 has only one entity for the battery level. It does not have an entity for the button itself. To trigger automations based on button presses, use the `shelly.click` event.
|
||||
|
||||
### Listening for events
|
||||
|
||||
You can subscribe to the `shelly.click` event type in [Developer Tools/Events](/docs/tools/dev-tools/) in order to examine the event data JSON for the correct parameters to use in your automations. For example, `shelly.click` returns event data JSON similar to the following when you press the Shelly Button1.
|
||||
|
||||
```json
|
||||
Event 0 fired 9:53 AM:
|
||||
{
|
||||
"event_type": "shelly.click",
|
||||
"data": {
|
||||
"device_id": "e09c64a22553484d804353ef97f6fcd6",
|
||||
"device": "shellybutton1-A4C12A45174",
|
||||
"channel": 1,
|
||||
"click_type": "single"
|
||||
},
|
||||
"origin": "LOCAL",
|
||||
"time_fired": "2021-04-28T08:53:12.755729+00:00",
|
||||
"context": {
|
||||
"id": "e0f379706563aaa0c2c1fda5174b5a0e",
|
||||
"parent_id": null,
|
||||
"user_id": null
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Automations
|
||||
|
||||
The simplest way to create automations is to use the Home Assistant automation editor. For example, to set an automation triggered by a double press of a particular Shelly Button1:
|
||||
|
||||
1. In the Triggers section of the automation, set Trigger Type to `Device`.
|
||||
2. In the Device dropdown menu. find the Shelly Button1.
|
||||
3. In the Trigger dropdown menu, select `Button double clicked`.
|
||||
4. Set any conditions and actions to complete your automation.
|
||||
|
||||
You can also create automations using YAML, for example:
|
||||
|
||||
```yaml
|
||||
- alias: "Toggle living room light"
|
||||
|
@ -32,8 +32,6 @@ sensor:
|
||||
entity_id: sensor.cpu
|
||||
- platform: statistics
|
||||
entity_id: binary_sensor.movement
|
||||
max_age:
|
||||
minutes: 30
|
||||
```
|
||||
|
||||
{% configuration %}
|
||||
|
@ -85,6 +85,12 @@ Entities reporting status, total size (TB), used size (TB), % of volume used, av
|
||||
|
||||
Entities reporting the update and security status of the NAS.
|
||||
|
||||
<div class='note'>
|
||||
|
||||
The security status corresponds with the analysis of the DSM Security Advisor, e.g., an `outOfDate` state for the `Update` attribute not only reflects the update status of the installed DSM version but also the status of the installed DSM packages.
|
||||
|
||||
</div>
|
||||
|
||||
### Disk sensors
|
||||
|
||||
Similar to the [normal disk sensors](#disk-sensors), there are binary sensors reporting each drive's status. These sensors report if a drive has exceeded the maximum threshold for detected bad sectors and if a drive has dropped below the threshold for its remaining life.
|
||||
|
@ -40,6 +40,9 @@ resources:
|
||||
required: false
|
||||
{% endconfiguration %}
|
||||
|
||||
After restarting Home Assistant, these sensors will show up and update their
|
||||
information every 15 seconds.
|
||||
|
||||
The table contains types and their argument to use in your `configuration.yaml`
|
||||
file.
|
||||
|
||||
|
@ -128,13 +128,13 @@ monitored_conditions:
|
||||
detault: All conditions
|
||||
type: list
|
||||
keys:
|
||||
current_bandwidth_used:
|
||||
current_bandwidth_gb:
|
||||
description: The current (invoice period) bandwidth usage in Gigabytes (GB).
|
||||
pending_charges:
|
||||
description: The current (invoice period) charges that have built up for this subscription. Value is in US Dollars (US$).
|
||||
{% endconfiguration %}
|
||||
|
||||
Full `configuration.yaml` using `{}` to format condition name (produces `sensor.server_current_bandwidth_used` and `sensor.server_pending_charges`):
|
||||
Full `configuration.yaml` using `{}` to format condition name (produces `sensor.server_current_bandwidth_gb` and `sensor.server_pending_charges`):
|
||||
|
||||
```yaml
|
||||
sensor:
|
||||
@ -142,7 +142,7 @@ sensor:
|
||||
name: Server {}
|
||||
subscription: 123456
|
||||
monitored_conditions:
|
||||
- current_bandwidth_used
|
||||
- current_bandwidth_gb
|
||||
- pending_charges
|
||||
```
|
||||
|
||||
|
@ -191,6 +191,7 @@ This integration is tested to work with the following models. If you have a diff
|
||||
| `mono` | YLTD03YL | Yeelight Serene Eye-Friendly Desk Lamp |
|
||||
| `ceiling10` | YLDL01YL | Yeelight Meteorite Pendant Light |
|
||||
| `ceiling13` | YLXD01YL | Yeelight LED Ceiling Light |
|
||||
| `ceil26` | YLXD76YL | Yeelight Ceiling Light - Updated HomeKit 23w |
|
||||
| `lamp` | MJTD02YL | Xiaomi Mijia Desk Lamp Pro |
|
||||
|
||||
## Services
|
||||
|
102
source/_posts/2021-05-21-community-highlights.markdown
Normal file
102
source/_posts/2021-05-21-community-highlights.markdown
Normal file
@ -0,0 +1,102 @@
|
||||
---
|
||||
title: "Community Highlights: 22nd edition"
|
||||
description: "A new highlight with 2 new cards that you can use, blueprint for those who always leave the door open and give your TV an upgrade with Hyperion project."
|
||||
date: 2021-05-21 00:00:00
|
||||
date_formatted: "May 21, 2021"
|
||||
author: Klaas Schoute
|
||||
author_twitter: klaasnicolaas
|
||||
categories: Community
|
||||
og_image: /images/blog/2021-05-21-community-highlights/social.png
|
||||
---
|
||||
|
||||
The 22nd 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 <br>
|
||||
*Intern on Home Assistant Energy*
|
||||
|
||||
## Blueprint of the week
|
||||
------
|
||||
|
||||
Are you one of those who always leave the doors open?
|
||||
|
||||
Then this week we have a nice blueprint for you! [BasTijs](https://community.home-assistant.io/u/bastijs )
|
||||
has made a blueprint that announces through text to speech in the house,
|
||||
that a door is open and only stops when the door is closed again.
|
||||
|
||||
{% my blueprint_import badge blueprint_url="https://community.home-assistant.io/t/door-open-tts-announcer/266252" %}
|
||||
|
||||
Try it out! Read more about it on the [community forum][week_blueprint] or
|
||||
install this automation in your instance with a click on the My button!
|
||||
|
||||
## Sun card
|
||||
------
|
||||
|
||||
<div style="margin:0 auto; text-align:center">
|
||||
<a href="https://github.com/AitorDB/home-assistant-sun-card" target="_blank">
|
||||
<img
|
||||
src='/images/blog/2021-05-21-community-highlights/sun-card.png'
|
||||
alt="preview of the sun card"
|
||||
style='border: 0;box-shadow: none;width:80%;margin-bottom:15px;'
|
||||
/>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
On our [Home Assistant reddit][reddit] page we also encountered another nice
|
||||
project, namely that of [AitorDB](https://github.com/AitorDB). Who made a
|
||||
[Lovelace card](https://github.com/AitorDB/home-assistant-sun-card) that shows
|
||||
the position of the sun when it rises, is at its highest point and sets again.
|
||||
|
||||
<a href="https://github.com/AitorDB/home-assistant-sun-card"><img style="border: 0;" src="https://gh-card.dev/repos/AitorDB/home-assistant-sun-card.svg"></a>
|
||||
|
||||
## Collapsed card
|
||||
------
|
||||
|
||||
Is your Lovelace dashboard overflowing with cards and do you want to
|
||||
make some free space? Then try the card made by [RossMcMillan92](https://github.com/RossMcMillan92),
|
||||
which makes it possible to collapse entire cards and reappear as a dropdown.
|
||||
|
||||
<a href="https://github.com/RossMcMillan92/lovelace-collapsable-cards"><img style="border: 0;" src="https://gh-card.dev/repos/RossMcMillan92/lovelace-collapsable-cards.svg"></a>
|
||||
|
||||
## Hyperion - HA bridge
|
||||
------
|
||||
|
||||
<iframe src="https://drive.google.com/file/d/1nQzYOKjLEz-CBqsog2uumT8Dyv8r0y-A/preview" width="100%" height="400" style="margin-bottom:15px;"></iframe>
|
||||
|
||||
You have those TVs where LEDs are mounted on the back so that the colors of
|
||||
the TV continue over the wall behind it, this is also called ambilight. If
|
||||
your TV is not equipped with this, you can also make this yourself through
|
||||
the [Hyperion project](https://hyperion-project.org). [pimw](https://community.home-assistant.io/u/pimw)
|
||||
has also written an [instruction post](https://community.home-assistant.io/t/instruction-hyperion-ha-bridge-home-assistant/307708)
|
||||
about this on our [community forum][community] on how to connect the bridge
|
||||
to Home Assistant.
|
||||
|
||||
## 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/door-open-tts-announcer/266252
|
BIN
source/images/blog/2021-05-21-community-highlights/social.png
Normal file
BIN
source/images/blog/2021-05-21-community-highlights/social.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 129 KiB |
BIN
source/images/blog/2021-05-21-community-highlights/sun-card.png
Normal file
BIN
source/images/blog/2021-05-21-community-highlights/sun-card.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 22 KiB |
Loading…
x
Reference in New Issue
Block a user