8000 supported_features Vs current_supported_features · Issue #1 · home-assistant/architecture · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
supported_features Vs current_supported_features #1
Closed
@lucasweb78

Description

@lucasweb78

Currently Entity exposes supported_features that has become overloaded to mean both:

  • all of the entities supported features
  • the current set of supported features based on the entities state

The second use case breaks Alexa Discovery which relies on supported_features to discover all of the capabilities of an entity not just the ones that are available in it's current state.

One proposal from @balloob is to use supported_features as the list of all features and introduce a new current_supported_features that will reflect the features available at the current time base on the players state.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0