I went to perform the manual install, but my system was already running on 2.1.4. And my HomeKit is not working. Do I need to perform the manual install anyway?
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
I have updated my RBR50 without problem. When I try to update the RBS50's it fails with a message stating the file is not correct. How do I get the Satellites updated?
After much teeth nashing, pulling of hair, swearing, etc. I finally got my system back up and running on 2.1.4.14 on a wired backhaul. I finally had to factory restore everything, reloaded firmwares, say a prayer, and finally it is up and running.
My Homekit stuff seams to be ok for now, but I am still getting "unreachable" message on most of my Hue stuff. Hopefully you have had better luck.
After many wasted hours spent fighting this system this week, I can't take any more, so hopefully it will stay stable and they won't push another auto update that breaks it all again. I don't think my mental health can take it.
Updated to v2.1.4.14 on both RBR50 and RBS50 (satellite first). The update went smoothly. It will take me a few days to determine whether it has cured my issues with Philips Hue Routines becoming unreliable; here's hoping!
Where are you getting FW V2.1.4.14 from? Only recently Netgear releseased FW V2.1.4.10-0430-dbg for which I was a beta tester. Previously I was having major issues when upgrading to FW 2.1.3.4 and FW 2.1.4.10, which buggered up my Homekit and Lifx devices, so I downgraded to FW V2.1.2.18, but once I installed V2.1.4.10-0430-dbg about a week ago after working with Netgear, my system has been perfect for at least a week.
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
Where are you getting FW V2.1.4.14 from? Only recently Netgear releseased FW V2.1.4.10-0430-dbg for which I was a beta tester. Previously I was having major issues when upgrading to FW 2.1.3.4 and FW 2.1.4.10, which buggered up my Homekit and Lifx devices, so I downgraded to FW V2.1.2.18, but once I installed V2.1.4.10-0430-dbg about a week ago after working with Netgear, my system has been perfect for at least a week.
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
I have been having this SERIOUS problem with many of my homekit products displaying "no response". I updated to the newest version 2.1.4.14 which was suppose to fix this. It DID NOT fix it for me. Still...most of my homekit devices are still showing "no response". Why is this still happening? Is there some special thing I need to do...to get this new version to work with homekit? The devices work fine in their respective apps but in homekit, they show "no response". PLEASE HELP!
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
Using my Mac osx 10.13.4 downloaded the link for the RBR50 which is a dmg file. The downloaded file says 31.MB and your server says 29 MB. After download, my Mac can't open it, it says invalid image. Did it like 10 times and same result.
Delete the old downloads and try again. I have same OS as you and no issue. File is .img when I just checked. Yes, Finder will say 31.1MB, difference in disk access standards.
Sorry, just realized what you're doing. You shouldn't opening the file in your Mac, you should usually Manual Update option in Orbi itself. I posted the steps earlier in this thread.
Just download the img file(s) to your Mac, login to your Orbi, Advanced, Administration, Firmware Update, Manual. Do the sat first, when it’s rebooting do the router.
I've brought this up in previous threads but my only issue I am having is that my rainmachine (and maybe other devices?) seem to lose connection randomly and then don't pick the connection back up from the orbi when this happens. I never had this issue with my Asus N66U router so I'm pretty sure this is an Orbi specific bug much like this Homekit issue. Who knows maybe the homekit fix would fix this issue? When this issue happens my log is full of DHCP requests from my RainMachine MAC address. The other device that was doing this in this log was a Roomba which is also 2.4GHz only. So that's why I say maybe this issue affects more than one device. I would appreciate if someone from Netgear would reach out to help make sure this issue gets fixed in a future firmware release.
I have tried manually assigning a 2.4GHz channel, tried a clean factory restart, etc. I have ethernet backhaul and its worked fine for me without issue.
[DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 02:07:08 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:59:02 [DHCP IP: 192.168.1.10] to MAC address e0:b9:4d:40:97:04, Friday, May 11, 2018 00:59:02 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:32:51 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:32:47 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:27:18 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:27:14 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:24:54 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:24:49 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:24:45 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:21:36 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:18:24 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:18:20 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:28 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:24 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:17 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:13 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:08 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:14:06 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:03:46 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:01:33 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Friday, May 11, 2018 00:01:29 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:52:18 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:50:35 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:46:46 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:30:13 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:27:57 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:27:53 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 23:00:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 22:59:59 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 22:55:15 [DHCP IP: 192.168.1.21] to MAC address 78:24:af:45:30:da, Thursday, May 10, 2018 22:55:12 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 22:46:37 [DoS Attack: TCP/UDP Chargen] from source: 184.105.139.93, port 29977, Thursday, May 10, 2018 22:46:34 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:33:01 [DoS Attack: RST Scan] from source: 66.85.80.245, port 1414, Thursday, May 10, 2018 21:32:58 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:26:33 [DHCP IP: 192.168.1.22] to MAC address 00:05:cd:28:48:4e, Thursday, May 10, 2018 21:26:31 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:21:47 [DoS Attack: RST Scan] from source: 74.91.117.227, port 443, Thursday, May 10, 2018 21:21:46 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:01:17 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:01:14 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 21:01:12 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:43:03 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:43:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:42:42 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:42:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:42:24 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:42:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:42:02 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:42:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:41:43 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:41:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:41:24 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:41:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:41:03 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:41:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:40:42 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:40:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:40:23 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:40:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:40:02 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:40:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:39:44 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:39:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:39:22 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:39:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:39:04 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:39:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:38:42 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:38:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:38:24 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:38:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:38:02 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:38:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:37:44 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:37:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:37:22 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:37:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:37:04 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:37:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:36:42 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:36:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:36:24 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:36:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:36:02 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:36:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:35:44 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:35:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:35:23 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:35:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:35:04 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:35:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:34:42 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:34:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:34:24 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:34:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:34:03 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:34:01 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:33:44 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:33:41 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:33:22 [DHCP IP: 192.168.1.14] to MAC address 80:a5:89:c2:dd:9e, Thursday, May 10, 2018 20:33:21 [DHCP IP: 192.168.1.12] to MAC address 98:de:d0:12:26:00, Thursday, May 10, 2018 20:33:03
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
I have installed the temporary FW version 2.1.4.10_0430_dbg, links below, which fixed my system. I have several Lifx globes that became unresponsive in the two upgrades since FW V2earlier FW upgrades.1.2.18.
After installing the FW linked below, my system is now sttable and working as it should, including wired backhaul
I have installed the temporary FW version 2.1.4.10_0430_dbg, links below, which fixed my system. I have several Lifx globes that became unresponsive in the two upgrades since FW V2earlier FW upgrades.1.2.18.
After installing the FW linked below, my system is now sttable and working as it should, including wired backhaul
Hm...this sounds promising...where did this firmware come from? I would definitely like to try it but just want some input from Netgear on what this was designed to fix. If it has something to do with connectivity from 2.4GHz devices then I am extremely hopeful this will fix my last issue!
