Closed cjhesse closed 3 months ago
The only problem I see with your template is that has_value
only takes one parameter, but that's not relevant to the failure.
When run_seconds
is passed via Developer tools > Services
, the keys are converted to strings, whereas when passed via the template, they are passed as integers. Since the code is expecting strings, it fails, but quietly so that all run durations are 0.
I suspect this worked in the past since the examples are written using integers, but it no longer works. However, the fix is easy--simply pass the keys as strings:
run_seconds:
'0': 60
'1': 60
'2': 60
'3': 60
'4': 60
'5': 60
I will be submitting a fix to the code so that either will work.
The only problem I see with your template is that
has_value
only takes one parameter, but that's not relevant to the failure.
That's what I get for using copy/paste...
I will be submitting a fix to the code so that either will work.
Tested the new update and my template indeed works as-is (without converting the keys to chars).
Thanks!
I'm not certain whether this is an issue with this integration, HASS, or my templating. That being said, the exact same service YAML works using the developer tools.
Here's what I have in
configuration.yaml
:When turning the switch on, nothing (apparently) happens. I didn't see any warnings or errors in the log that appeared related.
Turning the switch off does successfully stop the sprinkler when it's already running.
I tested the same "turn on" action in Developer tools > Services, and that worked: