Troubleshooting
Where: not in the sidebar; look up by symptom
When something goes wrong, find the symptom that looks most like yours, then check the "Possible cause" and "What to do" columns. The link at the end of each table leads to the full description on the matching page.
A device shows as unreachable
The device's "Connectivity" in "Device List" is not "Online".
| What you see | Possible cause | What to do |
|---|---|---|
| "Waiting for Response" | The device has not reported for more than 2 minutes but less than 10 | Wait first. Common while a device restarts or the network drops briefly |
| "Not Reporting" | The device has not reported for more than 10 minutes and was not powered off. The system creates an "Unexpected Offline" notification | Check the device's power and Wi-Fi on site. When 3 or more devices have problems at the same time, a "Site Alert" is created; check the network equipment first |
| "Powered Off" | The device was sent the "Power Off" command | The device has to be switched on at the site; it cannot be woken from the console |
| "Local control · offline" | The device is under local control and has not reported for more than 2 minutes | Check the device's power and network |
| "Unknown" | The device has never reported | Check that the device has finished binding and connection setup; see CMS connection and control |
| "Online" with an orange exclamation mark (Platform Administrator) | There is a connection quality problem | Hover over the icon to see which items, then look at "Incident History" in Connectivity Diagnostics |
When the Wi-Fi signal column shows a grey "- dBm", it is usually just that the device is offline or has stopped reporting; see Wi-Fi signal strength.
See also: Connectivity, Connectivity Diagnostics
An image is blocked from reaching the device
"Create Task", "Clear Current Screen", "Power Off" or a schedule did not send content to the device.
| Message or symptom | Possible cause | What to do |
|---|---|---|
| "Device is under local control. Take over first." | The device is under local control | Click "Takeover" in "Device List"; see Control |
| "already has an active task" | This device's previous task has not finished | Wait for it to finish, or cancel the task in "Task List" |
| "Device already has a pending command" | The device has not answered the previous command | Wait for the device to answer. While a device is offline, it keeps waiting until the device comes online |
| "Device Name" is running firmware too old to …. Please update its firmware first. | A legacy-protocol device does not support this command | Update the device in "Firmware Update" first; see Firmware Update |
| A schedule reached its time and the device did not change image | When a device is under local control, schedules skip it, do not retry, and show no message | "Takeover" first; the next schedule then takes effect. You can also use "Trigger Schedule" |
| Task state is "Waiting for Device Online" | The device is offline | See A device shows as unreachable; the device receives the task automatically once it is online |
| Task state is "Not Reached" | The device was notified more than 5 minutes ago and looks online but has not received it | Wait first; if it is still not received, check the device and its connection |
| Task state is "Superseded" | A schedule started playing new content and the original task was stopped | Normal, not a fault |
| Task state is "Failed" | The device hit an error it could not continue past | Look at "Current Stage" to find the step that failed; see Current stage. The system also creates a notification |
See also: Task List, Schedule Settings, Command restrictions
Takeover is refused
After you click "Takeover", the "Control" column never becomes "CMS".
| What you see | Possible cause | What to do |
|---|---|---|
| "Takeover" is greyed out and shows "Locked on site until HH:mm" | The on-site lock is active | Wait until that time; it recovers automatically |
| "Takeover" is greyed out with no other message | The system's recorded control is already "CMS" | See Control mismatch |
| The "Control Command" result in "Device Information" is "Rejected" | By the reason column: "Takeover locked on device", "Device has joined a video wall", "Device not bound", "App did not respond" | See Rejected |
| The "Control" column shows "Device did not report completion" | More than 2 minutes passed after sending and the device did not report completion | Check that the device is online, then click "Takeover" again |
| "Device already has a pending command" | The previous command has not been answered | Wait for the device to answer, then try again |
Control mismatch
An orange exclamation mark appears in the "Control" column, or you received a "Control Mismatch" notification.
| Possible cause | What to do |
|---|---|
| Control was just changed on site (for example takeover requested on site, or forced to local in engineering mode) | To let the CMS control, click "Takeover"; to let the device control, click "Release Control (Switch to Standalone)" |
| 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 the connection is restored, click "Takeover" |
For the details, see Control mismatch.
An update failed
The device's update state in "Firmware Update" is not "Succeeded".
| State | Meaning | What to do |
|---|---|---|
| "Rejected (Not Run)" | The device is under local control and refused the update; nothing was changed | "Takeover" first, then start the update again |
| "Failed (Rolled Back)" | The check after installation failed, and the device returned to the version before the update | The device can be used as usual. Look at the failed stage in the update detail, and try a different firmware package if needed |
| "Failed (Rollback Failed)" | The check after installation failed, and returning to the old version also failed | Contact the manufacturer |
| "Failed" | The update failed and no rollback result was reported (for example the download failed) | Check that the device is online and the network works, then start the update again |
| It stays at "Waiting for Device" | The device is offline | See A device shows as unreachable |
| No new update appears for this device after starting | This device already has an update that has not finished, so it was skipped | Wait for the current update to finish, or cancel it in the update detail and then start again |
When an update finally fails, the system creates an "OTA Failure" notification. For the full description, see Update states.
Other common situations
| Symptom | Possible cause | What to do |
|---|---|---|
| You chose a "Status" in the device list but new-protocol devices do not show | "Status" works only for legacy-protocol devices | Use the "Connectivity" column; see Device List |
| You cannot see a device's new task under "Task Info" in the device list | "Task Info" lists only tasks from the old mechanism | Look in "Task List" |
| An image cannot be deleted and "Cannot delete: referenced by a playlist" appears | A playlist is using the image | Remove it from the playlist first; see My Gallery |
| The bell shows a number but you do not see that item in the list | The bell and the list may differ by role, and the list shows only unacknowledged notifications | See Notifications |
| After signing in you see only "My Gallery" | The account's role is Content Manager | This is the intended permission design; see Console tour and role permissions |
If the steps above do not solve the problem, contact the manufacturer and give the device name, the time it happened, and the diagnostic data exported from Connectivity Diagnostics.
Related pages: Device List, Task List, Schedule Settings, Firmware Update, Notifications, Control