Device and connectivity troubleshooting
This guide covers common Arthoff device problems involving lighting, audio, cameras, effect machines, network connectivity, triggers, synchronization conflicts, and local browser storage.
This guide covers common problems involving Arthoff devices such as lighting, audio, cameras, and effect machines. It focuses on connection checks, trigger configuration, synchronization conflicts, and browser-side diagnostics.
Device does not connect (🔴 connection error)
Causes and solutions
| Symptom | Possible cause | Step-by-step solution |
|---|---|---|
| 🔴 Connection error | Device is powered off or unreachable on the network. | Verify power, confirm the device and Arthoff computer are on the same IPv4 network, test the address with ping, and inspect firewall/network rules. For Art-Net/sACN, verify the required UDP/multicast behavior. |
| 🟡 Connecting | The device is listening but has not responded yet. | Verify protocol and port, enable the device’s remote/API/OSC input mode, and allow a short time for Arthoff to detect the connection. |
| 🟢 Connected, but DMX values do not reach the console | Incorrect channel/universe mapping or network filtering. | Verify device IP and universe in the cue, confirm that the lighting console receives the expected Art-Net universe, and check VPN or UDP filtering. |
Diagnostic panel
In Devices, open the device and select the Test panel (🔧).
Send values manually, for example DMX values from 0 to 255.
If manual control works but cues do not, inspect the cue trigger configuration.
If manual controls are unavailable or do not work, investigate the device connection itself.
Cue runs but the device does not react
| Symptom | Possible cause | Solution |
|---|---|---|
| Lighting cue runs but output does not change | Manual trigger was not fired or the automatic trigger is misconfigured. | Trigger the cue manually, inspect the cue’s Trigger settings, and verify incoming MIDI/OSC signals when used. |
| Audio cue produces no sound | Missing source, volume at zero, or unavailable output device. | Verify the selected device, cue volume, source file/URL, and use the audio device test panel. |
| Camera cue does not change the shot | Camera control protocol is unsupported or OSC/MIDI control is configured incorrectly. | Check the camera’s supported control protocol, verify address/port/channel data, and test Pan/Tilt/Zoom manually. |
Synchronization conflicts
Symptoms
- The same cue or completion state was changed independently by multiple users.
- Offline edits conflict with newer server-side changes after reconnecting.
Resolution
Identify the conflict
Arthoff presents actions such as Use server version, Use local version, or Open in editor.
Choose the correct state
- Use the server version when the shared team state should win.
- Use the local version when your offline/local edit is the intended final state.
- Use Open in editor when the conflict needs to be merged manually.
Reduce future conflicts
Coordinate simultaneous editing, use section/script locking when available in the documented workflow, communicate in team chat, and create history checkpoints before large changes.
Developer console errors (F12 → Console)
The source documentation mentions IndexedDB/Dexie-related errors such as DOMException or QuotaExceededError.
IndexedDB/cache problems
Clear site data when appropriate and reload Arthoff with a hard refresh.
Storage quota exceeded
Very large local projects with many cues and media files can exceed browser storage. Split large projects into smaller scripts and archive older versions through JSON export when necessary.
Technical support
Open the developer console and copy the most recent relevant errors.
When reporting the issue, include the Arthoff version, device model and firmware, network setup, reproduction steps, screenshots, and relevant DMX/MIDI/OSC state.
Most connectivity issues in the source guide come down to three checks: the device address, the protocol/port, and the cue trigger.
Pre-show checklist
- Power on all devices and connect them to the intended network.
- Confirm each device shows a connected state in Arthoff.
- Verify manual versus automatic triggers.
- Run a short device test.
- Save the project state or create a checkpoint before the event.
Tutorial: Triggering devices from cues
Learn how to use manual, automatic, timed, MIDI, OSC, HTTP, cue-based, and device-state triggers to synchronize stage devices in Arthoff.
Offline mode (Offline First)
Arthoff is designed for environments where internet connectivity can be unstable or completely unavailable. Its Offline First architecture keeps most core functions available without a network connection and synchronizes changes after reconnecting.