Wirepas Linux Gateway

Build Status

This repository contains Wirepas’ reference gateway implementation, which relies on a set of services to exchange data from/to a Wirepas Mesh network from/to a MQTT broker or host device.

The services will be known from now on as sink service and transport service. The sink service is responsible to interface locally with a Wirepas device running its Dual MCU API. The transport service packs network messages on protobuffers and publishes them on top of MQTT according to Wirepas Backend API.

Figure 1, provides an overview of the gateway implementation and the apis involved at each step.

Wirepas gateway architecture

Figure 1 - Gateway services overview.

Cloning this repository

This repository depends on two other projects, c-mesh-api and backend-apis.

The c-mesh-api contains the library used by the sink service, which interfaces with the sink devices. The backend-apis contains api and message wrapper over the protocol buffers that are transmitted over MQTT.

We are currently using the repo tool to upkeep the project dependencies and for that reason we recommend that you use it as well.

The manifest files are located in at the manifest repository and are organized inside the gateway folder as follows:

  • dev.xml: points to the development branches, intended for collaborators
  • stable.xml: points to the latest release

If you wish to pull the latest release then use the following command:

repo init -u https://github.com/wirepas/manifest.git \
          -m gateway/stable.xml \

and if you wish to track the development branches, please use

repo init -u https://github.com/wirepas/manifest.git \
          -m gateway/dev.xml \

afterwards download the repositories with

repo sync
To clone a particular version, vX.Y.Z, please specify the tag with the
-b switch and use the stable manifest:
repo init (...) -m gateway/stable.xml -b refs/tags/vX.Y.Z

Usage of repo is also documented in the release Dockerfiles (see Dockerfile).

Please read more on the repo tool usage from its official documentation.

Linux Requirements

The implementation is based on DBus. The C binding used to access DBus is sdbus from systemd library so even if systemd is not required to be running, the libsystemd must be available.

Systemd version must be higher or equal to 221. You can check it with:

systemd --version

In order to build the sink service, systemd headers are needed

sudo apt install libsystemd-dev

Python 3 and a recent pip version (>= 18.1)

sudo apt install libsystemd-dev python3 python3-dev python3-gi
wget https://bootstrap.pypa.io/get-pip.py \
   && sudo python3 get-pip.py && rm get-pip.py \
   && sudo pip3 install --upgrade pip


Sink service

Sink service is written in C and can be built with following command from sink_service folder:


This implementation uses system bus that has enforced security. In order to obtain a service name on system bus, the user launching the sink service must be previously declared to system. Provided file com.wirepas.sink.conf inside sink_service folder must be copied under /etc/dbus-1/system.d/ and edited with the user that will launch sink_service (and transport service).

To change the default wirepas user, please edit the following lines from com.wirepas.sink.conf:

<!-- Only wirepas user can own the service name -->
<policy user="wirepas">

It is recommended to restart your gateway once this file is copied.

Transport service

Transport service is implemented in python 3 and is delivered as a Python wheel, either through PyPi or the release section of this repository.

The library contains a c extension which will be compile upon installation. Please ensure that you have met all the build requirements prior to attempting the installation with:

pip3 install wirepas_messaging-*.whl


pip3 install wirepas_gateway-*.tar.gz

If you wish to build the wheel yourself, please refer to the transport’s service readme file.

Configuration and starting services

Sink service configuration

A sink service must be started for each connected sink on Gateway:

sink_service/build/sinkService -p <uart_port> -b <bitrate> -i <sink_id>

Parameters are:

  • uart_port: uart port path (default: /dev/ttyACM0)
  • bitrate: bitrate of sink uart (default: 125000)
  • sink_id: value between 0 and 9 (default: 0).

If multiple sinks are present, they must have a different sink_id.

Transport service configuration

Parameters can be set from command line or from a setting file in YAML format. To get an the full list of parameters, please run:

wm-gw --help

From command line

Here is an example to start the transport module from the command line:

wm-gw \
      --mqtt_hostname "<server>" \
      --mqtt_port <port> \
      --mqtt_username <user> \
      --mqtt_password <password> \
      --gateway_id <gwid> \
      [--ignored_endpoints_filter <ignored endpoints list>] \
      [--whitened_endpoints_filter <whitened endpoints list>]


  • mqtt_hostname: Hostname or IP where the MQTT broker is located

  • mqtt_port: MQTT port

  • mqtt_username: MQTT user

  • mqtt_password: MQTT password

  • gateway_id: the desired gateway id, instead of a random generated one.

    It must be unique for each gateway reporting to same broker.

  • ignored_endpoints_filter: destination endpoints list to ignore

    (not published)


    To filter out destination endpoints  1, 2, 10, 11, 12:
    --ignored_endpoints_filter "[1,2, 10-12]"
  • whitened_endpoints_filter: destination endpoints list to whiten

    (no payload content, only size)


    To whiten destination ep 1, 2, 10, 11, 12
    --whitened_endpoints_filter "[1,2, 10-12]"

From configuration file

wm-gw --settings=settings_files.yml

All parameters that are accepted by the transport service can be set through the settings file. An example of a settings_file.yml file is given below:

# MQTT brocker Settings
mqtt_hostname: <IP or hostname where the MQTT broker is located>
mqtt_port: <MQTT port (default: 8883 (secure) or 1883 (local))>
mqtt_username: <MQTT user>
mqtt_password: <MQTT password>

# Gateway settings
gateway_id: <the desired gateway id, must be unique for each gateway>
gateway_model: <Custom gateway model, can be omitted>
gateway_version: <Custom gateway version, can be omitted>

# Filtering Destination Endpoints
ignored_endpoints_filter: <Endpoints to filter out. Ex: [1, 2, 10-12]>
whitened_endpoints_filter: <Endpoints to whiten. Ex: [1, 2, 10-12]>


Launch local gateway process to see messages received from sinks at Dbus level. It can be launched from the command line with:


Building and running with Docker

In the container folder you will find three folders, one for development purposes and two other for architecture images, x86 and arm.

The development folder builds an image based on the contents of the repository, whereas the other two folder will provide you a build for what is specified in the repo tool’s manifest.

To make a development build type:

[IMAGE_NAME=wirepas/gateway-x86:edge] docker-compose -f container/dev/docker-compose.yml build

If you want to build a stable image for x86 type:

docker-compose -f container/stable/x86/docker-compose.yml build

Alternatively you can use our ci tool.

We also have pre-built images available from docker hub under the following registries:

Starting docker services

When running the gateway over docker, the composition will mount your host’s system dbus inside each container. This is necessary to allow exchanging data between both services. For that reason you will have to copy the dbus manifest to your host’s and change the policy user to reflect what is used within the docker-compose.

After configuring your host’s dbus, review the environment file where you can define settings for the sink and transport service.

The environment parameters will be evaluated by the container’s entry point and passed on to the sink and transport service.

Please ensure that you define the correct password and MQTT credentials and launch the services with:

[IMAGE_NAME=wirepas/gateway-x86:edge] docker-compose -f container/dev/docker-compose.yml up [-d]

To view the logs, use

docker-compose -f container/dev/docker-compose.yml logs

or specify which container you want to view the logs from with

docker logs [container-name]


We welcome your contributions!

Please read the instructions on how to do it and please review our code of conduct.


Copyright 2019 Wirepas Ltd licensed under Apache License, Version 2.0 See file LICENSE for full license details.

Indices and tables