Great to hear you got him working……But the process is not easy.
I did notise that alsamixer were at zerro to - so adding to the script to set it to 75% would be a good idea.
I dont understand why you nedded /home/pi/mycroft-core/dev_setup.sh as I remember that that to is done in the scrpt. I did when I did run it…Strange.
I think the picroft scrit could benefit from a rewrite, so installation of hardware were in differet scripts one for every hardware one will write installation for.
That would make the installation of picroft simpler - get mycroft up and running, and then add hardware. But that is just my opinion.
In picroft-google-aiy-voicekit.andlo/_init_.py, create_skill() creates a new PicroftGoogleAiyVoicehat, but the class is PicroftGoogleAiyVoicekit so loading the skill fails - last word is ‘hat’ vs ‘kit’
I got my AIY kit working, but only when I signin to it. There are no mycroft scripts in /etc/init.d/
What do I need to do to get the startup scripts?
One thing I had to do (like guidol did above) was modify /home/pi/audio_setup.sh to have “amixer set Master 75%” I had to do this as I had no PCM controls (used “amixer scontents” to see what I do have).
Reboot did not fix it. I tried imaging a SD card from picroft 2018-09-12, and it did not have the /etc/init.d scripts still. This time I selected option 1 for the audio setup and I got a PCM decvice. After that, the audio still did not work and I got the same error as others regarding the "aiy-python-wheels: protobuf not supported on armv6.1.
So I started over again:
I imaged a SD card from picroft 2018-09-12
I selected 1) Speakers for the audio
Audio test does not work, but continue since that is fixed later
I selected 3) Google AIY
Wow… this is a lot to follow, but it’s been a couple months since this was updated, and I’m still not having any luck, even following what I think is all the recommendations above. I seem to be stuck with this:
protobuf-3.6.1-cp35-cp35m-linux_armv6l.whl is not a supported wheel on this platform.
In the bootup, I was getting this:
Traceback (most recent call last):
File “/usr/lib/python3.5/runpy.py”, line 183, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File “/usr/lib/python3.5/runpy.py”, line 109, in _get_module_details import(pkg_name)
File “/home/pi/mycroft-core/mycroft/init.py”, line 17, in
from mycroft.api import Api
File “/home/pi/mycroft-core/mycroft/api/init.py”, line 26, in
from mycroft.identity import IdentityManager, identity_lock
File “/home/pi/mycroft-core/mycroft/identity/init.py”, line 21, in
from mycroft.util.combo_lock import ComboLock
File “/home/pi/mycroft-core/mycroft/util/combo_lock.py”, line 16, in
from fasteners.process_lock import InterProcessLock
ImportError: No module named ‘fasteners’
but I did find that I could do:
pip install fasteners
And it got me beyond this - I only bring it up in case it helps refine the initial install script or helps someone else, but I’m not sure where to go from here… From the description, it seemed that the AIY kit hardware was pretty much supposed to be working “out of the box” with the raspbian-stretch_Picroft_2018-09-12 image, but I’m at a loss… Any ideas??
Great to hear you are going The strange thing is I dossnt see same issues when I reflash. OK I havnt reflashed for a monts or so. Yo can open a issue on the gitrepo that you see that module fasteners are missing.
I am just not ure if that is the AIY skill that causes this though. But I will look into it as soon as I reflash again.
GREAT - you done more than needed I think but that is OK.
As you did a git pull you have to run dev_setup.sh as stated. But it is a bit misleading that it says ./dev_setup.sh. That is right when you are in the mycroft-core directory.
So cd /home/pi/mycroft-core and then ./dev_setup.sh or simple just run
~/mycroft-core/dev_setup.sh
`But I think the 9-12 can install the AIY right from the setup wizard. Same whith wifi.
Wait for startup then run ./mycroft-core/dev_setup.sh as long as it tells you and reboot afterwards, eventually it starts into the cli and starts intializing. This takes a while, you should see output and you are asked to register at home.mycroft.ai, do that and wait a while until it stops loading skills.
Ctrl-C and install the AIY skill (you can do that in a different ssh window) and reboot
For sound levels, not sure if you tried this already and it didn’t work, but you can set default a default level for the Volume Skill via mycroft.conf. There’s a short example with the required entries in our docs.