Coder Social home page Coder Social logo

Comments (11)

dgomes avatar dgomes commented on July 25, 2024 1

I also like the idea, actually some components such as camera already have brand and model properties:

https://github.com/home-assistant/home-assistant/blob/de50d5d9c1c0375c5e46042f3168d356c73f6aa1/homeassistant/components/camera/__init__.py#L254

from architecture.

balloob avatar balloob commented on July 25, 2024

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).

from architecture.

ubnt-marc-khouri avatar ubnt-marc-khouri commented on July 25, 2024

Thanks for the feedback! I'll stay tuned for any other comments, and probably prepare a PR near the end of the week

from architecture.

fabaff avatar fabaff commented on July 25, 2024

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.

from architecture.

balloob avatar balloob commented on July 25, 2024

We should make sure to align those. Note that this property will only be used for entities with a unique id.

from architecture.

ubnt-marc-khouri avatar ubnt-marc-khouri commented on July 25, 2024

As pointed out by @dgomes , the current Camera Entity class uses brand and model, whereas my proposal is manufacturer_name and model_name.

Any strong opinions on naming? I slightly prefer manufacturer_name over brand, but I don't feel strongly about it

from architecture.

Kane610 avatar Kane610 commented on July 25, 2024

I prefer it as Zigbee does it; uses modelid and manufacturer

from architecture.

balloob avatar balloob commented on July 25, 2024

The downside of model id is that we can't just show it in the frontend.

from architecture.

Kane610 avatar Kane610 commented on July 25, 2024

@balloob I see them as the same thing

from architecture.

balloob avatar balloob commented on July 25, 2024

Interesting. I would expect id to reference an identifier, name to reference a name.

I think that we should have the names contain the source + the attribute. So I wouldn't like manufacturer, I would prefer manufacturer_name. I think for model, initially I would be interested in the model_name, not the model_id. I would want to show a list of devices in Home Assistant.

from architecture.

MartinHjelmare avatar MartinHjelmare commented on July 25, 2024

@balloob we can close this I think. It was solved with the device registry.

See #36.

from architecture.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.