Installing Apps/Devices that cannot connect on 5g when trying to use Orbi and Pixel Phones

---

TButcher wrote:

That pesky Amazon Echo that just will not see my network no matter what, well, whatever..maybe it's just an old one (it is actually a first generation).  So, I'm just scrapping that damn thing.

---

Don't scrap it - complain to Amazon! 

For other failures, it's typically crappy IoJ and App design: The mobile device with the App does connect to the very same L2 and L3 network - any kind of discovery (broadcast, known multicast like UPnP SSDP or Bonjour, proprietary multicast protocols*, ...) - does work fully transparent between any AP radio band and the network. 

*in some managed network environments, unknown (non-registered) multicast might be blocked - so using these is another no-go.

"I don't disagree with the sentiment that it's the App developers that are the issue.  Because it is quite the pain in the butt to have to do this each time I will say."

Your disagreement would be misplaced. You must undertand that these "IoT Mfrs" put out these 2.4Ghz only supporting devices and then tie them up with there 2.4Ghz only suporing setup and management software apps that get in installed on "dual band" supporting devices. Both phones and pads of today are dual band supporting. 2.4Ghz and 5Ghz. These two frequencys are on the SAME WLAN side network. Thus there is a connection with either frequency to the same network. It's these "IoT Mfrs" who fail to realized or possible just don't want to invest more money in development in there "setup software application" that gets installed on dual band devices that "there" application could and should work on a dual band supporting device regardless of which frequency it's connected too. If the IoT device can see the 2.4Ghz SSID while the phone or pad is on the 5Ghz SSID, both frequencies being connected to the SAME WLAN network, then why should there "setup application" be so limiting and causing "quite the pain in the butt" experiences. 

You'd think maybe some IoT Mfrs would look into this more and make the change with there application. It shouldn't be that hard. It's there application that is causing this problem. Has nothing to do with NG or Smart Connect MESH systems! 

FYI, my 1st gen DOT has never had a problem connecting to either Orbi AC RBK50 or Orbi AX RBK853. Though I have always used the same SSID name and PW when migrating or installing new routers. 

---

TButcher wrote:

So, first off, I'm back from travel and came straight to the office to try CrimpOn's solution since, this was the fist time after scouring the Web I saw an actual solution I could try (note: this is after contacting both Netgear PAID support and Amazon's support departments, mind you, as well as searching the Web, before I stumbled across some sort of post here that led me to try posting/searching here).

 

Let me say, KUDOS.  It worked.  Mostly.  It got the smart plugs I was trying to get installed right off the bat.  That pesky Amazon Echo that just will not see my network no matter what, well, whatever..maybe it's just an old one (it is actually a first generation).  So, I'm just scrapping that damn thing.  Anyway, thank you very much.

 

I don't disagree with the sentiment that it's the App developers that are the issue.  Because it is quite the pain in the butt to have to do this each time I will say.  However, I will also say, the fact that I contacted Netgear Support first who had no clue and the fact that there is no Knowlege Gear article (I'm a tech writer and know this should be one) is an issue as well.

 

Finally - I want to address Michael's comments:

 

<<It is surprising how many people insist that it is impossible to set up IoT gadgets without separating 2.4 GHz and 5 Ghz. They bang on without even bothering to try this well known strategy for getting things to work.>>

 

Well known to whom?  Networking gurus such as yourself?  I know just enough to get into the Admin section and that's it.  And that's only because I'm "sort of" in the tech world.  The fact that I called Netgear support and THEY didn't know makes this statement suspect.

 

So they turn up here with complicated scenarios that have nothing to do with the real world. The pity is that Netgear has failed to come up with a KnowledgeBase article that explains what to do.

 

<< Oh, and if anyone does encounter a reluctant device, tell the people who made the IoT device that they need to get their act together: also tell people here so that @plemans can buy some new toys. Netgear is not the only maker of Mesh stuff and Orbis are not the only Netgear devices that combine SSIDs. >>

 

Can't disagree here.

 

<<Finally, when trying anew device, search this community for it. You might be surprised to learn that it has already cropped up here, along with advice on how to get it to work.>>

 

First thing I did.  As well as  the Web before here.  However, unless the Subject line/text is very specific it is often hard to find.  And people do not know what is wrong.  Case in point:  When I first started researching this subject, it was because I was being told my network password was incorrect even though I knew I had not changed it.  Which, in the end, led me here but had nothing to do with the issue (Amazon Support told me my network was open and then never got back to me).  Even though I've been a bit more specific in my Subject line, I'm not sure it will help.  Because I'm not sure people know what they are actually looking for at first.

 

---

---

TButcher wrote:

Finally - I want to address Michael's comments:

 

<<It is surprising how many people insist that it is impossible to set up IoT gadgets without separating 2.4 GHz and 5 Ghz. They bang on without even bothering to try this well known strategy for getting things to work.>>

 

Well known to whom?  Networking gurus such as yourself?  I know just enough to get into the Admin section and that's it.  And that's only because I'm "sort of" in the tech world.  The fact that I called Netgear support and THEY didn't know makes this statement suspect.

Anyone who turns up here and asks for help, or who bothers to search the archives for the devices they want to connect.

Believe me, there have been dozens of discussions of this issue over recent months. I have lost count of the number of times people have been told "turn off the 5Ghz SSID" only to be amazed that it works.

Sadly, these messages do get muddled up with contributions from people who insist that the only answer is for users to have the ability to break Orbi's underlying technology and run with separate SSIDs. Nonsense.

By the way, I am no networking guru, just a long-time user from dial-up days, acoustic couplers eve, who has earned a living writing about technology that makes this stuff look trivial.

---

TButcher wrote:

However, I will also say, the fact that I contacted Netgear Support first who had no clue and the fact that there is no Knowlege Gear article (I'm a tech writer and know this should be one) is an issue as well.

 

Sadly, this seems to be a common issue. Many of Netgear's support people seem to know less than some of the regulars here.

You are not the first person to suggest writing a KnowledgeBase article. See above

Re: Installing Apps/Devices that cannot connect on... - NETGEAR Communities

And that isn't even the first time that I have put forward the idea.