Damn… I of cause saw those docs. But mis-spelling “number” is a new kind of idiotic fault of mine. Thank you for helping me out. It works of cause now…
I’ve tried a few variants of this (both with and without the float but I seem to get a float error every time), also tried setting the step to simply increment in the card, but that didn’t work (I need step to remain as 1 generally)
Even ignoring the +10 and just trying to grab the value this fails…
I also tried this example over in the link and that failed too
{% set state = states('sensor.temperature') %}{{ state | float + 1 if is_number(state) else "invalid temperature" }}
I’m sure I’m missing something obvious, but I’m stuck
I get the same error. Trying to choose an input number instead of a value but it doesn’t help. I have some tv02 thermostats here where I can set a specific boost time. I want to enter a number in the dashboard i.e. 100 and than the thermostat should boost for 100 seconds. This is my automation:
Device actions do not support templates. They have other problems too. Stop using them (and device triggers and conditions). In this case use the set value service instead.
I have been fighting with HA for hours trying to set an entity to a value of an input helper where the UNHELPFUL error message kept asking for a float. I’d almost given up when I found this.
This type of of inconsistency in HA is what makes me want to throw it all in the bin. HA needs to fully commit one way or the other. All in with templating or not. I don’t care about “The year of the Voice Assistant”. I care about not wasting several hours due to inconsistent interface and unhelpful error messages.