Device lifecycle
Device lifecycle
After Bind a device via API, day-two operations use current v2 device APIs and device capabilities for maintenance. Legacy list HTTP is not the new-integration default. Index: Device management and Legacy APIs.
Query current details
| Need | Current entry |
|---|---|
| Page through bound devices | Paged device detail (device.detail.page) |
| Known serial numbers | Batch detail (device.detail.list) |
| Online / offline | Online status (device.status.get) |
| Bind flag | Bind state (device.bindstate.get) |
Legacy list methods such as deviceList are documented under Legacy APIs for existing clients. New integrations should use device.detail.* on Device management. Sub-account list helpers stay on the main device path: subAccountDeviceList, subAccountDeviceInfo.
Rename, password, upgrade
These old HTTP methods are explicitly replaced. Use the v2 maintenance pages:
| Old HTTP (do not prefer) | Current entry |
|---|---|
modifyDeviceName | Rename device (device.name.set) |
modifyPassword | Change password (device.password.set) |
upgradeDevice | Trigger upgrade (device.upgrade.execute) |
upgradeProcessDevice | Upgrade progress (device.upgrade.process) |
Pages: Legacy APIs. Capability errors: Capability errors.
Unbind
unBindDevice stays under Device management. After unbind, query APIs stop returning the serial number.
Related
- Set up a sub-account if an app user must operate the device.
- Device capability integration for other old HTTP.