Update documentation for fyta

[dontinelli]

Proposed change

Update documentation with new functionality (user image).

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).
  • I've opened up a PR to add logos and icons in Brands repository.
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase: Add user picture to fyta core#140934
• Link to parent pull request in the Brands repository:
• This PR fixes or closes issue: fixes #

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

• New Features
  • Introduced a "User Image" option that allows you to display your custom image instead of the default image.
• Documentation
  • Revised the configuration section for clarity, with updated headers and descriptions that better explain the image selection process.

[home-assistant]

It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the current branch. Please change the target branch of this PR to current and rebase if needed. If this is documentation for a new feature, please add a link to that PR in your description.

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	d00da3b
🔍 Latest deploy log	https://app.netlify.com/sites/home-assistant-docs/deploys/67e11f29c133250008b79397
😎 Deploy Preview	https://deploy-preview-38079--home-assistant-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the FYTA integration documentation by restructuring the configuration section. The header is changed from “Configuration options” to “Configuration”. Additionally, a new configuration option labeled “User Image” has been added. Its description clarifies that when enabled, the user image replaces the generic plant image. A reference to an external file ("option_flow.md") has also been inserted to provide further details on configuration options.

Changes

File	Change Summary
source/_integrations/fyta.markdown	Changed header to "Configuration"; added "User Image" configuration option with detailed description; added reference to "option_flow.md".

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

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

• 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>, 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 generate docstrings to generate docstrings for 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

source/_integrations/fyta.markdown (2)

44-47: Inconsistent Configuration Description

The header now reads "## Configuration," yet the paragraph immediately following (line 46) still states, "The integration has no additional configuration options." This is now contradictory given that a new configuration option ("User Image") has been added later. Please update this text to accurately describe the available configuration options.

---

72-72: Grammar & Link Fragment Improvement in Image Section

In the sentence on line 72, consider adding an article for clarity (e.g., "a generic plant image" instead of just "generic plant image"). Additionally, verify that the link fragment "preferences" correctly points to an existing section in the documentation.

🧰 Tools

🪛 LanguageTool

[uncategorized] ~72-~72: You might be missing the article “a” here.
Context: ...pending on the preferences, generic plant image or the user image set in th...

(AI_EN_LECTOR_MISSING_DETERMINER_A)

🪛 markdownlint-cli2 (0.17.2)

72-72: Link fragments should be valid
null

(MD051, link-fragments)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bec6495 and eb34337.

📒 Files selected for processing (1)

• source/_integrations/fyta.markdown (2 hunks)

🧰 Additional context used

🪛 LanguageTool

source/_integrations/fyta.markdown

[uncategorized] ~72-~72: You might be missing the article “a” here.
Context: ...pending on the preferences, generic plant image or the user image set in th...

(AI_EN_LECTOR_MISSING_DETERMINER_A)

🪛 markdownlint-cli2 (0.17.2)

source/_integrations/fyta.markdown

72-72: Link fragments should be valid
null

(MD051, link-fragments)

🔇 Additional comments (1)

source/_integrations/fyta.markdown (1)

48-54: New "User Image" Option Added Successfully

The documentation block introducing the "User Image" option is clear and adheres to expected documentation standards. Please ensure that its description—"When checked, the user image is used instead of the generic plant image."—accurately reflects how the feature functions within the integration.