OpenVoiceOS - A bare minimal (production type of) OS based on Buildroot

Release Spotlight: Backend UI

A benefit to hosting the back end for OVOS is better control over the systems within, no longer relying on another party to uphold promises of privacy or for server uptime. However a drawback comes in the form of it being command line focused, with little in terms of visual feedback. But thanks to the work of @JarbasAl, running a local back end now comes with the ability to monitor and manage it with a UI!

Check out the Github page here: GitHub - OpenVoiceOS/ovos-backend-manager: A simple web UI for personal backend, powered by PyWebIO

What does the UI do for me?

It was possible before to run a local back end for OVOS, but in order to set various settings you would need to do so via a command line. This is a barrier for entry for some people, passing the line of wanting better privacy but requiring too much investment to manage such systems. The user interface for the back end allows people to not only configure settings within the local back end for OVOS, but to also view metrics and information about the system.

OVOS is meant to allow developers to create voice activated systems that respect your privacy. But we also want to enable as many people as possible to partake in this mission. Creating easier to navigate systems plays an important role in allowing people to participate. Raising the bar for FOSS voice activated systems, lowering the barrier for entry.


Announcing: OVOS Community Docs

No project is complete without documentation directing the users how to use said project, and OVOS now has it’s very own Community documentation github page! Check it out here: GitHub - OpenVoiceOS/community-docs: community maintained documentation

What can I find in the docs?

Right now? Well as I write this, it includes sections for understanding what OVOS is, why it was made, what some terms mean, some developer FAQ, some compatibility reading, and some additional reading. But these are community docs, meaning that if someone would like to make additions or changes, they can easily submit a pull request and participate in growing the knowledge base!

What can I contribute to the docs?

Anything and everything you find relevant! The information presented is meant to answer questions users and developers have about the system, whether they’re juts getting started or want to dive deep into the systems and components that makes OVOS tick. Users who wish to make a change can do so via a pull request. We encourage those who want to get involved to feel free to suggest changes and improvements.

How can I get started?

  1. Read the docs
    • Simple as that. Read them and see where that leaves you in terms of understanding.
  2. Contribute where you see fit
    • Create an issue if you have a question, or create a pull request(pr) if you have something to contribute.**
  3. Enjoy.

Call to action

Want to get involved? Check out our website! Find links to our Matrix chat and other information about our work and find ways to get involved!

1 Like

Announcing the Release OVOS 0.0.5

As these dot releases do we find ourselves with a handful of helpful fixes, as well as a plethora of bug fixes. These major changes includes a kick…uh…butt new listening mode!

update to Log location
#210 - ovos-core will now automatically write logs to $XDG_STATE_HOME/mycroft/xxx.log, until now the launcher scripts were responsible for writing and rotating logs, this often caused permission issues or images to suddenly run out of space, we now ensure logs directory is writable and enforce a limit of 50MB for logs, you can see all logging config options here

i’ll be ready in a minute
#211 - mycroft-core had a hardcoded dialog “please wait a moment as i finish booting up”, this was not actually related to the boot process and misleading, ovos-core now plays a error sound instead, other components may reuse the same sound to indicate failures if appropriate. the sound file can be changed under mycroft.conf just like the start_listening and acknowledge sounds

#204 - the helper method ask_yesno was very limited, it has been updated and will now handle things like double negations and changing your mind mid sentence, the logic for this has now been moved to ovos-lingua-franca OpenVoiceOS/ovos-lingua-franca#30

end to the backend
#189 + #201 - backend has now been abstracted away, by default ovos-core uses no backend but multiple backends are supported, check out our new backend docs Backend Services - Documentation

now you listen here
#150 - new experimental listening modes have been added, you can now completely disable wake word or not require it for follow up interactions, this is not enabled by default and should be considered only a preview

Full list of changes can be found on our Github, or just below these words:

Fixed Bugs
Implemented enhancements

Come hangout

Want to get involved? Check out our website at Find links to our Matrix chat and other information about our work!

GUI and Skill Updates For OpenVoiceOS

Some interesting projects to test and run on your OVOS powered images / devices

Home Assistant PHAL Plugin:

Introducing Home Assistant PHAL plugin it provides GUI interfaces and API for Home Assistant Instants. The plugin is in early development, so there are some features that are not yet implemented. It currently supports the following entities:

  • Media Player: Start / Pause / Change Tracks / View Status
  • Light: Turn On / Off / View Status
  • Vacuum: Turn On / Off / View Status
  • Binary Sensor: Status Updates
  • Sensor: Status Updates
  • More device support and features will be added, need community help to get more actual operation data for different type of devices


Available to Install For Testing From:

Routine’s Skill:

A new routines skill is available for testing:

  • Supports create schedules to run utterance one or several action on specific days at specific times
  • GUI and Voice interface to easily add and remove routines
  • A dashboard to view and manage current routines



Available To Install For Testing From:

Food Wizard Skill:

Introducing Food Wizard, a recipes skill, it was a skill around for a while as a demo for GUI API usage, but now has been converted into a fully functional recipes skill.

  • Adds voice and ui supports for ingredients and cooking instructions (cooking instructions for supported recipe providers)


Available To Install For Testing From: