tired elm
my voice assistant can't set timers for entities. When i e.g. say turn off the lights ... in 10 seconds it does not work neither with open Ai nor with Gemini and also not with Home Assistant cloud.
With open Ai Assist turns off the lights immediately.
With Home Assistant pipeline i get the following error: no area with the name 10 seconds
with Gemini nothing happens.
Is there any known issue with that, or a workaround?
Thank you
unborn swan
Turn on "prefer handling commands locally" in your conversation agent settings.
unborn swan
Hmm, looks like these delayed commands are broken even for local control..
tired elm
I have turned this setting on already.
Is it not working on your HA as well?
unborn swan
Yeah tried with Respeaker satellite and Wyoming satellite.
It says "command will be executed... ", and debug in pipeline shows correct command (so no STT bug or any) - but the command isn't executed.
spark knoll
You have two issues combined.
Initially, deferred commands stopped working with AI agents. I pointed this out. https://github.com/OHF-Voice/intents/issues/3174
Additionally, you have a collision of two intents, as indicated by the error "no area with the name 10 seconds," meaning your request is misdirected.
You can prioritize the command by creating a local copy as a custom sentences, but this isn’t a complete solution.
In a related thread, we addressed a deferred action issue—you could tweak the script’s code, and that might work for you. These are instructions for implementing three components that will work together. https://github.com/mitrokun/custome_sentences/blob/main/start_with_timer.yaml But be careful with the voice command template in automation so that you don't lose the ability to control devices in rooms.
Unfortunately, lists from the yaml configuration are not supported in the GUI, so it is not possible to implement automation in a neat way. However, you can personalize triggers for minutes, seconds and hours (if required) and run your own script variant via the Choice.
tired elm
Ok thanks a lot. I am seeing a bit clearer now. So my best bet is to wait till it is fixed for using it with ai (hope it ts getting so).
Since i am not used to yaml it is a hassle for me to use the workaround. And i also use the AI agent most of the time.
full quarry
Just thought I would add, that I tried the "turn off the lights in ten seonds" and it works on my setup (ChatGPT w. prefer handling locally)
tired elm
Hmm lucky! Do you have something special in your Promt?
full quarry
Sorry, just now seeing your reply ....I double checked and I now see that this was handled locally, so ChatGPT didn't get a chance to run it. The built-in intent that matched was '{timer_command:conversation_command} in <timer_duration>'