Hey hey
Ive had an automation that i run when my door is locking and when its locked.
It turns on a light (outside), That flashes red for example if any window or door is opened, or bleu if my robot vacuum didnt get fresh water this day.
This works perfectly fine so far, but the problem is that light is outside.
If the light doesnt flash green (what signalisizes everything is ok) I have to unlock again and go inside again.
So I got a signal light for inside and want to add the same thing as outside inside my house.
If the door is unlocking (at a specified time) I want to have the same thing as outside.
I dont want to use this inside an automation, too. Because this would mean doubling the code for unlocking and locked.
So I think have a script is best way here.
I did create the script so far, but always turning on both lamps, which isnt exactly what I want.
If the door in UNLOCKING, I want to use the inside lamp.
If the door is LOCKING, I want to use the outside lamp (or lamps in nearer future).
So I suppose I need a field and call the script giving it the field value I can react to.
So I can keep my tests (light on test, robot vaccum test, and so on) and depending on the field value I turn the specific light on.
Am I correct with this way? Or is there any better solution?
And can someone give me a hint how to use the fields?
Since you are calling the scripts yourself, you can pass information to the script and use that in the script to choose what to do. See the section about passing variables to scripts here:
You could for instance pass the color to the script that flashes the light.
iāve switched your field to be an entity type. with a default set to light.nachtlicht_eingang_licht. so you can call this script with any light entity, and it will use that light to do your signaling.
have your automation pass in whichever light is appropriate.
Just for my understanding.
When calling the script by an automation I hand over the entity I want to shine.
This seems to be perfectly what I wanted. (will test your code this afternoon).
There is a little but:
One of the two entitties Im using in this script should flash, the other shouldnt.
Is there a way to hand this setting, too?
If this is a big deal, or would make the script unneccessary difficult, ofcourse I can live without the flashing on all lights.
the way I have done it, the entity that you pass in turn on and flash. The other light wonāt get touched. is that what you wanted? apologies if I misunderstood
or are you saying that one of the lights when it is the one chosen, should turn color and flash, and the other, when chosen, should only turn color? If this is what you mean, I would add a new field that says flash, and invoke flash if requested by the caller
I see that you call turn_on. Then turn_on with flash. Do you always have to do that as two separate calls? Your light wonāt turn on and flash in one call?
I want one light to turn on and flash and the other light to turn on without flashing.
So it would be awsome if you give me an example how to hand over the device and the flashing status to my script
I do two light.turn_on calls, because I dont think its possible to to turn on more than one light with different settings (flash and not flash) in this one call.
just noticed you had repliedā¦ when you reply, please hit the reply next to my post, not the blue button at the bottom of the thread. if you reply to my post instead of to the thread, iāll get notified and be able to respond to you fasterā¦
this automation is getting very long and unwieldy. it would be much better if you collapse a bunch of itā¦ for example, at the end of each conditoin, you do a delay and then turn off the light. you could pull those out of each individual condition and just do that after the whole condition block. you could also just determine what color you want at the beginning then call to turn the light on and maybe flash using the color.
but without doing all that re-designing of your code, hereās how you can add a field that tells it whether to flash or not. thereās a new field required called should_flash
Man! Thanks for your awsome help.
I just copied your code in my HomeAssistant and its looking exactly what I wanted.
Really really thank you!
Ofcourse Iāll redesign my code with your āmake it easierā suggestions and tell my result here.
But before I do there is another question to your code.
If we look at turning on the light in condition 1 for example.
You turn on the light, check if it should flash and call turn on again.
Im not 100% sure, but Im quit sure that using the light.turn on on a light that is turned on already is the way to change its lightning behavior (making it flash in this case).
Wouldnt it be better to use sth like this (I can code this my own - just a question of understanding):
If āshould_flashā == true
then light.turn_on - with flashing
else light.turn_on - without flashing
And if you allow I got one more request.
Im really not familiar with fields and variables in home assistant.
After your code example here and reading a bit about fields I guess I did get the basics and should be able to try and error (and google) to achieve what I want).
But Ive never used variables - what I suppose need to to get the color saved.
Can you give me an example with just a blanc script creating an ārgb_colorā variable (or field if its more usefull) and assigning it a random rgb color, so that it can be used within the light.turn_on call?
ha! this is the question i was asking YOU when i asked this:
i donāt know what lights you are using, so i figured maybe your specific lights had to be turned on first before you can turn it on to flash. i think this came about because of how i edited your code initially (i did a global replace for your light entities to the new variable)ā¦ i didnāt realize that i had introduced thisā¦ i thought it was your original code.
so take a look at thisā¦ this does the āif/then/elseā to remove to duplicate calls to light.turn_on
it also combines all the delay/turn_off to the end (this could be optimized further)
one noteā¦ of course iām not able to test all of it, so iām writing code blindā¦ i may have a typo or such, but i hope this helps you get the right idea. i have a couple other questions/optmizations for you, but iāll do that in another post
you have the lights flashing by having effect: flash, according to the documentation: Light - Home Assistant, flash is turned on by flash: slow or flash: fast but i suppose this might vary depending on what light you have. i donāt know (i donāt have any lights that do this).
you could potentially simplify the code further by replacing:
note that iām not positive if passing ānoneā in for effect will get rejected but i thought this format using template would simplify a lot if it were allowed.
warning again, this is not tested because i donāt have light entities that can change colors or flash, but hereās the general idea for you for variables:
see how this can make things much simpler for you?
important notes.
variables are defined at the top of itās scope block. no matter where you write them, they are defined at the top of their block (you can read the indent level as the block)
variables cannot be changed. so you canāt do an āifā later on and change the variable.
Really Thanks for your great explanation and tipps!
This is far too complicated (atleast for me as a beginner for now), to do it while im working.
Ill take a deep look into this at the weekend, where I can try and google without having people interrupting me.
To the two light.turn_ons.
In my original script, I always turn on BOTH lights.
The INSIDE lamp should NOT FLASH.
The OUTSIDE lamp should FLASH.
This is the reason for the two calls. There is no need to turn my light on and change settings then.
coolā¦ holler if u have questionsā¦thereās a lot to be said for being satisfied with just having something that worksā¦ but also some best learning in trying to optimize. if u are interested in the fun and learning, donāt be shy about experimenting and asking questions here. lots of us are happy to helpā¦ especially helping people who are curious and want to learn. cheers!