OwO is a hackable open source voice assistant.
First, get the code on your system! The simplest method is via git (git installation instructions):
cd ~/git clone --depth=1 https://github.com/OwOAI/OwO-core.gitcd OwO-corebash dev_setup.sh
This script sets up dependencies and a virtualenv. If running in an environment besides Ubuntu/Debian, Arch or Fedora you may need to manually install packages as instructed by dev_setup.sh.
NOTE: The default branch for this repository is 'dev', which should be considered a work-in-progress. If you want to clone a more stable version, switch over to the 'master' branch. NOTE: If you are willing to contribute to this project, clone the entire repository by
git clone https://github.com/OwOAI/OwO-core.gitinstead ofgit clone --depth=1 https://github.com/OwOAI/OwO-core.gitwhich is said above.
OwO provides start-owo.sh to perform common tasks. This script uses a virtualenv created by dev_setup.sh. Assuming you installed OwO-core in your home directory run:
cd ~/OwO-core./start-owo.sh debug
The "debug" command will start the background services (microphone listener, skill, messagebus, and audio subsystems) as well as bringing up a text-based Command Line Interface (CLI) you can use to interact with OwO and see the contents of the various logs. Alternatively you can run ./start-owo.sh all to begin the services without the command line interface. Later you can bring up the CLI using ./start-owo.sh cli.
The background services can be stopped as a group with:
./stop-owo.sh
OwO AI, Inc. maintains a device and account management system known as OwO Home. Developers may sign up at: https://home.owo.ai
By default, OwO-core is configured to use Home. By saying "Hey OwO, pair my device" (or any other request verbal request) you will be informed that your device needs to be paired. OwO will speak a 6-digit code which you can entered into the pairing page within the OwO Home site.
Once paired, your unit will use OwO API keys for services such as Speech-to-Text (STT), weather and various other skills.
OwO is nothing without skills. There are a handful of default skills that are downloaded automatically to your /opt/OwO/skills directory, but most need to be installed explicitly. See the Skill Repo to discover skills made by others. And please share your own interesting work!
Pairing information generated by registering with Home is stored in:
~/.OwO/identity/identity2.json <-- DO NOT SHARE THIS WITH OTHERS!
OwO configuration consists of 4 possible locations:
OwO-core/OwO/configuration/owo.conf(Defaults)- OwO Home (Remote)
/etc/OwO/owo.conf(Machine)$HOME/.OwO/owo.conf(User)
When the configuration loader starts, it looks in these locations in this order, and loads ALL configurations. Keys that exist in multiple configuration files will be overridden by the last file to contain the value. This process results in a minimal amount being written for a specific device and user, without modifying default distribution files.
If you do not wish to use the OwO Home service, you may insert your own API keys into the configuration files listed below in configuration.
The place to insert the API key looks like the following:
[WeatherSkill]
api_key = ""
Put a relevant key inside the quotes and OwO-core should begin to use the key immediately.
These are the keys currently used in OwO Core:
Many schools, universities and workplaces run a proxy on their network. If you need to type in a username and password to access the external internet, then you are likely behind a proxy.
If you plan to use OwO behind a proxy, then you will need to do an additional configuration step.
NOTE: In order to complete this step, you will need to know the hostname and port for the proxy server. Your network administrator will be able to provide these details. Your network administrator may want information on what type of traffic OwO will be using. We use https traffic on port 443, primarily for accessing ReST-based APIs.
If you are using OwO behind a proxy without authentication, add the following environment variables, changing the proxy_hostname.com and proxy_port for the values for your network. These commands are executed from the Linux command line interface (CLI).
$ export http_proxy=http://proxy_hostname.com:proxy_port
$ export https_port=http://proxy_hostname.com:proxy_port
$ export no_proxy="localhost,127.0.0.1,localaddress,.localdomain.com,0.0.0.0,::1"If you are behind a proxy which requires authentication, add the following environment variables, changing the proxy_hostname.com and proxy_port for the values for your network. These commands are executed from the Linux command line interface (CLI).
$ export http_proxy=http://user:password@proxy_hostname.com:proxy_port
$ export https_port=http://user:password@proxy_hostname.com:proxy_port
$ export no_proxy="localhost,127.0.0.1,localaddress,.localdomain.com,0.0.0.0,::1"This is an open source project and we would love your help. We have prepared a contributing guide to help you get started.
If this is your first PR or you're not sure where to get started, say hi in OwO Chat and a team member would be happy to mentor you. Join the OwO Forum for questions and answers.