Open mikejgray opened 1 year ago
Looks like version mismatches. I'm doing a lot of reinstalling to make things work.
I have exactly the same issue!
I tried nuking the .venv
folder and starting fresh, but no luck. I'm wondering if there's a lack of version pinning somewhere in either the skills, this repo, or one of the other core dependencies. Not quite sure where to start unraveling that, though.
The weird thing is, that it worked for quite some time on my DevKit. I made the setup for mimic3 and it seemed to work until one of the reboots afterwards.
Still having this same issue. I thought it might have been a problem with fann2 or padaos, but after scping the wheels for both from a working Picroft it still failed.
Found it - quantulum3, which is required by homeassistant, causes this problem. pip uninstall quantulum3
will get the system back to working order. Now, as to why...that's still unknown. :)
FWIW, quantulum3 is optional for the homeassistant skill, so uninstalling it has no significant negative impact.
Describe the bug I tried (unsuccessfully) to install Mimic3 on my Picroft and now I can't get Mycroft to properly parse via Padatious.
To Reproduce Steps to reproduce the behavior:
Incorrectly install Mimic3 on a Picroft Raspberry Pi 4 machine Try to use Mycroft for anything at all (I tested with "what time is it" and "tell me a joke")
Expected behavior The STT should get passed cleanly to Padatious, not turn into gibberish (
'\\~?(?
)Log files If possible, add log files from
/var/log/mycroft/
to help explain your problem.Splicing together
voice.log
andskills.log
gets you:You may also include screenshots, however screenshots of log files are often difficult to read and parse.
If you are running Mycroft, the Support Skill helps to automate gathering this information. Simply say "Create a support ticket" and the Skill will put together a support package and email it to you.
Environment (please complete the following information):
Additional context Add any other context about the problem here.
Please think carefully about whether you have modified anything in Mycroft's code or configuration files. If so, can you reproduce this on a clean installation of Mycroft? Many "bugs" turn out to be non-standard configuration errors.