-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Griffen Fargo edited this page May 14, 2026
·
4 revisions
Common issues and how to fix them.
Start with these commands to identify issues:
./lightsctl.sh doctor # Full health check
./lightsctl.sh validate # Pre-flight validation
./lightsctl.sh diagnose # Detailed diagnostic dumpSymptoms:
-
test-dmxcommand fails - No DMX output from fixtures
- USB device not showing in
lsusb
Solutions:
./lightsctl.sh test-dmx
./lightsctl.sh lsusb./lightsctl.sh ssh
groups $USER # should include dialoutUnplug and replug the ENTTEC. If harden was run, it should appear at /dev/dmx0.
Symptoms:
- Web UI not accessible
- Service status shows failed
- Logs show Qt platform errors
Solutions:
./lightsctl.sh logs
./lightsctl.sh logs-errors./lightsctl.sh qlc-headless
./lightsctl.sh restart./lightsctl.sh doctor
./lightsctl.sh healthSymptoms:
-
lights.localdoesn't resolve - SSH connection fails
- Can't access web UI
Solutions:
./lightsctl.sh scan
./lightsctl.sh checkEnsure WiFi credentials were set correctly during SD card preparation.
Check your router's DHCP leases to find the Pi's IP address, then update PI_HOST in .env.
Symptoms:
- Browser connects but page never loads
- Spinning wheel forever
- Interface unresponsive
Solutions:
./lightsctl.sh ssh
sudo sed -i 's/--operate//' /etc/systemd/system/qlcplus-web.service
sudo systemctl daemon-reload
sudo systemctl restart qlcplus-web./lightsctl.sh restart
./lightsctl.sh healthSymptoms:
- DMX fixtures don't respond
- Scenes don't affect lights
- Everything else works
Solutions:
- Check Universe Output — In QLC+ web UI, go to Inputs/Outputs and ensure universe output is enabled
- Verify ENTTEC Selection — Confirm ENTTEC is selected as the output plugin for the correct universe
- Check DMX Addresses — Verify fixture DMX addresses in QLC+ match their physical DIP switch settings
- Test DMX Output:
./lightsctl.sh test-dmx- Report an issue on GitHub
- Join the community on Discord