Remote commands on Amazon Signage Stick
Amazon Signage Stick supports four remote commands sent from the CastHub web app. These commands are unique to the Signage Stick platform and make it the right choice when screens are in places that are hard to reach in person.
The four commands
Reboot
Restarts the device. Use it when a screen is unresponsive, or after a network change that the device should pick up cleanly. Reboot is the most universally useful of the four; it works regardless of display capabilities.
Display wake and sleep
Turns the connected display on or off. This works over HDMI CEC, so the connected TV must support CEC for the command to take effect. Most TVs from the last several years support CEC under names like Anynet+ (Samsung), Bravia Sync (Sony), or SimpLink (LG); you may need to enable it in the TV settings.
Clear cache
Clears the device’s local cache. Use it when a screen seems to be stuck on an outdated version of a slide, or when storage pressure is causing playback issues.
Screenshot
Captures what is currently on the device’s display and uploads the image to command history. Use it to confirm a screen is showing the right content without having to physically be there. Screenshots require network access, since the image is uploaded back to CastHub.
Send a command
From the Devices page, open the Signage Stick device and choose Remote Commands. Pick the command, set any options (display on/off for display power), and Send. The command moves through Pending, Executing, and Completed states in command history. If a command takes longer than usual, it may be because the device is rate-limited or briefly offline.
Command history
Every command sent to the device is logged with type, status, time issued, and result. Screenshot commands include a thumbnail of the captured image. Command history is also useful for an audit trail when multiple admins manage the same fleet.
Why this matters
Most signage platforms only let you push content. Remote commands let you operate the hardware: reboot a stuck device, turn off displays after hours, clear a stale cache, or check what a screen is actually showing. For multi-location deployments, this is the difference between dispatching someone to a site and resolving the issue from your desk.