Merge remote-tracking branch 'upstream/next' into volvo/feature/device-tracker

Author: thomasddn

.github/copilot-instructions.md

@@ -51,9 +51,8 @@ speakers.
 The writing needs to be inclusive, objective, and not gender biased, polarizing,
 or discriminatory. We want to be welcoming to all users.
 
-Write towards the reader directly, and not a group of users. Write from a second-person perspective, using "you" and "your" instead of "the user"
-second-person perspective, using "you" and "your" instead of "the user"
-or "users".
+Write towards the reader directly, and not a group of users. 
+Write from a second-person perspective, using "you" and "your" instead of "the user" or "users".
 
 Make the text feel personal and friendly, as if you are talking to a friend who
 really enjoys technology and enjoys this hobby of home automation. Write in

CODEOWNERS

@@ -107,9 +107,9 @@ social:
 
 # Home Assistant release details
 current_major_version: 2025
-current_minor_version: 9
-current_patch_version: 4
-date_released: 2025-09-19
+current_minor_version: 10
+current_patch_version: 0
+date_released: 2025-10-01
 
 # Either # or the anchor link to latest release notes in the blog post.
 # Must be prefixed with a # and have double quotes around it.

_config.yml

@@ -34,14 +34,18 @@ Name:
   description: The button name that is displayed on the card. If this field is left blank and the card interacts with an entity, the button name defaults to the entity name. Otherwise, no name is displayed.
 Icon:
   description: The icon that is displayed on the card. If this field is left blank and the card interacts with an entity, the icon defaults to the entity domain icon. Otherwise, no icon is displayed.
-Show Name:
-  description: A toggle to show or hide the button name.
-Show Icon:
-  description: A toggle to show or hide the icon.
 Icon Height:
   description: The height of the icon, in pixels.
+Color:
+  description: The color of the icon.
 Theme:
   description: Name of any loaded theme to be used for this card. For more information about themes, see the [frontend documentation](/integrations/frontend/).
+Show Name:
+  description: A toggle to show or hide the button name.
+Show State:
+  description: A toggle to show or hide the state of the entity.
+Show Icon:
+  description: A toggle to show or hide the icon.
 Tap Action:
   description: The action taken on card tap. For more information, see the [action documentation](/dashboards/actions/#tap-action).
 Hold Action:
@@ -91,11 +95,11 @@ icon_height:
   description: The height of the icon. Any CSS value may be used.
   type: string
   default: auto
-state_color:
+color:
   required: false
-  description: If false, the icon does not change color when the entity is active.
-  type: boolean
-  default: true
+  description: Set the color for the icon. By default, the color is based on `state`, `domain`, and `device_class` of your entity. It accepts [color token](/dashboards/button/#available-colors) or hex color code.
+  type: string
+  default: state
 tap_action:
   required: false
   description: The action taken on card tap. For more information, see the [action documentation](/dashboards/actions/#tap-action).
@@ -203,3 +207,7 @@ cards:
         show_name: true
         show_icon: true
 ```
+
+## Available colors
+
+The following colors are available to colorize the button card: `primary`, `accent`, `disabled`, `red`, `pink`, `purple`, `deep-purple`, `indigo`, `blue`, `light-blue`, `cyan`, `teal`, `green`, `light-green`, `lime`, `yellow`, `amber`, `orange`, `deep-orange`, `brown`, `grey`, `blue-grey`, `black`, `white`, or any hex color code (for example, `#93c47d`).

source/_dashboards/button.markdown

@@ -121,10 +121,29 @@ link_dashboard: true
 The energy sources table card shows all your energy sources, and the corresponding amount of energy.
 If setup, it will also show the costs and compensation per source and the total.
 
+
+### YAML configuration
+
+The following YAML options are available
+
+{% configuration %}
+type:
+  required: true
+  description: "`energy-sources-table`"
+  type: string
+types:
+  required: false
+  description: "If defined, table displays listed types of consumption only. Valid values are: `grid`, `solar`, `battery`, `gas`, and `water`."
+  type: list
+{% endconfiguration %}
+
 ### Example
 
 ```yaml
 type: energy-sources-table
+types:
+  - gas
+  - water
 ```
 
 ## Grid neutrality gauge
@@ -196,7 +215,29 @@ type: energy-self-sufficiency-gauge
 
 The devices energy graph show the energy usage per device, it is sorted by usage.
 
-By default, this card will show all your devices. Optionally, the number of devices can be limited by adding the `max_devices` option and specifying the maximum number of devices to show. If there are more devices available than shown, the devices with the highest energy usage are shown.
+### YAML configuration
+
+The following YAML options are available
+
+{% configuration %}
+type:
+  required: true
+  description: "`energy-devices-graph`"
+  type: string
+title:
+  required: false
+  description: The title of the card.
+  type: string
+max_devices:
+  required: false
+  description: By default, this card will show all your devices. Optionally, the number of devices can be limited by adding the `max_devices` option and specifying the maximum number of devices to show. If there are more devices available than shown, the devices with the highest energy usage are shown.
+  type: integer
+hide_compound_stats:
+  required: false
+  description: Hide higher level devices like breakers. These are devices that are set as `included_in_stat` of another device.
+  type: boolean
+  default: false
+{% endconfiguration %}
 
 ### Examples
 

source/_dashboards/energy.markdown

@@ -32,7 +32,7 @@ type:
   type: string
 entity:
   required: true
-  description: Entity ID of `plant` domain.
+  description: Entity ID of `plant` domain. For more information, see the [`plant` integration](/integrations/plant).
   type: string
 name:
   required: false

source/_dashboards/plant-status.markdown

@@ -2,15 +2,15 @@
 type: card
 title: "Thermostat card"
 sidebar_label: Thermostat
-description: "The thermostat card gives control of your climate entity, allowing you to change the temperature and mode of the entity."
+description: "The thermostat card gives control of your climate or water heater entity, allowing you to change the temperature and mode of the entity."
 related:
   - docs: /integrations/frontend/
     title: Themes
   - docs: /dashboards/cards/
     title: Dashboard cards
 ---
 
-The thermostat card gives control of your [climate](/integrations/#climate) {% term entity %}, allowing you to change the temperature and mode of the {% term entity %}.
+The thermostat card gives control of your [climate](/integrations/#climate) {% term entity %} or [water heater](/integrations/#water_heater) {% term entity %}, allowing you to change the temperature and mode of the {% term entity %}.
 
 <p class='img'>
   <img src='/images/dashboards/thermostat_card.png' alt='Screenshot of the thermostat card'>
@@ -32,7 +32,7 @@ type:
   type: string
 entity:
   required: true
-  description: Entity ID of `climate` domain.
+  description: Entity ID of `climate` or `water_heater` domain.
   type: string
 name:
   required: false
@@ -50,7 +50,7 @@ show_current_as_primary:
   default: false
 features:
   required: false
-  description: Additional widgets to control your entity. See [available features](/dashboards/features). Only climate related features are supported.
+  description: Additional widgets to control your entity. See [available features](/dashboards/features). Only climate or water heater related features are supported.
   type: list
 {% endconfiguration %}
 

source/_dashboards/thermostat.markdown

@@ -71,6 +71,11 @@ hide_create:
   description: Hide the textbox for creating new tasks at the top of the card.
   type: boolean
   default: "false"
+hide_section_headers:
+  required: false
+  description: Hide the 'Active' and 'Completed' sections with the overflow menus.
+  type: boolean
+  default: "false"
 display_order:
   required: false
   description: "Optionally sorts the items in the to-do list for display. Options are: `none`: Show the list in its original order. `alpha_asc`: Sort the list in alphabetical order. `alpha_desc`: Sort the list in reverse alphabetical order. `duedate_asc`: Sort the list by due date (soonest first). `duedate_desc`: Sort the list by reverse due date (soonest last)."

source/_dashboards/todo-list.markdown

@@ -967,17 +967,27 @@ See the [Persistent Notification](/integrations/persistent_notification/) integr
 
 ## Webhook trigger
 
-Webhook trigger fires when a web request is made to the webhook endpoint: `/api/webhook/<webhook_id>`. The webhook endpoint is created automatically when you set it as the `webhook_id` in an automation trigger.
+Webhook trigger fires when a web request is made to the webhook endpoint: `/api/webhook/<webhook_id>`. The webhook endpoint is created automatically when you set it as the `webhook_id` in an automation trigger. The `webhook_id` can either be a static value or computed using [limited templates](/docs/configuration/templating/#limited-templates).
+
+{% note %}
+The `webhook_id` template is only evaluated when setting up the trigger, they will not be re-evaluated for incomming webhook triggers.
+{% endnote %}
 
 ```yaml
 automation:
+  trigger_variables:
+    webhook_id_variable: "template_webhook_id"
   triggers:
     - trigger: webhook
       webhook_id: "some_hook_id"
       allowed_methods:
         - POST
         - PUT
       local_only: true
+    - trigger: webhook
+      webhook_id: "{{ webhook_id_variable }}"
+      allowed_methods:
+        - POST
 ```
 
 You can run this automation by sending an HTTP POST request to `http://your-home-assistant:8123/api/webhook/some_hook_id`. Here is an example using the **curl** command line program, with an example form data payload:

source/_docs/automation/trigger.markdown

@@ -221,7 +221,7 @@ learn more about packages, see the [Packages](/docs/configuration/packages) page
 
 That about wraps it up.
 
-If you have issues, checkout `home-assistant.log` in the configuration directory as well as your indentations. If all else fails, head over to our [Discord chat server][discord] and ask away.
+If you have issues, check the file indentations and check [the Home Assistant logs](/integrations/logger/#viewing-logs). If all else fails, head over to our [Discord chat server][discord] and ask away.
 
 ## Debugging configuration files