Troubleshooting

Symptoms

• —The node is on Wi-Fi but does not appear with an IP address in the router's connected device list.

Possible causes

• •The router's DHCP server did not assign an address (DHCP pool exhausted or disabled).
• •The node connected but is still waiting for DHCP.

What to check

1. 1.Wait 15–30 seconds after the node boots, then check the router's device list again.
2. 2.Check the router's connected device list to see if the node appears with an IP.
3. 3.Verify the router has DHCP enabled and IP addresses available in the pool.
4. 4.If the router has DHCP disabled, the node must be configured with a static IP — consult the node firmware documentation.

Symptoms

• —The node is on Wi-Fi and has an IP address, but fixtures do not respond.
• —Moving faders in the Mixer has no effect on the output.

Possible causes

• •The node IP address entered in Settings is incorrect.
• •The phone and node are on different subnets.
• •AP isolation (client isolation) is enabled on the router.
• •A firewall is blocking UDP port 6454.
• •The phone is connected to mobile data instead of Wi-Fi.

What to check

1. 1.Confirm the node IP in Settings matches the node's actual IP (check your router's connected device list).
2. 2.Confirm the phone is connected to Wi-Fi — not mobile data.
3. 3.Verify both devices are on the same subnet (e.g., both in 192.168.1.x).
4. 4.Check the router for AP Isolation, Client Isolation, or Wireless Isolation settings and disable them.
5. 5.Check firewall rules on the router for UDP port 6454.
6. 6.If using a mobile hotspot, AP isolation may be enabled by default — use a dedicated router instead.

Symptoms

• —Moving channel faders has no visible effect on the fixture.
• —Recall scenes have no effect.

Possible causes

• •DMX cable not connected or faulty.
• •Fixture start address mismatch between app and physical fixture.
• •Wrong DMX channel for the parameter (channel mapping error).
• •Art-Net not reaching the node (separate issue — check Art-Net troubleshooting).
• •Fixture is in a mode that has a different channel layout than configured.

What to check

1. 1.Confirm the Art-Net signal is reaching the node first (see above).
2. 2.Check the DMX cable connection between the node's XLR output and the fixture's DMX input.
3. 3.Confirm the start address on the physical fixture matches the start address in DMX Node.
4. 4.Confirm the fixture is in the same operating mode as configured in DMX Node.
5. 5.Move the fader for channel 1 of the fixture to 255 to test. If channel 1 is DIMMER, the fixture should light up.
6. 6.If daisy-chaining multiple fixtures, confirm termination at the last fixture.

Symptoms

• —Moving a fader intended for Fixture A also moves Fixture B.
• —Color channels affect intensity, or intensity channels affect pan.

Possible causes

• •Channel overlap — two fixtures have overlapping address ranges.
• •The channel mapping in the fixture mode does not match the fixture's actual DMX channel order.
• •The fixture is in a different operating mode than configured.

What to check

1. 1.Check for address overlap: verify each fixture's start address and channel count, and ensure no two fixtures share channels.
2. 2.Confirm the fixture mode in DMX Node matches the mode set on the physical fixture.
3. 3.Consult the fixture's DMX manual to verify the channel order for the selected mode.
4. 4.If the channel order is wrong, correct the channel function assignments in DMX Node's fixture configuration.

Symptoms

• —Adjusting the Pan/Tilt joystick in the Color tab has no effect.
• —Pan or Tilt channels in the Mixer do not move the fixture.

Possible causes

• •The fixture mode does not define PAN and/or TILT channels.
• •The PAN/TILT channels are at the wrong position in the channel mapping.
• •The fixture is in a mode without pan/tilt (e.g., a basic color mode).
• •The fixture's movement is locked (some moving heads have a pan/tilt lock switch).

What to check

1. 1.Open the fixture's mode configuration and confirm PAN and TILT channels are defined.
2. 2.Check that the channel positions in the mode match the fixture's actual DMX channel order.
3. 3.Use the Mixer to manually set the PAN channel value and observe whether the head responds.
4. 4.Check the physical fixture for a pan/tilt lock switch or setting.

Symptoms

• —Setting color in the Color tab has no effect on the fixture.
• —Colors appear incorrect — red shows as blue, or adjusting hue changes intensity.

Possible causes

• •The fixture mode does not have RED, GREEN, and BLUE channels defined.
• •The channel functions are assigned in the wrong order for this fixture.
• •The fixture uses a different color order (e.g., GRB instead of RGB).

What to check

1. 1.Confirm the fixture mode defines RED, GREEN, and BLUE channels.
2. 2.Consult the fixture's DMX manual — some fixtures use GRB or other non-standard color orders.
3. 3.Correct the channel function assignments to match the fixture's actual order.
4. 4.Test by setting RED to 255 and all other color channels to 0. The fixture should show a fully saturated red.

Symptoms

• —An FX layer appears to have no effect.
• —The effect applies to the wrong channels.
• —The effect amplitude or speed is not as expected.

Possible causes

• •The targeted fixture does not have the required channel functions for that FX type.
• •The FX layer is disabled.
• •The amplitude parameter is set to 0.
• •The wrong scope or group is targeted.

What to check

1. 1.Confirm the FX layer is enabled.
2. 2.Check the amplitude parameter — a value of 0 produces no visible effect.
3. 3.Verify the targeted fixtures have the required channel functions (e.g., MOVEMENT requires PAN/TILT, COLOR_CYCLE requires RGB).
4. 4.Check the group or scope the FX is targeting — it may be referencing a group with no relevant channels.
5. 5.Increase the speed parameter if the effect appears very slow or invisible.