Skip to main content

Cellular IoT Communication

This page describes the possible uplink and downlink message contents when using NB-IoT or LTE-M (cellular IoT) as technology to communicate with the Lobaro IoT Platform, e.g. the firmware WAN parameter must be configured to lte.

Parsed and optionally decrypted Wireless M-BUS data can be viewed and further processed in the Lobaro IoT platform. Third-party systems can be integrated to retrieve Wireless M-BUS data and status information using various platform integrations. This enables seamless data forwarding via protocols like MQTT, HTTP-Push, or REST interfaces without requiring in-depth knowledge of the platform's communication with the device.

For communication between Lobaro products and the Lobaro IoT Platform, an optimized, low-power protocol secured by TLS is used.

SaaS instance Lobaro Platform

The SaaS instance is available at platform.lobaro.com and is free to use for testing purposes. To gain access, please contact Lobaro.

CoAP Protocol

The protocol details of the CoAP implementations will not be disclosed and are only used in conjunctions with the Lobaro IoT Platform. When looking for integration with third party systems, MQTT is the preferred protocol.

MQTT Protocol

With the V4-Series and app-nrf91-origin firmware family, Lobaro now offers a solution to connect to third-party MQTT brokers. See also the 'host' parameter description here in tab 'MQTT'.

Lobaro offers also a MQTT reference implementation in Phyton, please contact the Lobaro sales team.

tip

The Lobaro IoT Platform can also function as an MQTT broker or provide device management services alongside an external MQTT broker.

We highly recommend starting with the Lobaro IoT Platform, as it offers a straightforward and secure way to manage your devices and data. Integration with third-party systems can then be implemented step by step for a smoother transition.

Lobaro root certificate

Our devices are signed (via an intermediate) by our own device root certificate. Thus it is enough to trust the Lobaro CA to trust all devices. Devices might have different Intermediate CAs which are all signed by the Lobaro Root CA. If your MQTT / CoAP server does not trust this certificate, the connection will naturally be rejected.

The certificate can be downloaded here; if you should add it as a trusted CA on your server.

The cipher suites supported by our device are:

  • TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
  • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
  • TLS_ECDHE_ECDSA_WITH_AES_128_CCM
  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256