jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-18 23:06:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into rc

Browse Source
This commit is contained in:
Franck Nijhof 2024-11-05 17:17:33 +01:00
commit b58b5f8f12
No known key found for this signature in database
GPG Key ID: D62583BA8AB11CA3
29 changed files with 121 additions and 105 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Gemfile
View File

@ -10,11 +10,10 @@ group :development do
gem 'stringex', '2.8.6'
# > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
gem 'sassc', '2.1.0'
# 1.80.5 breaks the build
gem 'sass-embedded', '1.80.4'
gem 'rubocop', '1.67.0'
gem 'ruby-lsp', '0.20.1'
gem 'rackup', '2.1.0'
gem 'sass-embedded', '1.80.6'
gem 'rubocop', '1.68.0'
gem 'ruby-lsp', '0.21.2'
gem 'rackup', '2.2.0'
end
group :jekyll_plugins do

29
Gemfile.lock
View File

@ -66,7 +66,7 @@ GEM
nokogiri (~> 1.12)
jekyll-watch (2.2.1)
listen (~> 3.0)
json (2.7.4)
json (2.7.6)
kramdown (2.4.0)
rexml
kramdown-parser-gfm (1.1.0)
@ -86,7 +86,7 @@ GEM
nokogiri (1.16.7-x86_64-linux)
racc (~> 1.4)
parallel (1.26.3)
parser (3.3.5.0)
parser (3.3.5.1)
ast (~> 2.4.1)
racc
pathutil (0.16.2)
@ -100,9 +100,8 @@ GEM
rack (>= 3.0.0, < 4)
rack-session (2.0.0)
rack (>= 3.0.0)
rackup (2.1.0)
rackup (2.2.0)
rack (>= 3)
webrick (~> 1.8)
rainbow (3.1.1)
rake (13.2.1)
rb-fsevent (0.11.2)
@ -113,7 +112,7 @@ GEM
regexp_parser (2.9.2)
rexml (3.3.9)
rouge (4.4.0)
rubocop (1.67.0)
rubocop (1.68.0)
json (~> 2.3)
language_server-protocol (>= 3.17.0)
parallel (~> 1.10)
@ -123,9 +122,9 @@ GEM
rubocop-ast (>= 1.32.2, < 2.0)
ruby-progressbar (~> 1.7)
unicode-display_width (>= 2.4.0, < 3.0)
rubocop-ast (1.33.0)
rubocop-ast (1.34.0)
parser (>= 3.3.1.0)
ruby-lsp (0.20.1)
ruby-lsp (0.21.2)
language_server-protocol (~> 3.17.0)
prism (>= 1.2, < 2.0)
rbs (>= 3, < 4)
@ -134,9 +133,9 @@ GEM
ruby2_keywords (0.0.5)
safe_yaml (1.0.5)
sass (3.4.25)
sass-embedded (1.80.5-arm64-darwin)
sass-embedded (1.80.6-arm64-darwin)
google-protobuf (~> 4.28)
sass-embedded (1.80.5-x86_64-linux-gnu)
sass-embedded (1.80.6-x86_64-linux-gnu)
google-protobuf (~> 4.28)
sass-globbing (1.1.5)
sass (>= 3.1)
@ -150,7 +149,7 @@ GEM
rack-protection (= 4.0.0)
rack-session (>= 2.0.0, < 3)
tilt (~> 2.0)
sorbet-runtime (0.5.11625)
sorbet-runtime (0.5.11633)
stringex (2.8.6)
terminal-table (3.0.2)
unicode-display_width (>= 1.1.1, < 3)
@ -160,7 +159,7 @@ GEM
tzinfo-data (1.2024.2)
tzinfo (>= 1.0.0)
unicode-display_width (2.6.0)
webrick (1.8.2)
webrick (1.9.0)
PLATFORMS
arm64-darwin-23
@ -174,11 +173,11 @@ DEPENDENCIES
jekyll-sitemap (= 1.4.0)
jekyll-toc (= 0.19.0)
nokogiri (= 1.16.7)
rackup (= 2.1.0)
rackup (= 2.2.0)
rake (= 13.2.1)
rubocop (= 1.67.0)
ruby-lsp (= 0.20.1)
sass-embedded (= 1.80.4)
rubocop (= 1.68.0)
ruby-lsp (= 0.21.2)
sass-embedded (= 1.80.6)
sass-globbing (= 1.1.5)
sassc (= 2.1.0)
sinatra (= 4.0.0)

5
sass/homeassistant/base/_global.scss
View File

@ -64,6 +64,11 @@ table {
}
}
.text-input,
textarea {
cursor: text;
}
.gist {
font-size: 0.75em;
}

9
source/_dashboards/glance.markdown
View File

@ -115,15 +115,6 @@ double_tap_action:
type: map
{% endconfiguration %}
### Options for exemptions
{% configuration badges %}
user:
required: true
description: User ID that can see the view tab.
type: string
{% endconfiguration %}
### Examples
Basic example:

9
source/_dashboards/picture-elements.markdown
View File

@ -407,15 +407,6 @@ style:
default: "position: absolute, transform: translate(-50%, -50%)"
{% endconfiguration %}
## Options for exemptions
{% configuration badges %}
user:
required: true
description: User ID that can see the view tab.
type: string
{% endconfiguration %}
## Notes on element attributes
### How to use the style object

9
source/_dashboards/picture-glance.markdown
View File

@ -143,15 +143,6 @@ double_tap_action:
type: map
{% endconfiguration %}
### Options for exemptions
{% configuration badges %}
user:
required: true
description: User ID that can see the view tab.
type: string
{% endconfiguration %}
### How to use state_filter
Specify different [CSS filters](https://developer.mozilla.org/en-US/docs/Web/CSS/filter)

4
source/_dashboards/todo-list.markdown
View File

@ -74,6 +74,6 @@ Title example:
```yaml
type: todo-list
entity: todo-list
title: todo list
entity: todo.todo_list
title: Todo List
```

2
source/_includes/common-tasks/network_storage.md
View File

@ -1,6 +1,6 @@
## Network storage
You can configure both Network File Share (NFS) and Windows samba (CIFS) targets to be used within Home Assistant and add-ons.
You can configure both Network File System (NFS) and Samba/Windows (CIFS) targets to be used within Home Assistant and add-ons.
To list all your currently connected network storages, go to **{% my storage title="Settings > System > Storage" %}** in the UI.
{% if page.installation == "os" %}

3
source/_includes/installation/container/alternative.md
View File

@ -1,7 +1,6 @@
### Synology NAS
Synology with DSM now supports Docker, allowing you to install Home Assistant using Docker without the need for command-line. For details about the package (including compatibility-information, if your NAS is supported), see <https://www.synology.com/en-us/dsm/packages/Docker>
Synology with DSM now supports container management through the Container Manager package, allowing you to install Home Assistant without the need for command-line. For details about the package (including compatibility-information, if your NAS is supported), see <https://www.synology.com/en-us/dsm/packages/ContainerManager>
The steps would be:
- Install Docker "Container Manager" package on your Synology NAS

10
source/_integrations/alexa.smart_home.markdown
View File

@ -231,17 +231,17 @@ Now remove the long-lived access token (if you want), copy the ARN of your Lambd
## Account linking
Alexa needs to link your Amazon account to your Home Assistant account. Therefore Home Assistant can make sure only authenticated Alexa requests are able to access your home's devices. In order to link the account, you have to make sure your Home Assistant can be accessed from Internet at port 443.
Alexa needs to link your Amazon account to your Home Assistant account. Therefore Home Assistant can make sure only authenticated Alexa requests are able to access your home's devices. In order to link the account, you have to make sure your Home Assistant can be accessed from Internet.
- Return to the [Alexa Developer Console][alexa-dev-console], go to `Alexa Skills` page if you are not.
- 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]`. For Alexa account linking, by default, the standard port 443 is used. Use your firewall to forward this, if needed:
- `Authorization URI`: `https://[YOUR HOME ASSISTANT URL]/auth/authorize`
- `Access Token URI`: `https://[YOUR HOME ASSISTANT URL]/auth/token`
- Input all information required. Assuming your Home Assistant can be accessed by `https://[YOUR HOME ASSISTANT URL][:PORT]`, where `PORT` is the TCP port. The port can be omitted if it is `443`. For Alexa account linking, by default, the standard port 443 is used by default. Use your firewall to forward this, if needed:
- `Authorization URI`: `https://[YOUR HOME ASSISTANT URL][:PORT]/auth/authorize`
- `Access Token URI`: `https://[YOUR HOME ASSISTANT URL][:PORT]/auth/token`
Although it is possible to assign a different port, Alexa requires you use port 443, so make sure your firewall/proxy is forwarding via port 443.
Although it is possible to assign a different port, it is preferable to use port 443, so in that case make sure your firewall/proxy is forwarding via port 443.
Read [more from the Alexa developer documentation](https://developer.amazon.com/en-US/docs/alexa/account-linking/requirements-account-linking.html) about requirements for account linking.

2
source/_integrations/calendar.markdown
View File

@ -177,7 +177,7 @@ Add a new calendar event. A calendar `target` is selected with a [Target Selecto
You either use `start_date_time` and `end_date_time`, or `start_date` and `end_date`, or `in`.
{% endnote %}
This is a full example of a {% term service %} call in YAML:
This is a full example of an {% term action %} in YAML:
```yaml
action: calendar.create_event

1
source/_integrations/epson.markdown
View File

@ -39,6 +39,7 @@ When you want to add a device for the first time, turn it on before following th
- Epson EH-TW7000
- Epson EH-TW9400W (shares platform with 7400/8400/9400(w))
- Epson EH-TW3200
- Epson Powerlite W39
## Configuration

10
source/_integrations/history_stats.markdown
View File

@ -121,7 +121,11 @@ Depending on the sensor type you choose, the `history_stats` integration can sho
- **time**: The default value, which is the tracked time, in hours
- **ratio**: The tracked time divided by the length of your period, as a percentage
- **count**: How many times the tracked entity matched the configured state during the time period
- **count**: How many times the tracked entity matched the configured state during the time period. This will count states (for example, how many times a light was in the `on` state during the time period), as opposed to counting state transitions (for example, how many times a light was *turned* `on`). The difference is if the entity was already in the desired state at the start of the time period, that scenario will be counted with this sensor type.
{% note %}
For a count sensor that uses a time period that does not slide (such as one that resets upon each hour, as opposed to one which considers the trailing 60 minutes), consider using [customization](/docs/configuration/customizing-devices/#customizing-an-entity-in-yaml) to change the `state_class` to `total_increasing` to generate statistics that track the `sum`. This is useful when emulating the behavior of a `utility_meter` helper that has a defined reset cycle. Without intervention, the `state_class` of any `history_stats` sensor will be `measurement` and will therefore generate `average`, `min`, and `max` statistics.
{% endnote %}
## Time periods
@ -158,6 +162,10 @@ duration:
If the duration exceeds the number of days of history stored by the `recorder` integration (`purge_keep_days`), the history statistics sensor will not have all the information it needs to look at the entire duration. For example, if `purge_keep_days` is set to 7, a history statistics sensor with a duration of 30 days will only report a value based on the last 7 days of history.
{% endnote %}
{% note %}
The history stats sensor will be updated when the source entity changes or once per minute if there is no source change. Keep this in mind when using fixed durations that aren't evenly divisible by one minute.
{% endnote %}
### Video tutorial
This video tutorial explains how you can use history stats. It also shows how you can create a daily bar chart graph to visualize things such as occupancy, or how long the lights are on in a particular room.

2
source/_integrations/http.markdown
View File

@ -73,7 +73,7 @@ ip_ban_enabled:
description: Flag indicating whether additional IP filtering is enabled.
required: false
type: boolean
default: false
default: true
login_attempts_threshold:
description: "Number of failed login attempt from single IP after which it will be automatically banned if `ip_ban_enabled` is `true`. When set to -1 no new automatic bans will be added."
required: false

4
source/_integrations/intent_script.markdown
View File

@ -46,7 +46,7 @@ intent:
description: List of domains that the entity supports.
required: false
type: list
actions:
action:
description: Defines an action to run to intents.
required: false
type: action
@ -109,7 +109,7 @@ conversation:
intent_script:
EventCountToday:
actions:
action:
- action: calendar.get_events
target:
entity_id: calendar.my_calendar

28
source/_integrations/jewish_calendar.markdown
View File

@ -100,35 +100,35 @@ The following is the list of holidays the sensor knows about with their selected
| yom_kippur | Yom Kippur | יום הכפורים | YOM_TOV | 1 |
| erev_sukkot | Erev Sukkot | ערב סוכות | EREV_YOM_TOV | 2 |
| sukkot | Sukkot | סוכות | YOM_TOV | 1 |
| sukkot_ii | Sukkot II | שני של סוכות | YOM_TOV | 1 |
| hol_hamoed_sukkot | Hol hamoed Sukkot | חול המועד סוכות | HOL_HAMOED | 3 |
| hoshana_raba | Hoshana Raba | הושענא רבה | EREV_YOM_TOV | 2 |
| shmini_atzeret | Shmini Atzeret | שמיני עצרת | YOM_TOV | 1 |
| simchat_torah | Simchat Torah | שמחת תורה | YOM_TOV | 1 |
| chanukah | Chanukah | חנוכה | MELACHA_PERMITTED_HOLIDAY | 4 |
| rabin_memorial_day | Yitzhak Rabin memorial day | יום הזכרון ליצחק רבין | MEMORIAL_DAY | 8 |
| asara_btevet | Asara B'Tevet | צום עשרה בטבת | FAST_DAY | 5 |
| tu_bshvat | Tu B'Shvat | ט"ו בשבט | MINOR_HOLIDAY | 7 |
| family_day | Family Day | יום המשפחה | ISRAEL_NATIONAL_HOLIDAY | 9 |
| memorial_day_unknown | Memorial day for fallen whose place of burial is unknown | יום הזיכרון לחללי מערכות ישראל שמקום קבורתם לא נודע | MEMORIAL_DAY | 8 |
| taanit_esther | Ta'anit Esther | תענית אסתר | FAST_DAY | 5 |
| purim | Purim | פורים | MELACHA_PERMITTED_HOLIDAY | 4 |
| shushan_purim | Shushan Purim | שושן פורים | MELACHA_PERMITTED_HOLIDAY | 4 |
| erev_pesach | Erev Pesach | ערב פסח | EREV_YOM_TOV | 2 |
| pesach | Pesach | פסח | YOM_TOV | 1 |
| pesach_ii | Pesach II | שני של פסח | YOM_TOV | 1 |
| hol_hamoed_pesach | Hol hamoed Pesach | חול המועד פסח | HOL_HAMOED | 3 |
| pesach_vii | Pesach VII | שביעי פסח | YOM_TOV | 1 |
| yom_haatzmaut | Yom HaAtzma'ut | יום העצמאות | MODERN_HOLIDAY | 6 |
| lag_bomer | Lag B'Omer | ל"ג בעומר | MINOR_HOLIDAY | 7 |
| erev_shavuot | Erev Shavuot | ערב שבועות | EREV_YOM_TOV | 2 |
| shavuot | Shavuot | שבועות | YOM_TOV | 1 |
| tzom_tammuz | Tzom Tammuz | צום שבעה עשר בתמוז | FAST_DAY | 5 |
| tisha_bav | Tish'a B'Av | תשעה באב | FAST_DAY | 5 |
| tu_bav | Tu B'Av | ט"ו באב | MINOR_HOLIDAY | 7 |
| pesach_viii | Pesach VIII | אחרון של פסח | YOM_TOV | 1 |
| yom_hashoah | Yom HaShoah | יום השואה | MEMORIAL_DAY | 8 |
| yom_hazikaron | Yom HaZikaron | יום הזכרון | MEMORIAL_DAY | 8 |
| yom_haatzmaut | Yom HaAtzma'ut | יום העצמאות | MODERN_HOLIDAY | 6 |
| lag_bomer | Lag B'Omer | ל"ג בעומר | MINOR_HOLIDAY | 7 |
| yom_yerushalayim | Yom Yerushalayim | יום ירושלים | MODERN_HOLIDAY | 6 |
| shmini_atzeret | Shmini Atzeret | שמיני עצרת | YOM_TOV | 1 |
| pesach_viii | Pesach VIII | אחרון של פסח | YOM_TOV | 1 |
| erev_shavuot | Erev Shavuot | ערב שבועות | EREV_YOM_TOV | 2 |
| shavuot | Shavuot | שבועות | YOM_TOV | 1 |
| shavuot_ii | Shavuot II | שני של שבועות | YOM_TOV | 1 |
| sukkot_ii | Sukkot II | שני של סוכות | YOM_TOV | 1 |
| pesach_ii | Pesach II | שני של פסח | YOM_TOV | 1 |
| family_day | Family Day | יום המשפחה | ISRAEL_NATIONAL_HOLIDAY | 9 |
| memorial_day_unknown | Memorial day for fallen whose place of burial is unknown | יום הזיכרון לחללי מערכות ישראל שמקום קבורתם לא נודע | MEMORIAL_DAY | 8 |
| rabin_memorial_day | Yitzhak Rabin memorial day | יום הזכרון ליצחק רבין | MEMORIAL_DAY | 8 |
| tzom_tammuz | Tzom Tammuz | צום שבעה עשר בתמוז | FAST_DAY | 5 |
| zeev_zhabotinsky_day | Zeev Zhabotinsky day | יום זאב ז'בוטינסקי | MEMORIAL_DAY | 8 |
| tisha_bav | Tish'a B'Av | תשעה באב | FAST_DAY | 5 |
| tu_bav | Tu B'Av | ט"ו באב | MINOR_HOLIDAY | 7 |

2
source/_integrations/remote_rpi_gpio.markdown
View File

@ -19,7 +19,7 @@ related:
The `remote_rpi_gpio` {% term integration %} is the base for all related GPIO platforms in Home Assistant. For the platform configurations, please check their corresponding sections.
The remote Raspberry Pi, and the control computer where Home Assistant is running must be configured to be able to run `remote_rpi_gpio`, see [Configuring Remote GPIO](https://gpiozero.readthedocs.io/en/stable/remote_gpio.html) for more details.
The remote Raspberry Pi, and the control computer where Home Assistant is running must be configured to be able to run `remote_rpi_gpio`, see [Configuring Remote GPIO](https://gpiozero.readthedocs.io/en/stable/remote_gpio.html) for more details. Unfortunately, this setup is not currently possible with remote, Raspberry Pi 5 hosts, [due to a lack of support in pigiod](https://github.com/joan2937/pigpio/issues/586).
Note that for virtual environments, you may need to set an environment variable when starting the environment to set the pin factory, for example:

6
source/_integrations/schedule.markdown
View File

@ -171,10 +171,10 @@ triggers:
- schedule.light_schedule
to: "on"
actions:
- service: light.turn_on
- action: light.turn_on
target:
entity_id: climate.thermostat
data_template:
entity_id: light.kitchen
data:
brightness_pct: "{{ state_attr('schedule.light_schedule', 'brightness') }}"
kelvin: "{{ state_attr('schedule.light_schedule, 'temperature') }}"
```

13
source/_integrations/statistics.markdown
View File

@ -20,19 +20,14 @@ ha_config_flow: true
The `statistics` integration observes the state of a source sensor and provides aggregated statistical characteristics about its recent past. This integration can be useful in automation, for example, to trigger an action when the air humidity in the bathroom settles after a hot shower or when the number of brewed coffees over a day gets too high.
The `statistics` sensor can use either the numeric `sensor` or `binary_sensor` as it's input. The time period and/or number of recent state changes, which should be considered, must be given in configuration. Check the configuration section below for details.
The statistics sensor updates with every update of the source sensor, for which the numeric `sensor` and `binary_sensor` are supported. The time period and/or number of recent state changes, which should be considered, must be given in configuration. Check the configuration section below for details.
Assuming the [`recorder`](/integrations/recorder/) integration is running, historical sensor data is read from the database on startup and is available immediately after a restart of the platform. If the [`recorder`](/integrations/recorder/) integration is *not* running, it can take some time for the sensor to start reporting data because some characteristics calculations require more than one source sensor value.
{% tip %}
The `statistics` integration is not the same as the [Long-term Statistics](https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics). More details on the differences can be found in the [2021.8.0 release notes](/blog/2021/08/04/release-20218/#long-term-statistics).
The `statistics` integration is different to [Long-term Statistics](https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics). More details on the differences can be found in the [2021.8.0 release notes](/blog/2021/08/04/release-20218/#long-term-statistics).
{% endtip %}
The `statistics` sensor has an internal buffer that stores the values it needs for the computation of the various functions (for example, `average_step`). The sensor is updated whenever new values are added to the buffer or when elements are removed. This is triggered either by a change of the source sensor (which may or may not change its actual value) or by values expiring (in cases where `max_age` was specified). This means that the buffer can hold a sequence of identical values in cases where values are not changing over time.
When using a time-based buffer (by providing a `max_age`), it is recommended to ensure that the buffer contains at least a decent number of values spanning the full range of time. For sensors that don't change much, this can be achieved by using a template sensor with a time-based trigger as input. If the input values don't cover most of the time range, the computed output values could lead to unexpected results.
Example: To find out whether a switch was used in the last 5 minutes, `count_on` could be used. However, if there are no frequent readings a single "Off" (maybe only a second ago) in the buffer would produce 0 even though the sensor was "On" for most of the last five minutes.
{% include integrations/config_flow.md %}
Further information about these configuration options can be found under the [YAML configuration](#yaml-configuration)
@ -66,8 +61,8 @@ The following are supported for `sensor` source sensors `state_characteristic`:
| State Characteristic | Description |
| -------------------- | ----------- |
| `average_linear` | The average value of stored measurements under consideration of the time distances between them. A linear interpolation is applied per measurement pair. Suited to observe a source sensor with frequent, non-periodic sensor updates and when continuous behavior is represented by the measurements (e.g. your electricity consumption). WARNING: This doesn't compute the exact average over the full interval defined by `max_age`. It will only consider the interval between the first and the last value in the buffer. |
| `average_step` | The average value of stored measurements under consideration of the time distances between them. LOCF (last observation carried forward weighting) is applied, meaning, that the old value is assumed between two measurements. This is a better fit to how Home Assistant deals with constant values (compared to the linear function) and it is also better fitting to sensors that are switching between stable phases (e.g. a heating level set to either 1, 2 or 3). WARNING: This doesn't compute the exact average over the full interval defined by `max_age`. It will only consider the interval between the first and the last value in the buffer. |
| `average_linear` | The average value of stored measurements under consideration of the time distances between them. A linear interpolation is applied per measurement pair. Suited to observe a source sensor with frequent, non-periodic sensor updates and when continuous behavior is represented by the measurements (e.g. your electricity consumption). WARNING: This type of average may show unexpected behavior in cases where values remain stable (e.g. an equally spaced sequence of t1:0 -> t2:0 -> t3:0 -> t4:0 -> t5:10 would produce an average of 5 instead of 1,25 because the non-changing zeros in the middle (t2 to t4) are being filtered out by Home Assistant and so the actually computed curve already starts rising at t1 instead of staying flat until t4). Accordingly, this function is only making sense in the context of noisy sensors that keep changing constantly. |
| `average_step` | The average value of stored measurements under consideration of the time distances between them. LOCF (last observation carried forward weighting) is applied, meaning, that the old value is assumed between two measurements. This is a better fit to how Home Assistant deals with constant values (compared to the linear function) and it is also better fitting to sensors that are switching between stable phases (e.g. a heating level set to either 1, 2 or 3). WARNING: Even when a time interval is specified by the max age parameter, the average is not necessarily matching the average over that whole interval (e.g. when values were removed due to the sampling size limit). |
| `average_timeless` | The average value of stored measurements. This method assumes that all measurements are equally spaced and, therefore, time is ignored and a simple average of values is computed. Equal to `mean`. |
| `change_sample` | The average change per sample. The difference between the newest and the oldest measurement is divided by the number of in-between measurements (n-1). |
| `change_second` | The average change per second. The difference between the newest and the oldest measurement is divided by seconds between them. |

4
source/_integrations/tado.markdown
View File

@ -38,6 +38,10 @@ There is currently support for the following device types within Home Assistant:
- Sensor - for some additional information of the zones.
- Weather - for information about the current weather at the location of your Tado home.
## Unsupported device types
New Tado X devices are not supported by this integration, they have to be used through the [Matter integration](/integrations/matter).
{% include integrations/config_flow.md %}
The Tado thermostats are internet connected thermostats. There exists an unofficial API at [my.tado.com](https://my.tado.com/), which is used by their website and now by this component.

1
source/_integrations/verisure.markdown
View File

@ -96,6 +96,7 @@ Some users have reported that this integration currently doesn't work in the fol
- France
- Ireland
- Italy
- Spain
- Sweden
## Troubleshooting

2
source/connectzbt1/index.html
View File

@ -601,7 +601,7 @@ frontpage_image: /images/connectzbt1/connectzbt1-cover.jpg
</a>
<a
href="https://smarterhome.sk/en/zwave-pc-adapters/home-assistant-skyconnect-zigbee-and-thread-usb-controller-1403.html"
href="https://smarterhome.sk/sk/zwave-pc-adaptery/home-assistant-connect-zbt-1-zigbee-a-thread-usb-adapter-1646.html"
target="_blank"
>
<div class="distributor">

20
source/green/index.html
View File

@ -2489,6 +2489,24 @@ dark_header: true
</svg>
</div>
</a>
<a
href="https://dinamotech.it/products/home-assistant-green"
target="_blank"
>
<div class="distributor">
<div>
<div>🇮🇹</div>
<div>Dinamotech</div>
<div>Shipping from Italy</div>
</div>
<svg width="24" height="24" viewBox="0 0 24 24">
<path
d="M8.59,16.58L13.17,12L8.59,7.41L10,6L16,12L10,18L8.59,16.58Z"
/>
</svg>
</div>
</a>
<a
href="https://www.domadoo.fr/fr/box-domotique/7046-nabu-casa-box-domotique-home-assistant-green-0794677011758.html"
@ -2707,7 +2725,7 @@ dark_header: true
</a>
<a
href="https://smarterhome.sk/controllers/home-assistant-green-smart-home-hub-1490.html"
href="https://smarterhome.sk/sk/centralne-jednotky/home-assistant-green-smart-home-hub-1490.html"
target="_blank"
>
<div class="distributor">

BIN
source/images/assist/wearos_assist_app.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 219 KiB

2
source/integrations/index.html
View File

@ -120,7 +120,7 @@ regenerate: false
<div class="grid__item four-fifths lap-one-whole palm-one-whole">
<div class="component-search">
<form onsubmit="event.preventDefault(); return false">
<input type="text" name="search" id="search" class="search" placeholder="Search integrations..." autofocus />
<input type="text" name="search" id="search" class="search text-input" placeholder="Search integrations..." autofocus />
</form>
</div>
<div class="hass-option-cards" id="componentContainer"> </div>

6
source/more-info/statistics.markdown
View File

@ -3,6 +3,10 @@ title: "Expected data source not listed"
description: "More information on if your expected data source is not listed."
---
You're configuring a statistic but you couldn't find your source in the dropdown? That's caused by a bug in the integration providing the entity. Integrations need to configure their entities correctly so Home Assistant knows that we need to track statistics for it and how.
You're configuring a statistic but you couldn't find your source in the dropdown?
Check that it hasn't been excluded in the [Recorder](https://www.home-assistant.io/integrations/recorder/) configuration.
Otherwise, It's caused by a bug in the integration providing the entity. Integrations need to configure their entities correctly so Home Assistant knows that we need to track statistics for it and how.
Open an issue with the author of the integration and link them to https://developers.home-assistant.io/docs/core/entity/sensor#long-term-statistics.

3
source/privacy/index.markdown
View File

@ -48,7 +48,7 @@ Ads appearing on any of our websites may be delivered to users by advertising pa
## Companion Applications
All information collected by the applications is sent directly to your hosted instance of Home Assistant. This includes, but is not limited to, sensor data and location data, which at times is sent while the application is in the background. At no point is this data logged or given to a 3rd party.
All information collected by the applications is sent directly to your hosted instance of Home Assistant. This includes, but is not limited to, sensor, health, and location data, which at times is sent while the application is in the background. At no point is this data logged or given to a 3rd party.
## Privacy Policy Changes
@ -58,6 +58,7 @@ Although most changes are likely to be minor, Home Assistant may change its Priv
- October 19, 2017: Initial version
- October 19, 2020: Add information about Companion Applications
- October 30, 2024: Add health data to Companion Applications
_This privacy policy has been adapted from the [Automattic privacy policy][Home Assistant] and is licensed [Creative Commons ShareAlike][cc]._

29
source/voice_control/android.markdown
View File

@ -11,17 +11,25 @@ related:
## Assist on Android phones
Assist is available on Android phones and tablets using the [Home Assistant Companion App](https://companion.home-assistant.io/docs/getting_started/) for Android.
Assist can be used on Android phones and tablets using the [Home Assistant Companion App](https://companion.home-assistant.io/docs/getting_started/).
### Prerequisites
- [Home Assistant Companion App](https://companion.home-assistant.io/docs/getting_started/) installed
- Have an Assistant set up: either [cloud](/voice_control/voice_remote_cloud_assistant/) (recommended, more performant) or [local](/voice_control/voice_remote_local_assistant/).
- The devices you want to control with Assist are [exposed to Assist](/voice_control/voice_remote_expose_devices/)
### Setting up Home Assistant Assist as default assistant app on an Android phone
### Starting Assist in Home Assistant
1. On your phone, open Home Assistant.
2. In the top-right corner, select the three-dots menu and select **Assist**.
3. [Give a command](/voice_control/custom_sentences/).
### Setting up Home Assistant Assist as default assistant app
This section was written using an Android 13. Depending on your flavor of Android, the exact steps may vary.
To define Home Assistant Assist as default assistant app, follow these steps:
To define Home Assistant Assist as default assistant app on your Android phone, follow these steps:
1. On the Android phone, go to **Settings** > **Apps** > **Default apps**.
2. Under **Digital assistant app**, select **Default digital assistant app**.
@ -76,9 +84,11 @@ Assist is available on Wear OS using the [Home Assistant Companion App](https://
The way how Assist can be set up on your phone may differ depending on your version of Wear OS.
1. After [installing the companion app](https://companion.home-assistant.io/docs/getting_started/) and connecting it to your Home Assistant, Assist might appear automatically on the **Apps screen**.
2. If it does not, visit your watch companion app or the Wear OS app and select **Add tile** inside the **Tiles** area.
3. Tap the **Assist** tile to add it to your watch:
1. After [installing the companion app](https://companion.home-assistant.io/docs/getting_started/) on your watch and connecting it to your Home Assistant, Assist appears automatically on the **Apps screen**.
![Assist app](/images/assist/wearos_assist_app.png)
2. To add an Assist tile, in the Wear OS app, go to the **Tiles** area, select **Add tile** > **Assist**.
![Conversation tile](/images/assist/android_tile.png)
@ -94,10 +104,10 @@ The way how Assist can be set up on your phone may differ depending on your vers
![Assist complication](/images/assist/android_watch_5.png)
### Using Assist on Wear OS
1. On your watch, swipe left until the **Assist** button is visible.
1. On your watch, open Assist.
- For example, swipe left until the **Assist** button is visible.
![Assist button](/images/assist/android_watch_1.png)
@ -114,10 +124,9 @@ The way how Assist can be set up on your phone may differ depending on your vers
![List of assistants](/images/assist/android_watch_6.png)
### Setting up Home Assistant Assist as default assistant app on a Wear OS watch
This procedure was written using Wear OS version 3.5. The exact steps may vary depending on the watch and software version.
This procedure was written using Wear OS version 4.0. The exact steps may vary depending on the watch and software version.
To define Home Assistant Assist as default assistant app, follow these steps:

2
source/voice_control/custom_sentences.markdown
View File

@ -148,7 +148,7 @@ As mentioned above, you can then use the `intent_script` integration to implemen
# Example configuration.yaml
intent_script:
SetVolume:
actions:
action:
service: "media_player.volume_set"
data:
entity_id: "{{ media_player }}"