Scuba V3 aucune notification dans l’application après le cycle de nettoyage
Five likely causes: in-app notification settings, phone system permissions, phone notification permissions, poor pool-area Bluetooth signal, filtre blockage preventing surfacing, or the 1-hour deduplication rule.
If your Scuba V3 completes a cycle de nettoyage but you receive no notification push, work through these five checks in order: (1) In-app settings — open application Aiper > Paramètres de l’appareil > Rappels de notification, ensure all relevant toggles are ON. (2) Phone permissions — check Réglages iOS > Notifications > Aiper, or Paramètres Android > Apps > Aiper > Notifications. (3) Bluetooth range / phone network — the V3 uses your connexion Internet de votre téléphone via Bluetooth; the robot must surface and reconnecter via BLE, and votre téléphone needs network access to push the notification; weak signal = missed connection. (4) Filtre obstrué — a obstrué filtre prevents the robot from climbing to the ligne d’eau at all. (5) 1-hour dedup rule — only one low-batterie notification is sent per hour; re-déployerments within the same hour will not trigger a second alert.
0. Vérifiez d’abord les mises à jour du micrologiciel
Before troubleshooting notification settings, connect to your Scuba V3 in l’application Aiper and check for a pending OTA mise à jour du micrologiciel. Aiper periodically improves surfacing and notification behaviour through micrologiciel. Install the latest version if available, then run a short test cycle to see if notifications reprendre. Many notification issues are resolved by micrologiciel alone, sans avoir besoin de change any settings.
1. Vérifiez les paramètres de notification dans l’application
Open l’application Aiper, go to the device page for your Scuba V3, and tap the icône Paramètres (top-right corner). Select Rappels de notification and verify that the notification content you want (cleaning complete, low batterie, error alerts) is toggled ON. If any are off, l’application will not send notification pushs for those events even if the robot surfaces and reconnecters.
2. Vérifiez les autorisations du système téléphonique
Even if notifications are enabled in l’application Aiper, your système d’exploitation de votre téléphone may be blocking them. On iOS: go to Settings > Notifications > Aiper, and ensure Autoriser les notifications is enabled with Banners or Alerts selected. On Android: go to Settings > Apps > Aiper > Notifications, and ensure all notification categories are allowed. Some surcouches Android (Samsung, Xiaomi, Huawei) have aggressive batterie optimisation that suppresses notifications en arrière-plan — add Aiper to the ‘Sans restriction’ or ‘Ne jamais mettre en veille’ batterie list.
3. Portée Bluetooth et réseau téléphonique à la piscine
The Scuba V3 must surface and reconnecter to votre téléphone via Bluetooth before it can push a notification. The V3 n’a pas de Wi-Fi — it relies on votre téléphone’s internet connection. If the Bluetooth signal between votre téléphone and the pool is weak (e.g., votre téléphone is indoors far from the pool), or votre télé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 amarrage window. Bring votre téléphone to the poolside. Ensure Bluetooth is ON and l’application Aiper 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 notification push from Aiper’s servers. If Bluetooth keeps dropping at the poolside, try keeping votre téléphone within 5–10 mètres (15–30 pieds) of the pool during the cleaning window. A Bluetooth range extender is not supported — the V3 communicates directly with votre téléphone. Note: the robot stores cleaning data locally and syncs it the next time it successfully connects — no data is lost, only delayed.
4. Filtre obstrué empêchant la remontée à la surface
If the panier filtrant is severely obstrué, the rear buses de jet cannot produce enough jet d’eau for the robot to climb the wall. The robot will remain submerged and never surface to reconnecter — therefore no notification is sent. Rinse the panier filtrant after every 2-3 sessions. If the robot consistently fails to surface, clean the filtre immediately and run a test cycle to confirm it can now climb to the ligne d’eau. See also: Scuba V3 ne s’arrête pas à la ligne d’eau.
5. La règle de déduplication des notifications sur 1 heure
The Scuba V3 micrologiciel includes a 1-hour notification deduplication window. The system only sends one low-batterie amarrage notification per hour. If you re-déployer the robot after the first low-batterie s’amarrer and it s’amarrers again within the same hour, a second notification will not be sent. This is by design to prevent notification spam. If 1 heure has passed since the last notification and you still receive none, revisit steps 1-4 above.
Quand faire remonter au support Aiper
If you have verified all five steps above and still receive no notifications, collect the following before contacter le support: (1) your device numéro de série (SN) from the sticker on the robot or l’application, (2) screenshots of your in-app notification settings and phone system notification settings for Aiper, (3) l’applicationroximate date when notifications stopped working. Use l’application’s Upload Log function to send diagnostic data, then contact support technique Aiper or the groupe de feedback après-vente.
.webp)
