Project description
TranslatedOur fleet of connected field equipment is growing, and we're drowning in raw numbers because there's no single place to actually monitor them. The task is to build a full-featured IoT telemetry dashboard that receives device readings over MQTT, stores them as time series, and transforms them into a picture that an operator can understand at a glance. The basic cycle is simple but must work flawlessly: devices publish measurements to broker topics, the backend subscribes and parses these packets, values are written to time series storage, and the frontend renders them without manual page refresh. A reliable data reception pipeline matters to us more than any visual decorations.
On screen we expect live line graphs for each metric, numeric gauges for latest values, and a clear device control section where we can register new equipment, see which nodes are online, and view history for any individual sensor. Threshold alerts are mandatory: for each metric we set lower and upper bounds, and when a reading goes out of bounds the dashboard must visually highlight the device and record an event so nothing is lost overnight. Make the layout responsive and easy to read: the team will keep it open both on wall-mounted screens and laptops. This is specifically about device telemetry, not a public status page or a general business analytics tool, so the focus is on sensors, readings, and the physical equipment behind them.
We'll provide access to the broker, packet format descriptions, and a set of test devices. We expect clean documented code that we can deploy ourselves, plus brief notes on configuring data reception and alert rules.
— MQTT subscriber that receives and parses device packets
— Time series storage with fast history queries
— Live line graphs and numeric gauges in real time
— Configurable threshold alerts with upper/lower bounds and event log
— Device management: registration, list, online status, per-sensor history
— Responsive layout for wall-mounted screens and laptops
On screen we expect live line graphs for each metric, numeric gauges for latest values, and a clear device control section where we can register new equipment, see which nodes are online, and view history for any individual sensor. Threshold alerts are mandatory: for each metric we set lower and upper bounds, and when a reading goes out of bounds the dashboard must visually highlight the device and record an event so nothing is lost overnight. Make the layout responsive and easy to read: the team will keep it open both on wall-mounted screens and laptops. This is specifically about device telemetry, not a public status page or a general business analytics tool, so the focus is on sensors, readings, and the physical equipment behind them.
We'll provide access to the broker, packet format descriptions, and a set of test devices. We expect clean documented code that we can deploy ourselves, plus brief notes on configuring data reception and alert rules.
— MQTT subscriber that receives and parses device packets
— Time series storage with fast history queries
— Live line graphs and numeric gauges in real time
— Configurable threshold alerts with upper/lower bounds and event log
— Device management: registration, list, online status, per-sensor history
— Responsive layout for wall-mounted screens and laptops
Web programming Cash, Bank transfer
