Timers and enhanced media player control #2193
Replies: 6 comments 22 replies
-
One addition to timers: there is now a Example: |
Beta Was this translation helpful? Give feedback.
-
Trying to translate the intents for timer to Dutch, but I run into some errors. The error are about unsupported slots or missing slots, and I don't really understand why or how. Can someone shed a light on this?
|
Beta Was this translation helpful? Give feedback.
-
I think there is a bug or inconsistency. @synesthesiam could you take a look, please? # tests/ro/_fixtures.yaml
areas:
- name: "Bucatarie"
id: kitchen # <--- area_id different from name
floor: Parter
- name: "Sufragerie"
id: living_room # <--- area_id different from name
floor: Parter
timers:
- area: kitchen # <--- area_id provided
start_minutes: 5
total_seconds_left: 190
rounded_hours_left: 0
rounded_minutes_left: 3
rounded_seconds_left: 0 # tests/ro/homeassistant_HassPauseTimer.yaml
tests:
- sentences:
- "opreste putin cronometrul din sufragerie"
intent:
name: HassPauseTimer
slots:
area: Sufragerie # <--- area name provided - WORKS!
response: Am pus pe pauză temporizatorul # tests/ro/homeassistant_HassTimerStatus.yaml
tests:
- sentences:
- "care e statusul temporizatorului din bucatarie?"
intent:
name: HassTimerStatus
slots:
area: Bucatarie # <--- area name provided - DOES NOT PASS TEST
response: |
Mai durează 3 minute The test for HassTimerStatus responds with the equivalent of {% if num_timers == 0: %} It's easily fixable by providing the area name instead of ID to the It's easy to miss this in English, where most IDs ar the same as the names of areas. |
Beta Was this translation helpful? Give feedback.
-
when doing any time command (besides start) without any context - which timer is addressed? example
which timer gets canceled? |
Beta Was this translation helpful? Give feedback.
-
another question about the syntax - especial whitspaces within or outside of brackets - in #2183 we have the following syntax: - "<timer_cancel>[ the| my] timer"
- "<timer_cancel>[ the| my] <timer_start> timer" but i would expect something like - "<timer_cancel> [the|my] timer"
- "<timer_cancel> [the|my] <timer_start> timer" is this just a question of preference, or are there specific reasons for it? |
Beta Was this translation helpful? Give feedback.
-
I found a small bug. If the device alias (possibly name too) ends with a dot, the conversation_command is not executed. Although for ordinary intents these names are not an issue. |
Beta Was this translation helpful? Give feedback.
-
Hi @home-assistant/language-leaders 👋
The 2024.6 version of HA brings us one step closer to support all of the common tasks people need with voice satellites! This version will add support for timers in Assist and more ways of controlling media players 🚀
For timers, we have 6 new intents and 3 new error messages:
HassStartTimer
- start a new timer (requires area context)HassCancelTimer
- cancel a timer by name, area, or start timeHassTimerStatus
- report status of timer(s) (see the English response template)HassIncreaseTimer
- add time to a timerHassDecreaseTimer
- remove time from a timerHassPauseTimer
- pause a running timerHassUnpauseTimer
- resume a paused timerSee #2179 for an example of adding timers to the test fixtures.
The new error messages are:
timer_not_found
- error when no timer matches constraints (name, duration)multiple_timers_matched
- error when more than one timers matches constraints (timer intents can only target one timer for now)no_timer_support
- the voice satellite does not support timersFor enhanced media player control, the existing intents have been expanded so that a media player name is not required. Area context is required so that sentences like "pause" and "next" will target the media player(s) that are playing in the voice satellite's area. Only media players in the correct state (playing/paused) and supporting the required features (setting volume) will be targeted.
There are 2 new error messages:
entity_wrong_state
- an entity is not in expected state (e.g.,playing
for a media player when "pause" is spoken)feature_not_supported
- entity does not support the required feature (e.g.,VOLUME_SET
for a media player when "set volume..." is spoken)Let me know if you have any questions. Thanks! 🙂
Beta Was this translation helpful? Give feedback.
All reactions