I have created this climate:
- name: "Riscaldamento"
unique_id: "termostato"
modes:
- "off"
- "heat"
- "cool"
mode_command_topic: "home/riscaldamento_raffrescamento/TEST/mode/set"
mode_state_topic: "home/riscaldamento_raffrescamento/TEST/mode/state"
temperature_command_topic: "home/riscaldamento_raffrescamento/TEST/temp/set"
current_temperature_topic: "home/riscaldamento_raffrescamento/TEST/temp/state"
power_command_topic: "home/riscaldamento_raffrescamento/TEST/pump/set"
payload_on: 1
payload_off: 0
min_temp: 17
max_temp: 28
temp_step: 0.1
precision: 0.1
thinking that the power_command_topic would be sent whenever the temperature would go over/under the one set, but nothing ever get send to that topic. How can I turn on the pump when the temperature goes under the one set and turn it off when it goes over?
I completely missed your reply, sorry. My system cools and heats, and I really would like to avoid addons to avoid possible brakes in future updates. Do you think that it would be possible to do it with automation? (They can finally be divided into categories!)
Instead of using a community add-on, you can create two generic thermostat. https://www.home-assistant.io/integrations/generic_thermostat/
Mmm…ok. Do you think that there is a way to hide one of them based on the season?
You can use an helper to toggle from one to another and use an automation to trigger it (or a simple switch on your dashboard).
But if I were you, I would use a community add-on as dual AC isn’t a niche, I guess it will keep being updated in future. I’ve been using some community add-on for a couple of years and none have been dropped til now.