Skip to content
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.

No intents were loaded for language: * #29

Closed
kbromer opened this issue Sep 21, 2024 · 3 comments · Fixed by #30
Closed

No intents were loaded for language: * #29

kbromer opened this issue Sep 21, 2024 · 3 comments · Fixed by #30

Comments

@kbromer
Copy link

kbromer commented Sep 21, 2024

Having the same issue as @maxi1134 on issue #26. The original Home Assistant agent isn't actually loaded (I have Fallback properly configured and going from HA->OpenAI). Even with things HA understands and OpenAI doesn't, I receive no matched intent - this is a new issue that arose, it was working fine pre-update. Like the logged issue, I get this error in my logs:

Logger: homeassistant.components.conversation.default_agent
Source: components/conversation/default_agent.py:229
integration: Conversation (documentation, issues)
First occurred: 5:30:10 PM (10 occurrences)
Last logged: 5:36:50 PM
No intents were loaded for language: *

          I am on 2.0.0;

I reinstalled, Restarted, REmoved and re-added the integration.

I still get: Home Assistant failed with response: Sorry, I couldn't understand that for basic requests

image

HA logs show:

2024-09-17 11:21:07.193 WARNING (MainThread) [homeassistant.components.conversation.default_agent] No intents were loaded for language: *

Originally posted by @maxi1134 in #26 (comment)

@kbromer kbromer changed the title I am on 2.0.0; No intents were loaded for language: * Sep 21, 2024
@zSprawl
Copy link

zSprawl commented Sep 22, 2024

I'm seeing this error as well, but it also shows this message in the logs one time, before showing the above each time you attempt to use the voice control.

Logger: homeassistant.components.conversation.default_agent
Source: components/conversation/default_agent.py:697
integration: Conversation ([documentation](https://www.home-assistant.io/integrations/conversation), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+conversation%22))
First occurred: 9:11:26 PM (1 occurrences)
Last logged: 9:11:26 PM
Unable to find supported language variant for *

@m50
Copy link
Owner

m50 commented Sep 22, 2024

Interesting. I did make a change to the language thing, thinking I was just cleaning things up, but maybe I accidentally changed functionality since it had been a while since I looked at the code. I'll take a look

m50 added a commit that referenced this issue Sep 22, 2024
Change to be MATCH_ALL actually ended up breaking things, rather than cleaning them up
@m50 m50 closed this as completed in #30 Sep 22, 2024
m50 added a commit that referenced this issue Sep 22, 2024
Change to be MATCH_ALL actually ended up breaking things, rather than cleaning them up
@m50
Copy link
Owner

m50 commented Sep 22, 2024

Latest release v2.0.1 will fix it. Just need to edit your voice assistant and resave it to give it it's language back.

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

Successfully merging a pull request may close this issue.

3 participants