You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What vacuum are you using? Roborock S8 MaxV Ultra With Auto-Refill Dock (plumbed in)
Describe the bug
Within the app it is possible to override the floor type recognition and force the robot to see zones as a specific floor type. One of the methods of doing this is to delete an auto-recognized area of carpet, which will then allow the user to set a given zone where the robot should never re-recognize the floor as carpet. I use this feature in two rooms of my house where the vinyl flooring mis-triggers the robot to think the floor is carpet and therefore raises the mopping pad.
Unfortunately, when these override areas are configured in the app, they show up as red no-go areas within the map generated by this integration.
I have attached screenshots of both the app views (main map page, and editing of floor types - you can see the red boxes for "never recognize carpet here" in the "carpet" editing page) and the integration generated map which shows the "never recognize carpet" areas the same way as no-go-zones.
The text was updated successfully, but these errors were encountered:
Version of the custom_component: 1.0.13
What vacuum are you using? Roborock S8 MaxV Ultra With Auto-Refill Dock (plumbed in)
Describe the bug
Within the app it is possible to override the floor type recognition and force the robot to see zones as a specific floor type. One of the methods of doing this is to delete an auto-recognized area of carpet, which will then allow the user to set a given zone where the robot should never re-recognize the floor as carpet. I use this feature in two rooms of my house where the vinyl flooring mis-triggers the robot to think the floor is carpet and therefore raises the mopping pad.
Unfortunately, when these override areas are configured in the app, they show up as red no-go areas within the map generated by this integration.
I have attached screenshots of both the app views (main map page, and editing of floor types - you can see the red boxes for "never recognize carpet here" in the "carpet" editing page) and the integration generated map which shows the "never recognize carpet" areas the same way as no-go-zones.
The text was updated successfully, but these errors were encountered: