2.0.0 • Published 7 years ago

ttn-azure-iothub v2.0.0

Weekly downloads
3
License
MIT
Repository
github
Last release
7 years ago

The Things Network Azure IoT Hub Integration

This is an example integration of The Things Network with Azure IoT Hub. This integration features creating devices in the Azure IoT Hub device registry as well as sending events from uplink messages.

Example

This integration requires an shared access policy key name with Registry read and write and Device connect permissions. In this example, we use the iothubowner policy which has these permissions enabled by default.

'use strict';

const ttnazureiot = require('ttn-azure-iothub');

// Replace with your region, app ID and access key
const region = '<insert region>';
const appId = '<insert app ID>';
const accessKey = '<insert access key>';

// Replace with your Azure IoT Hub name, key name and key
const hubName = '<insert hub name>';
const keyName = 'iothubowner';
const key = '<insert key>';

const bridge = new ttnazureiot.Bridge(region, appId, accessKey, hubName, keyName, key);

bridge.on('ttn-connect', () => {
  console.log('TTN connected');
});

bridge.on('error', err => {
  console.warn('Error', err);
});

bridge.on('message', data => {
  console.log('Message', data);
});

Options

When creating and initializing the Bridge, you can specify options:

const options = {};
const bridge = new ttnazureiot.Bridge(region, appID, accessKey, hubName, keyName, key, options);

createMessage

The function to create a message. By default, the message is a combination of the result of the payload functions fields, the unique device ID and the server time:

options.createMessage = function(deviceId, message) {
  const metadata = {
    deviceId: deviceId,
    time: message.metadata.time,
    raw: message.payload_raw
  };
  return Object.assign({}, message.payload_fields, metadata);
}

Note: if the result of your payload functions contain the fields deviceId or time, these fields will be overwritten by the metadata. Use a custom createMessage function to use custom field names.

2.0.0

7 years ago

1.0.0-5

8 years ago

1.0.0-4

8 years ago

1.0.0-3

8 years ago

1.0.0-2

8 years ago

1.0.0-1

8 years ago

0.2.1

8 years ago

0.2.0

8 years ago

0.1.1

8 years ago

0.1.0

8 years ago