Skip to content

Web Remote Control

DMXRouter edited this page Mar 25, 2026 · 1 revision

Web Remote Control

DMXRouter includes an embedded HTTP + WebSocket server with a built-in web interface. Control playback, manage engines, monitor RDM devices, and view live stats from any phone, tablet, or laptop on the network.

Accessing the Web Interface

The server starts automatically on launch:

  • HTTP: port 9090
  • WebSocket: port 9091

Open http://<dmxrouter-ip>:9090 in any browser. No app install required.

Web Interface Pages

Playback

Full show management with transport controls: Previous, Go Back, Stop, Next, GO, Play/Pause, Take Snapshot, Record, and Autopilot. Shows the cue list with inline editing, live fade progress bars, and playback state per cue.

Engines

Enable/disable toggles, snapshot/failsafe controls, channel patch editing, and a 512-channel DMX output grid with colour-coded intensity. Fullscreen mode available. Global Blackout and Show Mode toggles.

RDM Devices

Device list grouped by gateway with DMX address range, Fixture ID, personality, probe progress, status indicators, and last seen time. DMX address conflicts highlighted in red. Inline SET for address, personality, and label.

Stats & Log

Live packets per second, active universes, error count, per-interface breakdown, and scrollable log with colour-coded severity.

More

  • Profiles — full create, load, delete, import/export
  • Interfaces & VLANs — combined view of all network adapters
  • Discovered Nodes — Art-Net and sACN sources
  • System Info — version, platform, Qt version, uptime

Server Features

  • Bidirectional sync — changes from the desktop push to web via WebSocket in real time, and vice versa
  • Optional PIN authentication — protects HTTP and WebSocket access. The PIN is saved in the browser for convenience
  • CORS enabled — accessible from any web browser or third-party tool
  • PWA support — add to home screen for a native app experience on mobile
  • Self-describing APIGET /api returns a JSON index of all endpoints and WebSocket channels

Configuration

Open Network → Web API... to configure:

  • Enable / disable the server
  • Bind address (restrict to a specific NIC)
  • HTTP port (default 9090)
  • PIN authentication

Changes take effect immediately.

API Integration

The REST API and WebSocket channels can be used from curl, Postman, Bitfocus Companion, or custom automation scripts. Subscribe to specific WebSocket channels (playback, stats, rdm, engines, log, interfaces) to receive real-time updates.

Clone this wiki locally