NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OrbiOS 2.1.4 availability
A quick update. We're about to release an updated version of OrbiOS 2.1.4 in the next few days through our auto-update mechanism for all Orbi models. When it goes live, you should see a prompt in t...
ARG!!! Now I'm having the same HomeKit issues I was having after the botched 2.1.2.x update. The Home app is expeiencing consistent issues with 'not responding' devices when they are clearly online and connected.
Repeated issues with devices not responding that was only solved after going back to V2.0.1.4. I got to enjoy 2 weeks of blissful stability after you pulled that update. Now you've FORCE AutoUpdated to 2.1.4.10 and I'm having the *exact* same issue.
The inability to control how and when my hardware is updated is a HUGE problem. You have a bug in this firmware that clearly maifests itself after updating OFF 2.0.1.4 and I cannot go back to the last stable firmware version without the damned thing autoupdating nearly immediately after downgrading.
Homekit relies solely on mDNS (aka Bonjour). There are a number of apps available on iOS and macOS, which will tell you which Homekit devices are present on your network. Look for the HAP entries and verify, that the IPs of your Homekit devices are present. If they're not, than something might be blocking the mDNS broadcast on your network.
As far as I can tell, nothing has changed between either 2.1.2.18, 2.1.3.4 and 2.1.4.10 regarding Homekit, but I do have only one Homekit-Bridge on my network.
- Something MUST have changed in the 2.1.4.x! I updated to 2.1.4.14 last week (& I was probably running 2.1.4.10 just prior to that).
I lost ALL mDNS/Bonjour discovery late last week for the first time ever.I know that people never should have to do this, since this is the responsibility of the manufactuer, but have you ever tried running tcpdump or Wireshark on your LAN to see, if the Orbi router - when in router mode and I guess this is the reason, I am not experiencing this, is blocking the mDNS multicasts? I know the setting up some probing can be cumbersome, but it may be worth it.