NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
I just got off the phone with their support, which was useless
I just got off the phone with their support, which was useless. They told me to separate my network and rename them different names for the 2.4GHz and 5.2Ghz bands. I have a boatload of devices conne...
Yes, it's really annoying to have to dig for tweaks anymore. It's just not that hard to code for.
Anyway, I also thought about turning off SSID broadcast on the 5GHz network yesterday. By itself it still didn't work. What did work was also turning off 20/40MHz coexistence, essentially favoring the 2.4GHz network. Together, that finally worked. What a pain.
Thanks for taking the time to try to help. I forwarded the solution that worked for me to them, but you should definitely hit them up for a contract to improve their product and customer experience.
A simple fix on the **** code would solve all problems. There is no reason for the App to check if the connection is established on the 2.4 GHz band - all there is is to double check if there is a network IP connection, then an IP broadcast (as proprietary Apps or programs do it for decades), or a multicast (like Bonjour...) to the network (WiFi, 2.4 GHz, 5 GHz, 6 GHz, Bluetooth, whatever does not matter at the end of the day)... and voila, the devices will be discovered. Nothing on your infrastructure requires adjusting - Orbi (and the Nighthawk Mesh) are nice systems.
I'm happy to go into a consulting job for this lock manufacturer (and any other OEM implementing the same poor chipset code) - usually, I'm can be hired for a one-off fee of 10% of the annual product volume they make.
There is no reason for a "new" Mesh system, all the additions crafted allowing to create an SSID (connecting to the very same L2 network at the end of the day!!!!) are just hacks to work around dumb IoT design. Waste of time, energy, money, and valuable resources to "fix" something some **** engineers created years ago, with ZERO understanding on how networking works since abut the year 1980. About the year I started my first Ethernet deployments with DEC.
Yes, it's really annoying to have to dig for tweaks anymore. It's just not that hard to code for.
Anyway, I also thought about turning off SSID broadcast on the 5GHz network yesterday. By itself it still didn't work. What did work was also turning off 20/40MHz coexistence, essentially favoring the 2.4GHz network. Together, that finally worked. What a pain.
Thanks for taking the time to try to help. I forwarded the solution that worked for me to them, but you should definitely hit them up for a contract to improve their product and customer experience.