system.diagnostics.rebootState (Set reboot state)

system.diagnostics.rebootState: Set reboot state

system.diagnostics.rebootState · device scope · permission Config

What it does

Set reboot state. Legal values match Read reboot state. Out-of-range values are rejected (not clamped).

Request URL

POST https://openapi-[DataCenter].easy4ip.com/openapi/v2/device.property.set

The administrator does not need an extra permission on a device they bound. A shared device needs the basic configuration permission. A bound sub-user does not. A sub-account needs Config. A write timeout does not mean the operation did not run.

Request parameters

Name	Type	Required	Description
`token`	String	yes	Access token for an administrator, sub-user, or sub-account
`deviceId`	String	yes	Device serial number
`productId`	String	no	Optional. If sent and it does not match the device model → `DV2009`
`properties`	Object	yes	Key is `system.diagnostics.rebootState`, `text` enum (commonly `"0"`/`"1"`/`"2"`; see get page)

For common request fields and signing, see Signing conventions and Common request payload.

Request example

{
 "id": "d5c287b4-5b2f-4f03-baf5-8032c5c354af",
 "system": {
 "ver": "1.0",
 "appId": "lcdxxxxxxxxx",
 "sign": "xjhCQBoJ9hRDsCjyDcHjtDNzRZ3ZJezcawsfWeiaoxU=",
 "time": 1706511734,
 "nonce": "f5a1ae2d-c09c-4d39-a744-83a5c2c653c2"
 },
 "params": {
 "token": "<yourAccessToken>",
 "deviceId": "TESTIPC000012345",
 "properties": {
 "system.diagnostics.rebootState": "1"
 }
 }
}

Response data fields

On success, code is "0" and data is {}.

Response example

{
 "id": "d5c287b4-5b2f-4f03-baf5-8032c5c354af",
 "result": {
 "code": "0",
 "msg": "Operation is successful",
 "data": {}
 }
}

Error codes

Code	When
`0`	Success
`SN1001`	Signature error
`TK1002`	Token invalid or expired
`DV2007`	Wrong or missing `channelId` for scope
`DV2008`	Device and channel properties mixed in one request
`DV2004`	Out-of-range `rebootState` value

See Global return codes. All DV20xx: Capability errors.

Read reboot state · Diagnostics