Skip to content

Add eve brand #38326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 2, 2025
Merged

Add eve brand #38326

merged 2 commits into from
Apr 2, 2025

Conversation

joostlek
Copy link
Member

@joostlek joostlek commented Apr 2, 2025

Proposed change

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).
  • 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 Eve brand core#142067
  • 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 new integration for Eve Matter devices within Home Assistant, enabling seamless local operation and instant status updates.
    • Included comprehensive device information with links for further details.

@joostlek joostlek added this to the 2025.4 milestone Apr 2, 2025
@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo next This PR goes into the next branch labels Apr 2, 2025
Copy link

netlify bot commented Apr 2, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 67d8d16
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/67ed1b12ace5b1000837b369
😎 Deploy Preview https://deploy-preview-38326--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@joostlek joostlek marked this pull request as ready for review April 2, 2025 11:09
Copy link
Contributor

coderabbitai bot commented Apr 2, 2025

📝 Walkthrough

Walkthrough

A new documentation file for the Eve integration has been added. The file details how Eve Matter devices connect and operate locally within the Home Assistant ecosystem. It includes metadata about the integration such as title, description, release version, IoT class, category, domain, integration type, supported platforms, IoT standard, and brand status. The document also lists and links to various supported Eve devices.

Changes

File(s) Change Summary
source/_integrations/eve.markdown Added new documentation for the Eve integration. The file outlines metadata and describes the local operation and control of Eve Matter devices within Home Assistant.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HA as Home Assistant
    participant Eve as Eve Integration
    participant Device as Eve Matter Device

    User->>HA: Issue control command
    HA->>Eve: Forward command to Eve integration
    Eve->>Device: Send command locally
    Device-->>Eve: Return status update
    Eve-->>HA: Relay update
    HA->>User: Display updated status
Loading

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between aa6edc6 and 67d8d16.

📒 Files selected for processing (1)
  • source/_integrations/eve.markdown (1 hunks)
🔇 Additional comments (5)
source/_integrations/eve.markdown (5)

1-16: Metadata Header is Well-Structured

The YAML front matter includes all the required fields for the Eve integration. The metadata (e.g., title, description, release version, IoT class, platforms, etc.) is consistent with Home Assistant documentation standards.


18-21: Clear Introduction and Integration Overview

The introductory content concisely explains Eve as a manufacturer of Matter products and outlines the local connectivity benefits. The explanation of how Eve Matter devices integrate with Home Assistant is clear and informative.


22-23: Template Directive Verification

The templating directive {% my add_matter_device badge domain=page.ha_domain %} is correctly placed and appears to follow the expected syntax for including a Matter device badge.


24-25: Proper Link to Additional Documentation

The link to "Learn more about Matter in Home Assistant." is correctly formatted. Please double-check after merging that the target URL resolves correctly.


26-37: Comprehensive Supported Devices List

The bullet list of supported devices is well-defined and each device entry is linked directly to its respective product page. This detailed list provides users with clear guidance on available devices under the Eve integration.


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
🪧 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 plan to trigger planning for file edits and PR creation.
  • @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.

@github-project-automation github-project-automation bot moved this from Todo to Approved in Documentation PRs Apr 2, 2025
@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Apr 2, 2025
@frenck frenck merged commit 773ff8a into home-assistant:next Apr 2, 2025
7 checks passed
@home-assistant home-assistant bot removed the parent-merged The parent PR has been merged already label Apr 2, 2025
@github-project-automation github-project-automation bot moved this from Approved to Done in Documentation PRs Apr 2, 2025
@joostlek joostlek deleted the eve branch April 2, 2025 12:23
@frenck frenck added the cherry-picked This PR has been manually picked and merged into the current branch label Apr 2, 2025
frenck pushed a commit that referenced this pull request Apr 2, 2025
@frenck frenck mentioned this pull request Apr 2, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Apr 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cherry-picked This PR has been manually picked and merged into the current branch has-parent This PR has a parent PR in a other repo next This PR goes into the next branch
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants