Document websocket api to get triggers/conditions/services for target

[abmantis]

Proposed change

SSIA.

Type of change

• Document existing features within Home Assistant
• Document new or changing features for which there is an existing pull request elsewhere
• Spelling or grammatical corrections, or rewording for improved clarity
• Changes to the backend of this documentation
• Remove stale or deprecated documentation

Checklist

• I have read and followed the documentation guidelines.
• I have verified that my changes render correctly in the documentation.

Additional information

• This PR fixes or closes issue: fixes #
• Link to relevant existing code or pull request: Add get_triggers_for_target websocket command core#156778

Summary by CodeRabbit

• Documentation
  • Added WebSocket API docs for extracting triggers, conditions, and services for a target. Covers supported target parameters, optional group expansion (including changed default expansion behavior), standardized identifier response format, error handling, and example requests/responses.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new documentation subsection "Get triggers/conditions/services for target" under "Extract from target", documenting three WebSocket commands—get_triggers_for_target, get_conditions_for_target, and get_services_for_target—that accept a target structure (entity_id, device_id, area_id, label_id) with an optional expand_group flag (default true). Describes input/output formats, group expansion semantics, examples, and error handling.

Changes

Cohort / File(s)

Summary

WebSocket API Documentation docs/api/websocket.md

Adds new "Get triggers/conditions/services for target" subsection under "Extract from target". Documents three commands (get_triggers_for_target, get_conditions_for_target, get_services_for_target), the target input structure (entity_id, device_id, area_id, label_id), the optional expand_group flag (default true), response format (domain.trigger_name identifiers or analogous formats), examples for requests/responses, group-expansion behavior, and error handling notes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Verify documentation accuracy against the actual command implementations.
• Confirm example requests/responses and default expand_group semantics match the code.
• Check formatting and style consistency with adjacent WebSocket API docs.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete. The 'Proposed change' section contains only 'SSIA' (which means 'same subject as issue/already said'); the checklist items are unchecked; and while it references a related PR, it lacks substantive explanation of the changes.	Expand the 'Proposed change' section with a clear explanation of what was documented and why. Check the appropriate checklist items and provide details about what was verified or followed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: documenting websocket API commands for retrieving triggers, conditions, and services for a target.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch get_triggers_for_target

---

📜 Recent 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 2dcbb22 and dc6400a.

📒 Files selected for processing (1)

• docs/api/websocket.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/api/websocket.md

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}