Custom voice command, which contain 2 or more starters

[Patrik2]

Hello,
From one day to the next, all automations created by my custom voice command, which contain 2 or more starters in one automation, have stopped working correctly.
Until now, they all worked correctly for a long time.
I am attaching a simple automation for blinds.
When I say "Open Tables", the blinds open to 1 percent and everything works correctly.
However, when I say "Close Tables", the blinds open to 1 percent again, but they should open to 3 percent. This means that the first automation was triggered, not the second one. A few days ago, everything still worked correctly.
Of course, the solution would be to split the automations into two separate ones, then it works correctly, but that is not a solution because I would have many separate and unclear automations.
I am using the Nest Mini 2 assistant.
Is Google Home having any technical problems?
Will everything start working correctly again soon?

metadata:
name: Blinds Open/Close with voice
description: Open/Close Blinds with voice
automations:
- starters:
- type: assistant.event.OkGoogle
eventData: query
is: Open Tables
actions:
- type: device.command.OpenClose
devices:
- Blind 1 - My Room
- Blind 2 - My Room
openPercent: 1.0

- starters:
- type: assistant.event.OkGoogle
eventData: query
is: Close Tables
actions:
- type: device.command.OpenClose
devices:
- Blind 1 - My Room
- Blind 2 - My Room
openPercent: 3.0

[OptimumPrime]

I’m experiencing the same issue.

I have multiple automations in a single file, and all of them were working perfectly fine until about 2-3 days ago.

The timed automations are still functioning, but anything involving voice commands is no longer working.

I’ve deleted all existing scripts and created new ones, but the problem persists.

To troubleshoot, I deleted all scripts and created a simple one to turn on a light bulb when I say “Turn on bulb,” and a separate one to turn it off when I say “Turn off bulb.” This setup works fine on its own.

However, when I combine these two scripts/commands into one script (see below), the bulb turns on, but it does not turn off as expected with the respective command.

I swapped the order of the automations, and it turns out that Google only executes the first automation in the script, ignoring all subsequent ones.

This is rather very annoying considering the time and energy spent into creating these automations.

metadata:
name: Bulb control
description: Bulb control

automations:
- starters:
- type: assistant.event.OkGoogle
eventData: query
is: turn on bulb
actions:
- type: device.command.OnOff
devices:
- Bulb - Kitchen
on: true

- starters:
- type: assistant.event.OkGoogle
eventData: query
is: turn off bulb
actions:
- type: device.command.OnOff
devices:
- Bulb - Kitchen
on: false

[Patrik2]

Yes, it's frustrating. I have 15 scripts that I need to convert into 35 separate voice automations. The worst part is that I don't know if I should wait for Google to fix their issues, and how long it will take them.

[OptimumPrime]

Well, based on the other thread you replied in, it took them about 6+ months to fix the issue in 2023!

At least yours can be split into 35 separate automations, mine is likely around 400.

For me, it might be faster to switch to Alexa than stick with Google home. With AI features built into Alexa now, whisper mode, drop-in feature etc., it seems Alexa gets better over time and Google gets worse. 

Even the broadcast feature now is a hit and miss - sometimes it'll broadcast my voice, sometimes the Google reads out what I say using text to voice (most of the time it's usually off).

[Patrik2]

But hopefully this time they will realize their problem sooner and fix it. I've also been thinking about Alexa

[ByronP]

Hi Folks,

Thank you for posting in the community. I apologize that you're experiencing trouble with your starter routines on your Nest Mini 2nd Gen, specifically with voice command routines. I understand how frustrating this must be. Let's work together to find a solution.

To assist you further, I need to ask a few questions:

• Are the routines set up for the household or personal option?

• When did the situation start?

• What troubleshooting steps have you taken so far?

In the meantime, please try deleting one or two of the routines and setting them up again. Then, try starting the routines once more.

Keep me posted on how it goes.

Regards,

Byron

[Patrik2]

These routines are set up for the household.

The situation started around March 5th.

The only solution to eliminate the problems was to split the script into separate automations, then everything works correctly.

I tried deleting the routines and creating new ones, but it didn't help.

Exactly the same problem started at the same time for multiple users.

[OptimumPrime]

Patrik2 has put it succinctly.

The routines are all created via the script editor from Google home web. As far as I am aware, these routines can ONLY be household, not personal.

Rest of the questions were already answered in the first post. Reading that would be a first step to resolving the issue.

[ByronP]

Hi Folks,

Thank you for your responses. I appreciate the information provided. Help's here.

Please answer these additional questions:

• When did you expect the routine to start?

• Was this routine created using the Google Home app or a third-party app?

• Is the Activate Routine toggle enabled?

• What starters do you have configured to start the routine? Which specific starter do you think should have activated the routine?

• Can you find an entry in the Activity tab for the routine running?

Keep me posted.

Regards,

Byron

[mpn554]

As noted in the original post, the routines are not scheduled, they are triggered with a voice command via "Ok Google".

These issues started a week ago without any changes from our end.

To reiterate the issue:

When a single script has multiple automations, each automation containing separate "assistant.event.OkGoogle" starters, no matter which starter we trigger the furthest top action in the entire script is executed. Prior to 1 week ago, the appropriate action (for each individual trigger) would be executed.

There's an example in the first post, all of the necessary information is available above. Please escalate this to be investigated.

[OptimumPrime]

Oh, it's so clear from the questions being asked by the "Community Specialist" that the issue is still not fully understood. One might even say that a solution isn't exactly on the horizon. But then again, considering this isn't the first time this problem has popped up, and it took over 6 months to fix last time, I wouldn't be holding my breath for any quick fixes.

In the best-case scenario, you might want to consider separating the automations into their own scripts. That's exactly what I did—after 6 hours and 387 scripts later, I managed to get everything working again.

Now, I don’t have to sit around waiting for another half-year for a solution to appear.

[ByronP]

Hi Folks,

Thank you for your insight. I understand your frustration regarding this situation, and I apologize for the misunderstanding. We're always looking for improvements. Please share your experiences and thoughts by submitting them through the feedback form, so we can address this concern in future updates.

Please let me know if you have any further questions.

Regards,

Byron