Added missing parameter names and register start climate

[TobiasLaross]

Summary by CodeRabbit

• New Features

  • Added a GitHub workflow to automatically synchronize translation files upon PR updates.
  • Updated Lynk & Co integration in Home Assistant with new service keys and additional configuration fields such as "Duration in Minutes" and "Climate Level".
  • Introduced settings in Lynk & Co integration for refresh and scan intervals.

• Enhancements

  • Improved GitHub release automation with new workflow steps.
  • Updated Lynk & Co component name and version for clarity and tracking.

• Documentation

  • Updated translations and service descriptions for Lynk & Co integration to enhance user understanding and interaction.

[coderabbitai[bot]]

Walkthrough

This update introduces new GitHub workflows enhancing automation around PR updates and release management. It also includes significant updates to the Lynk & Co Home Assistant integration, with changes in service keys, component naming, version increment, and new configuration options in both service definitions and translation files.

Changes

File Path	Change Summary
.github/workflows/...	Added release management step and a new workflow for syncing translations on PR updates.
custom_components/lynkco/...	Updated service keys, component name, version, added new service fields, and updated translations.
hacs.json	Configured settings for Lynk & Co integration with Home Assistant.

🐇✨ In the land of code and gear,
Changes come both far and near.
From workflows to a car's new key,
Syncing strings with glee, you see!
Hop along, dear Lynk & Co,
With every update, more we grow! 🚗💨
🐇✨

---

Recent Review Details

**Configuration used: CodeRabbit UI**

Commits

Files that changed from the base of the PR and between fa21845e57863d4acfa0b643df72cdbcb629f30a and 58191410bde46d61740a55862d00e3692235d208.

Files selected for processing (7)

* .github/workflows/release.yml (1 hunks) * .github/workflows/sync-translations-on-pr.yml (1 hunks) * custom_components/lynkco/__init__.py (2 hunks) * custom_components/lynkco/manifest.json (1 hunks) * custom_components/lynkco/services.yaml (3 hunks) * custom_components/lynkco/translations/en.json (1 hunks) * hacs.json (1 hunks)

Files skipped from review due to trivial changes (1)

* custom_components/lynkco/manifest.json

Additional comments not posted (7)

custom_components/lynkco/translations/en.json (2)

`38-39`: The addition of `refresh_interval` and `scan_interval` keys under the Lynk & Co Integration Settings is a positive change, enhancing user control over the integration's behavior. Ensure that the intervals are documented in the user manual or README to help users understand the expected values and their impact. --- `37-37`: The updated description for the `experimental` key is clear and informative. It properly warns users about the nature of experimental features.

.github/workflows/release.yml (1)

`39-48`: The addition of a step to create a GitHub release is correctly implemented using the `actions/create-release@v1` action. The configuration uses dynamic values for `tag_name` and `release_name`, which is a good practice. Ensure that the `VERSION` variable is always correctly extracted and validated to prevent errors during the release process.

custom_components/lynkco/services.yaml (2)

`10-10`: The new field `Duration in Minutes` for the `start_climate` service is a useful addition, providing users with the ability to specify the operation duration. The configuration of the selector with a minimum of 1 and a maximum of 30 minutes is appropriate for this context. --- `20-20`: The addition of the `Climate Level` field with options for LOW, MEDIUM, and HIGH provides clear choices for users. This is a good practice for user interfaces, making it easier for users to understand and use the service.

custom_components/lynkco/__init__.py (2)

`14-14`: The introduction of `SERVICE_START_CLIMATE_KEY` and the update in service registration from `SERVICE_START_ENGINE_KEY` to `SERVICE_START_CLIMATE_KEY` are correctly implemented. This change aligns with the PR's objective to focus more on climate control features. --- `123-123`: The registration of the `start_climate` service using the new `SERVICE_START_CLIMATE_KEY` is correctly done. This ensures that the service can be accessed and used within the Home Assistant environment.

--- 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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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.` 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 a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.