Sun State change 3 minutes after sunrise event [Solved]

Not sure as my trigonometry requires that I know the length of the hypotenuse - I don’t have a bit of string that long…

we didnt think so in 1953: North Sea flood of 1953 - Wikipedia

then again, we’ve managed now, and as a consequence fly all over the world to share our knowledge and experience, with those countries (or liars if you wish) with less inclination to solve their issues at the root…and take their money elsewhere.

Back to the issue at hand: restarting at the correct height above sea-level as we speak…

yep…

Thanks for your answer.
Setting condition in action allows to check condition even if the automation is triggered manually.
And put the condition in action is great to debug an automation without wait the event trigger :slight_smile:

I didn’t know about the default AND conditions

I configured that from the UI and nothing is set on the config file

Thanks

Thanks everybody for this good discussion :smile:

Finally I solved my issue by this condition:

- id: volets_ouverture_default
  alias: Volets Ouverture 8H/Sunrise
  trigger:
  - at: '08:00:00'
    platform: time
  - event: sunrise
    platform: sun
  action:
  - condition: time
    after: '08:00:00'
  - condition: template
    value_template: "{{ as_timestamp(state_attr('sun.sun', 'next_rising')) > as_timestamp(now().replace(hour=23, minute=59, second=59, microsecond=999999)) }}"
  [...]

If the next rising is tomorrow, sunrise is done :wink:

Thanks,

I certainly hope that the sun will rise tomorrow, I didn’t see it ‘not’ as being one of the insurance options for Marius !

sorry to bump this, but only getting back to this earlier thread because of the topic, I now see a lot of flagged posts all of a sudden.
Was this done recently, and why? Who flagged these harmless replies, now getting more attention than before.

Feels this is becoming a less free community than it should be. Not good.

4 Likes