Repository navigation
Deebot N20 Plus (buom7k) works with Bumper 0.4.1, needs CERT_KEY_TYPE=rsa #290
MaximallyMaximum
started this conversation in
Show and tell
Replies: 0 comments
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.
Uh oh!
There was an error while loading. Please reload this page.
Tested model: Deebot N20 Plus (class
buom7k)Protocol: MQTT
Firmware:
Ecovacs Home app: , patched with
scripts/create-unpinned-app.shfrom v0.4.1Bumper: 0.4.1 in Docker, with the nginx proxy from the compose file
It works, with one required change:
CERT_KEY_TYPE=rsa.With the default EC certificates, the robot connects every 5 seconds (port 443, no SNI, routed to 8883), and every handshake fails with:
After setting
CERT_KEY_TYPE=rsaand deleting the existing certificates so Bumper regenerated them, the robot connected right away and shows under Bots as connected via MQTT. No certificate unpinning on the robot was needed.Home Assistant's Ecovacs integration in self-hosted mode controls it through Bumper as well.
Side note: on a Docker host with IPv6 enabled on bridge networks, nginx sometimes tried Bumper's IPv6 address and got "connection refused", since Bumper listens on 0.0.0.0. Setting
enable_ipv6: falseon the stack's network fixed that.What doesn't work (main image)
Adding the robot again in the patched app fails: the list of models that support discovery is empty, and the app shows the error
(,-9002). The first pairing on 0.4.1 went through, but the user record lists a different device ID than the robot's DID.Thanks for maintaining Bumper!
All reactions