This article applies as of PRTG 22

Monitoring Sigfox callbacks with PRTG

With PRTG, you can monitor Sigfox callbacks out of the box with the HTTP IoT Push Data Advanced sensor. You can use this sensor to monitor measurements such as temperature and humidity with PRTG.

Note: In the following examples, we used a device like Sens'it.

Create an HTTP IoT Push Data Advanced sensor

The first step to monitoring Sigfox callbacks is to add an HTTP IoT Push Data Advanced sensor to your PRTG installation.

1. Create a new device or use an existing device (for example, with IP address 127.0.0.1).
2. Add an HTTP IoT Push Data Advanced sensor to the device.
3. In the sensor settings, set the Scanning Interval according to the device transmit interval, for example 15 minutes.
4. Note the SSL Port 5051 and the Identification Token, you need both values when setting up your Sigfox callback configuration, so copy them.

Create a Sigfox callback

The next step to monitoring Sigfox callbacks is to create the corresponding callback in the Sigfox interface.

Click to enlarge.

1. Open Callbacks.
2. Select the Device Type tab.
3. Under Type, select Data and Uplink.
4. Under Custom payload config, enter the following
   humidity::int:16:little-endian temperature::int:16:little-endianNote: The custom payload config is important for decoding purposes. For the values to be properly displayed in PRTG, they must be decoded.
   
5. Under URL pattern, enter the URL in the following format.
   https://<PRTG IP>:5051/<Sensor-specific identification token>Note: You can reference the Sigfox Id as {device} in your push identification token.
   
6. In the URL, replace
   • <PRTG IP> with the IP address of the system on which your PRTG probe with the HTTP IoT Push Data Advanced sensor is running.
   • <Sensor-specific identification token> with the Identification Token that you defined in the sensor settings.
7. Select POST as HTTP method.
8. Change the Content type to application/json
9. Add the following JSON to the Body field { "prtg": { "text": "OK", "result": [ { "channel": "Temperature", "value": {customData#temperature}, "float": "1", "unit": "custom", "customunit": "°C" }, { "channel": "Humidity", "value": {customData#humidity}, "float": "1", "unit": "custom", "customunit": "%" } ] } } Note: The {customData#NAME} pattern references the named values you defined in the Custom payload config field. Please see PRTG Manual: Custom Sensors for an explanation of all possible JSON properties.
   
10. Click Ok to save the callback.

Optional: decode the callback data

After the first successful push from your Sigfox callback to your HTTP IoT Push Data Advanced sensor, the channels will appear in your sensor as defined by the JSON body payload. You can now edit the channels and adjust the scaling factors.

Because there is a Sigfox transmit limitation of 12 bytes, manufacturers often convert values, for example from float to integer, to make them smaller. For these values to be properly displayed in PRTG, they must be returned to their original format using scaling.

When decoding values that were converted from float to integer, the scaling needs to be configured as follows in the respective channel's settings.

Click to enlarge.

Note: The values in the screenshot are just examples. The type of conversion that is used varies from manufacturer to manufacturer. See your manufacturer's documentation for details.

More

• How can I monitor Sigfox Geolocation with PRTG?
• How can I monitor the Sigfox API with PRTG?