17-Jan-2018, 16:54
@angenet - the Dialog is literally five feet from the Phantom with the optical input. The other one is ~20 feet away, line-of-sight. And mine is the only network physically located in the building. Believe me, there's nothing pathological about my environment. If these devices are meant to operate in an urban setting at all, mine is a relatively unchallenging one.
@streamy - that's an interesting device. But I'd like to keep this thread focused on the topic of how the Phantom / Dialog Wifi functionality works (or doesn't). Specifically, whether Devialet's own people are giving me advice that doesn't apply to my configuration.
@Jamington2004 - Your comment directly addresses the point I'm trying to clarify: "the dialog network relies on a very steady uninterrupted network feeding it" The dedicated networks that the Dialog itself sets up are, in fact, fenced-off networks with no other traffic except for Dialog->Phantom communication. And since I'm using the optical input, not using Spark, and not streaming audio to the Dialog, there is no Devialet-specific traffic on my home network. The two are completely separate. In other words, my assertion is that the Phantoms never connect to any Wifi except the dedicated Dialog-initiated networks.
Adding an Airport, if the above theory is correct, should have no effect, because there will be no Devialet-specific traffic on the Airport's network. It replaces my home network in this equation, it doesn't replace the Dialog-initiated networks. Again, this should be testable by turning off *all* networking gear except the Dialog - the system will continue to function.
Hypothetically, an Airport might make the situation worse, as I'd be using more of the available channels for non-Phantom traffic and "squeezing" the Dialog-initiated network into the remaining space. Anyway, the Airport has arrived from Devialet, so I can test my assertion this weekend.
@streamy - that's an interesting device. But I'd like to keep this thread focused on the topic of how the Phantom / Dialog Wifi functionality works (or doesn't). Specifically, whether Devialet's own people are giving me advice that doesn't apply to my configuration.
@Jamington2004 - Your comment directly addresses the point I'm trying to clarify: "the dialog network relies on a very steady uninterrupted network feeding it" The dedicated networks that the Dialog itself sets up are, in fact, fenced-off networks with no other traffic except for Dialog->Phantom communication. And since I'm using the optical input, not using Spark, and not streaming audio to the Dialog, there is no Devialet-specific traffic on my home network. The two are completely separate. In other words, my assertion is that the Phantoms never connect to any Wifi except the dedicated Dialog-initiated networks.
Adding an Airport, if the above theory is correct, should have no effect, because there will be no Devialet-specific traffic on the Airport's network. It replaces my home network in this equation, it doesn't replace the Dialog-initiated networks. Again, this should be testable by turning off *all* networking gear except the Dialog - the system will continue to function.
Hypothetically, an Airport might make the situation worse, as I'd be using more of the available channels for non-Phantom traffic and "squeezing" the Dialog-initiated network into the remaining space. Anyway, the Airport has arrived from Devialet, so I can test my assertion this weekend.
