Error when using Sucks #51
Labels
No labels
bug
dependencies
duplicate
enhancement
good first issue
help wanted
invalid
question
waiting for fix validation
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: mia/bumper#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
Trying to get a new Deebot Ozmo 950 working with bumper and sucks. I'm trying to get bump working with sucks and I'm getting the following error:
Expected behavior
Sucks works with bumper
Desktop (please complete the following information):
Vacuum (please complete the following information):
Additional context
While this model isn't supported I'm trying to see what all we need to do to get it working with bumper. I can see a new domain in the error above (
ecorobot.net). Maybe we also need to add this to the DNS list?I was able to get @bmartin5692 's fork of sucks talking to bumper but i'm not getting a response from my bot.
Some logs that seem pertinent:
@bmartin5692 any idea where I can start to try to fix this? I'm hoping to get this working with bumper or I'll have to return it.
I’ll see if I can take a look this weekend. It may just be a quick model update for the “EcoVacsHomeProducts” to support newer bot models -
1fdbb055df/bumper/models.py (L88)I'd appreciate it. thank you.
I just pushed an update that includes the latest mapping. Update and lets see if that works before I dig too deep into this.
I'll test this first thing tomorrow and report back. Thank you.
@bmartin5692 so we've made progress! I'm now able to see the robot on the Ecovacs Home app but still can't communicate with it. Once i click on the bot I get an error on the app
Information acquisition timeout. Please exit and try again. Here are the logs from bumper: https://pastebin.com/raw/z8vRE4x3It looks like the bot is sending back a
500error for all messages:The 500 is a timeout from waiting for a response. Does the bot show online? If you hit the website for Bumper, what does it show? (https://bumperip) should display some basic status of the services and connected clients/bots.
Edit: Update with json once Ecovacs Home app is launched.
Yea it shows online. Here's the json from the bumper website:
@bmartin5692 just FYI, i've verified against both sucks and Ecovacs Home app and both result in the same thing as reported above.
Hi @uchagani -
Do you see any bot activity in the logs? The snippets you've shared so far only show server/app communications. What is interesting is the status json above shows your new OZMO 950 model using MQTT, but the OZMO bots that I've seen in the wild thus far have used XMPP for communication.
Could you clear the logs you have then try:
If possible zip/send all the logs in the logs folder? If I can't figure out how it is communicating from that, then you may have to sniff the bot communication so we can get an idea of what it is doing.
@bmartin5692 here are clean logs of the steps you listed above. I can see the bot
onlinein the Ecocavs Home app but when i click on the bot to do any operations, i get errorInformation acquisition timeout. Please exit and try againI really appreciate you looking into this. thanks again!
Hi @bmartin5692 were the logs helpful at all? Anything else I can help with?
Thanks for pulling those together, I just got a chance to review.
It looks like your bot does use MQTT and checking version is successful. However, the other commands issued to it don't get a response for some reason. There isn't enough details in the logs to determine why. It is possible your bot is using a different topic or method for communication that we haven't seen before.
I'll have to look around to see if there is some additional logging I could do in Bumper to get a better dump of the communications, otherwise this may require you to man in the middle the communications yourself.
My system is currently in a broken state due to a RPi SD card failure and I haven't had time to fix it yet, so I can't do much testing at the moment. It may take me a bit to get more details, if you are feeling up for the challenge check out man in the middling the communications with a hotspot on Kali linux.
Once I get my system working, I can try to build some additional logging to hopefully cut out that piece.
@bmartin5692 cool I'll look into this. To be clear, should I be monitoring traffic between the phone and the router, the bot and the router, or the phone and the bot? I'm guessing the latter but I came up empty when I tried it really quickly on my Ubuntu box. I was able to get some data between my phone and the router but it was just registration info and something about flash player.
Ideally both. Seeing both sides of the communication is extremely helpful, but key will be the traffic to/from the bot.
@bmartin5692 I was able to capture the traffic. Is there an email I can reach you at to send you some of these request/response flows or are you on discord?
@uchagani - I just started a gitter community for this - https://gitter.im/ecovacs-bumper
Send me a private message there.
@bmartin5692 Awesome, sent the info to you on gitter. thanks!
Similar problem with my OZMO Slim10(firmware 1.1.4) in Germany.
bumper works in general fine.(Thanks a lot) I'm able to receive mqtt-messages of the bot with the home-app 1.2.0 and other mqtt-clients. But issued commands are not successful. The bot "ignores" them. No reaction, no error messages.
Currently I'm not able to capture traffic between the bot and ecovacs-servers. Traffic between bot & bumper & home-app & otherMqttCliens shows nothing helpful.
Any further ideas about maybe different topic than iot/p2p/command..... ?
Can you try the Ozmo950 branch with debug enabled? I pushed it yesterday, but it enables additional MQTT logging in the mqttserver.log and will hopefully shed some light on what topics these bots subscribe to and how they are communicating.
I expected no new informations since I already had a client subscribed to '#':
still no reaction on commands/topic iot/p2p.....
The only new information is that the bot subscribes to the topic structure bumper sends:
Not clear about iot/ota... topic
command send with my mqtt-client
Edit: The only functioning command seems to be
Only difference I can see is the "j" instead of "x" in topic. Change in command sent by my mqtt-client doesn't help for other commands.
Do you see anything that could help ? Any further informations from logging needed ?
Are you able to use the official Ecovacs app with Bumper? It would be useful to see what the app is sending for commands.
I opened a new issue in the Sucks project #80 regarding what I saw with @uchagani's output. You are correct the Ozmo950 and your Ozmo Slim10 seem to be using a new communication protocol of all json commands instead of the xml commands of previous bots.
@KoelnSolar - Can you pull the latest Ozmo950 branch and report if it works? @uchagani was able to test last night with success.
Unfortunately it changed nothing. ;-(
With your explanation of x and j I figured out following things:
iot/p2p/GetWKVer/helper1/bumper/helper1/+/+/+/q/+/j {'td': 'GETWKVer'}
iot/p2p/Clean/helper1/bumper/helper1/+/+/+/q/+/x <ctl/> (e.g.)
since I received iot/atr/GetIOTConnStatus/+/+/+/j {'td': ....} I tried to publish iot/p2p/GetIOTConnStatus/helper1/bumper/helper1/+/+/+/q/+/j {'td': 'Blabla'} and the bot answered with iot/p2p/GetIOTConnStatus/+/+/+/helper1/bumper/helper1/p/+/j {'td': '....'}
But with other commands I tried it didn't work. Any further idea ?
Edit: The bot publishs topics e.g. iot/atr/ChargeState/+/+/+/x
It sounds like your bot communicates similar to my 901. I'm surprised it doesn't work. I'm a bit confused about how you are using this and issuing commands though. Are you using the Ecovacs app or something else to try to control the bot?
bumper Ozmo950-branch on Rpi2(tcpdump installed)
Ecovacs Home App V1.2.1 in Android-Emulation-Environment on Win-Tablet. Android 5.1.1
2 additional mqtt-clients. mqtt.fx on Win-PC(Wireshark installed) mainly to monitor topics. subscription to #. The other client is part of the smart-home-system FHEM(Rpi3) with which I receive already the messages published by bumper.
Using the app and ecovacs-servers it works fine.
In my bumper environment , I'm able to analyze traffic. But no idea to catch and analyze traffic if using ecovacs-servers. Only thing are the used servers(captured by pi-hole).
eco-de-api.ecovacs.com
com.ecovacs.ecosphere.International
bigdata-international.ecovacs.com
msg-ww.ecouser.net
recommender.ecovacs.com
gl-de-openapi.ecovacs.com
msg-ww.ecouser.net
portal-ww.ecouser.net
bigdata-europe.ecovacs.com
gl-de-api.ecovacs.com
mq-ww.ecouser.net
com.eco.global.app
Can you get a hold of an android iOS device? If so, I can show you how to
capture traffic via mitmproxy. My guess is that the layers of emulations
and such are the problem here.
On Thu, Oct 3, 2019 at 9:52 AM KoelnSolar notifications@github.com wrote:
Would be an option, but I can't. ;-(
No, I don't think so since the app is ok with ecovacs-servers, but with bumper commands are issued but the bot doesn't answer. Only the 2 json-commands mentioned above give a reply.
In order to use the app with bumper you need to install the certificates
and I'm wondering if that is what is causing the problem.
On Thu, Oct 3, 2019 at 11:05 AM KoelnSolar notifications@github.com wrote:
Maybe. But isn't the reception of bot's status publishing and reply on json-commands a contra indicator ? I've only installed ca.cert.
Edit: found a 3d json command: GetNetInfo
I've installed now Wireshark on the Win-Tablet. These are the servers the Home-App communicates with:
portal-ww.ecouser.net, msg-ww.ecouser.net [47.91.67.63] port: 443, 5223 gl-de-openapi.ecovacs.com [47.91.65.136] port: 443 bigdata-europe.ecovacs.com [47.91.65.122] port: 443Responses seem to be received from
mq-ww.ecouser.net [47.254.143.26] port: 8883Is it possible with the information of Wireshark to connect as a client(mqtt.fx)to the mqtt-Server and to emulate the bot to receive the decrypted mqtt-commands ?
May I'm able to decrypt the Wireshark captures ?
Other ideas to analyze my problem ?
Edit: captured now a beep-comand out of the app:
{"td":"q", "toId":"myBot", "toType":"02uwxm", "toRes":"Uq7d", "cmdName":"PlaySound", "payloadType":"x", "auth":{"with":"users","userid":"myUserid","realm":"ecouser.net", "token":"myToken","resource":"GLB19396e86"}, "payload":"<ctl sid='0'\/>"}Is it just the small difference in the payload ? (receiving <ctl/> issued by bumper)
Edit2: The GetNetInfo in Json:
{"td":"q","toId":"myBot","toType":"02uwxm","toRes":"Uq7d","cmdName":"GetNetInfo", "payloadType":"j","auth":"with":"users","userid":"myUserid","realm":"ecouser.net","token":"myToken","resource":"GLB19396e86"}, "payload":{"td":"GetNetInfo"}}No ideas ?
I currently updated the App to a new version, but the situation ist still the same.
The App communicates in json for GetNetInfo, GetWKVer and GetIOTConnStatus, e.g.
Topic: iot/p2p/GetWKVer/helper1/bumper/helper1/myBot/02uwxm/Uq7d/q/BCnGPd/j - Message: {"td": "GetWKVer"}answer
Topic: iot/p2p/GetWKVer/myBot/02uwxm/Uq7d/helper1/bumper/helper1/p/BCnGPd/j - Message: {"ret":"ok","ver":"0.3.5e"}All other commands do not use json, e.g.
Topic: iot/p2p/GetBatteryInfo/helper1/bumper/helper1/myBot/02uwxm/Uq7d/q/xyz123/x - Message: <ctl/>All these commands are not answered by the bot.
Broadcasts by the bot are ALL received with e.g.
Topic: iot/atr/BatteryInfo/myBot/02uwxm/Uq7d/x - Message: <ctl td='BatteryInfo'><battery power='112'/></ctl>I'm still confused about that behaviour. What might be the reason ?
The App works fine if I use it without bumper. But I've no idea how to catch the issued commands. Any suggestions appreciated !
@uchagani: can you please post your json-commands out of the helperbot-log to give me a hint about the syntax to try to issue them with my MQTT-tool.
@KoelnSolar -
Per #61 -
Could you try with the extend-confserver-logging branch with --debug enabled? This should give me more detailed logs on what is happening in your setup. Please send me the logs via gitter (https://gitter.im/ecovacs-bumper) for review when you have them.
@uchagani Please can you confirm sucks and bumper work for the Deebor Ozmo 950 using @bmartin5692 's branch? Looking to buy it and want to make sure I can integrate it into homeassistant.
Thanks!
I can confirm that Bumper works but sucks does not. It needs to be updated
to work.
On Sat, Dec 21, 2019 at 12:37 PM gbenrus25 notifications@github.com wrote:
@uchagani Do you have an idea what kind of changes to sucks would be necessary? Just some small additions of certain commands or larger changes?
Its quite a bit of work - I just did some quick changes for basic testing here:
https://github.com/bmartin5692/sucks/tree/add-jsonSupport
Right now this will only work using custom commands, sucks would need many changes to do this automatically for the various bot types.
But for example using this branch you could issues a command that is in json like so:
vacbot.run(VacBotCommand("GetWKVer", {}), isjson=True)My bot only has this one json command, so maybe someone with a 950 could take this and run with it to extend it further.
I made a working prototype for Ozmo 950 of library and hassio component
https://github.com/And3rsL/Deebot-for-hassio
I cant test for other robots because i doesnt have it
feel free to get/integrate everything