[DE] Added areas to homeassistant_HassTurnOff and HassTurnOn

[SaftigeSteaks]

Now sentences like "Schalte den Computer im Wohnzimmer an" or "Mache im Wohnzimmer den Computer aus" will work

Summary by CodeRabbit

• New Features
  • Enhanced HassTurnOff intent to support varied order of <name> and <area> parameters for more flexible commands.
  • Expanded HassTurnOn intent to include optional area specifications, allowing more versatile device activation commands.

[coderabbitai]

Walkthrough

Walkthrough

The recent updates to the HassTurnOff and HassTurnOn intents enhance the flexibility of user commands by allowing optional area specifications. This change enables users to issue commands in various sequences, making interactions with the system more intuitive and accommodating different speaking styles.

Changes

File	Change Summary
sentences/de/homeassistant_HassTurnOff.yaml	Expanded the HassTurnOff intent to include optional area parameters in various sequences for user commands.
sentences/de/homeassistant_HassTurnOn.yaml	Enhanced the HassTurnOn intent by adding optional area parameters in different command sequences.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 5a8beec and 9bead00.

Files selected for processing (2)

• sentences/de/homeassistant_HassTurnOff.yaml (1 hunks)
• sentences/de/homeassistant_HassTurnOn.yaml (1 hunks)

Files not reviewed due to errors (1)

• sentences/de/homeassistant_HassTurnOn.yaml (no review received)

Additional comments not posted (10)

sentences/de/homeassistant_HassTurnOff.yaml (10)

6-6: LGTM! The optional area specification after the device name is correctly implemented.

---

7-7: LGTM! The pattern correctly allows the area to precede the device name.

---

8-8: LGTM! The optional area specification for the 'stoppe' command is correctly implemented.

---

9-9: LGTM! The pattern allowing the area before the device name with the 'stoppe' command is correctly implemented.

---

10-10: LGTM! The optional area specification for the 'deaktivieren' command is correctly implemented.

---

11-11: LGTM! The pattern allowing the area before the device name with the 'deaktivieren' command is correctly implemented.

---

12-12: LGTM! The optional area specification after the device name for the 'deaktivieren' command is correctly implemented.

---

13-13: LGTM! The pattern allowing the area before the device name for the 'deaktivieren' command is correctly implemented.

---

14-14: LGTM! The optional area specification after the device name for the 'aus' command is correctly implemented.

---

15-15: LGTM! The pattern allowing the area before the device name for the 'aus' command is correctly implemented.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.

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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.