search

bmartin5692 / bumper

A standalone and self-hosted implementation of the central server used by Ecovacs vacuum robots.
GNU General Public License v3.0
271 stars 48 forks source link

Deebot Neo 2.0 Plus not working with Bumper #145

Open Sam01101101 opened 1 week ago

Sam01101101 commented 1 week ago

A previous model of Deebot was working fine on Bumper, once replaced with a newer model due to failure https://www.ecovacs.com/au/deebot-robotic-vacuum-cleaner/deebot-neo-2-plus the robot does not make connection to Bumper.

Does anyone know if bumper is compatible with newer model of Ecovacs like DEEBOT NEO 2.0 PLUS

pmquanphucthinh commented 1 week ago

i think you should capture the packet from the bot to the network so that everyone will see and make a change for it

Sam01101101 commented 1 week ago

Deebot Neo 2.0 Packet Capture.pcapng.zip I'm not entirely sure what i'm looking at here, but here's a few mins of Wireshark capture.

The DNS xx.20.25 is my local DNS server which is doing the rewrites to my instance of bumper on xx.20.13

pmquanphucthinh commented 1 week ago

Hey, as i can see, this is only the capture from 10.14.20.13, i think newer bots use different endpoint url (Example as mine is ecouser.cn) so that the DNS server can't detect and reroute it. In my opinion, you should redirect all network traffic from the vacuum robot to the device running Wireshark. Then, power off and on the robot to see which domain it is sending to. After that, adjust bumper accordingly

Sam01101101 commented 1 week ago

Hey, thanks for looking into this. This capture is actually from the access point, its all traffic out of the bot.

I'll give that ago, instead of DNS rewrites, i'll forward all traffic to the server running bumper.

Sam01101101 commented 1 week ago

Please have a look at the above, from what i can see all the traffic out of the bot goes to the bumper server, and I’ve also included bumpers’ responses. Deebot Neo 2.0 Packet Capture_2.pcapng.zip

let me know if you need any more data.