NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Doug-48051
Mar 04, 2019Luminary
Orbi System RBR50 - Bandwidth Connection Issue with Amazon Echo
Hello All
I have been using the AC3000 Orbi System with the Amazon echo devices for over 15 months. I am using tp-link HS100 plugs switches to control my house lamps.
Today the Amazon echo do...
Doug-48051
Mar 04, 2019Luminary
I see both devices in the Orbi Device list. I agree the logical answer is a hiccup. I updated my FW to the latest 2.1.2.232 version. I removed the Tp-link from the Amazon device list, but it will not add back in because it doesn't see them.
I am going to rest one the plugs and start from scratch. Wish me luck will keep all posted.
Now, where do I update my message board signature? LOL
ekhalil
Mar 04, 2019Master
Doug-48051 wrote:......
I am going to rest one the plugs and start from scratch. Wish me luck will keep all posted.
Now, where do I update my message board signature? LOL
Very good. Good luck.
Here is how you can change your signature:
(1)
(2)
- Doug-48051Mar 04, 2019Luminary
Thanks for the reminder, it has been a few months. Your tag says you are using AC3000 with a wired backhaul?
How did you hard wire the RBR50 to the RBS50 ?
- FURRYe38Mar 04, 2019Guru - Experienced User
Set up IP address reservations for each satellite and devices on the router as you add them to the router. The satellites need to be set up via wireless first. Then connect 1 satellite at a time to the ethernet LAN cable. Wait 5 minutes and the top led on the satellite should turn on BLUE. Set up an IP address reservation for the 1st satellite. Continue to do the same thing for the 2nd satellite. Then follow up with your devices.
- Doug-48051Mar 04, 2019Luminary
UPDATE:
Amazon calls and stated they would do a 3-way call with Netgear Support to split the SSIDs.
During the call with the 2 vendors, Netgear created an issue ticket and promised to call back in 30 mins. (NetGear NEVER called back???)
Amazon still states the devices must be on the same network.
While waiting I started doing additional research.
The user credentials for the TP-Link Skill inside the Alexa app was missing. Once the Tp-Link credentials were updated I re-enabled the skill and had the Alexa device re-discover the devices. All the devices were re-populated in the Alexa app, even those on different networks.
This would seem to indicate a few things:
1. A possible update eraser the credentials (Only guessing here)
2. Amazon does not seem to understand how a MESH network works.
3. NetGear did not seem to care enough to call back.
Not to be too personal here but... I am disabled in a chair and I use this network and these products to live and function. I understand that troubleshooting takes effort and not everyone knows everything, but at least both companies could have stuck it out instead of passing the buck and leaving the customer with no options. :(