Home Assistant: HVAC entity

[wlcrs]

Following the native HA-integration of john30, I adapted the configuration of my MQTT HVAC entity as follows:

climate:
  - platform: mqtt
    name: CV
    max_temp: 25
    min_temp: 15
    precision: 0.1
    temp_step: 0.5

    action_topic: "ebusd/bai/Status01"
    action_template: "{{ (value_json['5'].value == 'on') | iif('heating', 'idle') }}"
    modes:
      - auto
      - heat
      - cool
      - "off"
    mode_state_template: >-
      {% set mode_values = { 'auto':'auto', 'on':'heat',  'night':'cool', 'summer':'off'} %}
      {{ mode_values[value_json['0'].value] | default('off') }}
    mode_state_topic: "ebusd/35000/Hc1OPMode"
    mode_command_template: >-
      {% set values = { 'auto':'auto', 'heat':'on',  'cool':'night', 'off':'summer'} %}
      {{ values[value] | default('auto') }}
    mode_command_topic: "ebusd/35000/Hc1OPMode/set"
    value_template: "{{ value_json.temp1.value }}"
    temperature_state_topic: "ebusd/35000/DisplayedHc1RoomTempDesired"
    temperature_low_state_topic: "ebusd/35000/Hc1NightTemp"
    temperature_high_state_topic: "ebusd/35000/Hc1DayTemp"

    temperature_low_command_topic: "ebusd/35000/Hc1NightTemp/set"
    temperature_high_command_topic: "ebusd/35000/Hc1DayTemp/set"
    current_temperature_topic: "ebusd/35000/DisplayedRoomTemp"
    current_temperature_template: "{{ value_json.temp.value }}"

This results in the following entity becoming available in the Lovelace interface:

Note that I abuse the HA thermostat slightly by setting the night temperature as "low temperature" in this entity. Normally you only set the "low temperature" if you have a device that can both heat and cool your place to keep it within the stated temperature range.

[pepsonEL]

Hi
I created thermostat as you for my heating but no working. Nothing show....

- platform: mqtt
  name: Parter podłogówka
  max_temp: 30
  min_temp: 5
  precision: 0.1
  temp_step: 0.5
  modes:
    - auto
    - heat
    - cool
    - "off"
  mode_state_template: >-
    {% set mode_values = { 'auto':'auto', 'day':'heat',  'night':'cool', 'off':'off'} %}
    {{ mode_values[value_json['0'].value] | default('off') }}
  mode_state_topic: "ebusd/700/z2OpMode"
  mode_command_template: >-
    {% set values = { 'auto':'auto', 'heat':'day',  'cool':'night', 'off':'off'} %}
    {{ values[value] | default('auto') }}
  mode_command_topic: "ebusd/700/z2OpMode/set"
  value_template: "{{ value_json.temp1.value }}"
  temperature_state_topic: "ebusd/700/z2ActualRoomTempDesired"
  temperature_low_state_topic: "ebusd/700/z2NightTemp"
  temperature_high_state_topic: "ebusd/700/z2DayTemp"
  temperature_low_command_topic: "ebusd/700/z2NightTemp/set"
  temperature_high_command_topic: "ebusd/700/z2DayTemp/set"
  current_temperature_topic: "ebusd/700/z2RoomTemp"
  current_temperature_template: "{{ value_json.temp.value }}"

I dont know why... maybe anybody can help me please.

[Koky05]

Try MQTT explorer and check what values you get into MQTT.

[KoksaJanosch]

problem solved? I have the same problem, btw I receive values through MQTT explorer.

[Koky05]

@KoksaJanosch can you post data hierarchy which you see in MQTT Explorer?

[KoksaJanosch]

Sure, here it is:)

[Koky05]

@KoksaJanosch I wrote you on FB messanger. It will be faster and in our language.

[eiabea]

@wlcrs thank you for the config, this got my mode setting to work. I had a hard time debugging the json objects. Unfortunately the temperature setting only shows 1 circle which always snaps back to 0

PS: Sorry for heating up such an old discussion

[eiabea]

Never mind, i had the min_temp set to i higher value than my heater published over mqtt 😒