Hello. I have recently moved from Homebridge to Home Assistant because one lightbulb stopped playing ball and I’m well impressed with what HA can do. But, I have an issue that I cannot resolve. On HB I set the triggers for heating as an any temp change so it constantly checked the conditions. It worked very well and never had issues. But with HA I can get the heating on by using the same type of trigger but not off. Most of the answers online are not what I am looking for as it’s a single temperature based trigger which doesn’t really work all of the time. I have two triggers in the one automation. One for on and one for off as I saw this in an online tutorial. The logic behind the triggers must be sound as it’s coming on. I would greatly appreciate any help. Below is the YAML of the automation
alias: Office Heating Full Day
description: “”
trigger:
platform: state
entity_id:
sensor.office_motion_sensor_temperature
id: Office-heat-on
alias: Office On Trigger
from: null
to: null
platform: state
entity_id:
sensor.office_motion_sensor_temperature
from: null
to: null
id: Office-heat-off
alias: Office off Trigger
condition:
condition: time
after: “08:05:00”
before: “17:00:00”
weekday:
mon
tue
wed
thu
fri
condition: zone
entity_id: device_tracker.marc_iphone_2
zone: zone.home
action:
I think you should use 2 triggers:
sensor.office_motion_sensor_temperature above 16
sensor.office_motion_sensor_temperature below 18
and choose you actions based on that.
And then in the choices you can add your conditions again
This will also prevent the unneccesary triggering on every temperature change
Your automation would simply enable/disable the Generic Thermostat at the appropriate time (i.e. only on weekdays between 8:05 and 17:00 when you are home). The Generic Thermostat is responsible for maintaining the temperature at the desired setpoint. It’s represented by a climate entity so it can (optionally) be displayed in the UI using a Thermostat card.
Hi all,
If anyone is looking for an answer to the same issue this is the solution that I came up with. It has worked flawlessly for about 3 weeks and it keeps it neat. I basically have different options depending on the time of day. So a heating run in the am. Heating run at lunchtime etc etc. It does trigger about 6 times per hour but that’s acceptable if it works. If HA started to neaten up it’s automations I would perhaps write something for each time. For now that would be incredibly messy.
It’s triggered every time the value of sensor.dining_temperature changes.
If you used the Generic Thermostat integration, the automation that would control it would be more concise, easier to maintain, and more flexible than what you posted above.
The Generic Thermostat integration produces a climate entity whose sole responsibility is to maintain a target temperature. The automation’s task is to control the climate entity’s operation based on your preferences such as occupancy, schedule, etc. You could optionally use the Schedule integration to specify operating hours.
Your reply got me thinking if I also should be using the generic thermostat and how to nest additional functions inside the automation.
I have an automation already working that cools or heats at certain times using the scheduler. But when the temp is reached the AC fan stays on (without cooling or heating). From what I gather this is normal AC behavior. But I would rather have the AC turn off when the temp is within range. Reason for this is that in my climate it can be days, weeks or even months between operations. All that time the AC will create a draft with its fan and use electricity.
I’ve been playing with Generic Thermostats and scheduler. The Scheduler is an amazing tool and works well. The same can’t be said for the generic thermostats. I’m not sure what in the hell I’m doing wrong but when I set the temperature in the config/yaml it’s blindly ignored and does whatever it wants. Whilst I set it at 18 on some mornings it comes on at 25C. No idea why either. It’s always wrong, just different every time. Maybe it doesn’t work with Tado as I have them working successfully on 3 oil filled electric heaters.
I have kept the thermostats in play and the automation now triggers a scene based on the schedule I set. This way I can specifiy the exact temperature I want and it just works.
The only reason I have kept the GT as it’s useful for adjusting the temperature after the automation has triggered. Or if you want a quick blast in between schedules.
In the next week I will create an video that explains the entire process for anyone else that has had this convoluted process keep them up a night. For the past week my heating has works perfectly using automation, schedules and scenes so feel I can offer something to newbies like me who just want something simple.
If anyone else is having issues with Tado and Generic Thermostat this is the solution I have found works well. I’m guessing they are just don’t work together.
Good morning @Perla
i am trying out your code and i am also having a midea unit, but i dont get the options for min and max temp and so on…
in your code it states the max and min and how does your scheduler look like?
Just standard time x on and time y off?
Thx alot, cause i would love to use this ac in a way that she turns on and off as needed and not staying on the hole time blowing air…
button to format your yaml code, so we can read it properly 
