Generic Thermostat Improvements

I’d like to add a couple of features/changes to the generic thermostat component.

  1. Keep Alive - my A/C unit has the thermostats incorporated into its remote controls, and depends on IR packets from the remotes to know when to turn on and off, based on temperature. This works with the generic thermostat. However, the A/C unit automatically shuts off if it doesn’t receive an IR packet from the remote for a while, which can happen when reaching the target temperature takes a long time. I suggest an optional keep-alive field in the generic thermostat configuration. When configured, it will automatically send the switch.on or switch.off signals (depending on whether the A/C is supposed to keep working or to stay in standby mode) at the defined interval.
  2. Add option to change the operation mode. Currently, the only way to switch from heating to cooling and back (that I found, at least), is via the ac_mode configuration field, and thus requires a configuration change. If you’re lucky, you’ll only have to do that twice a year :slight_smile: But, since the other thermostat components have this functionality, why not add it to the generic thermostat, as well? I believe a switch between heating and cooling in the frontend will be great.

What do you think?

Hi there,

I’m using the generic thermostat to implement multi-zone climate control but a restriction from the generic thermostat is that you can’t have the ‘same’ thermostat to be able to control heating/cooling/fan.

Currently you’d need ‘2’ to achieve that for a single zone. (one each for heating and cooling). Fan/Auto is not possible.
If you add the ability to select Off/Heating/Cooling/Fan/Auto that would give more more ability to do some cool stuff and not need to duplicate items.

Should be a trivial change.
You could either use the default ‘climate’ range or allow the user to enter their own list.

Hi, any update on this?
I really miss an option to switch between heating and cooling mode on the frontend. I am using Lovelace Thermostat card.
Thanks

Sorry, I haven’t worked on this for a while… I don’t know when I’ll have the time to add that feature.

No problem, it is getting warmer now, so I just checked if there is an update on this. Thanks in advance.
I will come back in November :smiley:

The current climate (generic_thermostat at least) seems to want to act as a thermostat to turn off & on heating or cooling when the room temp drifts out of range.
Inverter air-cons do not function this way … you set them at a specific temperature and them turn them on!

All it needs is:

  • power switch (on / off)
  • target temp setting (with a max and min that it can output), an optional current temp would be great to.
  • The target temp steps should be able to be set … e.g. some support adjustments in 0.5 degree increments (most in 1 degree).

Additional options should be able to be set (not specifying should mean it doesn’t support this feature) but not required for eg:

  • fan speed (integer with min / max & auto)
  • louvre horiz (on / off)
  • louvre vert (on / off)
  • eco mode (on / off)
  • mode (cooling / heating / auto)

edit after 123 Taras comment:

Hello,

I have an air conditionner heat pump “Daikin” which is composed of two AC units in my house.
Both AC units is “reversible” that means it can heat or cool.

The problem with Generic Thermostat is that I need to use two of them in order to manage one single physical unit…

Would it be possible to implement one or both of the following:

  • The most logical: Generic Thermostat Integration support for heating AND cooling mode in one single thermostat (with away temp for each heat and cool mode.
  • Maybe easier and faster: Having the following Climate Control Service: climate.set_away_temp in order to be able to dynamically set the away temp of a thermostat. So if using a custom component (for example zacs Dual Mode Generic Thermostat: GitHub - zacs/ha-dualmodegeneric: Generic thermostat capable of heating and cooling), I can set the away_temp dynamically and avoid changing it manually and need to reboot the server.

Thanks

You appear to be asking for two different things:

  1. Allow the Generic Thermostat integration to support heating and cooling modes.
  2. Allow the custom integration created by “Zacs” to set away_temp.

The second request concerns a custom integration so it should be posted in Zac’s GitHub repository.

I have edited my post that wasn’t clear. Thanks @123

I used climate (MQTT) with my HVAC system to communicate to the HVAC via MQTT .
Currently, the climate only allows you change heating or cooling temperature settings but not both . However, my HVAC system has active settings for both heating and cooling. Many recent HVAC systems do. Right now, I have to toggle between cooling and heating and change the target temperature. It would be nice if we could set both thru climate.
Also, maybe add support for two stage systems (low/high for cooling/heat). Display and control the stages?