No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.orbiwiseserver.metadata Update May 17, 2018

Orbiwise connector

About Orbiwise

Orbiwise is an IoT company that offers a full network software solution for LoRaWAN-based networks, which can scale to support millions of devices. Orbiwise's network server connects loRaWAN devices to the outside word, either through API exposed by the server or through packet propagation (invocation of callbacks registered at the server).

Purpose of the connector

The connector wraps the APIs that are exposed by the Orbiwise server and allows you to seamlessly communicate with your loRaWAN devices through the Orbiwiser server, as if they were objects of your applications.


  • /orbiwiseserver: defines the OrbiwiseServer class that exposes all the methods you need to intereact with your devices
  • /client: a generic HTTP client that handles the communication with the Orbiwise server
  • /config: the configuration script, where to specify the URL of your Orbiwise server, your Orbiwise credentials and your callbacks
  • /webhook/rest/callback: base folder containing the scripts that are invoked by the Orbiwise server when subscribing a callback

Configuring the connector

You can configure your application in the connector using the "/config" file:

  • Specfify the URL of the Orbiwiser server using the "orbiwiseUrl" variable,
  • Specify your Orbiwise credentials using the "username" and "password" variables. These will be used by default if no credentials ae passed to the OrbiwiseServer constructor (see below).
  • You can use the default value for the callback URL. If you have opted for the Orbiwise automatic packet forwading option (see below), this URL is automatically invoked by the Orbiwise server whenever updated data is available. Note that this value will also be used by default if no alternative configuration is passed to the OrbiwiseSerer constructor.
var orbiwiseUrl = "The URL of the Orbiwise server";

var username = "your_username";
var password = "your_password";

var callback = {
  host: "", 
  port: 443,
  path_prefix: "/modules/orbiwise/webhooks", // NOTE: THIS IS A PREFIX. 
  auth_string: "Bearer A_VALID_SCRIPTRIO_AUTH_TOKEN",
  retry_policy: 1

Using the connector

Instantiating the connector

The first thing to do is to create an instance of the Orbiwise Server. From a script, require the orbiwiseserver script then create an instance of the aforementioned class:

var orbiwise = require("/modules/orbiwise/orbiwiseserver");
// option 1: use the default configuration
var defaultOrbiwiseServer = new orbiwise.OrbiwiseServer(); 
// option 2: use the a custom configuration
var customOrbiswiserServer = new orbiwise.OrbiwiseServer({username:"xxx", password:"yyyy", callback: {// some object}});

List all available devices (nodes)

var nodes = customOrbiswiserServer.listNodes();

Get latest payload for a given node

var deviceId = nodes[0].deveui; // deveui is the property that identies a node
var payload = customOrbiswiserServer.getLatestPayload(deviceId);

List all available payloads for a given device

var payloadList = customOrbiswiserServer.listPayloads(deviceId);

Register to the callback service to automatically receive data updates

The preceding methods allow you to explicitely ask for a device's latest payload. You can also register a callback to the Orbiwise server that will automatically forward updates to the given callback URL. The registerCallback method can be invoked without passing any parameter, which will make it use the value of the "callback" variable of the "./config" script. You can also choose to overwrite the default callback by providing a specific configuration.

var result = customOrbiwiseServer.registerCallback(); // option1, use default configuration
// option 2, use specific callback 
var callback = {
  host: "", 
  port: 443,
  path_prefix: "/myapplication/webhooks", // NOTE: THIS IS A PREFIX
  auth_string: "Bearer A_VALID_SCRIPTRIO_AUTH_TOKEN",
  retry_policy: 1

result = customOrbiwiseServer.registerCallback(callback);


  • Callback URLs specification set by Orbiwise to send different data are as follow:
  • path_prefix/rest/callback/payloads/ul (new device data)
  • path_prefix/rest/callback/payloads/dl (notification that downlink data sent to device was received)
  • path_prefix/rest/callback/nodeinfo (updates on the node)
  • path_prefix/rest/callback/joininfo (node joined upates)
  • path_prefix/rest/callback/status (node status updates)
  • You can only register one callback at a time. Therefore, invoking twice the registerCallback() method with different callback URL and configuration ends up only registering the second callback configuration

Un-register from the callback service

var result = customOrbiwiseServer.unregisterCallback();