-
Notifications
You must be signed in to change notification settings - Fork 13
How do I enable chatbot failback? #2
Comments
I agree, this doesn't seem to work on my mycroft installation either (unless it falls back to AIML only if there's no Internet connection). I assume it was meant to provide conversational responses in the case that a command doesn't match, but all I get is "Sorry, I didn't catch that. Please rephrase and try again." |
Hi, this was disabled (in a hard way) back in August when we had some memory issues associated with this skill. I've been meaning to re-enable it now when we've gotten that issue resolved but I've not gotten around to it. I'll make an update to enable this in the skill settings on home.mycroft.ai during the week. |
#7 will fix this |
Enable AIML Fallback
I'm trying to use Mycroft git/dev with fallback-aiml/master and "Enable chatbot fallback" set via skill configuration on Mycroft Home. The fallback doesn't seem to work. Is this a known issue? As I'm new to Mycroft - could you give me a hint, how to debug the problem? I didn't see anything wrong in /var/log/mycroft/skills.log so far. |
I am also looking to get this skill working, Any input from the author would be appreciated |
Hi @th3r00t sorry for the delay in answering. There was an issue due to a change on how boolean settings were reported which made this skill never activate. This was resolved in #19, the update is still pending in mycroft-skills repo so it won't be upgraded unless you ask mycroft to install the beta version. |
Team,
Platform: Ubuntu server 17.10
Step 1: Install Mycroft in /home - ~/mycroft-core using git clone method
Step 2: Install skill in skills directory & add my own AIML files
Step 3: launch & attempt to start chatbot - no idea how to start the chatbot.
The text was updated successfully, but these errors were encountered: