Support entity device and area #144
Merged
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
|
Perhaps an example would help:
|
|
@daringer: Do you have an issue with this PR? I have a growing number of fixes and features I'd like to push through the pipeline, but I need to know I'm not wasting my time. |
daringer
approved these changes
Nov 19, 2024
|
oh wow - this is from september sorry! |
|
@daringer: Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #49.
Makes the entity's device name and assigned area name accessible if available. Uses the
hassobject'sentitiesproperty to locate this information. Unfortunately, not all entities are listed here for some reason. So even if an entity belongs to a device or is assigned to an area, that information may not be available, though most entities do seem to be in the list. This is mentioned in the update to the docs.