[LV] Add Latvian binary sensor get state translations

[klejejs]

Added sentences and tests for Latvian language binary sensor get state functionality.

The PR and translations are heavily inspired by English language implementation.

Summary by CodeRabbit

• New Features

  • Enhanced the HassGetState intent in Latvian (lv) to include new response variations (one_yesno, any, all, which, how_many) based on query context.
  • Introduced comprehensive intents for querying states of various binary sensors (battery, carbon monoxide, motion, etc.) in home automation.

• Bug Fixes

  • Corrected and updated binary sensor state values to ensure accurate responses for various conditions (e.g., battery, connectivity, door status).

• Tests

  • Added extensive test cases in Latvian for different binary sensor states to validate HassGetState intents and responses.

[coderabbitai[bot]]

:memo: Walkthrough

Walkthrough

The recent changes enhance the HassGetState intent in Latvian, adding nuanced response variations optimized for different query contexts. This involves new response formats and conditional logic to correctly address various binary sensor states. Updates span across intent, binary sensor definitions, and YAML configuration files to support more tailored and accurate user interactions.

Changes

Files	Change Summaries
responses/lv/HassGetState.yaml	Expanded HassGetState intent in Latvian with new response variations (one_yesno, any, all, which, how_many).
sentences/lv/_common.yaml	Updated binary sensor state values for various conditions (battery, gas, light, etc.).
sentences/lv/binary_sensor_HassGetState.yaml	Added intents for querying various binary sensor states in a home automation system.
tests/lv/_fixtures.yaml	Added new binary sensor configurations with specific states and attributes.
tests/lv/binary_sensor_HassGetState.yaml	Introduced comprehensive tests for various binary sensor states in Latvian for HassGetState intent.

Sequence Diagrams

New HassGetState Response Handling

sequenceDiagram
    actor User
    participant HassGetState
    participant BinarySensor
    participant CustomResponses
    User->>HassGetState: Query binary sensor state
    HassGetState->>BinarySensor: Fetch state details
    BinarySensor->>HassGetState: Return state with attributes
    HassGetState->>CustomResponses: Process state based on context
    CustomResponses->>HassGetState: Provide tailored response
    HassGetState->>User: Deliver appropriate response

---

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?

:heart: Share

• X
• Mastodon
• Reddit
• LinkedIn

:placard: 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.
  • 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 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 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 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 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.

[synesthesiam]

@makstech Does this look OK to you?