Gateway - Sigfox

Follow

In this article you are going to learn about Sigfox Network.

1. What is Sigfox network?

2. How to create a Sigfox gateway in the platform

         2.1. Create a Callback in Sigfox backend to send data to the EMS

 

1. What is Sigfox network?

Sigfox is a network operator dedicated to the Internet of Things (IoT). The Sigfox network is using the UNB (Ultra Narrow Band) and allows devices to communicate with low power on a wide area. 

The Sigfox technology allows transmitters to send their data (temperature, humidity, metering values…) without distance constraints directly on the Sigfox servers.

The data stocked on the Sigfox cloud can then be sent to the EM platform by configuring a Callback in the Customer Sigfox Backend.

 

Captura_de_Pantalla_2019-10-23_a_les_14.52.49.png

 

Sigfox compatible devices are battery powered and communicate wirelessly without any extra gateway to Sigfox Cloud, allowing you to send data from different Type of probes and sensors like Temperature, pulses, etc. directly to the platform using Sigfox Network..

The EM platform is compatible with several Sigfox enabled device manufacturers like Sensohive, or Enless Wireless.

2. How to create a Sigfox Gateway in the Platform

Sigfox is integrated with the EMS, so to communicate your Sigfox cloud with the latform is easy and quick.

To start receiving data to your account from your Sigfox Cloud follow this steps:

1. Login to the EMS with your user and password

2. Go to Settings sections: dexma-sigfox-1.png

3. On the left menu go to Gateways and click on Register a new gateway: dexma-gatewaysSigfox-2.png

4. Select Sigfoxdexma-gatewayssigfox-3.png

5. Fill in the following fields:

  • Name: write a distinctive name for your gateway
  • Model: select a device model from the list
  • Time Zone: select the time zone where it is located

dexma-gatewayssigfox-4.png

 

6. Once you click on Save you will see two information fields with the data you need to configure in the Sigfox Backend. 

  • Sigfox Callback Request. It contains the expected format of the message to configure in Sigfox. This is different in each Sigfox Gateway in the platform, and has to be used just in one Sigfox callback
  • Platform Bridge URL. It contains the endpoint URL to configure in Sigfox. This URL is always the same but has to be configured in all Sigfox Callbacks: https://sigfox.source.dexma.com/metrics 

Screenshot_2019-10-25_at_12.53.53.png

2.1. Creating a Callback in Sigfox backend to send to the EM platform

To send information from all your Sigfox devices to the EM platform it is necessary to create a callback in Sigfox Backend and configure it to send to a gateway.

Devices in Sigfox Cloud are organised in “DEVICE TYPES”. Each device type contains all the devices (of the same model and manufacturer) you want to group to send to a third party (like the EM platform). 

Captura_de_Pantalla_2019-10-23_a_les_14.58.03.png

#NOTE: All devices inside a Sigfox “DEVICE TYPE” have correspond to the same Model from the same manufacturer.

Once you have all the devices grouped in your different device types, then you have to create a “Callback” to send the data from all those devices to the platform's gateway.

Captura_de_Pantalla_2019-10-23_a_les_14.58.33.png

Callback configuration:

Screenshot_2019-10-25_at_12.55.46.png

Configuring the frequency at which Sensohive Orbit 3 sends data to the platform.

Sensohive Temperature probes can be configured to send data in any resolution between 2,5 minutes to 7 days. However in the platform some restrictions have been implemented in order to limit the possible options, to avoid high freqency data insertion.

In order to configure this, you can modify the probe configuration by sending a message from the Sigfox backend to the probe. This message has to be formatted in a certain way (period in seconds and in HEX numbers) according to Sensohive’s manual.

On the EM platform, there is a dropdown in the gateway configuration, to select the resolution that will be applied to the incoming data. This dropdown applies only when a Sensohive device is selected, and possible values in the resolution dropdown are:

  • Time between readings 10 min → 4 values in 40 min

  • Time between readings 15 min → 4 values in 1 h

  • Time between readings 30 min → 4 values in 2 h

  • Time between readings 1 h → 4 values in 4 h

  • Time between readings 2h → 4 values in 8 h

  • Time between readings 6h → 4 values in 24 h

  • Time between readings 24h → 4 values in 4 day

  • Time between readings 7 day → 4 values in 28 day

Therefore, only one of those will be configured in Sigfox Callback.

On Sigfox's backend, you need to follow these steps to modify the frequency (described here to change the time between readings to 2 hours. Check Sensohive's manual if needed:

You need to downlink to the devices an instruction to send every two hours - and if you want to save even more battery, you can instruct the device to only ask for downlinks every 6 days e.g.

In order to do that you will have to downlink the following payload to the devices

1e0007082007E900

The easiest way to set this up, is if you have all the devices on the same (or a few) device types. Then you can under 'Edit' device type set the downlink data to 'Direct' and set the downlink data to the string listed above.

This will ensure that this string is sent to every device in the device type. However, if you have other devices - or devices which you do not want to change the settings on, you cannot do it this way.

Other Sigfox devices

If you need additional Sigfox devices that are not yet integrated in the platform, do no to hesitate to contact us at support@dexma.com.

Was this article helpful?