This was great – for about a year, lots of people were boasting about the many, many, many Terabytes of data they had stored on Amazon Drive. For me it was a perfect solution to my cloud backups. I subscribed to ODrive and synced all my working data to Amazon Drive.

Then one day Amazon announced that Amazon Drive for Prime customers would no longer have unlimited storage, and would no longer be free. In fact 1TB of storage would cost $99.99 per year. They had dangled a nice free juicy worm in front of me, I had bitten and now I was well and truly hooked – hook line and sinker.

What choice did I have? All my data was already stored on Amazon Drive so I swore a lot, got out my credit card and paid up.

Another year or so later (2019) it’s time to pay Amazon another 100 bucks and I notice that Amazon Drive is now called Amazon Photos, without really informing their customers Amazon have rebranded it into a photo and video storage service. Not exactly what I expected from a cloud storage solution.

As soon as I discovered Google Drive offering twice the amount of storage (2TB) for the same price I decided it was time to migrate my ODrive from Amazon Drive to Google Drive. The problem is, with almost 1TB of data in the cloud – even with reasonably fast home DSL internet bandwidth how do you move so much data around? To download it all, and then upload it all would take days – and I don’t even have enough disk space on my shiny silver macbook pro to temporarily store it all (the reason why I moved to cloud storage in the first place.)

Here is the solution – How To Migrate your Terabytes in Hours not Days

1. Spin up a bare metal Windows server
   1.  I used a Win2k16 Server on a Packet c1.small.x86c1.small.x86 with super duper gigabit bandwidth.
2. Install the AmazonPhotos app.
   1. Using the Amazon app restore your files to a local folder.
3. Login to Google and upload the restored files to Google Drive.
4. In Odrive unsync Amazon Drive synced folders and resync them to Google Drive
5. FIN.

I moved all of my data in a few hours, and it cost about $30.

Goodbye Amazon, please don’t try and trap me into a shitty service again.

If you are building skills with my PHP code here are a few notes on using the ASK CLI to do simple skill invocation tests using a Docker compose ASK CLI nodejs container.

Assuming you are familiar with using Docker and docker-compose here are the steps to testing your skill from the command line :

1. git clone https://github.com/gaiterjones/docker-amazon-ask-cli
2. cd docker-amazon-ask-cli
3. docker-compose build
4. docker-compose up -d
5. ./init.sh
   1. Initialise ask with your amazon developer credentials, you will be prompted to create a default profile and then to paste an authorisation url into your browser. The url will take you to an Amazon authorisation page where you need to login with your developer login. You will then receive an authorisation code which you can paste into the init window to create your cli-config credentials file.
   2. 
6. Test skill with skill simulation
   1. ./ask.sh amzn1.ask.skill.123 “ask my skill to do something” where amzn1.ask.skill.123 is the id of your skill and “ask my skill to do something” is the invocation term you want to test with your skill – i.e. what you would ask Alexa to do to open and use your skill.
   2. 

Check out ask.sh for the ASK CLI syntax being used. You can use this directly from the container with docker exec -it dockeramazonaskcli_nodejs_1 /bin/bash

The credentials will be saved in cli-config when the container is stopped.

You can do a whole lot more with the ASK CLI, check out the documentation here https://developer.amazon.com/docs/smapi/ask-cli-command-reference.html

Yes, I did just say unlimited storage.

This is pretty neat, but I already use an open source cloud storage system on my own cloud server – called er, Owncloud.  Wouldn’t it be really nifty if I could attach the unlimited Amazon Cloud drive storage to my Owncloud.

Here is how to do it in 5 easy steps:

1. Sign up for an unlimited Amazon Cloud Drive storage plan at https://www.amazon.de/clouddrive
2. Install and configure acd_cli
   1. pip3 install –upgrade –pre acdcli
   2. acd_cli -v init
      1. authenticate with Amazon and save the generated oauth_data file to ~/.cache/acd_cli/oauth_data
3. Sync acd_cli
   1. acd_cli -v sync
4. Mount acd with fuse
   1. acd_cli mount –allow-other -i 0 /home/acd/
5. Create a new external storage folder in Owncloud

   

That’s it, Amazon cloud drive will now appear as an ACD folder in Owncloud.

Is it really unlimited? In their license agreement it says that your service will terminate if your usage “substantially exceeds or differs from normal use by other users”. Be sure to check out the fine print. A quick Google around shows users already at hundreds of terabytes which sounds good to me.

In part one of the Alexa PHP Hello World example I created a very basic skill and a PHP app to show how to handle Amazon Alexa IntentRequest data and provide a response. In part two I will extend the code to allow us to create interactive prompt and responses.

If you are new to Alex skills and PHP read part one of this Hello World example first.

To demonstrate prompt and responses we will ask Alexa for a “clever quote”, Alexa will give us the quote and ask if we want another. If the user replies yes, Alexa reads another quote and prompts again until all the available quotes have been used.

Alexa Prompt and Response

To allow this prompt and response interaction we simply tell our skill to keep the session open when we require a response, and we store the data we need for the session in the session attributes array.

First let’s modify the Hello World skill interaction model :

{
  "intents": [
    {
      "slots": [
        {
          "name": "command",
          "type": "COMMANDOBJECTS"
        },
        {
          "name": "prompt",
          "type": "PROMPTOBJECTS"
        }
      ],
      "intent": "HelloWorld"
    },
    {
      "intent": "HelpIntent"
    }
  ]
}

Now we have command and prompt slots, with command objects and prompt objects to catch our prompt and response utterances. I have also added two new utterances

HelloWorld for {command}
HelloWorld {prompt}

“Clever” quotes

The clever quotes data is an array of sentences stored in Data::cleverQuotes(). We load the data, and then create a list of random numbers we will use as array keys to get random quotes from the array. The list of random array keys will be stored in the session data.

// clever quotes data
//
$_cleverQuotesData=Data::cleverQuotes();
$_cleverQuotesArrayKeys= range(0, (count($_cleverQuotesData)-1));
shuffle($_cleverQuotesArrayKeys);

• alexa ask hello world for clever quotes

In the HelloWorld php intent class I have added some new code to parse the user request for clever quotes. The response includes the first “clever quote” fetched from the array using the first of our random array key numbers and the prompt to the user – “would you like some more clever quotes“. We also set endsession to false to keep the session open and save the random key data and prompt count data we need for the next session.

// response
//
return array(
	'intent' => array(
		'response' => 'Ok, here comes your first clever quote : '. $_cleverQuotesData[$_cleverQuotesArrayKeys[0]]. ' Would you like some more clever quotes?',
		'card' => array(
			'title' => $_target,
			'text' => $_now->format('H:i:s'). ' '. $_cleverQuotesData[$_cleverQuotesArrayKeys[0]],
			'image' => false
		),											
		'target' => $_target,
		'status' => false,
		'sessionattributes' => array('object' => 'clever quotes','target' => $_target,'prompt' => true, 'count' => 1,'data' => $_cleverQuotesArrayKeys),
		'endsession' => false
	)
);

With the session still open the user has about 8 seconds to reply and we will see the response in the prompt slot. In the same way we parse the command slot data we parse the response slots for the yes or no response from the user.

If the user responded with yes, we extract the data we need from the session to provide the next “clever quote” and then provide the exact same response and session data including an incremented prompt count variable.

If there are no more quotes available we respond appropriately and end the session. Similarly if the user responds with no, we respond and end the session by setting endsession to true.

Alexa Session Data

If you check the logs generated by the php script you will see the session data:

    [session] > Array
        (
            [new] > 
            [sessionId] > SessionId.1-2-3
            [application] > Array
                (
                    [applicationId] > amzn1.ask.skill.1-2-3
                )

            [attributes] > Array
                (
                    [data] > Array
                        (
                            [0] > 0
                            [1] > 1
                            [2] > 5
                            [3] > 3
                            [4] > 7
                            [5] > 4
                            [6] > 10
                            [7] > 6
                            [8] > 2
                            [9] > 8
                            [10] > 9
                        )

                    [count] > 1
                    [prompt] > 1
                    [object] > clever quotes
                    [target] > clever quotes
                )

            [user] > Array
                (
                    [userId] > amzn1.ask.account.123
                )

Custom Help and Launch intent

Alexa has some default built in intents such as STOP, HELP and LAUNCH.

When you say “Alex open skillname” the LAUNCH intent is used. When you say HELP in a skill, the HELP intent is used. When you submit your skill Amazon will check these intents for functionality. To create your own custom LAUNCH and HELP intent responses you must create or edit the example file in AmazonDev/Alexa/Launch and AmazonDev/Alexa/Help.

The filenames should be as follows

launch123.php
help123.php

Where 123 is replaced with the last digits from your skill id, i.e. if your skill id is amzn1.ask.skill.111-222-333-444-555 then the launch and intent filenames should be

launch555.php
help555.php

You should also change the class name of the launch and help classes to the same as the filename (without .php). Now you can customise the launch and help intent for you skill by editing the responses in the help and launch methods.

	public static function help($_alexaRequest=false)
	{
		$_response="Hello, I am happy to Help! To start this skill please say 'Alexa, open Hello World'";
		$_card=false;
		$_endSession=false;
		$_sessionAttributes=false;
		$_outputSSML=false;

		return array(
			'response' => $_response,
			'card' => $_card,
			'endsession' => $_endSession,
			'sessionattributes' => $_sessionAttributes,
			'outputssml' => $_outputSSML
		);

	}

You can see here that it is relatively simple to include prompts and responses in your Alexa skill by controlling and storing data in the skill session.

The example “clever quotes” intent show here is published in the Alexa skill store as “Clever Stuff”.

The updated code for this Hello World and Clever Quotes example is available from github here.

This Christmas (2016) a lot of people in Europe will be unpacking a shiny new Amazon Echo device and enjoying meaningful discussions with Alexa about life, the universe and everything.

If you are a geek like me then you will probably want Alexa to do a bit more than tell you about the weather or play Last Christmas by Wham. I bought my Amazon Echo Dot primarily to use for extremely important Home Automation tasks such as ‘Alexa, switch on the Christmas Tree lights‘.

The developer documentation from Amazon is good but very biased towards node.js. I know absolutely nothing about node.js and some of the online examples seemed overly complex to me. Eventually I found some useable PHP code examples and set about creating my own flexible PHP server side app for handling Alexa requests.

The app I created uses Alexa to send home automation commands via an Internet server to a home based Raspberry Pi server that lets me control Lights and Audio equipment. This is a step by step Hello World example using the same script that shows how relatively simple it is to create an Amazon Alexa App using PHP on your server to handle requests.

Before we start, here is a shopping list of things you will need :

1. Amazon developer account
2. Internet accessible web server (project tested with Apache)
3. SSL Certificate
4. PHP
5. Amazon Echo

1. Install and Test the PHP Application

• Download my example PHP application and extract it to your web server
  • https://github.com/gaiterjones/amazon-alexa-php-hello-world-example
  • preserve the file and folder structure
    • Application
    • Library
    • www
    • autoload.php
  • Your web server needs to be able to serve web pages over SSL.
• create a folder that is writeable by your www server user, i.e. www-admin
  • configure this folder path as amazonCacheFolder in config.php
    • const amazonCacheFolder=’/home/www/amazon/cache/’;
• make the file PAJ/www/AmazonDev/alexa.php web accessible
  • Test that the application is working by browsing to
    • https://www.your.server/youralias/alexa.php?debug
  • Make sure you see
    • PAJ\Application\AmazonDev\AlexaRequest
    • logfolder is writeable
  • note the debug curl information as this will be helpful in testing access to your application.

2. Register a Developer Account

Register and login to Amazon Developer Services at https://developer.amazon.com. You should register with the Amazon account you used to setup your Amazon Echo device. Once you are registered and logged in, click on the Alexa tab, and then the Get Started button for the Alexa Skills Kit and click the Add a New Skill button.

3. Create and Test the Alexa Skill

Skill Information

Amazon calls the process used to interact with the Alexa Voice Service a Skill. We will create a new private skill called Hello World.

• Skill Type
  • choose Custom Interaction Model
• Language
  • Select from drop down
• Name
  • The name of the skill
    • Hello World
• Invocation Name
  • This is the name we will use to activate the skill when talking to Alexa
    • hello world
      • “Alexa, ask hello world to say hello world“
• Click Next

Interaction Model – Skill Builder Beta

The interaction model describes how the user will interact with the voice service. In the context of Alexa, an intent represents an action that fulfills a user’s spoken request. Intents can optionally have arguments called slots. The intent schema is configured as an array in JavaScript Object Notation (JSON) format.

Use the Skill Builder Beta and paste the following skills builder intent json schema into the code section :

Here we have defined our intent name HelloWorld and associated slots.

Some default Intents are added by Amazon

AMAZON.CancelIntent
AMAZON.HelplIntent
AMAZON.StoplIntent

You can think of slots as variables to the intent, we have a slot (variable) named command with possible values contained in the COMMANDOBJECTS intent slot.

Next we configure the sample utterances for the skill. These are what people say to Alexa to invoke the intents configured in the skill.

The sample utterance starts with the intent name HelloWorld, followed by any combination of words a user might use to interact with the skill, and then the slot name that corresponds with this interaction.

When a user interacts with our Alexa Skill

‘Alexa, ask hello world to say hello world’

The voice service try to determine the user intention by matching the spoken words to the configured utterances, invoking the configured intent and matching the slot values to the phrases provided to the slot. In this case it will match ‘hello world‘ to the value configured in the command slot of the HelloWorld intent. This data will be sent to our server for us to process.

Why use slots? By using the amazon voice service to process and match the users spoken words to a configured set of slot variables (object types) we do not have to process the spoken words ourselves, we simply match the slot type to the command or processes we want to execute making it easier to determine user intent.

When you are finished configuring the Skill Builder you must save your configuration by clicking the Save Model button, and then build the model by clicking the Build Model button.

Configuration

Now we will configure how the Skill communicates with our PHP application.

• Select HTTPS
• Select the geographical location closest to your server
• Enter the URL to the Alexa php script on your server
  • https://www.your.server/youralias/alexa.php

Click Next.

SSL Certificate

Assuming your web server has a valid SSL certificate select ‘My development endpoint has a certificate from a trusted certificate authority’.

Click Next.

TEST

We can now test the Skill and server PHP application by using the service simulator.

In the Enter Utterance text box we can type the phrase we would say to invoke the application using our Echo device

Alexa, ask hello world to say hello world

The application will fail with an exception error if you have not yet added your amazon credentials to the config file in PAJ/Application/Amazon/Alexa/config.php. You can see the application id and userid in the service request. Copy these and add them to config.php.

	// AMAZON ALEXA
	const amazonSkillId = 'amzn1.ask.skill.XXX';
	const amazonUserId = 'amzn1.ask.account.XXX';
	const amazonEchoServiceDomain = 'echo-api.amazon.com';
	const amazonCacheFolder='/home/www/amazon/cache';

Run the test again. If the application is working you will see the service response JSON data returned from our PHP application, and the text that would be spoken by the Echo device.

  "response": {
    "outputSpeech": {
      "type": "PlainText",
      "text": "OK, I will now say hello world"
    },

Publishing

The publishing information is used to define how the app will appear to users if it is made public. This includes the category, countries the app will be available in, description, sample phrases and images.

This information will also be displayed in the Alexa mobile app.

You cannot publish your app until you have completed this section. When all sections are complete the Submit for Certification button will be available. Clicking this will begin the certification process where Amazon checks your app for compliance and functionality before publishing it in the Alexa Skills store and making it publicly accessible.

Privacy & Compliance

Complete the privacy and Compliance section and click Save to save the Skill.

4. Test with Amazon Echo device

To use your newly created Hello World skill with your Echo device make sure the skill is visible and enabled in the Alexa app, under Home -> Skills select Your Skills

Now say to Alexa

Alexa, ask hello world to say hello world

Your Echo device will respond with

OK, I will now say hello world

You can also say, ‘Alexa, open hello world‘, this initiates a Launch Request.

Ok, so this is a bit lame, change the output text response by modifying the response text in the HelloWorld.php intent return array.

	return array(
		'intent' => array(
			'response' => 'OK, I will now say something much more meaningful',
			'target' => $_target,
			'status' => false
		)
	);

How the PHP application works

The PHP server side process is relatively straightforward:

• Amazon sends the Alexa request data as an HTTP POST request to alexa.php.
  • alexa.php initiates the wwwApp bootload which injects the following php objects
    • Config
      • config data for the app
    • Security
      • validates the Alexa Request as per the guidelines here.
      •  This includes :
        • Validating the amazon application id
        • Verifying that the Request was Sent by Alexa
          • determine whether the URL meets each of the following criteria:
            • The protocol is equal to https (case insensitive).
            • The hostname is equal to s3.amazonaws.com (case insensitive).
            • The path starts with /echo.api/ (case sensitive).
            • If a port is defined in the URL, the port is equal to 443.
        • Validate the Signature of the Request
        • Validate the Timestamp of the Request
    • Log
      • logging
    • Request
      • parses the alexa post data
    • Data
      • renders the response
      • renders default intent responses
        • STOP, CANCEL, HELP
      • render LaunchRequest response
        • open hello world
      • initiating PAJ\Application\AmazonDev\Alexa\Intent\IntentName()
      • processing the Amazon intent data
        • formulating a text response based on the process data, in this case simply returning the response text for hello world
          • ‘OK, I will now say hello world‘
        • managing session attribute data
      • wrapping the response text and card data into a JSON request and outputting it

If you look at HelloWorld.php in Alexa\Intent you will see how we are parsing the intent data from Amazon, looping through the slot data and performing an action on each slot. In this case looking for the ‘command’ slot, validating the spoken words and then acting on them to formulate a response.

Further customisation

Here you can also see how you can now further customise the application. For example suppose you want to ask alexa to turn the lounge lights on

‘Alexa, ask Home to switch the lounge lights on’

Here my Alexa Skill is called Home, my intent name is Command, and I have configures a slot called switch which contains object types (variables) such as ‘lounge lights on’ and ‘lounge lights off’.

In Alexa/Intent/Command.php I parse the intent data to find the switch slot, verify that the slot value contains either ‘lounge lights on’, or ‘lounge lights off’ and the send the appropriate commands to my home automation system, i.e. FHEM. When the command has been successfully executed I can return the appropriate response.

‘Ok, I have switched the lounge lights on’

Debugging

If the Application is not working as expected check out the logfiles in your cache folder, for each Amazon Alexa request you will see the request, intent and response data logged in a file called helloworld_yyyy-mm-dd.log.

Use the skills tester in the Amazon skill builder to test and debug your skill. To debug further use the example curl command from the debug page. Execute this from a bash terminal to run curl and simulate an alexa request to your application.

Amazon Default Intents

You will notice that Amazon includes some default intents in the interaction model : AMAZON.StopIntent, AMAZON.CancelIntent, AMAZON.HelpIntent. If you want to publish your skill you must also include responses for these default intents. The default response for the Stop and Cancel intent is included in the renderAlexaResponse method. An examples for the Stop intent can be found in the Help folder.

Prompt and Response Dialog

Having completed a basic Alex command skill I will extend this PHP example to allow for prompts and responses in part 2 of this blog post.

Submit for Certification

Alexa Skills built with this project will pass the Amazon certification process. After submitting your skill you will receive a confirmation email from Amazon, and within 24 hours a response to notify you whether your skill has passed certification of not. Once your skill has been certified you cannot make any changes to the skill configuration without revoking it’s published status.

If you publish a skill with this application please let us know in the comments!

This made me very grumpy.

I created an eBay and Amazon admin website to allow us to consolidate order info from both merchants. It was useful to go directly from this site to the Amazon order in seller central by clicking on a button, even more useful was showing this in a fancybox iframe so the user didn’t have to leave the admin page. This worked, up until yesterday, when the iframe request is cancelled due to a :

Refused to display …. in a frame because it set ‘X-Frame-Options’ to ‘SAMEORIGIN’.

X-Frame-Options is an HTTP response header to prevent framing of pages. If the header is present the browser will refuse to render (cancel) the page in a frame depending on the values:

DENY – stops all framing
SAMEORIGIN – stops framing except for requests from the website itself.

So it looks like Amazon changed the security policy on their customer admin pages (Seller Central) yesterday to match the front end product pages and block frame request to content using the SAMEORIGIN header. There is no way around this so it is no longer possible to frame any amazon content. Boo!

The workaround is to load the content into a new _blank page and not use iframes – Hurrah!