Repository navigation
Deebot T90 Pro Omni (fw 1.97.0) — bot pins TLS on port 443, self-signed cert rejected #267
Unanswered
Doenourustig
asked this question in
Q&A
Replies: 2 comments
|
As this bot is a newer bot, you will not get any support. bumper seems for older bots only where you can install self signed certs on the bot. as the t90 is newer than the x11 it should be the same situation: #186 |
0 replies
Have you checked the UART pinout on the T90 Pro Omni to see if it looks similar to the one shown in the T10 PLUS guide? If the pinout is similar, the same connection method might work. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Reporting my findings for the Deebot T90 Pro Omni (CES 2026 model),
in case it's useful for the compatibility list or the ngiot/robotww work.
Short version: on my firmware the bot rejects self-signed certificates,
so Bumper cannot intercept it without unpinning the bot itself.
Device
Setup
blocking of Ecovacs traffic.
jmq-ngiot-eu.dc.robotww.ecouser.netto a local test server.Domains the bot actually queries
This bot is fully on the ngiot / robotww stack. No legacy
portal-*,msg-*ormq-*.ecouser.netqueries at all. Observed on boot:jmq-ngiot-eu.dc.robotww.ecouser.netapi-ngiot.dc-eu.robotww.ecouser.netca.robotww.ecouser.net← looks like an Ecovacs-run CA endpointeis-nlp.dc-eu.ww.ecouser.net(voice/NLP)perf-ops-cn.dc.cn.ecouser.net(telemetry to CN datacenter)Note
jmq-ngiot-eu.dc.robotww.ecouser.netis already listed under"Current Domains with TLS Errors" in the docs — same domain, so this
matches what the maintainer already saw.
The pinning test
Instead of standing up full Bumper, I ran a minimal TLS server with a
self-signed cert (CN =
jmq-ngiot-eu.dc.robotww.ecouser.net) and pointedonly that one domain at it via DNS.
state table.
after ServerHello.
certificate) three times in a row on reboot.
Conclusion: this firmware pins certificates. The
ca.robotww.ecouser.netlookup on every boot supports that — the bot appears to validate against
Ecovacs' own CA rather than the system/user trust store.
Question
Has anyone unpinned a T90 Pro Omni (or any recent
robotww/ngiot bot) viaUART yet? The bot-unpinning guide is written for the T10 PLUS and I can't
find any teardown/UART reference for this model.
All reactions