You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: