Open schwatter opened 4 years ago
I must revoke my findings. The port 1883 ist only visible by sniffing the app. So a port scan on the robot just show port 8888.
Hi schwatter,
can you confirm Deebot950 with 1.8.2 firmware doesn't work with bumper?
Yep, I have issues connecting it as well.
I have the same problem and found out, that my 950 is connecting to the URL mq-ww.ecouser.net
on port 443. Bumper is listening for MQTT on port 8883.
As workaround I redirected the traffic from the bot to 8883 (MQTT port) with my firewall and everything is working again.
Are you sure that bumper is listening on 8886? When i open init.py i found in the past
mqtt_listen_port = 8883
conf1_listen_port = 443
conf2_listen_port = 8007
xmpp_listen_port = 5223
Can you please test it with change the port in init.py
Are you sure that bumper is listening on 8886? When i open init.py i found in the past
mqtt_listen_port = 8883 conf1_listen_port = 443 conf2_listen_port = 8007 xmpp_listen_port = 5223
Can you please test it with change the port in init.py
Sorry I meant 8883
Thx :)
running again when edit the init.py to new port.
mqtt_listen_port = 443
conf1_listen_port = 443
conf2_listen_port = 8007
xmpp_listen_port = 5223
Thx :)
running again when edit the init.py to new port.
mqtt_listen_port = 443 conf1_listen_port = 443 conf2_listen_port = 8007 xmpp_listen_port = 5223
Only for completeness, you can't run two services on the same port. You probably will require a reverse proxy. See an example in PR #116
I have no more access to the bot after i updated to the lastest fwVer, 1.8.2. When i sniff the traffic from app, it looks like they shutdown mqttport 8883. I only see mqttport 1883. So then i changed the port in bumper init.py to 1883 without luck.
Infos about server i found out.
puplic.itls.eu-central-1.aliyuncs.com / 47.61.64.194:1883 securemode=2, signmethod=hmacsha1,ext=1