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-16 05:46:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'current' into next

Browse Source
This commit is contained in:
Franck Nijhof 2025-06-25 11:39:04 +00:00
commit 7e22546b28
No known key found for this signature in database
GPG Key ID: AB33ADACE7101952
34 changed files with 866 additions and 775 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Gemfile
View File

@ -11,8 +11,8 @@ group :development do
# > 2.1.0 causes slowdowns https://github.com/sass/sassc-ruby/issues/189
gem 'sassc', '2.1.0'
gem 'sass-embedded', '1.89.2'
gem 'rubocop', '1.76.2'
gem 'ruby-lsp', '0.24.1'
gem 'rubocop', '1.77.0'
gem 'ruby-lsp', '0.24.2'
gem 'rackup', '2.2.1'
end

10
Gemfile.lock
View File

@ -119,7 +119,7 @@ GEM
regexp_parser (2.10.0)
rexml (3.4.1)
rouge (4.5.2)
rubocop (1.76.2)
rubocop (1.77.0)
json (~> 2.3)
language_server-protocol (~> 3.17.0.2)
lint_roller (~> 1.1.0)
@ -133,7 +133,7 @@ GEM
rubocop-ast (1.45.1)
parser (>= 3.3.7.2)
prism (~> 1.4)
ruby-lsp (0.24.1)
ruby-lsp (0.24.2)
language_server-protocol (~> 3.17.0)
prism (>= 1.2, < 2.0)
rbs (>= 3, < 5)
@ -159,7 +159,7 @@ GEM
rack-protection (= 4.1.1)
rack-session (>= 2.0.0, < 3)
tilt (~> 2.0)
sorbet-runtime (0.5.12189)
sorbet-runtime (0.5.12201)
stringex (2.8.6)
terminal-table (3.0.2)
unicode-display_width (>= 1.1.1, < 3)
@ -185,8 +185,8 @@ DEPENDENCIES
nokogiri (= 1.18.8)
rackup (= 2.2.1)
rake (= 13.3.0)
rubocop (= 1.76.2)
ruby-lsp (= 0.24.1)
rubocop (= 1.77.0)
ruby-lsp (= 0.24.2)
sass-embedded (= 1.89.2)
sass-globbing (= 1.1.5)
sassc (= 2.1.0)

4
_config.yml
View File

@ -108,8 +108,8 @@ social:
# Home Assistant release details
current_major_version: 2025
current_minor_version: 6
current_patch_version: 1
date_released: 2025-06-13
current_patch_version: 3
date_released: 2025-06-24
# Either # or the anchor link to latest release notes in the blog post.
# Must be prefixed with a # and have double quotes around it.

967
package-lock.json generated
View File

File diff suppressed because it is too large Load Diff

2
package.json
View File

@ -15,7 +15,7 @@
"remark-lint-prohibited-strings": "^4.0.0",
"remark-lint-unordered-list-marker-style": "^4.0.1",
"remark-stringify": "^11.0.0",
"textlint": "^14.8.4",
"textlint": "^15.0.1",
"textlint-filter-rule-comments": "^1.2.2",
"textlint-rule-common-misspellings": "^1.0.1",
"textlint-rule-terminology": "^5.0.13"

109
source/_docs/automation/templating.markdown
View File

@ -1,30 +1,37 @@
---
title: "Automation trigger variables"
description: "List all available variables made available by triggers."
title: "Automation Templates"
description: "List all trigger variables available to templates."
---
Automations support [templating](/docs/configuration/templating/) in the same way as scripts do. In addition to the [Home Assistant template extensions](/docs/configuration/templating/#home-assistant-template-extensions) available to scripts, the `trigger` and `this` template variables are available.
Automations support the advanced features of [templating](/docs/configuration/templating/) in the same way as scripts do. In addition to the [Home Assistant template extensions](/docs/configuration/templating/#home-assistant-template-extensions) available to scripts, the `trigger` and `this` template variables are available for automations.
The template variable `this` is also available when evaluating any `trigger_variables` declared in the configuration.
Example of variables used in templates:
## Available `this` data
```jinja
{{ this.name }} is the name of the automation executing from this trigger
{{ trigger.platform }} is the type of trigger object, like `calendar`
```
The variable `this` is the [state object](/docs/configuration/state_object) of the automation at the moment of triggering the actions. State objects also contain context data which can be used to identify the user that caused a {% term script %} or {% term automation %} to execute. Note that `this` will not change while executing the {% term actions %}.
## Available state data
The template variable `this` is an object that contains the [state](/docs/configuration/state_object) of the automation at the moment of triggering the actions and can be used to evaluate [`trigger_variables`](/docs/automation/trigger/#trigger-variables) declared in the configuration of the active {% term trigger %}.
State objects also contain context data which can be used to identify the user that caused a {% term script %} or {% term automation %} to execute. Note that `this` will not change while executing the {% term actions %}.
## Available trigger data
The variable `trigger` is an object that contains details about which {% term trigger %} triggered the automation.
The template variable `trigger` is an object that contains details about which {% term platform %} triggered the automation. The `platform` property contains the name of the {% term platform %} whose event triggered the automation.
Templates can use the data to modify the actions performed by the automation or displayed in a message. For example, you could create an automation that multiple sensors can trigger and then use the sensor's location to specify a light to activate; or you could send a notification containing the friendly name of the sensor that triggered it.
Each [trigger platform](/docs/automation/trigger/#event-trigger) can include additional data specific to that platform.
Each [trigger](/docs/automation/trigger/#event-trigger) platform includes additional data specific to that {% term platform %}.
### All
Triggers from all platforms will include the following data.
Triggers from all platforms will include the following properties.
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Trigger object type.
| `trigger.alias` | Alias of the trigger.
| `trigger.id` | The [`id` of the trigger](/docs/automation/trigger/#trigger-id).
| `trigger.idx` | Index of the trigger. (The first trigger idx is `0`.)
@ -33,18 +40,18 @@ Triggers from all platforms will include the following data.
These are the properties available for a [Calendar trigger](/docs/automation/trigger/#calendar-trigger).
| Template variable | Data |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| `trigger.platform` | Hardcoded: `calendar` |
| `trigger.event` | The trigger event type, either `start` or `end` |
| `trigger.calendar_event` | The calendar event object matched. |
| `trigger.calendar_event.summary` | The title or summary of the calendar event. |
| `trigger.calendar_event.start` | String representation of the start date or date time of the calendar event e.g. `2022-04-10`, or `2022-04-10 11:30:00-07:00` |
| `trigger.calendar_event.end` | String representation of the end time of date time the calendar event in UTC e.g. `2022-04-11`, or `2022-04-10 11:45:00-07:00` |
| `trigger.calendar_event.all_day` | Indicates the event spans the entire day. |
| `trigger.calendar_event.description` | A detailed description of the calendar event, if available. |
| `trigger.calendar_event.location` | Location information for the calendar event, if available. |
| `trigger.offset` | Timedelta object with offset to the event, if any |
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `calendar`
| `trigger.event` | The trigger event type, either `start` or `end`.
| `trigger.calendar_event` | The calendar event object matched.
| `trigger.calendar_event.summary` | The title or summary of the calendar event.
| `trigger.calendar_event.start` | String representation of the start date or date time of the calendar event e.g. `2022-04-10`, or `2022-04-10 11:30:00-07:00`
| `trigger.calendar_event.end` | String representation of the end time of date time the calendar event in UTC e.g. `2022-04-11`, or `2022-04-10 11:45:00-07:00`
| `trigger.calendar_event.all_day` | Indicates the event spans the entire day.
| `trigger.calendar_event.description` | A detailed description of the calendar event, if available.
| `trigger.calendar_event.location` | Location information for the calendar event, if available.
| `trigger.offset` | Timedelta object with offset to the event, if any.
### Device
@ -54,18 +61,42 @@ Inherites template variables from [event](#event) or [state](#state) template ba
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `device`.
| `trigger.platform` | Hardcoded: `device`
### Event
These are the properties available for a [Event trigger](/docs/automation/trigger/#event-trigger).
An [Event](/docs/configuration/events/) trigger is fired each time an {% term entity %} state changes or an event matching the configured event_type occurs.
These are the properties available for an [Event trigger](/docs/automation/trigger/#event-trigger).
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `event`.
| `trigger.event` | Event object that matched.
| `trigger.platform` | Hardcoded: `event`
| `trigger.event` | Event object that matched.
| `trigger.event.event_type` | Event type.
| `trigger.event.data` | Optional event data.
| `trigger.event.data` | Optional event data.
### Geolocation
These are the properties available for a [Geolocation trigger](/docs/automation/trigger/#geolocation-trigger).
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `geo_location`
| `trigger.event` | The trigger event type, either `enter` or `leave`.
| `trigger.source` | The Geolocation platform creating the trigger event.
| `trigger.zone` | State object of the zone.
### Home Assistant
The Home Assistant trigger is recommended for automations instead of [homeassistant_start or homeassistant_stop events](/docs/configuration/events/#homeassistant_start-homeassistant_started).
These are the properties available for a [Home Assistant trigger](/docs/automation/trigger/#home-assistant-trigger).
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `homeassistant`
| `trigger.event` | The trigger event type, either `start` or `shutdown`.
### MQTT
@ -73,7 +104,7 @@ These are the properties available for a [MQTT trigger](/docs/automation/trigger
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `mqtt`.
| `trigger.platform` | Hardcoded: `mqtt`
| `trigger.topic` | Topic that received payload.
| `trigger.payload` | Payload.
| `trigger.payload_json` | Dictionary of the JSON parsed payload.
@ -100,9 +131,9 @@ These are the properties available for a [Sentence trigger](/docs/automation/tri
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `conversation`
| `trigger.sentence` | Text of the sentence that was matched
| `trigger.slots` | Object with matched slot values
| `trigger.details` | Object with matched slot details by name, such as [wildcards](/docs/automation/trigger/#sentence-wildcards). Each detail contains: <ul><li>`name` - name of the slot</li><li>`text` - matched text</li><li>`value` - output value (see [lists](https://developers.home-assistant.io/docs/voice/intent-recognition/template-sentence-syntax/#lists))</li></ul>
| `trigger.sentence` | Text of the sentence that was matched.
| `trigger.slots` | Object with matched slot values.
| `trigger.details` | Object with matched slot details by name, such as [wildcards](/docs/automation/trigger/#sentence-wildcards). Each detail contains: <ul><li>`name` - name of the slot</li><li>`text` - matched text</li><li>`value` - output value (see [lists](/docs/voice/intent-recognition/template-sentence-syntax/#lists))</li></ul>.
| `trigger.device_id` | The device ID that captured the command, if any.
### State
@ -127,6 +158,16 @@ These are the properties available for a [Sun trigger](/docs/automation/trigger/
| `trigger.event` | The event that just happened: `sunset` or `sunrise`.
| `trigger.offset` | Timedelta object with offset to the event, if any.
### Tag
These are the properties available for a [Tag trigger](/docs/automation/trigger/#tag-trigger).
| Template variable | Data |
| ---- | ---- |
| `trigger.platform` | Hardcoded: `tag`
| `trigger.tag_id` | The tag ID captured.
| `trigger.device_id` | Optional device ID that captured the tag.
### Template
These are the properties available for a [Template trigger](/docs/automation/trigger/#template-trigger).
@ -166,9 +207,9 @@ These properties are available for a [persistent notification trigger](/docs/aut
| `trigger.platform` | Hardcoded: `persistent_notification`
| `trigger.update_type` | Type of persistent notification update `added`, `removed`, `current`, or `updated`.
| `trigger.notification` | Notification object that triggered the persistent notification trigger.
| `trigger.notification.notification_id` | The notification ID
| `trigger.notification.title` | Title of the notification
| `trigger.notification.message` | Message of the notification
| `trigger.notification.notification_id` | The notification ID.
| `trigger.notification.title` | Title of the notification.
| `trigger.notification.message` | Message of the notification.
| `trigger.notification.created_at` | DateTime object indicating when the notification was created.
### Webhook
@ -193,7 +234,7 @@ These are the properties available for a [Zone trigger](/docs/automation/trigger
| `trigger.entity_id` | Entity ID that we are observing.
| `trigger.from_state` | Previous [state object] of the entity.
| `trigger.to_state` | New [state object] of the entity.
| `trigger.zone` | State object of zone
| `trigger.zone` | State object of the zone.
| `trigger.event` | Event that trigger observed: `enter` or `leave`.
## Examples

2
source/_docs/automation/trigger.markdown
View File

@ -985,7 +985,7 @@ additional event data available for use by an automation.
## Sentence trigger
A sentence trigger fires when [Assist](/voice_control/) matches a sentence from a voice assistant using the default [conversation agent](/integrations/conversation/). Sentence triggers only work with Home Assistant Assist. External conversation agents such as OpenAI or Google Generative AI cannot be used to trigger automations.
A sentence trigger fires when [Assist](/voice_control/) matches a sentence from a voice assistant using the default [conversation agent](/integrations/conversation/). Sentence triggers work with Home Assistant Assist. They will not work with external conversation agents such as OpenAI or Google Generative AI unless "Prefer handling commands locally" is enabled in the conversation agent settings.
Sentences are allowed to use some basic [template syntax](https://developers.home-assistant.io/docs/voice/intent-recognition/template-sentence-syntax/#sentence-templates-syntax) like optional and alternative words. For example, `[it's ]party time` will match both "party time" and "it's party time".

22
source/_docs/configuration/customizing-devices.markdown
View File

@ -9,23 +9,35 @@ related:
- docs: /docs/organizing/labels/
---
## Customizing an entity
After adding a new device, you might find the automatically assigned entity ID too technical and the entity lacking a friendly name. You can personalize these elements to better fit your naming conventions or modify other attributes like the icon.
To change entity attributes, follow these steps:
1. Go to {% my entities title="**Settings** > **Devices & services** > **Entities**" %} and select the entity from the list.
2. In the top right corner, select the cog icon.
2. In the top-right corner, select the {% icon "mdi:cog" %} cog icon.
![Entity dialog box with cog icon.](/images/docs/configuration/customizing-entity-dialog.png)
3. Enter or edit the attributes:
- For example, the entity ID here could be shortened to `binary_sensor.living_room_motion_1`.
- Do not change the domain of the entity - the part before the `.` (binary_sensor, in this example).
- For example, the entity ID here could be shortened to `binary_sensor.lumi_sensor_aq2_opening`.
- You can use lowercase letters, numbers, and underscores.
- The ID must not start or end with an underscore.
- To undo the change and revert the ID to the default, select the {% icon "mdi:restore" %} icon.
- **Note**: You can only reset the ID to the default ID for entities with a unique ID.
- IDs of entities that are disabled or for which the integration is not set up cannot be reverted.
- To revert all the entity IDs for a device, on the device page, select the three dots {% icon "mdi:dots-vertical" %} menu, then select **Recreate entity IDs**.
- **Result**: This resets the entity ID and applies the current default naming convention.
- The terms used to generate the entity ID depends on a few factors. Prioritization is as follows:
1. If you changed the friendly name of the entity, the friendly name will be used.
2. The entity ID suggested by the integration (just a few integrations do this).
3. The default name in the user language, if using Latin script.
- If the something other than Latin script is used, the entity ID is based on the English default name.
- This is because entity IDs must use lowercase alphanumeric characters in the range of [a-z,1-9].
![revert all entity IDs for a device from the device page](/images/docs/configuration/device-page-revert-entity-id.png)
- Enter or edit the friendly name.
- In this example, this would change "Opening".
- If needed, from the **Shown as** menu, you can select a different [device class](/integrations/homeassistant/#device-class).
- If you like, add a [label](/docs/organizing/labels/).

2
source/_docs/energy/water.markdown
View File

@ -42,7 +42,7 @@ There are also products for water usage monitoring that are based on existing co
If your water meter lacks a rotary disk, magnetic disk, or coil. There are alternative solutions available to seamlessly integrate water monitoring into your smart home setup:
- [AI-on-the-edge-device](https://github.com/jomjol/AI-on-the-edge-device) is a project running on an ESP32-CAM and can be fully integrated into Home Assistant using the Home Assistant Discovery Functionality of MQTT. It digitalizes your gas/water/electricity meter display and provides its data in various ways.![Photo of the AI-on-the-edge-device Workflow](/images/docs/energy/
- [AI-on-the-edge-device](https://github.com/jomjol/AI-on-the-edge-device) is a project running on an ESP32-CAM and can be fully integrated into Home Assistant using the Home Assistant Discovery Functionality of MQTT. It digitalizes your gas/water/electricity meter display and provides its data in various ways.![Photo of the AI-on-the-edge-device Workflow](/images/docs/energy/ai-on-the-edge-device.jpg)
If you have a Culligan Water Softener, you may be able to interface with the inbuilt `DEBUG PORT` and receive water usage stats including `Gallons` (gal), `Gallons Per Minute` (gal/min), and `Gallons to Recharge` (gal):

2
source/_includes/installation/operating_system.md
View File

@ -102,7 +102,7 @@ To write the HAOS image to the boot medium on your x86-64 hardware, there are 2
- Computer
- The target x86-64 hardware, on which you want to install the {% term "Home Assistant Operating System" %} (HAOS)
- USB flash drive (USB thumb drive is sufficient, it should be at least 4&nbsp;GB in size)
- USB flash drive (USB thumb drive is sufficient, it should be at least 8&nbsp;GB in size)
- Internet connection
#### To install HAOS via Ubuntu from a USB flash drive

2
source/_includes/integrations/wwha.md
View File

@ -17,7 +17,7 @@
{% endif %}
{% endfor %}
**[{{ name }}]({{ url }})** is a member of the Works with Home Assistant partner program for their {{ formatted_types }} products. {{ name }} is committed to making sure their products are up-to-date and ready to use in Home Assistant.
{% if url and url != "" %}[{{ name }}]({{ url }}){% else %}{{ name }}{% endif %} is a member of the Works with Home Assistant partner program for their {{ formatted_types }} products. {{ name }} is committed to making sure their products are up-to-date and ready to use in Home Assistant.
{% if page.works_with contains "zwave" %}
{{ name }} Z-Wave devices work locally and integrate seamlessly with the Z-Wave integration in Home Assistant (Z-Wave stick required). As all connectivity is happening locally, status updates and controlling your devices happen instantly in Home Assistant.

4
source/_integrations/alexa_devices.markdown
View File

@ -81,7 +81,7 @@ automation:
data:
message: Welcome home Simone
target:
entity_id: notify.announce_echo_dot_livingroom
entity_id: notify.echo_dot_livingroom_announce
```
### Automation: Start Radio on all Echo dots
@ -104,7 +104,7 @@ automation:
data:
message: Play B.B.C. on Tunein
target:
entity_id: notify.custom_everywhere
entity_id: notify.everywhere_announce
```
## Data updates

4
source/_integrations/axis.markdown
View File

@ -53,6 +53,10 @@ If you are having issues and want to report a problem, always start with making
If your device is not discovered. On your camera, go to **System Options** -> **Advanced** -> **Plain Configuration**. Change the drop-down box to `network` and click `Select Group`. If `Network Interface I0 ZeroConf` contains the `169.x.x.x` IP address, unchecked the box next to `Enabled` for this section and click `Save`.
### Internet access required for full integration
If the Axis device does not have internet access, Home Assistant may only display the camera stream. Other entities such as sensors and output controls might not appear. To ensure all device features are available, make sure the camera has internet access during initial setup.
### Reporting a problem
When creating an issue detailing a problem related to the integration make sure to share the device model and firmware as well as prepare logs. Logs might contain sensitive information so make sure to look through it before sharing.

6
source/_integrations/device_tracker.markdown
View File

@ -17,10 +17,10 @@ The device tracker allows you to track devices in Home Assistant. This can happe
## Configuring a `device_tracker` platform
To get started add the following lines to your {% term "`configuration.yaml`" %} (example for Netgear):
To get started add the following lines to your {% term "`configuration.yaml`" %} (example for NETGEAR):
```yaml
# Example configuration.yaml entry for Netgear device
# Example configuration.yaml entry for NETGEAR device
device_tracker:
- platform: netgear
host: IP_ADDRESS
@ -50,7 +50,7 @@ Note that setting `track_new_devices: false` will still result in new devices be
In the {% term "`configuration.yaml`" %}, the extended example from above would look like the following sample:
```yaml
# Example configuration.yaml entry for Netgear device
# Example configuration.yaml entry for NETGEAR device
device_tracker:
- platform: netgear
host: IP_ADDRESS

4
source/_integrations/doorbird.markdown
View File

@ -32,7 +32,7 @@ There is currently support for the following device types within Home Assistant:
## Setup
It is recommended to set up a new & dedicated account on your DoorBird App/web portal for use with Home Assistant. The instructions in this document refer specifically to the DoorBird IOS/Android app. Still, most actions can also be performed using the web-based [DoorBird - WebAdmin](https://webadmin.doorbird.com) portal and logging in on your DoorBird admin account.
It is recommended to set up a new & dedicated account on your DoorBird App/web portal for use with Home Assistant. The instructions in this document refer specifically to the DoorBird iOS/Android app. Still, most actions can also be performed using the web-based [DoorBird - WebAdmin](https://webadmin.doorbird.com) portal and logging in on your DoorBird admin account.
To setup a new account for Home Assistant, open the DoorBird App by selecting **Settings** (cog icon) > **Administration** > **LOGIN** (using your DoorBird App Administration details). Under the **USER** section, choose **Add**. This new user account requires specific permissions enabled (depending on what functionality you want). Permissions can be found under **Permissions**. The following permissions are recommended (or amend depending on your requirements:
@ -84,7 +84,7 @@ The URLs on the event will be based on the configuration used to connect to your
Once events have been registered on the DoorBird device, they must be attached to a schedule using the official DoorBird app on Android or iOS or the [DoorBird - WebAdmin](https://webadmin.doorbird.com) portal. Currently, there are schedules available for doorbell, motion, relay, and RFID events (on supported DoorBird devices). Essentially, you can enable an HTTP(S) call from your DoorBird device to the Home Assistant DoorBird API by configuring an action/event (by enabling a schedule).
The schedules can be found by navigating to the following area of the DoorBird app (Android or IOS):
The schedules can be found by navigating to the following area of the DoorBird app (Android or iOS):
**Settings** (cog icon) > **Administration** > **LOGIN** (using your App Administration details) > (under **EXPERT SETTINGS**) Schedule for doorbell.

2
source/_integrations/file.markdown
View File

@ -31,7 +31,7 @@ After creating a config entry, you can change the entry name, the name of the no
To use notifications in automations or scripts, see the [getting started with automation page](/getting-started/automation/).
Use the `notify.send_message` entity to store notification messages.
Use the `notify.send_message` action to store notification messages.
## Sensor

1
source/_integrations/harmony.markdown
View File

@ -99,6 +99,7 @@ Send a single command or a set of commands to one device, device ID and availabl
| `command` | no | A single command or a list of commands to send. |
| `num_repeats` | yes | The number of times to repeat the command(s). |
| `delay_secs` | yes | The number of seconds between sending each command. |
| `hold_secs` | yes | The number of seconds the button on the remote is held before the release is sent. |
In the file 'harmony_REMOTENAME.conf' you can find the available devices and commands, for example:

10
source/_integrations/heltun.markdown
View File

@ -21,16 +21,10 @@ ha_iot_standard: zwave
ha_brand: true
---
[HELTUN](https://www.heltun.com/) is a member of the Works with Home Assistant partner program for their Z-Wave products. HELTUN is committed to making sure their products are up-to-date and ready to use in Home Assistant.
[HELTUN](https://www.heltun.com/) thermostats make it easy to automate your heating system, their touch panel switches control your lighting and motorized appliances and their high load switches control any high load appliances like groups of lights, heaters, or individual sockets.
HELTUN thermostats make it easy to automate your heating system, their touch panel switches control your lighting and motorized appliances and their high load switches control any high load appliances like groups of lights, heaters, or individual sockets.
HELTUN Z-Wave devices work locally and integrate seamlessly with the Z-Wave integration in Home Assistant (Z-Wave stick required). As all connectivity is happening locally, status updates and controlling your devices happen instantly in Home Assistant.
{% include integrations/wwha.md %}
### Firmware updates
HELTUN periodically releases new firmware with additional features and functionality which can be sent to devices via an encrypted OTA (Over-The-Air) update process. In Home Assistant, you can navigate to your device page and use the Update Device Firmware option to upload the firmware from HELTUN for your device.
{% my add_zwave_device badge domain=page.ha_domain %}
[Learn more about Z-Wave in Home Assistant.](/integrations/zwave_js/)

4
source/_integrations/here_travel_time.markdown
View File

@ -20,9 +20,9 @@ The `here_travel_time` sensor provides travel time from the [HERE Routing API](h
You need to register for an API key by following the instructions in the [API Developer Guide](https://www.here.com/docs/bundle/routing-api-developer-guide-v8/page/topics/send-request.html).
HERE offers a Limited Plan which includes 1000 free transactions per day. If you are not [updating sensors on demand](#updating-sensors-on-demand-using-automation), you can track 3 routes without exceeding the limit.
HERE offers a Base Plan which includes 5000 free transactions per month. If you are not [updating sensors on demand](#updating-sensors-on-demand-using-automation), you can track 1 route without exceeding the limit.
You can provide payment details if you want to pay for unlimited transactions. Be aware that the amount of transactions included for free in the paid plan might be _less_ than the 1000 transactions per day in the free plan. More information can be found [on the pricing page](https://www.here.com/get-started/pricing)
More information can be found [on the pricing page](https://www.here.com/get-started/pricing)
{% include integrations/config_flow.md %}

13
source/_integrations/homee.markdown
View File

@ -2,7 +2,20 @@
title: Homee
description: Instructions on how to setup Homee devices in Home Assistant.
ha_category:
- Alarm
- Binary sensor
- Button
- Climate
- Cover
- Event
- Fan
- Light
- Lock
- Number
- Select
- Sensor
- Switch
- Valve
ha_config_flow: true
ha_release: 2025.2
ha_iot_class: Local Push

2
source/_integrations/itach.markdown
View File

@ -90,7 +90,7 @@ An example to call the integration from developer tools using the `remote.send_c
Note: Global Cache devices expect data in their own format of "sendir...". This integration converts hex code to Global Cache IR form.
API Docs:
API Documentation:
- [iTach](https://www.globalcache.com/files/docs/API-iTach.pdf)
- [GC-100](https://www.globalcache.com/files/docs/API-GC-100.pdf)

24
source/_integrations/kodi.markdown
View File

@ -71,22 +71,22 @@ automation:
Add music to the default playlist (i.e., playlistid=0).
| Data attribute | Optional | Description |
| ---------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `entity_id` | no | Name(s) of the Kodi entities where to add the media. |
| `media_type` | yes | Media type identifier. It must be one of SONG or ALBUM. |
| `media_id` | no | Unique Id of the media entry to add (`songid` or `albumid`). If not defined, `media_name` and `artist_name` are needed to search the Kodi music library. |
| `media_name` | no | Optional media name for filtering media. Can be 'ALL' when `media_type` is 'ALBUM' and `artist_name` is specified, to add all songs from one artist. |
| `artist_name` | no | Optional artist name for filtering media. |
| -------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `entity_id` | no | Name(s) of the Kodi entities where to add the media. |
| `media_type` | yes | Media type identifier. It must be one of SONG or ALBUM. |
| `media_id` | no | Unique Id of the media entry to add (`songid` or `albumid`). If not defined, `media_name` and `artist_name` are needed to search the Kodi music library. |
| `media_name` | no | Optional media name for filtering media. Can be 'ALL' when `media_type` is 'ALBUM' and `artist_name` is specified, to add all songs from one artist. |
| `artist_name` | no | Optional artist name for filtering media. |
#### Action `kodi.call_method`
Call a [Kodi JSON-RPC API](https://kodi.wiki/?title=JSON-RPC_API) method with optional parameters. Results of the Kodi API call will be redirected in a Home Assistant event: `kodi_call_method_result`.
| Data attribute | Optional | Description |
| ---------------------- | -------- | --------------------------------------------------------- |
| `entity_id` | no | Name(s) of the Kodi entities where to run the API method. |
| `method` | yes | Name of the Kodi JSON-RPC API method to be called. |
| any other parameter | no | Optional parameters for the Kodi API call. |
| Data attribute | Optional | Description |
| ------------------- | -------- | --------------------------------------------------------- |
| `entity_id` | no | Name(s) of the Kodi entities where to run the API method. |
| `method` | yes | Name of the Kodi JSON-RPC API method to be called. |
| any other parameter | no | Optional parameters for the Kodi API call. |
### Event triggering
@ -392,7 +392,7 @@ key presses of keyboards/remotes can be overwritten in Kodi and configured to se
A keypress can be overwritten in Kodi by using the [Kodi keymap XML](https://kodi.wiki/view/Keymap) or from within the Kodi GUI using the [Keymap Editor add-on](https://kodi.wiki/view/Add-on:Keymap_Editor).
An example of the Kodi keymap configuration using XML, which will overwrite the volume_up/volume_down buttons and instead send an event to HomeAssistant:
An example of the Kodi keymap configuration using XML, which will overwrite the volume_up/volume_down buttons and instead send an event to Home Assistant:
```xml
<keymap>

6
source/_integrations/onkyo.markdown
View File

@ -107,6 +107,12 @@ script:
Network receivers from Onkyo and Integra are supported starting with models from the year 2011. Pioneer network receivers are supported starting with models from 2016.
## Troubleshooting
### No entities created
Restart your receiver (power cycle).
## Removing the integration
This integration follows standard integration removal. No extra steps are required.

4
source/_integrations/recorder.markdown
View File

@ -257,6 +257,10 @@ Perform the action `recorder.enable` to start again saving events and states to
Perform the action `recorder.get_statistics` to retrieve statistics for one or more entities from the recorder database. This action is useful for automations or scripts that need to access historical statistics, such as mean, min, max, or sum values, for supported entities like sensors.
{% note %}
Statistics are only available for entities that store [Long-term Statistics](https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics). More details can be found in the [2021.8.0 release notes](/blog/2021/08/04/release-20218/#long-term-statistics).
{% endnote %}
| Data attribute | Optional | Description |
| -------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `statistic_ids`| no | The entity IDs or statistic IDs to get statistics for. |

38
source/_integrations/snmp.markdown
View File

@ -38,24 +38,24 @@ This device tracker needs SNMP to be enabled on the router. It could be that you
The following OID examples pull the current MAC Address table from a router. This reflects all recent devices seen on the network. However, since devices are not removed until they time out, this is less effective for [device tracker integration page](/integrations/device_tracker/) than desirable. It is recommended to use [Ping](/integrations/ping) or [Nmap](/integrations/nmap_tracker) instead.
| Brand | Device/Firmware | OID |
| --- | --- | --- |
| Aerohive | AP230 | `1.3.6.1.4.1.26928.1.1.1.2.1.2.1.1` |
| Apple | Airport Express (2nd gen.) 7.6.9 | `1.3.6.1.2.1.3.1.1.2` or `1.3.6.1.2.1.4.22.1.2`|
| Aruba | IAP325 on AOS 6.5.4.8 | `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.1` |
| BiPAC | 7800DXL Firmware 2.32e | `1.3.6.1.2.1.17.7.1.2.2.1.1` |
| DD-WRT | unknown version/model | `1.3.6.1.2.1.4.22.1.2` |
| IPFire | 2.25 | `1.3.6.1.2.1.4.22.1.2` |
| MikroTik | unknown RouterOS version/model | `1.3.6.1.4.1.14988.1.1.1.2.1.1` |
| MikroTik | RouterOS 6.x on RB2011 | `1.3.6.1.2.1.4.22.1.2` |
| OpenWrt | Chaos Calmer 15.05 | `1.3.6.1.2.1.4.22.1.2` |
| OPNSense | 19.1 | `1.3.6.1.2.1.4.22.1.2` |
| pfSense | 2.2.4 | `1.3.6.1.2.1.4.22.1.2` |
| Ruckus | ZoneDirector 9.13.3 | `1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6` |
| TP-Link | Archer VR1600v | `1.3.6.1.2.1.3.1.1.2.16.1` |
| TP-Link | Archer VR2600v | `1.3.6.1.2.1.3.1.1.2.19.1` |
| TP-Link | Archer VR600 | `1.3.6.1.2.1.3.1.1.2` |
| Ubiquiti | Edgerouter Lite v1.9.0 | `1.3.6.1.2.1.4.22.1.2` |
| Brand | Device/Firmware | OID |
| -------- | -------------------------------- | ----------------------------------------------- |
| Aerohive | AP230 | `1.3.6.1.4.1.26928.1.1.1.2.1.2.1.1` |
| Apple | Airport Express (2nd gen.) 7.6.9 | `1.3.6.1.2.1.3.1.1.2` or `1.3.6.1.2.1.4.22.1.2` |
| Aruba | IAP325 on AOS 6.5.4.8 | `1.3.6.1.4.1.14823.2.3.3.1.2.4.1.1` |
| BiPAC | 7800DXL Firmware 2.32e | `1.3.6.1.2.1.17.7.1.2.2.1.1` |
| DD-WRT | unknown version/model | `1.3.6.1.2.1.4.22.1.2` |
| IPFire | 2.25 | `1.3.6.1.2.1.4.22.1.2` |
| MikroTik | unknown RouterOS version/model | `1.3.6.1.4.1.14988.1.1.1.2.1.1` |
| MikroTik | RouterOS 6.x on RB2011 | `1.3.6.1.2.1.4.22.1.2` |
| OpenWrt | Chaos Calmer 15.05 | `1.3.6.1.2.1.4.22.1.2` |
| OPNSense | 19.1 | `1.3.6.1.2.1.4.22.1.2` |
| pfSense | 2.2.4 | `1.3.6.1.2.1.4.22.1.2` |
| Ruckus | ZoneDirector 9.13.3 | `1.3.6.1.4.1.25053.1.2.2.1.1.3.1.1.1.6` |
| TP-Link | Archer VR1600v | `1.3.6.1.2.1.3.1.1.2.16.1` |
| TP-Link | Archer VR2600v | `1.3.6.1.2.1.3.1.1.2.19.1` |
| TP-Link | Archer VR600 | `1.3.6.1.2.1.3.1.1.2` |
| Ubiquiti | Edgerouter Lite v1.9.0 | `1.3.6.1.2.1.4.22.1.2` |
To use the SNMP version 1 or 2c platform in your installation, add the following to your `configuration.yaml` file:
@ -434,7 +434,7 @@ switch:
payload_off: 0
- platform: snmp
name: Enable PoE on Netgear switch port 2 using SNMP v3
name: Enable PoE on NETGEAR switch port 2 using SNMP v3
host: 192.168.0.4
version: "3"
username: "myusername"

2
source/_integrations/template.markdown
View File

@ -178,7 +178,7 @@ Each entity platform has its own set of configuration options, but there are som
```yaml
# Example configuration.yaml entry
template:
binary_sensor:
- binary_sensor:
# Common configuration options
- unique_id: my_unique_sensor_id
availability: "{{ 'sensor.watts' | has_value }}"

2
source/_integrations/torque.markdown
View File

@ -31,7 +31,7 @@ Under the **Realtime Web Upload** header:
- Check **Upload to web-server**.
- Enter `https://HOST/api/torque` or `https://@/HOST:PORT/api/torque` as the **Web-server URL**, where `HOST` and `PORT` are your externally accessible Home Assistant HTTP host. To use a Bearer Token, this has to be [SSL/TLS](/docs/ecosystem/certificates/).
- Enable **Send https: Bearer Token** (available since Torque Pro 1.12.46)
- Enable **Send HTTPS: Bearer Token** (available since Torque Pro 1.12.46)
- Paste a Long-Lived Access Token from any Home Assistant user in **Set Bearer Token** field.
- Enter an email address in **User Email Address** (this can be any non empty string you like).
- Optionally set the **Web Logging Interval**. The 2-second default may quickly fill up the Home Assistant history database.

19
source/_integrations/xiaomi_miio.markdown
View File

@ -136,7 +136,7 @@ Not yet implemented features (but possible):
### Supported subdevices
These subdevices are fully implemented in HomeAssistant:
These subdevices are fully implemented in Home Assistant:
- **Weather sensor (WSDCGQ01LM)**
- Zigbee ID: `lumi.sensor_ht`
@ -1218,11 +1218,6 @@ Set the humidifier operation mode.
| `entity_id` | no | Only act on a specific Xiaomi humidifier entity. |
| `mode` | no | The humidifier operation mode |
### Action `fan.set_percentage`
Set the fan speed percentage.
| Data attribute | Optional | Description |
| ---------------------- | -------- | ---------------------------------------------- |
| `entity_id` | no | Only act on a specific Xiaomi fan entity. |
| `percentage` | no | Fan speed. Percentage speed setting |
@ -1654,16 +1649,16 @@ Note: If your vacuum is in motion and does not respond to the `xiaomi_miio.vacuu
Start the remote control mode of the robot. You can then move it with `remote_control_move`; when done, call `remote_control_stop`.
| Data attribute | Optional | Description |
| ---------------------- | -------- | ---------------------------- |
| `entity_id` | no | Only act on a specific robot |
| -------------- | -------- | ---------------------------- |
| `entity_id` | no | Only act on a specific robot |
### Action `xiaomi_miio.vacuum_remote_control_stop`
Exit the remote control mode of the robot.
| Data attribute | Optional | Description |
| ---------------------- | -------- | ---------------------------- |
| `entity_id` | no | Only act on a specific robot |
| -------------- | -------- | ---------------------------- |
| `entity_id` | no | Only act on a specific robot |
### Action `xiaomi_miio.vacuuNm_remote_control_move`
@ -2048,10 +2043,6 @@ Turn the wifi LED off.
| ---------------------- | -------- | ------------------------------------------------- |
| `entity_id` | no | Only act on a specific Xiaomi switch entity. |
### Action `xiaomi_miio.switch_set_power_price` (Power Strip)
Set the power price.
| Data attribute | Optional | Description |
| ---------------------- | -------- | ------------------------------------------------- |
| `entity_id` | no | Only act on a specific Xiaomi switch entity. |

159
source/_posts/2025-06-11-release-20256.markdown
View File

@ -48,6 +48,8 @@ _PS: We will pick up the regular release schedule again now, so expect the next
- [Reset/restore entity IDs](#resetrestore-entity-ids)
- [Patch releases](#patch-releases)
- [2025.6.1 - June 13](#202561---june-13)
- [2025.6.2 - June 23](#202562---june-23)
- [2025.6.3 - June 24](#202563---june-24)
- [Need help? Join the community!](#need-help-join-the-community)
- [Backward-incompatible changes](#backward-incompatible-changes)
- [All changes](#all-changes)
@ -388,6 +390,163 @@ release every Friday.
[@tronikos]: https://github.com/tronikos
[@tsvi]: https://github.com/tsvi
### 2025.6.2 - June 23
- Remove address info from Rachio calendar events ([@brg468] - [#145896])
- Bump uiprotect to 7.12.0 ([@RaHehl] - [#146337])
- Bump uiprotect to 7.13.0 ([@RaHehl] - [#146410])
- Bump reolink-aio to 0.14.0 ([@starkillerOG] - [#146566])
- Bump pypck to 0.8.7 ([@alengwenus] - [#146657])
- Update rokuecp to 0.19.5 ([@ctalkington] - [#146788])
- Use Shelly main device area as suggested area for sub-devices ([@bieniu] - [#146810])
- Fix blocking open in Minecraft Server ([@elmurato] - [#146820])
- Bump aioamazondevices to 3.1.3 ([@chemelli74] - [#146828])
- Bump aiohttp to 3.12.13 ([@bdraco] - [#146830])
- Bump motion blinds to 0.6.28 ([@starkillerOG] - [#146831])
- Bump pypck to 0.8.8 ([@alengwenus] - [#146841])
- Fix missing key for ecosmart in older Wallbox models ([@hesselonline] - [#146847])
- Bump bthome-ble to 3.13.1 ([@Ernst79] - [#146871])
- Bump reolink-aio to 0.14.1 ([@starkillerOG] - [#146903])
- Add debug log for update in onedrive ([@zweckj] - [#146907])
- Switchbot Cloud: Fix device type filtering in sensor ([@SeraphicRav] - [#146945])
- Bump pySmartThings to 3.2.5 ([@joostlek] - [#146983])
- Bump ical to 10.0.4 ([@allenporter] - [#147005])
- Fix incorrect use of zip in service.async_get_all_descriptions ([@emontnemery] - [#147013])
- Disable Z-Wave indidator CC entities by default ([@MartinHjelmare] - [#147018])
- Fix Shelly entity names for gen1 sleeping devices ([@bieniu] - [#147019])
- Disable Z-Wave idle notification button ([@MartinHjelmare] - [#147026])
- Fix log in onedrive ([@zweckj] - [#147029])
- Bump holidays lib to 0.75 ([@gjohansson-ST] - [#147043])
- Bump aiohomeconnect to 0.18.0 ([@Diegorro98] - [#147044])
- Bump ZHA to 0.0.60 ([@puddly] - [#147045])
- Bump pylamarzocco to 2.0.9 ([@zweckj] - [#147046])
- Handle missing widget in lamarzocco ([@zweckj] - [#147047])
- Bump aioamazondevices to 3.1.4 ([@chemelli74] - [#146883])
- Bump aioamazondevices to 3.1.12 ([@chemelli74] - [#147055])
- Bump uiprotect to version 7.14.0 ([@RaHehl] - [#147102])
- Improve advanced Z-Wave battery discovery ([@MartinHjelmare] - [#147127])
- Fix Charge Cable binary sensor in Teslemetry ([@Bre77] - [#147136])
- [ci] Bump cache key version ([@cdce8p] - [#147148])
- Bump homematicip to 2.0.6 ([@hahn-th] - [#147151])
- Wallbox fix too many requests by API ([@hesselonline] - [#147197])
- Bump deebot-client to 13.4.0 ([@edenhaus] - [#147221])
- Handle the new JSON payload from traccar clients ([@ludeeus] - [#147254])
- Bump aioamazondevices to 3.1.14 ([@chemelli74] - [#147257])
- Bump uiprotect to version 7.14.1 ([@RaHehl] - [#147280])
- Bump aioesphomeapi to 32.2.4 ([@synesthesiam] - [#147100])
- Bump aioesphomeapi to 33.0.0 ([@bdraco] - [#147296])
- Fix reload for Shelly devices with no script support ([@chemelli74] - [#147344])
- Add Matter protocol to Switchbot ([@joostlek] - [#147356])
[#145650]: https://github.com/home-assistant/core/pull/145650
[#145896]: https://github.com/home-assistant/core/pull/145896
[#146337]: https://github.com/home-assistant/core/pull/146337
[#146410]: https://github.com/home-assistant/core/pull/146410
[#146566]: https://github.com/home-assistant/core/pull/146566
[#146657]: https://github.com/home-assistant/core/pull/146657
[#146764]: https://github.com/home-assistant/core/pull/146764
[#146788]: https://github.com/home-assistant/core/pull/146788
[#146810]: https://github.com/home-assistant/core/pull/146810
[#146820]: https://github.com/home-assistant/core/pull/146820
[#146828]: https://github.com/home-assistant/core/pull/146828
[#146830]: https://github.com/home-assistant/core/pull/146830
[#146831]: https://github.com/home-assistant/core/pull/146831
[#146841]: https://github.com/home-assistant/core/pull/146841
[#146847]: https://github.com/home-assistant/core/pull/146847
[#146871]: https://github.com/home-assistant/core/pull/146871
[#146883]: https://github.com/home-assistant/core/pull/146883
[#146903]: https://github.com/home-assistant/core/pull/146903
[#146907]: https://github.com/home-assistant/core/pull/146907
[#146945]: https://github.com/home-assistant/core/pull/146945
[#146983]: https://github.com/home-assistant/core/pull/146983
[#147005]: https://github.com/home-assistant/core/pull/147005
[#147013]: https://github.com/home-assistant/core/pull/147013
[#147018]: https://github.com/home-assistant/core/pull/147018
[#147019]: https://github.com/home-assistant/core/pull/147019
[#147026]: https://github.com/home-assistant/core/pull/147026
[#147029]: https://github.com/home-assistant/core/pull/147029
[#147043]: https://github.com/home-assistant/core/pull/147043
[#147044]: https://github.com/home-assistant/core/pull/147044
[#147045]: https://github.com/home-assistant/core/pull/147045
[#147046]: https://github.com/home-assistant/core/pull/147046
[#147047]: https://github.com/home-assistant/core/pull/147047
[#147055]: https://github.com/home-assistant/core/pull/147055
[#147100]: https://github.com/home-assistant/core/pull/147100
[#147102]: https://github.com/home-assistant/core/pull/147102
[#147127]: https://github.com/home-assistant/core/pull/147127
[#147136]: https://github.com/home-assistant/core/pull/147136
[#147148]: https://github.com/home-assistant/core/pull/147148
[#147151]: https://github.com/home-assistant/core/pull/147151
[#147197]: https://github.com/home-assistant/core/pull/147197
[#147221]: https://github.com/home-assistant/core/pull/147221
[#147254]: https://github.com/home-assistant/core/pull/147254
[#147257]: https://github.com/home-assistant/core/pull/147257
[#147280]: https://github.com/home-assistant/core/pull/147280
[#147296]: https://github.com/home-assistant/core/pull/147296
[#147344]: https://github.com/home-assistant/core/pull/147344
[#147356]: https://github.com/home-assistant/core/pull/147356
[@Bre77]: https://github.com/Bre77
[@Diegorro98]: https://github.com/Diegorro98
[@Ernst79]: https://github.com/Ernst79
[@MartinHjelmare]: https://github.com/MartinHjelmare
[@RaHehl]: https://github.com/RaHehl
[@SeraphicRav]: https://github.com/SeraphicRav
[@alengwenus]: https://github.com/alengwenus
[@allenporter]: https://github.com/allenporter
[@bdraco]: https://github.com/bdraco
[@bieniu]: https://github.com/bieniu
[@brg468]: https://github.com/brg468
[@cdce8p]: https://github.com/cdce8p
[@chemelli74]: https://github.com/chemelli74
[@ctalkington]: https://github.com/ctalkington
[@edenhaus]: https://github.com/edenhaus
[@elmurato]: https://github.com/elmurato
[@emontnemery]: https://github.com/emontnemery
[@frenck]: https://github.com/frenck
[@gjohansson-ST]: https://github.com/gjohansson-ST
[@hahn-th]: https://github.com/hahn-th
[@hesselonline]: https://github.com/hesselonline
[@joostlek]: https://github.com/joostlek
[@ludeeus]: https://github.com/ludeeus
[@puddly]: https://github.com/puddly
[@starkillerOG]: https://github.com/starkillerOG
[@synesthesiam]: https://github.com/synesthesiam
[@zweckj]: https://github.com/zweckj
[alexa_devices docs]: /integrations/alexa_devices/
[bthome docs]: /integrations/bthome/
[ecovacs docs]: /integrations/ecovacs/
[esphome docs]: /integrations/esphome/
[holiday docs]: /integrations/holiday/
[home_connect docs]: /integrations/home_connect/
[homematicip_cloud docs]: /integrations/homematicip_cloud/
[lamarzocco docs]: /integrations/lamarzocco/
[lcn docs]: /integrations/lcn/
[local_calendar docs]: /integrations/local_calendar/
[local_todo docs]: /integrations/local_todo/
[minecraft_server docs]: /integrations/minecraft_server/
[motion_blinds docs]: /integrations/motion_blinds/
[onedrive docs]: /integrations/onedrive/
[rachio docs]: /integrations/rachio/
[remote_calendar docs]: /integrations/remote_calendar/
[reolink docs]: /integrations/reolink/
[roku docs]: /integrations/roku/
[shelly docs]: /integrations/shelly/
[smartthings docs]: /integrations/smartthings/
[switchbot_cloud docs]: /integrations/switchbot_cloud/
[teslemetry docs]: /integrations/teslemetry/
[traccar docs]: /integrations/traccar/
[unifiprotect docs]: /integrations/unifiprotect/
[wallbox docs]: /integrations/wallbox/
[workday docs]: /integrations/workday/
[zha docs]: /integrations/zha/
[zwave_js docs]: /integrations/zwave_js
### 2025.6.3 - June 24
- Update frontend to 20250531.4 ([@bramkragten] - [#147414])
[#147414]: https://github.com/home-assistant/core/pull/147414
[@bramkragten]: https://github.com/bramkragten
## Need help? Join the community!

53
source/_posts/2025-06-24-community-day-2025-wrap-up.markdown Normal file
View File

@ -0,0 +1,53 @@
---
layout: post
title: "Community Day 2025 Wrap-up"
description: "We highlight the best moments, what we learned, and how we will keep supporting meetups worldwide."
date: 2025-06-24 00:00:01
date_formatted: "June 24, 2025"
author: Missy Quarry
comments: true
categories: Announcements
og_image: /images/blog/2025-06-community-day-wrap-up/art.jpg
---
<img src='/images/blog/2025-06-community-day-wrap-up/art.jpg' style='border: 0;box-shadow: none;' alt="Pictures of multiple community day meetups">
Our first Home Assistant Community Day was a humbling success --- we knew that the community had a desire to have something coordinated like this, but we really did not expect just how widely this would spread. 💖
So much happened in such a short window of time, so let's talk about how this year's event went and what the future looks like for Home Assistant meetups.<!--more-->
## It started with a question...
Home Assistant Community Day was born from a conversation last year where we asked, "Would the community even *want* this?" We dropped hints here and there to test how y'all would react to a worldwide event, and after weeks of planning, the response to the event announcement was overwhelmingly positive. 🤩
First, **THANK YOU** 🙏🏻 to all **the hosts** for their local coordination, **community members** who showed up, and **the venues** that made all this possible. I learned so much with your help, and it will make next year's Community Day one to remember.
## ...that turned into a movement...
When I announced Home Assistant Community Day, I didn't give hosts a lot to work with. I didn't want the community to think they had to fit into a specific format, and wanted it to be unique to their region. It became clear pretty quickly what information was missing and what people wanted guidance on. For example, some asked for suggestions on what types of venues to book or which activities could make the event more interactive, such as quizzes or presentations. Your questions helped us make it easier for hosts to build cool events, thank you for those!  
All around the world, everyone came together to talk about Home Assistant (and its related projects). You swapped hardware, you showed off your automations or dashboards, you participated in quizzes, and you formed new bonds with people in your area who share your passion for Home Assistant. Some people had custom swag printed, others received hardware from a couple of our [Works With Home Assistant](https://works-with.home-assistant.io/) partners, and one group had a Hackathon event the day before! So many great photos were shared from the events that we can't possibly include them all here! You can find plenty more by searching #HADay2025 on social media or by checking the [Discord meetup thread](https://discord.com/channels/330944238910963714/1364989531069091920/1375786903324070042) for this event. It was seriously one of the most uplifting things I've had the pleasure to not only facilitate, but also witness. 🥰
## ...but not without complications
Swag was an unexpected complication. When I first announced the day, we planned to have me order the merch and then send it off to the hosts. This would require collecting addresses and sending packages to people around the world, and we realized quickly that the logistics of that would end up a mess.  Instead, we made the sticker designs (along with the Luma calendar invite graphic) publicly available for the hosts to print something locally.
When we did this, we (as the Open Home Foundation) committed to reimbursing the hosts for these swag purchases, along with venue fees or other reasonable expenses they might have on the day. The idea being that no host should be out of pocket for supporting their local Home Assistant community. You support us (by contributing time or by being [Home Assistant Cloud](/cloud/) subscribers), and we want to give back to the community in any way we can.
I'm excited to share that we plan on using those same guidelines for any community meetup, not just the ones that happen on Community Day! 👏🏻 We're building a new community page where all of these details will be available, so stay tuned for more information.
## Some stats for the nerds
We had [82 events](https://lu.ma/haday2025) with over 1,600 registered guests, spanning nearly every corner of the globe. The events started in New Zealand and ended on the West Coast of North America. This meant we had meetups held from 10 pm May 23 to midnight May 25 (UTC time), that's over 26 hours of constant partying! 🥳
We had events in every major region except Australia! Most meetups were in Europe and North America --- probably not too surprising for most. The smallest events had 2 registered guests, and the event that had the largest number of registered guests was Utrecht, with 200!
With an average of 20 people attending a meetup, we know that we can advise a lower capacity limit for future events. This will be included as part of the guidelines we'll have on that new community page I mentioned above.
## Keep the fun going!
Many hosts told me that they've created a new space for the attendees to chat or that they were going to start doing some regular meetups (some have done both!). Since Luma worked so well for us for Community Day, I've created [a general calendar for meetups](https://lu.ma/homeassistant)! I also have [graphic assets](https://drive.google.com/drive/folders/1i7Ta0910ozc66jKqhib5fCrOpYyt9b_J?usp=share_link) publicly available for your Luma event and any social media you'd like to post your event on --- use the 1:1 ratio image for the invite image on Luma. There are two events live there now, way to go Chile (Santiago) and Belgium (Hasselt)! 🤩
While we don't have a solid date for next year's Home Assistant Community Day, I can at least let you know that it will not be in May and instead later in the year. I'm aiming to give you at least a two-month heads-up for when it will be this time. We're planning on doing something bigger and I can't wait to do it all again with y'all next year. 😌
P.S. - Did you spot our [refreshed Creator Network](https://creators.home-assistant.io) page yet? 👀

158
source/changelogs/core-2025.6.markdown
View File

@ -745,6 +745,164 @@ For a summary in a more readable format:
[@tronikos]: https://github.com/tronikos
[@tsvi]: https://github.com/tsvi
## Release 2025.6.2 - June 23
- Remove address info from Rachio calendar events ([@brg468] - [#145896])
- Bump uiprotect to 7.12.0 ([@RaHehl] - [#146337])
- Bump uiprotect to 7.13.0 ([@RaHehl] - [#146410])
- Bump reolink-aio to 0.14.0 ([@starkillerOG] - [#146566])
- Bump pypck to 0.8.7 ([@alengwenus] - [#146657])
- Update rokuecp to 0.19.5 ([@ctalkington] - [#146788])
- Use Shelly main device area as suggested area for sub-devices ([@bieniu] - [#146810])
- Fix blocking open in Minecraft Server ([@elmurato] - [#146820])
- Bump aioamazondevices to 3.1.3 ([@chemelli74] - [#146828])
- Bump aiohttp to 3.12.13 ([@bdraco] - [#146830])
- Bump motion blinds to 0.6.28 ([@starkillerOG] - [#146831])
- Bump pypck to 0.8.8 ([@alengwenus] - [#146841])
- Fix missing key for ecosmart in older Wallbox models ([@hesselonline] - [#146847])
- Bump bthome-ble to 3.13.1 ([@Ernst79] - [#146871])
- Bump reolink-aio to 0.14.1 ([@starkillerOG] - [#146903])
- Add debug log for update in onedrive ([@zweckj] - [#146907])
- Switchbot Cloud: Fix device type filtering in sensor ([@SeraphicRav] - [#146945])
- Bump pySmartThings to 3.2.5 ([@joostlek] - [#146983])
- Bump ical to 10.0.4 ([@allenporter] - [#147005])
- Fix incorrect use of zip in service.async_get_all_descriptions ([@emontnemery] - [#147013])
- Disable Z-Wave indidator CC entities by default ([@MartinHjelmare] - [#147018])
- Fix Shelly entity names for gen1 sleeping devices ([@bieniu] - [#147019])
- Disable Z-Wave idle notification button ([@MartinHjelmare] - [#147026])
- Fix log in onedrive ([@zweckj] - [#147029])
- Bump holidays lib to 0.75 ([@gjohansson-ST] - [#147043])
- Bump aiohomeconnect to 0.18.0 ([@Diegorro98] - [#147044])
- Bump ZHA to 0.0.60 ([@puddly] - [#147045])
- Bump pylamarzocco to 2.0.9 ([@zweckj] - [#147046])
- Handle missing widget in lamarzocco ([@zweckj] - [#147047])
- Bump aioamazondevices to 3.1.4 ([@chemelli74] - [#146883])
- Bump aioamazondevices to 3.1.12 ([@chemelli74] - [#147055])
- Bump uiprotect to version 7.14.0 ([@RaHehl] - [#147102])
- Improve advanced Z-Wave battery discovery ([@MartinHjelmare] - [#147127])
- Fix Charge Cable binary sensor in Teslemetry ([@Bre77] - [#147136])
- [ci] Bump cache key version ([@cdce8p] - [#147148])
- Bump homematicip to 2.0.6 ([@hahn-th] - [#147151])
- Wallbox fix too many requests by API ([@hesselonline] - [#147197])
- Bump deebot-client to 13.4.0 ([@edenhaus] - [#147221])
- Handle the new JSON payload from traccar clients ([@ludeeus] - [#147254])
- Bump aioamazondevices to 3.1.14 ([@chemelli74] - [#147257])
- Bump uiprotect to version 7.14.1 ([@RaHehl] - [#147280])
- Bump aioesphomeapi to 32.2.4 ([@synesthesiam] - [#147100])
- Bump aioesphomeapi to 33.0.0 ([@bdraco] - [#147296])
- Fix reload for Shelly devices with no script support ([@chemelli74] - [#147344])
- Add Matter protocol to Switchbot ([@joostlek] - [#147356])
[#145650]: https://github.com/home-assistant/core/pull/145650
[#145896]: https://github.com/home-assistant/core/pull/145896
[#146337]: https://github.com/home-assistant/core/pull/146337
[#146410]: https://github.com/home-assistant/core/pull/146410
[#146566]: https://github.com/home-assistant/core/pull/146566
[#146657]: https://github.com/home-assistant/core/pull/146657
[#146764]: https://github.com/home-assistant/core/pull/146764
[#146788]: https://github.com/home-assistant/core/pull/146788
[#146810]: https://github.com/home-assistant/core/pull/146810
[#146820]: https://github.com/home-assistant/core/pull/146820
[#146828]: https://github.com/home-assistant/core/pull/146828
[#146830]: https://github.com/home-assistant/core/pull/146830
[#146831]: https://github.com/home-assistant/core/pull/146831
[#146841]: https://github.com/home-assistant/core/pull/146841
[#146847]: https://github.com/home-assistant/core/pull/146847
[#146871]: https://github.com/home-assistant/core/pull/146871
[#146883]: https://github.com/home-assistant/core/pull/146883
[#146903]: https://github.com/home-assistant/core/pull/146903
[#146907]: https://github.com/home-assistant/core/pull/146907
[#146945]: https://github.com/home-assistant/core/pull/146945
[#146983]: https://github.com/home-assistant/core/pull/146983
[#147005]: https://github.com/home-assistant/core/pull/147005
[#147013]: https://github.com/home-assistant/core/pull/147013
[#147018]: https://github.com/home-assistant/core/pull/147018
[#147019]: https://github.com/home-assistant/core/pull/147019
[#147026]: https://github.com/home-assistant/core/pull/147026
[#147029]: https://github.com/home-assistant/core/pull/147029
[#147043]: https://github.com/home-assistant/core/pull/147043
[#147044]: https://github.com/home-assistant/core/pull/147044
[#147045]: https://github.com/home-assistant/core/pull/147045
[#147046]: https://github.com/home-assistant/core/pull/147046
[#147047]: https://github.com/home-assistant/core/pull/147047
[#147055]: https://github.com/home-assistant/core/pull/147055
[#147100]: https://github.com/home-assistant/core/pull/147100
[#147102]: https://github.com/home-assistant/core/pull/147102
[#147127]: https://github.com/home-assistant/core/pull/147127
[#147136]: https://github.com/home-assistant/core/pull/147136
[#147148]: https://github.com/home-assistant/core/pull/147148
[#147151]: https://github.com/home-assistant/core/pull/147151
[#147197]: https://github.com/home-assistant/core/pull/147197
[#147221]: https://github.com/home-assistant/core/pull/147221
[#147254]: https://github.com/home-assistant/core/pull/147254
[#147257]: https://github.com/home-assistant/core/pull/147257
[#147280]: https://github.com/home-assistant/core/pull/147280
[#147296]: https://github.com/home-assistant/core/pull/147296
[#147344]: https://github.com/home-assistant/core/pull/147344
[#147356]: https://github.com/home-assistant/core/pull/147356
[@Bre77]: https://github.com/Bre77
[@Diegorro98]: https://github.com/Diegorro98
[@Ernst79]: https://github.com/Ernst79
[@MartinHjelmare]: https://github.com/MartinHjelmare
[@RaHehl]: https://github.com/RaHehl
[@SeraphicRav]: https://github.com/SeraphicRav
[@alengwenus]: https://github.com/alengwenus
[@allenporter]: https://github.com/allenporter
[@bdraco]: https://github.com/bdraco
[@bieniu]: https://github.com/bieniu
[@brg468]: https://github.com/brg468
[@cdce8p]: https://github.com/cdce8p
[@chemelli74]: https://github.com/chemelli74
[@ctalkington]: https://github.com/ctalkington
[@edenhaus]: https://github.com/edenhaus
[@elmurato]: https://github.com/elmurato
[@emontnemery]: https://github.com/emontnemery
[@frenck]: https://github.com/frenck
[@gjohansson-ST]: https://github.com/gjohansson-ST
[@hahn-th]: https://github.com/hahn-th
[@hesselonline]: https://github.com/hesselonline
[@joostlek]: https://github.com/joostlek
[@ludeeus]: https://github.com/ludeeus
[@puddly]: https://github.com/puddly
[@starkillerOG]: https://github.com/starkillerOG
[@synesthesiam]: https://github.com/synesthesiam
[@zweckj]: https://github.com/zweckj
[alexa_devices docs]: /integrations/alexa_devices/
[bthome docs]: /integrations/bthome/
[ecovacs docs]: /integrations/ecovacs/
[esphome docs]: /integrations/esphome/
[holiday docs]: /integrations/holiday/
[home_connect docs]: /integrations/home_connect/
[homematicip_cloud docs]: /integrations/homematicip_cloud/
[lamarzocco docs]: /integrations/lamarzocco/
[lcn docs]: /integrations/lcn/
[local_calendar docs]: /integrations/local_calendar/
[local_todo docs]: /integrations/local_todo/
[minecraft_server docs]: /integrations/minecraft_server/
[motion_blinds docs]: /integrations/motion_blinds/
[onedrive docs]: /integrations/onedrive/
[rachio docs]: /integrations/rachio/
[remote_calendar docs]: /integrations/remote_calendar/
[reolink docs]: /integrations/reolink/
[roku docs]: /integrations/roku/
[shelly docs]: /integrations/shelly/
[smartthings docs]: /integrations/smartthings/
[switchbot_cloud docs]: /integrations/switchbot_cloud/
[teslemetry docs]: /integrations/teslemetry/
[traccar docs]: /integrations/traccar/
[unifiprotect docs]: /integrations/unifiprotect/
[wallbox docs]: /integrations/wallbox/
[workday docs]: /integrations/workday/
[zha docs]: /integrations/zha/
[zwave_js docs]: /integrations/zwave_js
## Release 2025.6.3 - June 24
- Update frontend to 20250531.4 ([@bramkragten] - [#147414])
[#147414]: https://github.com/home-assistant/core/pull/147414
[@bramkragten]: https://github.com/bramkragten
[#123284]: https://github.com/home-assistant/core/pull/123284
[#125764]: https://github.com/home-assistant/core/pull/125764
[#129456]: https://github.com/home-assistant/core/pull/129456

BIN
source/images/blog/2025-06-community-day-wrap-up/art.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 130 KiB

BIN
source/images/docs/configuration/customizing-entity-dialog.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 30 KiB

After

Width:  |  Height:  |  Size: 31 KiB

BIN
source/images/docs/configuration/customizing-entity.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 69 KiB

After

Width:  |  Height:  |  Size: 81 KiB