Skip to content

Add expect_response to TtsReponseData for klat.response - #38

Merged
NeonDaniel merged 1 commit into
NeonGeckoCom:devfrom
mikejgray:feat/klat-response-expect-response
Aug 14, 2026
Merged

NeonDaniel merged 1 commit into
NeonGeckoCom:devfrom
mikejgray:feat/klat-response-expect-response

Conversation

@mikejgray

Copy link
Copy Markdown
Collaborator

Description

Follow-up to NeonGeckoCom/neon_audio#198, per Daniel's review note: klat.response messages now forward expect_response (mapped from listen) so remote clients (e.g. hana's Node WebSocket) know to re-open the mic after TTS playback. TtsReponseData, which backs both neon.get_tts.response and klat.response via NeonTtsResponse, didn't have a field for it.

Adds expect_response: bool = False to TtsReponseData.

Issues

Related: NeonGeckoCom/neon_audio#198

Other Notes

Extended test_neon_tts_response to cover the default value and the klat.response case with expect_response=True.

neon_audio PR #198 forwards `listen` on klat.response so remote clients
(e.g. hana Node WebSocket) know to re-open the mic after playback; this
model needs the matching field to validate/support that payload.
@NeonDaniel
NeonDaniel merged commit b106348 into NeonGeckoCom:dev Aug 14, 2026
5 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.

2 participants