NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Bill____
Apr 06, 2018Apprentice
Orbi RBS/RBR 50 Version 2.1.3.4 and Apple homekit iDevices and Philips Hue problems.
I have updated to firmware version 2.1.3.4 and have noticed some homekit instability. I have several iDevices Switches which have become intermittent and no other changes than the router firmware. I was re-initializing one in an effort to get it to join, and on the second unsuccessful try, it said it is "not compatible with my router". The one I reset along with other ones work one moment and don't work the next. They used to be very very stable. Also getting problems with Philips Hue devices.
121 Replies
This auto update to 2.1.4.10 has made my HomeKit unresponsive and keeps dropping devices and reconnecting like a min later I have my satellite off right now to see if that would help it did not and it’s also up to date they need to let us have control when we want to update I’m trying to finger out If they have any date to fix this problem. HomeKit showing the disconnect I have koogeek leviton ecobee eve appletv 4K x2 both hubs on and iPad hubs on as well did all the basics restarts on Apple devices and on modem and on router please fix this ASAP
- Bill____Apprentice
The orbi firmware issue is getting famous, and for the wrong reasons. I guess this is what happens when things don’t get fixed for weeks on end.
Thanks for the Reddit link, I see it reverts back to this one.
Still no resolution in sight and it has highlighted another criticial issue with the Orbi - the inability to stop automatic updates on a reliable basis.
This is getting ridiculous ! No answers from Netgear at all !
Can I suggest that everyone start posting on Twitter (maybe it will get more attention), and also on the Wirecutter review for mesh network, that still has Orbi as the recommended model. Maybe if we get Wirecutter attention, we will get Netgear attention.
Same issue 2.1.4.10 kills Homekit as soon as I downgrade to 2.1.2.18 it works fine. I can't believe they don't have a way to disable auto firmware upgrades. I really wish I didn't invest so much into Netgear! I certainly will not be recommending to anyone! Come on Netgear! get your act together!
- stumantexasAspirant
Spent days trying to figure out homekit issues - saw post on firmware and tried it. Downgraded from the latest 2.1.4.10 to 2.0.1.4 and have not had a device show no response or any other issue since.
- stumantexasAspirant
DarrenM - yes, still having the issues. I got auto upgraded and devices started to not respond immediately. Downgraded and
all good again. Please let me know how to get in touch with support.
Thanks for your help.
- BartleyR7Aspirant
No new information here, just wanted to also mention I'm experiencing the same issues with firmware v2.1.4.10. I've downgraded to 2.1.2.18 multiple times (the NVRAM method and others mention don't seem to keep my Orbi setup from updated the firmware, which is incredibly frustrating in its own right). Like others have mentioned, v.2.1.2.18 works great for me with HomeKit.
It does appear to be limited to HomeKit for me. I have Hue lights, 2 Ecobee 4 thermostats, and multiple iDevice switches. Regardless of the Orbi firmware versions, their individual apps (Philips, Ecobee, and iDevices) work fine. However, HomeKit becomes unreliable with any firmware version > v2.1.2.18.
It's frustrating for sure, but ultimately it's more disappointing that Netgear isn't taking a more proactive approach to this issue. It really does start to errode trust in the product, not to mention the company.
- FURRYe38Guru - Experienced User
A fix for HomeKit on 50 series models:
https://community.netgear.com/t5/Orbi/OrbiOS-2-1-4-Homekit/m-p/1565698#M31140
- kmapleTutor
This didn't seem to work for me. Had to go back to 2.1.2.18. Of course my Orbi's will auto update in a few days and I will have to go through the process again.
- cheshbrApprenticeIt worked perfectly for me. Here’s what I did. I started with a stable v2.1.2.18 in place for several days. I have 4 Lifx smart globes which all worked on 2.1.2.18 with Alexa, Google Home and HomeKit. I was happy at this point. I backed up, downloaded the new firmware, installed it manually, satellite first then router. At this point I disconnected my wired backhaul from the satellite. Then I checked, and found a couple of magenta ovals, so I rebooted my ADSL modem and power cycled the Orbi devices and eventually, after an hour of fiddling and phaffing around I got it working. HomeKit and Lifx behaved themselves, so I reconnected my wired backhaul to the satellite. More magenta ovals and phaffing about power cycling, but eventually it worked. It took about three hours, which about half of that in HomeKit and Lifx and working with the Netgear Genie device map to identify weak signal strength, usually occurring because the device latched onto the router instead of the satellite. I visited each device and either power cycled it or temporarily disabled WiFi. This worked on iPads and iPhones. Now everything is good. I can’t fault the Orbis or HomeKit/Lifx any more. For me it’s a success, but very fiddly. The use of the Genie is an important trobleshooting tool. Don’t give up. You have to work at it, then you will be rewarded. Good luck
- jhalkiasAspirant
Same problems here, and it has been driving me CRAZY. None of my automations are working (which is a pain with outdoor lighting) and my iDevices randomly connect and lose connection. I contacted iDevices and they told me of the problem with the Orbi firmware and that Netgear is working on it. I see NOWHERE here that I can contact Netgear to ask them when, other than to pay $49.99 for a tech support call.
VERY disappointed and very upset about this.
I also have an airport extreme router and the cable modem that I have turned off the wireless. However, to get the iDevices to access either one of them, I have to reset each individual switch to the other network. I am thinking of renaming the Orbi Network to a new name, and naming the Apple network the old name to see if that is an easier work around. This has been a HUGE cluster.
- DavidJZUGuide
There's two ways get your homekit devices behaving immediately:
- downgrade to firmware 2.1.2.18 which is known to be stable with Homekit.
- Use netgear's published temp fix found in the URL below
https://community.netgear.com/t5/Orbi/OrbiOS-2-1-4-Homekit/m-p/1565698#M31140
- Bill____Apprentice
Downgrading is not likely to be a good fix since the device will automatically upgrade (even if you set it in the firmware not to).
The temporary fix is the solution I use...
- DavidJZUGuide
Yes, I agree.
However, I used the nvram method to stop auto-upgrading and it worked for me.
I know others have reported that it doesn't work.
Nevertheless, the official netgear temp fix does seem to be simplest choice right now.
cheers
Dave