Table of Contents generated with DocToc
- Nightscout Alexa Plugin
To add Alexa support for your Nightscout site, here's what you need to do:
- Activate the
alexaplugin on your Nightscout site, so your site will respond correctly to Alexa's requests. - Create a custom Alexa skill that points at your site and defines certain questions you want to be able to ask. (You'll copy and paste a basic template for this, to keep things simple.)
To add Alexa support for a plugin, check this out.
- Your Nightscout site needs to be new enough that it supports the
alexaplugin. It needs to be version 0.9.1 (Grilled Cheese) or later. See updating my version if you need a newer version. - Add
alexato the list of plugins in yourENABLEsetting. (Environment variables are set in the configuration section for your monitor. Typically Azure, Heroku, etc.) - The Alexa plugin pulls its units preferences from your site's defaults. If you don't have a
DISPLAY_UNITSentry, it will default tomg/dl. If you want it to use mmol/L, make sure you have aDISPLAY_UNITSline, and set it tommol(notmmol/l).
- Sign up for a free Amazon Developer account if you don't already have one.
- Register your Alexa-enabled device with your Developer account.
- Sign in and go to the Alexa developer portal.
- Select "Alexa Skills Kit" in the main menu bar.
- Click the "Start a Skill" button. This will take you to the Skills console.
- Click the "Create Skill" button on the Skills console page.
- Name your new skill "Nightscout" (or something else, if you like). Use English (US) as your language. Click "Next".
- Choose a model to add to your skill. Click "Select" under "Custom" model, then click "Create skill" on the upper right.
- Congrats! Your empty custom skill should now be created.
Your Alexa skill's "interaction model" defines how your spoken questions get translated into requests to your Nightscout site, and how your Nightscout site's responses get translated into the audio responses that Alexa says back to you.
To get up and running with a basic interaction model, which will allow you to ask Alexa a few basic questions about your Nightscout site, you can copy and paste the configuration code below.
{
"interactionModel": {
"languageModel": {
"invocationName": "nightscout",
"intents": [
{
"name": "NSStatus",
"slots": [],
"samples": [
"How am I doing"
]
},
{
"name": "UploaderBattery",
"slots": [],
"samples": [
"How is my uploader battery"
]
},
{
"name": "PumpBattery",
"slots": [],
"samples": [
"How is my pump battery"
]
},
{
"name": "LastLoop",
"slots": [],
"samples": [
"When was my last loop"
]
},
{
"name": "MetricNow",
"slots": [
{
"name": "metric",
"type": "LIST_OF_METRICS"
},
{
"name": "pwd",
"type": "AMAZON.US_FIRST_NAME"
}
],
"samples": [
"What is my {metric}",
"What my {metric} is",
"What is {pwd} {metric}"
]
},
{
"name": "InsulinRemaining",
"slots": [
{
"name": "pwd",
"type": "AMAZON.US_FIRST_NAME"
}
],
"samples": [
"How much insulin do I have left",
"How much insulin do I have remaining",
"How much insulin does {pwd} have left",
"How much insulin does {pwd} have remaining"
]
}
],
"types": [
{
"name": "LIST_OF_METRICS",
"values": [
{
"name": {
"value": "bg"
}
},
{
"name": {
"value": "blood glucose"
}
},
{
"name": {
"value": "number"
}
},
{
"name": {
"value": "iob"
}
},
{
"name": {
"value": "insulin on board"
}
},
{
"name": {
"value": "current basal"
}
},
{
"name": {
"value": "basal"
}
},
{
"name": {
"value": "cob"
}
},
{
"name": {
"value": "carbs on board"
}
},
{
"name": {
"value": "carbohydrates on board"
}
},
{
"name": {
"value": "loop forecast"
}
},
{
"name": {
"value": "ar2 forecast"
}
},
{
"name": {
"value": "forecast"
}
},
{
"name": {
"value": "raw bg"
}
},
{
"name": {
"value": "raw blood glucose"
}
}
]
}
]
}
}
}Select "JSON Editor" in the left-hand menu on your skill's edit page (which you should be on if you followed the above instructions). Replace everything in the textbox with the above code. Then click "Save Model" at the top. A success message should appear indicating that the model was saved.
Next you need to build your custom model. Click "Build Model" at the top of the same page. It'll take a minute to build, and then you should see another success message, "Build Successful".
You now have a custom Alexa skill that knows how to talk to a Nightscout site.
Now you need to point your skill at your Nightscout site.
- In the left-hand menu for your skill, there's an option called "Endpoint". Click it.
- Under "Service Endpoint Type", select "HTTPS".
- You only need to set up the Default Region. In the box that says "Enter URI...", put in
https://{yourdomain}/api/v1/alexa. (So if your Nightscout site is atmynightscoutsite.herokuapp.com, you'll enterhttps://mynightscoutsite.herokuapp.com/api/v1/alexain the box.) - In the dropdown under the previous box, select "My development endpoint is a sub-domain of a domain that has a wildcard certificate from a certificate authority".
- Click the "Save Endpoints" button at the top.
- You should see a success message pop up when the save succeeds.
Click on the "Test" tab on the top menu. This will take you to the page where you can test your new skill.
Enable testing for your skill (click the toggle). As indicated on this page, when testing is enabled, you can interact with the development version of your skill in the Alexa simulator and on all devices linked to your Alexa developer account. (Your skill will always be a development version. There's no need to publish it to the public.)
After you enable testing, you can also use the Alexa Simulator in the left column, to try out the skill. You can type in questions and see the text your skill would reply with. You can also hold the microphone icon to ask questions using your microphone, and you'll get the audio and text responses back.
Forecast:
- "Alexa, ask Nightscout how am I doing"
- "Alexa, ask Nightscout how I'm doing"
Uploader Battery:
- "Alexa, ask Nightscout how is my uploader battery"
Pump Battery:
- "Alexa, ask Nightscout how is my pump battery"
Metrics:
- "Alexa, ask Nightscout what my bg is"
- "Alexa, ask Nightscout what my blood glucose is"
- "Alexa, ask Nightscout what my number is"
- "Alexa, ask Nightscout what is my insulin on board"
- "Alexa, ask Nightscout what is my basal"
- "Alexa, ask Nightscout what is my current basal"
- "Alexa, ask Nightscout what is my cob"
- "Alexa, ask Nightscout what is Charlie's carbs on board"
- "Alexa, ask Nightscout what is Sophie's carbohydrates on board"
- "Alexa, ask Nightscout what is Harper's loop forecast"
- "Alexa, ask Nightscout what is Alicia's ar2 forecast"
- "Alexa, ask Nightscout what is Peter's forecast"
- "Alexa, ask Nightscout what is Arden's raw bg"
- "Alexa, ask Nightscout what is Dana's raw blood glucose"
Insulin Remaining:
- "Alexa, ask Nightscout how much insulin do I have left"
- "Alexa, ask Nightscout how much insulin do I have remaining"
- "Alexa, ask Nightscout how much insulin does Dana have left?
- "Alexa, ask Nightscout how much insulin does Arden have remaining?
Last Loop:
- "Alexa, ask Nightscout when was my last loop"
(Note: all the formats with specific names will respond to questions for any first name. You don't need to configure anything with your PWD's name.)
If your device is registered with your developer account, you should be able to use your skill right away. Try it by asking Alexa one of the above questions using your device.
This document assumes some familiarity with the Alexa interface. You can find more information here.
To add alexa support to a plugin the init should return an object that contains an "alexa" key. Here is an example:
var iob = {
name: 'iob'
, label: 'Insulin-on-Board'
, pluginType: 'pill-major'
, alexa : {
rollupHandlers: [{
rollupGroup: "Status"
, rollupName: "current iob"
, rollupHandler: alexaIOBRollupHandler
}]
, intentHandlers: [{
intent: "MetricNow"
, routableSlot: "metric"
, slots: ["iob", "insulin on board"]
, intentHandler: alexaIOBIntentHandler
}]
}
};There are 2 types of handlers that you will need to supply:
- Intent handler - enables you to "teach" Alexa how to respond to a user's question.
- A rollup handler - enables you to create a command that aggregates information from multiple plugins. This would be akin to the Alexa "flash briefing". An example would be a status report that contains your current bg, iob, and your current basal.
A plugin can expose multiple intent handlers.
intent- this is the intent in the "intent schema" aboverouteableSlot- This enables routing by a slot name to the appropriate intent handler for overloaded intents e.g. "What is my " - iob, bg, cob, etc. This value should match the slot named in the "intent schema"slots- These are the values of the slots. Make sure to add these values to the appropriate custom slotintenthandler- this is a callback function that receives 3 argumentscallbackCall this at the end of your function. It requires 2 argumentstitle- Title of the handler. This is the value that will be displayed on the Alexa cardtext- This is text that Alexa should speak.
slots- these are the slots that Alexa detectedsandbox- This is the nightscout sandbox that allows access to various functions.
A plugin can also expose multiple rollup handlers
rollupGroup- This is the key that is used to aggregate the responses when the intent is invokedrollupName- This is the name of the handler. Primarily used for debuggingrollupHandler- this is a callback function that receives 3 argumentsslots- These are the values of the slots. Make sure to add these values to the appropriate custom slotsandbox- This is the nightscout sandbox that allows access to various functions.callback-error- This would be an error messageresponse- A simple object that expects aresultsstring and apriorityinteger. Results should be the text (speech) that is added to the rollup and priority affects where in the rollup the text should be added. The lowest priority is spoken first. An example callback:callback(null, {results: "Hello world", priority: 1});