Quick start

Go from a bare screen to a live, config-spanned video wall in one sitting. The YBeeM cloud is fully hosted, so there is nothing to install or maintain — you sign in, mint a key, flash your units, and lay them out.

Before you begin

You will need a YBeeM account, at least one Raspberry Pi 4/5 or x86 PC to run as a unit, and a screen to plug it into. Everything else lives in the cloud: your dashboard mints keys, holds your floorplans and wall layouts, and serves updates to your fleet.

A quick vocabulary check before you start — see concepts for the full picture:

• A swarm is one licensed site: a set of units that share a single cloud key and cooperate, usually to render one combined image.
• A cloud key is the swarm's licence and the credential each unit uses to reach the cloud.
• A video wall is a rows×cols layout over a swarm, where every unit owns one tile.

From zero to a live wall

1. Sign in to your dashboard

   Open /app/ and sign in. This is where you manage every site, key, floorplan, and wall from one place.

2. Mint a cloud key for your first site

   Create a swarm and mint its cloud key. The key is shown to you exactly once and never appears in a URL, so copy it somewhere safe before you leave the page. You can revoke it at any time to cut that site off instantly.

3. Flash a unit and power it on

   Write the YBeeM image to your Raspberry Pi 4/5 or x86 PC, connect it to a display and the network, and power it on. It boots straight into the kiosk platform.

4. Get the unit onto your swarm

   Two ways, both covered below: paste the cloud key into the unit during setup, or let a factory-fresh unit announce itself and adopt it from your dashboard's Pending units list.

5. Lay it out on a floorplan and a wall

   Under Floorplans, drop the unit where it physically stands. Under Video walls, drag it into a grid cell. Save, and the swarm converges on one combined image.

6. Wire it to the building (optional)

   If you run a BMS or SCADA, expose the unit over BACnet/IP and Modbus TCP so the building can read its health and drive the screen.

Two ways to enrol a unit

Both paths land the unit in your fleet with the same credentials; pick whichever fits how you provision hardware.

Once enrolled, the unit joins over the swarm's private link, reports a live online status, and shows up in your fleet table. online

Place it and build the wall

In Floorplans, create a site and upload a floorplan SVG, then drag units from the tray onto the plan. Positions are stored proportionally, so pins hold at any display size; drag a pin off the plan to unplace it. See floorplans.

In Video walls, open the swarm, set the grid size, and drag units into cells. Saving records each unit's tile and pushes the layout to the whole swarm, so every screen — including the master — renders its own piece of the one image. See video walls.

Wire it to the building

Every unit is also a first-class BMS/SCADA endpoint, concurrently over BACnet/IP and Modbus TCP. Health is exposed as read-only points and control lives in writable ones — reboot, blank, brightness, kiosk mode, target host or URL. A write from the building system is applied exactly like a change made in the unit's own settings: it takes effect and the display reconnects to the new target. Full point maps are in integrations.

What next

You are live. From here:

• Your subscription tracks your active units, so you pay for exactly the screens you run.
• Updates flow from the cloud automatically to units on an active subscription. On device they are A/B and power-cut-safe, so a bad update rolls back on its own.
• Read concepts for how swarms, keys, and walls fit together, then dig into video walls, floorplans, and integrations.