@kwint That’s what I use it for. If your light supports transition. You can add a service call ligth.turn_on with transition time to the actions.
Add Action → Call Service → Light: turn on → Select your Target → Select Transition (set a time) → select Brightness (target brightness)
When I make a new automation the alarm which is already sets works. But when I change the alarm the steps in the automation change.
If I look at the trace timeline it says: “Triggered by the state of sensor.tel_ruben_next_alarm at December 22, 2023 at 15:42:42” and suddenly only chooses option 1 therefore not executing the sequence.
sorry, not sure if I understand your question/problem. Sorry. But the blueprint/automation has two triggers. One, when the alarm is being set/changed (changes the helper) and the time condition (actual alarm, with the configures actions)
Thank you for this blueprint, it is exactly what I was looking for.
But I still have a question of understanding:
If I create several automations with the blueprint, do I need a separate helper for each automation or can the automations share one helper?
It was working for a while, but since a few days ago I have an issue: the first alarm fails to trigger anything, and only the subsequent snoozes work.
But even weirder: it works fine when I use an alarm in the middle of the day; only the morning one fails
There should be something happening at 8:42(alarm at 8:45 with 180s offset) but there is nothing.
It is simply not triggering
NOTE: the logs contain a test around 15:48 to confirm it indeed works sometimes/in the middle of the day.
Also I originally thought there could be an issue with the fact that I use a “long running” script as action (Sunrise Simulator Manual) but that does not seem to be an issue (and it worked for a while anyway).
I have in fact the same problem. In my oppion there is a design failure at the blueprint.
My alarm is set automatically to the next event on the next day at the same time.
Actions are starting with an offset of -60 and if I turn off the alarm the automation is already running. Trigger for a new alarm is starting but cannot run while the automation is already running.
I’v set the automation in mode parallel. In this way it is working but it isn’t the best solution.
Would be awesome to have also an offset (+) for the new next_alarm trigger. Or something else.
Sorry, I don’t really understand the problem.
If you could maybe list a timeline (Setting the alarm, Snoozing, state of the helper, state of the automation). It may be that your alarm app is different and therefore behaves different than mine.
I usually have 3 alarm clocks set. 5 seconds before the alarm clock triggers actions - turning on the light or raising the blinds (depending on the sun level) and starting the alarm clock on the nest speaker with a one minute delay.
This one-minute delay means that when the phone alarm clock starts after 5 seconds and the automation wants to set the time of the next alarm clock it does not happen because the automation is already running.
I know that getting rid of the delay will solve the problem but I’m looking for a way to trigger some of the action also after the alarm clock, not just before. To be honest, raising the blinds/ turning on the light would also suit me better after the alarm clock than 5 seconds before.
After update to Google alarm App (7.10 (685617841)) yesterday my automations based on this blueprint no longer triggers the intender funktions, i had this problem on android 13 but on android 14 it have been rock solid the last year.
it seems when i look at automation traces that it “chooses” option 1 or 2 But “my” actions is run on option 3 but there is no “choose” options 1 or 2 in the blueprint.
so i think that it maybe some “internal” functions of the blueprint
Hi @Stephan0815, sorry for the late reply.
under conditions, add Entity and then state, you can try with a schedule helper or calendar entity. And it’s state.
hi @martinelv, I just checked my Google alarm version, i am on the exact same version as you are and I even created a new alarm which worked just fine. Things you can check
Is your entity helper input_datetime.xxxxx updated? If not check if the sensor in the HA app is enabled
Check if your actions run on it’s on, test them in another automation
I noticed one thing, which I need to monitor. That when the alarm has run, it hasn’t update to the next day. But I am not sure when this actually happens. That’s a thing the alarm app does and the home assistant app then updates. Let me montitor this the next few days.
I rebooted my phone after and also checked the companion app and enabled and disabled some other app in the allowed list.
i made a copy of the my automation with the blueprint and changed the actions to something “testable” and also changed it to the “newish” feature “Take control”
and made a lot of tests last night and discoveret that the automations “both” original and copy also triggers when is change an alarm on the phone i did not know that.
Most of the times Both automations triggered but some times the original with the blueprint didn’t update the last time “run time” when but looking in the traces the both triggede.
but it worked this morning so i will monitor it the followings days and keep you updated
Thanks.
I have now “monitored” the automation for sometime and in the last about 17 days it have failed me 4 times since google released the update to the “alarm app”
every time it fails the automation trace is saying that the automation takes “option1” but it seems that “option1” is something in the blueprint and not my “actions”
it failed these times
1= 31 okt
2= 4 Nov
3= 6 Nov
4= 10 Nov
but it seems random so i have not been able to find the root course other than
the google app update. and before i updated to android 14 i was the same “instability”
but after upgrading to android 14 and before the new google time update it was rock solid.
