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.