Devices

Universal Light Driver — WLED, LIFX, Hue, Nanoleaf, Art-Net, sACN, ESP32, generic HTTP.

BRIDGE OFFLINE

Your PulseBox

No PulseBox paired yet. On the box screen you'll see a 6-character code — enter it here to link it to your account.

Device Registry

0 of 0 devices

No devices yetOpen PulseBox locally to scan — cameras, microphones, ESP32 and more appear here automatically. On the cloud this stays empty (it can't see your LAN).

Advanced diagnostics · raw bridge · telemetry · power tools

Commissioning views

Real Devices 0 displays · 0 controllers

Your PulseBox, projector and TVs are real — this cloud view just can't see them directly until the on-site connector links your network to the cloud. Manage them now with Remote access; they list here automatically once the connector is linked (no IP typing).

PULSEBRIDGE

PulseBox apponline

PulseBridgenot reachable from this browser

Expected bridge URLws://127.0.0.1:8787

This browserLocal — this computer

Bridge not running on this computer

You're on localhost, so the bridge should run on this same machine. Start it once:

cd tools/pulse-bridge && npm install && node index.mjs

Then it auto-connects. (On a PulseBox the bridge is a systemd service — you don't run this.)

Diagnostics

Attempted URLws://127.0.0.1:8787

Last errornone

Reconnectingyes — auto-retry

Last connected—

Last event— · —

Bridge URL (manual override)

The bridge is optional — Pulse runs fully in the browser without it. It adds native I/O the browser can't do (Link, native MIDI/HID, OSC, DMX, OpenCV, NDI, Home Assistant). LAN/localhost only. Capabilities below are honest: “unavailable” until that native module ships.

link unavailable

midi unavailable

osc unavailable

hid unavailable

dmx unavailable

opencv unavailable

ndi unavailable

homeAssistant unavailable

audioRouting unavailable

cameras unavailable

Clock source — use bridge clock → Pulse transport

Devices (0) none reported

Bridge version —

Pulse Health

0 nodes

No telemetry yet. Nodes appear here when a bridge publishes pulse.health on the back channel.

To find your Wi-Fi lights, start Pulse Bridge.

Pulse works with LIFX / WLED / Hue smart bulbs, projectors and DMX. This website can't scan your Wi-Fi directly — that's a browser safety rule. Pulse Bridge is a small helper that runs on your laptop or PulseBox and scans your lights safely on the local network.

Start it once, then press Find lights:

node tools/pulse-bridge

Advanced — bridge runs on another device

Only if Pulse Bridge runs on a different machine on your network — enter its LAN address. Otherwise you don't need this.

Bridge URL

Discover on your network

Click Scan to find lights on this network (LIFX broadcast + mDNS).

Start the bridge to scan for devices.

Add a LIFX bulb by IP — when discovery doesn't find it

Find the bulb's IP in the LIFX app (bulb → settings → IP). This talks to it directly (unicast), bypassing broadcast — works across subnets if the bridge can reach the IP.

Supported today: LIFX (LAN broadcast + add-by-IP) and WLED (mDNS + HTTP). Art-Net nodes that advertise mDNS show up here too. Hue / Nanoleaf pairing, Tuya / BLE / Bluetooth, and DMX-over-USB are not wired — DMX USB needs WebSerial or a native bridge.

Your lights · 0

No lights registered yet. Scan above to discover devices on your network, or click Add manually.

Map Pulse → Lights

No mappings yet. Dispatch is throttled to 20 Hz once you save one.