Agreed. 100% need to deal with that first.
Thanks to all for brainstorming on my problem.
When I say unreliable I mean the Integration gets offline which I suppose is because it reached an API request limit on Honeywell side (I put an automatin to reload after 5min and it often comes back).
I have to dig the Dual Thermstat coupled with switch templates to turn on or off each HVAC. Not sure it’s simpler than my automation.
I had already made a decoupling automation but I wanted it to be more, I mean that wathever thermostat you use to set the target temp, I wanted the according device (Heat or AC) to turn on and do it’s job (while the other is turned off).
Sorry for the delay guys, but I have two limits, one the place is occupied so I can’t play with the thermostat while guest are in, second I have an API request limit on the Honeywell side.
My Node Red automation which is an eclusive On switch works well, I’m digging into the dual thermostat now…
If I understood correctly you may control cooling and heating with the same thermostat. Commercial thermostats that handle underfloor heating and cooling do it, its a common a feature, using the same relay of course.
The heat pumps with underfloor heating and cooling are quite frequent in Spain.
Commercial Thermostats have the option to invert the output for cooling.
To summarize:
- In general for heating almost all thermoestats use a Normaly Open mode.
- However for cooling the mode should be Normaly Closed
Lets say the target temperature is 20 degrees in cooling mode, and the current temperature is 25, the output would be closing the relay hence activating the valve.
This behaviour could be implemented theoretically at the code without hardware changes or recabling?
Vartkat, I have the exact same situation as you. Did you ever come up with a solution? Would you share your node red automation?
@Kernelg Sorry but not really, I’m hitting two problems with the Honeywell API, first is a delay which is not always the same, the other is the API limit.
I thought of replacing the two thermostat with a fake one made on a Sonoff NS Panel, letting people think they’re managing everything while automations would do the real job behind teh scenes with high and low tem limits, but never did it.
If ever you want to investigate, the best way I found is the Dual Thermostat integration.
You have to first create a bunch of templates (sensors and switches) that will be part of the Dual Thermostat.
In my case
sensor:
- platform: template
sensors:
ac3_current_temp:
friendly_name: "AC3 Current temp"
value_template: "{{ state_attr('climate.ac_cabin_3', 'current_temperature') }}"
unit_of_measurement: "°F"
Which is the current temp from one thermostat to be used as current temp for the dual one.
Then you have to create switches to make service calls to the real thermostats :
switch:
- platform: template
switches:
ac3_switch:
friendly_name: "AC3_Switch"
unique_id: '0a7476cc-d6c1-40cb-8ae1-60651752497f'
# value_template: "{{ states.climate.ac_cabin_3.state }}"
turn_on:
- service: climate.set_hvac_mode
target:
entity_id: climate.ac_cabin_3
data:
hvac_mode: cool
# temperature: >
# {{ state_attr("climate.dualtemp_cab3", "target_temp_low") }}
- delay: '00:00:02'
- service: climate.set_temperature
target:
entity_id: climate.ac_cabin_3
data:
# hvac_mode: cool
temperature: >
{{ state_attr("climate.dualtemp_cab3", "target_temp_low") }}
turn_off:
service: climate.turn_off
target:
entity_id: climate.ac_cabin_3
- platform: template
switches:
heat3_switch:
friendly_name: "Heat3_Switch"
unique_id: '0a7476cc-d6c1-40ba-8ae1-60651752497f'
# value_template: "{{ states.climate.heat_cab_3.state }}" # le state heat ou cool n'est pas interprété comme on, pas genant mais on peut améliorer
turn_on:
- service: climate.set_hvac_mode
target:
entity_id: climate.heat_cab_3
data:
hvac_mode: heat
# temperature: >
# {{ state_attr("climate.dualtemp_cab3", "target_temp_high") }}
- delay: '00:00:02'
- service: climate.set_temperature
target:
entity_id: climate.heat_cab_3
data:
# hvac_mode: heat
temperature: >
{{ state_attr("climate.dualtemp_cab3", "target_temp_high") }}
turn_off:
service: climate.turn_off
target:
entity_id: climate.heat_cab_3
as far as I remember I commented the part which were not working for me, but you should adjust for your case, this is just to give you the idea.
Then and finally you can create your dual thermostat :
climate:
- platform: dual_smart_thermostat
name: DualTemp_Cab3
heater: switch.heat3_switch
cooler: switch.ac3_switch
target_sensor: sensor.ac3_current_temp
heat_cool_mode: true
cold_tolerance: 0.5
hot_tolerance: 0.5
precision: 1
# floor_sensor: sensor.floor_temp
# max_floor_temp: 28
# openings:
# - binary_sensor.lumi_magnet_opening_cab3
# timeout: 00:00:30
min_temp: 65
max_temp: 80
ac_mode: false
target_temp: 68
# target_temp_high: 26
# target_temp_low: 23
#cold_tolerance: 0.3
#hot_tolerance: 0
min_cycle_duration:
seconds: 5
keep_alive:
minutes: 3
initial_hvac_mode: "off" # hvac mode will reset to this value after restart
away: # this preset will be available for all hvac modes
temperature: 68
target_temp_low: 65
target_temp_high: 70
# home: # this preset will be available only for heat or cool hvac mode
# temperature: 21
# precision: 0.1
# target_temp_step: 0.5
That’s the rough idea, it works but we don’t use it cause we still have to do three things
1- Hide the real thermostats and replace by a real temp sensor
2- Replace one of them with a Broadlink IR cause the one piloting the AC is IR emeter and if it’s hidden it can no more send commands to the unit…
3- Put a tablet or a Xiaomi Smart Clock as thermostat with a custom dashboard with the dual thermostat
Hope this helps