IoT Device Network Events

This dataset provides a comprehensive event log from diverse IoT devices deployed in a smart building, including device identifiers, event types, sensor readings, and maintenance indicators. It enables robust anomaly detection, predictive maintenance, and spatial analysis of device health and performance across locations and time. The rich event details support operational monitoring, troubleshooting, and optimization of building systems.

  • last updated 21 Aug 2025
  • by GoMask
The brief that made it

Real-time anomaly detection for building security and safety

Sample rows

preview · 8 of 200 rows · all 17 columns
event_idstringdevice_typestringsensor_reading_valuefloatmaintenance_requiredbooleansensor_reading_unitstringdevice_idstringdevice_location_floorintegerdevice_location_roomstringevent_timestampdatetimeevent_typestringevent_severitystringfirmware_versionstringbattery_levelfloatnetwork_statusstringanomaly_scorefloatassigned_technician_idstringevent_descriptionstring
EVT-0001camerablanktrueblankDEV-CAM-015Roof2024-06-01T08:15:23Zanomalycriticalv2.3.222.5degraded0.89TECH-101Camera detected unauthorized motion on roof.
EVT-0002thermostat22.8false°CDEV-THM-032ConfRoom2024-06-01T08:45:12Zreadingblankv1.4.595.2onlineblankblankThermostat reported temperature reading.
EVT-0003water_leak_sensorblanktrueblankDEV-WLS-010Basement2024-06-01T09:02:48Zalertcriticalv1.1.914.6offlineblankTECH-112Water leak detected near main pipes.
EVT-0004humidity_sensor46.1false%DEV-HUM-031Lab2024-06-01T09:30:15Zreadingblankv1.0.782.3onlineblankblankHumidity sensor captured reading.
EVT-0005smoke_detectorblanktrueblankDEV-SMK-011Kitchen2024-06-01T09:46:37Zalertcriticalv2.0.117.9degradedblankTECH-109Smoke detected in kitchen area.
EVT-0006environmental_monitorblanktrueblankDEV-ENV-014ServerRoom2024-06-01T10:12:21Zanomalywarningv2.1.066.7degraded0.74TECH-104Environmental monitor detected temperature spike.
EVT-0007thermostatblankfalseblankDEV-THM-013OfficeA2024-06-01T10:45:49Zstatus_updateinfov1.4.367.6onlineblankblankThermostat operating within normal range.
EVT-0008light_sensor1230.6falseluxDEV-LUX-012Lobby2024-06-01T11:05:32Zreadingblankv1.2.599.8onlineblankblankLight sensor reported illumination level.

What the 200 rows show

from the 200-row sample

Light_sensor (device type) stands out: mean sensor_reading_value is 1,285, against 33.1 for the rest.

  • 30%maintenance_required = true
  • 45.8median sensor_reading_value
  • 3event severities
  • 3network statuses
  • 5event types
  • 28device location rooms
Mean sensor_reading_value by device_type76 rows
01,0002,00022.0thermo…13 rows44.1humidi…28 rows22.0enviro…3 rows1,285light_…28 rows0.01smoke_…4 rows
sensor_reading_value76 rows, in bands of 200
02550480001614708001,600sensor_reading_value →

Median 45.8, from 0.0 to 1,532.

sensor_reading_unit76 rows with a value · 124 left blank
  1. %28
  2. lux28
  3. °C16
  4. ppm4
17 columns by typefrom the column list below
  • string 11
  • integer 1
  • float 3
  • datetime 1
  • boolean 1

Columns

17 columns in four groups
blueprint · 17 columns
columntypedescriptionexample
Text 11 columns
event_idstringUnique identifier for each event recorduniqueEVT-0001
device_idstringUnique identifier for the IoT device generating the eventDEV-CAM-01
device_typestringType or model of the IoT device (e.g., thermostat, camera, sensor)8 typescamera
device_location_roomstringRoom identifier or name where the device is installedoptionalRoof
event_typestringType of event (e.g., status_update, anomaly, alert, reading)status_update · anomaly · alert · reading · maintenanceanomaly
event_severitystringSeverity level of the event (e.g., info, warning, critical)info · warning · critical · optionalcritical
event_descriptionstringDetailed description or message associated with the eventoptionalHumidity reading: 45.7%
sensor_reading_unitstringUnit of measurement for the sensor reading (e.g., °C, %, lux)4 units · optional°C
firmware_versionstringFirmware version running on the deviceoptionalv2.3.2
network_statusstringNetwork connectivity status of the device (e.g., online, offline, degraded)online · offline · degraded · optionaldegraded
assigned_technician_idstringIdentifier for technician assigned to the device/event (if applicable)optionalTECH-101
Numbers 4 columns
device_location_floorintegerFloor number where the device is located0 or more · optional5
sensor_reading_valuefloatNumeric value reported by the device (if applicable)optional22.8
battery_levelfloatCurrent battery level of the device as a percentage (0-100)0 to 100 · optional22.5
anomaly_scorefloatScore indicating likelihood of anomaly (0-1, higher is more anomalous)0 to 1 · optional0.89
Dates and times 1 column
event_timestampdatetimeDate and time when the event occurred2024-06-01T08:15:23Z
True or false 1 column
maintenance_requiredbooleanIndicates if the device requires maintenanceoptionaltrue

Use it for

  • maintenance re…30%60 of 200 rowsmean sensor reading v…22.0ther…44.1humi…22.0envi…1.3kligh…

    A technology dashboard

    The maintenance_required rate, sensor_reading_value by device_type and a breakdown of sensor_reading_unit. Excel, Power BI or Tableau.

  • Why do the 28 light_sensor rows have a mean sensor_reading_value of 1,285?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable events with device_id, device_type and device_location_floor to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 17 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset200 rows17 columns
Yours1,000 rows17 columnsdevice_location_floor: UK only

blueprint · iot-device-network-events

Behind this dataset

Same schema. As many rows as you need.

These 200 rows came out of a blueprint — 17 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each event has device ID, timestamp, event type
  • Critical events must be acknowledged
  • Devices grouped by network segment
  • Event frequency tracked per device
  • Offline events flagged for investigation
Rows
Open the blueprint in Data Factory

1 credit per row. New accounts start with 25 free credits.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
iot-device-network-events

More in Technology

Browse all
Also in TechnologySmart City Technology Failure LogsTech Support Ticket AnalyticsSupport TicketsAll 1,954 datasets

What should your data show?

Preview 20 rows free
No signup. No card.