@SS76 wrote:
Is it possible that the setup box is still looking for the old SSID and if so, how do I stop that from happening?
I get the feeling that the set-top box's WiFi behaviour has changed over time. The really frustrating thing is that nothing about the Ignite TV equipment's internal workings are documented anywhere that is available to us.
Comcast designed the modem and set-top boxes to work together seamlessly. To add a new set-top box, all that you need to do is take it out of the box and plug it in. The XB6 helps the set-top box discover and connect to your internal WiFi network automatically.
In my current setup, I connected all of my set-top boxes to the XB6 gateway, as described above, the way that they were meant to be installed. I had previously also configured the same WiFi credentials (as what was configured into the XB6) into my own Wi-Fi Access Points. To switch over to my network equipment, I simply put the XB6 into bridge mode, powered up my equipment, rebooted the set-top boxes, and everything continued to "just work".
@SS76 Keep in mind that the XB6 is a different animal than the Hitron CODA gateways. Comcast designed the XB6 to be the Hub for a "Connected Home". It can provide connectivity for IoT devices and it also has a bunch of services that continue running even when Bridge Mode is enabled. Even with WiFi disabled or in Bridge Mode, the XB6 will continue to have multiple hidden WiFi networks active, on both the 2.4 and 5 GHz bands; they support other services that are still running on the XB6.
The Xi6 set-top boxes were also designed to connect to the XB6. Don't expect them to behave like an Apple TV or Roku streaming box.
@ColdGranite I was merely trying to explain why those hidden SSIDs are there.
One of those hidden SSIDs is also associated with an internal service that helps the Ignite set-top box discover and connect to the WiFi SSID that is configured in the XB6. I'm wondering if the set-top box is connecting to that same service when it boots up or connects to WiFi, and if it runs into problems when the only available WiFi networks are different from the one that is configured in the XB6.
@ColdGranite wrote:
How would that explain that a tv box is quite willing and able to connect to MY OWN router with my router's SSID... in fact it actually connects to an plain vanilla EXTENDER for that router? That particular box is so far away from the XB6 that I doubt it would see it (without pods), even if wifi were enabled on the XB6.
The Ignite set-top box connects to my own WiFi network just fine as well. I'm just postulating why @SS76 might be experiencing difficulties and why you need to jump through hoops from time to time to get the STB to connect to your equipment.
@macdted wrote:
Thank you, worked for me to connect my STB to my Deco Mesh. It really should be an option in the setup screen on the Set Top Box.
Is there a list of the options in diagnostic mode after you do the 3 second exit and down down?
As far as I know, there isn't any easier way to connect to the 3rd-party Wi-Fi network. Another option is to connect the set-top box to a Wi-Fi network using WPS, using the button on the bottom of the STB.
Keep in mind that in a typical Rogers-supported configuration, the Ignite TV set-top box automagically connects to Wi-Fi on the Ignite gateway, without any action required by the end-user. Rogers (and Comcast) didn't intend for their users to connect Ignite TV to third-party equipment, and making the Wi-Fi network connection option available in settings could result in users accidentally disconnecting their set-top box from Wi-Fi.
@ColdGranite wrote:
Is there really any difference whether the WIFI is being provide by the Gateway, or by another router?? I don't see it.
It all depends on the home, the options that you have available for placing your Ignite gateway, and your technical requirements. I currently run Ignite TV over my own network gear and use business-grade Wi-Fi access points. Other family members use the XB6 gateway and nothing else. Previously, I ran Ignite TV on a 3rd-party consumer-grade Wi-Fi mesh.
Wi-Fi on Rogers-supplied and Rogers-supported equipment should work perfectly fine for most people, assuming that it has been installed correctly. I also recommend the "all-Rogers" solution because it is easy to manage and the Ignite components were designed to work together seamlessly.
@SpeedyC That button sequence still works... but as you and others have reported, apparently not always, and I confirmed that the hard way last week after making some Wi-Fi changes in my home.
Remember that these set-top boxes were meant to connect to (and even auto-discover) Wi-Fi on the Ignite gateway.
If the magic button sequence does not work, you can try to get the Ignite boxes to connect to an external Wi-Fi network through WPS but depending on what state the STBs are in, that may not work either.
To get my STBs connected again, I ended up disabling Bridge Mode on my gateway, programming the WiFi credentials that I wanted to use into my XB6, connecting my set-top boxes via Wi-Fi to the my XB6 by pressing the WPS button on the bottom of the STB, disabling Wi-Fi on the XB6, and then programming that same SSID/passphrase into my external Wi-Fi gear. The boxes then reconnected without issues and remained connected.
One other thing: I have also found that you definitely do need to use the same SSID/passphrase on your external Wi-Fi gear as what you had configured on your Ignite gateway. I did not, and found that my set-top boxes kept losing Wi-Fi connectivity... and when that happened, I found that I could not get them to reconnect to the external Wi-Fi network using the magic button sequence or with WPS.
-
25539 views
-
5 Likes
-
-
