RelocationState

RelocationState	Deebot Ozmo 950
ok	Bot knows its current position
start	Relocation was started, waiting for result
fail	Bot tried relocating but failed to get position
break	Bot tried relocating but was disturbed (e.g. by picking the bot up)
required	The last known position got invalid (e.g. by picking the bot up)

All states except "required" are directly retrieved from the API (onRelocationState, attribute "state", required is only set if last state was 'ok' and a position messsage is received which contains the attribute "invalid: 1".

Example response for valid position: data:{"deebotPos":{"x":88,"y":64,"a":104,"invalid":0}}

Example response for invalid position: data:{"deebotPos":{"x":88,"y":64,"a":104,"invalid":1}}

event retrieved from API for relocation state: data:{"mode":"manu","state":"ok","isHasMap":1}

onRelocationState	Deebot Ozmo 950
attribute	mode
value(s)/range	[appoint, dynamic, goCharging, lift, manu, recover, slot]
self-triggering	no
remark	only modes lift (relocating after lifting the bot and starting a clean) and manu (relocating from the app or iobroker) were seen
-	-
attribute	state
value(s)/range	[break, fail, ok, start]
self-triggering	no
remark