NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Adding 2.4 ghz devices to Orbi
I have the Orbi RBR20 which is not listed in the model drop down. I also have an Android phone runing Oreo. I have bought two wi-fi plugs to connect to Alexa and a La Crosse weather station that us...
I did some experiments trying to learn "what goes on" when a smart plug is configured to work on a WiFi network. I now have three smart plugs: TP-Link HS-105, Belkin Wemo mini smart plug, and Aukey SH-PA1 mini smart plug. The goal was to use Wireshark to capture the packets which go back and forth across the network and see how they connect.
TP-Link HS-105 mini smart plug.
There was an immediate problem: my Orbi 2.4G network was on channel 11 and the TP-Link plug created a WiFi access point on channel 6 ("TP-Link_Smart Plug_171F", where 17:1F is the last two octets of the MAC address). Alas, a WiFi adapter used with Wireshark can monitor only one channel, so I did not get packets between phone and plug. However, this did confirm my belief that the existing smartphone connection was irrelevant, The smartphone TP-Link Kasa app connected to the TP-Link smart plug even though it
was on a different WiFi channel. And, once the SSID and password were sent to the plug, the plug was able to find my Orbi on channel 11. TP-Link printed the plug MAC address on the case, so I forced Orbi to channel 6 and was able to capture the entire process. The STRANGE thing was that I did NOT capture any packets directly between the smart plug and my smartphone. All I saw were broadcast packets. It was also clear that the smartphone app encrypted my Orbi SSID and password before sending them to the smart plug.
Belkin Wemo mini smart plug.
Configuring the Belkin Wemo mini smart plug went about the same way, except it was a lot more complicated and confusing. Belkin printed the MAC address on plug so I was able to configure a Wireshark capture on channel 6. The app complained about my Android phone being too cavalier about changing WiF networks, and it spent a LONG time "looking". Eventually, the Wemo app turns the plug on and off as it should. Once again, the Wireshark captured almost entirely broadcast packets. i.e. the phone does not seem to talk directly to the Wemo. During the process, my phone remained connected to Orbi at 5G and simultaneously talked 2.4G on channel 6. Wemo also appears to encrypt data that goes to the smart plug.
Aukey SH-PA1 mini smart plug.
It appears that the Aukey did NOT create a WiFi SSID. The Aukey app was similar to Belkin Wemo in complaining about "must be connected to 2.4G". I ignored the complaint and clicked "Continue". App found the plug and it turns on and off as expected. Aukey did not print the device MAC address on the product, so after it was working, I went to Orbi's attached devices and learned the MAC address. Reset the plug to factory and did a Wireshark capture. THIS TIME, the Aukey app asked if I wanted to use Bluetooth to find and configure the plug. "What the heck. Why not?" Went smoothly and the plug works fine. (Maybe it asked about bluetooth the first time and I just didn't see the message.) Aukey also seems to communicate using only broadcast packets and encrypts data.
I have noticed that all three smart plugs make a distinctive "snapping" sound when they turn on and off. I guess to support 15 amps, they need to switch a physical relay.
So, what have I learned (besides how difficult it is to use Wireshark on WiFi networks)?
I now have three brands of smart plug (a) that all say they require a 2.4G network, (b) that managed to get connected even though my phone was connected to an Orbi 5G channel, (c) that seem to communicate using only broadcast packets, and (d) that I really like using bluetooth to connect devices. I still have no clue how the plugs can be controlled remotely. (Does Orbi have a way to report when devices open ports to remote hosts?)
I remain convinced that "Orbi isn't the problem" when devices cannot be connected, but I am no closer to learning what IS the problem.
After installing several TP Link devices, including switches and lights as well as plugs, while disregarding the "Set you mobile device to 2.4GHz" instruction and never having any problem, I am convinced that Orbi is both the problem and the solution. The initial search for the Kasa device on the app is between the device and phone. You need to be there, near the Kasa device for that to properly work. Especially true with a switch in the wall. Before setting up devices, people read the 2.4GHz requirement and try to figure out how to do this with the Orbi and run into a wall. However, I believe that the instruction has more to do with connecting the device to the network. In a some non mesh router, your device chooses between bands in a manner that is actually switching networks though you may have set the SSID to a single name. Some do not. If your phone is connected to 5GHz but with the common name, when you choose the network for the Kasa to hook up to it will look for that.and falter. To prevent this, the instructions are specific to insure your device is connected to your 2.4GHz network so you can properly tell the Kasa device the right band network. With Orbi the SSID base is inherently common for either network. Telling the Kasa device to hook up to you Orbi network it is slam dunk. It sees the 2.4GHz Orbi network SSID and connects. Bottom line on Kasa, the instructions for the mobile device hook up to the wifi are more for the Kasa network hook up section for non mesh type routers. When hooking the Kasa device to the network your phone may only be giving you the network option that your phone is currently on with conventional dual band routers. With Orbi that is no problem.