Integrations
The DMX Core 100 is built to talk to the rest of your installation - audio DSPs, IoT devices, pixel controllers, and control apps. The current integrations:
- Open Sound Control (OSC) - two-way control with apps like TouchOSC
- MQTT - IoT and building automation messaging
- MCP Server - AI clients (Cursor, Claude Desktop, and others) control lights over the Model Context Protocol
- Bitfocus Companion - the DMX Core 100 Companion module, built on the Integration API, puts cues and presets on Companion buttons.
- Integration API - versioned HTTP + WebSocket wire contract for control systems such as Bitfocus Companion, Crestron and Node-RED: enumerate the live catalog, execute entities, receive state, and poll device health from
GET /info - Home Assistant - the device and all its scenes, dimmers, and switches appear in Home Assistant automatically
- Control Values - bridge Q-SYS and Symetrix audio controls to faders, menus, and triggers
- Q-SYS & Symetrix - use the DMX Core 100 as a DSP wall controller, and vice versa
- Plugins - install and update on-device integration plugins from the plugin registry (DSP, Home Assistant, Shelly, LIFX, WiZ, Govee, …)
- Building & Publishing Plugins - write your own plugin with the .NET SDK and publish it to the registry
- Advatek Lighting - discover, drive, and monitor Advatek PixLite pixel controllers
- Cloud Tunnel - remote access from anywhere
- Internet Passthrough - temporary internet access via a computer on the same network
- Linked Units - several units as one show: a Main Unit holds the show, Satellite Units control it from their own touchscreens
- HTTP, TCP, and UDP via input triggers
Physical controllers - Stream Deck, MIDI devices, Key Digital keypads, and OSC panels - are covered in Control Surfaces.
Please contact us to let us work with you on extending this list.
Linked Units
Several DMX Core 100 units can work together as one show: a Main Unit holds the cues, presets, custom menus and users and drives the lights, and each Satellite Unit is a touchscreen on the wall that shows and controls the Main Unit’s content. Set a unit’s Main Unit under Control & Integrations > Linked Units, approve it on the Main Unit, restart it, and it is a Satellite Unit. The Linked Units page has the setup steps, what each unit does, what happens while the Main Unit is unreachable, how to unlink, and the error messages.
Most installs use a single unit, so Linked Units is hidden until Hide Linked Units is turned off in System settings. Setting it up needs the Edit Linked Units permission, separate from the permission for keypads, Stream Decks and OSC panels.