core icon indicating copy to clipboard operation
core copied to clipboard

Assist sentence parser non-functional 2024-2-0b8

Open Didgeridrew opened this issue 1 year ago • 6 comments
trafficstars

The problem

Assist seems to have completely lost the ability to parse sentences. The Sentence parser in dev. tools returns nothing. Every intent, even previously-working, built-in intents, returns "Unexpected error during intent recognition".

What version of Home Assistant Core has the issue?

core-2024.2.0b8

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

Assist

Link to integration documentation on our website

https://www.home-assistant.io/voice_control/

Diagnostics information

Sample from Voice assistant debug:

init_options:
  start_stage: intent
  end_stage: intent
  input:
    text: turn on the lights in the kitchen
  pipeline: 01hnxx0m198kjpx5a21xa5tg44
  conversation_id: null
stage: done
run:
  pipeline: 01hnxx0m198kjpx5a21xa5tg44
  language: en
  runner_data:
    stt_binary_handler_id: null
    timeout: 300
events:
  - type: run-start
    data:
      pipeline: 01hnxx0m198kjpx5a21xa5tg44
      language: en
      runner_data:
        stt_binary_handler_id: null
        timeout: 300
    timestamp: "2024-02-06T00:57:35.923058+00:00"
  - type: intent-start
    data:
      engine: homeassistant
      language: en
      intent_input: turn on the lights in the kitchen
      conversation_id: null
      device_id: null
    timestamp: "2024-02-06T00:57:35.923092+00:00"
  - type: error
    data:
      code: intent-failed
      message: Unexpected error during intent recognition
    timestamp: "2024-02-06T00:57:35.932002+00:00"
  - type: run-end
    data: null
    timestamp: "2024-02-06T00:57:35.932052+00:00"
intent:
  engine: homeassistant
  language: en
  intent_input: turn on the lights in the kitchen
  conversation_id: null
  device_id: null
  done: false
error:
  code: intent-failed
  message: Unexpected error during intent recognition

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.assist_pipeline.pipeline
Source: components/assist_pipeline/pipeline.py:988
Integration: Assist pipeline (documentation, issues)
First occurred: 7:22:08 PM (7 occurrences)
Last logged: 7:57:35 PM

Unexpected error during intent recognition
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/assist_pipeline/pipeline.py", line 988, in recognize_intent
    conversation_result = await conversation.async_converse(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/conversation/__init__.py", line 543, in async_converse
    result = await agent.async_process(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 221, in async_process
    result = await self.async_recognize(user_input)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 186, in async_recognize
    if trigger_result := await self._match_triggers(user_input.text):
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 881, in _match_triggers
    for result in recognize_all(sentence, self._trigger_intents):
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 507, in recognize_all
    for maybe_match_context in maybe_match_contexts:
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 1082, in match_expression
    group_contexts = [
                     ^
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 1074, in match_expression
    yield from match_expression(settings, context, item)
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 1082, in match_expression
    group_contexts = [
                     ^
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 1363, in match_expression
    raise MissingRuleError(f"Missing expansion rule <{rule_ref.rule_name}>")
hassil.recognize.MissingRuleError: Missing expansion rule <numeric_value_set>



### Additional information

I'm not sure this is related to the beta release, I haven't been using the integration regularly so I have no idea when it was last working. However, @tetele told me to go ahead and create an issue.

I've removed all custom intents, sentences, and automations with sentence triggers. 

Didgeridrew avatar Feb 06 '24 15:02 Didgeridrew

Hey there @home-assistant/core, @synesthesiam, mind taking a look at this issue as it has been labeled with an integration (conversation) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of conversation can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign conversation Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


conversation documentation conversation source (message by IssueLinks)

home-assistant[bot] avatar Feb 07 '24 14:02 home-assistant[bot]

Could you also run the same sentence here and paste the results? Try multiple times, you might get different results

tetele avatar Feb 07 '24 14:02 tetele

.... Try multiple times, you might get different results

The results in the Assist tool are always the same, no results...

I have tried 3 versions of the phrase, testing each 2 times... and repeated that using Chrome, Firefox, and the Companion app. None of them produced a result.

FWIW, I am currently running 2024.2.0b11

When using intents with aliases or entity names the following errors are produced:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/conversation/default_agent.py:881
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 10:01:09 AM (17 occurrences)
Last logged: 10:34:41 AM

[140069820485824] Error handling message: Unknown error (unknown_error) Drew Devices from 73.132.63.72 (Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0)
[140069820483008] Error handling message: Unknown error (unknown_error) Drew Devices from 73.132.63.72 (Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0)
[140069815514944] Error handling message: Unknown error (unknown_error) Drew Devices from 73.132.63.72 (Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36)
[140069803243968] Error handling message: Unknown error (unknown_error) Drew from 73.132.63.72 (Mozilla/5.0 (Linux; Android 10; B130DL Build/QP1A.190711.020; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/120.0.6099.232 Mobile Safari/537.36 Home Assistant/2024.1.5-12102 (Android 10; B130DL))
[140069756637120] Error handling message: Unknown error (unknown_error) Drew Devices from 10.0.0.78 (Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/conversation/__init__.py", line 318, in websocket_hass_agent_debug
    await agent.async_recognize(
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 186, in async_recognize
    if trigger_result := await self._match_triggers(user_input.text):
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/conversation/default_agent.py", line 881, in _match_triggers
    for result in recognize_all(sentence, self._trigger_intents):
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 507, in recognize_all
    for maybe_match_context in maybe_match_contexts:
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 1082, in match_expression
    group_contexts = [
                     ^
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 1074, in match_expression
    yield from match_expression(settings, context, item)
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 1082, in match_expression
    group_contexts = [
                     ^
  File "/usr/local/lib/python3.12/site-packages/hassil/recognize.py", line 1363, in match_expression
    raise MissingRuleError(f"Missing expansion rule <{rule_ref.rule_name}>")
hassil.recognize.MissingRuleError: Missing expansion rule <numeric_value_set>
Logger: frontend.js.latest.202402070
Source: components/system_log/__init__.py:306
First occurred: 9:58:03 AM (1 occurrences)
Last logged: 9:58:03 AM

Uncaught error from Firefox 121.0 on Linux x86_64 ReferenceError: can't access lexical declaration 'i' before initialization unsub (src/dialogs/voice-command-dialog/ha-voice-command-dialog.ts:390:12) callback (node_modules/home-assistant-js-websocket/dist/connection.js:23:33) forEach (node_modules/home-assistant-js-websocket/dist/connection.js:15:25)

Didgeridrew avatar Feb 07 '24 15:02 Didgeridrew

There seems to be a missing/broken dependency in your HA instance: home-assistant-intents. How are you running HA?

tetele avatar Feb 07 '24 15:02 tetele

@Didgeridrew What language code were you using for the custom sentences?

synesthesiam avatar Feb 07 '24 17:02 synesthesiam

@tetele

How are you running HA?

HA OS on x86

System Health Output ## System Information
version core-2024.2.0b11
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.1
os_name Linux
os_version 6.1.74-haos
arch x86_64
timezone America/New_York
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 5000
Installed Version 1.34.0
Stage running
Available Repositories 1391
Downloaded Repositories 76
AccuWeather
can_reach_server ok
remaining_requests 45
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 11.5
update_channel beta
supervisor_version supervisor-2024.01.1
agent_version 1.6.0
docker_version 24.0.7
disk_total 234.0 GB
disk_used 183.1 GB
healthy true
supported true
board generic-x86-64
supervisor_api ok
version_api ok
installed_addons Duck DNS (1.15.0), Terminal & SSH (9.8.1), Vaultwarden (Bitwarden) (0.21.1), Home Assistant Google Drive Backup (0.112.1), Mosquitto broker (6.4.0), Grocy (0.21.0), SQLite Web (4.1.1), Portainer (2.0.0), ESPHome (2023.12.9), Node-RED (17.0.5), Calibre (7.4.0), Samba share (12.2.0), Music Assistant BETA (2.0.0b92), File editor (5.7.0), Studio Code Server (5.15.0)
Dashboards
dashboards 7
resources 55
views 40
mode storage
Recorder
oldest_recorder_run January 30, 2024 at 5:40 PM
current_recorder_run February 7, 2024 at 10:52 AM
estimated_db_size 977.46 MiB
database_engine sqlite
database_version 3.44.2

@synesthesiam

What language code were you using for the custom sentences?

language: en

I do have both en and es directories, but I never got around to actually setting up a Spanish assistant or any custom intents or sentences.

Didgeridrew avatar Feb 07 '24 20:02 Didgeridrew

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Issue self-resolved with 2024.5

Didgeridrew avatar May 14 '24 16:05 Didgeridrew