Aether DMX | AI-Powered Architectural Lighting Control

# Network Setup AETHER creates its own dedicated WiFi network for reliable, low-latency DMX control. This guide covers how the network works, how to connect your devices, and how to integrate with existing venue infrastructure. *** ## How AETHER Networking Works The AETHER Portal (AETHER Portal) acts as both the control server and a WiFi access point. When you power on the Portal, it broadcasts a network called **AetherDMX** that your Pulse nodes and control devices connect to. All DMX communication stays on this dedicated network, keeping it isolated from internet traffic and venue WiFi congestion. This means your lighting control never competes with streaming, downloads, or other network activity. The system uses three communication protocols on this network: HTTP for the control interface (ports 3000 and 8891), WebSocket for real-time status updates, and UDP for DMX data to Pulse nodes (port 6455). *** ## Default Network Configuration When first set up, AETHER uses these defaults: * **Network Name (SSID):** AetherDMX * **Portal IP Address:** 192.168.50.1 * **Subnet:** 192.168.50.0/24 * **DHCP Range:** 192.168.50.10 – 192.168.50.250 * **Control Interface:** http://192.168.50.1:3000 Pulse nodes automatically receive IP addresses via DHCP when they connect. You don't need to configure them manually. *** ## Connecting Your Control Device To control AETHER from your phone, tablet, or laptop: 1. Open your device's WiFi settings. 2. Connect to the **AetherDMX** network using the password you set during initial setup. 3. Open a web browser and navigate to **http://192.168.50.1:3000** (or **http://aether.local:3000** if mDNS is supported on your device). 4. The AETHER interface will load automatically. Bookmark this page for quick access. If you're using the Portal's built-in touchscreen (kiosk mode), the interface loads automatically on boot — no WiFi connection needed. *** ## Extending WiFi Range with Seance Bridge For larger venues where Pulse nodes are too far from the Portal, the AETHER Seance bridge extends your WiFi coverage. The Seance connects to the Portal's network and rebroadcasts it, creating a secondary access point that Pulse nodes can connect through. To set up a Seance bridge: power it on near the Portal first so it pairs, then move it to the location where you need extended coverage. Pulse nodes will automatically connect through whichever access point (Portal or Seance) has the stronger signal. A typical extended network looks like this: the Portal covers nearby nodes directly, while the Seance bridge covers nodes at greater distances. You can verify which nodes are connected through which path in the Fixtures view under node details. *** ## Connecting to Venue WiFi (Internet Access) AETHER works entirely offline — no internet connection is required for DMX control. However, you may want internet access for cloud backups, AI features (cloud mode), or software updates. To connect the Portal to a venue's existing WiFi network, use the Settings view and navigate to the Network section. Enter the venue WiFi credentials there. The Portal will maintain both networks simultaneously: the AetherDMX access point for DMX control and the venue WiFi connection for internet access. Important: DMX data always travels over the dedicated AetherDMX network, never over venue WiFi. This dual-network setup ensures your lighting control remains reliable regardless of venue network conditions. *** ## Troubleshooting Network Issues **Pulse nodes not appearing:** Make sure the node is powered on and within WiFi range of the Portal (or a Seance bridge). Nodes broadcast a discovery heartbeat every few seconds. Check the Fixtures view — new nodes typically appear within 10–15 seconds of powering on. If a node doesn't appear, try moving it closer to the Portal. **Control device can't connect:** Verify you're connected to the AetherDMX network, not the venue WiFi. Try navigating directly to http://192.168.50.1:3000 rather than using the .local hostname. If the page doesn't load, the Portal may still be booting — wait 45–60 seconds after power-on. **Intermittent DMX dropouts:** This usually indicates WiFi interference. Common sources include microwave ovens, wireless video transmitters, and congested 2.4GHz environments. The Portal uses 2.4GHz for maximum compatibility. If interference is severe, try changing the WiFi channel in Settings, or reposition the Portal away from interference sources. **High latency or sluggish response:** Check that your control device is connected to AetherDMX (not accidentally on venue WiFi). Close any bandwidth-heavy applications on your device. If controlling from a laptop, wired Ethernet to the Portal is the fastest option for demanding shows. *** ## Network Specifications | Parameter | Value | |-----------|-------| | WiFi Band | 2.4 GHz | | Protocol | 802.11n | | Max Nodes | ~20 per Portal (practical limit) | | DMX Refresh Rate | 40 Hz (25ms per frame) | | DMX Transport | UDP unicast, port 6455 | | Control Transport | HTTP + WebSocket, ports 3000/8891 | | Discovery | UDP broadcast, port 9999 | | Typical Latency | < 5ms (direct WiFi) |