Reviewed and corrected September 21, 2026.
A church lighting setup starts with a simple question: who needs to operate it during a service? Build the patch and controls around the actions that person actually needs.
Map the fixtures
List each fixture, selected mode, universe and start address. A 12-channel fixture at address 1 uses channels 1–12; another independently controlled fixture cannot start at 2 on that same stream. Keep the full patch documented.
Independent universes can reuse channel numbers. However, when one USB DMX input is deliberately fanned out to several mapped universes, those outputs share the incoming channel values. Plan non-overlapping assignments across that fanout when different controls are required.
Choose the control path
DMXSmartLink can run its own scenes and visual controls or receive a compatible console's output. Match Art-Net or sACN input deliberately. For physical DMX, use an interface that supports the required direction; confirm the product's included hardware.
Commission smart lights separately
Verify each model through Homebridge, Home Assistant or the configured provider before mapping it to DMX. Test white temperature and brightness as well as RGB. Smart-light groups and individual devices may overlap; verify saving and recall with your actual configuration.
Create the volunteer workflow
- Save a small set of clearly named scenes.
- Test transitions while checking the room and camera view.
- Assign supported scene buttons or explicit MIDI bindings.
- Write startup, normal-lighting and recovery instructions.
- Rehearse with the volunteer who will operate the service.
Budget the lights, controller, interfaces, cabling and installation separately. A HUB purchase does not automatically include a complete venue rig. Schedule software changes and beta testing outside service time.
Check your version and your lights
DMXSmartLink runs on supported macOS, Windows 11, Ubuntu and Raspberry Pi 5 systems, or on a preconfigured HUB. It accepts Art-Net and sACN input and provides Art-Net output; physical DMX requires a supported interface. Smart-light functions depend on the model and integration, including Homebridge or Home Assistant. The bundled Home Assistant companion on Pi/Ubuntu is experimental. Cloud integrations require internet; local paths have their own compatibility requirements.
See current capabilities and beta limitations and compare setups. Use the free 14-day trial, with no credit card required, to test your actual lights. Current prices and included items are on the product pages.
