built in intent taking over by mistake

[fairbanksbs]

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[bot]]

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]

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.

[issue-triage-workflows[bot]]

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.