NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Your experience with Firmware 2.2.1.210 released as of 10/3/18
The other long thread on the new firmware is useless and has become a tech support thread. Please only post your experience after upgrading to the new firmware, good or bad. I'd like to see everyone'...
Update went smoothly. However my two Carrier Infinity Touch thermostats lost connection and I could not get them to connect manually no matter what I tried. Every other device had no problem. I rolled back to 2.1.4.16 firmware, and they connected within minutes. They identify themselves as "Microchip Technology Inc.". Please fix this incompatability. I have a router and two satellites. When I check for networks to connect to it shows all three devices as separate networks. Three networks with the same SSID. I don't see this on any other clients.
The roll back procedure needs some work. When trying it with the cable modem connected the firmware kept going back to the latest version even after manually updating to the old firmware. I don't know if it was really, but the router kept insisting that is was on the latest 2.2.1.210 firmware. Once I disconnected the cable modem I was able to update everything back to 2.1.4.16.
Just want to update my post from 10/6. I had rolled back the firmware so my two Carrier Infinty Touch thermostats would connect since they would not with the new firmware. Well on 10/14 I got an email from the Carrier Server that my thermostats had not reported in for a while. I checked the router and found it had autoupdated to the new firmware. I disconncected the cable modem and tried to roll back the firmware again, but as soon as I connected the modem the router autoupdated the firmware again. TELL IT TO STOP AUTO UPDATING! I would but there is no way to turn it off. Horrible way to configure it. You HAVE to be able to roll back firmware when it breaks your network! I tried a factory reset but that did not help. I tried changing channels on the 2.4G network. I tried changing CTS/RTS threshold, changing MTU size, turning off 20/40 MHz coexistence. I tried turning off Daisy Chaining. All that did was give me a poor connection on the satellite furthest away. I do not have beam forming, MU-MIMO, or fast roaming enabled. I can get the thermostats to connect to the wifi by using the guest with no security, but they cannot connect to the Carrier server because it is not a secure connection. I need them to connect to the server for remote access and weather information, etc. I have never had anything like this happen in all the years I have had wireless. I have a $300 network router and I will have to add an access point to get my two thermostats back. All because I cannot roll back the firmware. What a joke.
Yep, super annoying that they just decided on their own to upgrade our firmware without our knowledge. It's screwed my devices up...and you can't even contact them thru their site without paying for support..der. All you can do is leave them a tweet but of course they wont reply to that either since it would be a free reply.
If you updated to recent FW v.210, try enabling Daisy Chain. Some have mentioned that this seems to be working in reverse order, enabling means disabled actually. Hoping NG support can have a look at this. So try this out as well.
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-and-connection-problems-Skybell/m-p/1649275/highlight/true#M43001Try this:
vice86 wrote:
Yep, super annoying that they just decided on their own to upgrade our firmware without our knowledge. It's screwed my devices up...and you can't even contact them thru their site without paying for support..der. All you can do is leave them a tweet but of course they wont reply to that either since it would be a free reply.
The only way to get help after 90 days is to submit a ticket for an RMA if you are within the 1 year warranty period. Then they will try and help you over the phone. I had someone who had me change some settings, none of which worked of course. After that she was done with me.
Bottom line, there were three things that she cared about.
1.Could I connect to the router through a browser.
2. Was there internet access.
3. Were the satellites on line.
After that you are on your own. If nothing connects to the router, too bad.
About autoupdating the firmware, her line was "you have to auto update to get the best speed. If you roll back it won't be as fast", or something like that. I never had a speed issue, so don't know if that was a company line or her own made up BS.
ratb3rt wrote:
Just want to update my post from 10/6. I had rolled back the firmware so my two Carrier Infinty Touch thermostats would connect since they would not with the new firmware. Well on 10/14 I got an email from the Carrier Server that my thermostats had not reported in for a while. I checked the router and found it had autoupdated to the new firmware. I disconncected the cable modem and tried to roll back the firmware again, but as soon as I connected the modem the router autoupdated the firmware again. TELL IT TO STOP AUTO UPDATING! I would but there is no way to turn it off. Horrible way to configure it. You HAVE to be able to roll back firmware when it breaks your network! I tried a factory reset but that did not help. I tried changing channels on the 2.4G network. I tried changing CTS/RTS threshold, changing MTU size, turning off 20/40 MHz coexistence. I tried turning off Daisy Chaining. All that did was give me a poor connection on the satellite furthest away. I do not have beam forming, MU-MIMO, or fast roaming enabled. I can get the thermostats to connect to the wifi by using the guest with no security, but they cannot connect to the Carrier server because it is not a secure connection. I need them to connect to the server for remote access and weather information, etc. I have never had anything like this happen in all the years I have had wireless. I have a $300 network router and I will have to add an access point to get my two thermostats back. All because I cannot roll back the firmware. What a joke.
ratb3rt Carrier Infinity Touch Thermostats seem to only support 802.11b and only WPA2 security. Please make sure that you have 20/40 MHz coexistence turned ON and that you have security option WPA2-PSK (not WPA-PSK [TKIP] + WPA2-PSK [AES]).
I have the correct wireless security option and 20/40 coexistence is on. Every version of firmware since 11/17 has worked fine, until now.
ratb3rt wrote:
I have the correct wireless security option and 20/40 coexistence is on. Every version of firmware since 11/17 has worked fine, until now.
ratb3rt Can you please -just for testing purposes- test to change your wifi password to a simpler one and test if there will be any change, and then set your original password back. NG might have changed something in security handling in the latest patch?
I see that Carrier Infinity Touch thermostat has similar issues with many other products like Eero, Lynksys, D-link, so it's not only Orbi :)
If you updated to recent FW v.210, try enabling Daisy Chain. Some have mentioned that this seems to be working in reverse order, enabling means disabled actually. Hoping NG support can have a look at this. So try this out as well.
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-and-connection-problems-Skybell/m-p/1649275/highlight/true#M43001Try this:
ratb3rt wrote:
Just want to update my post from 10/6. I had rolled back the firmware so my two Carrier Infinty Touch thermostats would connect since they would not with the new firmware. Well on 10/14 I got an email from the Carrier Server that my thermostats had not reported in for a while. I checked the router and found it had autoupdated to the new firmware. I disconncected the cable modem and tried to roll back the firmware again, but as soon as I connected the modem the router autoupdated the firmware again. TELL IT TO STOP AUTO UPDATING! I would but there is no way to turn it off. Horrible way to configure it. You HAVE to be able to roll back firmware when it breaks your network! I tried a factory reset but that did not help. I tried changing channels on the 2.4G network. I tried changing CTS/RTS threshold, changing MTU size, turning off 20/40 MHz coexistence. I tried turning off Daisy Chaining. All that did was give me a poor connection on the satellite furthest away. I do not have beam forming, MU-MIMO, or fast roaming enabled. I can get the thermostats to connect to the wifi by using the guest with no security, but they cannot connect to the Carrier server because it is not a secure connection. I need them to connect to the server for remote access and weather information, etc. I have never had anything like this happen in all the years I have had wireless. I have a $300 network router and I will have to add an access point to get my two thermostats back. All because I cannot roll back the firmware. What a joke.
ratb3rt wrote:
Just want to update my post from 10/6. I had rolled back the firmware so my two Carrier Infinty Touch thermostats would connect since they would not with the new firmware. Well on 10/14 I got an email from the Carrier Server that my thermostats had not reported in for a while. I checked the router and found it had autoupdated to the new firmware. [...]
Sorry to hear you're having issues, but thanks for the dates. I've been having issues since 10/13, and while I don't know for sure when it auto-updated, the timeframe seems to match nicely here.
I run a continuous ping from my wired network to the satellite, and am experiencing frequent and crazy packet loss since then :(
router is running 2.2.1.210, satellite is running 2.2.1.204_1.0.5
I've just re-enabled daisy-chaining but why would it matter for a simple setup like this? anyways, we shall see.
Does anyone know where the auto-updates are downloaded from? I just want to blackhole that traffic and save myself the pain of my wife and kids coming to me to fix the WiFi that Netgear has once again screwed up.
If you updated to recent FW v.210, try enabling Daisy Chain. Some have mentioned that this seems to be working in reverse order, enabling means disabled actually.
https://community.netgear.com/t5/Orbi/Firmware-2-2-1-210-and-connection-problems-Skybell/m-p/1649275/highlight/true#M43001Try this as well:
UnhappyOrbiUser wrote:
ratb3rt wrote:
Just want to update my post from 10/6. I had rolled back the firmware so my two Carrier Infinty Touch thermostats would connect since they would not with the new firmware. Well on 10/14 I got an email from the Carrier Server that my thermostats had not reported in for a while. I checked the router and found it had autoupdated to the new firmware. [...]
Sorry to hear you're having issues, but thanks for the dates. I've been having issues since 10/13, and while I don't know for sure when it auto-updated, the timeframe seems to match nicely here.
I run a continuous ping from my wired network to the satellite, and am experiencing frequent and crazy packet loss since then :(
router is running 2.2.1.210, satellite is running 2.2.1.204_1.0.5
I've just re-enabled daisy-chaining but why would it matter for a simple setup like this? anyways, we shall see.
Does anyone know where the auto-updates are downloaded from? I just want to blackhole that traffic and save myself the pain of my wife and kids coming to me to fix the WiFi that Netgear has once again screwed up.
i read someone saying add downloads.netgear.com to your blocked list.
Although my FW hasn't updated since downgrading...and if you read any of my replied I realized I must have updated my FW by accident and didn't notice...nothing to do with auto-updating for me.
