Continued Conversations always active

[cursive umbra]

Please give us an option to make Continued Conversations always happening after a response and not just after it (thinks it) has asked a question.

[fresh laurel]

How would you stop it then?

And this is one o millions questions I have

[hardy igloo]

stop

🙃

[fresh laurel]

Right. Who would have thought. 🫣

[fickle cypress]

doesnt it currently work by recognising a ? at the end of the message. you could add to your prompt to include a ? at the end of the message i guess

[sage ledge]

Yeah could tell the LLM to ask the user if they need anything further after each request, which would make the continued conversation kick in I think

[cursive umbra]

I did not mean that it is always on. I meant that so it always waits a bit after a response for me to follow up with something. This is not so much for controlling the home, but for interaction with my LLM.

[fresh laurel]

It's not intended to work like this.

[left herald]

For a voice chatbot, you'd better take an esp32 (or s3) board and build a simple version of the firmware from the available components in esphome. This is implemented quite easily if you are willing to give up some features.
If the response flag at the end of the pipeline is active, a new cycle is started.
If in the listening phase the VAD does not trigger in the set time or a stop word (homeassistant_HassNevermind) is sounded, the cycle is aborted.

As you create and use it, you will understand why this is not implemented in a mass-produced device. Besides the technical nuances, there are too many unnecessary reactions to any sound. But it's still fun, definitely give it a try.

[cursive umbra]

Yep. Exactly. I don't need to do something special. The functionality is already there. Just give me the option to make that happen every time. I will worry about the implications, for now, and they can improve/fix that over time. I don't have much to worry about when I live alone. A 'smart home' should have a interactive AI.