"Error: Unknown command: protocol" when following example from serverless readme

[smoll]

This is a Bug Report

Description

I followed the steps listed in https://github.com/graphcool/chromeless/tree/master/serverless with the following changes

custom:
  stage: dev
- debug: "*"
- awsIotHost: ${env:AWS_IOT_HOST}
+ debug: false
+ awsIotHost: myiotendp.iot.us-east-2.amazonaws.com
  chrome:
    functions:
      - run
@ -12,7 +12,7 @@ provider:
  name: aws
  runtime: nodejs6.10
  stage: ${self:custom.stage}
- region: eu-west-1
+ region: us-east-2
  environment:
    DEBUG: ${self:custom.debug}
    AWS_IOT_HOST: ${self:custom.awsIotHost}

However, when I ran the full example https://github.com/graphcool/chromeless/tree/master/serverless#full-example I get the following error:

$ node spike.js
Error: Unknown command: protocol

I also tried updating the chromeless dependency in https://github.com/graphcool/chromeless/blob/master/serverless/package.json#L15 to 1.4.0 but that didn't seem to change anything.

Additional Data

• Chromeless Version you're using: 1.3.0 or 1.4.0
• Operating System: macOS High Sierra 10.13
• Stack Trace: not sure how to get a better stack trace, please advise
• Error messages: when I add debug: true to the opts, I see one additional log statement

$ node spike.js
Connected to message broker.
Running remotely: {"type":"goto","url":"https://www.google.com"}
Error: Unknown command: protocol

[smoll]

Just discovered that downgrading my sls chromeless dependency down to 1.2.0 fixes this issue.

[asendia]

I got the same error when following the readme tutorial using the latest npm version of chromeless.

• nodejs version: v9.8.0
• yarn version: 1.3.2
• Chromeless version: 1.5.1
• Operating System: macOS High Sierra 10.13.4

$ node google-remote.js
Connected to message broker.
Running remotely: {"type":"goto","url":"https://www.google.com"}
Error: Unknown command: protocol
Chromeless Proxy disconnected due to inactivity (no commands sent for 30 seconds).

[aaronromeo]

@asendia bumping the chromeless version as seen in PR #415 got me past this issue. (I had to then redeploy my remote browser)