Franck Nijhof
Franck Nijhof
> The related architecture discussion can be solved by frontend simply picking MAC(s) from the device entry and displaying that. I'm confused by this comment @emontnemery, so your are saying...
Marked this PR as draft, as it depends on #71051
> see the smash label - not sure if I should feel fear or excitement Neither :)
I'm kinda lost on why we do this? (Motivation? SSIA doesn't help in this case). As in, EntityDescription are pretty much limited to their basic, descriptive, properties, not to their...
> We already use the descriptions for many different kind of attributes in the implementing integrations. Yeah sure, they can extend it they way they like.
👍 Will be getting back to this after the beta stuff is out.
> That is the reason why I didn't implement current_option which gets adjusted throughout the life of the entity. Sure, but it can provide a default. When setting the entity...
I've seen you've applied `current_option` already, but I would love to hear the opinion of @MartinHjelmare on this as well. > I have added it because it was requested, but...
> Conversely however, I think only static attributes should have corresponding properties in the description. In that case, this PR is invalid, as `options` doesn't have to be static...
Thanks, @epenet 👍