Some thoughts on Picroft

First I want to say that I really want mycroft/picroft to work, and the problems I am having are undoubtedly due to operator error, but if I am having trouble then I suspect others will too.

  1. I have a raspberry pi audio hat that does not seem to work very well. I have to talk quit loudly and very close to picroft before he responds

  2. I can’t get emby to work at all

  3. Since yesterday, no matter how many times I plug it in picroft says ‘please wait a moment while I reboot’ but never does.

  4. Now It does not work at all. I imagine I will have to copy the image again onto the micro sd for the umpteenth time

I only want to be helpful here.



aaron57, I share some of your pain. Maybe not in the exact same ways, but similarly. Some of it may be operator error, but I don’t think it all is.

I have a Picroft with the latest stable version (September 2018). I have re-imaged it several times as well. It always takes tweaking with the audio drivers to make it functional. This was discussed and recognized as an issue several months ago, but no updated stable version has been released.

  1. I don’t have audio issues like yours. Mine is almost the opposite. It triggers on all sorts of works that are no where near to “Hey Mycroft”. I switched to “Hey Jarvis” and it still triggers as I listen to videos, online classes, podcasts, etc.

  2. I don’t use emby, but Pandora is functional for me.

  3. I had the “please wait a moment” issue a few days ago and was able to tinker with it following the forum topic: Skills not loading / Please wait a moment as I finish booting up.

  4. Bummer. I have been there, too.

Some other issues:
After a reboot, the volume level is usually at zero and I have to reset.

Skills frequently get left behind with upgrades and changes. First was the upgrade to Python 3 and several skills that were useful stopped working. Then the upgrade to 19 left the podcast-skill and the Internet Radio skill behind. I realize that these are user developed and probably not officially recognized, but it still is no fun to find something useful fall by the wayside with no work-around. Probably just a result of the open source nature of the project.

The effort required to make things work, while OK for hobbyists, gets old after a while. Having to check the Documentation, then the Community Forum and the Mattermost channels to find tips and tricks for normal functioning is frustrating and time consuming. Plus, if you have to reimage, you have to go through it all again.

I, too, really want to make it work and usually tolerate the chaos, but from time to time have to leave it alone to regain sanity.

Hi there,

Apologies for a delayed response Aaron, not sure how I missed this thread.

Picroft is a fantastic DIY kit but it does have its challenges. Audio issues are of course top of that list. With the wide range of audio devices it is not possible for us to support them all. Even with well established hardware like the Google AIY Kit we sometimes run into trouble, and because these rely on both Mycroft and 3rd party software, we cannot control if something is going to break.

I’ve been thinking about how we can improve our documentation to better direct people to the guides and fixes that the community have posted. As you said, sifting through the many threads here and in Chat can be a hair puller, it would be good to draw them out and incorporate them into our main docs or at least link directly to them from a central source.

In terms of stability and breaking changes, I can confidently say that from 19.02 onward, Mycroft will be far more stable now that we have a much more mature core. I know Steve is also very keen to get a new 19.02 Stable Picroft image out as soon as he can find a few spare moments.

Particularly through it’s early days, Mycroft has been evolving extremely rapidly and this does at times mean that certain breaking changes must be made. We try where ever possible to provide backwards compatibility and flag things that will be deprecated six months in advance to give time for people to make necessary changes, but this can never work 100% of the time and requires skill authors to put work into something they may have not thought about for a while. One of the great things about our model is that currently all Skills in the Marketplace must have an open license, so if something does stop working, even if an author is no longer around, anyone can fork the Skill and re-purpose it how they want. This is one of the strengths but also one of the challenges of open source - with great power comes great responsibility…

A few more specific things that got mentioned:

  • Hey Mycroft is likely to be the best performing wake word as it has the most number of people contributing to the Open Dataset and tagger samples. This may vary as the team tries various optimisations but should become more consistent over time.
  • For default audio levels, you can add a default level to your volume skill via mycroft.conf though I’m wondering if we should add it as a setting through
"VolumeSkill": {
    "default_level": 6

Overall I’m glad that people can raise these frustrations openly here, and hopefully we can find some better ways to handle the pain points that do arise.

1 Like