Lyric binary sensor and new sensors docs

CODEOWNERS

@@ -366,6 +366,7 @@ source/_integrations/garage_door.markdown @home-assistant/core
 source/_integrations/garages_amsterdam.markdown @klaasnicolaas
 source/_integrations/gardena_bluetooth.markdown @elupus
 source/_integrations/gate.markdown @home-assistant/core
+source/_integrations/gatus.markdown @TN-1
 source/_integrations/gaviota.markdown @starkillerOG
 source/_integrations/gdacs.markdown @exxamalte
 source/_integrations/generic.markdown @davet2001
@@ -792,7 +793,6 @@ source/_integrations/peco.markdown @IceBotYT
 source/_integrations/peco_opower.markdown @tronikos
 source/_integrations/pegel_online.markdown @mib1185
 source/_integrations/pepco.markdown @tronikos
-source/_integrations/permobil.markdown @IsakNyberg
 source/_integrations/persistent_notification.markdown @home-assistant/core
 source/_integrations/pge.markdown @tronikos
 source/_integrations/pglab.markdown @pglab-electronics

source/_actions/jewish_calendar.count_omer.markdown

@@ -5,7 +5,11 @@ domain: jewish_calendar
 description: "Returns the phrase for counting the Omer on a given date."
 ---
 
-Use this action to get the phrase for counting the Omer on a given date.
+The **Count the Omer** action returns the phrase for counting the Omer on a given date.
+
+This is useful when you want an automation or script to announce or display the daily Omer count, for example as part of an evening routine during the Omer period.
+
+This action does not support targets. In the UI, you are not prompted to choose an area, device, entity, or label. Instead, you provide the date and tradition to count for.
 
 {% include actions/ui_header.md %}
 
@@ -15,32 +19,30 @@ To count the Omer from an automation or a script:
 2. Open an existing automation or script, or select **Create automation** > **Create new automation**.
 3. If you're setting up a new automation, add a trigger in the **When** section. Scripts don't need a trigger. They run when something else calls them.
 4. In the **Then do** section, select **Add action**.
-5. Select **Jewish Calendar: Count the Omer**.
-6. Set the nusach and other options.
+5. From the search box, search for and select **Jewish Calendar: Count the Omer**.
+6. Select the **Nusach**, and optionally set the **Date**, **After sunset**, and **Language**.
 7. Select **Save**.
 
 ### Options in the UI
 
 {% options_ui %}
 Date:
-  description: The date for which to get the Omer count. If unset, the action uses today.
+  description: The date to count the Omer for. Defaults to today.
   required: false
 After sunset:
-  description: If enabled and a date is provided, the action calculates the Omer count based on the Hebrew date, which starts after sunset. Ignored if no date is specified.
+  description: Uses the next Hebrew day, which starts at sunset, for the given date. This option is ignored if the date is empty. Defaults to on.
   required: false
-  default: true
 Nusach:
-  description: The nusach, or tradition, of the Omer blessing.
-  default: sfarad
+  description: The nusach (tradition) to count the Omer in. One of Sfarad, Ashkenaz, Adot Mizrah, or Italian.
+  required: true
 Language:
-  description: The language to return. Supported languages are English, Hebrew, and French.
+  description: The language to count the Omer in. Supported languages are English, Hebrew, and French. Defaults to Hebrew.
   required: false
-  default: he
 {% endoptions_ui %}
 
 {% include actions/yaml_header.md %}
 
-In YAML, refer to this action as `jewish_calendar.count_omer`. Store the result in a response variable so you can use it in later steps:
+In YAML, refer to this action as `jewish_calendar.count_omer`. Because this action returns data, use `response_variable` to capture the result. A basic example looks like this:
 
 {% example %}
 action: |
@@ -49,63 +51,89 @@ action: |
     nusach: sfarad
     date: "2025-05-20"
     language: en
-  response_variable: omer_count
+  response_variable: omer
 {% endexample %}
 
-This returns the Omer count for May 20, 2025, in English.
+This counts the Omer for the given date and stores the result in the `omer` variable.
 
 ### Options in YAML
 
 {% options_yaml %}
 date:
-  description: The date for which to get the Omer count. If unset, the action uses today.
+  description: >
+    The date to count the Omer for. Defaults to today.
   required: false
-  type: string
+  type: date
 after_sunset:
-  description: If true and a date is provided, the action calculates the Omer count based on the Hebrew date, which starts after sunset. Ignored if no date is specified.
+  description: >
+    Uses the next Hebrew day, which starts at sunset, for the given date.
+    This option is ignored if the date is empty.
   required: false
   type: boolean
   default: true
 nusach:
-  description: The nusach, or tradition, of the Omer blessing. Supported values are `sfarad`, `ashkenaz`, `adot_mizrah`, and `italian`.
+  description: >
+    The nusach (tradition) to count the Omer in. One of `sfarad`,
+    `ashkenaz`, `adot_mizrah`, or `italian`.
   required: true
   type: string
   default: sfarad
 language:
-  description: The language to return. Supported values are `en`, `he`, and `fr`.
+  description: >
+    The language to count the Omer in. Supported values are `en`, `he`,
+    and `fr`. Defaults to Hebrew.
   required: false
   type: string
   default: he
 {% endoptions_yaml %}
 
-This action does not support targets.
-
 ## Response data
 
-The action response includes the following fields:
+The action returns the following data:
 
-- `message`: The phrase for counting the Omer. If there is no Omer count on the given day, this value is empty.
-- `weeks`: The number of complete weeks.
-- `days`: The number of days after the complete weeks.
-- `total_days`: The total number of Omer days.
+- `message`: The phrase for counting the Omer. Empty when there is no Omer count on the given day.
+- `weeks`: The number of complete weeks counted.
+- `days`: The number of days counted beyond the complete weeks.
+- `total_days`: The total number of days counted.
 
-## Good to know
+For the example above, the response looks similar to this:
 
-- If there is no Omer count on the given day, the message is empty.
-- The Hebrew date starts after sunset.
+{% example %}
+output: |
+  message: >-
+    Today is the thirty-seventh day, which are five weeks and two days of the
+    Omer
+  weeks: 5
+  days: 2
+  total_days: 37
+{% endexample %}
 
 {% include actions/more_examples.md %}
 
-### Minimal count in Hebrew
+### Count today's Omer in Hebrew
+
+For a minimal call, provide only the required nusach. With no date, the action counts the current Hebrew day, taking the current time relative to sunset into account, and returns the text in Hebrew by default.
 
 {% example %}
 action: |
   action: jewish_calendar.count_omer
   data:
     nusach: sfarad
-  response_variable: omer_count
+  response_variable: omer
+{% endexample %}
+
+This returns a response similar to:
+
+{% example %}
+output: |
+  message: היום ארבעה עשר יום שהם שני שבועות לעומר
+  weeks: 2
+  days: 0
+  total_days: 14
 {% endexample %}
 
+{% include actions/try_it.md %}
+
 {% include actions/stuck.md %}
 
 {% include actions/related.md %}

source/_actions/mastodon.post.markdown

@@ -61,6 +61,12 @@ Media description:
 Media warning:
   description: Mark the attached media as sensitive.
   required: false
+In reply to:
+  description: The ID of the status to reply to. Setting this makes the new post a reply, allowing you to create or continue a thread.
+  required: false
+Quote:
+  description: The ID of the status to quote in this post.
+  required: false
 {% endoptions_ui %}
 
 {% include actions/yaml_header.md %}
@@ -136,6 +142,16 @@ media_warning:
   required: false
   type: boolean
   default: false
+in_reply_to:
+  description: >
+    The ID of the status to reply to. Setting this makes the new post a reply, allowing you to create or continue a thread.
+  required: false
+  type: string
+quoted_status:
+  description: >
+    The ID of the status to quote in this post.
+  required: false
+  type: string
 {% endoptions_yaml %}
 
 {% note %}

source/_actions/music_assistant.play_media.markdown

@@ -39,7 +39,7 @@ Enqueue:
 Enable radio mode:
   description: Turns on radio mode to auto-generate a playlist based on the selection.
 Username:
-  description: Use this Music Assistant user to adjust the playlog entry. If the specified user has provider filtering configured, the media item selection will be made accordingly. For example, this has an effect on the resume point retrieval of an audiobook.
+  description: Use this Music Assistant user to adjust the playlog entry. If the specified user has provider filtering configured, the media item selection will be made accordingly. For example, this has an effect on the resume point retrieval of an audiobook. When left empty, it defaults to the Home Assistant user that made the request, if their username matches a Music Assistant user. When you call this action from an automation or script, set the username explicitly so the request is attributed to the right user.
 {% endoptions_ui %}
 
 {% include actions/yaml_header.md %}
@@ -84,7 +84,7 @@ radio_mode:
   type: boolean
   default: false
 username:
-  description: Use this Music Assistant user to adjust the playlog entry. If provider filtering is used, the media item will be selected accordingly.
+  description: Use this Music Assistant user to adjust the playlog entry. If the specified user has provider filtering configured, the media item selection will be made accordingly. For example, this has an effect on the resume point retrieval of an audiobook. When left empty, it defaults to the Home Assistant user that made the request, if their username matches a Music Assistant user. When you call this action from an automation or script, set the username explicitly so the request is attributed to the right user.
   required: false
   type: string
 {% endoptions_yaml %}

source/_actions/omie.get_prices_for_date.markdown

@@ -0,0 +1,106 @@
+---
+title: "Get prices for date"
+action: omie.get_prices_for_date
+domain: omie
+description: "Retrieves OMIE electricity spot prices for a specific date, for Spain, Portugal, or both."
+---
+
+Use this action to retrieve the day-ahead electricity spot prices for a specific date, for Spain, Portugal, or both countries.
+
+The OMIE sensors always reflect the current price. This action lets you fetch the prices for any published date instead, which is useful when you want to look ahead. For example, you can compare tomorrow's prices or schedule an appliance to run during the cheapest hours.
+
+This action returns its result in a response variable, which you can use in later steps of the same automation or script.
+
+Prices for the next day are published daily at around 13:30 CET/CEST. If you request a date that has not been published yet, the action reports that the prices are not available. Similarly if you request a date that is previous to the date when quarter-hourly prices became available, the action reports that no prices exist for that date and tells you the earliest date you can request.
+
+{% include actions/ui_header.md %}
+
+To get prices from an automation or a script:
+
+1. Go to {% my automations title="**Settings** > **Automations & scenes**" %}.
+2. Open an existing automation or script, or select **Create automation** > **Create new automation**.
+3. If you're setting up a new automation, add a trigger in the **When** section. Scripts don't need a trigger. They run when something else calls them.
+4. In the **Then do** section, select **Add action**.
+5. From the search box, search for and select **OMIE - Spain and Portugal electricity prices: Get prices for date**.
+6. Select the **Date** you want, and choose the **Countries** to get prices for.
+7. In the **Response variable** field, enter a name to store the data in, such as `prices`.
+8. Select **Save**.
+
+### Options in the UI
+
+{% options_ui %}
+Date:
+  description: The date to get the prices for.
+  required: true
+Countries:
+  description: The countries to get the prices for. Choose Spain, Portugal, or both. Both are selected by default.
+  required: true
+{% endoptions_ui %}
+
+{% include actions/yaml_header.md %}
+
+In YAML, refer to this action as `omie.get_prices_for_date`. Store the result in a response variable so you can use it in later steps:
+
+{% example %}
+action: |
+  action: omie.get_prices_for_date
+  data:
+    date: "2026-07-08"
+    countries:
+      - es
+      - pt
+  response_variable: prices
+{% endexample %}
+
+This fetches the prices for both Spain and Portugal on the given date.
+
+### Options in YAML
+
+{% options_yaml %}
+date:
+  description: >
+    The date to get the prices for, in YYYY-MM-DD format.
+  required: true
+  type: date
+countries:
+  description: >
+    The countries to get the prices for. A list containing es, pt, or both.
+    Defaults to both.
+  required: true
+  type: list
+{% endoptions_yaml %}
+
+## Response data
+
+The response contains a key for each requested country: `es` for Spain and `pt` for Portugal. If you request both countries, both keys are present.
+
+Each key holds a list of quarter-hourly intervals. Each interval includes the following fields:
+
+- `start`: The start time of the interval, in CET/CEST.
+- `end`: The end time of the interval, in CET/CEST.
+- `price`: The electricity spot price for the interval, in €/kWh.
+
+A shortened example of the response looks like this:
+
+```yaml
+es:
+  - start: "2026-07-08T00:00:00+02:00"
+    end: "2026-07-08T00:15:00+02:00"
+    price: 0.03415
+  - start: "2026-07-08T00:15:00+02:00"
+    end: "2026-07-08T00:30:00+02:00"
+    price: 0.03521
+pt:
+  - start: "2026-07-08T00:00:00+02:00"
+    end: "2026-07-08T00:15:00+02:00"
+    price: 0.0361
+  - start: "2026-07-08T00:15:00+02:00"
+    end: "2026-07-08T00:30:00+02:00"
+    price: 0.0372
+```
+
+{% include actions/try_it.md %}
+
+{% include actions/stuck.md %}
+
+{% include actions/related.md %}

source/_actions/onedrive.upload.markdown

@@ -66,6 +66,9 @@ filename:
   description: >
     One or more paths to the files you want to upload. The path must be in
     the `allowlist_external_dirs` of your `homeassistant:` configuration.
+    Wildcards (glob patterns) are supported, so you can upload several files
+    at once. When you use a wildcard, the folder part before the first
+    wildcard must be in `allowlist_external_dirs`.
   required: true
   type: [string, list]
 destination_folder:
@@ -104,6 +107,32 @@ action: |
 
 {% enddetails %}
 
+### Upload files using wildcards
+
+The `filename` option supports wildcards (glob patterns), so you can upload several files without listing each one:
+
+- `*` matches any number of characters within a single folder level. For example, `/media/snapshots/*.jpg` uploads every JPG file in the `snapshots` folder.
+- `**` matches folders recursively. For example, `/media/snapshots/**/*.jpg` uploads every JPG file in the `snapshots` folder and all of its subfolders.
+- `?` matches a single character.
+- `[` starts a character range, such as `[0-9]`.
+
+When a wildcard matches files in subfolders, those subfolders are recreated inside the `destination_folder` on OneDrive, preserving the original structure.
+
+If a wildcard pattern does not match any files, the action fails with an error listing the patterns that had no matches. The characters `*`, `?`, and `[` are always treated as wildcards.
+
+{% details "Upload files using a wildcard" %}
+
+{% example %}
+action: |
+  action: onedrive.upload
+  data:
+    config_entry_id: a1bee602deade2b09bc522749bbce48e
+    filename: /media/snapshots/**/*.jpg
+    destination_folder: Snapshots/2025
+{% endexample %}
+
+{% enddetails %}
+
 {% include actions/stuck.md %}
 
 {% include actions/related.md %}