Skip to main content

How to Control One Screen from a Tablet

Completion Time: 45 minutes

This guide shows you how to use a touch tablet as a remote control for another screen. A staff member taps a button on the tablet, and the big screen switches to the matching page, for example in a waiting room, a lobby or a meeting room.

The two devices never talk to each other directly. They share an internal datasource:

  1. The tablet writes a value (for example, the name of a page) into the internal datasource.
  2. The big screen watches the same datasource and jumps to the matching page when the value changes.

Because the value is stored on the server, it also survives restarts. ❓ Confirm that a display reloaded mid-session lands on the stored page or on its start page (see Step 4).

What you need​

  • Two devices: the tablet (touch) and the display it controls.
  • Two Contents: one for the tablet, one for the display.
  • One internal datasource that both Contents use.

Step 1: Create the shared internal datasource​

  1. Go to Datasources and create a new Internal datasource, for example Lobby remote.
  2. Give it a simple structure with one field that holds the page to show:
{
  "page": "Welcome"
}
  1. Turn on Allow displays to update data. Without it, the tablet cannot write to the datasource and the change is rejected.
  2. Save.

Learn more: Internal Table Datasources

Step 2: Build the display Content​

  1. Create the Content for the big screen.
  2. Add one page per state you want to control, for example Welcome, Video, Map.
  3. Open the Content-level settings and find the External events section. Click Edit datasource events.
  4. Add an event bound to the page field of your Lobby remote datasource.
  5. For each page, add a rule that checks whether page equals that page's name, with the action Jump to and the matching page as target. ❓ Confirm the exact evaluation label shown in the editor (the code value is "==").

Learn more: Evaluation Types and Jump To Action

Shortcut

Instead of one rule per page, a single Jump to action can take the target page from the data: set Value origin to Property of received value. Use this only if the values you write always match page names exactly. ❓ Test it before recommending it; the per-page rules above are the safer default.

Step 3: Build the tablet Content​

  1. Create the Content for the tablet.
  2. Add one button per page of the display, for example three Image or Shape Widgets labeled Welcome, Video and Map.
  3. Select the first button. On the Other tab, set Click type to Actions and click Edit touch events.
  4. Add the action Overwrite internal datasource (group Internal Datasource Value Management):
    • Datasource: Lobby remote
    • Value origin: static value, with Data set to {"page": "Welcome"}. ❓ Confirm the exact name of the static option in this dialog.
  5. Repeat for the other buttons with Video and Map.

Learn more: Override Internal Datasource Value

tip

Give the tablet visual feedback, for example highlight the button of the active page, so staff can see what the big screen is showing. One way is to bind each button's look to the same page field.

Step 4: Assign and test​

  1. Assign the display Content to the big screen and the tablet Content to the tablet.
  2. Tap a button on the tablet. The display should jump to the matching page within a few seconds. ❓ Measure the typical delay on a real pair of devices.
  3. Open the datasource in Datasources and check that page holds the last value you tapped.

Good to know​

  • Tapping the same button twice does nothing new. The display reacts when the value changes. If staff need a "restart this page" button, write a different value first, or add a counter field.
  • One datasource per room. Two tablets writing to the same datasource control the same screen. Create a separate datasource for each tablet and screen pair.
  • Several screens can follow one tablet. Every display Content that listens to the same datasource follows the same tablet.
  • Display page timing. If the display pages have their own durations, the display may move on by itself. Set the controlled pages to stay until the next command. ❓ Name the exact page setting.

Alternative: send a sensor event to the display​

If the controlling side is not a Wallboard device (for example, a building system or a custom app), it can call a Device Action of the Send sensor event type, targeted at one device, a device group, a device tag or all devices. The display Content then reacts with a Sensor event that jumps to a page.

This requires an API key in the calling system, so do not use it from a Wallboard tablet Content unless you accept that the key is stored in the Content. ❓ Confirm the recommended practice with the product team.

Learn more: Device Actions and Sensor events