Good day all, hopefully I can explain this well enough to render some insight and help.
I have an automation that is triggered by a sentence, that sends some information off to a LLM via the 'Conversation Process' action. I am then using the 'Conversation Response' action in the automation to play back what was returned from the LLM.
My TTS is running Piper on an seperate local server with a bit more beef to it than my Home Assistant server.
This all works fine when the response is short, what I have found is less than 120 words. However, if the response from the LLM is a bit longer, this causes Piper to have to work a little harder and thus take a little longer.
What I am finding is that the conversation process or keep alive (I'm not sure what to call it tbh) seems to be ending before Piper can finish processing the response from the LLM. Which is often somewhere between 800 and 1200 words.
The end result is that nothing is played back via the media_player through the Conversation Reponse action.
I've tested this with simple asks of the LLM, such as "Tell me a story in 200 words". This helped determined how many words I could successfully get to work. Which seems to be 120 or less.
I am using the ReSpeaker Lite as the media player that initiates the automation via the wake word and then sentence. I have no issue with this automation or assist pipeline, if the the response from the LLM is small enough. Only why the response is a bit more verbose.
So my question or ask for help is, what causes the Conversation Process to timeout, can this value be adjusted, or is this just a limitation at the moment? Any workarounds?