Set the KIN counter offsets for a Bluetooth tag
PUT/v1/bluetooth-tags/:telematicsDeviceId/counter-offsets
Persist the KIN counter offsets for a Bluetooth tag by proxying to the Telematics Device Configuration API's generic device-state PATCH endpoint (PATCH /telematics-devices/{id}/state) with a nested desired.sensor.activity.<counter>.offset body. Values are integer seconds for the three duration counters and an integer event count for extreme events. Negative values are allowed. The client MUST supply exactly the counters that apply to the target device: KIN1 requires only movingOffsetInSeconds (operatingOffsetInSeconds, overloadOffsetInSeconds, and extremeEventsCountOffset MUST be null); KIN2 requires all four fields. Missing required fields or unsupported fields on KIN1 yield 400. Non-KIN devices yield 400. Devices not attached to any asset are rejected with 409.
Request
Responses
- 204
- 400
- 401
- 403
- 404
- 500
No Content
Bad request
Invalid or missing bearer token in Authorization header
User not allowed to make this request
Resource not found
Internal server error