IoT

Every device in one registry, every reading into a workflow.

One IoT app runs every device in the building: temperature sensors, put-to-light racks, door contacts, location tags and more — one registry, one health board, one rule engine that turns readings into jobs, alerts and audit trails. The hardware is ordinary and cheap; the value is in the software.

Clay-style illustration of IoT devices in a warehouse: small sensors on shelves, a glowing gateway box and a worker checking a dashboardClay-style illustration of IoT devices in a warehouse: small sensors on shelves, a glowing gateway box and a worker checking a dashboard

About this product

Docklify IoT is the one registry for every device around the work — sensors, lights, cameras, speakers, gateways — and the orchestration layer that turns their signals into action. Devices connect through one adapter per device or interface, self-registered, so the floor team manages one device file, one health board and one alert center instead of a different console per gadget. A LoRa temperature sensor, a put-to-light module and a forklift telematics unit all speak the same event language, and the same orchestration engine — trigger, condition, action — decides what happens next. The business result never lives here: temperature curves go back to WMS, yard occupancy to Yardor, and the operator’s day stays in the apps they already use.

What it is for

Who it is for:For warehouse managers and device admins who run the building's hardware and want one place to see it all.

Warehouse managers

Temperature compliance in cold chain and pharma: automatic logging, over-limit alerts, and records that stand up to audit.

Packing and sorting teams

Light-guided sorting and picking: the right slot lights up, the count shows on the module, and hands stay on the goods.

Dock and gate teams

Gate and dock sensor kits: vehicle presence and door state, wired into the appointment flow.

Fleet and equipment

Forklift collision warnings and fleet telemetry: impacts, speed and location, on the record.

Core workflow

  1. Add a device with the guided setup — one adapter per device type.
  2. Watch health and readings on one board, with calibration on the record.
  3. Rules turn readings into actions: alert, job, or automated response.
  4. Results land where the work happens — the warehouse, the yard, the dock.
  5. Every reading, rule and action stays on an append-only audit trail.

Key features

Clay illustration: a single device registry book with sensors, lights and gateways lined up beside itClay illustration: a single device registry book with sensors, lights and gateways lined up beside it

One device registry

Every device in the operation has one file: what it is, where it is, what it is bound to, and whether it is healthy. Binding ties a device to the place or job it serves — a sensor to a cold room, a light module to a wall slot, a gateway to a yard — and the binding is the reference, not a second writable copy somewhere else. Health and freshness are judged at one point, so a stale sensor and a dead gateway read the same way everywhere: the device is either reporting or it is not, and the alert center says so in plain words. The file also carries the device’s picture, its calibration record and its install history, so a technician arriving on site already knows what they are looking at.

Clay illustration: ten small devices in a row — camera, sensor, light module, tag, speaker, forklift unitClay illustration: ten small devices in a row — camera, sensor, light module, tag, speaker, forklift unit

Ten device classes

The catalog covers ten classes, and each one earns its place by solving a real warehouse job. Cameras count what sits in the yard. LoRa sensors watch temperature and humidity for compliance. Put-to-light modules guide sorting and picking. Gate and dock kits sense vehicles and doors. BLE tags locate assets by zone. Speakers announce. Forklift telemetry watches collisions and driving. Gas sensors watch the air. Water sensors watch for leaks. And a depth camera measures boxes and pallets. Classes outside the ten — self-built hardware, centimeter-grade UWB, a tag on every pallet, weighing smart shelves — are explicitly out, so the catalog stays honest about what it does.

Clay illustration: plugs and adapters clicking into one hub, each device type with its own matching socketClay illustration: plugs and adapters clicking into one hub, each device type with its own matching socket

One adapter per device

Every device type arrives through its own adapter, self-registered in the adapter registry: one device or interface, one adapter, and the layers above only ever see one uniform capability and one event shape. The warehouse team never writes a driver — a new device class lands as one new adapter, with its contract frozen before construction: what it reports, what commands it accepts, and how health is judged. The Device Hub carries the same pattern to the edge: its camera sources, inference dispatch and credential vault already run on it, so the box on the packing bench and the gateway in the yard speak the same language.

Clay illustration: numbered event cards flowing into an engine that sends out numbered action cardsClay illustration: numbered event cards flowing into an engine that sends out numbered action cards

Events and actions, numbered

Devices speak in events, and the platform answers in actions — both catalogued, numbered and added to only, never rewritten. The event catalog lists every device event by number, from a temperature reading crossing its limit to a forklift impact, and the action catalog lists every answer: sound the speaker, light the module, notify the supervisor, open a task. A streaming evaluator watches events as they arrive and settles each one against its rule, so an over-limit reading becomes a ticket while it is still true, not in tomorrow’s report. Nothing in the catalog is a slogan: each entry names its trigger, its evidence and its cost.

Clay illustration: a small engine with three gears — trigger, condition, action — and a human hand on a confirm leverClay illustration: a small engine with three gears — trigger, condition, action — and a human hand on a confirm lever

Orchestration engine

The orchestration engine is the platform’s shared automation, not a private script per device: trigger, condition, action, with human steps, timeouts and branches. A temperature breach opens a task, assigns it, waits for the check, and escalates if nobody answers. An AI step starts as a suggestion that a person confirms — the engine never lets a model act alone on a decision that moves stock or money. The engine lives in the platform base, so any trigger source can use it: a device event today, a schedule or a business event tomorrow, with the same three tiers and the same risk-graded permissions.

Clay illustration: a temperature sensor on a cold-room wall, its reading curve rising past a red limit lineClay illustration: a temperature sensor on a cold-room wall, its reading curve rising past a red limit line

Temperature compliance, on the record

LoRa sensors sample temperature and humidity on schedule and write every reading to the record automatically — no clipboards, no end-of-shift typing. A reading over the limit raises an alert and opens the response task in the same breath, and the record is append-only: once written, a reading is never edited, so the history a food or pharma auditor reads is the history that happened. Calibration travels with the device file, and the sensor’s battery and signal are part of the same health picture, so a dying sensor is replaced before it goes quiet.

Clay illustration: a sorting wall with glowing light modules and a depth camera measuring a box on a benchClay illustration: a sorting wall with glowing light modules and a depth camera measuring a box on a bench

Light-guided work and dimensioning

Lights lead the hands. A put-to-light module sits above every sorting-wall slot — no display, just light: scan a tote and the target slot lights up, and a full slot turns steady to call for merging and packing. A pick-to-light module at every pick face adds a quantity display: the module for the current step lights up and shows how many to pick, and the picker confirms on the module’s button. And a depth camera measures what the hands just packed: boxes and pallets dimensioned to the millimeter, so the carton, the label and the freight quote all start from a true size.

The everyday essentials

Onboarding wizard

Guided device setup: register, bind and accept, step by step.

Health dashboard

Every device’s freshness at a glance, with the stale ones on top.

Groups and bindings

Group devices by area and bind them to the locations and jobs they serve.

Alert center

One queue for every device alert, with the evidence attached.

Rules configuration

Thresholds, schedules and escalation, set per device or per group.

Diagnostics and firmware

Remote diagnosis and firmware rollout with staged release and rollback.

Roles

Warehouse admins, supervisors and device admins — operators never need this app.

Offline autonomy

Edge execution keeps working when the network drops, and syncs back after.

Ecosystem support

Vision

The camera registry belongs to Vision, not to IoT: one camera file for the whole platform, owned by the Vision base registry, while IoT manages every other device class around it. Camera sources register once and every screen reads the same file, so the console, the event center and the playback layer never disagree about which camera is where.

WMS

Temperature curves, light-guided picking and dimensioning feed straight into warehouse work: the cold room’s breach becomes a WMS task, the light module answers to the WMS task engine, and the measured box sizes the carton before the label prints. The same task engine that guides picking also answers the light module, so the light and the phone never disagree about the next step.

Device Hub

Pairing, heartbeat and over-the-air updates reuse the Hub pattern: the desktop hub on the packing bench and the gateway in the yard register the same way, report health the same way, and take commands only through the whitelisted command channel. A hub that loses its network keeps the last good configuration and keeps working, then reports what it did when the link returns.

How it connects:IoT manages the devices; the work shows up where it belongs. Yard occupancy goes to the yard, temperature curves and over-limit handling go to WMS, dock occupancy goes to WMS and the yard. Cameras stay in Vision's registry — IoT never keeps a second camera list — and the orchestration engine lives in the base, so any trigger source can use it.

Ready to put it to work?

Explore the other apps