Skip to content

Add weekdays to time trigger #39707

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: next
Choose a base branch
from
Open

Add weekdays to time trigger #39707

wants to merge 1 commit into from

Conversation

frenck
Copy link
Member

@frenck frenck commented Jun 25, 2025

Proposed change

Documents the new week day option on the time trigger

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

  • Documentation
    • Added a new section on "Weekday filtering" to the time trigger documentation, detailing how to use the weekday option to restrict automations to specific days. Includes examples for single and multiple weekdays, weekends, and combining with input datetime entities.

@Copilot Copilot AI review requested due to automatic review settings June 25, 2025 11:59
@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo next This PR goes into the next branch labels Jun 25, 2025
Copy link

netlify bot commented Jun 25, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit b80f77a
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/685be4b08e3e3d0008974b18
😎 Deploy Preview https://deploy-preview-39707--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This pull request documents the new weekday filtering option for time triggers in Home Assistant automations. It adds a new section with examples demonstrating the use of a single weekday, multiple weekdays, a weekend example, and integration with an input datetime entity.

Copy link
Contributor

coderabbitai bot commented Jun 25, 2025

📝 Walkthrough

Walkthrough

The documentation for automation time triggers has been updated to include a new "Weekday filtering" section. This section explains the use of a new weekday option, providing examples of how to configure automations to trigger on specific days of the week using YAML configuration snippets.

Changes

File Change Summary
source/_docs/automation/trigger.markdown Added documentation for the weekday option in time triggers, including usage examples and YAML.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant AutomationEngine

    User->>AutomationEngine: Define time trigger with weekday option in YAML
    AutomationEngine->>AutomationEngine: Evaluate current day and time
    AutomationEngine-->>User: Trigger automation only if current weekday matches configuration
Loading

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
source/_docs/automation/trigger.markdown (4)

828-835: Add trailing blank line & clarify “expanded format” list

  1. Markdown-lint MD032 is triggered because the bullet list isn’t followed by a blank line.
  2. “Expanded format” is mentioned but not exemplified (e.g. "monday", "tuesday"). Adding one short sentence or an example avoids confusion.
-The `weekday` option accepts:
-- A single weekday as a string: `"mon"`, `"tue"`, `"wed"`, `"thu"`, `"fri"`, `"sat"`, `"sun"`
-- A list of weekdays using the expanded format
+The `weekday` option accepts:
+- A single weekday as a string: `"mon"`, `"tue"`, `"wed"`, `"thu"`, `"fri"`, `"sat"`, `"sun"`
+- A list of weekdays using the expanded format, e.g. `"monday"`, `"tuesday"`, …
+

841-850: Indentation inconsistent with earlier Time-trigger snippets

Previous examples use four-space indent for the inner trigger list. Keeping that style improves readability & copy-paste reliability.

-  - triggers:
-      - trigger: time
+  - triggers:
+    - trigger: time

Repeat the same 2-space reduction for the subsequent lines in this block.


857-867: Same indentation issue propagates to “Multiple weekdays” sample

Align this block with the “Time string” sample shown earlier for visual consistency:

-  - triggers:
-      - trigger: time
+  - triggers:
+    - trigger: time

905-921: Optional: call out that weekday works with sensor/offset form too

Since the preceding section demonstrated offsets (entity_id + offset), consider adding a one-liner that offsets remain supported when weekday is present, e.g. weekday-filtered “5 min before alarm”.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 479cd16 and b80f77a.

📒 Files selected for processing (1)
  • source/_docs/automation/trigger.markdown (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_docs/automation/trigger.markdown

833-833: Lists should be surrounded by blank lines
null

(MD032, blanks-around-lists)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - home-assistant-docs
  • GitHub Check: Header rules - home-assistant-docs
  • GitHub Check: Pages changed - home-assistant-docs
🔇 Additional comments (1)
source/_docs/automation/trigger.markdown (1)

876-899: Minor YAML style polish in dual-automation example

The two automation items are fine, but you can drop the blank line before the second - alias: to keep the list compact, or alternatively add # --- to visually separate them. Not critical, purely cosmetic.

Copy link
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @frenck 👍

@c0ffeeca7 c0ffeeca7 added the awaits-parent Awaits the merge of an parent PR label Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaits-parent Awaits the merge of an parent PR has-parent This PR has a parent PR in a other repo next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants