Control
Where: sidebar → Device Management → Device List → the "Control" column and the "⋯" menu
This page explains "control" from the console's screens: what happens after you click "Takeover" or "Release Control (Switch to Standalone)" in "Device List", what you see when a request is refused, and what to do when control is out of step. For how control works, and for the screens on the device itself, see CMS connection and control in the Product Guide.
Control decides who is in charge right now, and there are only two owners: "CMS" means the E-Paper Content Management System decides what the panel shows, and "Local" means the standalone app on the device decides. Only Platform Administrators and System Operators can send takeover and release commands, and the two roles can do the same things.
Takeover
In "Device List", click "Takeover" in the device's "⋯" menu (use "Bulk Takeover" for several devices) and confirm "Confirm Takeover"; the system then sends the command to the device.
- The "Control" column shows "Switching".
- The device receives and handles the command, then reports the result. On success "Control" becomes "CMS"; if it is refused, it stays "Local".
- If more than 2 minutes pass after sending and the device still has not reported completion, the "Control" column shows "Device did not report completion".
The result is recorded under "Control Command" in Device Information: the times "Sent", "Received by device" and "Completed", and the result "Succeeded", "Failed" or "Rejected".
Rejected
A device can refuse a takeover. When it does, it stays under local control and nothing changes. The result in "Control Command" shows "Rejected" with a reason:
| Reason | Meaning and what to do |
|---|---|
| "Takeover locked on device" | The device was forced back to local control on site and is still in the lock period. See On-site lock; take over again after the lock ends |
| "Device has joined a video wall" | A device in a cluster video wall cannot be taken over by the CMS; remove it from the video wall on site first |
| "Device not bound" | The device has not been bound to the E-Paper Content Management System yet; finish binding on site first |
| "App did not respond" | The standalone app on the device did not respond. Try again later; if it keeps happening, contact the manufacturer |
For the checks made before a command is sent (the previous command has not been answered, a legacy-protocol device, and so on), see Command restrictions.
Release
Click "Release Control (Switch to Standalone)" (use "Bulk Release Control (Switch to Standalone)" for several devices) and confirm "Confirm Standalone Mode"; the device returns to local control.
- The "Control" column again shows "Switching" first, and becomes "Local" when finished.
- After a release, images sent by tasks and schedules are not shown, and the device keeps reporting its status. To let the E-Paper Content Management System control it again, click "Takeover".
- The system does not send "Takeover" or "Release Control (Switch to Standalone)" directly to a legacy-protocol device; it asks you to update the firmware first; see Firmware Update.
What CMS actions do under local control
When a device is under "Local" control:
| Action | Result |
|---|---|
| Create a task, "Clear Current Screen", "Power Off" | Cannot be sent; "Device is under local control. Take over first." appears |
| A schedule triggers | This device is skipped, not retried, and no notification is created |
| Firmware update | The device refuses it and the state is "Rejected (Not Run)"; see Firmware Update |
If either the system's record or the device's report says "Local", the device is treated as under local control, which is the more cautious handling.
Changes made on site
Control can also change on site, not only from the console. The device leaves a record in the "Incident History" of connectivity diagnostics (event "Recovery Action"). The records are:
| Record | Meaning |
|---|---|
| "Takeover requested on site" | Someone on site asked the CMS to take over from the device |
| "Taken over automatically on first image" | The device took over automatically when it received an image from the CMS |
| "Forced to local in engineering mode" | Local control was forced on site in engineering mode, which starts the on-site lock |
| "Released to local after a long time without CMS contact" | The device had not been in contact with the E-Paper Content Management System for too long and returned to local control by itself |
After a change on site, the "Control" column updates to match what the device reports.
On-site lock
After local control is forced on site in engineering mode, the device refuses takeover for a period of time; this period is called the on-site lock. During the lock:
- The "Control" column shows a lock icon; hover over it to see "Locked on site until HH:mm".
- "Takeover" in the "⋯" menu is greyed out and cannot be clicked, and shows "Locked on site until HH:mm".
- When the time is up, it recovers automatically; you do not need to do anything.
Control mismatch
An orange exclamation mark in the "Control" column means the control owner the system has recorded differs from what the device last reported (hover over it to see what each side says). A common cause is that control was just changed on site.
When a device reports a control owner that differs from the system's record twice in a row, the system creates a "Control Mismatch" notification, which says "CMS record: …, device reports: …. Take over again or release control."
To bring both sides back in line:
| Who you want in control | What to do |
|---|---|
| CMS | First click "Release Control (Switch to Standalone)", then "Takeover" after it succeeds ("Takeover" is greyed out when the record says "CMS"; see the note below) |
| Local | Click "Release Control (Switch to Standalone)" |
After the command succeeds, the exclamation mark disappears. The "Control Mismatch" notification does not go away by itself; once the two sides match, go to "Notifications" and click "Acknowledge".
"Takeover" is greyed out when the record says "CMS"
When the system's recorded control is already "CMS", "Takeover" cannot be clicked, even if the device actually reports "Local". In that case click "Release Control (Switch to Standalone)" instead, and click "Takeover" after it succeeds. This is the current behavior.
Viewing it on the device
On site, staff can see the same information on the "CMS Connection" page of the device's management interface. The console and the device each show their own screen; see CMS connection and control for details.
Related pages: Device List, Notifications, Troubleshooting, Firmware Update, CMS connection and control