NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Adding Eve Light Strip as accessory in Home in iOS with ORBI RBR50v2 mesh network (requires 2.4 GHz)
Hi, I have been trying for the past several days to configure a brand new Eve Light Strip to work with my existing WiFi network which consists of an ORBI RBR50v2 + satellite. iOS refuses to add t...
Yes I agree that at this stage, it doesn't look like an ORBI problem. It looks like an Eve problem, and either they can help solve it or they can't.
Interestingly, two more things I noticed: after the failed pairing (and even before), the Eve Light Strip is listed as a connected device under the list of connected devices on my router's web-based control panel, with IP address 192.168.1.5. AND even though, after the failed pairing, the Eve software on the iPad (IP address 192.168.1.12) says that the Eve device is "not responding", if I tap on the "ID" button in the settings for that accessory, it still causes the Eve device to blink, so that part of the system works. Obviously this suggests that there is SOME connection between the Eve software on the iPad and the Eve device!
Just shared these two bits of additional info with Eve's tech support. We'll see what they have to say. But you're right that this closes the ORBI/Netgear chapter of this "adventure" for now. Thanks for the suggestions.
shutting off wifi doesn't shut off its routing functions and causes a double nat.
A double nat happens when you cascade more than 1 router.
https://kb.netgear.com/30186/What-is-Double-NAT
Fixes? There’s 3 options but only use 1.
1. Put the modem/gateway in modem only/pass through mode. This disables its routing functions.
2. Leave the modem/gateway in router mode but put the Netgears IP address into its DMZ. This forwards the data to the netgear. You can either leave the modem/gateway’s wireless enabled or disabled. Just make sure its using a different wifi channel to prevent interference
3. Put the Netgear into access point mode. This disables its routing functions. Wifi/ethernet still works but it does disable some features.
https://kb.netgear.com/26765/Which-features-are-disabled-on-my-NETGEAR-router-when-it-is-set-to-AP-Mode
The cable router IS configured properly. It doesn't act as a router. It IS in pass-through mode. I just thought I'd specify that the WiFi part of the configuration is definitely OFF.
Now I've just been told by Eve support that not only is the 2.4 GHz band required for configuration, but Eve also doesn't support a LAN using 10.0.x.x IP addresses, which is what I have. Apparently, it REQUIRES 192.168.x.x addresses, which sound ridiculous to me. There's nothing anywhere against using 10.0.x.x addresses, which I cannot easily changed because all kinds of devices are configured for that network.
In any case, I have turned off my ORBI bnetwork, added a 2.4 GHz WiFi network to the configuration of the cable router, using the same SSID and password, and connected my devices to it. Then I I have reset the Eve LS and tried pairing again.
It STILL failed.
At this point, I am afraid I am going to have to give up and ask for a refund. This is absurd. If that's the future of home automation, we're in for a world of hurt.
Pierre
A suggestion, if you want to try this to see if you can keep the Eve Light strip. Turn OFF the Orbi system.
Enable the router and wifi signal on the modem. Use same SSID name and PW as you use on the Orbi system.
If the modem has a option to either disable the 5Ghz radio or have separate SSID names then set the 2.4Ghz radio on the modem for same SSID name and PW as on the Orbi system.
Use this to get this Light strip connected. If and when you get it connected, Turn ON the Orbi system. While the orbi system is coming online, change the modem back to bridge mode, this should also disable it's wifi radios.
During this transition period, if you leave the light strip ON, it should auto connect and migrate to the Orbi system which it should see the same SSID name and password and connect there.
Thanks for the suggestion, FURRYe38. As a matter of fact, that's exactly what I tried. I should have provided more information. I actually have TWO Internet connections in my house, one for personal home service and one for home-based business service. Both of them use the same kind of modem (Arris DG3270), The business one is configured with the 10.0.x.x IP range and the home one is configured with the 192.168.x.x IP range. By default, I only have ONE WiFi network, the one provided by the ORBI system connected to the business router, so that my IP addresses for WiFi devices are in the 10.0.x.x range. THAT is the router that is configured as a bridge (pass through) and does not have WiFi on.
The home router is configured with the 192.168.x.x range and does not work as a bridge (pass through) because there is nothing else connected to it other than wired end devices via Ethernet (TV, home computer, etc.). THAT is the router that I used to follow your suggestion, i.e.
1) I turned the ORBI system completely off, so that I no longer had a WiFi network with its SSID in the house.
2) I configured the home router to turn its 2.4 GHz-only WiFi network on, using the exact same SSID and password as the now-off ORBI.
3) I connected my iPad to the "new" network with the same SSID. (It actually did it automatically, since it was the same SSID with the same password.)
4) I attempted to pair the Eve Light Strip with the iPad using the Eve mobile app.
As in previous attempts, the iPad did "see" the Eve Light Strip and the first steps appeared to work fine. But then at the last hurdle (Enable Light Automations, etc.), it failed with an unhelpful error message (see pic). Needless to say, the iPad WAS connected to the Internet and the Internet connection worked just fine.
After that, when I tapped on OK in the error dialog, the Eve was added to my Home as an accessory, but the device was listed as "not responding" and I could not control it using the Eve app.
This is the exact same error I have been getting all along. The light strip is "seen" by iOS/Eve, but the accessory never does get added properly and it always has a "warning" icon indicating that it's not responding.
I have already spent way too much time on this. Unless the Eve folks can finally come up with a solution that works, I am going to give up. I like tinkering as much as the next Mac user, but this is getting to be too frustrating for words.
betalogue wrote:As in previous attempts, the iPad did "see" the Eve Light Strip and the first steps appeared to work fine. But then at the last hurdle (Enable Light Automations, etc.), it failed with an unhelpful error message (see pic). Needless to say, the iPad WAS connected to the Internet and the Internet connection worked just fine.
Sorry you're having Eve issues but your last test (without Orbi) shows it's not an Orbi-specific problem.
BTW I guess that the app error at the last hurdle is saying your iPad cannot see the/a home IP address of the Eve device, not that your iPad doesn't have internet connectivity. The initial "sees Eve device" is not over IP but instead Bluetooth. Your wi-fi network is configured to allow any home device to see other devices, right (not Guest wireless with device isolation enabled)?
