Skip to main content
goweb
Contributor I
August 7, 2019

Alarm not working on Google Assistant

  • August 7, 2019
  • 42 replies
  • 6542 views
Alarms don't seem to be set through Google Assistant.

Steps to reproduce:

  1. "Hey Google, set an alarm for xxx"
  2. Google responds that alarm is set
  3. "Hey Google, what alarms do I have set?"
  4. Google responds that no alarms have been set
    This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

    42 replies

    Show previous replies
    Bob1
    Lyricist I
    September 9, 2019
    I have a google home mini and the alarm function works just fine. The function used to work on my Sonos One, it stopped working a few weeks ago. I removed the Google Assistant option from the Sonos One as recommended by the Sonos trouble shooting guide, rebooted and reinstalled the Google Assistant. Same problem, no change. Really seems like a Sonos problem, would be nice if someone from Sonos would acknowledge the problem and label this a "known issue" which they are working to resolve.
      Skoven
      Lyricist I
      September 10, 2019
      Seems like the newest update solved the problem... hurra 🙂
      Bob1
      Lyricist I
      September 11, 2019
      Two steps forward ... yes, the alarm function is now working but when you ask google if there are any alarms set it says “the alarm is set for x:xx time with a snooze for x:xx time.” The alarm time is correct, the snooze time is something new. I sense another update coming soon.
        Ditsy
        Enthusiast I
        September 12, 2019
        Ours worked initially, then some time back ceased working. As others report, it now verifies that it's understood the command, leading you to assume the alarm is indeed set. The alarm never goes off, and any subsequent queries reveal that it has no knowledge of a set alarm. When the alarms were working we had to use "Ok Google, stop", whereas Google Nest devices will cancel an alarm with just "stop".

        We've had to resort to using Google Nest devices in other rooms to set alarms. It's a great shame, we've been very happy with the Beam, but if they can't get the Google Assistant integration resolved, we won't be buying anything else.
          obiekt0
          Lyricist I
          September 16, 2019
          Same here,
          any alarm I set seems to be set for 5 am snoozed until xx (actual alarm). Then the alarm rings and snooze function is not available. I ask google assistant to snooze, it responds correctly, yet the alarm sound still goes off. If I use the command stop after I ask it to snooze it just deletes the alarm. Sonos get on in please as I don’t even trust these alarms anymore.
            Elizabeth_3
            Contributor I
            November 22, 2019

            “Hey google, set an alarm for 6:15 AM on weekdays”  Google confirms

            “Hey google, what are my alarms?”

            ...”You have an alarm set for 2:15 PM snoozed until 6:15 AM”

            6:15 AM alarm goes off.

            “Hey google, what are my alarms?”

            ...”You have an alarm snoozed until 10:15 PM” (WTF?!!)

            10:15 PM goes off (waking me up as I’m trying to go to sleep)

            At this point, I cancel all alarms and start over. I have no idea if 6:15 on the next weekday would go off.

            **

            Google won’t support this issue; they tell me to contact SONOS support

            After the runaround, SONOS claims they don’t support this issue either.

            I have several google minis around the house and they set alarms normally.

            I’ve gone back to setting my alarm with Alexa until I decide whether to purchase another google mini for the bedroom

              tomythomson
              tomythomson
              Lyricist II
              December 8, 2019

              Same here,
              any alarm I set seems to be set for 5 am snoozed until xx (actual alarm). Then the alarm rings and snooze function is not available. I ask google assistant to snooze, it responds correctly, yet the alarm sound still goes off. If I use the command stop after I ask it to snooze it just deletes the alarm. Sonos get on in please as I don’t even trust these alarms anymore.

              I’m noticing the same thing. Bizarre. I’m not sure if GA on Sonos is reliable enough to be my main alarm. Seems too buggy. 

                tomythomson
                tomythomson
                Lyricist II
                December 12, 2019

                I was awoken at 4am today by the GA alarm on my One. The alarm was supposed to go off at 9am. Sonos needs to fix this alarm problem now. This is ridiculous and if they don’t fix this I will not be buying anymore Sonos speakers and will instead buy Google Nest speakers. 

                jphogan1
                Lyricist I
                January 13, 2020

                Just chiming in to say I have the same issue. I have an alarm set for 7:43am every weekday (when my son needs to leave for school). The Sonos one has the “alarm set for 7:43am, snoozed until 1:43am” and I can’t undo it. 

                ry bread
                Contributor I
                June 20, 2020

                just want to say i’m also experiencing this very weird bug on my sonos one.

                 

                “hey google, set my alarm for 7 AM"

                 

                “got it. alarm set for 7 AM"

                 

                “hey google, what alarms do i have set?"

                 

                “you have one alarm set for 2 PM, snoozed until 7 AM."

                 

                this seems to be some kind of glitch on sonos’s side, because my other google home products can set alarms normally. unfortunately i haven't been able to find a fix; i’ve tried disconnecting & reconnecting the speaker to google home & google assistant, manually setting the time in google assistant’s settings, changing the name of my room in google home, even clearing my history on google assistant… the issue persists.

                 

                Show more replies
                Terms & ConditionsAccessibility statement