Open dj-sf opened 2 weeks ago
brief update -- i tried labeling my devices with an "area" to see if this made a difference. it did not.
After some tinkering locally, I've discovered a few things.
maybe_result.unmatched_entities
.)timers.yaml
from original post) , the error being thrown is the TimersNotSupportedError
on line 815 of the dev
branch. This is because it fails the logic check that occurs immediately beforehand -- conversation_command
& intent_obj.device_id
are both None
, and the device, not having an id, is not registered with the timer_manager
.Therefore, I'd like to propose some possible fixes:
First, we should either remove the area
requirement from the default intent OR give the clients some sort of placeholder area value so that requirement is fulfilled.
Second, we should either modify the default attributes of the web & mobile clients so that they can pass this logic check out of the box OR we should change this logic to allow them to use the timer intents with their current attributes.
@synesthesiam I see that you have worked on the timer logic quite a bit. Do you know if any of these proposed solutions might work?
It should be also possible to start, stop, ... already existing timer with their default duration entities in HA with a sentance like "start timer {timer_name:name}" so the timer duration needs to be an optional parameter.
The problem
I have been trying to get voice activated timers working for several days now. First I tried using the built in HassStartTimer intent, being sure to adhere to the sentence structures I saw in the yaml file. This only ever produced "Sorry, I couldn't understand that" responses.
I made a HA forum post about this and was told it may be due to the
require_context: area
param. So I created a custom version of the sentences file (timers.yaml
) with that section removed. This led to to new behavior; it correctly interpreted the intent but says the requesting device is incompatible with timers.Yaml & assist conversation text below:
Default conversation behavior:
modified
timers.yaml
withoutrequire_context
block:behavior with custom timers.yaml file:
What version of Home Assistant Core has the issue?
core-2024.6.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
Link to forum post: https://community.home-assistant.io/t/hassstarttimer-built-in-intent-not-working-with-assist/741117/4