#HA Voice cannot parse a sentence for a specific light

1 messages · Page 1 of 1 (latest)

elfin tartan
#

I’m struggling to resolve an issue with Home Assistant voice when saying "office light on":

  • Home Assistant Voice PE responds “An unexpected error occurred”
  • Sentence Parser cannot parse “office light on” or “office light off”. It doesn’t respond at all. In debug mode, the browser reports unidentified errors
  • The entity is named “office Light” and it’s in an area called “office”.
    all other similar commands work “kitchen light off”, “bedroom light on” even areas with no area like “ground light on” gets parsed.
  • Office light is a valid entity (light.office_light) that has been type changed from a matter switch (switch.office_light)
  • Alexa works (through HA Cloud) using the same sentence.
  • I’ve completely removed all my custom intents and scripts…
  • Also, if I use “set the office light to 20 percent” (it’s not a dimmable light) it parses using HassLightSet properly..

Any advice appreciated.

polar yacht
#

you aren't using LLM, so your command has to be very specifically worded

elfin tartan
#

Hmmm..

  • Same phase works on all my other lights (Kitchen light off)
  • "Turn off office light" doesn't work either
polar yacht
#

would need to check the logs and see what it says is failing

#

Seems that sentence structure is actually technically correct

sharp halo
#

The sentences themselves should work. Check for what that "unexpected error" is

#

And i mean HA core logs, not browser logs

elfin tartan
# 
Logger: homeassistant.components.conversation.default_agent
Source: components/conversation/default_agent.py:456
integration: Conversation (documentation, issues)
First occurred: 12:57:57 PM (1 occurrences)
Last logged: 12:57:57 PM

Unexpected intent error
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/intent.py", line 145, in async_handle
    result = await handler.async_handle(intent)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/intent.py", line 1031, in async_handle
    match_result = async_match_targets(hass, match_constraints, match_preferences)
  File "/usr/src/homeassistant/homeassistant/helpers/intent.py", line 603, in async_match_targets
    _add_areas(ar, dr, candidates)
    ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/intent.py", line 503, in _add_areas
    assert candidate.area is not None
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 456, in _async_process_intent_result
    intent_response = await intent.async_handle(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<10 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/intent.py", line 153, in async_handle
    raise IntentUnexpectedError(f"Error handling {intent_type}") from err
homeassistant.helpers.intent.IntentUnexpectedError: Error handling HassTurnOn
sharp halo
#

Do you happen to have an empty alias for one of your areas?

elfin tartan
#

All areas named, but no alias's

sharp halo
#

Please add an issue for the conversation integration. It must have to do with your setup, but throwing "an unexpected error" is not nice user experience 😬

elfin tartan
#

Will do. I'm not seeing anything abnormal with this setup... and it works with alexa. Thanks for looking