Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Function spec example for say_tts #176

Merged
merged 1 commit into from
Mar 24, 2024

Conversation

danielp370
Copy link

A flexible say tts example. This allows the LLM to pass in any tts entity so it can direct the message to where it is needed.

Copy link
Owner

@jekalmin jekalmin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution!
It will be released in the next version.

@jekalmin jekalmin changed the base branch from main to v1.0.4 March 24, 2024 13:04
@jekalmin jekalmin added this to the 1.0.4 milestone Mar 24, 2024
@jekalmin jekalmin merged commit 79fbe01 into jekalmin:v1.0.4 Mar 24, 2024
@Scags104
Copy link
Contributor

Question on this, and i know its not its intended purpose but could this be modified and utilized in a way that my input device and output device were separate entities?

Example:
Ask home assistant satellite with no external speaker a question
Home assistant pipeline using extended openai processes
Function always called to export response to specific speaker based on area of input satellite

Let me know your thoughts

@TGrounds
Copy link

Question on this, and i know its not its intended purpose but could this be modified and utilized in a way that my input device and output device were separate entities?

Example: Ask home assistant satellite with no external speaker a question Home assistant pipeline using extended openai processes Function always called to export response to specific speaker based on area of input satellite

Let me know your thoughts

I'm looking for a similar solution.

@jekalmin
Copy link
Owner

If this PR is merged, you can use input device_id in service template. In this way, it seems you will be able to conditionally select a output speaker.

@Scags104
Copy link
Contributor

If this PR is merged, you can use input device_id in service template. In this way, it seems you will be able to conditionally select a output speaker.

sure but how would i grab the response back that open AI is sending?

@jekalmin
Copy link
Owner

jekalmin commented Apr 3, 2024

Currently, as far as I know, Assist pipeline doesn't support respond to another speaker.
Although I haven't tried, this will be a workaround that it pretends to be output speaker but it isn't in reality.
Hence, the response will be lost.

@rfam13
Copy link

rfam13 commented Apr 3, 2024

Check out stream assist integration, I am using it with this. It creates a pipeline from any camera entity or rtsp stream, and allows you to select the output speaker. That is the basic function. However I wanted my Alexa to be the output but that does not work with TTS service streamassist calls on the output device, so I had to install Alexa Media Player addon, and use the custom command for Alexa to use "Simon says , for this to work I have an automation that is triggered when the pipeline (stream assist) says text is detected from the STT entity, if that is true then parse the text from the TTS entity with templating and send to whatever device you want, in my case Alexa. That sounds more confusing than it is lol.

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.

None yet

5 participants