This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
No intents were loaded for language: * #29
Comments
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.
|
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
added a commit
that referenced
this issue
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.
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 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
HA logs show:
Originally posted by @maxi1134 in #26 (comment)
The text was updated successfully, but these errors were encountered: