NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Bryant Connex thermostat won't connect to Orbi RBS753
The Bryant Connex thermostat is the same as Carrier Infinity and only works at 2.4ghz. Had no issues connecting to the Netgear Nighthawk which I replaced with the Orbi. Suggestion on this forum t...
Turn OFF all RBS to help elimiate seeing to many SSID names.
Disable AX mode on the RBR:
Set CTS values to 2347. Under Advanced Tab/Advanced Settings/Wireless Settings. Save settings and apply.
If the Controller is taking 20 minutes to report back that it can't connect, this would not be a Orbi problem. Contact the Mfr about this. Shouldn't take that long. My NEST report with in seconds if it can't connect for some reason.
Try this with your prior router, set it up near the controller. Turn OFF the RBS temporarily. Use same SSID name and PW as set on the Orbi. Let the controller connect to this router. If it does, turn on the RBS, then just turn off this router and the controller should auto connect to the Orbi SSID name and PW.
Yes you can try different CTS values.
Ya some engineers may not be aware of how there products and software handle smart connect wifi systems and MESH. IoT has been a big problem for single SSID name wifi systems. Some fail to realized that 2.4Ghz and 5Ghz wifi networks are on the SAME SIDE network.
FURRYe38
"Try this with your prior router, set it up near the controller. Turn OFF the RBS temporarily. Use same SSID name and PW as set on the Orbi. Let the controller connect to this router. If it does, turn on the RBS, then just turn off this router and the controller should auto connect to the Orbi SSID name and PW. "
Before seeing this suggestion, I brought one of the satellites within a couple of feet of the thermostat so it would have the strongest signal and ideally the first that would be seen. It worked.
Part of the problem with the list of available SSIDs was that they all showed up with 5 bars.
Funny thing is that I thought that after getting the thermostat recognized and connected with the IP reserved on the RBR and set as the static IP on the thermostat, I tried switching the thermostat to DHCP but it wouldn't connect.
So, currently these are the settings that are working:
1. AX disabled for the 2.4ghz band
2. RTS/CTS set to 2347
3. Thermostat IP address reserved on the RBR
4. Static IP on the thermostat set to the reserved IP
As time permits, I plan to see if AX can be enabled. After that, I'll experiment with lower RTS/CTS thresholds.
"Try this with your prior router, set it up near the controller. Turn OFF the RBS temporarily. Use same SSID name and PW as set on the Orbi. Let the controller connect to this router. If it does, turn on the RBS, then just turn off this router and the controller should auto connect to the Orbi SSID name and PW. "
Before seeing this suggestion, I brought one of the satellites within a couple of feet of the thermostat so it would have the strongest signal and ideally the first that would be seen. It worked.
Part of the problem with the list of available SSIDs was that they all showed up with 5 bars.
Funny thing is that I thought that after getting the thermostat recognized and connected with the IP reserved on the RBR and set as the static IP on the thermostat, I tried switching the thermostat to DHCP but it wouldn't connect.
So, currently these are the settings that are working:
1. AX disabled for the 2.4ghz band
2. RTS/CTS set to 2347
3. Thermostat IP address reserved on the RBR
4. Static IP on the thermostat set to the reserved IP
As time permits, I plan to see if AX can be enabled. After that, I'll experiment with lower RTS/CTS thresholds.
titaniumrx8 wrote:
FURRYe38
"Try this with your prior router, set it up near the controller. Turn OFF the RBS temporarily. Use same SSID name and PW as set on the Orbi. Let the controller connect to this router. If it does, turn on the RBS, then just turn off this router and the controller should auto connect to the Orbi SSID name and PW. "
Before seeing this suggestion, I brought one of the satellites within a couple of feet of the thermostat so it would have the strongest signal and ideally the first that would be seen. It worked. Seems like the stronger single is preferred by the controller.
Part of the problem with the list of available SSIDs was that they all showed up with 5 bars.
Funny thing is that I thought that after getting the thermostat recognized and connected with the IP reserved on the RBR and set as the static IP on the thermostat, I tried switching the thermostat to DHCP but it wouldn't connect.
So, currently these are the settings that are working:
1. AX disabled for the 2.4ghz band
2. RTS/CTS set to 2347
3. Thermostat IP address reserved on the RBR
4. Static IP on the thermostat set to the reserved IP< Set the Thermostat to Auto, It's not recommended or normal practice to set a static IP address to same IP address reservation ON the router.
As time permits, I plan to see if AX can be enabled. After that, I'll experiment with lower RTS/CTS thresholds.Sounds good.