Add New Device

No devices found

Identity 01
Select the type of LED controller
Connection 02
IP address or hostname of the device (e.g. http://192.168.1.100)
Which MQTT broker this device publishes to. Manage brokers under Integrations → MQTT Sources. Leave unset to use the first available broker.
Select the COM port of the Adalight device
Select which LED zones to control (leave all unchecked for all zones)
Combined treats all zones as one continuous LED strip. Separate renders each zone independently with the full effect.
Number of LEDs on the strip (must match your Arduino sketch)
Serial communication speed. Higher = more FPS but requires matching Arduino sketch.
RGB (3 channels) or RGBW (4 channels with dedicated white)
Simulated network/serial delay per frame in milliseconds
Art-Net uses UDP port 6454, sACN (E1.31) uses UDP port 5568
First DMX universe (0-32767). Multiple universes are used automatically for >170 LEDs.
First DMX channel within the universe (1-512)
UDP port (0 = protocol default 4048).
DDP destination identifier (1 = display).
Channel byte order on the wire. Most DDP receivers expect RGB.
OPC channel (0 = broadcast to every channel on the server, 1-255 = specific output).
Client-side rate limit between commands in ms. Default 500 ms keeps the bulb under its ~1 cmd/sec cap. Lower = faster updates but risk throttling.
Client-side rate limit between commands in ms. UDP fire-and-forget tolerates fast updates; default 50 ms ≈ 20 Hz.
Client-side rate limit between commands in ms. LIFX recommends ≤20 cmd/sec; default 50 ms matches that ceiling.
Address individual zones (Z/Beam multizone) or pixels (Tile/Canvas matrix) instead of one averaged colour. Auto-detected on connect; older bulbs fall back to single colour.
Client-side rate limit between commands in ms. UDP fire-and-forget tolerates fast updates; default 50 ms ≈ 20 Hz.
Client-side rate limit between commands in ms. Default 100 ms ≈ 10 Hz; HTTP request overhead caps the practical max around 20 Hz.
Stream each panel individually via extControl UDP instead of one averaged colour. Requires a recent controller firmware.
MAC address of the remote ESP32 receiver (e.g. AA:BB:CC:DD:EE:FF)
WiFi channel (1-14). Must match the receiver's channel.
Hue bridge application key from pairing
Entertainment API client key (hex string from pairing)
Entertainment configuration ID from your Hue bridge
Spread the strip across a gradient lightstrip's segments (channels) instead of one averaged colour per light. Auto-detected on connect; plain bulbs are unaffected.
Which BLE protocol your controller speaks. Match the phone app you normally use.
Optional. Newer Govee firmware needs a per-model AES key — leave blank for older firmware.
SPI clock speed. 800000 Hz for WS2812, 2400000 Hz for APA102.
Type of addressable LED strip connected to the GPIO/SPI pin
Which Razer peripheral to control
Select devices to include in this group (order matters for sequence mode)
Sequence concatenates LEDs end-to-end. Independent mirrors the full strip to each device.
Which SteelSeries peripheral to control
Output 03
Default processing template applied to all color strip outputs on this device