Setup manual & FAQ

Self-determined (link-local) addresses are fine. If there's no DHCP — a direct cable or an isolated switch — machines self-assign on the 169.254.0.0/16 subnet (the same approach Dante and other pro-AV gear use every day). As long as every machine sits on that one subnet, KueSync runs on it perfectly.

"The agent's web page loads, but Companion still won't connect"

This is the most common confusion, and it has a precise cause: the agent's web pages (the Setup page, /health, /status) are read-only and open to anyone on the network, so they load fine. But Companion controls the agent over a WebSocket, which is a different, persistent connection. If the page loads but Companion shows the machine disconnected, check, in order:

1. Both machines are on the same subnet. Guest / hotel Wi-Fi often has "client isolation" that blocks device-to-device traffic — use a dedicated router or switch instead.
2. The IP in Companion matches the machine's current address (DHCP can change it).

Tip: from the Companion machine, open http://<other-ip>:37100/health in a browser. If that loads, the network is fine and the issue is the address you typed.

Leader / Follower (machine-to-machine advancing)

A Follower (the default) just receives commands — no setup, no license needed. A Leader drives the whole fleet from its own presenter remote. To set it up, open the Leader machine's Setup page (menu-bar/tray → Setup, or http://<leader-ip>:37100/leader):

1. Switch that machine to Leader.
2. Add each Follower by its real network IP (or scan the subnet to find them). This step is required — a Leader only drives the Followers you list.
3. Use Learn to bind your remote's forward / back buttons.

For redundancy, set up two or more Leaders with different priorities: the highest-priority healthy machine drives, the others stand by and take over instantly on failure, and a recovered primary only reclaims control once it's provably stable again.

Driving from Companion + a Leader at the same time: point Companion at the Leader and it drives the whole fleet — the Leader fans your commands out to its Followers. A machine that's being led ignores direct commands so Companion and the Leader never fight. (From Companion's point of view, the primary machine is the Leader.) Type a slide number + Enter on the Leader during a show and the whole fleet jumps there, just like it does locally in Keynote / PowerPoint.

Companion buttons — what each one does

Add the KueSync connection, then in the button library you'll find these preset groups. Every navigation button has a Machines field: blank / "all" drives the whole fleet, or comma-separate machine numbers and/or IPs (e.g. 1,3) to target some.

Transport

• Next / Prev — advance or reverse one step, playing in-slide builds and animations, synced across the fleet by timing (the default).
• Next (static) / Prev (static) — jump by absolute slide number, self-correcting; skips in-slide builds. Best for video walls and build-free decks.
• First / Last — go to the first or last slide. Start / Stop — begin or end the slideshow on every machine. +5 / −5 — jump several slides.
• Go to slide — jump to a specific slide number.

Sync

• Sync Now — one tap snaps every machine to the Leader's current slide. Use it after a Follower drifts, reconnects, or gets advanced on its own. It jumps to the slide and skips that slide's builds — a great "panic re-align" button.
• Resync — same idea, but you can pass a specific slide number.

Deck control, cue & loop

• Go deck — bring the show up full-screen at slide 1 on every machine and hold (no auto-advance). End show — stop any roll/cue and exit the slideshow everywhere.
• Run cue — auto-advance with per-slide timing, optional loop and synced builds. Cue: pause / resume / cancel — control a running cue.

Video (PowerPoint)

• Media: play/pause, jump to end, stop — control the current slide's video on every machine.
• Video — time remaining / TRT / elapsed / source — readout buttons showing the clip's total running time and countdown (measured on Windows/PowerPoint, or planned from a cue sheet on Mac).

Status & monitor (display buttons)

• Current slide, Machines healthy, Fleet in sync, Per-machine slides, Current Leader, Build position, License — live indicators; several double as a tap-to-resync.
• Presenter notes, Presentation name, Slide name — mirror the primary machine's deck so you can read ahead at front-of-house.

Cue light (PerfectCue-style)

The Cue Light preset group turns Stream Deck keys into a DSAN-style cue light: it flashes green on a forward move and red on a backward move, mirroring the presenter's clicker. Drop the Cue lamp on one key, or tile it across several to build a big lamp; use the Go lamp and Back lamp on different keys to build a two-zone panel. The lamps are output-only — they light from the show, there's nothing to press. Tune the flash hold and pick flash-vs-latch in the connection settings.

Phone remote & clicker links

Every agent is a tiny web server, so a presenter can drive the show from their phone — no app, no Companion. On the Leader's Setup page, open Clicker Links, create a link, and share its URL. They open it and get a full-screen advancer with big GO / BACK, a green/red cue lamp, the slide number, and a LIVE / STANDBY banner. Commands ride the same path as the physical clicker, so they inherit all the sync, gating, and failover.

• Master links always drive and can take control at any time — that's the stage manager / operator.
• Presenter links drive only while you make them Live, so you hand the cue from speaker to speaker. One-session links are for a single show; reusable links persist for a recurring speaker. Revoke any link with one tap.

Choosing the network KueSync traffic rides

On a job site you often have a dedicated control LAN and house Wi-Fi. Agents always listen and discover on every interface — but you can pin which network the show runs on. Two places to set it:

• In Companion — the Preferred network for traffic field. Enter the first three octets of your control subnet (e.g. 172.26.32). The module asks each agent for all its addresses and connects over the one on that subnet, so you can type any reachable IP per machine and still keep the show on your control network.
• On each agent — the menu-bar/tray address list ranks networks best-first and lets you check one as the priority/broadcast network.

The only requirement is that the machines share a subnet. A self-determined 169.254.x.x network is a perfectly good choice for an isolated wired rig — pick it as your preferred network and KueSync rides it.

How tight is the sync?

Every screen flips together to within a couple of milliseconds — on any network, including isolated direct-wired rigs. KueSync continuously measures each machine and corrects every cue per machine, so there's no tuning, no drift, and nothing to set up. If you ever want to nudge the feel, the Setup page and the Companion connection both have a single Sync tightening (ms) control: a touch higher is a touch more consistent, a touch lower is a touch snappier. The default is the sweet spot.

One thing that isn't us: a heavy slide can paint a hair slower on one machine than another — that's the app's render time, not the cue.

Locking down control

By default the agents accept control from anyone who can reach them — perfect for an isolated show network, but on a shared or house network set a control password. Pick one value (e.g. from openssl rand -hex 16), set KUESYNC_TOKEN=… in each agent's config.env, and enter the same password in the Companion connection's Control password field. From then on only your control surfaces can drive the show, and the agent's Setup page shows a notice whenever control is open on a routable network. Phone clicker links are separate — each link carries its own revocable credential, so a presenter's link never exposes fleet control.

Licensing

Every install starts with a 30-day free trial — full features, no card. During the beta, the trial is your free access. After that, you license the one control machine (the Companion machine, or the primary Leader). Enter the key once there; the presentation machines it drives connect for free. A pure Follower needs no license — it shows "Not required in Follower mode." Existing keys keep working, and a key is verified offline so it works at the venue with no internet.

Presenter remote / keyboard

On a Leader machine, KueSync watches the configured presenter-remote keys (arrows, Space, Page Up/Down) only while a slideshow is actually running. When you're not presenting, your keyboard is completely untouched — type normally. If you ever need to, switching the machine back to Follower (or quitting KueSync) releases the keys immediately.

Health-check commands

On any machine, confirm its agent is alive:

curl -s http://localhost:37100/health

From the Companion machine, confirm it can reach another machine (replace the IP):

curl -s --max-time 4 http://192.168.1.50:37100/health

If the first works but the second doesn't, it's a network/IP issue, not KueSync — re-check that both machines are on the same subnet and that the address is the machine's current one.

Download KueSync   or email support@krometis.com.