Stuck LEDs & Timers

[TE5LA]

Oh boy! I get to make a double gripe today. First, whenever I use an automation that I've used hundreds of times, the speaker will perform it as usual,  but then start its LEDs scanning endlessly. It will not stop until I use the wake phrase again. I don't have to issue a command. It will just stop after it acknowledges my command. 

Secondly,  who thought it would be a great idea to remove the ability to assign names to timers? Yeah, this works great if you have three timers running simultaneously. 

Google is making me regret switcing from Alexa. Stop screwing up the system.

[ByronP]

Hi TE5LA,

Thank you for posting in the community. I see you're having trouble using an automation on your Google Nest Speakers which are running as usual, but then the speaker LEDs begins scanning continuously until you say the wake-up command again. I also note your concern regarding the inability to assign names to timers. I appreciate all the detailed information you've provided, and I understand how frustrating this can be. I'm here to help.

For better assistance, please answer the following questions:

• What type of Google Nest Speaker do you have? (Here is a helpful article to identify the model of Google Nest Speaker).
• When did the situation start?
• Is this a Custom Routine? If yes, is it a Personal or Household Routines?
• What color are the LED lights, and how many lights are displayed on the device?
• Does this only happen with Custom Routines or does it also occur with a daily task or action?

Additionally, regarding the ability to assign names to timers, we're always looking for ways to improve. Please consider sharing your thoughts and insights by submitting them through the feedback form so we can implement improvements in future updates.

Please keep me posted on your findings.

Regards,

Byron

[TE5LA]

It is a Google Home Bluetooth speaker, the sort of flattened cylinder with cloth all over. It has four LEDs on the front.

This started a few weeks ago, I guess. Around the same time as an update to Home Assistant. It affects two automations for the same equipment. Two devices to simply turn on and off. These automations have been used for around 2 years. Nothing has been changed here. This doesn't occur with any other automation. It doesn't happen if I give the two commands in the automation as independent commands, only when they are in an automation.

I have already tried rebooting the speaker and creating a new automation with the same commands. It is still the same. The LEDs scan from left to right across all four in white. They will continue for eternity unless I say, "Hey, Google." I don't need to issue another command. They just stop after waking the speaker.

This is very annoying. 

Also annoying is the fact that naming timers had been removed. Previously,  you could say, Hey, Google. Set a 30-minute timer named oven," and it would confirm the timer and name, and announced the name at the end. This no longer works.

I discovered a work-around. You can ask it to set a timer, giving it a name without a time, and Google will ask, "How long?" Then, you can give a time. However,  at the end, the notification will not announce what the timer is for unless you ask, "Hey, Google, what was the timer for?"

This is all very awkward if you have multiple timers going. You don't know which timer has expired. I don't know why they would change things like this. Alexa's timers are far better. It even tells you on other speakers that timers in another room have ended.

I would think they'd want to make Google Home better, not worse. Another thing they should change is Google confirming every command verbally. Just do the things silently that are obvious. If I tell it to turn off a light, why do I need confirmation? I can tell if the light is off.

Many times, I will use an automation that turns on several things. Sometimes,  it will say a light is offline (3 annoying times in a row), yet the light turns on just fine.

I used to be able to pause playback on my Nvidia Shield via voice. This no longer works either. It will say, "Pausing Shield," but it doesn't. 

[ByronP]

Hi TE5LA,

Thank you for your prompt reply. I appreciate all the detailed information.

Based on your answers, please do the following recommendations:

Step 1: Active Routine toggle off and on. Here are the steps:

1. Open the Google Home app.
2. Tap Automations.
3. Check which section (Household Routines or Personal Routines) the Routine is listed under.
4. Toggle the Routine off and then back, and try running it again.

Step 2: Find the Routine Entry in the Activity tab.

The Google Home app includes information about when and why Household Routines ran, which can help determine the cause of the failure. Here are the steps:

1. Open the Google Home app.
2. Tap Activity.
3. Find “Routine Started” events. The entry should include the time the Routine ran, the name of the Routine, and what caused the Routine to start or fail.

Additionally, please provide the firmware version for your Nest Speaker. Here are the steps:

1. Open the Google Home app.
2. Tap Home and then All (if necessary), then touch and hold your device's tile.
3. Tap Settings icon, then Device information.
4. Under 'Technical information', check for the Cast firmware version: 'X.XXX.XXXXX'.

Please keep me posted.

Regards,

Byron

[TE5LA]

I don't think pausing and starting applies as I have already created new automations that have the same issue. 

The only thing activities show is an automation started "because of a voice command." No more details. 

The cast firmware is:

3.77.505721

[ByronP]

Hi TE5LA,

Thank you for your reply. I appreciate all the information. Let's explore additional options.

Based on your answers provided, please do the following:

Step 1: Do an additional factory reset to the device. Here are the steps:

1. On the side of the device, unplug the power cord.
2. Wait 10 seconds.
3. Plug the device back in.
4. Wait until the 4 LEDs light up.
5. Repeat the steps for 8 more times.
6. On the side of the device, switch the mic off. The LED lights should turn orange.
7. Press and hold the top of the device where the LED lights are. After 5 seconds, the device should begin the reset process.
8. Continue to hold the top of the device for another 10 seconds or until the Google assistant confirms that the factory reset process has started.
9. Wait until you hear a voice prompt “Welcome to Google Home." Then use the Google Home app to set up the device again.

Step 2: Create a new automation or edit the existing one using different names or similar actions.

Edit the custom routine to give a different name to the starters and actions. Here are the steps:

1. Open the Google Home app.
2. Tap Automations.
3. Choose a Routine to edit
4. Edit the Routine, then you can do the following:

• Edit Routine name.
• Add or edit starter.
• Add or edit actions.
• Reorder actions.

Please let me know how it goes.

Regards,

Byron

[TE5LA]

A factory reset is simply touching the top of the speaker for around 10 seconds. You must be thinking of a different product. 

Why would just this one automation exhibit this issue when I have more than a dozen that don't? It also contains a power toggle for just two devices, and does not go into this mode if I issue separate voice command for those devices. This must have something to do with the update.

[ByronP]

Hi TE5LA,

Thank you for your reply. I appreciate your insights regarding the previous steps provided.

I understand about the reset process that you performed. However, there is an alternative factory reset that needs to be tried. Doing these alternative steps can delete all previous data from the device and start from the beginning.

Also let me know if you did the alternative custom automation using a different wording and actions.

Please let me know how it goes.

Regards,

Byron

[TE5LA]

I figured it out. Google wants to keep removing abilities so users can have a worse experience, like how they removed naming timers.

They also removed allowing voice commands within automations. The automations for the device in question literally had, "Turn off Shield." Well, it isn't allowed anymore.  I replaced it with a device control instead of a custom one, and now it works as it should.

I wish Google would stop screwing things up with Home Assistant, but if they are going to change something, they at least inform us.