...
The Sigfox protocol is similar to LoRaWAN, however, it uses different frequency bands. It uses the infrastructure built by Sigfox and its partners and messages (with a maximum payload size of 12 bytes, and a maximum frequency of 140 messages per day) are transmitted to the cloud (backend.sigfox.com) from which they can be obtained through the REST API.
The communication was tested between sensors and the Sigfox cloud using curl utility to retrieve data via httpsHTTPS connection.
| Kotva |
|---|
| komunikacna_linka |
|---|
| komunikacna_linka |
|---|
|
Communication line configuration
...
| Parameter | Description | Unit / size | Default Value |
|---|
| Type of connection between the D2000 KOM process and the other party (LoRaWAN gateway, network server, cloud).
Currently supported are:- Kerlink IoT Station SPN (JSON via UDP packets): communication with Kerlink IoT Station with firmware SPN (Small Private Network). Line must be of the SerialOverUDP Device Redundant type.
- MQTT Client (JSON via MQTT): communication with a network server or cloud using MQTT protocol. The line must be of the TCP/IP-TCP type.
- Sigfox Client (JSON via HTTPS): communication with Sigfox cloud
| - | Kerlink IoT Station SPN |
| Name of the field with an identifier of the LoRaWAN device (mote).
Note: For JSON messages that can be structured, the syntax level1.level2.level3 ... is supported e.g. rx.moteeui and if they contain fields (indexed from 1) then also the syntax level1[index1].level2[index2].level3 ... is supported e.g. rx.gwrx[1].time. As examples, see the description of I/O tags of the Envelope type.
Note: For Sigfox data files, which may contain multiple values (historical), index 0 resp. empty index (e.g. data[].device) can be used. This indicates that all field elements are to be processed. | - | rx.moteeui |
| Name of the field with the payload. See the notes next to the Mote Field Name parameter. | - | rx.userdata.payload |
| A method of payload encoding in the message. Supported encoding:- Base16 + Base64 encoding (Kerlink SPN) - for Connection Type=Kerlink IoT Station SPN
- Base64 encoding (TheThings.network) - for Connection Type=MQTT Client communicating with TheThings.network cloud
- Base64 encoding (Loriot, Slovanet, Sigfox) - for Connection Type=MQTT Client communicating with LoRaWAN clouds (Lorio, Slovanet) as well as Sigfox
- None - message contains a payload without encoding - not yet used
| - | Base16 + Base64 encoding |
| Name of the field with a timestamp. If the field is not found, the current time is assigned to the values. See the notes next to the Mote Field Name parameter. | - | rx.gwrx[1].time |
| Mask for parsing a value in the field with a timestamp.
Note: from settings of time station parameters depends whether the time is interpreted as local or UTC with configured offset.
Special masks are:- UNIX - the numeric value represents the number of seconds from epoch 00:00:00 01.01.1970 UTC.
- UNIXMS - the numeric value represents the number of milliseconds from epoch 00:00:00.000 01.01.1970 UTC.
| - | yyyy-mm-dd hh:mi:ss |
| The name of the field indicating the message type. If the value is empty, the message type is not distinguished. (For example, cloud Loriot sends messages of various types.) | - |
|
Frame Type Field Required Value | If the message type differentiation is active (non-empty value of Frame Type Field Name parameter), the message type must match the specified value, otherwise, the message is ignored. | - |
|
| Writing detailed information about sending and receiving values in a log file. | YES/NO | NO |
| Parameters specific for Connection Type=MQTT Client. |
| See the description of the User Name parameter in the MQTT protocol documentation documentation. |
| See the description of the Password parameter in the MQTT protocol documentation documentation. |
| See the description of the Topic Filter parameter in the MQTT protocol documentation documentation. | +/+/+/up |
| See the description of the Subscribe QoS parameter in the MQTT protocol documentation documentation. |
| See the description of the Client ID parameter in the MQTT protocol documentation documentation. |
| See the description of the Clean Session Flag parameter in the MQTT protocol documentation documentation. |
| Format of JSON message used while writing a value. The content of the I/O tag of Write type will be encoded (depending on the Payload Encoding parameter) and inserted into the message, where it will replace the #PAY# string.
The default value "{"port":1, "confirmed":false, "payload_raw":#PAY#} was tested when sending data to cloud TheThings.Network. | - | "{"port":1, "confirmed":false, "payload_raw":#PAY#} |
| See the description of the Publish QoS parameter in the MQTT protocol documentation. |
| See the description of the Ping Interval parameter in the the MQTT protocol documentation. |
| See the description of the Reply Timeout parameter in the the MQTT protocol documentation. |
| See the description of the Wait Timeout parameter in the the MQTT protocol documentation. |
| See the description of the Max. Wait Retry parameter in the the MQTT protocol documentation. |
Line parameters tested for Connection Type=Kerlink IoT Station SPN for Kerlink IoT Station 868 with firmware SPN
...