Scuba V3 Sin Notificación de la App Después del Ciclo de Limpieza
Cinco causas probables: configuración de notificaciones en la aplicación, permisos del sistema del teléfono, permisos de notificación del teléfono, señal Bluetooth deficiente en el área de la piscina, obstrucción del filtro que impide la emersión o la regla de deduplicación de 1 hora.
If your Scuba V3 completes a ciclo de limpieza but you receive no notificación push, 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) alcance Bluetooth / phone network — the V3 uses el internet de su teléfono vía Bluetooth; the robot must surface and reconnect via BLE, and your teléfono necesita acceso a la red to push the notification; weak signal = missed connection. (4) Filtro obstruido — a filtro obstruido prevents the robot from climbing to the línea de flotación 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. Verifique las actualizaciones de firmware First
Before troubleshooting notification settings, connect to your Scuba V3 en la aplicación Aiper and check for a pending OTA actualización de firmware. Aiper periodically improves surfacing and notification behaviour through firmware. Instale la última versión if available, then run a short ciclo de prueba to see if notifications resume. Many notification issues are resolved by firmware alone, without needing to change any settings.
1. Verifique la configuración de notificaciones en la aplicación
Abra la aplicación Aiper, 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 (limpieza completada, batería baja, error alerts) is toggled ON. If any are off, the app will not send notificación pushs for those events even if the robot surfaces and reconnects.
2. Verifique los permisos del sistema del teléfono
Even if notifications are enabled en la aplicación Aiper, 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. Alcance Bluetooth y red del teléfono en la piscina
The Scuba V3 must surface and reconectarse a su teléfono vía Bluetooth before it can push a notification. El V3 no tiene Wi-Fi propio — it relies on your phone’s conexión a internet. If the señal Bluetooth 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 no logre establecer una conexión BLE dentro de la ventana de atraque de 10 minutos. Bring your phone to the poolside. Ensure Bluetooth is ON and la aplicación Aiper is allowed to run in the background. Su teléfono también necesita una conexión a internet activa (datos móviles o Wi-Fi doméstico que llegue al área de la piscina) to deliver the notificación push from Aiper’s servers. If Bluetooth keeps dropping at the poolside, try keeping su teléfono a una distancia de 5–10 metres (15–30 feet) of the pool during the cleaning window. A alcance Bluetooth extender is not supported — the V3 communicates directly with your phone. Note: the robot stores datos de limpieza localmente and syncs it the next time it successfully connects — no se pierden datos, solo se retrasan.
4. Obstrucción del filtro que impide la emersión
If the cesto del filtro is severely clogged, the rear jet nozzles cannot produce enough chorro de agua for the robot to climb the wall. The robot will remain submerged and never surface to reconnect — therefore no notification is sent. Rinse the cesto del filtro after every 2-3 sessions. If the robot consistently fails to surface, clean the filter immediately and run a ciclo de prueba to confirm it can now climb to the línea de flotación. Consulte también: Scuba V3 No Atraca at Waterline.
5. La regla de notificación duplicada de 1 hora
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. Esto es por diseño to prevent notification spam. If 1 hour has passed since the last notification and you still receive none, revisit steps 1-4 above.
Cuándo escalar a Soporte de Aiper
If you have verified all five steps above and still receive no notifications, reúna lo siguiente antes de contactar a support: (1) your device número de serie (SN) from the sticker on the robot or the app, (2) screenshots of your in-notificación de la app settings and phone system notification settings for Aiper, (3) the approximate date when las notificaciones dejaron de funcionar. Use the app’s Subir registro function to send datos de diagnóstico, then contact soporte técnico de Aiper or the grupo de comentarios postventa.
