-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rank-automation.yaml doesn't work #34
Comments
I noticed same thing. Always goes to else. |
I've been running the code I've suggested above for a week now – works like a charm. |
Even with these changes get always if condition false. |
There should be no magic that it works for me flawlessly and doesn't work for you at all... Here's the full updated file I'm using, you can try it out: |
Only rank works with this, but not price. Needs some debugging. |
Both rank and price work for me, but there's another issue with this.
"Run" # 1 gets executed and naturally goes to the One fast solution which works with added limitation is setting the trigger to ignore state change to
With this fix in place only events 3 and 4 from above result in script triggering, with # 3 going through all conditions and performing as expected and # 4 getting terminated. Interestingly, event 5 also disappeared with this fix. Other option I see is modifying the
This particular code doesn't work and I'm not sure what am I missing here. |
Why this is not still fixed? I fought with this problem many hours and now I found this thread. |
Remember the price is in euros. So for example 4.4c is 0.044 € |
For me the automation works, but it only when I trigger it manually. |
I'm curious whether I'm doing something wrong, but the rank-automation.yaml doesn't work for me at all.
The automation I've created form that blueprint doesn't ever get triggered automatically and when triggered manually always results in
else
clause being executed.Having spent a full day on it, I found the root cause: those input_variables are not accessible inside the
value_template
of thetrigger
despite the fact they're defined astrigger_variables
(which in theory should work fine). I've tried pretty much all the approaches suggested at https://community.home-assistant.io and I just couldn't find a way to make those variables available.The only solution I've found was moving all the if-else logic into the
action
section, subsequently changing thetrigger
to just rank & price state changes and and also changingtrigger_variables
tovariables
. That way all the variables are nicely available and automation works as expected:The text was updated successfully, but these errors were encountered: