This page explains what you can do to a kiosk from the Merlin Cloud dashboard, who can do it, how actions are delivered, and what to expect.
Who can control devices
Admins and Managers can perform device actions.
Viewers can see analytics and status but cannot control devices.
How remote actions work
Actions are sent instantly when a device is online.
If a device is offline, Merlin Cloud retries when it reconnects.
Devices send a heartbeat every 30 seconds so status and delivery timing stay accurate.
The experience reloads every 15 minutes when online, which helps pull new code and content.
Tip: Keep devices online daily for fast action delivery.
Core actions
Action | What it does | Typical use | Expected result |
Ping device | Sends a network ping and status check | Quick health verification | Dashboard confirms reachability and updates Last seen |
Beep device | Plays a sound | Locate hardware on site | Kiosk emits a short audible beep |
Send screen message | Shows a message overlay on the kiosk | Inform store staff or customers | Message displays until dismissed or timeout |
Lock screen | Freezes UI input | Prevent use during maintenance | Screen locked, content visible, no touches accepted |
Unlock screen | Restores input after a lock | Reopen kiosk to customers | Normal interaction resumes |
Enter lockdown | Forces Merlin Cloud Lockdown shell | Prevent access to system UI | Device restricted to the kiosk app |
Exit lockdown | Releases Lockdown | Technician access | Kiosk resumes standard Android UI |
Adjust volume | Sets media and system volume | Noise policy compliance | New volume applied immediately |
Adjust brightness | Sets screen brightness | Power saving or glare reduction | Brightness updates immediately |
Rotate screen | Sets orientation | Portrait or landscape fixtures | Orientation changes without reboot |
Set screen timeout | Controls display sleep | Prevent unintended sleep | Timeout applied at OS level |
How to exit Lockdown on device
If you need to exit physically on site: tap the screen 7 times in the bottom right corner.
Content and syncing controls
Immediate content refresh: Allowed by the 15 minute reload and session refresh logic when the device is online.
Pause new content: Do not include the device in your next campaign release.
Clear local cache: Contact support. We can clear cache and reseed content remotely.
Power and restart behaviour
Devices auto restart on power restore.
Keep kiosks plugged in for consistent uptime. All devices we sell support 8 hours or more on battery for power cuts.
Action delivery rules and timing
Online: Actions execute as soon as they are received.
Offline: Actions wait and execute after the next successful connection.
Visibility: You can see Last seen and heartbeat history on the device page to judge timing.
Security and audit
All actions are sent over HTTPS with TLS 1.2 or 1.3.
Role-based access controls apply.
Changes are recorded in system logs for audit.
Troubleshooting remote actions
Check the device status and Last seen. If offline, wait for reconnection.
Confirm network access on site. Ensure Wi-Fi has internet and no captive portal blocks traffic.
If an action does not apply, allow the 15 minute reload to complete or resend the action.
For persistent issues, contact support. We can review logs, clear cache, or reseed content.