Settings

The IOT Platform supports different communication channels. All of these channels can be configured in 

Account Management > Settings

A “doc” tab contains the explanations specific to each communication channel.

LORAWAN

  • Connect the platform to a “LORAWAN Network Server”
  • In the details of the chosen Network Server, the “doc” tab provides the information to encode. Most of this information must be obtained from the LORAWAN Network Server.
  • Uplink: for messages sent from the Network Server (device payloads). Any payload from a new device will cause the creation of a device on the platform. It will then be necessary to define the “Device Type” in order to be able to correctly decode these payloads.

For more information about our integrated LORAWAN Network Server, go to Integrated LNS

Sigfox

  • Connect the platform to the SigFox Back-end
  • Generate a URL on the platform. Then copy this url and configure the SigFox callback as described in the “doc” tab.
  • Any payload from a new device will cause the creation of a device on the platform. It will then be necessary to define the “Device Type” in order to be able to correctly decode these payloads.

MQTT Broker

  • Allow devices to connect to the MQTT Broker integrated into the platform (“iotfactory-broker”).
  • 3 types of topic format are supported:
    • Standard: for VEGA brand NB-IOT devices
    • Custom: to be used in conjunction with a custom Custom MQTT Topics whose JSON document specification and decoding are defined in the Advanced Configuration > Custom MQTT Topics
    • Iotfactory: the JSON format supported as standard by the platform
TAIGA NODE (NB-IOT)

For the configuration of TAIGA Node (NB-IOT), follow these steps:

  • In Taiga Node (using the mobile configurator application),
    • configure the MQTT Broker and port. You should use the Endpoint (not the TLS endpoint, as TLS is not supported by TAIGA Node) shown in the in Settings > mqtt > iotfactory-broker. It shows the Broker address and the port number
    • enter the User
    • enter the Password that was generated in the Settings > mqtt > iotfactory-broker

  • As a topic, enter /custom/raw/<device-id>
    • replace <device-id> by a unique identifier of your Taiga Node.
    • Example: /custom/raw/123456362
  • Once your Taiga Node communicates with the IOT Platform, you should see a new device in the Devices module.
  • Select this device, and change its Device Type to taiga-node and save
  • From the next payload received from your device, measurements should appear (payload is decoded)

Web Services

  • The platform offers a JSON data format to transmit data in the form of an https POST. The specification of this format is documented in the “doc” tab
  • It is also possible to receive data in a different format. The decoding of this format must be defined in the Advanced Configuration > Custom Types module (type: Web Service)

M2M

  • COAP
    • Support for devices that send their data in COAP.
    • Specific support for certain devices on the market (contact us for other integrations)