Home / Documentation / Devices

Devices

Device management is about "this specific device". It is where devices are registered, monitored day to day, inspected for data, sent commands and tagged with a location — so it is the module operations staff spend most time in.

6 sections · Updated with each platform release

Register a device

Jiwu AIoT Platform · [object Object] Interface mock
ProductsDevicesData ScreensAI AssistantCredentials
Devices Export + Add device
Product: Air compressor type A Status: All Search
Device nameProductStatusLast reportedWorkshop 3-Air compressor-01Air compressor type A● Online2 seconds agoWorkshop 3-Air compressor-02Air compressor type A● Online5 seconds agoWorkshop 2-Air compressor-01Air compressor type A○ Offline3 hours ago
[object Object]
  1. 1[object Object]
  2. 2[object Object]
  1. Open "Devices" and choose "Add device".
  2. Select the product the device belongs to — this decides which properties the device has.
  3. Enter the device name and a note; include the location in the name (for example "Workshop 3-Air compressor-01").
  4. Set the device group and geographic location as needed, so you can filter by area and see it on the map later.
  5. After saving, the platform generates the device identity used by the device side to connect.

NoteThe device name is the field most often searched during operations, so agree on a naming rule before onboarding, for example "location-device type-index".

Status: online state and online records

  • The device list shows the current online state of every device and can filter out offline devices.
  • Online records show the device’s connect and disconnect trail on a timeline, which tells you whether it "keeps dropping" or "disconnects occasionally".
  • Together with online records you can work out active periods, which helps plan inspections and network tuning.

NoteFrequent connect and disconnect cycles are usually not a platform problem; check the stability of the on-site network and the heartbeat interval configured on the device first.

Data: live stream and historical curve

Jiwu AIoT Platform · [object Object] Interface mock
Workshop 3-Air compressor-01 Online Send command
Pressure0.72 MPaDischarge temperature78.4 ℃Runtime1264 hMotor current42.6 A
Live data stream
14:02:11　Pressure 0.72 MPa 14:02:11　Discharge temp 78.4 ℃ 14:02:06　Motor current 42.6 A
Pressure trend (last 24 hours)
0.6 – 0.8 MPa

After onboarding, check the live data stream first to confirm the device is reporting; when a screen shows no data, come back and verify the field names.

[object Object]
  1. 1[object Object]
  2. 2[object Object]
  3. 3[object Object]
  • Live data stream: shows the latest fields and values a device reported, in streaming form, to confirm whether the device is actually sending data.
  • Historical data: queries a device property’s time series over a time range, for trends and anomaly analysis.
  • The data stream page suits early checks after onboarding; historical data suits day-to-day analysis and fault investigation.

NoteIf the live data stream has values early on but the data screen stays empty, the property name selected on the screen most likely does not match the field name the device actually reports.

Send a command

When a device needs to be operated remotely, open command dispatch from device details and the platform delivers the command to the device.

  1. In device details, choose "Send command".
  2. Select the service to invoke (defined by the product’s thing model) and fill in the parameters.
  3. After submitting, the platform records what was sent and the execution result, which can be reviewed in the history.
  4. If the device does not acknowledge as specified, the platform marks it unconfirmed and the device must be checked on site to see whether it really executed.

NoteSending a command operates field equipment directly, so always confirm the parameter range and the device’s current state; for critical operations, verify on one device first.

Location and maps

  • Devices can be tagged with a geographic location and viewed together on Tianditu or Baidu Maps.
  • This suits scenarios with dispersed sites (pump stations, street lights, base stations, refrigerated vehicles), where the map view locates anomalies quickly.

Device will not connect? Check in this order

  1. Check whether the device is online: if it is offline, start with on-site power and network.
  2. Check whether the live data stream shows new data: online but silent usually means the reported fields do not match the thing model.
  3. Verify the product-device binding: a device registered under the wrong product will have mismatched properties.
  4. Compare the reporting frequency with the time shown by the platform: a device whose clock is out of sync makes data look stale.
  5. Confirm protocol-side configuration: for Modbus devices, verify the gateway point table, the slave address and the register address.