Configuration

Configuration

All the configuration of this application is stored in one single file, config.json. Here's how it looks:

{
	"on-start": <ACTION>,
	"on-exit": <ACTION>,
	"on-activation": <ACTION>,
	"on-timeout": <ACTION>,
	"on-command-spoken": <ACTION>,
	"on-reload": <ACTION>,
	"on-wrong-command": <ACTION>,
	"activation-commands": [],
	"timeout": 30,
	"tts": {
		<SETTINGS>
	},
	"stt": {
		<SETTINGS>
	},
	"active-modules": [],
	"modules": {
		<SETTINGS>
	}
}

If you don't have this file or delete it, a version with all the defaults will be restored on next start.

General settings

The "on-XXX" options are triggered if XXX happens and will then execute the action specified. XXX may be:

• "start": When starting the application
• "exit": When stopping the application
• "activation": When speaking the activation command
• "command-spoken": When a correct command was spoken and recognized.
• "wrong-command": When a wrong or illegal command (non-existing command, not recognized correctly, in the wrong state) was spoken.
• "timeout": When speaking the activation command but no actual command for "timeout" seconds. A value of zero will will disable this feature, as well as having no activation command.
• "reload": When reloading the configuration.

"activation-commands" contains a list of all commands that will activate the application. Only after having spoken it, you will be able to tell commands. If you don't, it will deactivate again after "timeout" seconds. If you keep this list empty, the application will always be activated and execute spoken commands. The "timeout" setting will be ignored then.

STT and TTS engine settings

The "tts" and stt entries configure the STT or TTS engine to use. See here (STT) and here (TTS) for more information about which engines exist and how to configure the used engine.

Module settings

modules contains a map of all configured module instances and active-modules is a list of modules that will be used. See here link for more information.