Merge branch 'current' into patch-107

Author: Hedda

.github/workflows/test.yml

@@ -8,7 +8,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out files from GitHub
-        uses: actions/[email protected].0
+        uses: actions/[email protected].1
       - name: Setting up Node.js
         uses: actions/[email protected]
         with:
@@ -25,7 +25,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out files from GitHub
-        uses: actions/[email protected].0
+        uses: actions/[email protected].1
       - name: Setting up Node.js
         uses: actions/[email protected]
         with:

Gemfile

@@ -10,8 +10,8 @@ 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'
-  gem 'rubocop', '1.66.1'
-  gem 'ruby-lsp', '0.19.1'
+  gem 'rubocop', '1.67.0'
+  gem 'ruby-lsp', '0.20.1'
   gem 'rackup', '2.1.0'
 end
 

Gemfile.lock

@@ -91,10 +91,10 @@ GEM
       racc
     pathutil (0.16.2)
       forwardable-extended (~> 2.6)
-    prism (1.1.0)
+    prism (1.2.0)
     public_suffix (6.0.1)
     racc (1.8.1)
-    rack (3.1.7)
+    rack (3.1.8)
     rack-protection (4.0.0)
       base64 (>= 0.1.0)
       rack (>= 3.0.0, < 4)
@@ -113,7 +113,7 @@ GEM
     regexp_parser (2.9.2)
     rexml (3.3.8)
     rouge (4.4.0)
-    rubocop (1.66.1)
+    rubocop (1.67.0)
       json (~> 2.3)
       language_server-protocol (>= 3.17.0)
       parallel (~> 1.10)
@@ -125,18 +125,19 @@ GEM
       unicode-display_width (>= 2.4.0, < 3.0)
     rubocop-ast (1.32.3)
       parser (>= 3.3.1.0)
-    ruby-lsp (0.19.1)
+    ruby-lsp (0.20.1)
       language_server-protocol (~> 3.17.0)
-      prism (>= 1.1, < 2.0)
+      prism (>= 1.2, < 2.0)
       rbs (>= 3, < 4)
       sorbet-runtime (>= 0.5.10782)
     ruby-progressbar (1.13.0)
     ruby2_keywords (0.0.5)
     safe_yaml (1.0.5)
     sass (3.4.25)
-    sass-embedded (1.79.4)
-      google-protobuf (~> 4.27)
-      rake (>= 13)
+    sass-embedded (1.80.3-arm64-darwin)
+      google-protobuf (~> 4.28)
+    sass-embedded (1.80.3-x86_64-linux-gnu)
+      google-protobuf (~> 4.28)
     sass-globbing (1.1.5)
       sass (>= 3.1)
     sassc (2.1.0)
@@ -149,7 +150,7 @@ GEM
       rack-protection (= 4.0.0)
       rack-session (>= 2.0.0, < 3)
       tilt (~> 2.0)
-    sorbet-runtime (0.5.11597)
+    sorbet-runtime (0.5.11611)
     stringex (2.8.6)
     terminal-table (3.0.2)
       unicode-display_width (>= 1.1.1, < 3)
@@ -175,8 +176,8 @@ DEPENDENCIES
   nokogiri (= 1.16.7)
   rackup (= 2.1.0)
   rake (= 13.2.1)
-  rubocop (= 1.66.1)
-  ruby-lsp (= 0.19.1)
+  rubocop (= 1.67.0)
+  ruby-lsp (= 0.20.1)
   sass-globbing (= 1.1.5)
   sassc (= 2.1.0)
   sinatra (= 4.0.0)

_config.yml

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

source/_dashboards/entity-filter.markdown

@@ -95,7 +95,7 @@ state_filter:
 
 ## Conditions options
 
-You can specify multiple `conditions`, in which case the entity will be displayed if it matches any condition.
+You can specify multiple `conditions`, in which case the entity will be displayed if it matches every condition.
 
 ### State
 

source/_dashboards/heading.markdown

@@ -23,7 +23,7 @@ heading: Living room
 icon: mdi:sofa
 badges:
   - type: entity
-    entity_id: sensor.living_room_sensor_temperature
+    entity: sensor.living_room_sensor_temperature
     color: red
   - type: entity
     entity: sensor.living_room_sensor_humidity

source/_data/glossary.yml

@@ -87,6 +87,9 @@
     A binary sensor returns information about things that only have two states -
     such as on or off.
   link: /integrations/binary_sensor
+  aliases:
+    - binary_sensor
+    - binary_sensors
 - term: Blueprint
   definition: >-
     A blueprint is a script or automation configuration with certain parts
@@ -104,6 +107,13 @@
     configuration-specific settings.
   aliases:
     - blueprints
+- term: Button
+  definition: >-
+    A button entity can fire an event, or trigger an action towards a device or
+    service. It can be compared to a physical push button. The button entity does not have a state like `on` or `off`, but keeps the timestamp of when it was last pressed in the Home Assistant UI or via an action.
+  link: /integrations/button
+  aliases:
+    - buttons
 - term: Category
   definition: >-
     A category is an organization tool that allows grouping items in a table.
@@ -114,6 +124,13 @@
     have different categories than the scene, scripts, or helpers settings page.
   aliases:
     - categories
+- term: Climate
+  definition: >-
+    The Climate entity allows you to control and monitor HVAC (heating,
+    ventilating, and air conditioning) devices and thermostats.
+  link: /integrations/climate
+  aliases:
+    - climates
 - term: Commissioning
   definition: >-
     In the context of Matter devices, *commissioning* is the process of adding a
@@ -155,6 +172,8 @@
     Covers are devices such as blinds, garage doors, etc that can be opened and
     closed and optionally set to a specific position.
   link: /integrations/cover
+  aliases:
+    - covers
 - term: Custom integration
   definition: >-
     A custom integration is an integration that has been created by someone from the Home Assistant community and has been published for others to use at their own risk. Custom integrations are not supported by the Home Assistant project. They are not reviewed or tested by the Home Assistant development team and thus may negatively impact the stability of your Home Assistant instance. An example of a custom integration is the [Spook](https://spook.boo/) integration.
@@ -399,6 +418,8 @@
     A light has a brightness you can control, and optionally color temperature
     or RGB color control.
   link: /integrations/light
+  aliases:
+    - lights
 - term: Matter
   definition: >-
     Matter is an open-source standard that defines how to control smart home

source/_data/people.yml

@@ -20,7 +20,7 @@ Madelena Mak:
 
 Guy Sie:
   name: Guy Sie
-  github: GuySie
+  github: guysie
 
 Gordon Cameron:
   name: Gordon Cameron
@@ -77,3 +77,11 @@ Zac West:
 Klaas Schoute:
   name: Klaas Schoute
   github: klaasnicolaas
+
+Joakim Sørensen:
+  name: Joakim Sørensen
+  github: ludeeus
+
+Andy Gill:
+  name: Andy Gill
+  github: ncandyg

source/_includes/post/author.html

@@ -8,7 +8,7 @@
 {% if author %}
   {% assign person = site.data.people[author] %}
   {% if person %}
-    <span class="byline author vcard"
+    <span class="byline author vcard">
       <a href="https://github.com/{{ person.github }}" target="_blank"><img class="author-avatar" src="https://avatars.githubusercontent.com/{{ person.github }}?size=64" alt="{{ person.name }}"/> {{ person.name }}</a>
     </span>
   {% else %}

source/_integrations/alarm_control_panel.mqtt.markdown

@@ -250,7 +250,7 @@ retain:
   type: boolean
   default: false
 state_topic:
-  description: The MQTT topic subscribed to receive state updates. A "None" payload resets to an `unknown` state. An empty payload is ignored.
+  description: "The MQTT topic subscribed to receive state updates. A \"None\" payload resets to an `unknown` state. An empty payload is ignored. Valid state payloads are: `armed_away`, `armed_custom_bypass`, `armed_home`, `armed_night`, `armed_vacation`, `arming`, `disarmed`, `disarming` `pending` and `triggered`."
   required: true
   type: string
 supported_features:

source/_integrations/ambient_station.markdown

@@ -30,8 +30,9 @@ generate both, simply utilize the profile section of
 ## Local API Option
 
 This integration communicates with Ambient Weather PWS units via the Ambient Weather
-Cloud. Users desiring a local option are encouraged to explore the
-[Ecowitt](https://www.ecowitt.com) family of devices, which are able to read RF signals
-directly from the PWS and transmit them to a variety of other applications, including
-[`ecowitt2mqtt`](https://github.com/bachya/ecowitt2mqtt) (which supports
-[MQTT Discovery](/integrations/mqtt/#mqtt-discovery)), or the built-in [Ecowitt](/integrations/ecowitt/) integration.
+Cloud. Users desiring a local option can utilize
+[`ecowitt2mqtt`](https://github.com/bachya/ecowitt2mqtt#input-data-formats)
+in `ambient_weather` mode, (which supports [MQTT Discovery](/integrations/mqtt/#mqtt-discovery)).
+
+Another option is to explore the [Ecowitt](https://www.ecowitt.com) family of devices,
+which support the built-in [Ecowitt](/integrations/ecowitt/) integration.

source/_integrations/binary_sensor.mqtt.markdown

@@ -198,7 +198,7 @@ qos:
   type: integer
   default: 0
 state_topic:
-  description: The MQTT topic subscribed to receive sensor's state.
+  description: The MQTT topic subscribed to receive sensor's state. Valid states are `OFF` and `ON`. Custom `OFF` and `ON` values can be set with the `payload_off` and `payload_on` config options.
   required: true
   type: string
 unique_id: