Cleaning logs aren't shown in EcoVacs Home app for some bots #58

New issue

Open

opened 2019-10-23 14:39:22 +02:00 by bmartin5692 · 2 comments

bmartin5692 commented

2019-10-23 14:39:22 +02:00

(Migrated from github.com)

In the case of the Ozmo950 it is uses a new json based protocol which utilizes a new format and headers for all commands sent.

The app makes a request for the following:
Method: POST
Path: /api/lg/log.do?u=tmpuser&av=1.2.1&cv=1.94.28&td=GetCleanLogs&t=i
Body: {'did': 'test_did', 'country': 'US', 'td': 'GetCleanLogs', 'auth': {'token': 'test_token', 'resource': 'app_resource', 'userid': 'tmpuser', 'with': 'users', 'realm': 'ecouser.net'}, 'resource': 'bot_resource'}

The proper command to send to the bot needs to be identified, then the results reviewed to determine if further modification is required for it to be displayed properly in the app.

The cleaning logs aren't returned for some bots in the EcoVacs Home app. So far this appears to be for newer bots (Ozmo950). A workaround was put in place for at least the D901 by capturing the request and sending a modified command to the bot. In the case of the Ozmo950 it is uses a new json based protocol which utilizes a new format and headers for all commands sent. The app makes a request for the following: Method: POST Path: /api/lg/log.do?u=tmpuser&av=1.2.1&cv=1.94.28&td=GetCleanLogs&t=i Body: `{'did': 'test_did', 'country': 'US', 'td': 'GetCleanLogs', 'auth': {'token': 'test_token', 'resource': 'app_resource', 'userid': 'tmpuser', 'with': 'users', 'realm': 'ecouser.net'}, 'resource': 'bot_resource'}` The proper command to send to the bot needs to be identified, then the results reviewed to determine if further modification is required for it to be displayed properly in the app.

boriswerner commented

2020-02-21 18:32:59 +01:00

(Migrated from github.com)

I also did quite some further testing on the API commands of the 950 and will provide my findings incl. more details on the exact and available commands with their parameters and responses soon.
What I am still missing is how to set/remove no-go areas and virtual walls with the API.
Do you also have found the request from the API for that kind of actions?

What can I provide you to also help improving the bumper support for 950?

@bmartin5692 thank you very much for that hint. I was able to send that command to the 950 and I am getting a response with the log timestamps and other information (I have to take a closer look) back, incl. imageURL. I am working with mrbungle64 on the enhancement of a JavaScript library based on sucks and putting together findings from other forks of sucks (https://github.com/mrbungle64/ecovacs-deebot.js) and we have quite some bots, incl. the 950 working already with basic commands but the logs were not tackled yet for the 950. I also did quite some further testing on the API commands of the 950 and will provide my findings incl. more details on the exact and available commands with their parameters and responses soon. What I am still missing is how to set/remove no-go areas and virtual walls with the API. Do you also have found the request from the API for that kind of actions? What can I provide you to also help improving the bumper support for 950?

edenhaus commented

2021-05-21 13:38:14 +02:00

(Migrated from github.com)

Unfortunately the cleaning logs are not stored on the robot but directly on the backend server.
I think ecovacs creates a new log, when the cleaning job is finished or aborted.
When we want to support this we need to add the possibility to create them

Unfortunately the cleaning logs are not stored on the robot but directly on the backend server. I think ecovacs creates a new log, when the cleaning job is finished or aborted. When we want to support this we need to add the possibility to create them

👍 1