Before, I had same problem about wag_tail function in chat-gpt.
But, I could fix it by changing line#62 in action_flow.py file in /home/pidog/pidog/gpt_examples folder. Just put underline instead of space.
Before Change : “wag tail”
After Change : “wag_tail”
Same way for other 2 words commands such as “turn right.”
Sorry if my understanding was wrong.
1 Like
I’m Having this issue as well: PiDog does everything it’s supposed to in the /examples/ directory and is responsive to keyboard input for GPT, but just stays in ‘listening’ / teal lights state when I talk to it verbally while running gpt_dog. I’ll attach screenshots of my errors when running i2samp.sh | Note, the speaker test seemed to work, but gpt_dog script still can’t hear me.
Errors: In the screenshot you see errors related to /usr/bin/dpkg error code 1 for JQ and sox, but this also occurs for alsa-utils, pulseaudio, and pulseaudio-utils.
Then you see the ‘no robothat found’ that probably resuls from it. I tried the advice given earlier in the thread to enable i2c service, but that did not fix it even after restarting twice.
Thanks for any help
The problem is indeed with “wag tail” and “wag_tail”, gpt doesn’t return the expected “wag tail” according to the hints, so it doesn’t match the action correctly, maybe including “wag tail” in the OPERATIONS would be a solution!
We did not reproduce your problem, what system are you using? We are testing with Raspberry OS (64bit) 2024-11-19
Did you follow our tutorials in order.
Yes. You are right. It is a matter how we wrote action name in the open-ai OPERATION.