6.4. MQTT - Adding a Device to EdgeX

In this example, we use the simulator instead of a real device. This provides a straight-forward way to test the device-mqtt features.

MQTT Setup

6.4.1. Environment

You can use any operating system that can install docker and docker-compose. In this example, we use Photon OS to deploy EdgeX using docker. The system requirements can be found at https://docs.edgexfoundry.org/Ch-GettingStartedUsers.html#what-you-need.

Photon Operating System Version Information

6.4.2. MQTT Broker

EMQ is a MQTT broker that is easy to configure and use. You can download it from http://emqtt.io. It’s fully open source and licensed under Apache Version 2.0.

Run using the following docker command:

docker run -d --rm --name emqx -p 18083:18083 -p 1883:1883 emqx/emqx

After the MQTT broker has started, login to the dashboard using the default account details (name = admin, password = public)

MQTT Broker

6.4.3. MQTT Device (Simulator)

The device-mqtt source code provides a mock device that can send async values and handle commands. You must implement these two functions when using the device-mqtt service as described below.

MQTT Device Service

To set up the service:

  1. Download the source code:

    git clone git@github.com:edgexfoundry/device-mqtt-go.git
  2. Modify the broker connection

    The broker connection information must be modified to meet our requirement.

    device.go Set Up
  3. Run the device simulator

    Run the following command in your terminal:

    go run ./mock/device.go

6.4.4. Set Up

The following sections describe how to complete the set up. Set Up Device Profile

The DeviceProfile defines the device’s values and operation method, which can be Read or Write.

Device profile

You can download and use the provided mqtt.test.device.profile.yml. Set Up Device Service Configuration

Use this configuration file to define devices and schedule jobs. The device-mqtt generates a relative instance on startup.

MQTT is subscribe/publish pattern, so we must define the MQTT connection information in the addressable.

configuration.toml File

You can download and use the provided EdgeX_ExampleMQTT_configuration.toml. MQTT Driver Configuration

In the MQTT driver configuration:

  • Incoming defines DataTopic for receive async value from device

  • Response defines ResponseTopic for receive command response from device

    configuration.toml Incoming and Response Entries Add Device Service to docker-compose File

Because we deploy EdgeX using docker-compose, we must add the device-mqtt to the docker-compose file ( https://github.com/edgexfoundry/developer-scripts/blob/master/compose-files/docker-compose-delhi-0.7.0.yml ). If you have prepared configuration files, you can mount them using volumes and change the entrypoint for device-mqtt internal use.

  image: docker.edgexfoundry.org/device-mqtt-go-x86_64:test ports:
    - "49982:49982"
  container_name: edgex-device-mqtt
  hostname: edgex-device-mqtt
      - edgex-device-mqtt
  priviledged: true
    - db-data:/data/db
    - log-data:/edgex/logs
    - consul-config:/consul/data
    - /device-service-demo/mqtt:/custom-config
    - data
    - command
    - /device-mqtt
    - --registry
    - --confdir=/custom-config

    driver: "bridge"

6.4.5. Start EdgeX Foundry on Docker

Finally, we can deploy EdgeX in the Photon OS.

  1. Prepare configuration files by moving the files to the Photon OS

  2. Deploy EdgeX using the following commands:

    docker-compose pull
    docker-compose up -d
Start EdgeX
  1. Check the consul dashboard

    Consul Dashboard

6.4.6. Execute Commands

Now we’re ready to run some commands. Find Executable Commands

Use the following query to find executable commands:

Executable Commands Execute GET command

Replace <host> with the server IP when running the edgex-core-command.

GET Command Execute PUT command

Execute PUT command according to url and parameterNames.

PUT Command PUT Command Body

6.4.7. Schedule Job

After service startup, query core-data’s reading API. The results show that the service auto-executes the ping command every 10 seconds and the readRandnum command every 30 seconds.

Schedule Configuration GET Readings

6.4.8. Async Device Reading

Async Device Reading

device-mqtt subscribes to a DataTopic, which is wait for real *device to send value to broker, then device-mqtt parses the value and sends it back to core-data.

The data format contains the following values:

  • name = device name
  • cmd = deviceResource name
  • method = get or put
  • cmd = device reading

You must define this connection information in the driver configuration file.

Connection Information