Starting yet another thread on this since Google insists on closing them all.
I have a morning routine set to activate when an alarm is cancelled.
I also set the routine through another routine with the "Ask what time the alarm should be set for" with "Run the Good Morning routine after dismissing alarm on speakers" set.
Sleep sensing is active. As per many other threads, this seems to cause issues.
The routine almost never triggers. The only times it does, it stops straight away.
Leave this open so others can share that they have the issue. Every time this gets closed without the issue being fixed I will just create a new one with exactly the same text.
Thanks for reaching out. We're sorry to hear that you're experiencing this on your Google Nest Hub. Could you please tell us if this routine has worked before on your end? Also, kindly share us the similar threads so we can check on it further.
We'll be waiting for your response.
Here are a number of similar threads showing that there is a common issue:
In particular, the first link has quite a bit of discussion around sleep sensing being the cause of the issue, which may apply to me as I do have that on, and that might be when the morning routine stopped triggering.
After the alarm goes off, and I dismiss it - the screen shows as below:
If I "dismiss" it, it just turns our lights down low (possibly a particular point during "sunrise") and seems to go back to an alarm being set - saying it will wake me up in x minutes (the x seems to be random). It's as though I'm dismissing the idea of it being morning or something.
Also note that if I say "OK Google, Good Morning" after stopping the alarm, it works fine. It's only the trigger which seems to be broken (which, as I say and as per other threads, seems to be related to Sleep Sensing).
I took a few photos showing there is very obviously at least one bug, but to be honest it seems like there's more than 1:
Before the alarm goes off (at 8am), there is a synchronisation issue between the current time and the alarm:
It's apparently waking me up in 3 minutes, but should be in 2.
When the alarm actually goes off, at 8, it seems to have two things going off. The actual 8am alarm, and another sunrise finishing in 1 minute. The only alarm that should be set is the 8am alarm which was set by the Good night routine.
When I stop the alarm with voice control, it goes to this:
If I leave it, nothing happens. If I hit dismiss, the bedroom lights go back to minimum brightness (having correctly woken up during the "sunrise" period - note they first turn on at exactly 7:30 expected - not 7:31 as might be expected based on the first screenshot), and then it shows this:
If I leave it, this happens:
The exact process isn't always entirely consistent. But one thing that's consistent is that the Good Morning routine does not run.
I have found a possible cause (and therefore realistic but not ideal workaround).
We changed our alarm time today - and the good morning routine actually worked. We happen to have a reminder at the same time as the usual alarm. So it might be that a combination of sleep tracking, and a simultaneous alarm and reminder triggers the problem.
I will test over the coming days and see if it's consistent.
THIS IS NOT SOLVED - DO NOT CLOSE. Please read
But it seems it's working for us following a change of situation. When it was NOT working, we had the following combination:
- An alarm set on the Nest Hub 2nd Generation
- A "gentle wake up" on 2 Philips Hue BT bulbs, controlled from the Hub
- Having "gentle wake up" on also seemed to turn on the sunrise alarm on the Hub itself
- A reminder at the same time as the alarm
This combination seemed to be what caused the problem, and the morning routine could not successfully complete.
We moved the reminder, and that allowed the morning routine to run.
We then changed our lighting setup, and there is no longer a sunrise alarm (because of a separate issue, where Google Home cannot perform sunrise for non-Hue bulbs). Now if we set a reminder for the same time as the alarm, the routine still seems to work.
So as it happens, at the moment, it is working for us. However, this is NOT because it has been fixed. By coincidence we have a workaround which is suitable for us. I am simply providing this information for anyone else who is having a similar issue.
Keep this thread open to allow others to provide information if they are also having the issue. If you close it, I will simply copy it and create a new one. This is to ensure the purpose of the forum is maintained - which is to allow people with similar issues to discuss the issue.
Thanks for additional info. We appreciate all your efforts. We'd be happy to take a look into this for you. Please fill out this form with all the needed information then let me know once done.
I have created this thread so people can discuss the issue. It is a bug in the Hub or Google Home, so there is nothing to investigate specifically for me.
Just leave the thread open so people can contribute their experience or work arounds.
If the problem is actually fixed, or there is a GENUINE solution, I would be happy for that to be posted and then it can be closed.
If you actually read the thread, you will see that I, personally don't need help right now. It is almost always working for me.
The point of this thread now is to allow others to share their experience and for people to share knowledge about the issue and perhaps other workarounds they have found - since we all know it's unlikely that the bug will actually be fixed.
So the problem happened again yesterday - could have been a glitch. But we don't have a reminder at the same time as the alarm, and it's not controlling sunrise. So there's definitely a general issue, it's just more likely to occur if the hub is doing more things at the same time as the routine.
The problem still exists. There is no reason to close the thread. I have provided information which others may find helpful - but it is not solved, and other users may also be able to contribute. If you lock the thread now, then this is not a forum, or a community.