Add cover entity #38894
Closed
Add cover entity #38894
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
📝 WalkthroughWalkthroughThis update introduces multiple new integrations and expands documentation across several Home Assistant components. It adds new configuration options, updates entity support, clarifies setup and troubleshooting procedures, and enhances YAML schemas for various integrations and dashboard cards. Several new integration metadata files are included, while some documentation files are removed or replaced. The changes also standardize terminology and add new device/platform support in existing integrations. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant HomeAssistant
participant ZimiCloudConnect
participant ZimiDevices
User->>HomeAssistant: Initiate Zimi integration setup
HomeAssistant->>ZimiCloudConnect: Discover Zimi Cloud Connect devices
alt One device found
ZimiCloudConnect-->>HomeAssistant: Return device info
HomeAssistant->>User: Auto-configure integration
else Multiple devices found
ZimiCloudConnect-->>HomeAssistant: Return device list
HomeAssistant->>User: Prompt user to select device
User->>HomeAssistant: Select device
else Discovery fails
HomeAssistant->>User: Prompt for manual IP/port entry
User->>HomeAssistant: Enter IP/port
end
HomeAssistant->>ZimiCloudConnect: Connect and retrieve device list
ZimiCloudConnect-->>HomeAssistant: Return connected Zimi devices
HomeAssistant->>ZimiDevices: Map Zimi device types to Home Assistant entities
Note right of HomeAssistant: Entities created for lights, covers, switches, fans, outlets, etc.
ZimiCloudConnect-->>HomeAssistant: Send real-time updates
HomeAssistant->>User: Display/control Zimi devices in UI
sequenceDiagram
participant User
participant HomeAssistant
participant ESPHomeDevice
User->>HomeAssistant: Add/reconfigure ESPHome device
HomeAssistant->>ESPHomeDevice: Attempt connection
alt Name conflict detected
HomeAssistant->>User: Trigger Name Conflict Resolution
User->>HomeAssistant: Choose "Migrate" or "Overwrite"
alt Migrate
HomeAssistant->>ESPHomeDevice: Transfer config, preserve history
else Overwrite
HomeAssistant->>ESPHomeDevice: Replace config, erase history
end
else No conflict
HomeAssistant->>ESPHomeDevice: Complete setup/reconfiguration
end
HomeAssistant->>User: Device available in Home Assistant
sequenceDiagram
participant User
participant HomeAssistant
participant ntfyService
User->>HomeAssistant: Configure ntfy integration (URL, credentials, topics)
HomeAssistant->>ntfyService: Register/validate topic(s)
HomeAssistant->>User: Create notify entities for each topic
User->>HomeAssistant: Send notification via notify service
HomeAssistant->>ntfyService: Publish message to topic
ntfyService-->>User: Deliver notification to devices
sequenceDiagram
participant User
participant HomeAssistant
participant S3Service
User->>HomeAssistant: Configure S3 backup integration (credentials, bucket, endpoint)
HomeAssistant->>S3Service: Validate credentials and bucket
HomeAssistant->>User: Confirm S3 backup location
HomeAssistant->>S3Service: Upload backup files as scheduled
S3Service-->>HomeAssistant: Confirm upload success
sequenceDiagram
participant User
participant HomeAssistant
participant MCPServer
User->>HomeAssistant: Configure MCP integration (host, protocol, OAuth credentials)
HomeAssistant->>MCPServer: Authenticate via OAuth (if required)
MCPServer-->>HomeAssistant: Provide access token
HomeAssistant->>MCPServer: Establish connection (SSE or stdio)
MCPServer-->>HomeAssistant: Stream data/events
HomeAssistant->>User: Display/control MCP devices
sequenceDiagram
participant User
participant HomeAssistant
participant HomeConnectIntegration
participant Appliance
User->>HomeAssistant: Add Home Connect family integration (e.g., Balay, Gaggenau)
HomeAssistant->>HomeConnectIntegration: Register new brand/domain
HomeConnectIntegration->>Appliance: Discover/control appliance
Appliance-->>HomeConnectIntegration: Report status/events
HomeConnectIntegration-->>HomeAssistant: Update entities
HomeAssistant->>User: Show appliance status in UI
sequenceDiagram
participant User
participant HomeAssistant
participant ZimiCloudConnect
User->>HomeAssistant: Change device/entity name in Zimi app
ZimiCloudConnect-->>HomeAssistant: No automatic update (requires restart)
User->>HomeAssistant: Restart Home Assistant
HomeAssistant->>ZimiCloudConnect: Refresh device/entity names
HomeAssistant->>User: Display updated names
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
❌ Deploy Preview for home-assistant-docs failed.
|
|
It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the |
|
Wrong branch |
|
the build failure was not your fault. it's an error I introduced elsewhere, see #38896. The indent was wrong there. So, if this PR has a related parent in core, |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.Summary by CodeRabbit
New Features
Documentation
Bug Fixes
Chores