I have Daikin split heat pump units and the temperature setting on them bear no relation to reality. What I would like to do is have the temperature sensor in my now unconnected (but still alive) Ecobee wall thermostat to give instructions to the two Daikins to either provide more heat or not. I think the way to do this is to change the heat setting on the Daikins to 75 F when we need heat an 60 F when we don’t. Making this work is beyond me.
Any ideas or help?
TIA
Paddy
Hi there. The logic is simple and it can be effiecently done witha single automation. But before we get into automation building, we should integrate both these components into HA. Both these components have official integrations but it also depends on the model. Have to integrated them?
Yes, they are both integrated, though the Daikins seem to be showing up as a sensor.
We need Dalkin as a climate component to control the heating operations. Please check if there is any climate entity also. If not we have to try other integrations which supports your heat pump.
It isn’t in the UI, but does show up under entity as climate.lr_daikin.
We dont need it in UI. The entity we are looking for is climate.lr_daikin. Now we want to test if everything is working fine with this entity. For that we are going to check if we can change the temperature of this entity. Go to Developer tab and then services. In the services tab select climate.set_temperature and then select the entity climate.lr_daikin.
In the service data tab paste this temperature: 75
Then call service and see if the temperature of the device changes.
Yes! That works.
Now its simple. We have to create an automation. For that you have to decide what should be the target temperature of the ecobee sensor below which the heat pump should be turned on and when it should turn off. Also share the entity_id of the ecobee sensor and the state of it.
Thank you so much for your help. The ecobee is climate.home It is no longer hooked up to the heating system so is now just a sensor. There are two Daikin units: climate.lr_daikin and climate.kitchen_ac
Between 5:00 am and 9:00 pm, when temp on the Ecobee is 68 F, I’d like the Daikins to be set to 72 F, and when it’s 69 or above, the Daikins should be at 55 F. From 9:00 pm to 5:00 am, the Daikins can stay at 55 F, regardless of the Ecobee reading. Does that make sense? Paddy
I have made an automation but we may have to tweak it a bit. Just try it.
alias: Temperature Control
description: ''
mode: single
trigger:
- platform: state
entity_id: climate.home
attribute: current_temperature
- platform: time
at: '21:01:30'
condition: []
action:
- choose:
- conditions:
- condition: and
conditions:
- condition: time
after: '05:00:00'
before: '21:00:00'
- condition: template
value_template: >-
{{state_attr('climate.home', 'current_temperature') | float >=
69}}
sequence:
- service: climate.set_temperature
data:
temperature: 55
entity_id: 'climate.lr_daikin,climate.kitchen_ac'
- conditions:
- condition: and
conditions:
- condition: time
after: '05:00:00'
before: '21:00:00'
- condition: template
value_template: >-
{{state_attr('climate.home', 'current_temperature') | float <=
68}}
sequence:
- service: climate.set_temperature
data:
temperature: 75
entity_id: 'climate.lr_daikin,climate.kitchen_ac'
- conditions:
- condition: time
after: '21:01:00'
before: '21:02:00'
sequence:
- service: climate.set_temperature
data:
temperature: 55
entity_id: 'climate.lr_daikin,climate.kitchen_ac'
default: []
If you are not familar with adding this to you HA, please see this gif.
Okay, it’s loaded and I hit execute. My reading is that nothing is really supposed to happen until 21:01:30 tonight. Right?
If the thermostats are already set to the correct temperature in relation to the ecobee, you wont have any change of temperatures with the thermostats. And at 21:01:30 if the thermostats are not set at 55, then it will be set. The automations is triggered with any change of ecobee sensor.
Please make sure that your ecobee sensor has a current_temperature state attribute.
Go to the developer console and in the states tab check what it the state of the sensor.home_temperature and also climate.home. Then share a screen shot. We can tweak the automation accordingly.
The fist code will work but since you have a particular temperature sensor, we can tweak it like this.
alias: Temperature Control
description: ''
mode: single
trigger:
- platform: state
entity_id: sensor.home_temperature
- platform: time
at: '21:01:30'
condition: []
action:
- choose:
- conditions:
- condition: and
conditions:
- condition: time
after: '05:00:00'
before: '21:00:00'
- condition: template
value_template: >-
{{ states('sensor.home_temperature') | float >=
69}}
sequence:
- service: climate.set_temperature
data:
temperature: 55
entity_id: 'climate.lr_daikin,climate.kitchen_ac'
- conditions:
- condition: and
conditions:
- condition: time
after: '05:00:00'
before: '21:00:00'
- condition: template
value_template: >-
{{ states('sensor.home_temperature')| float <=
68}}
sequence:
- service: climate.set_temperature
data:
temperature: 75
entity_id: 'climate.lr_daikin,climate.kitchen_ac'
- conditions:
- condition: time
after: '21:01:00'
before: '21:02:00'
sequence:
- service: climate.set_temperature
data:
temperature: 55
entity_id: 'climate.lr_daikin,climate.kitchen_ac'
default: []Ok…that came because I forgot a line in the code. sorry I have corrected it. Copy the new code and try now.
It’s run through a full cycle and works perfectly. Thank you so much for helping this noon out. I really appreciate it.
This morning, the Daikin’s thermostats were at 75F but they weren’t putting out heat. I think they need to be reminded to do that because I used the UI to turn them off and then to heat and they started right up. I was thinking about adding a command to set the mode to heat at 5:00. So I am thinking the following needs to be added, but I am not certain where. Or should it be a separate automation?:
trigger:
platform: time
at: "05:00:00"
action:
- service: climate.set_hvac_mode
data:
entity_id: 'climate.lr_daikin,climate.kitchen_ac'
hvac_mode: "heat"