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

Home Assistant responded with: Not any #12

Closed
Ricardo-Miguel-Caldeira opened this issue May 21, 2024 · 4 comments
Closed

Home Assistant responded with: Not any #12

Ricardo-Miguel-Caldeira opened this issue May 21, 2024 · 4 comments

Comments

@Ricardo-Miguel-Caldeira
Copy link

Ricardo-Miguel-Caldeira commented May 21, 2024

I can't make the fallback work...
Whenever for a general knowledge question the answer I always get:

Home Assistant responded with: Not any

Fallback

image

Great project and idea! Thank you for your work!

@m50
Copy link
Owner

m50 commented May 21, 2024

That's interesting. It appears that the Home Assistant agent itself is trying to respond to it.

I am able to recreate this myself, but I'm not sure why it's happening. I'll have to look more into it. It appears to be for any question that starts with "Who is...". Repeating the question as "What is..." makes it forward properly.

What I've noticed is that the response_type is normally "action_done", but in this case is "query_answer".

If I had to take a guess, there is a built in intent that is triggering on "Who is [name]", but doesn't really seem to be working as I'd expect (Why does it response with just "Not any", even if you ask about a user on the same system?).

This could be a quirk we could work around, but obviously the workaround would likely only work in English. Testing it in Dutch, it does the same thing (returns "Geen"). However, in German for some reason it passed to ChatGPT correctly. In Spanish it also properly passed to ChatGPT.

Possibly it is a work in progress or partially completed (or possibly scrapped?) built-in Intent, that only has Dutch and English defined? Not sure.

I'll have to look further into this

@freakshock88
Copy link

@m50
Copy link
Owner

m50 commented Jun 28, 2024

That's almost definitely the problem intent. That is frustrating. The intent would likely need to be modified to fix it.

m50 added a commit that referenced this issue Jun 30, 2024
* [fix] #12 Workaround for strange "Not any" response

* Fix issues caused by me writing it like Go

* Lowercase + if agent_names[agent_id] is not found, use unknown

* Have it say 1.0.4
@m50
Copy link
Owner

m50 commented Jun 30, 2024

I implemented a fix in v1.0.4. Can you upgrade and confirm it is fixed for you?

Please note: The only languages that I know this is an issue in is English and Dutch. If anyone knows what the response would look like in other languages, you can create a PR with updating the STRANGE_RESPONSES constant.

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

No branches or pull requests

3 participants