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.
titaniumrx8 wrote: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.
I reserved the address of ".32" for the thermostat, rebooted everything and tried again after setting the ".32" address in the thermostat's settings. Haven't been able to connect since.
With the nighthawk, I used a lot of reserved addresses for stationary, dumb devices and never had any issues. If I can't resolve the thermostat issues I'll return the Orbi and go back to the Nighthawk.
It appears that you have learned that Orbi provides the same IP reservation feature that Nighthawk does. Is that the meaning of "reserved"? (Or did you mean that the Orbi has a "gap" where 32 would be?)
My thermostat (different brand) had me select the WiFi SSID from a list of available WiFi and then enter the password on the thermostat. (very cumbersome selecting those CAPITAL letters and numbers). Is that how the Bryant works?
It is a little strange to mix IP reservation with static IP (setting the IP address on the device.
"My thermostat (different brand) had me select the WiFi SSID from a list of available WiFi and then enter the password on the thermostat. (very cumbersome selecting those CAPITAL letters and numbers). Is that how the Bryant works?
It is a little strange to mix IP reservation with static IP (setting the IP address on the device."
I use the address reservation table in the advanced tab of the router. In the case of the Bryant thermostat, I have also set the static IP to the same IP as the reservation table. The Connex shouldn't need a fixed IP but it seems to make it's connection more stable, at least it did with the nighthawk.
So far It looks like the AX has to be turned off for 2.4ghz AND RTS/CTS has to be expanded to get the Connex connected.
titaniumrx8 wrote:So far It looks like the AX has to be turned off for 2.4ghz AND RTS/CTS has to be expanded to get the Connex connected.
This might be a typo? The thermostat supports only 2.4ghz.
I am still confused about "where things go wrong". Does it not have you select an SSID from a list and enter the password on the thermostat?
"The thermostat supports only 2.4ghz.
I am still confused about "where things go wrong". Does it not have you select an SSID from a list and enter the password on the thermostat?"
2.4ghz only
The thermostat brings up 6 SSIDs, three for primary and three for guest. There's no way of delineating which device the SSID is associated with. And the list can come up in a different sequence after every scan. There are typically a dozen SSID visible. So I pick one of the orbi's ssids, enter the correct password and wait.
The thermostat is very slow so it takes about 15-20 minutes just to see if the connection failed. Never had an issue with it on the Tri-Band Nighthawk so I probably need to review every setting that's different on the Orbi. There's no other option for a Wifi thermostat which can control this variable speed, multi-zone heat pump system. If I can't get the thermostat to work, the Orbi gets returned.
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.