Custom sentence wildcard order matters?

Configuration Voice Assistant
1

I’m adding a custom sentence automation as outlined in the docs

specifically, playing and stopping two different media players.

“{location} News {action}” works fine
“{action} {location} News” fails

trigger: conversation
command:
  - "{location} News {action} "
  - "{action} {location} News"

I don’t see where the assist pipeline debug is helpful.

nit_options:
  start_stage: intent
  end_stage: intent
  input:
    text: play kitchen news
  pipeline: 01gzyhjtavg8n7hbg7f0pcpa02
  conversation_id: null
stage: done
run:
  pipeline: 01gzyhjtavg8n7hbg7f0pcpa02
  language: en
  conversation_id: 01JXZSND3C0HG9AFXMMPKEN101
  runner_data:
    stt_binary_handler_id: null
    timeout: 300
events:
  - type: run-start
    data:
      pipeline: 01gzyhjtavg8n7hbg7f0pcpa02
      language: en
      conversation_id: 01JXZSND3C0HG9AFXMMPKEN101
      runner_data:
        stt_binary_handler_id: null
        timeout: 300
    timestamp: "2025-06-17T20:35:34.638055+00:00"
  - type: intent-start
    data:
      engine: conversation.home_assistant
      language: en
      intent_input: play kitchen news
      conversation_id: 01JXZSND3C0HG9AFXMMPKEN101
      device_id: null
      prefer_local_intents: false
    timestamp: "2025-06-17T20:35:34.638134+00:00"
  - type: intent-end
    data:
      processed_locally: true
      intent_output:
        response:
          speech:
            plain:
              speech: Sorry, I couldn't understand that
              extra_data: null
          card: {}
          language: en
          response_type: error
          data:
            code: no_intent_match
        conversation_id: 01JXZSND3C0HG9AFXMMPKEN101
        continue_conversation: false
    timestamp: "2025-06-17T20:35:34.641906+00:00"
  - type: run-end
    data: null
    timestamp: "2025-06-17T20:35:34.642008+00:00"
intent:
  engine: conversation.home_assistant
  language: en
  intent_input: play kitchen news
  conversation_id: 01JXZSND3C0HG9AFXMMPKEN101
  device_id: null
  prefer_local_intents: false
  done: true
  processed_locally: true
  intent_output:
    response:
      speech:
        plain:
          speech: Sorry, I couldn't understand that
          extra_data: null
      card: {}
      language: en
      response_type: error
      data:
        code: no_intent_match
    conversation_id: 01JXZSND3C0HG9AFXMMPKEN101
    continue_conversation: false

Is “play” a reserved word? It doesn’t show up in the dev docs.

2

I don’t think it’s an issue with a reserved word though because

trigger: conversation
command:
  - "goat {action} {location} News"

doesn’t work either.