Thanks for the quick reply. Unfortunately, that didn’t work and get this error
Invalid config for [automation]: expected float for dictionary value @ data['trigger'][0]['below']. Got None. (See /home/homeassistant/.homeassistant/configuration.yaml, line 147). Please check the docs at https://home-assistant.io/components/automation/
15:44 config.py (ERROR)
Would that work for my use-case ? I assume this will only trigger when I change the input_number. Rather, I need it to trigger when the reported humidity drops below the input_number.
Using the template binary sensor did the trick. Thanks for your help.
In the post above, where the link to how to create a binary_sensor is, the reason the template trigger did not work is because only one of the two entities used in the template was listed. Also it is comparing strings instead of first converting them to numbers. It would have worked if the entity_id line was removed and the trigger changed to:
Is there a way to combine both a hard-coded pre-defined trigger number in an automation and an input_number slider to fine-tune?
I have a number of automations for triggering a humidifier relay for growing edible mushrooms - they have different humidity parameters at different growth cycles, so I would like to add an input number slider to fine tune when I happen to be growing a different species for instance.
I have to agree with Phil, if you have a number range, set that as the input number range, then tweak the input number according to what you are growing and the stage in its growth cycle.
Though not sure why you don’t automate that as well (different cycles for different crops, started when you initialise them)
Really, that easy? I’ll implement that later then. Thanks!
…and hello again Matt! Actually, i have automated the whole thing, with the automations triggered by sensors. I just wanted to add a fine-tune tweak slider to do some minor adjustments if need be because in this case we are dealing with nature.
I couldn’t seem to find a way to add the slider with the necessary presets to the automation - as the slider is in the config.yaml. I didn’t think i could just use the same automation and add the slider too - though i still don’t understand why the trigger thresholds wouldn’t just revert back to the number hardcoded in the automation…
This way when you adjust the ‘humidity’ you are adjusting a ‘real world’ number, not (say) : -15
Minus 15 on what ??? you then have to remember the hard-coded and subtract 15, why make life hard ?