-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistent maps, virtual walls, and forbidden zones #15
Comments
I'm also seeing:
It is also possible that persistent maps are stored in the mii cloud and downloaded if requested. |
3.3.9_001633 Lab mode ON: req: Lab mode OFF: req: Software barrier: req: No-go zone: req: |
Thanks for sharing these, @FeatureExpert!! |
It looks like these features are yet to be ported to the Gen 1 Firmware. But given the similarities I would hope to see it soon |
Completely untested for now, works only on gen2 and requires a fairly recent firmware version supporting no-go zones and barriers. Based on information from marcelrv/XiaomiRobotVacuumProtocol#15
I'm not sure these numbers. Some kind of coordinates for sure, but I do not know yet how to calculate them correctly. My image with the map is 900x767, so the coordinates does not match the size. But maybe I generate map incorrectly... |
Hi, This may be a stupid question but how can you get the list of the commands ? Thanks |
@FeatureExpert I guess they would be like the |
You are probably right. So we can set coords as follows counting from bottom left corner and where the dock is at [25500, 25500]:
or
or even barrier and no-go zone in one command:
|
Seems the first argument of the array is not an id, but rather a type: 0 = zone, 1 = barrier. |
@JensBuchta nice find! |
Completely untested for now, works only on gen2 and requires a fairly recent firmware version supporting no-go zones and barriers. Based on information from marcelrv/XiaomiRobotVacuumProtocol#15
* Add some map editing commands Completely untested for now, works only on gen2 and requires a fairly recent firmware version supporting no-go zones and barriers. Based on information from marcelrv/XiaomiRobotVacuumProtocol#15 * Add parameters to no-go zone, fix type handling
sorry for my stupid question : how are no-go zones and barriers removed or how can i see these zones or barriers ? |
Calling |
It looks like it is a slot, it seems you can switch between 0 and 1.
|
|
So how do you remove virtual walls and no-go zones? |
Any news on this, did someone figure out how to delete virtual walls or no-go zones, Maybe the original app doesn't delete single entities, but resets all and re-builds the other ones. |
If you want to remove all walls and zones:
|
If you want to remove one part, you parse the current map file, remove the part you don't want and call save_map with the params you want. |
This is nothing you can simply set in the request, nor is there an obvious way to avoid it. Besides that it offers the location of the various objects & tracks etc. You might be able to create a client that does some smart things to the bitmap, to determine if it is part of a larger(largest) cloud of pixels or something, but that would be totally client dependent. |
Hello,
I came upon the following commands on a gen2 vacuum with v001780 firmware:
mirobo raw-command set_lab_status 1
allows the robot to "remember" maps after a reboot.The
start_edit_map
,end_edit_map
, andsave_map
appear to be related to the virtual walls and forbidden zones functionality. I believe a JSON is expected as parameters for the function.I do not have the xiaomi app, and I was not able to figure out the format of these parameters.
Note that calling
start_edit_map
,end_edit_map
, orsave_map
without first enabling the lab_status will result in the following response:The Lab Status is disable
.Not sure what the
use_new_map
,use_old_map
, andget_persist_map
do.The text was updated successfully, but these errors were encountered: