Skip to content



Repository files navigation

Things Gateway by Mozilla

Build Status codecov dependencies devdependencies license

Web of Things gateway.

If you have a Rasberry Pi, the easiest way to use the gateway is to download and flash a pre-built software image from Mozilla to an SD card. Otherwise you can build it from source yourself (see below).

Prerequisites for Building

Install OS

(If you're just installing on your PC, you can skip this step).

If you're installing on a Raspberry Pi then you may need to set up the OS on the Raspberry Pi first. See here for instructions.

Install pkg-config

Under Linux:

$ sudo apt-get install pkg-config

Under OSX:

See here.

Install curl (needed to install nvm)

Under Linux:

$ sudo apt-get install curl

Install nvm (Recommended)

nvm allows you to easily install different versions of node. To install nvm:

$ curl -o- | bash

Close and reopen your terminal window. Use nvm to install a LTS version of node and set the default version.

$ nvm install --lts
$ nvm use --lts
$ nvm alias default lts/*

Verify that node and npm have been installed:

$ npm --version
$ node --version

Note: these versions might differ from the LTS version installed locally.

Install node (if you didn't use nvm)

(If you already installed node via nvm you can skip this step)

Follow the directions from NodeJS to install on your platform.

Set up Bluetooth permissions

The following is required in order to let node use the Bluetooth adapter.

$ sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)

Install libusb and libudev (Linux only)

$ sudo apt-get install libusb-1.0-0-dev libudev-dev

Install git

You'll need git to checkout the repositories.

$ sudo apt-get install git

Install gcc (needed to build open-zwave)

Under Linux:

$ sudo apt-get install build-essential

Build and Install openzwave

$ cd
$ git clone
$ cd open-zwave
$ CFLAGS=-D_GLIBCXX_USE_CXX11_ABI=0 make && sudo CFLAGS=-D_GLIBCXX_USE_CXX11_ABI=0 make install
$ sudo ldconfig

Note: You may need to manually add /usr/local/lib to your LD_LIBRARY_PATH enviroment variable by adding the following to your ~/.profile file:

export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH

You can run this on the command line as well so it has immediate effect. After running it, you should run sudo ldconfig again to make sure the configuration change goes through.

Install OpenSSL (Windows only)

The Gateway depends on ursa, which requires OpenSSL.

Install OpenSSL =< 1.0.2 (normal, not light) in the same bitness as your Node.js.

See here.

Install Python 2.7 (Windows only)

PageKite works with Python 2.7.

Install Python 2.7 from here.

Enable "register extensions" on installing package, or associate file extension .py with python.

Install Python 3.X and packages (Optional, Windows only)

This is required in order to use Python 3 add-ons, e.g. tplink-adapter.

  • Install Python 3.X (ideally 3.4+) from here.
    • Enable "Install launcher for all users" and "Add Python 3.X to PATH" on installing.
    • Enable python3 command using the following.
mklink "C:\path\to\python3\python3.exe" "C:\path\to\python3\python.exe"
  • Install nanomsg.
    • Follow the directions from nanomsg to install in the same bitness as your Python 3.X.
    • If you want to build for 64-bit, you need to execute cmake with -DCMAKE_GENERATOR_PLATFORM=x64.
    • Add C:\path\to\nanomsg\bin to PATH.
  • Install nnpy
git clone
cd nnpy

Add a file: site.cfg

include_dirs = C:\path\to\nanomsg\include\nanomsg
library_dirs = C:\path\to\nanomsg\lib
host_library = C:\path\to\nanomsg\bin\nanomsg.dll

Execute the following command as an administrator.

python3 -m pip install .
python3 -m pip install git+

Note: 2018-04-12: pip3 has an issue with some languages.

Download and Build Gateway

  • Clone the GitHub repository (or fork it first):

    $ cd
    $ git clone
  • Change into the gateway directory:

    $ cd gateway
  • Install dependencies:

    • NOTE: yarn is preferred but npm install will also work. To install yarn run npm install --global yarn or for a more secure installation follow the directions for your OS.
    $ yarn
  • Set up domain:

    • If you plan to use Mozilla's provided tunneling service to set up a * domain:
      • Start the web server:

        $ npm start
      • Load http://localhost:8080 in your web browser (or use the server's IP address if loading remotely). Then follow the instructions on the web page to set up domain and register. Once this is done you can load https://localhost:4443 in your web browser (or use the server's IP address if loading remotely).

    • If you plan to use your own SSL certificate:
      • The HTTPS server looks for privatekey.pem and certificate.pem in the ssl sub-directory of the userProfile directory specified in your config. You can use a real certificate or generate a self-signed one by following the steps below.

        $ MOZIOT_HOME="${MOZIOT_HOME:=${HOME}/.mozilla-iot}"
        $ SSL_DIR="${MOZIOT_HOME}/ssl"
        $ [ ! -d "${SSL_DIR}" ] && mkdir -p "${SSL_DIR}"
        $ openssl genrsa -out "${SSL_DIR}/privatekey.pem" 2048
        $ openssl req -new -sha256 -key "${SSL_DIR}/privatekey.pem" -out "${SSL_DIR}/csr.pem"
        $ openssl x509 -req -in "${SSL_DIR}/csr.pem" -signkey "${SSL_DIR}/privatekey.pem" -out "${SSL_DIR}/certificate.pem"
      • Start the web server:

        $ npm start
      • Load https://localhost:4443 in your web browser (or use the server's IP address if loading remotely). Since you're using a self-signed certificate, you'll need to add a security exception in the browser.


If you are using VS Code, simply use the "launch" target. It will build the gateway in debugger mode.

If you are not using VS Code, run npm run debug and it will build the gateway and launch it with --inspect.

Running Tests

To run the linter and all tests:

$ npm test

To run a single test:

$ jest src/test/{test-name}.js

(assumes you have the jest command on your PATH, otherwise use ./node_modules/jest/bin/jest.js)

Source Code Structure

  • config/ - Gateway configuration files
  • doc/ - Additional documentation
  • image/ - Tools for building the Raspberry Pi image
  • src/
    • addons-test/ - Add-ons used strictly for testing
    • controllers/ - App URL routes and their logic
    • models/ - Data model and business logic
    • plugin/ - Utility classes and methods used by add-ons
    • rules-engine/ - The rules engine
    • test/ - Integration tests
    • views/ - HTML views
    • addon-loader.js - Script used for starting up Node-based add-ons
    • addon-manager.js - Manages add-ons (e.g. ZigBee, Z-Wave)
    • app.js - The main back end
    • app-instance.js - Application wrapper for integration tests
    • constants.js - System-wide constants
    • db.js - Manages the SQLite3 database
    • deferred.js - Wraps up a promise in a slightly more convenient manner for passing around, or saving
    • ec-crypto.js - Elliptic curve helpers for the ES256 curve
    • jwt-middleware.js - Express middleware for determining authentication status
    • log-timestamps.js - Utilities for adding timestamps to console logging functions
    • oauth-types.js - OAuth types
    • passwords.js - Password utilities
    • router.js - Routes app URLs to controllers
    • ssltunnel.js - Utilities to determine state of tunnel and manage the PageKite process
    • tunnel_setup.js - Express middleware to determine if the tunnel is set up
    • user-profile.js - Manages persistent user data
    • utils.js - Various utility functions
  • static/ - Static CSS, JavaScript & image resources for web app front end
  • tools/ - Helpful utilities (not part of the build)
  • package.json - npm module manifest


No packages published


  • JavaScript 69.7%
  • Python 16.3%
  • Shell 5.5%
  • CSS 4.6%
  • HTML 2.3%
  • TypeScript 1.6%