Devices
Understand IoT digital twins in Kilo: connect hardware, replace sensors, and keep an asset's measurement history together.
A Digital Twin in Kilo IoT Server is a persistent digital device representing something you monitor or control: a refrigerator, a pump, a vehicle, or an individual sensor. Its name, measurements, history, and configuration belong to that digital record. Physical hardware supplies the readings through a connector and can be replaced without creating a new twin.
This is useful whenever the equipment you care about lasts longer than the sensor measuring it. A refrigeration operator needs the temperature record for Refrigerator 1, even after its original probe is replaced. Building the monitoring around the refrigerator's twin keeps that record together across hardware changes.
What does the Devices page show?
Open Devices in the main menu.
Add device (top right) starts the registration flow for a new device. See Registering Devices.
Metrics opens the shared metric catalog. See Metrics.
Search by name filters the list as you type.
The Device name and Creation date headers sort the table. The Status column shows when each device last reported; the time and the dot update on their own while the page is open, so you do not need to refresh.
Edit opens the device editor (see Emulated Devices for a tour of its tabs), Clone creates a copy, and Delete removes the device after a confirmation.
How an IoT digital twin connects to hardware
Three parts work together:
Digital device
The lasting record of the monitored object
Refrigerator 1, with its name, photo, and measurements
Connected source
The hardware or emulator supplying data through a connector
A LoRaWAN temperature probe
Measurements
The readings mapped onto the twin
Temperature in °C and the probe's battery level
A digital device has one connected source at a time. That source can provide several measurements. Supported source types include LoRaWAN, MIOTY, MQTT-connected equipment, vehicle trackers, and the Emulator. A protocol adapter can bring other equipment in through MQTT; the connector must receive a supported payload and the readings must be mapped.
A metric template defines what a measurement means, including its unit and value type. A connector key is the field name arriving from the source. Mapping connects the two, so a probe reporting temp_c and its replacement reporting temperature can feed the same temperature measurement on the twin. See Metrics.
Replacing a refrigeration probe without starting over
Consider a pharmaceutical refrigerator whose probe is replaced after a failure or because it no longer meets the operator's calibration requirements:
Register a digital device named Refrigerator 1 and connect the installed probe.
When the probe needs replacing, open Refrigerator 1 and detach its physical device from the Connection tab.
Bind the replacement probe to that same digital device. Reconnect its incoming fields to the existing measurement rows.
Check the new values and timestamps, then review a history range spanning the replacement.
The refrigerator keeps its identity and existing measurement history. Dashboard and rule references to those retained measurements continue to refer to the same record. The new probe supplies future readings; it does not erase the old probe's readings or fill a gap when no probe was reporting.
Follow Replace a physical sensor for the detailed procedure. Keep the existing measurement rows when changing a source: deleting and recreating them is a different operation from remapping their incoming fields.
Build around the asset's lifecycle
The same model supports more than replacement. Create the digital device before commissioning hardware, give it an asset-oriented name, and add a photo that helps the team recognize it. Use Application to associate it with the solution it belongs to. Use the Emulator to prepare dashboards and automation with generated readings before connecting real equipment.
Once hardware reports, the twin's measurements can feed dashboards, alarm conditions, and rules. Where the hardware supports it, commands also let users or rules request an action and check reported feedback. Replacing an actuator requires checking its command payloads and routing against the new model, even when the twin stays the same.
Across multiple refrigerators or sites, consistent metric definitions let the team compare the same kinds of readings while each asset keeps its own record.
How long history is retained
History remains subject to the retention period included in your plan or agreed for your organization. Replacing a probe does not reset that period or extend the lifetime of older readings.
For longer-term refrigeration records or other compliance and operational needs, contact the team to discuss extended retention. See Data retention for plan limits and the request route.
Choose the source for your digital twin
LoRaWAN sensor
LoRaWAN Devices — profiles, radio identity, decoding and first readings
MQTT publisher or bridged sensor
MQTT Devices — connect messages to a twin and its measurements
GPS tracker
Tracker Connector — tracker identity, model and reporting endpoint
MIOTY endpoint
MIOTY Devices — endpoint configuration and blueprint decoding
Generated readings
Emulated Devices — prepare a deployment before hardware arrives
In this section
Registering Devices — the shared registration flow, and the fields each connector type asks for.
Device Management — replace a physical sensor while keeping its twin, manage mappings, and review history.
Device Diagnostics — why a device is silent: reception status, pipeline, and the event feed.
Metrics — units, metric keys and templates that normalize raw sensor data across manufacturers.
Payload Decoding and Connector Keys — see which fields a device reports and what values they carry.
MIOTY Devices and MIOTY Blueprints — commissioning MIOTY endpoints and decoding their payloads.
Emulated Devices — devices that generate their own data, so you can build before the hardware arrives.
Device Commands — defining, confirming and dispatching the actions a device can perform.
Last updated