NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Carrier Thermostat systxccitc01-b can't connect to Orbi AX6000 RBR850 / RBS8540
Hello, I have a carrier thermostat systxccitc01-b and it suddenly won't connect to my Orbi Router. The strange thing is it worked fine for almost a year. I found another thread to change the foll...
Are you using armor? Or any other network security? Armor Not active, no other security system
Just seems a little off its its connecting to orbi's wifi fine but not back to its main server. Yes, it doesn't make sense, but when I connect it to my cell hotspot works fine.
Are you using ipv6? did you try it with it both enabled and disabled? Both are enabled, let me disable IPV6 and try it.
This is sort of a "Twilight Zone" hypothesis....
I once had a device that showed "no internet" despite being connected to WiFi and being restarted several times. I finally opened the Orbi web interface (http://orbilogin.net ) and navigated to Access Control where I found:
- Access Control was enabled. (although I never enable Access Control.) and
- This device was shown as Blocked.
My hypothesis was that at some point I was messing around with the damn Orbi 'app' and must have "slid my fat finger" and "Paused" this one device without meaning to. When I edited the device back to "Allowed" and disabled Access Control, suddenly the device had internet again.
Blocked apparently does not mean, "Cannot connect to WiFi" but instead means, "Can connect (because it presents the correct SSID/password) but is not allowed to access the network."
Or.... not what's happening with this thermostat (sorry to waste your time).
Actually went into the device and this is the first time I have seen it but it has a valid IP address of 192.168.1.5
Server connection Diagnostics
Server Connection Status code: 201
Failure reason code: 19
So off to the web to see what these mean.
If you search, there's quite a few posts on carrier thermostats not connecting. this one for example removed it from his carrier web account and re-added it and it worked.
https://www.reddit.com/r/hvacadvice/comments/x00o6k/carrier_infinity_server_down_for_4_days/
might try something like that. With what you're reporting, its seems something on carrier's end.
