Lights on mini constantly pulsing

[richardtc007]

Over the past 2 weeks I've noticed that the Google Home Minis  (5 of them) throughout my house frequently have four pulsing white lights. This is not the result of someone saying anything remotely close to "Hey Google" or "Ok Google" and it is not the result of an errant broadcast. 

I've noticed that it even happens when I'm the only one home and haven't said a word.

I've done the whole unplug and reset routine. Why are they all suddenly listening???

[Dan_A]

Hi JayDeeDaz,

I'm jumping in to ensure everything is good here. Have you seen @davidking’s response? Let us know of the answers so we could take a closer look at them.

Best,

Dan

[JayDeeDaz]

No it hasn't worked. I've removed and reseated power on them all, but they're still flashing.

[LovelyM]

Hey JayDeeDaz, 

If you haven't already, please try to factory reset one of your Google Home or Nest speakers and set it up as a new device again. Check if that resolves the issue or not. 

Cheers, 
Lovely

[GoHawks1225]

I did a factory reset on one of my minis second gen and it did not fix the problem. 

[korpx]

Factory resets doesn't work. This is a firmware bug.

Factory reset and unlugged all Google devices. After the third Nest mini is plugged in and configured the broadcast functionality breaks.

[GoHawks1225]

This works momentarily! 

[robinwillems]

I'm having the same problem since a week or so. Same problem on all my devices (3x mini).
Looks like it's been triggered by broadcast (we use that a lot) and never stops listening or so.
Saying He Google, Stop. stops the blinking/breathing for a while.

Edit: Just found topic https://www.googlenestcommunity.com/t5/Speakers-and-Displays/Google-mini-lights-flashing-after-a-bro...
Seems like my problem... maybe yours too? @JayDeeDaz 

Did not try a factory reset yet.

[JayDeeDaz]

Hi @robinwillems , yes we use broadcast a lot too, really good to know. Just annoying!

Thanks for replying!

[Muddi]

Hello JayDeeDaz,

Just an added question: have you noticed the lights after broadcasting? Is continued conversation enabled on your device?

Cheers,

Muddi

[JayDeeDaz]

Hi @Muddi 

Yes it's turned on - but I thought it should only be on for seven seconds?

[Muddi]

Hi JayDeeDaz,

Got it! To cover all bases here, please try to disable the continued conversation first to see if your device will have the same behavior.

Keep us posted.

Cheers,

Muddi

[GlassFamily]

Mine was not turned on and it was still doing it. 

[FreeThink4Peace]

The issue is clearly not continued conversation. Google Nest is aware of the issue and is working on it.

[Muddi]

Hey there,

I just wanted to follow up on this. Let us know if you still need help, and glad to further assist you.

Cheers,

Muddi

[Juni]

Hello there,

Just checking in to make sure that you saw our responses. I'll be locking this thread if we don't hear back from you again in 24 hours. Should that happen, feel free to create a new one if you have more questions or have other concerns in the future.

Best,

Juni

[JayDeeDaz]

Apologies!

Found a "workaround" - I've had to disable Continued Conversation. Not great, as that was a selling point!

[JayDeeDaz]

Not only this, but I've today had to return my new Nest Wifi Pro units due to extremely slow wireless speeds, and the little green dot that appears on the screen after using Assistant on the Chromecast with Google TV isn't disappearing until I reboot.

All eggs in one basket springs to mind 😔

[robinwillems]

How do you do that? I cannot find it on the Dutch version. 

[JayDeeDaz]

In the Google Home app:

- Open Settings (bottom right)

- Under the "Home features" heading, select "Google Assistant"

- Click the "Manage all Assistant settings" button

- You should find Continued Conversation in there, and untick "Shared devices"

[robinwillems]

Ok great found it, I think, and unticked it. Thank you!

[Muddi]

Hey everyone,

I appreciate all your efforts, and thanks to @JayDeeDaz for providing steps on how to disable the continued conversation. I've duplicated this thread to a similar trending issue. We need help in gathering more feedback, please follow the instructions from the "Recommended answer" for the team to investigate the issue further.

Cheers,
Muddi

[GlassFamily]

Did not work

[Duncan68]

Hi all

About two months ago we had to reboot whole 'Home' after V.Media went down.

Since then when we use 'Broadcast' it is no longer our voices, but Google's and also the lights on all out Mini's continue to pulse left to right (white) until we tell the unit to stop.

We have done resets and reboots but the same thing continues. Has something changed in settings, or could it just be time to upgrade our Mini's?

Thanks.

[GlassFamily]

Looks like it has something to do with Google itself. We cannot fix it. 
They may be working on a solution

[Muddi]

Hey folks,

Thanks for bringing this up. I know the feeling when something strange is happening on your Google Home or Nest devices. Since we're getting similar reports, I'll go ahead and merge this thread with the main one so everyone will be updated on the progress of the issue. Please make sure to follow the main thread for updates and additional steps. 

Also, please note that once merged, this original thread will be locked, and no further comments or updates can be made.

Cheers,

Muddi

[fcfdbrian]

I am having the same issue on all of my nest speakers at home.  Started about two weeke ago as well.

[B-Rex]

Our speakers have the same problem of 4 lights pulsing continuously. We have 1st Gen minis, 2nd gen minis, an original Google home speaker, and a 2nd gen larger speaker. They all remain on after a broadcast, except the speaker that sent the broadcast. Have tried all sorts of resets. Also, many other glitches lately since this started, like asking a speaker in the bathroom to stop and it shuts off the tv upstairs.

[GoHawks1225]

Ah, turning off the TV thing is happening to me as well. I'll ask it to stop playing the alarm and it'll shut off the TV!!!!

[richardtc007]

I just took photos of 3 of my minis with the pulsing lights. Conveniently, I'm not permitted to upload them here to show you. Disappointing how silent Google is on his topic. Very little should be as important as data/information privacy and security, so how do we know this isn't eavesdropping?

[Muddi]

Hey everyone,

Just a quick update. Our team is on top of this. We've received some reports that resetting the device has fixed the issue. If you haven't tried it yet, please proceed with resetting your devices and check if they still have the same behavior.

Keep us potsed.

Cheers,

Muddi

[artisticcheese]

Resetting did not do anything to me.

[TheHabs]

I reset one of our minis and it didn't help.

[Laupsavea]

Muddi

I am unsure why this has been marked as the best answer because it hasn't actually answered the problem.

You say the team "are on top of this" - I am not sure what that means. Does it mean that they are aware of the issue that has clearly not been caused by your customers? That is not a fix. You have offered no acknowledgement that it is a bug introduced in an update - perhaps you are not allowed to do this? You have given no timescale for a proper fix. So this would indicate that the issue is not fixed so why mark your response as the best answer? Surely the best answer is when something is fixed?

I have noticed this before with issues that have been introduced by Google, the admins suggest a lot of activity (like try and reset your devices) but this seems to be a stalling strategy whilst the dev teams look at the real bug fix. It is a shame that you waste a lot of customers' time this way rather than just acknowledging there is a known issue and that a fix will be released probably in the next X weeks.

[Muddi]

Hi folks,

Thanks for trying. I'll communicate this to the team and update this thread again for more information.

@Laupsavea: Sorry for the misunderstanding. In this case I marked the most helpful response to make sure new visitors are able to see the update, but I understand how the terminology can be misleading. We’re always looking to improve how we surface recommended answers here in the community and appreciate the feedback.

Cheers,

Muddi

[GlassFamily]

Bravo! 

[GlassFamily]

This week we did the following. Deleted the Google Home 'network'. Unplugged all the minis. Deleted the gmail account. We factory reset every mini. Starting with a blank slate. 

We rebooted our internet, created a new Gmail account and then using a different phone created a new Google Home 'network'. We started reconnecting one Mini at a time. This is where things got interesting. 
Each time we connected a mini it would only broadcast to itself and the the ones we had already connected would stop working. We had to go in and reboot every mini every time we added a new mini.  Eventually,, all were reconnected and rebooted and we could broadcast to/from every room. The issue with the lights is still ongoing-the receiving minis still light up and will not turn off until told to stop.  Additionally, we noticed that you do not have to wait for Google to reply "What's the message?" before broadcasting. and sometimes the messages come through incomplete. It is obvious that the minis are not communicating with each other properly.  
Minis seem to be able to send and receive messages (kind of) with the lights pulsing. 
We turned off continuous ed conversation AND removed voice calls. 
It is something Google did when they performed maintenance or upgraded the app?

[TLALB]

We are having the same issues. At times the minis can’t find each, too. 

[Flash442]

I have factory reset all 7 of my devices (3 homes, 3 minis and 1 hub) it worked for few hours then it came back and started pulsing again.

[jackdaniels]

Resetting seems to have no effect.  Broadcast immediately triggers the same behavior on the devices.

[Malthasian]

Hi Muddi. Thank-you for bringing this to the development teams attention.

Do you know what the issue tracker ID is for this bug?