Skip to content

A voice command that acts says what it did - #28

Merged
AboveColin merged 2 commits into
feature/1.16from
action-speech
Sep 24, 2026
Merged

AboveColin merged 2 commits into
feature/1.16from
action-speech

Conversation

@AboveColin

Copy link
Copy Markdown
Owner

Jev ran an action through the intent layer, which sets no speech, so the Assist dialog showed no reply and a satellite said nothing. Home Assistant's own agent picks a sentence from home-assistant-intents by what the command targeted. Jev now reads the same response key off the slots it sent and renders that sentence in the pipeline's language, such as "Turned on the light". Where the package has no sentence, as for a toggle, it says "Done."

This changes what existing users hear: an action that was silent now speaks one sentence.

Tests: test_an_action_says_what_the_default_agent_says, test_an_action_with_no_sentence_of_its_own_says_done, test_a_brightness_command_says_it_was_set.

Local gate: ruff, ruff format, mypy --strict, pytest (417 passed), config_flow 100%, mkdocs --strict, hassfest. EXIT 0.

Jev ran the action through the intent layer, which says nothing, and the
Assist dialog showed no reply at all. Home Assistant's own agent picks a
sentence from home-assistant-intents by what the command targeted. Jev
now reads the same key off the slots it sent and renders that sentence,
and says "Done." where the package has none, as for a toggle.
# Conflicts:
#	custom_components/jev/conversation.py
#	tests/test_conversation.py
@AboveColin
AboveColin merged commit da968ff into feature/1.16 Sep 24, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant