ovos-personal-backend VS ovos-core

Trying out OVOS on my Mark II, and using the ovos-personal-backend on a docker container. I noticed that there is a ovos-backend-manager project and wernt to roll my own docker container for it, but noticed that it is already installed via the ovos-personal-backend Dockerfile https://github.com/OpenVoiceOS/ovos-personal-backend/blob/dev/Dockerfile

MycroftAI : Does seem to be going away - They are currently winding down operations. Apparently the local-only OpenVoiceOS personal backend will also work as a backend for Mycroft - that repo has a Dockerfile. I haven't used Selene or the OVOS personal backend but would sway towards the OVOS solution.

some great responses here already, if you want to verify what information is sent you can also install the mock-backend. the logs will show you exactly what is being sent.

Check out OVOS.

I used to work for Mycroft, so I'm hoping to eventually create an image that's compatible with Home Assistant pipelines.

For now, though, you may want to check out OVOS: https://openvoiceos.com/

Blast you're so right! I already ordered an M92, but when LLaMA takes off for voice assistants and I max out my RAM I shall have a think about that HP G2!! With one of those maybe I could have enough RAM to run openbsd and have several VMs running on it! Thank you :D

The upper NUC is running a manual install of ovos-core with sound output through the 22" touchscreen monitor and a kinect V1 as a microphone.

Good news, everyone! As those of you who are following OpenVoiceOS GoFundMe campaign may already have spotted, we've surpassed our most recent fundraising target, and set a new one. Our current stretch goal is a doozy. We're looking to give the Assistant a personality! More specifically, a configurable personality, to make your Assistant that much more... yours.

However it did not work for me out-of-the-box. I had to create some custom Dockerfiles to make adjustments to some of the images before all of them would start up correctly. i got around the Rapidfuzz issue you ran I to using the fix described here: https://github.com/OpenVoiceOS/ovos-core/issues/267

OVOS : There's a Dockerfile in the core repo that you should be able to use to make a Docker image for headless OVOS-Mycroft. You'd probably still have to set up the personal backend for it - not sure as I haven't set it up yet. This is likely the voice assistant replacement route that I'm going with, when there is time to do it.