Skip to main content

Embed the Fusion Signage PWA in a BrightSign Presentation

Updated over 2 weeks ago


Use case

Combine Fusion Signage with BrightSign’s powerful native features. By embedding the Fusion Signage Progressive Web App (PWA) inside a BrightSign presentation, you can keep using Fusion Signage for content playback while leveraging BrightSign-only capabilities like UDP, GPIO, and touch inputs directly from the device.

Demo video

Before you start (one‑time setup)

  1. Install BrightAuthor:connected for your BrightSign model and sign in to your BrightSign account.

  2. Provision the device for Local Network publishing. This allows you to publish completed presentations over your network.

  3. Enable storage limits so the PWA caches (identity persists):

    • Go to Admin → Preferences → Storage.

    • Turn on Limit storage.

    • Increase each storage limit to 9999 MB.

    • Click Apply Changes.

Why this matters – enabling storage limits ensures the Fusion Signage PWA is cached locally so the identity code isn’t lost between reboots or updates.

Part 1: Create the HTML presentation that loads the Fusion Signage PWA

  1. In BrightAuthor:connected, go to Presentation → New.

  2. In the left panel, select HTML (not playlist).

  3. Give your presentation a name.

  4. In HTML Site, enter the Fusion Signage player URL:

    • https://player.fusionsignage.com.au

    • Important – use https:// (secure). http:// will not target correctly.

  5. Target player – choose the exact BrightSign model you’re using.

  6. Set any specific resolution and orientation options as required.

  7. Click Start.

At this point, your HTML asset (the Fusion Signage PWA) is created and will act as your home state.

Part 2: Configure interactivity in advanced view

  1. Open the Content tab. You should see the HTML asset you just created.

  2. Switch from Simple to Advanced (dropdown at the top).

  3. Confirm the HTML asset is your Home state (the default state the device will return to). This is your Fusion Signage player.

  4. Import any additional content you want to trigger to (e.g. videos, images, additional HTML or widgets).

  5. Add your triggers and link states:

    • Choose the trigger type you need: UDP, GPIO, Touch, or a Timeout.

    • Drag the trigger from the Home state to the target state you want to transition to.

    • With the connector selected, configure the trigger under Event Properties on the right.

  6. Set return conditions so the device comes back to the Fusion Signage PWA after the triggered content finishes. Examples:

    • Video → set Return trigger to Media End.

    • Timeout → return to Home after X seconds.

    • Touch/UDP/GPIO → define the specific signal that returns to Home.

Handy hint – keep your Home state minimal (the single HTML asset pointing to the Fusion Signage PWA). Add as many other states as needed for your interactive/triggered content.

Part 3: Publish and test

  1. Publish your presentation to the device over the Local Network.

  2. On the device, verify that:

    • The Fusion Signage PWA loads correctly.

    • Your configured triggers (UDP, GPIO, Touch, Timeout) transition to the correct states.

    • The return conditions bring you back to the Home (Fusion Signage PWA) state as expected.

Troubleshooting

  • PWA won’t load

    • Confirm the URL is exactly https://player.fusionsignage.com.au.

    • Ensure the device has network access and correct DNS.

    • Re-check Admin → Preferences → Storage: Limit storage must be enabled and set to 9999 MB per limit, then Apply Changes.

  • Identity code lost after reboot

    • Storage limits likely not enabled or too low. Re-enable and set to 9999 MB and publish again.

  • Triggers not firing

    • For UDP: verify IP/port and the message payload matches your Event Properties.

    • For GPIO: confirm wiring and the selected pin and edge (high/low) are correct.

    • For Touch: ensure the display/controller is supported by the BrightSign model and touch events are mapped to the correct state.

  • Doesn’t return to the PWA

    • Make sure you set a return trigger/condition (e.g. Media End for videos, a Timeout, or a specific signal).

Did this answer your question?