network.provisioning.accessoryPaired (Accessory paired)
network.provisioning.accessoryPaired: Accessory paired
network.provisioning.accessoryPaired · device scope · message query permission Alarm
What it does
Reported when an accessory pairs successfully. msgType is network.provisioning.accessoryPaired. Subscribe to capabilityEvent via setMessageCallback for real-time push; pull and push use the same payload shape. Common fields are in Receive device messages and the shared event payload conventions.
Reported fields
Fields inside outputData. Root-level localTime and other platform fields are shared; when both root localTime and outputData.localTime appear, follow the live device payload.
| Name | Description | Type | Required |
|---|---|---|---|
sn | Accessory serial number | text | no |
mac | MAC address | text | no |
localTime | Local time | text | no |
pid | Accessory product ID | text | no |
Example
{
"msgType": "network.provisioning.accessoryPaired",
"deviceId": "TESTGW000012345",
"productId": "56WGTET2",
"outputData": { "sn": "ACC0001", "mac": "AA:BB:CC:DD:EE:FF" },
"time": 1673406989,
"localTime": "20230111T111629",
"alarmId": "116257862023505xxxx"
}
Minimum permission
The administrator does not need an extra permission on a device they bound. A shared device needs the alarm-message permission. A bound sub-user does not. A sub-account needs Alarm. List and search APIs filter out events you are not allowed to see. Provisioning.
