NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
IOT device fails to communicate to cloud
Subject: RS280 Protection Engine Blocks Beatbot AquaSense 2 Pro Cloud Registration Router Information Model: NETGEAR Nighthawk RS280 Firmware: V1.2.7.2 Internet Configuration AT&T BGW320-505 configured in IP Passthrough mode RS280 receives the public WAN IP address directly IPv6 disabled WPA2 security tested Protection Engine enabled (default configuration) Device Affected Beatbot AquaSense 2 Pro robotic pool cleaner Problem Description The Beatbot AquaSense 2 Pro successfully connects to my 2.4 GHz Wi-Fi network and receives network configuration, but it consistently fails during the final "Connecting to cloud" step within the Beatbot app. The app displays: "Robot addition timed out." The robot is able to: Connect over Bluetooth. Join the 2.4 GHz Wi-Fi network. Complete Wi-Fi configuration. However, it never completes cloud registration while the RS280 Protection Engine is enabled. Troubleshooting Performed I verified all of the following: Updated RS280 to firmware V1.2.7.2. Disabled WPA3 and tested with WPA2 only. Disabled Pi-hole. Changed DNS servers. Disabled IPv6. Verified AT&T BGW320 firewall configuration. Confirmed NETGEAR Armor is not enabled. Factory reset the Beatbot multiple times. Removed and re-added the device from the Beatbot app. None of the above resolved the issue. Isolation Test To determine whether the problem was the Beatbot or my network, I connected the Beatbot to a neighbor's Wi-Fi network. The robot immediately completed cloud registration and operated normally. This confirmed: The Beatbot hardware is functioning correctly. The Beatbot cloud service is reachable. My Beatbot account is functioning correctly. The problem is isolated to the RS280. Root Cause After extensive troubleshooting, I disabled the RS280 Protection Engine under: Advanced → Security → Protection Engine Once the Protection Engine was disabled: The Beatbot immediately completed cloud registration. The device came online successfully. The robot operates normally through the Beatbot cloud and mobile app. Re-enabling the Protection Engine causes the cloud registration problem to return. Request This appears to be a false positive or compatibility issue within the RS280 Protection Engine. It is preventing legitimate outbound communication required by the Beatbot AquaSense 2 Pro during cloud registration. Please investigate whether the Protection Engine is blocking or inspecting traffic used by the Beatbot cloud service and consider providing: A firmware update to correct the issue. A whitelist or exception mechanism for trusted IoT devices. Guidance on which Protection Engine feature is responsible. This issue is fully reproducible on my RS280 running firmware V1.2.7.2. Thank you for your assistance.I'm getting ready to pull the trigger on an RS100
Sorry, i know this is a few months old, but i am curious about your comment as to why the RS200 would be better for this use case. I'm getting ready to pull the trigger on an RS100, but would like to separate my IoT devices, but still manage them with apps on my phone on my regular wifi setupDHCP address reservations had not been respected
I am having similar issues with a RS280 and firmware 1.0.6.16. We recently had an extended power outage that outlasted my UPS. When the power returned, most of the DHCP address reservations had not been respected. Looking at the reservation interface, all of my established reservation entries were there, but the attached devices list showed randomly assigned IP addresses. I did a power cycle on a couple of the devices and they were assigned the proper IP addresses. But that's a non-starter. I will double check, but I believe that all of the misassigned IP addresses were for wired connections.RS180 /BE5500 5ghz radio issue "teardown" error.
Hello. I bought this RS180 Router new from Amazon (1-21-26) and out of the box even with factory ssid/ setting it started out with the default "Netgear 11" ssid and within 30 to 40 seconds of connecting my phone to the wifi the ssid signal dropped out and came back with "teardown" as an ssid and wrong password message. the RS180 would stay like that until i restarted it. Then it would reboot with the default info again and within 30 to 40 seconds the wifi would drop out and again come back with that same error of "teardown" as the ssid. The only way i could even get into this router to configure it was the web UI, being the nighthawk app on my phone required wifi. Now after Many days of going back between this unit and my old tp-link trying everything i can think of, all the firmware's, all the resets, all the 30/30/30 hard resets, nothing. I finaly traced this issue down to just when the 5ghz radio is enabled. if you disable the 5ghz band in the web ui settings this router seems to operate correctly for the most part. ( sorry but the firmware/ web ui is the worst i have seen in almost 30 years as far as functionality that ACTUALLY DOES what the settings are supposed to do) At this point my conclusion is that the actual hardware, or the 5ghz radio it self is damaged being i have tried everything i can think of software and settings related. Everything , 2.4ghz, all the wired ports , connections and basic web ui/ android app seem to function as intended with the 5ghz radio disabled. This kinds bums a person out especially for a $200 usd unit. (was on sale for $159, but still...) and A LOT of time wasted. Any ideas or suggestions would be appreciated Thank you.
