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.
"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.
- Turn OFF all RBS to help elimiate seeing to many SSID names.
*If I turn off the satellites there won't be any wifi in the thermostat's location. The orbi is replacing a Nighthawk + extender to get wifi to the other end of the house.*
Disable AX mode on the RBR:
*Done previously and currently as set*
Set CTS values to 2347. Under Advanced Tab/Advanced Settings/Wireless Settings. Save settings and apply.
*Done previously but it really killed performance. Is there a reason to use 64 or 2347 specifically? I put it back to 64 because all the TV's were buffering which never happened with the Nighthawk setup. Can I try 128, 256, 512 etc?*
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.
*Actually calling it a thermostat is a misnomer. It's actually a display station for a hard wired remotely located controller which houses all the logic and interfaces for the HVAC system. But the wifi is located in the display the furthest point of the house from the router. The time it takes is totally normal unfortunately, the result of software written by HVAC engineers. Changing the wifi is part of a "new" installation process which takes the entire system through a sequence of self-tests where the wifi connect is the final step. Worked exactly the same after a power outage even with the Nighthawk.*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.
Although certainly frustrating for the person afflicted, this situation presents an entirely different approach to WiFi connection.
Just to confirm, the process is as shown on pages 52 and 54 of this manual:
https://www.shareddocs.com/hvac/docs/1009/Public/03/OMSYSTXBBEC-07.pdf
What is "different" is the concept of showing the SSID of each separate access point as if they were totally different systems.
Taking 10-20 minutes to confirm seems at odds with page 53 where it says the control will inform you if the connection is successful.
Since this controller has already been in use, there is probably no need to proceed on to the registration step on page 54.
Page 52 seems to indicate that each of the WiFi access points will appear with an indication of signal strength. I'm wondering if it might be possible to temporarily locate the nearest satellite to be in the same room as the controller. It ought to have the greatest signal strength.
