Leaderboard

My brother opened ticket #496504 to report this issue. He was told by Line6 that he's not the only one seeing this problem, but there are not very many. I went to see him yesterday to help him out, because I'm not having that problem. His Stadium is connected to the WiFi and logged into his Line6 account. His Laptop is connected to the same WiFi and logged into his Line6 account. However, the Laptop CANNOT see the Stadium, or loses connection to it after a few minutes. So, the Laptop can connect to Line6 through the WiFi, and the Stadium can connect to Line6 through the WiFi, but they cannot Connect to each other. I submitted all the information to CoPilot AI, including info on the router and ISP. Here is CoPilot's analysis of the situation and suggestions for solutions. Issue: Stadium editor cannot connect or loses connectivity after a few minutes even though the Stadium remains fully online. The failure is isolated to LAN discovery, not Wi‑Fi or internet connectivity. Environment: Stadium on Wi‑Fi Windows 11 editor ISP: Fidium Router: Adtran 854‑series gateway (Fidium standard) LAN subnet: 192.168.40.x Stadium maintains valid IP and Line 6 login at all times Observed Behavior: Editor initially cannot find the Stadium or loses connection after a few minutes. Stadium’s Wi‑Fi remains stable (no DHCP loss, no reassociation) Stadium retains internet access and Line6 account authentication Only local discovery fails; reboot sometimes temporarily restores it Technical Analysis: The Stadium editor appears to rely exclusively on multicast‑based service discovery (mDNS/SSDP‑style). Adtran 854 gateways used by Fidium aggressively prune or filter multicast and broadcast traffic after a short period of device uptime. This results in: Unicast traffic: unaffected Internet connectivity: unaffected Multicast discovery: silently dropped This matches known behavior of Adtran 854 IGMP snooping, multicast filtering, and band‑steering logic. Why Other Devices Don’t Exhibit the Issue: Smart TVs and casting apps use cloud‑mediated discovery or Wi‑Fi Direct, not LAN multicast. They bypass the failure mode entirely. Root Cause Summary: Stadium remains reachable at L3, but the editor cannot rediscover it because the router suppresses L2/L3 multicast discovery packets after a few minutes. Proposed Engineering‑Level Solutions: Add a direct‑IP connection path in the editor (bypasses multicast entirely). Add cloud‑assisted discovery (similar to Google Cast). Add a unicast beacon or fallback discovery protocol to avoid reliance on multicast. Any of these would eliminate dependency on consumer‑grade router multicast behavior and resolve issues with ISP‑locked gateways like the Adtran 854.

UPDATE: I opened up the LT and used a multimeter to test the power supply unit's input and output voltages. These are the measured results: INPUT: PIN 1 to PIN 2: 122 VAC OUTPUT: PIN 1 to PIN 3 12.42VDC PIN 1 to PIN 4 12.42VDC PIN 2 to PIN 3 12.42VDC PIN 2 to PIN 4 12.42VDC Measurements of both the input and outputs were done when the unit did NOT boot up properly, AND when the device did boot up properly and was fully functional with no issues. Lastly, while inside, I made sure all terminal and molex connections were clean and making good contacts: - from the incoming power cable, - throught the rocker switch, - input molex connector on PSU, - output molex connector on PSU, - molex connector on circuit board (from PSU) I have read that there "could" be a startup sequencing glitch that may be causing the problem, but cannot confirm nor know where or how to diagnose this possibility> Thanks again for everyone's assistance.

Silverhead and Datacommando: Thanks for the replies. Silverhead: I did open a ticket and hoping the techs will get back with me soon (and with a means to avoid sending it to a service center). Awaiting their response. Datacommand: I considered a "funky" preset may be causing, or part of, the problem. My thought was to test if the unit would bootup properly with only the factory setting. So immediately after the 9/10 reset procedure completed, and when the unit successfully booted up, I believe that it did go through the "reloading presets" process (with only reloading the factory installed presets and not my library of presets). I say "I believe" because I went through quite a few resets, reloads, restores, during my attempts to resolve this issues, it was difficult for me to remember the steps I did in proper order. However, I do know that I sat through several "presets loading" routines during my attempts, with the belief the LT did this procedure (as it does it without my initiation all other times) - but.... I could not testify that I actually remember that it DID perform this action on that specific occasion. Sorry, its been a long evening of internet researching and trying to find anyone that has encountered this exact problem (and while there have been others with various booting issues, I am surprised that I have been unable to find anyone that has encountered this "every other time" scenario). If I am able to eventually resolve it, I am staking my claim for the right of naming this malfunction. With the unit only having the factory installed presets installed, I turned it off and on a few times, and sadly the issue continued (first time no screen on boot, 2nd time bootup and operationally fine, 3rd time no boot, 4th bootup fine. ad infinitum). After restoring the system backup (with my presets and settings), whenever the unit cycled through the boot process successfully, the "reloading presets" process DID run and all my presets and settings appeared to be installed properly. Since it the problem was repeated on the factory reset AND a restored backup, this may not be an absolute conclusion to remove the presets as culprits, it is moving it down on the "highest suspected" list (at least for now). It is difficult for me to understand WHY it is a predictable problem which occurs on every other switching ON and OFF of the unit. Most electronic issues present themselves in an ALL or NOTHING manner, or after some warmup time, or even after a series of functions or operations accumulate glitches that ultimately lead to some type of failure. If I find the cause of the problem, I will post, and again, I thank you, and other potential respondees that can offer any advice or suggestions. Best wishes and ROCK ON!

I can understand your disappointment. Of course, disappointment is a corollary of expectations. Recall that, late in development, Line 6 publicly polled users with the question “Would you prefer a more complete and finished product that will be released later, or a less complete product available sooner?” The clear user preference was sooner, with additional features coming later. Accordingly one should not expect a complete product at this point. You’re absolutely right that promised features like proxy capture remain unfulfilled, as expected. Will other features like preset spillover be added in a future firmware release? I certainly expect so, but I’m not putting any timing on that. Helix Stadium is still very much in its early development. It will, and already has, been much improved. For instance the Showcase feature was not released in v1.1; it arrived in v1.2. Also, v1.2.1 was released very recently, fixing some 50-odd bugs. I think anyone who owns a Stadium device now should consider themselves to be early adopters, complete with the associated bugs and glitches. You don’t have to use it yet. You can wait for several more months until it is more complete and less buggy. Most users responding to the Line 6 outreach wanted it sooner rather than later, and that’s what Line 6 did. Who knows what Stadium will become? Recall that the original Helix product has evolved significantly since its release. It is hardly recognizable now compared to that time. The same will happen with Stadium. As you point out it is currently unfinished. Of course, your feelings are your own and they are legitimate based on a certain set of (reasonable?) expectations.

Okay. I figured it out. WIERD, but I figured it out. I now see that the Stadium XL is connected via USB (USB icon) and the Stadium is connected via Wifi (Network icon). Line 6 has never been perfect at naming consistency!