Combine whatever entities like sensor, number, sellect,.. in to a climate entity

Feature Requests
1

I am looking for a way to combine entities that come from a esphome device like a sensor, a number (to set target temperature), a sellect (to set mode) in to a climate to be used in HA like any other climate. kind of like climate in modbus that is setup in config.yaml and combines addresses into a climate entity so that by using the thermostat card everything gets updated. To be clear it is not another thermostat that drives a switch or service to make the heater go on or off that i want. just a climate that can pass on and update the values target temperature, mode towards other entities. All of that in a simple way so that a simple farmer like me can use and understand.

2

So you want a thermostat that isn’t a thermostat?

:thinking:

3

That seems to be the main problem that everyone assumes that a thermostat in HA switching a output entity is the solution. there are thermostat devices out there that use modbus to comunicate but that control the temperature safely on their own. Ok there is the modbus climate in HA, perfect exept if the modbus device is not connected via modbus to HA but connected to an esp32 board running esphome that has the measured temperature as a sensor id, the target temperature as a number id and the mode as a sellect id how will you make a thermostat card where these id’s are updated bidirectional, because it is possible to change the set temperature on the modbus thermostat device.
a thermostat / climate that uses a sensor entity and switches a switch entity is nice untill at the exact moment the thermostat needs to switch off the heater and there is a interuption in the network comunication you end up with a swimming pool at 35°C in the morning.

4

Ok I think I understand. Why can’t you connect via modbus?

Also please open ESPhome feature requests here:

Edit: Also you could probably use this:

And just supply delays for the actions.

5

I’m not sure it is really relevant but take a look here:

6

Surely Generic thermostat - Home Assistant

7

The heater/Cooler switch is a required option and they do not want to control anything. Sure you could use an input boolean but they sounded like they wanted to use ESPHome and the generic thermostat in that (bang bang) is easier to bluff into thinking it is controlling something.

8

Absolute overkill. All they want to do is to be able to set a set-point and display current temperature on a thermostat control.

9

Yeah I read it again. So they just want to see a picture of a thermostat?

10

Yeah. And be able to set the set point and have the current temperature update. But all the control is handled by the device.

11

English is not my language so I may have misinterpreted the OP but it states:

That bidirectional means to me that he wants to control the thing from HA and in the meantime he wants to see the states in HA if something is changed on the device/pool/spa/whatever.

I agree with him on the necessity of having a fully functional regulation independent from HA for everything that’s not really trivial/superfluous. My HA is solid enough but my home must “survive” a botched upgrade as an example.

12

If it is just adding a climate interface on to what could be seen as an existing working climate system made out of loose components, I think this would fit the bill:

It is what is strangely missing from HA because we have template cover, fan, etc, but not a template climate entity. Generic thermostat is not a template entity in the same sense, because it actually takes control of a switch and does not allow you to template the set point.

13

Please read what they said:

So as I said above all they need to do is use the bang bang climate component with delays instead of actions (which are required options).

That way they get a thermostat that they can change the set point of and it will display the current temperature. It just won’t do anything. The actual modbus device takes care of that.

Everyone else is just complaining matters with unnecessary third party integrations.

14

Sorry for the late reply. So, there is a lot of how to, maybe, use this,that. fine.but the main thing is nobody seems to understand the concept of a simple climate in ESPHOME (not in HA ) where i have a esp32 board that is comunicating to a “thermostat” device over a ttl uart TX/RX line that carries the modbus protocol. here in esphome i can create a number for the temperature setpoint, i can create a sensor for the measured temperature but there is no climate platform in ESPHOME where i can use that number as setpiont. Also i know i can do this with a modbus tcp/rs232 gateway or whatever that puts the modbus data on the modbus tcp and use climate in HA what works great by the way. but that is not usefull here because i also need other values from the “thermostat” device to use on the esp32board in ESPHOME to control other “things”. my question is how can we create a climate platform “modbus” in ESPHOME that works just like in HA where in ‘modbus’ you can create 'climates ’ and assign the modbus address as climate sensor and assing an address as target_temp_register.
and @ Tom_I, “Everyone else is just complaining matters with unnecessary third party integrations.” isnt that what homeassistant and esphome is all about? not the complaining but the try to.

15

I think @tom_l meant “complicating”.

16

Tom, about the bang bang climate component where do i find documentation for using delays instead of actions? Where exactly does my number/ address for target temperature fit in this solution?
i have tryed to abuse this:

climate:
  - platform: daikin_brc
    name: "AC"
    id: tempcontrol
    sensor: modbus_temp
    use_fahrenheit: false
    on_control:
      - delay: 5sec
      - number.set:
          id: modbus_rly3set
          value: !lambda |-        
            return id(tempcontrol).target_temperature;

but the target temperature (set temperature is not bidirectional, if i change the set temperature on the modbus thermostat device itself the target temperature does not change according to what was set on the device.

And sorry again for thinking i was on the ESPHOME forum :see_no_evil:

17

:see_no_evil: this forum is full of smart people and smart solutions.in the end we all get smarter in complicating things.

1 Like
18

since this is the HA forum the main thing is it works by using modbus but we fail to use entities from esphome devices to create this kind of climate entity.
this “template climate device”, thanks Edwin_D, could be a good solution but it is by no means bidirectional, if we change the set temperature on the actual thermostat device HA climate control is not updated.

19

I saw something maybe usefull in the beta release for this month: a thermostat helper, wait and see

20

The “thermostat helper” is the Generic Thermostat integration. Instead of configuring it in YAML you’ll be able to use the UI. Either way, it’s the same integration as what nickrout suggested 21 days ago.

1 Like