Do [thing] at [time] doesn’t seem to work?

[blissful pollen]

I have a IR blaster and a couple of scripts to send various commands. I can use built in HAOS assist to say ‘Run device command in x minutes’ eg ‘run fan power in 10 minutes’ will trigger the script called ‘power’ under entity ‘fan’, and this works no problem.

But if I say ‘At 10pm run fan power’ then it has no idea what I’m asking. I’ve tried various variations but only specifying in hours and minutes seems to work, not a specific time. Any idea how to get assist working with times?

[queen knoll]

No, it won't work. There's no intent for this.
You can create some automation for this I guess, but it will be hanging there while awaiting for right time - and of course, no restart after HA reboot.

Also there will be no check if your action can be ran, or it will fail. Same applies to "in 5 minutes do something". Assist won't check if it can "do something", it will just silently fail in 5 minutes.

[blissful pollen]

So I find that in x minutes does work, I wouldn’t expect either to work if for some reason had to reboot but I don’t expect to have to reboot very often.

I just don’t understand why it can schedule a command in hours and minutes but not at a time?

[queen knoll]

Simply because it's not yet implemented.

Scheduling something in 5 minutes means simple delay(5min)->execute
Scheduling something to certain time means dealing with local clock (which can lie because of incorrect time zone), creating listener for that time and placing all this somewhere in the system. Much harder. There's no ecosystem for dynamic automations (and this is actually dynamic automation).
Also, despite you don't expect something to happen in 5 minutes if you rebooted, you certainly will want it to happen if you set certain time for it (like alarm).

Anyways. You can achieve this with some extensive intent_script and manually created calendar, probably. I have reminders set in this manner, and they work.

[blissful pollen]

Hmm okay, would have thought quite a basic functionality so thought would be built in, like it just creates equivalent of cron job.

I guess I’ll look into casa nabu and getting Alexa to send a web hook at a specific time or something?

(This isn’t any shade against you, just assumed dynamically being able to set a trigger by time would be basic built in functionality, I appreciate you taking the time to respond)

[queen knoll]

No offense taken. 🙂
I believe it's worked on - voice is just young enough to have flaws.

[queen knoll]

Well, not just the Cron job, but register it somewhere to be able to cancel, or track... All this requires metadata, and building into existing entities/services/automations paradigm...