Starting MyCroft / PiCroft

Hi,

sharing some initial experiences of setting up MyCroft on a Raspberry Pi3 aiming for integrating it with [AgoControl], my home control system that is active at the moment.

  • configuration of MyCroft seems to have changed in syntax (originally not JSON?). At least I learned that WeatherSkill needs to be configured with

    “WeatherSkill”: {
    “api_key” : “XXXXXXXXXXXXXX”
    },

the documentation provides a slightly different syntax.

Further had some difficulties in getting the Google credentials correctly dropped into the config file. Getting the errors identified took some time as error reporting was not providing the right clue. Good news, it works now. This is the way it should like like when using google cloud STT:

“stt”: {
“module”: “google_cloud”,
“google_cloud”: {
“credential”: {
“json”: {
“type”: “service_account”,
“project_id”: “my-project-111111111”,
“private_key_id”: “0e22222222222222222222222222222222222222222222222222”,
“private_key”: “-----BEGIN PRIVATE KEY-----\nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\n-----END PRIVATE KEY-----”,
“client_email”: “starting-account-7777777777777777777777777@my-project-5555555555555555555555.iam.gserviceaccount.com”,
“client_id”: “1111111111111111111111111111111111111111”,

    }
  }
}

},

The json part is what you receive when creating a google service account key (BTW, had to remove some lines in the part that you receive from Google to allow this post to be posted in the first place).

Getting Google Cloud STT to work meant making some changes in the “speech recognition” package. This concerns at least the version loaded automatically (version 3.7.1). Changes required are related to “sampleRate” → “sampleRateHertz” and changing the API version from “v1beta1” to “v1”.

First results in integration with AgoControl have been achieved, lights can be turned on and off, sensor values can be articulated.

Will be continued

Thanks for the update! We’d be very interested in how you progress.