Skip to content
English
  • There are no suggestions because the search field is empty.

How To Set Up Screen Sync

How To Set Up A Screen Sync WebSocket Connection

Last updated: October 2025

Please note: Android OS Devices.

The current screen sync method is outlined below. We are actively developing enhancements, and broader compatibility is expected in future updates. An upcoming major improvement for Android devices will eliminate the need for an external Windows device to serve as the local server. Instead, the Android device itself will handle this function.

Caution:

Screen Sync is supported exclusively on the device operating systems and app versions listed below and above.

● Samsung Tizen 7 (v 5.2.31)
● Samsung Tizen 6.5 (v 5.2.31) - Via External Server method
● Android (v 5.2.31) - Via External Server

For Android devices, a local WebSocket server must be set up on an external Windows device to enable sync commands.

Please be aware that if your operating system is not listed above, NowSignage cannot guarantee compatibility.

Firewall & Network Requirements


To ensure the NowSignage application operates as intended, specific firewall and network configurations must be applied. For a detailed overview of the domains and ports that should be whitelisted to support standard player functionality, please consult the comprehensive guide:
https://knowledgebase.nowsignage.com/firewall-installation-requirements
 
Screen Sync Local Server Specific Rules

For the screen sync to work, you must ensure the following local network rules are in
place:

Enable Internal LAN Communication: Communication between devices on the
local area network (LAN) must be permitted.


Player Reachability: To ensure reliable communication, the player device must be accessible on the local network. The NowSignage application operates by listening for synchronisation commands on port 5001. The local server is launched using the device’s IP address and port 5001, enabling seamless interaction with other devices within the same network.

Step 1:

Prepare Screens for Sync

  • Create 2+ screens in the CMS.
  • Create a playlist/playlists and add content with matching duration so they’ll sync
    properly.
  • Schedule these playlists on the screens.
  • Navigate to Apps and ensure Screen Sync is installed on your account profile.
  • Click Screen Sync to access the app, then select “Add Sync Group” and give the group a name.


Step 2:

Initialise the Server (If running Samsung Tizen 7, skip to step four)

  • On a Windows PC, download and install the latest version of Node.js from
    https://nodejs.org/en (you can test if it installed correctly by opening Command
    Prompt and typing the command “node -v”)
  • Download our “screen_sync.js” script from this link
    https://drive.google.com/file/d/1iuzgBUb8sMIF6ENM40YvUuamFPFuy9lG/view
  • Create a folder for your server to run from (e.g. C:\Users\<user>\Folder Name) and
    note down the folder location path.
  • Copy the file screen_sync.js into your folder.
  • Open Command Prompt, and run the following commands:

   cd C:\Users\<user>\ Folder Name [Replace underlined text with your folder location]
   npm init -y
   npm install ws
   node screen_sync.js

Step 3:

Connect the Screens to the Server

  • Leave the server running, and open up another Command Prompt window.
  • Run the command “ipconfig” and look for the IPv4 field for your private IP address
    (e.g. 192.168.1.95)
  • In the CMS open Screen Sync, and copy the IP address from the device being used
    as the server, followed by “:5001” into the “WebSocket Server Address” field. This
    should look like “192.xxx.x.x:5001” where 192.xxx.x.x is the device IP. After this
    click Update at the bottom of the screen to finalise the changes.


Step 4:

Add Screens to Sync Group

  • In your screen sync group, add all screens to be synchronised by using the
    navigation arrows or search function, then clicking on the plus icon next to its name.
  • Click Update, and reboot all screens in the screen group to initiate connection to the
    server. After rebooting, it may take a few minutes for all screens to sync.

Note: For Samsung Tizen 7 Only:
The WebSocket server will be set up locally on the first screen to be added (this screen will function as the master, and broadcast the sync commands to all other peripheral screens).

Troubleshooting:

Q. Delays in content synchronisation:

A. Verify that the date and time settings on your hardware are consistent across all media players and System on Chip (SoC) screens.

Important considerations when using Screen Sync:

 
1. To utilise this feature, NowSignage transmits 'sync' commands over the network. It is essential to maintain a stable and reliable network connection for all screens in the sync group. If any screen disconnects from the network, it may gradually fall out of sync with the other displays. Our application regularly sends 're-sync' commands over the network to help maintain synchronisation, as long as the connection remains intact.
 
2. It is highly recommended to conduct thorough testing on your screens prior to launching any live campaigns. While the NowSignage application includes a screen sync feature, the effectiveness and precision of the synchronisation may vary based on the specific hardware in use.
 
3. To ensure seamless synchronisation, make sure that the playlists assigned to each screen are matched in duration and scheduled appropriately alongside your content. For best results, use shorter playlists, as this helps optimise performance with the Screen Sync feature.
 
4. Once the screens are added to a 'sync group' within the NowSignage platform, a reboot of the screens is necessary. Upon restarting, the NowSignage app will automatically synchronise the displays, ensuring they operate in unison. This reboot process is required only once when new screens are added to a sync group.
 
5. The dimensions of your content play a critical role in achieving accurate screen synchronisation. If your content does not adhere to the recommended specifications, it may disrupt synchronisation across your screens. Please see our guide here for more information: Content Recommendations Guidance