image.flicker.config (Set anti-flicker config)
image.flicker.config: Set anti-flicker config
image.flicker.config · Channel scope · Permission Config
What it does
Sets anti-flicker configuration. Set fields must match what get returns (some IPCs only support frequency). Out-of-range values are rejected, not clamped.
Request URL
POST https://openapi-[DataCenter].easy4ip.com/openapi/v2/device.property.set
Minimum permission
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. Omitting channelId on a channel-scope capability returns DV2007. Mixing device and channel in one request returns DV2008. A write timeout does not mean the operation did not run.
Request parameters
| Name | Type | Required | Description |
|---|---|---|---|
token | String | yes | Administrator, sub-user, or sub-account accessToken |
deviceId | String | yes | Device serial number |
productId | String | no | Optional. If sent and it does not match the device model → DV2009 |
channelId | String | yes | Channel ID; "0" is common on IPCs |
properties | Object | yes | Key is image.flicker.config |
| Name | Description | Type | Required | Values |
|---|---|---|---|---|
frequency | Camera frequency. | enum | yes | 0 Outdoor; 1 50 Hz; 2 60 Hz |
shutterSpeed | Shutter speed. | enum | yes | 0 Auto; 1 1/120; 2 1/100; 3 1/60; 4 1/50; 5 1/30; 6 1/25 |
brightness | Brightness. Range 0–100, step 1, unit %. | int | yes | 0–100, step 1, unit % |
Common request fields and signing: Signing 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",
"channelId": "0",
"properties": {
"image.flicker.config": {
"frequency": "0",
"shutterSpeed": "0",
"brightness": 50
}
}
}
}
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
Gateway and device error codes are in Global return codes.