Music Assistant player support for OVOS ( OpenVoiceOS) open-source voice assistant platform?

[Hedda]

Any plans to develop Music Assistant player support for the new OVOS (OpenVoiceOS) open-source voice assistant platform?

• https://www.openvoiceos.org

  • https://www.openvoiceos.org/press

OpenVoiceOS Foundation ("OVOS Foundation" for short) is a new non-profit organization dedicated to advancing open-source voice assistant technology (so it has similar but perhaps more narrower goals to the Open Home Foundation that Home Assistant's founders started). See:

• https://github.com/OpenVoiceOS/

  • https://openvoiceos.github.io/ovos-technical-manual/

Maybe it will be the other way around? Anyway, I understand that OVOS is primary designed to run on Raspberry Pi type SBC hardware:

• https://www.cnx-software.com/2025/02/24/the-openvoiceos-foundation-aims-to-enable-open-source-privacy-and-customization-for-voice-assistants/

@j1nx (Peter Steenbergen) has apparently explained to CNX Software that they have more or less taken over the Mycroft A.I. codebase, as well as the Mycroft community forums which now resides here:

https://community.openconversational.ai

You can read more about the history of the project in the "About" section on their website:

• (https://www.openvoiceos.org/about

OpenVoiceOS is now split into multiple modules:

• ovos-messagebus – The BUS all different modules talk over to each other.
• ovos-core – The main system that handles all skills. Basically the brain of it all and is fully Mycroft A.I. skill compatible.
• ovos-listener – Access to your microphone that handles the keyword, STT, etc… again fully modular by plugins. You can fully choose your wake-word plugin (the default is still “Hey Mycroft”). You can choose any STT plugin of your liking be it on-device, on-premises, or online.
• ovos-audio – Access to your speaker. Plugin-based so the user chooses TTS (on-device, on-premise, or online). Basically everything that relates to sound output.
• ovos-phal – Platform/Hardware Abstraction Layer. A plugin-based system to handle and provide anything from hardware integrations (HATs, The Mycroft A.I. Mark1, The Mycroft A.I. Mark2, etc.) or system integrations (Network manager, Keyboard input, Camera, etc.)
• ovos-gui – The Graphical User Interface. The GUI has been split up into two systems: a bus to extend the messagebus for GUI-related communication and the GUI itself. The default is still the KDE Qt-based GUI, however, vastly falling behind as AIX the lead developer is pursuing other endeavors and there’s no Qt developer within the community any longer. An HTMX version is currently also being worked on as a lightweight alternative and the GUI’s can now even run on completely different devices if wanted.

The project is complemented by HiveMind, a separate project of jarbas, the lead Python developer of the OVOS project, that allows all the different OpenVoiceOS framework modules to be split over multiple devices. Peter explains further:

"This extends the message bus(‘s) to talk over the network with all associated security mitigations involved. This allows for instance to lift all the heavy duty over to a beefy server and have small low resource “satellites” to talk to it. So the core skill/phal systems run on a big server, while on a low-resource device, you just only run the listener for the microphone and the audio for the sound output. The best and most current example would be to run your own Home Assistant Voice cloud server and Home Assistant voice satellite."

PS: Hopefully the OpenVoiceOS Foundation and its voice assistant operating-system also plan to fully support Music Assistant for playback:

• https://www.music-assistant.io

  • https://github.com/music-assistant