Add metadata support for genericmiot #1618
Open
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 PR is continuation for #1581 and improves genericmiot by adding support for defining metadata (e.g., description, icon) for miotspec entities.
The idea behind this PR is to have consolidated descriptions, icons, etc. for standard properties, actions, and settings no matter what is defined in the the miotspec file.
At the moment the following metadata can be defined:
The structure for metadata files is:
Example definition (namespace defined one level higher and thus not shown here):
The screenshot below shows what a simulated
dreame.vacuum.p2009
looks like in homeassistant (compare to the one in #1581).miiocli status
output showing also items in Chinese that have no metadata defined: