Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

built in intent taking over by mistake #115706

Open
fairbanksbs opened this issue Apr 16, 2024 · 2 comments
Open

built in intent taking over by mistake #115706

fairbanksbs opened this issue Apr 16, 2024 · 2 comments

Comments

@fairbanksbs
Copy link

fairbanksbs commented Apr 16, 2024

The problem

a conversation put in a specific build up is triggering a built in intent instead of the custom one

What version of Home Assistant Core has the issue?

core-2024.4.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

conversation

Link to integration documentation on our website

https://www.home-assistant.io/integrations/conversation/

Diagnostics information

intent_results.json

Example YAML snippet

custom_sentences/nl/customfancontrol.yaml:
language: "nl"
intents:
  CustomFanControl:
    data:
      - sentences:
          - "(schakel|zet|stel) [de ]ventilator [in ][de ]{area} [op ]{snelheid}"
          - "(schakel|zet|stel) [de ]{area} ventilator [in ][op ]{snelheid}"
        response: "customfancontrol"
responses:
  intents:
    CustomFanControl:
      customfancontrol: "Whatever"
lists:
  snelheid:
    values:
      - in: "langzaam"
        out: "Langzaamst"
      - in: "gemiddeld"
        out: "Gemiddeld"
      - in: "medium"
        out: "Gemiddeld"
      - in: "snel"
        out: "Snelst"
      - in: "uit"
        out: "Uit" 

configuration.yaml:
intent:
conversation:
intent_script:
  CustomFanControl:
    action: []

Anything in the logs that might be useful for us?

No response

Additional information

Tested together with tetele on Discord. He said he can remember the custom ones taking precedence but he is unsure about that and if so, if that may have been broken by or purposefully changed with the latest updates.

@home-assistant
Copy link

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)

@tetele
Copy link
Contributor

tetele commented Apr 16, 2024

IIRC, the custom sentences should have overridden the build-in sentences, which seems to be the gist of the problem here.

Here is a link to our debugging thread on Discord.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants