Get discovery status
GET /clip/v2/resource/zigbee_device_discovery
Check whether Zigbee device discovery is running. The response includes the discovery service's UUID, which you need to start or stop discovery.
Example response
json
{
"code": 0,
"data": {
"arr": [
{
"id": "576A6228-CB9E-48D2-B6B6-447C657CF465",
"owner": {
"rid": "EA7297E0-5959-4585-9740-AA5BD41707D1",
"rtype": "device"
},
"status": "stopped",
"type": "zigbee_device_discovery"
}
],
"len": 1,
"obj": {}
},
"msg": "success"
}Responses
| Status code | Meaning |
|---|---|
| 200 | OK |
Response fields
HTTP 200 OK
| Field | Type | Required | Description |
|---|---|---|---|
code | integer | Yes | Status code |
msg | string | Yes | Message |
data | object | Yes | Response payload. |
data.obj | object | Yes | Returned resource. |
data.arr | object[] | No | Returned resources. |
data.arr[].id | string | Yes | Service UUID. Use this UUID to start or stop discovery. |
data.arr[].owner | object | Yes | Owning device |
data.arr[].owner.rid | string | Yes | Device UUID. |
data.arr[].owner.rtype | string | Yes | Device type |
data.arr[].status | string | Yes | Current discovery status. start: discovery in progress; stop: discovery stopped. |
data.arr[].type | string | Yes | Service type |
Check your firmware: The field definition lists
startandstop, while the example returnsstopped. Check the values your gateway returns when handling discovery status.