#Hi guys iam new at hass and atm a little
1 messages Β· Page 1 of 1 (latest)
You'll want to share the automation - which you can find in automations.yaml - if you want us to have any chance of helping π
Please use a code share site to share code or logs, for example:
- http://pastie.org/ (select YAML for the language)
- https://dpaste.org/ (select YAML for the language)
- https://paste.debian.net/ (you guessed it, select YAML as the language)
Please don't use Pastebin, since it can randomly add spaces to the main view. Please also don't share text as images since it makes it harder for people to help you. Remember that others may have colour blindness, impaired vision, etc.
Why use the sun elevation trigger or condition rather than a time offset from sunset or sunrise? Because the elevation more consistently relates to the light level than a fixed time offset. An hour before sunset is very different light levels on the longest day than the shortest day, for example.
Change
mode: single
``` to
```yaml
mode: restart
thats all? π
Yes
okay fine, i will test it. π How can i add a condition, that check if the light is on? When my wife turn on the light manually, the automation should check that.
Well, the state condition would be that the light is off
Just add it to your condition block
- condition: state
entity_id: switch.shelly_1_spots_haustur
state: 'off'
Of course, that'll then break the turning off 
You'll need a second automation, and an input_boolean
dont forget, iam new at this π
ill add this...
So... I'd use https://www.home-assistant.io/integrations/template#trigger-based-template-binary-sensors-buttons-numbers-selects-and-sensors to create an entity that's turned on when the sensor reports motion
thats the pro league π
template:
- trigger:
- platform: event
event_type: doorbird_doordbird_bewegung_haustΓΌr
binary_sensor:
- name: "motion"
state: 'on'
auto_off: 10
That's a template sensor - it goes in configuration.yaml
Then you end up with
https://dpaste.org/LKWrc
https://dpaste.org/AdoDQ
https://dpaste.org/u6ESW
The first one turns the switch on when motion is detected, and turns on a boolean to show that it turned the light on
The second turns it off when motion hasn't been detected for 30 seconds and the light was turned on by the first automation
The third turns off the boolean whenever the switch turns off
fixed it. π
okay, it didnt work
When i start manually the "doorbird_doordbird_bewegung_haustΓΌr" event, the lights dont switch to on.
ahh forget to restart...
Okay, the "on" automation works, but the "off" doesnt...
Does the binary sensor turn off?
what you mean with binary sensor? the light (shelly) is on
The automations I provided use that created entity to work
I don't know whether you followed what I provided, or did something different, as you didn't say either way
ah okay.. forget that - where can i see if the sensor is on?
show your state developer tools
okay, the sensor is off
and it turns on? You're using the automations I wrote, or are you doing something else?
no i use all 3 from you
it didnt turn the light off
And the boolean... you created it?
Or did you skip right over input_boolean.create_me
Did you know that integration?
https://www.home-assistant.io/integrations/vallox/
At the Moment, i switch the profils manually. But for the future they should switch profils when iphones are at home or away. Did i need here two automations? One for coming home and one for leaving? How can i add conditions, based on when one person (iphone) is leaving and one stays at home (profil should stay on "home")? Here is the yaml code for the testversion... https://dpaste.org/yJqXY
When i should ask this in the main channel, let me know. π
You probably want to ask in the main automations channel so that others see the new question
with the share of yaml?
Yup