Skip to content
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

Feature request: get config from MQTT, allowing multiple cards for one entity #28

Open
decramy opened this issue Apr 28, 2023 · 0 comments

Comments

@decramy
Copy link

decramy commented Apr 28, 2023

I would like to have an overview of upcoming tasks in a dashboard and would like to use the 'auto-entities' card for that; it supports filtering and sorting to determ the entities to show. But the configuration of a task (like the timeout) could defer over multiple tasks.

Therefor I would like to hide the cards for the initial configuration in a separate dashboard, so the MQTT-topic will be generated, containing all configuration. Then, when I use the same entity again (in the main dashboard with upcoming tasks), this configuration could be gathered from MQTT and not again from Lovelace.

So; my feature request: if an entity already exists, try to get the config from MQTT. Then override this with the values given in Lovelace (like severity).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant