Sorry if I’m being unclear or if that question has already been answered (and sorry, my technical competence is very low).
I installed Picroft on a Raspberry Pi 3B+ with a Jabra 410 Speaker, did the little tweak found here (No Audio Output on Picroft with Jabra 410), and, after running after a few errands, wiped it and did the whole process again.
Now, Mycroft only works if I ssh in it via Putty. In fact, as soon as I use CTRL + c to run a command or leave Putty, Mycroft stops working.
So you can only talk to it when you ssh in or does it only work via command line? Does it drop you directly to the command line interface or do you have to run through the setup questions each time? What’s in the logs (/var/log/mycroft/*)?
Hello! Thank you for your answer, and sorry for my imprecision.
When I ssh into it, it works normally and I can talk to it. I can also talk to it via command line.
Each time I ssh into it, it seems to reinitialize itself and restart all of it’s skills (see pictures 1 & 2).
I’m sorry in advance for my next questions : do you need all the logs of the audio, bus, enclosure, skills and voice logs? If so, how can I do this (because there seems to be a lot of data in those files)?
Can I check, Mycroft won’t respond at all until you SSH into the Picroft?
Sometimes Picroft can take a while to do its initial boot for example if it finds a system update (and your system is set to auto update). It looks like you are using the dev branch which means you will be downloading an update most days of the week.
Alternatively is the issue that after SSH’ing in, if you quit the CLI using Ctrl+C it doesn’t respond until you restart the CLI using mycroft-cli-client?
Exactly : Mycroft won’t respond at all until I SSH into it. And if I quit che CLI using Ctrl+C, it doesn’t work either. I admit I did not try to restart the CLI ; I could try that to see if Mycroft starts working again when I come back from work.
I tried waiting for a long time (10+ minutes) to see if it was just a long booting sequence, but it didn’t work.
I can still format the SD card and reinstall Picroft completely, but was hoping to find a less drastic solution (and to understand what happened!)
When your Picroft boots it should create a shell session and launch all of the mycroft services as well as the CLI. SSHing in creates a new shell session and connects to the existing Mycroft processes.
It sounds like your boot sequence isn’t launching the services after startup and hence this is done when you SSH in. Exiting the CLI is then terminating the running processes.
Are you able to plug your Picroft into a monitor to see what happens when it boots?
It would also be useful to check the logs after booting but before you SSH in to see if there’s anything useful in there. To make it easier to search, I’d delete or backup your existing logs first:
SSH in to Picroft
rm /var/log/mycroft/*
or mv /var/log/mycroft/* /some/other/directory/
sudo reboot
Wait for it to boot
From your local machine - using the IP of your Picroft: scp pi@192.168.*.*:/var/log/mycroft/* /path/to/local/dir/
Was there any resolution to this post? I am having pretty much the very same problem.
I have Picroft running on a Pi 3A, a Sabrent USB Controller. When the unit boots I don’t hear the I am ready skill. However when I ssh in, CTRL+C and then issue mycroft-start debug it works perfectly. The microphone is responsive and all the audio works well.
However the second I log out of the terminal window, that’s it, if it was playing the news it terminates and the PiCroft doesn’t work.
After digging with a screen, I found that in my case it was related to the detection mecanism for internet connection ( auto_run.sh ping for 1.1.1.1 to check internet connection ) that is not working with my custom internet setup (ICMP not allowed).
So it was waiting for internet connection setups, rather than starting mycroft.
when connecting through SSH it bypassed this check, and it works.
Workaround : disable internet check by directly return 0 at start of function “network_setup”
How is this done? I am have the same issue. If putty is focused, mycroft hears the wake word and responds. Else it just ignores me. I’ve tried factory reset and it’s still doing this.
edit: evidently this post was flagged by its recipient as “spam”, causing it to be hidden. In the future I should be clearer up front: OVOS is the surviving Mycroft project, and NeonAI is the surviving company offering Mark II support. We are not attempting to migrate users away; we are trying to migrate them to software which is still being maintained.
Fair enough. “Factory reset” threw me off. I’m sorry for the drive-by, but my best advice is that Picroft is no longer being maintained, and has not been updated in years. Information about the future of this community is forthcoming; between Neon and OVOS (I realize you might not have heard of us yet) we have several options for a DIY smart speaker, all running a descendant of the Mycroft version from Picroft.
OpenVoiceOS comes in a few flavors, two of which are developed directly against the Pi4. NeonOS is a Debian-based system, also targeting the Pi4. These will be the actively-developed smart speakers moving forward.
It wasn’t our intention when it was created, but OpenVoiceOS became a third-party replacement for Picroft some years ago (active thread at this forum dating back to 2018) and, although it’s a particularly awkward moment in our journey, can be found at https://openvoiceos.com/.
Sorry, this was not meant to be an advertisement, but direction. I may not have made myself clear.
MycroftAI is kaput. OVOS is creating an open source foundation in order to take over and continue development. NeonAI has formally taken over Mark II support from Mycroft.
As far as we know, the original company only exists anymore in order to wind down its operations. We are the surviving Mycroft projects. NeonClary is the new forum moderator.
Adding a moderator comment here to affirm that this is not spam. @ChanceNCounter and the OVOS team are putting a lot of work into community support on here. Though it’s the “Mycroft” forum, it’s no longer managed by the Mycroft company.
I have removed the flag, and raised all the user “trust levels” for the OVOS team to the highest level - “leader”. That’s a feature many folks don’t notice at first, but you may find it helpful to consider when evaluating a reply or post.
Thanks for joining the forum, I hope you have an excellent experience with your voice assistant.
