system.upgrade.started: Upgrade started

system.upgrade.started · device scope · message query permission Alarm

What it does

Reported when upgrade starts. Standard msgType is system.upgrade.started (legacy upgrading/5100, e_upgradeStart/305900 empty payload merged). Subscribe to capabilityEvent; see Event catalog, Event catalog, Overview and common payload, and Receive device messages and setMessageCallback.

Reported fields

outputData has no business fields (often {}). Platform fields: Overview and common payload.

Example

{
 "msgType": "system.upgrade.started",
 "deviceId": "TESTIPC000012345",
 "productId": "56WGTET2",
 "outputData": {},
 "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. When a sub-account queries messages for this event, each message is checked against the capability row share/sub codes (system.upgrade is usually Config; triggering upgrade invoke also needs Upgrade). list / search filters out events without permission. Upgrade.