This repository has been archived by the owner on Sep 14, 2023. It is now read-only.
New device and entity architecture #8
Closed
Conversation
This file contains 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
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.
This draft tracks the new changes planned for the entity and device architecture that is meant to simply the process of integrating new components and entities.
The goal is to refactor the current system for creating entities using a unified approach where each homee node is represented using a device in Home Assistant and can "produce" multiple entities among multiple components.
Additionally, the current way of choosing the "right" entity/entities for each node should be refactored to rely less on the
NodeProfilebut instead move to an approach that is primarily based on the available node attributes.This change will be the foundation for integrating new components (#2, #3)