Could not determine which routine to run. Please use a unique voice starter for each routine.

[glencreek]

When you create a routine in the Google Home app, it won't allow you to repeat a previously used voice command. In that case, the text box is outlined in red with the warning 'The command phrase "blah" is already being used in another routine.' Therefore it should not even be possible to have multiple routines with the same command phrase.

It appears that I have corrupted settings with a phantom routine. If I enable the visible routine and speak the command, the subject error is announced. If I disable the visible routine and speak the command, there's a silent failure. It seems the only possible fix would be to start over with a new account. That doesn't sound like fun-- especially when this could happen again.

Any ideas?

[SmartHomeH-TAGS]

You could have one automation that is enabled and one disabled.

Can you delete both automations before recreating the automation you actually want?

[glencreek]

Thanks for your interest. You can't have more than 1 routine with the same name or starter command-- even if 1 is disabled. Try it. Only 1 routine is visible in the app and on the web. I've deleted and recreated multiple times. The fact that Google silently does nothing rather than complaining about lack of matching routine, suggests that there's an orphan somewhere.

I even downloaded my Google data. I only see 1 copy of the routine.

[SmartHomeH-TAGS]

Yes, I know. The exact same command phrase is impossible to use twice.

Could it be possible that you have the same words pronounced the same, but misspelt or Bedtime/Bed time?

How many automations do you have? I have about 300.

[glencreek]

I only have 24 Google automations-- mostly to smooth over errors in Google's command interpretation. All the heavy-lifting is in Home Assistant. The problem routine is one that received multiple edits. I was tweaking and then at some point it failed. I really think the backend Google database is corrupt.

If it were a case of sound-alike, then there should be some evidence of the other routine. There's no 'ding' or verbal response from the command when the visible routine is disabled or deleted.

[glencreek]

assistant.command.OkGoogle requires one or more explicit devices. Is there a way to substitute the device which received the command? Alternatively, is there a way to conditionally test which device received the command?

I really think Google is late to the game and reinventing the wheel. If there were some way to export the command text and the device it came from, I could do everything in Home Assistant so much more efficiently.