-
Notifications
You must be signed in to change notification settings - Fork 11
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
“<media_id> playing in” returned when no area is requested #45
Comments
Are you using the latest version of the LLM enhanced blueprint? We had added different logic for getting the area info for replies, as well as the ability to customize the replies. The above looks like it may be the old way? |
I made a diff and only found minor differences but pulled the latest version anyway to be certain. I would suggest to add some kind of version string to the blueprint intro to help in troubleshooting:-) Problem persists with the version pulled today. I setup the following response: The following request:
Results in this result from the query (interesting that the correct area is included):
But the reply is:
|
I suspect this is the LLM failing to follow the instructions correctly. Is this a Local model? May also want to check the trace and see how variables changed along the way to see where it failed to properly set the area info. |
I am using ChatGPT without exposing areas to it. The citations above are from a trace. All along the trace I can see that target is set to the correct area_id. In the step "Set variables for responses" the following appears:
I don't find anything in the trace that sets area_info. |
in the trace you'd want to look at the changed variables tab. |
Well, yes. What I posted I took from there. |
When requesting to play without an area specified the LLM enhanced local version plays correctly on the player in the satellite’s area. The reply however is “… is playing in ”. I would suggest that the blueprint should cater for that case by leaving out the area part in the response if none provided.
The text was updated successfully, but these errors were encountered: