Group of climates state logic missing

[mouth4war]

Home Assistant release with the issue:

0.73.0.dev0

Last working Home Assistant release (if known):
0.73.0.dev0

Operating environment (Hass.io/Docker/Windows/etc.):

HASSbian
Component/platform:

group

Description of problem:
Group of climates has unknown state in states browser but in UI it shows state of first member. The logic should be shifted to state reporting of group instead of keeping it in UI.

For example, group of fans shows state in states browser and in UI (consistent).

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

[mouth4war]

Impact: Cannot view state of group of climate using service/external apps like tileboard/hadashboard. Group of climate cannot be used anywhere else but HASS UI.

[mouth4war]

It seems this is because the group component has no on/off states mapped for climate. eg. Cool/Idle, Heat/Idle

But this doesn't explain how the UI is able to show first member state instead of unknown, leading me to believe the logic is in the UI layer.

Function: _async_update_group_state

[FelixUster]

I can confirm this problem. It happends with Homematic thermostats and eq3btsmart devices, even if only one device is in the group.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[mouth4war]

Issue still exists. HASS UI allows setting temperature and mode using group of climate entities but doesn't report a state for the group.

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[dfigus]

I can confirm that this issue is still there in the current version 0.92.2,

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[jclusso]

Any update on this. Still broken in 0.104.0b4