Roku Premiere suddenly stopped detecting WiFi networks. There was no change on the WiFi Access point. 2.4Ghz is enabled and channel 1 has been in use for long time. I then bought another Roku Premiere model, it worked fine for few days then also suddenly stopped showing WiFi network.
If you have Xfinity/Comcast/Cox as an ISP, you may have to verify if the Mode/Protocol setting is set to b/g/n rather than g/n.
If the above does not pertain to you, or switching the Mode does not solve the issue, post back with the Roku model numbers (Settings..System..About), your router model number, and your ISP. Also mention any errors you are seeing on your screen.
I am using Meraki MR18 access point, This setup was working fine for over an year.
Model number of Roku is 3920X
Radio setting on Meraki is as follows
I also did packet capture in wireless network, It shows Probe request from Roku and Probe responses by the AP. See following;
thanks
There could be a few different things going on with that router/access point. Not sure in your screenshot if there is an option box to "Disable 802.11 ax" right under the 2.4 bitrate settings. If so, go ahead and mark that box so that ax is disabled. (Try disabling first on only 2.4 settings, but may have to do so on both bands.)
Additionally, verify that the default AP policy is allowing both 2.4ghz and 5ghz. (If set to 5ghz only , will override any 2.4ghz settings). Look under "Per AP" settings to enable.
Also, try manually assigning another channel. Try using 6 or 11 if ch1 is no longer working. Can also try using an "open" 2.4ghz network for testing (no password).
One more option is to lower the transmit power on the 2.4ghz. Loud/shouting APs can cause issues by announcing itself too much causing connection/performance issues.
These are a little finicky with 2.4ghz devices. Normal troubleshooting is to enable 2.4ghz only support and disable band steering (temporarily), but that used to require a call to Cisco so I would verify the settings mentioned above, then perhaps adjust the bitrate lower initially, and then a bit higher to eliminate "a" support unless you need it for a device.
On the Roku side, you can try Settings..System..Advanced System Settings..Network Connection Reset..Reset Connection, but since you encountered similar result with the new Premiere, most likely culprit is with an Access Point setting. If worked before, should be able to get to work again. Do the troubleshooting with the new Premiere in order to eliminate the old Premiere as an additional culprit.
Post back with the results from above and any other information you have gathered or can provide. (Screenshots are very helpful, thanks for posting them.)
I have setup a separate temporary AP (Cisco Aeropoint 2700e), at 2.4Ghz only , that is radio 0. This is working fine.
Earlier I configured Meraki AP as 2.4Gz only profile and without any authentication on ssid , it also worked but throughput was not good. I have not tried lowering the transmit power yet. ax setting is not applicable for MR18 APs , so this option is not even available in the AP profiles.
I am not an expert on the RF troubleshooting, but interested to explore it further for technical sake if there is some help / guidance available.
Thanks
Good to hear you found a workaround with another AP and adjusting some settings on the Meraki MR18 is at least establishing connection again.
Since you mentioned that the open network worked for connection purposes although not best performance, perhaps verify that the WPA encryption mode is set properly. Roku cannot see Enterprise, but since you had it working before, assumed you probably knew this.
Here is the link to the Meraki documentation for the Encryption standards. This will also take you to other Meraki documentation and they have a forum Community there as well that will probably be useful. (https://documentation.meraki.com/MR/Encryption_and_Authentication/Setting_a_WPA_Encryption_Mode).
Used to be able to put custom firmware (OpenWRT) on the old Merakis to use in different network environments but development stopped and I guess wasn't worth the effort anymore with newer mesh routers becoming available.
Please feel free to update this post if you find an underlying cause of your issue or need more help. Always appreciate the updates.