Bugzilla – Bug 1170777
mycroft plasmoid doesn't work - can't connect or respond to speech
Last modified: 2020-05-25 07:23:25 UTC
Installed package mycroft-plasmoid, expected behavior is to open plasmoid and say "Hey Mycroft, pair my device" and get a 6-digit code to input in my account on website home.mycroft.ai.
No response to voice input, for that matter no response to typed input.
Investigating, contents of /usr/share/plasma/plasmoids/org.kde.plasma.mycroftplasmoid/contents/code/startservice.sh are as follows:
However, there's np directory home/gef/mycroft-core, nor any file named start-mycroft.sh anywhere on my system per kfnd. Reviewing the file list for package mycroft-core, I don't see it listed.
Behavior has changed slightly; when I it the slider, mycroft reports connected instead of connection error, but still doesn't pair. Not sure why the change, but as I have been trying to get alternatives to work, I may have updated some component. (One of those alternatives is a git-based install of current version of mycroft, albeit without graphical interface. That version works, sort of, but doesn't understand much of what I say.)
And now it's actually working the plasmoid, after I go into ~/mycroft-core from the git-based install and run ./start-mycroft.sh. Certain functionality is absent, like "Hey Mycroft, open firefox" or any other program does nothing. Looking through the menu of skills in the plasmoid, the only one I see that looks relevant is plasma-mycroft-applet-control, and when I click to install, mycroft reports it doesn't exist.
While a good voice assistant is an important accessibility aid for some people, mycroft still seems to be at the proof-of-concept stage, insufficiently accurate in its speech-to-text to serve that purpose. Going to dictation.io website, I get much better accuracy, even though it's supposedly using the same stt engine as mycroft (google's). Therefore I agree with the low priority assigned to my report.