Has anyone gotten this Robot Vacuum to work with either SmartThings or Alexa?
I have 2 of them. I haven’t tried too hard yet. They don’t seem to have posted an api. Decent vacuum for the price.
There is a Alexa skill for the most expensive Ecovac, I installed it and as soon as my vac is delivered I will test it.
I’m not really interested in an Alexa skill. What I really want is for them to run when everyone leaves.
I would love the same thing but have no idea how to create a way of doing it.
I have two myself (dr98) and running into the api issue.
What i found sofar is that the app communicates with a server in China that controls the bots. It uses the xmpp protocol with tls encryption (which is why i didn’t get far yet). The robot itself has a listening tcp port 8111, but i haven’t been able to trace yet what it does.
I’m still tracing the network on what it does, but with all the encryption it’s quite annoying
Maybe some others would like to join in and work on defining the api via reverse engineering?
Albert, thanks for the work, I am not a programmer, so I am of no help other than to test. Let me know if you come up with something.
This is on sale for $160 with code indicated here…
That is a great deal to bad I have robots now.
Just an update on the quest for an API.
I have been able to decode the app to server connection and found that;
- it connects to web services to get the userid from the email address
- it logs on via the web service to get a login token that it later uses in the xmpp stream (the controlling part)
- the xmpp stream has an interesting SASL key, but I found out how it’s build up
- there’s a stream of data/commands in XMPP in request/response type and some that come out-of-band.
in short; It WORKS!. I’ve been able to make a small java app that connects to the server and can send the ‘auto clean’ command and ‘return to charger’.
more commands exist, but I haven’t had the time to decode those and at the moment having some trouble with the out-of-band messages.
anyone willing to help out… you’re welcome to, I can share the findings/code so far…
thanks for the offer. I’ll draft up what I have solar (5 json calls over https) and the findings.
right now there’s a few things I’m still puzzled by, the realm (resource) it connects to seems fixed but I have no idea where it comes from and the bots are an xmpp recipient with an idea that I can’t seem to find where it comes from (it’s fixed, but no idea on how it’s build up).
anyway, I think mail would work best; firstname.lastname@example.org
couldn’t post the debugger output of xmpp… site complains about links
Please keep me informed of the progress. Thanks.
Another update, quite some commands are now found and the code is working now with the async xmpp responses.
Even better, i have received information on the usb port from our local support. It is used for the firmware upgrades, which means it can be done by customers themselves, provided they have the firmware files.
(For dr9x, the latest firmware is 0.6.19 which i also received).
Now to see if there’s more to be found on firmware revisions and how to obtain them the correct way.
Is this something us non programers will be able to do?
If you know how tonhandle a usb stick, you’ll be ok.
It’s pretty much a trick with keycombo to get the device act as usb share on a pc, copy the firmware file and wait for it to process.
I’ll try the process later on when i have some time.
Can it be processed on a Mac?
I should think so, actually hope so as I work on Mac as well. I don’t figure it will be a problem, the vacuum will present itself as drive over usb (as with an usbstick).
but I’ll try anyway when I have a bit of time to play with it.
That sounds great. Keep me posted.