Is anyone successfully using v2.1.4.10 for wired backhaul?
I purchased the RBK53 kit from CostCo yesterday. I immediately updated the firmware which proved to be a challenge. One of the satellites refused to report the firmware version back to the router, so it just sat with the "please wait a moment message". At this point, all three units were in the same room about 15ft. apart, and they were still having trouble communicating. After several restarts, I finally managed to get them updated (v2.1.4.10) at which point I started the process of placing them in my home and configuring. Let's just say that it took several hours and starting over multiple times to get to a place where all units are communicating and using wired haulback. I did this by following the steps outlined earlier in the thread, and being very patient.
I wanted to point out a couple of things that I've observed during this setup process and during the post-setup testing to see if anyone has suggestions:
1. The overall coverage area of each unit seems to be very small with little ability to transmit through walls. I have a Nighthawk R7500 single router that seems to provide better coverage and faster speeds than all three of the Orbi units.
2. Once configured for wired haulback, the satellites do not seem to be able to communicate firmware version back to the router. That screen simply hangs, which implies that firmware updates will require moving all of the satellites closer together and leveraging wireless haulback.
3. When a client is connecting through a satellite the process of joining the wifi network fails with an incorrect password message even when the password is correct. Moving to the room with the router allows the user to join the network with the same password.
4. The Orbi iOS app fails to find the Orbi system when launching through a satellite, but does work when in the room with the router.
Any suggestions? I'm hoping that a firmware update will fix most of this stuff. If not, I will be taking advantage of CostCo's return policy.