Clean logs

Endpoints

You can receive clean logs by calling two different endpoints of Ecovacs API servers:

short	constant	endpoint	device type	response type
IOT_API	IOTDEVMANAGERAPI	iot/devmanager.do	XMPP, MQTT	XML
LOG_API	LGLOGAPI	lg/log.do	MQTT	JSON

Commands

name	endpoints	attributes	maps
GetCleanLogs	IOT_API	count
GetCleanLogs	LOG_API		x

Attributes

key	IOT_API	LOG_API	type	format
timestamp	s	ts	integer	unix timestamp
lastTime	l	last	integer	number of seconds
squareMeters	a	area	integer	number of square meters

Optional attributes

key	IOT_API	LOG_API	type	format
id	*	id	string	did@somenumber@resource
imageUrl	-	imageUrl	string	URL
type	-	type	string	clean mode
trigger	t	-	string	see below
stopReason	f	stopReason	integer	see below
totalTimeString	-	-	string	hourh minutesm secondss
date	-	-	string	date string

*) generated

Not in use

key	IOT_API	LOG_API	type	format
-	-	aiavoid	boolean (?)
-	-	aitypes	array

stopReason

LOG_API (Ozmo 950 only)

stopReason	traffic light color in app	text in app
1	green	Cleaning complete
2	green	Cleaning has been ended manually
3	orange	Cleaning has been ended

IOT_API

value	stop reason (Ecovacs)	stop reason (library)
s	CLEAN_SUCCESSFUL	clean_successful
r	BATTERY_LOW	battery_low
a	STOPPED_BY_APP	stopped_by_app
i	STOPPED_BY_IR	stopped_by_remote_control
b	STOPPED_BY_BUTTON	stopped_by_button
w	STOPPED_BY_WARNING	stopped_by_warning
f	STOPPED_BY_NO_DISTURB	stopped_by_no_disturb
m	STOPPED_BY_CLEARMAP	stopped_by_clearmap
n	STOPPED_BY_NO_PATH	stopped_by_no_path
u	STOPPED_BY_NOT_IN_MAP	stopped_by_not_in_map
v	STOPPED_BY_VIRTUAL_WALL	stopped_by_virtual_wall
wc	WIRE_CHARGING	-
aq	STOPPED_BY_AIR_SPOT	-
aqd	STOPPED_BY_AIR_AUTO	-

Trigger

IOT_API

value	trigger (Ecovacs)	trigger (library)
a	APP	app
i	IR	remote_control
b	BUTTON	button
s	SCHEDULE	schedule
p	SCHEDULE_FROM_APP	schedule_from_app
q	SCHEDULE_FROM_DEVICE	schedule_from_device
bp	PAUSE_FROM_BREAK	pause_from_break
dnd	PAUSE_FROM_DISTURB	pause_from_disturb
e	ERROR	error