I think it’s more a feature request than anything else: a way so I can, using voice assistant, turn a device just for a specific period of time.
My use case is when I’m going to sleep, I like to turn the AC for just a couple hours.
Using Google Home I can do that, saying something like “turn AC for 2 hours”.
But with Home Assistant I need to do a couple of things: first turn on the AC, and then request to be turned off after 2 hours.
I checked and saying to turn on triggers hassTurnOn, and saying to turn off after 2 hours triggers hassStartTimer.
The idea here is when turning on, that could be an extra option to set a timer to turn off the same device, like “turn on <for|during|etc.> ”.
That seems useful? Any ideas or comments about it?
Any idea how? I couldn’t understand how to do that based on the examples for custom sentences.
Also, being a built-in feature would be nice to be in pair with commercial smart assistants, like Google Assistant.
Start by building a script that accepts a target entity and a time. And does what you want the once you have it expose it to the voice assistant. Once the script works every time then…
If you are using assist without an LLM you will need to make a sentence trigger so it responds to a certain utterance. If llm only then make sure the llm understands the script.
Yes it would be nice to ‘add in’ but there’s also a lot of other high priority things they need to work on. And this can be done with a script.
I’m trying to create a intent script, but I want to do two things with the script: turn on the device, and then set a timer to turn off the save device after the time.
The problem is I can’t add more than one single action to my intent script.
Can we at least have a feature request in the GitHub for it? I had a long time feature requested related with Tuya and my standing desk and a person eventually implemented.
Go for it nothing is stopping you from requesting it (I’ll personally vote against it) if you want one do it. But ^^^ that guy mchk is one of the cores and if he’s telling you what to look at you have an indication of how that will go.
Tl,Dr. Assist already can delay action. If you need a more complex version you’re going to have to write it yourself. (and I may add tool slots are LIMITED and if using LLMs when you hit tool 129 your llm stops! Like dead cold stop - error talking to open ai) . This is a limit in the oai spec not a HA limit.) so i personally do NOT want random tool sprawl that can suddenly stop my LLM working if a random tool gets added…
My idea would be something locally processed. Instead of just recognizing “turn on ”, and at the same way it supports a variation, “turn on on ”, something like “turn on for ”.