Skip to main content
LIOMO
Request a demo

Technology · IoT & Connectivity

Reliable data starts at the device

We choose the sensors, gateways and networks that suit each site, then configure and look after them so data keeps arriving long after installation day.

Talk to an engineerExplore our solutions

Overview

The physical layer decides what is possible

Every connected system depends on a device somewhere: a tracker in a vehicle, a probe in a cold room, a meter on a distribution board. If that device is the wrong fit, poorly powered or badly installed, no software can recover the data it failed to send.

We treat device and network choices as engineering decisions, made against the site: what needs measuring, how often, where power is available, which networks reach the location and how much data actually needs to move. The answer is often a mix, such as cellular for vehicles and remote assets, LoRaWAN for sensors spread across a large site, and Ethernet or Wi-Fi where the infrastructure already exists.

Our own fleet platform shows this in practice. Trackers report to LIOMO Fleet over TCP using the Teltonika Codec 8 protocol, and the LIOMO gateway decodes and validates every packet and stores each position before the platform raises alerts, geofence events or fault-code events.

Connectivity options · relative, general characteristics

Principles

How we approach devices and networks

  • 01

    Start from the measurement

    We define what must be measured, how often and how accurately before choosing a device, not the other way round.

  • 02

    Fit the network to the site

    Coverage, power, data volume and running costs decide between cellular, LPWAN and local networks, and we check them where the devices will live.

  • 03

    Plan for gaps

    Networks drop and devices restart. We favour devices that hold readings until they can send them, and software that accepts data arriving late.

  • 04

    Manage devices as a fleet

    Configuration and health are managed centrally, and routine changes such as reporting intervals are made remotely rather than device by device on site.

Building blocks

What the connected layer is made of

A typical LIOMO system draws on the layers below. Each project uses only the parts the site needs.
  1. 01

    Devices and sensors

    Hardware that measures, tracks or switches something in the physical world.

    • GPS trackers
    • Temperature and humidity probes
    • Door and contact sensors
    • Fuel-level sensors and energy meters
    • Relays and digital inputs
  2. 02

    Gateways and edge

    Devices that collect local readings, hold them during outages and forward them to the platform.

    • LoRaWAN gateways
    • Industrial edge gateways
    • Local buffering
    • Protocol translation
  3. 03

    Networks

    The links that carry data from the site to the platform, chosen for coverage, power and data volume.

    • LTE-M
    • NB-IoT
    • 4G LTE
    • LoRaWAN
    • Wi-Fi and Ethernet
    • Bluetooth LE
  4. 04

    Protocols

    The message formats and rules that devices, gateways and platforms use to exchange data.

    • MQTT
    • TCP
    • Teltonika Codec 8
    • Modbus RTU and Modbus TCP
    • HTTPS
  5. 05

    Device management

    The tools that keep every device registered, configured and accounted for once it is installed.

    • Device registry
    • Remote configuration
    • Reporting intervals
    • Last-seen and health checks
    • Remote commands

Engineering practices

Engineering practices

Survey before hardware
Signal coverage, mounting points, power and access are checked at the site before the device list is fixed.
Power budgets
For battery devices, reporting interval, network type and sensor load are set against the battery life the site needs, and the trade-offs are written down.
Installation that lasts
Cable routes, enclosures, antenna placement and labelling are specified, so the installer knows what to do and a technician can find it later.
Validate at the gateway
Incoming packets are decoded and checked before anything is stored, so malformed or impossible readings never reach a report.
Honest sensor data
A "no signal" value is marked as missing rather than plotted as a false spike, and readings older than 15 minutes are flagged as stale.
Calibrated readings
Sensors such as fuel-level probes are calibrated so the platform shows real units, like litres, instead of raw sensor values.

Applied in

Solutions

FAQ

Questions buyers ask

Which network should our devices use?

It depends on the site. Vehicles and widely spread assets usually suit cellular networks such as LTE-M, NB-IoT or 4G. Many low-power sensors across one large site often suit LoRaWAN with a local gateway. Where Wi-Fi, Ethernet or Bluetooth LE is already available, it can be used. We check coverage and power on site before recommending one.

Can you work with devices we already have?

Often, yes. If a device sends data over a documented protocol such as MQTT, Modbus or a published TCP format, it can usually be brought into a LIOMO system. We assess each device and its documentation before committing to it.

What happens when a device loses its connection?

Well-chosen devices keep readings in memory and send them when the connection returns, and the platform should accept that late data in its proper place. On LIOMO Fleet, sensor readings older than 15 minutes are flagged as stale rather than shown as current.

Who installs the hardware?

LIOMO selects, registers and configures the devices and coordinates installation, with a specification for mounting, cabling and antenna placement. Depending on the site and the equipment, the work may also involve qualified electricians or the equipment owner.

Technology areas

Discuss the technical side of your project

Bring your engineers. We are happy to go into protocols, data models, security and integration details.

Request a demoContact us