Repository navigation
Deebot OZMO 920 working via MQTT and Python deebot-client v18 #205
Replies: 2 comments 3 replies
|
update. llm begin: Here's a detailed summary you can post: What we've tried to get the Ecovacs app working with Bumper Phones tested:
App versions tested:
Both downloaded from APKPure as XAPK split APKs. Attempt 1 — Install official app + install Bumper CA cert in user store Installed Bumper's Attempt 2 — android-unpinner patch Used the Attempt 3 — Network security config injection Discovered the app's <?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<base-config cleartextTrafficPermitted="false">
<trust-anchors>
<certificates src="system"/>
<certificates src="user"/>
</trust-anchors>
</base-config>
</network-security-config>First attempt: used Second attempt: used Attempt 4 — Testing patched app on all phones With the network_security_config patched v3.9.1 APK installed:
Current status: The network_security_config patch resolves the Java-level TLS trust issue on GrapheneOS but the robot still shows offline. On stock Android phones (S10e, Nokia 5.3), the native Questions:
llm finish tx 4 reading. really hope we can get the app working 🤞🙏 . |
|
You and your coworker have done a good job troubleshooting all those parts. Just to confirm: Your OZMO 920 is connected to Bumper without errors, and you can What's really puzzling is that Attempt 2 didn't work for you. What I miss in your Attempt 2 test description is whether you installed the user-installed certificate on Android, A few things to try:
Known quirks on my end:
I haven't found a better workaround yet, but I'll dig deeper when I get the chance, especially for mower support. |
Uh oh!
There was an error while loading. Please reload this page.
hi folks,
tx so much for Dev/s for amazing work.
Claude ai and I got my 920 working via python scripts and not yet via app 🤞
below is Claude summary as im a hobbyist and don't have too much of a clue. if you need any more info please do share. I'd love to get this to work via app 🙏
tx 4 reading
llm begin:
Sharing my setup in case it helps others with the 920 or similar models.
What's working:
OZMO 920 (firmware 1.8.2, AU region) fully connected to Bumper via MQTT
Python scripts using deebot-client v18 authenticating through Bumper and controlling the robot (start, dock, pause, clean specific rooms by ID)
Robot on isolated IoT VLAN, DNS overrides on OpenWrt redirect all Ecovacs domains to Bumper
Key things that were needed:
RSA 2048-bit certificates — the 920 firmware rejects EC certificates entirely. Set CERT_KEY_TYPE=rsa and CERT_RSA_KEY_SIZE=2048 in the Bumper container environment
The 920 uses port 443 for MQTT (not 8883), so nginx SSL termination proxying to Bumper's internal port 1883 is required
On the host running Bumper, /etc/hosts entries pointing all Ecovacs domains to the Bumper Docker bridge IP (172.22.0.2) are needed for the Python scripts to route through Bumper instead of real
Ecovacs servers
Install Bumper's ca.crt into the system CA store (/usr/local/share/ca-certificates/) so Python's SSL verification accepts Bumper's cert
App situation (still unresolved):
Ecovacs app v3.9.1 patched with android-unpinner installs and gets past login on GrapheneOS (Pixel 6a) but the robot shows offline
The app has cert pinning in native .so libraries that survives both the unpinner patch and network security config injection — SSLV3_ALERT_CERTIFICATE_UNKNOWN on most connections despite the CA being installed
Has anyone successfully gotten the app working with Bumper on a modern Android (7+) without root?
Setup: OpenWrt Flint 2 router, Intel N150 mini PC running Ubuntu + Docker/Dockge, MVladislav bumper:develop image
llm end.
take care.
All reactions