Scuba V3 No App Notification After Cleaning Cycle
Five likely causes: in-app notification settings, phone system permissions, phone notification permissions, poor pool-area Bluetooth signal, filter blockage preventing surfacing, or the 1-hour deduplication rule.
If your Scuba V3 completes a cleaning cycle but you receive no push notification, work through these five checks in order: (1) In-app settings — open Aiper app > Device Settings > Notification Reminders, ensure all relevant toggles are ON. (2) Phone permissions — check iOS Settings > Notifications > Aiper, or Android Settings > Apps > Aiper > Notifications. (3) Bluetooth range / phone network — the V3 uses your phone’s internet via Bluetooth; the robot must surface and reconnect via BLE, and your phone needs network access to push the notification; weak signal = missed connection. (4) Filter blockage — a clogged filter prevents the robot from climbing to the waterline at all. (5) 1-hour dedup rule — only one low-battery notification is sent per hour; re-deployments within the same hour will not trigger a second alert.
0. Check for Firmware Updates First
Before troubleshooting notification settings, connect to your Scuba V3 in the Aiper app and check for a pending OTA firmware update. Aiper periodically improves surfacing and notification behaviour through firmware. Install the latest version if available, then run a short test cycle to see if notifications resume. Many notification issues are resolved by firmware alone, without needing to change any settings.
1. Check In-App Notification Settings
Open the Aiper app, go to the device page for your Scuba V3, and tap the Settings icon (top-right corner). Select Notification Reminders and verify that the notification content you want (cleaning complete, low battery, error alerts) is toggled ON. If any are off, the app will not send push notifications for those events even if the robot surfaces and reconnects.
2. Check Phone System Permissions
Even if notifications are enabled in the Aiper app, your phone’s operating system may be blocking them. On iOS: go to Settings > Notifications > Aiper, and ensure Allow Notifications is enabled with Banners or Alerts selected. On Android: go to Settings > Apps > Aiper > Notifications, and ensure all notification categories are allowed. Some Android skins (Samsung, Xiaomi, Huawei) have aggressive battery optimisation that suppresses background notifications — add Aiper to the ‘Unrestricted’ or ‘Never sleep’ battery list.
3. Bluetooth Range & Phone Network at the Pool
The Scuba V3 must surface and reconnect to your phone via Bluetooth before it can push a notification. The V3 does not have its own Wi-Fi — it relies on your phone’s internet connection. If the Bluetooth signal between your phone and the pool is weak (e.g., your phone is indoors far from the pool), or your phone has poor mobile/Wi-Fi internet at the poolside, the robot may surface but fail to establish a BLE connection within the 10-minute docking window. Bring your phone to the poolside. Ensure Bluetooth is ON and the Aiper app is allowed to run in the background. Your phone also needs an active internet connection (mobile data or home Wi-Fi reaching the pool area) to deliver the push notification from Aiper’s servers. If Bluetooth keeps dropping at the poolside, try keeping your phone within 5–10 metres (15–30 feet) of the pool during the cleaning window. A Bluetooth range extender is not supported — the V3 communicates directly with your phone. Note: the robot stores cleaning data locally and syncs it the next time it successfully connects — no data is lost, only delayed.
4. Filter Blockage Preventing Surfacing
If the filter basket is severely clogged, the rear jet nozzles cannot produce enough water spray for the robot to climb the wall. The robot will remain submerged and never surface to reconnect — therefore no notification is sent. Rinse the filter basket after every 2-3 sessions. If the robot consistently fails to surface, clean the filter immediately and run a test cycle to confirm it can now climb to the waterline. See also: Scuba V3 Not Docking at Waterline.
5. The 1-Hour Duplicate Notification Rule
The Scuba V3 firmware includes a 1-hour notification deduplication window. The system only sends one low-battery docking notification per hour. If you re-deploy the robot after the first low-battery dock and it docks again within the same hour, a second notification will not be sent. This is by design to prevent notification spam. If 1 hour has passed since the last notification and you still receive none, revisit steps 1-4 above.
When to Escalate to Aiper Support
If you have verified all five steps above and still receive no notifications, collect the following before contacting support: (1) your device serial number (SN) from the sticker on the robot or the app, (2) screenshots of your in-app notification settings and phone system notification settings for Aiper, (3) the approximate date when notifications stopped working. Use the app’s Upload Log function to send diagnostic data, then contact Aiper technical support or the after-sales feedback group.
