Using Bumper with the Official Android/iOS App
You can use the official βEcovacsβ or βEcovacs Homeβ app to control your robot via your local Bumper server. This requires:
- DNS overrides as described in DNS Configuration.
- Trusting Bumperβs CA certificate on your device (generated via Create Certificates).
Note: Functionality may vary by app version; some features (e.g., push notifications) depend on cloud services and may not work.
π Install the Bumper CA Certificate
iOS (iOS 10+)
- Transfer
certs/ca.crt(DER format) to your device (e.g., email or AirDrop). - Tap the file to open the install prompt.
- In Settings β Profile Downloaded, tap Install and enter your passcode.
- Go to Settings β General β About β Certificate Trust Settings.
- Enable full trust for Bumper CA.
Android
Android < 7 (API 23-27)
For older releases, install the CA as a user certificate:
- Copy
certs/ca.crtto device storage. - Go to Settings β Security β Install from device storage.
- Select the cert, name it, and choose VPN and apps.
Tip: If your device or app still rejects the cert, consider pin-bypass or using a rooted device.
Android β€ 9 (API 28 and below)
On Android Pie (9) and lower, you can install the CA as a system certificate via adb:
# Start adb as root
adb root
# Remount /system writable
adb remount
# Push CA into system store
adb push certs/ca.crt "/system/etc/security/cacerts/$(openssl x509 -inform PEM -subject_hash_old -in certs/ca.crt | head -1).0"
adb reboot
Verify in Settings β Security β Trusted credentials β System.
Tip: For emulators, see the Prepare the Emulator section in Android Sniffing.
Android β₯ 10 (API 29 and above)
Starting with Android 10, user or system CA installation does not work for apps targeting API 29+. You must bypass certificate pinning instead:
- Follow the steps in Certificate Pinning Bypass.
π² Configure the App
- Launch Ecovacs Home.
- On the login screen, enter any email/password (6+ characters).
- If your robot is bound to Bumper, it appears in the device list.
- Tap the robot; the app pings it over MQTT or XMPP and opens the control interface.
Note: No real credential validation occurs; Bumper accepts all logins for compatibility.
π£οΈ Robot Voice Languages
The app can switch the voice language of the robot. The robot downloads the new voice from Bumper before it installs it, so the file has to be there:
- Fetch the voice files with
scripts/data/update-eco-voices.sh. They land in the voice directory (${BUMPER_DATA}/voicesby default) and are not part of the repository. - Start Bumper with
BUMPER_VOICESpointing at that directory. In a container the files belong in the data volume, see Docker.
Without the file the robot answers the switch with a download error and stays on the language it has. The list of languages the app offers is served by Bumper, the files themselves are fetched from the Ecovacs cloud.
πΊοΈ The Work Log
The app can show the list of the jobs of a robot and the map of every job. Bumper stores the map the robot uploads after a job and draws it as a picture, so the app has something to show:
- the work log screen reads the list from
/app/dln/api/log/clean_result/list, - the picture of a job is the map that is stored for it, drawn the same way the app draws the live map.
The pictures are kept per robot, the newest ones win when there are more than
PHOTO_MAX_PER_DEVICE of them.
The same map is shown in the web page of Bumper, under Clean Logs: the menu of a job has Show map, which opens the picture over the page.
π οΈ Troubleshooting
- No robots found: Confirm DNS overrides and that Bumper is reachable at
https://<domain>. - Login errors: Ensure your CA is trusted and HTTPS connection succeeds.
- Missing features: Some cloud-only functions (e.g., map history) are not implemented.