-
Notifications
You must be signed in to change notification settings - Fork 101
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
RFC: Device manufacturer / model reporting #26
Comments
I like this idea a lot . We won't pollute the state machine with it. I think the entity registry is an excellent place to change this as it won't ever change (contrary to say, firmware version). |
Thanks for the feedback! I'll stay tuned for any other comments, and probably prepare a PR near the end of the week |
I like it too. Having additional details at hand can help to debug issues. I'm thinking about the TP-Link switch support that broke with new firmware or the no-name/relabeled devices from Asia which belong to family of identical devices which are just sold under different names. |
I also like the idea, actually some components such as camera already have brand and model properties: |
We should make sure to align those. Note that this property will only be used for entities with a unique id. |
As pointed out by @dgomes , the current Camera Entity class uses Any strong opinions on naming? I slightly prefer |
I prefer it as Zigbee does it; uses modelid and manufacturer |
The downside of model id is that we can't just show it in the frontend. |
@balloob I see them as the same thing |
Interesting. I would expect I think that we should have the names contain the source + the attribute. So I wouldn't like |
Goal
Report device manufacturer and model in a standardized way, accessible to other components and the frontend. For example, allow showing whether a Sonos player is a
Play:1
vsPlaybar
. Many components/platforms already have this info, but either report it in state_attributes, or not at all.Proposal
Entity
to include amanufacturer_name
andmodel_name
property (similar tounique_id
)The text was updated successfully, but these errors were encountered: