Replies: 2 comments · 6 replies
-
try adding this to your config file
when running in docker theres some extra large messages that crash the bus if you dont allow larger sizes documented here but perhaps not obvious its still needed even without using the GUI (the messages are sent regardless of something listening to them) https://openvoiceos.github.io/ovos-docker/getting-started/docker/installation/gui/ |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks for the hand. Unfortunately that didn't solve the problem, I'm getting the following in the debug log now:
Here's my mycroft.conf file in case I'm missing something:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
I have not seen "skills": as apart of mycroft.conf. May you send me your reference to why you wrote your "skills": config like that? I'm trying to get my own skill to work. |
Beta Was this translation helpful? Give feedback.
All reactions
-
the error about the websocket crashing went away, the latest logs seem like skill isnt loaded at all? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Sorry, yes you're right, the websocket problem went away but the skill still isn't being called. When I call |
Beta Was this translation helpful? Give feedback.
All reactions
-
some error log on the startup of core about the skill not loading maybe? does any of the 3 skills work at all? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hmm I'm pretty sure the fallback skill works because it says something along the lines of "I don't quite understand" whenever I call
But it says that the skill was loaded successfully. If it helps I'm trying to run it on windows using WSL2. |
Beta Was this translation helpful? Give feedback.
All reactions
-
How are you installing this skill? Did you pip install it? Is it from a generated example or a template repo? When I've seen this in the past, there's something wrong with the skill code and it won't load, but the logs aren't passed to the OVOS logs. You can validate this by opening a Python REPL and importing your skill class, then calling it. Example: from skill_ovos_hello_world import MyHelloWorldSkill # Example only, replace with the appropriate package name and class name
MyHelloWorldSkill() |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm new to ovos and I wanted to run it using docker. I have an issue whenever I call a skill using
mana say-to "hello world"
or STT where instead of calling the skill I want it calls the fallback skill instead because I assume it is being interrupted somehow. Right now I'm trying to run the skills under the ovos_core container because I eventually want to move from my PC to a RPi4. Here is the log of the error:If any other logs or information is required, I would be happy to provide them.
Cheers
Beta Was this translation helpful? Give feedback.
All reactions