OK, sorry I wasn’t able to help.
No worries! That’s what these forums are all about. You helped me A TON! Much appreciated.
Jeff
Binary sensor… that’s the key that unlocks it and triggers the automation based on state change. Nothing else worked.
binary_sensor:
- platform: template
sensors:
bs_stove_error:
friendly_name: "BS Stove Error"
value_template: >-
{{ float( states('sensor.esph_house_stove_current_temp') , 0) <= float(states('sensor.esph_house_stove_set_temp') , 0)-4 }}
Automation:
platform: state
entity_id: binary_sensor.bs_stove_error
to: "on"
Finally!
Makes sense, binary_sensors are best for off/on things,
Glad it worked out!
It actually was syntax errors as to why the others didnt trigger… 2 really little things.. I guess its a lesson to us all that the really little things matter. A LOT.
I can see it now - that sneaky little " maybe from when you changed from a single line template to multi-line? …and the capitalisation as well, yep.
Well done on finding it all and most importantly, glad it is working!