Climate Group Helper

Feature Requests
, ,
10

Thank you - I actually played around with this a bit, and figured out It was Mushroom card (I already have HACS).

11

hi, how did you assigned for example “climate.radiator1” and “climate.radiator2” to the “climate.downstairs_radiators” entity? I’m sorry for my possible stupid question, but as a newbie I can’t find a way out for this… Thank you in advance!

12

Like this

climate:
  - platform: climate_group
    name: "Downstairs Radiators"
    temperature_unit: C # default to celsius, 'C' or 'F'
    entities:
      - climate.den_thermostat_z2m
      - climate.kitchen_thermostat
      - climate.dining_room_thermostat
      - climate.living_room_thermostat

Put that in a configuration.yaml

And reload HA

2 Likes
14

Thank you, did find my way out!

15

I know this is old, but I stumbled over it.

So everybody seems to be quite happy with how the custom integration handles it (set all group members to the selected option). It is not ideal for a house-wide groups because you might want have different options there, but the main use is to connect two radiators in one room, which works quite fine.

16

I also stumbled on it. Couldn’t find another way to combine climate entities. Seems to work fine for now.
Hopefully we’ll get a helper function in the future.

17

As of 2024.1, the HACS climate.group integration no longer works. (Dev stated on Git that he no longer maintains the code).

Therefore users with the need to group no longer have a work around.

Please upvote this feature request to allow this much needed functionality to be implemented.

Thanks :slight_smile:

2 Likes
18

using file editor, change the following lines to use new constants names in /custom_components/climate_group/climate.py:

SUPPORT_FLAGS = (
    ClimateEntityFeature.TARGET_TEMPERATURE | ClimateEntityFeature.TARGET_TEMPERATURE_RANGE | ClimateEntityFeature.PRESET_MODE | ClimateEntityFeature.SWING_MODE | ClimateEntityFeature.FAN_MODE
)


# HVAC Action priority
HVAC_ACTIONS = [
    HVACAction.HEATING,
    HVACAction.COOLING,
    HVACAction.DRYING,
    HVACAction.FAN,
    HVACAction.IDLE,
    HVACAction.OFF,
    None,
]

change also line 319:

        for hvac_mode in HVAC_MODES[1:] + [HVACMode.OFF]:
4 Likes
19

That did the trick! Thanks so much, @erpayo

20

I have put some thought into how to tackle the challenge that @tom_l identifies in which groups of climate entities can be both cooling and heating.

I believe that semantically a radiator thermostat is such a fundamentally different type of device (from e.g. an aircon thermostat) that it should warrant a seperate entity type all together.

If that is not a viable option, a solution that, when climate groups are created, limits functionality of the group/entity to the lowest denominator could work as an alternative. E.g. a thermostat with only heating should then exclusively enable a heating state and disable e.g. cooling.

I’m no dev-dude, so if this is actually doable - I have no idea :man_shrugging:

Anyone got any other ideas that might give us climate groups? :slight_smile:

21

That solved it! - Thanks!

May be do a fork with the correction?

24

Beta 1.0.0-rc of the custom component climate group is already available and for me, it solves the problem. People on GitHub already discussing it.

25

I can’t commit to mantain a repo, but there are a pair of forks with the changes needed for 2024.1.0

1 Like
26

There are some forks on GIT hub solving the problem with 2024.1. IMHO it would be a good idea to put them together in a main stream.

The best way would be integrating ‘climate groups’ in HASS directly as requested by https://github.com/home-assistant/core/pull/77737, but @daenny stopped workinb on this. Thanks to @deanny for this addon, which seems to be a good base!
May be one of the authors of the working forks can do the job - I would appreciate it.

1 Like
27

I upvoted this request too. Climate groups is a must have imo

Thanks !

2 Likes
28

This apparently no longer works properly (HA-Ver.2024.06.02). The temperature settings do not work properly, the thermostats are not synchronized (Z2M - thermostats from Nedis, which can be integrated and controlled individually very well…)
There is nothing useful or understandable to be found as to how this could be done - one room, several radiators, all synchronized settings - what is so exotic about it is incomprehensible…why can’t you group thermostat valves in such a way that it is easy to do even for people without a doctorate in rocket science…

29

Hi @heangel

You should be able to get it to work with this fork (available in HACS)

30

Thanks @carlhye … I’ll try it - in the meantime I did changings in the “original” as described in Climate Group Helper - #17 by TX9G9qBxid from erpayo - the temperature can now be controlled for the group from one thermostat card for the whole group…

31

There is still no “official” way (without Hacs) of doing it right? Or did I miss something?

1 Like
32

No, not to my knowledge…