Coap-gateway NPM

COAP Gateway

This is designed to be a modular gateway for devices using COAP + protobufs. Its core principle is allowing devices to specify how to parse the data they provide. It does this by allowing devices to specify their own protobuf specification that defines how to decode the data in their packets and format it into a JSON object.

Quick Overview

This script:

Waits for incoming CoAP packets.
If a received packet is from a known client device, and the script has already cached a parser, the protobuf payload is parsed and translated to a JSON object. This JSON is emmitted as a nodejs event.
Otherwise, the parser returns a 4.04 response code to the client, indicating that the parser could not be found. It is expected that the client then transmits a properly formatted protobuf message containing a "discovery_url" URL to the /discovery resource.
The script waits for a COAP message to the /discovery resource with a URL that points to a protobuf *.proto file.
Upon receiving such a packet, it pulls out the embedded URL and uses it to fetch a parse.proto file at <URL>/parse.proto. If the URL already specifies a particular file, it removes the filename and uses just the base. For example, if the URL is:
```
    http://example.com/folder/index.html

the gateway will use just `http://example.com/folder/` and look for `parse.proto` at:

    http://example.com/folder/parse.proto
```
If that parse.proto file exists, the gateway will cache the protobuf definition to parse other messages the device sends in the future.

To use this gateway with your COAP device

Configure your device to periodically send a COAP /discovery URL packet, or respond with one when presented with a 4.04 status (Not Found).
This packet should be formed as a protobuf payload adhering to the base header.proto.
The URL should point to a webserver path where you can host the needed protobuf file. For example, the URL could be hosted on github.io, and resemble:
```
 https://org.github.io/project/device/
```
Packets besides the discovery packet can be completely device specific, but should extend the existing header.proto. Each field can contain data or not. The parse.proto is what the gateway will use to parse data from these packets.

Create a parse.proto file and host it in the directory pointed to by the discovery packet URL. For example:

    https://org.github.io/project/device/parse.proto

See below for how to create the `parse.proto` file.

`parse.proto`

A parse.proto file contains the protobuf packet definition, and is an extension of the header.proto used by this package. The template of a parse.proto file looks like:

syntax = "proto3";

message Header {
  uint32 version = 1;
  bytes  id = 2;
  string device_type = 3;
  uint32 seq_no = 4;
  uint64 tv_sec = 5;
  uint32 tv_usec = 6;
}
message Data {
  string discovery_url = 1;
  string git_version = 2;

  // Add your custom definitions here
}

message Message {
  Header header = 1;
  Data data = 2;
}

One simple example of a parse.proto for an environmental sensor might look like:

syntax = "proto3";

message Header {
  uint32 version = 1;
  bytes  id = 2;
  string device_type = 3;
  uint32 seq_no = 4;
  uint64 tv_sec = 5;
  uint32 tv_usec = 6;
}
message Data {
  string discovery_url = 1;
  string git_version = 2;

  float temperature_c = 10;
  float pressure_mbar = 11;
  float humidity_percent = 12;
  float light_lux = 13;
  bool  motion = 14;
}

message Message {
  Header header = 1;
  Data data = 2;
}

Local parse.proto files

This gateway can be configured to prepopulate its cache of parsers by providing a list of objects that specify a URL and a path to a protobuf definition file to the gateway start method.

var local_parsers = [{"url": "someurl.com", "parser_path": "path/to/parse.proto"}];
CoapGateway.start(local_parsers);

Extending the Gateway

This gateway can run as a standalone application or as a module inside of another tool. When running as a embedded module, it follows the EventEmitter pattern allowing you to register callbacks for various events.

var CoapGateway = require('coap-gateway');

// Receive formatted advertisement data objects.
// adv_obj.id will be the peripheral id that it was captured from.
CoapGateway.on('payload', function (adv_obj) {
	...
});

// Get everything going.
CoapGateway.start();