Conversation response doesn't run when selecting "Run Actions"

Original Title: I think I found a bug. Can anyone confirm?

Conversation responses do not play when selecting “Run Actions” from the three dot menu within the edit automation page or using the three dot menu on the action itself. Other actions will run using “Run Actions” but not conversation response.

Can anyone else confirm this? Also, if anyone would like to suggest a better title for this post I’d be happy to change it.

Steps to reproduce:
Create new automation
Add any trigger you want
Add action “Conversation Response”
Save automation
Select “Run Action” from either three dot menu
Nothing happens
Run automation using trigger
“Conversation Response” plays

Edit: Forgot to add my HA version
Core 2025.3.0
Supervisor 2025.03.2
Operating System 14.2
Frontend 20250305.0

Play where? It’s setting the conversations response to be handed to the pipeline it doesn’t… Play. Per se

Post an example automation pls.

Based on the docs this doesn’t really qualify as a bug… it analogous to when templates based on the trigger variable don’t work when you use “Run Action”… if the automation isn’t triggered by a conversation engine, the set_conversation_response has nothing to respond to.

1 Like

Here is the code. Edit: When “Triggered” this runs as expected.

id: '1741361360767'
alias: Battle Stations
description: ''
triggers:
  - trigger: conversation
    command:
      - Battle Stations
      - Battlestations
    enabled: true
conditions: []
actions:
  - set_conversation_response: >-
      Aye Captain, rasing shields, arming phasers, arming photon torpedos,
      targeting sensors online, going to red alert
  - action: media_player.play_media
    target:
      entity_id: media_player.home_assistant_voice_09a7d8_media_player
    data:
      media_content_id: media-source://media_source/local/tos_red_alert_3.mp3
      media_content_type: audio/mpeg
    metadata:
      title: tos_red_alert_3.mp3
      thumbnail: null
      media_class: music
      children_media_class: null
      navigateIds:
        - {}
        - media_content_type: app
          media_content_id: media-source://media_source
mode: single

After reading the docs, I think this is what’s going on. Marked as solution. Thanks for your response.

Although not a bug, this does make testing the conversation response in an automation, more difficult.

1 Like