I am working on a version with more flexible conditions, that may be helpful to you.
Thank you. Do you need some help in testing? Please let me know if I can support you in any way.
Supporting entities instead of / in addition to fixed numbers
This bug seems to be unsolved until today:
…and a workaround (confirmed working):
==> Can the blueprint (template evaluation part) not just take care of this out of the box?
Because when applying the workaround (YAML mode)…
illuminance_below: "{{ states('input_number.light_abc_threshold') | int }}"
the UI only gives this, which is way to dangerous once one forgets about that templating hack and overrides stuff using the UI this way (accidentally breaking an automation):
Original full question
A completely other question - one I’m not sure someone talked about in this 123 posts long thread already:
I was trying to use an input_number entity for (Optional) Illuminance Below. That did not work (light stayed off). Once I put in a fixed number again, the automation works again.
→ Do fields like (Optional) Illuminance Below support entities?
The blueprint itself seems to want a number in the first place:
illuminance_below:
...
default:
selector:
number:
where e. g. the (Optional) Illuminance Sensor accepts (and works perfectly) with entities:
illuminance_sensor:
...
default:
selector:
entity:
Would it work if I change the selector from number to entity? Or is this just for the UI and the functional magic is done in the complex template part?
→ Answered by myself: I was/am still using a blueprint version from 2021-04-02, where this is used - and it doesn’t work…
illuminance_below:
...
default:
selector:
entity:
domain: input_number
So you actually removed that in newer versions of the blueprint… how can one use an input_number entity for this?
Use-case:
I have a use-case where the value of that (Optional) Illuminance Below changes based on physical circumstances. The value of my input_number helper entity is automatically and dynamically adjusted, so it would be perfect for the blueprint to simply use that (instead of me needing to change that value in the automation manually).
Hello,
I have the following in mind:
My fan is supposed to come on at 8:30 a.m. When a window is opened, the fan is supposed to go off and come on again when it is closed. But all of this only happens when I’m at home. The fan should then turn off again at 5:30 p.m. until the next day.
Anyone have an idea how I can do this with the blueprint?
Thank you very much
Hi again @kevinxw , another half year has passed.
Are you able to finally implement this?
No response at all for such a long time strongly indicates this great blueprint is unmaintained / dead.