NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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.
13 Replies
Something to contact NG support about and let them know. PE maybe blocking too much and may need to be tuned in.
Having some issue with Protection Engine on a RS200, cannot get my Tesla Powerwall 2 (2.4Mhz only on this item) to join my network, if I disable "Protection Engine" it can join, so something new in last firmware, running current V1.2.7.2
Something to contact NG support about and let them know. PE maybe blocking too much and may need to be tuned in.
Having some issue with Protection Engine on a RS200, cannot get my Tesla Powerwall 2 (2.4Mhz only on this item) to join my network, if I disable "Protection Engine" it can join, so something new in last firmware, running current V1.2.7.2
Thanks for the update there a section in router that has IOT, can I add Telsa Powerwall there, I will raise a support to let NG know.
Do you know this IOT section?
Right found under Advanced Tab / Advance Setup / Wireless Settings / IOT NETWORK
Will try if not a raise a ticket NG.Let us know if that works or not.
Well I set it up on IOT, but does not work, can see the Access Point, that able it.
So I try this one for Nighthawk Routers and it worked:https://kb.netgear.com/000066695/How-to-resolve-issues-connecting-devices-to-your-NETGEAR-WiFi-7-network
I'm still having issue with my printer not working as it uses Wifi as well.So your using Guest Network for your device now?
The IoT network and setting a WPA2 only mode didn't work?
What printer model is this? Does it have ethernet port by chance? if so, try ethernet connecting printer?
So your using Guest Network for your OLD devices now? Yes work fine. i.e Fronuis Inverter, and Telsa Powerwall 2.
The IoT network and setting a WPA2 only mode didn't work? Yes do not work.
But my problem now has nothing do with NG gear.
My Workforce 60 printer which has 10/100 port is stuck on wrong port via wireless which I cannot see, I've try with "Epson Net config port software" but cannot see this printer via wireless, would connecting it to the 10/100 port might help you think?
See photo.
Network sheet.
IP Address 192.168.0.4
Subnet Mask 255.255.255.0
Default Gateway 192.168.0.1
When my gateway is 192.168.1.1?Cannot get it to setup under 192.168.1.1 gateway, as the wireless in on the wrong ip address for this router?
Would pluging in the old router then using the "Epson Net config" to alter the ip address over to the right gateway and just pick 192.168.80.1 for printer would do, this is what I'm thinking of doing?
As we cannot use the wireless of this printer, and only can use via a usb cable.By the way I've not turn on "Protection Engine" as of yet, as I don't want anymore problem, so I'm leaving it off.
