Intents working but not firing intent_script

I have an intent_script issue. I have intents setup up and tested via sentence parser that they are being picked up, but the intent_script never triggers.

Here is my intent:(just a few, there are more)

language: en
intents:
  Spotify:
    data:
      - sentences:
        - "Play {media_search} on {media_player}"
  ShowMe:
    data:
      - sentences:
          - "Show me that you are working"
          - "Give me some love"
lists:
  media_search:
    wildcard: true
  media_player:
    values:
      - in: "(basement sonos)"
        out: "media_player.basement_sonos_2"
      - in: "(kitchen sonos)"
        out: "media_player.kitchen_sonos"
      - in: "(living room sonos)"
        out: "media_player.living_room_sonos"
      - in: "(basement chromecast)"
        out: "media_player.basement"
  volume:
    range:
      from: 0
      to: 100

Here is my config (eventually will be a package but I am keeping it simple until it works)

intent_script:
  
# Spotify
  Spotify:
    speech: 
      text: "No problem, playing {{media_search}} on {{media_player}}."
    action:
      service: spotcast.start
      data:
        entity_id: "{{media_player}}"
        search: "{{media_search}}"
        shuffle: true
  ShowMe:
    speech:
      text: "Yes, boss. I am working."

When I go into the parser to test. It finds the intent but doesn’t play the expected speech.

image

Here is the actual output via voice assist debug.

intent:
  engine: conversation.llama3_2
  language: "*"
  intent_input: " Give me some love."
  conversation_id: 01JD77J9EAP6Z0S6PEHBA7PH2B
  device_id: f7fe1ed43e1c739b9b33e2c89df78c17
  done: true
  intent_output:
    response:
      speech:
        plain:
          speech: >-
            The lights in the Basement area are already on. Would you like to
            try a different command?
          extra_data: null
      card: {}
      language: "*"
      response_type: action_done
      data:
        targets: []
        success: []
        failed: []
    conversation_id: 01JD77J9EAP6Z0S6PEHBA7PH2B
tts:
  engine: tts.piper
  language: en_US
  voice: en_US-hfc_female-medium
  tts_input: >-
    The lights in the Basement area are already on. Would you like to try a
    different command?
  done: true
  tts_output:
    media_id: >-
      media-source://tts/tts.piper?message=The+lights+in+the+Basement+area+are+already+on.+Would+you+like+to+try+a+different+command?&language=en_US&tts_options=%7B%22voice%22:%22en_US-hfc_female-medium%22,%22preferred_format%22:%22wav%22,%22preferred_sample_rate%22:16000,%22preferred_sample_channels%22:1,%22preferred_sample_bytes%22:2%7D
    url: >-
      /api/tts_proxy/f88ca68dd6a5aa2f2ba60a10af4bbc2a679dfc72_en-us_f632bda3b3_tts.piper.wav
    mime_type: audio/x-wav

How do I tie the intent to the intent_script? (I hope it’s not just bad formatting becuase I have tried is with all different indenting and Studio Code isn’t flagging anything.

Adding steps here.

  1. Disable llama3.2 and use core homeassistant conversation agent.
  2. Found 1 empty yaml script in custom_sentences/en folder, removed.
  3. Had a reference to packages but no scripts in the package folder. (considered this just like empty scripts.
  4. Removed the Shuffle: True

After doing that I get logs in HomeAssistant Core that were not there before.

Now some of my intents work but the main one above “Spotify” does not due to a slot issue. I can’t seem to find how to fix it.

Error message.

  File "/usr/src/homeassistant/homeassistant/helpers/intent.py", line 146, in async_handle
    raise InvalidSlotInfo(f"Received invalid slot info for {intent_type}") from err
homeassistant.helpers.intent.InvalidSlotInfo: Received invalid slot info for Spotify

There are some posts about slots, but nothing that is pointing me to a fix.