Added more information on device pairing, and cleaned up API Key documentation further.
parent
4347e6e4d0
commit
63b09d516f
10
README.md
10
README.md
|
@ -28,14 +28,20 @@ By default the Mycroft software is configured to use Cerberus, upon any request
|
|||
|
||||
Once signed and a device is paired, the unit will use our API keys for services, such as the STT (Speech-to-Text) API. It also uses allows you to use our API keys for weather, Wolfram-Alpha, and various other skills.
|
||||
|
||||
Pairing information generated by registering with Cerberus is stored in:
|
||||
|
||||
`~./mycroft/identity/identity.json` <b><-- DO NOT SHARE THIS WITH OTHERS!</b>
|
||||
|
||||
It's useful to know the location of the identity file when troubleshooting device pairing issues.
|
||||
|
||||
## Using Mycroft without Cerberus.
|
||||
If you do not wish to use our service, you may insert your own API keys into the configuration files listed below in <b>configuraion</b>.
|
||||
|
||||
The place to insert the API key looks like the following:
|
||||
|
||||
`[WeatherSkill]
|
||||
api_key = ""`
|
||||
`[WeatherSkill]`
|
||||
|
||||
`api_key = ""`
|
||||
|
||||
Put the relevant key in between the quotes and Mycroft Core should begin to use the key immediately.
|
||||
|
||||
|
|
Loading…
Reference in New Issue