gaunt urchin
is there an integration which lets me create custom climate entities from a template file?
i found this one: https://github.com/jcwillox/hass-template-climate but its super outdated and even the newest fork dose not work...
my issue is, that i have a water_heater entity which is currently not supported by the temperature card or the PV-optimizer script which is why i need to convert my water_heater to a climate entity
gaunt urchin
gaunt urchin
- climate:
name: "aquamqtt_climate"
unique_id: "aquamqtt_climate"
temperature_unit: C
min_temp: 43
max_temp: 60
temp_step: 1
# Current water temperature
current_temperature_topic: "aquamqtt/main/waterTemp"
current_temperature_template: "{{ value | float }}"
# Target temperature (read)
temperature_state_topic: "aquamqtt/hmi/waterTempTarget"
temperature_state_template: "{{ value | float }}"
# Target temperature (set)
temperature_command_topic: "aquamqtt/ctrl/waterTempTarget"
temperature_command_template: "{{ value | float }}"
# Only use standard HVAC modes
mode_state_topic: "aquamqtt/hmi/operationMode"
mode_state_template: >
{% set map = {
'MAN ECO OFF': 'off',
'AUTO': 'auto',
'MAN ECO ON': 'heat'
} %}
{{ map.get(value, 'auto') }}
mode_command_topic: "aquamqtt/ctrl/operationMode"
mode_command_template: >
{% set map = {
'off': 'MAN ECO OFF',
'auto': 'AUTO',
'heat': 'MAN ECO ON'
} %}
{{ map.get(value, 'AUTO') }}
modes:
- "off"
- "auto"
- "heat"
# Preset modes (must match device payloads exactly)
preset_mode_state_topic: "aquamqtt/hmi/operationMode"
preset_mode_command_topic: "aquamqtt/ctrl/operationMode"
preset_modes:
- "BOOST"
- "ABSENCE"
# Availability
availability_topic: "aquamqtt/stats/lwlState"
payload_available: "ONLINE"
payload_not_available: "OFFLINE"
thats how i solved it idk if there is a better way but i just used MQTT-Explorer to find the values i wanted to change or use (while having the program open change the values to get them in there its not showing all possible values and some are updated verry rarely) and then plugged them into the mqtt.yaml which is an !include to my configuration.yaml
starts with an "- " because i have other entities configured there if you dont have that your format might differ!
