Merge branch 'current' into dependabot/github_actions/docker/login-action-3.6.0

Author: bdraco

.github/workflows/component-image.yml

@@ -32,11 +32,20 @@ jobs:
 
       - name: Get Component name
         id: get_component
-        run: |-
-          comment="${{ github.event.comment.body }}"
-          component=$(echo $comment | sed -n 's/^@esphomebot generate image //p')
-          echo "name=$component" >> $GITHUB_OUTPUT
-          echo "name_lower=${component,,}" >> $GITHUB_OUTPUT
+        env:
+          COMMENT_BODY: ${{ github.event.comment.body }}
+        run: |
+          # Extract component name using bash parameter expansion (no external commands)
+          component="${COMMENT_BODY#@esphomebot generate image }"
+
+          # Validate component name: only lowercase alphanumeric and underscores
+          if [[ "$component" =~ ^[a-z0-9_]+$ ]]; then
+            echo "name=$component" >> $GITHUB_OUTPUT
+            echo "name_lower=${component,,}" >> $GITHUB_OUTPUT
+          else
+            echo "::error::Invalid component name. Must contain only lowercase letters, numbers, and underscores."
+            exit 1
+          fi
 
   generate:
     name: Generate
@@ -50,7 +59,7 @@ jobs:
           component: ${{ needs.prepare.outputs.name }}
 
       - name: Upload
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4.6.2
+        uses: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4 # v5.0.0
         id: upload-artifact
         with:
           name: ${{ needs.prepare.outputs.name }}

.github/workflows/stale.yml

@@ -16,7 +16,7 @@ jobs:
   stale:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@3a9db7e6a41a89f618792c92c0e97cc736e1b13f # v10
+      - uses: actions/stale@5f858e3efba33a5ca4407a664cc011ad407f2008 # v10
         with:
           days-before-pr-stale: 60
           days-before-pr-close: 7

.markdownlintrc

@@ -7,6 +7,7 @@
   "MD024": {
     "siblings_only": true
   },
+  "MD028": false,
   "MD029": {
     "style": "one"
   },

Dockerfile

@@ -3,6 +3,7 @@ FROM python:3.13-slim
 RUN apt-get update && apt-get install -y --no-install-recommends \
         curl \
         git \
+        jq \
         make \
         openssh-client \
         hugo \

content/automations/_index.md

@@ -7,6 +7,8 @@ params:
     image: auto-fix.svg
 ---
 
+{{< anchor "automation" >}}
+
 Automations are a very powerful aspect of ESPHome; they allow you to easily perform actions given some condition(s).
 
 When you want your ESPHome device to respond to its environment, you use an automation. Here are some examples:

content/automations/actions.md

@@ -62,7 +62,7 @@ switch:
      id: dehumidifier1
 ```
 
-First, we have to give the dehumidifier `switch` an [ID](#config-id) so that we can refer to it inside of our
+First, we have to give the dehumidifier `switch` an [ID](/guides/configuration-types#id) so that we can refer to it inside of our
 automation.
 
 {{< anchor "actions-trigger" >}}
@@ -178,11 +178,10 @@ on_...:
     - delay: !lambda "if (id(reed_switch).state) return 1000; else return 0;"
 ```
 
-{{< note >}}
-This is a "smart" asynchronous delay - other code will still run in the background while
-the delay is happening. When using a lambda call, you should return the delay value in milliseconds.
+> [!NOTE]
+> This is a "smart" asynchronous delay - other code will still run in the background while
+> the delay is happening. When using a lambda call, you should return the delay value in milliseconds.
 
-{{< /note >}}
 {{< anchor "if_action" >}}
 
 ### `if` Action
@@ -214,19 +213,19 @@ on_...:
 
 At least one of `condition`, `all` or `any` must be provided.
 
-- **condition** (*Optional*, [Condition](#config-condition)): The condition to check to determine which branch to take.
+- **condition** (*Optional*, [Condition](#all-conditions)): The condition to check to determine which branch to take.
   If this is configured with a list of conditions then they must all be true for the condition to be true.
 
-- **all** (*Optional*, [Condition](#config-condition)): Takes a list of conditions, all of which must be true (and is
+- **all** (*Optional*, [Condition](#all-conditions)): Takes a list of conditions, all of which must be true (and is
   therefore equivalent to `condition`  .)
 
-- **any** (*Optional*, [Condition](#config-condition)): Takes a list of conditions; if at least one is true, the
+- **any** (*Optional*, [Condition](#all-conditions)): Takes a list of conditions; if at least one is true, the
   condition will be true.
 
-- **then** (*Optional*, [Action](#config-action)): The action to perform if the condition evaluates to true.
+- **then** (*Optional*, [Action](#all-actions)): The action to perform if the condition evaluates to true.
   Defaults to doing nothing.
 
-- **else** (*Optional*, [Action](#config-action)): The action to perform if the condition evaluates to false.
+- **else** (*Optional*, [Action](#all-actions)): The action to perform if the condition evaluates to false.
   Defaults to doing nothing.
 
 {{< anchor "lambda_action" >}}
@@ -254,18 +253,20 @@ on_...:
   - repeat:
       count: 5
       then:
+        - lambda: ESP_LOGI("main", "Turning lights on for iteration [%d]", iteration);
         - light.turn_on: some_light
         - delay: 1s
+        - lambda: ESP_LOGI("main", "Turning lights off for iteration [%d]", iteration);
         - light.turn_off: some_light
         - delay: 10s
 ```
 
 #### Configuration variables
 
 - **count** (**Required**, int): The number of times the action should be repeated. The counter is available to
-  lambdas using the reserved word "iteration".
+  lambdas using the implicit script parameter `iteration`.
 
-- **then** (**Required**, [Action](#config-action)): The action to repeat.
+- **then** (**Required**, [Action](#all-actions)): The action to repeat.
 
 {{< anchor "wait_until_action" >}}
 
@@ -298,8 +299,8 @@ on_...:
 
 #### Configuration variables
 
-- **condition** (**Required**, [Condition](#config-condition)): The condition to wait to become true.
-- **timeout** (*Optional*, [Time](#config-time)): Time to wait before timing out. Defaults to never timing out.
+- **condition** (**Required**, [Condition](#all-conditions)): The condition to wait to become true.
+- **timeout** (*Optional*, [Time](/guides/configuration-types#time)): Time to wait before timing out. Defaults to never timing out.
 
 {{< anchor "while_action" >}}
 
@@ -322,10 +323,10 @@ on_...:
 
 #### Configuration variables
 
-- **condition** (**Required**, [Condition](#config-condition)): The condition to check to determine whether or not to
+- **condition** (**Required**, [Condition](#all-conditions)): The condition to check to determine whether or not to
   execute.
 
-- **then** (**Required**, [Action](#config-action)): The action to perform until the condition evaluates to false.
+- **then** (**Required**, [Action](#all-actions)): The action to perform until the condition evaluates to false.
 
 {{< anchor "component-update_action" >}}
 
@@ -456,10 +457,10 @@ on_...:
 
 #### Configuration variables
 
-- **time** (**Required**, [templatable](#config-templatable), [Time](#config-time)):
+- **time** (**Required**, [templatable](/automations/templates), [Time](/guides/configuration-types#time)):
   The time for which the condition has to have been true.
 
-- **condition** (**Required**, [condition](#config-condition)): The condition to check.
+- **condition** (**Required**, [condition](#all-conditions)): The condition to check.
 
 {{< anchor "lambda_condition" >}}
 

content/automations/templates.md

@@ -55,25 +55,23 @@ Finally, `id(...)` is a helper function that makes ESPHome fetch an object with
 somewhere else, like `top_end_stop`  ) and lets you call any of ESPHome's many APIs directly. For example, here we're
 retrieving the current state of the end stop using `.state` and using it to construct our cover state.
 
-{{< note >}}
-ESPHome does not check the validity of lambda expressions you enter and will blindly copy them into the generated
-C++ code. If compilation fails or something else is not working as expected with lambdas, it's always best to look
-at the generated C++ source file under `<NODE_NAME>/src/main.cpp`.
+> [!NOTE]
+> ESPHome does not check the validity of lambda expressions you enter and will blindly copy them into the generated
+> C++ code. If compilation fails or something else is not working as expected with lambdas, it's always best to look
+> at the generated C++ source file under `<NODE_NAME>/src/main.cpp`.
+
+> [!TIP]
+> To store local variables inside lambdas that retain their value across executions, you can create `static`
+> variables as shown in the example below. Here, the variable `num_executions` is incremented by one each time the
+> lambda is executed and the current value is logged.
+>
+> ```yaml
+> lambda: |-
+>   static int num_executions = 0;
+>   ESP_LOGD("main", "I am at execution number %d", num_executions);
+>   num_executions += 1;
+> ```
 
-{{< /note >}}
-{{< tip >}}
-To store local variables inside lambdas that retain their value across executions, you can create `static`
-variables as shown in the example below. Here, the variable `num_executions` is incremented by one each time the
-lambda is executed and the current value is logged.
-
-```yaml
-lambda: |-
-  static int num_executions = 0;
-  ESP_LOGD("main", "I am at execution number %d", num_executions);
-  num_executions += 1;
-```
-
-{{< /tip >}}
 {{< anchor "config-templatable" >}}
 
 ## Templating Actions

content/changelog/2022.1.0.md

@@ -44,7 +44,7 @@ With ESPHome Web we took the installation bits of the ESPHome dashboard and made
 over HTTPS. It works 100% in your browser without a backend or data leaving your computer. Now anyone can easily
 install ESPHome on their devices to get started.
 
-`Visit ESPHome Web`_
+[Visit ESPHome Web](https://web.esphome.io)
 
 ## JSON
 

content/changelog/2022.12.0.md

@@ -32,11 +32,10 @@ of the performance increases for bluetooth, it is best to at least one serial fl
 
 ## Container images
 
-{{< note >}}
-This breaking change only affects you if you use docker containers directly and specify the suffix
-in your image.
+> [!NOTE]
+> This breaking change only affects you if you use docker containers directly and specify the suffix
+> in your image.
 
-{{< /note >}}
 2022.12.6 changes the way the container images are built and published. This is due to something
 breaking somewhere that we could not explain. It has to do with the `docker manifest` command
 which has been around for a while but always been marked as `experimental` so we cannot really

content/changelog/2023.12.0.md

@@ -32,7 +32,7 @@ This is a common source of issues and generally a pin does not need to be reused
 in a single configuration. Pins should only be reused in a very limited set of circumstances and seeing the
 error will generally mean that you need to reorganise your configuration to not reuse the pins.
 The error can be bypassed by specifically adding another config item to all of the
-duplicate pin definitions. See the [Pin Schema](#config-pin_schema) for details.
+duplicate pin definitions. See the [Pin Schema](/guides/configuration-types#pin-schema) for details.
 
 ## Touchscreen internal changes