Connect a screen

Get Screenly running on your device, read the code it shows, enter the code in your dashboard, and know what to check if it will not connect.

Updated

Copy page
View as Markdown View this page as plain text Open in Claude Ask questions about this page Open in ChatGPT Ask questions about this page

Connecting a screen is how you tell Screenly that a display is yours. It takes about a minute once the device is running, and it works the same way whatever the hardware is.

How it works

  1. You get Screenly running on the device. This is the only part that depends on what the device is, and the picker below gives you the steps for yours.
  2. The device shows a short code on the display. We call it a pairing code.
  3. You type that code into your dashboard. The display stops showing the code, and the screen appears in your list, ready to be given something to play.

Before you start

Have the device connected to a display and on the network, and have your dashboard open on a computer or phone, because the code shown on the screen has to be typed into the dashboard. If you have no device yet, a second browser tab on this computer is one. If you do not have a workspace yet, sign up first: it takes a minute and the trial needs no card.

Get Screenly running on your device

Pick what the screen runs on, or that you have nothing yet, and you get only the steps for that. Every route ends with a code on the display.

Step 1 What is going to drive the screen?

The display itself, whatever is plugged into it, or nothing yet. Pick what you already have, or what you are about to buy.

Step 2 Screenly AnywhereAbout 2 minutes

A browser tab is a screen. You can do the whole walkthrough without buying anything.

  1. Open a second browser tab and go to anywhere.screenlyapp.com.
  2. Wait for the pairing code to appear in that tab.

Everything you build carries over to real players when they arrive, because it lives in the cloud rather than on the device.

Digital signage in a web browser ScreenlyOS or Screenly Anywhere
Step 2 ScreenlyOSAbout 5 minutes

It arrives ready. There is nothing to install and no image to write.

  1. Connect the player to the display over HDMI, and to the network by cable or Wi-Fi. On a Sharp display there is nothing to connect, because the player is inside the panel.
  2. Power it on. On Wi-Fi the player asks for the network first, which you can answer with a USB keyboard or with a network.yaml from the Network Config Generator on a USB drive.
  3. Wait for the pairing code to appear on the display.
Boot and pair the device Screenly players
Step 2 ScreenlyOSAbout 20 minutes, most of it writing the card

ScreenlyOS goes on the SD card, and the Pi becomes a player and nothing else.

  1. Install Raspberry Pi Imager on your computer and put the Pi’s microSD card in a card reader.
  2. In Imager, pick your model under Choose Device, then Choose OS > Freemium and Paid-For OS > Digital Signage OS > ScreenlyOS.
  3. Write the image, eject the card safely, and put it back in the Pi.
  4. Connect the Pi to the display over HDMI, power it on, and give first boot a few minutes.

Use a good quality SD card. A partly written or failing card is the most common reason a Pi never starts.

Write the image Supported boards
Step 2 ScreenlyOSStarts with a conversation

ScreenlyOS installs onto Scala players directly, so a fleet that is already mounted keeps its hardware and swaps only the software.

  1. Contact support with the models you have. The ScreenlyOS image for Scala players is not a public download; we confirm which models are supported and send you the image and the steps for them.
  2. Write the image to the player and boot it. Installing ScreenlyOS replaces what is on the device, including any content stored on it and its Scala configuration.
  3. Wait for the pairing code to appear on the display.

Confirm you can rebuild the schedule in Screenly before you begin, because nothing held only on the player survives the install.

Scala players Supported models Get the image
Step 2 Which panel is it?

Samsung and LG are inverses of each other here, so check which line your model belongs to rather than assuming. Anything else with Android built in takes the Android route.

Step 3 Screenly AnywhereAbout 10 minutes

Screenly installs onto the panel from its own settings menu, so no player gets mounted behind it.

  1. On the display, go to Settings > System > Play Via > Custom App.
  2. Go to App Management > Install Custom App, enter https://tizen.srly.io, and press Go.
  3. Wait for the pairing code to appear.

Consumer Samsung televisions do not allow custom app installation. For those, use a stick or a box over HDMI instead.

Install the app Supported models
Step 3 Screenly AnywhereAbout 5 minutes

The television’s own browser runs Screenly, so there is nothing to install.

  1. On the TV, open the Web Browser app.
  2. Go to anywhere.screenlyapp.com.
  3. Wait for the pairing code to appear.

LG support covers consumer sets. webOS Signage on LG business displays is not supported yet.

Open it and pair the screen Keep it running unattended
Step 3 Screenly AnywhereAbout 10 minutes

The app comes from the Play Store on the panel itself, so nothing is plugged in behind it.

  1. On the display, open the Google Play Store and search for Screenly.
  2. Install the app and open it.
  3. Wait for the pairing code to appear.

The app launches itself on boot, but two device settings have to allow it first, and both are off on many devices. The display also runs its own power schedule, independent of Screenly.

Install the app Launch the app automatically on power on
Step 3 Your choiceDepends on what you plug in

Then the panel is only a display, which is the part that lasts, and something else drives it over HDMI.

  1. For a permanent installation, use a Screenly Player, which runs ScreenlyOS and is the setup we can look after end to end.
  2. For hardware you already own, a Fire TV Stick or an Android box runs Screenly Anywhere over HDMI.
  3. Either way, the device shows a pairing code once it is running.
ScreenlyOS or Screenly Anywhere Screenly players
Step 2 Which kind of device?
Step 3 Screenly AnywhereAbout 10 minutes

The app comes from the Amazon Appstore on the device itself.

  1. On the device, open the Amazon Appstore and search for Screenly.
  2. Install the app and open it.
  3. Wait for the pairing code to appear.

Fire TV devices sleep by default, and that is the usual reason a Fire TV screen goes dark.

Install the app Keep it running unattended
Step 3 Screenly AnywhereAbout 10 minutes

The app comes from the Play Store, and the device keeps its own system.

  1. On the device, open the Google Play Store and search for Screenly.
  2. Install the app and open it.
  3. Wait for the pairing code to appear.

The app launches itself on boot, but two device settings have to allow it first, and both are off on many devices.

Install the app Launch the app automatically on power on
Step 2 Screenly AnywhereAbout 10 minutes

Screenly is selected as the CMS provider in Amazon’s console rather than installed by hand.

  1. Connect the stick to the display over HDMI and power it on.
  2. Complete the on-screen setup, choosing language and network.
  3. In the Amazon Signage console, add the stick and select Screenly as the CMS provider.
Pair the stick
Step 2 How do you want to run it?
Step 3 Screenly AnywhereAbout 2 minutes

This is the Windows route as well. There is no separate Windows app, because Windows uses a browser in kiosk mode.

  1. On the device you want to use as a screen, open a browser and go to anywhere.screenlyapp.com.
  2. Wait for the pairing code to appear.

A general-purpose computer behaves like one until you tell it not to. It sleeps, it shows a screensaver, and it puts notifications over your content.

Open it and pair the screen Run it unattended
Step 3 Screenly AnywhereAbout 20 minutes for the first device

Set the policy before enrolling the device, so it restarts straight into Screenly.

  1. In the Google Admin Console, go to Devices > Chrome > Apps and Extensions > Kiosks, and add Screenly Anywhere by URL.
  2. Set it as the auto-launch kiosk app for that policy.
  3. Install ChromeOS Flex on the device, enrolled to the same organizational unit.
  4. The device restarts into Screenly Anywhere and shows a pairing code.
Deploy the kiosk app
Step 3 ScreenlyOSStarts with a conversation

ScreenlyOS runs on other amd64 hardware, including signage players you already own, once we have tested the specific model.

  1. Contact support and tell us the make and model.
  2. We confirm whether that model is supported, and send you the image and the steps for it.
  3. Write the image and boot the device, and it shows a pairing code.

Installing ScreenlyOS replaces what is on the device. Anything held only on that machine is gone once the install starts.

ScreenlyOS or Screenly Anywhere Scala players

Enter the code in your dashboard

This half is the same for every device.

  1. Open Screens.
  2. Click Connect screen. On an empty Screens page the same button sits in the middle.
  3. Type the code shown on the display.
  4. Give the screen a name you would recognize in a list of hundreds, such as the room or the site, rather than “Screen 1”.
  5. Click Connect.

The screen appears in your list within a minute or two and the display stops showing the code. It has nothing to play yet, which is expected: content reaches a screen through a playlist, and Set up your first screen takes you through that.

About the code

A code is eight lowercase characters, good for 30 days, and it leaves out the characters people misread across a room. Pairing codes lists them, and every reason the dashboard refuses a code.

If it will not connect

A rejected code has either expired or had a character misread, and rebooting the device shows a current one.

No code on the display means the device is not online, or it has not finished its first round of updates. Give a new device fifteen minutes before deciding something is wrong.

Nothing on the display at all is a display or a cable problem before it is a Screenly problem. Setup issues covers the usual causes, including captive portals and a device clock wrong enough to break the connection.

Was this page helpful?

Thanks. Glad it helped.

Thanks. That tells us where to look next.

Contact support

Type to search the documentation