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
The sibling Comfortable Environment Card has a more direct approach when asking for the temperature and humidity sensors: it simply filters by those attributes, instead of rulling out anything that "might not be useful" (which could then cause more issues in the future, such as #393).
Is there any reason for going the long way instead of the simpler one? This still causes my setup to show a lot of irrelevant sensors on the config flow. Would there be scenarios where the temperature sensor would not be identified as such, for instance?
The text was updated successfully, but these errors were encountered:
The sibling Comfortable Environment Card has a more direct approach when asking for the temperature and humidity sensors: it simply filters by those attributes, instead of rulling out anything that "might not be useful" (which could then cause more issues in the future, such as #393).
Is there any reason for going the long way instead of the simpler one? This still causes my setup to show a lot of irrelevant sensors on the config flow. Would there be scenarios where the temperature sensor would not be identified as such, for instance?
The text was updated successfully, but these errors were encountered: