Issue with Neato botvac zones

Third party integrations
61

Alright so minor set back… The other day without warning I am now getting the dreaded Floor plan error that everyone has been complaining about since the dang thing came out. I THINK I actually fixed that issue for good if anyone is interested and wants to read below… The side issue I am having again dshokouhi, is with the Neato app I can run a zone without and issue. But when I try to have Home assistant run the zone I get the same error I was having earlier. I have tired rebooting the vac, uninstalling the integration, rebooting HA, and reinstalling. And same issue. Neato app will trigger the vacuum but my script in HA won’t. Here is my script that you sent me last time. (Which WAS working btw)

entity_id: vacuum.name
zone: Kitchen

Possibly floor plan error Fix
Please someone else try it, because it worked for me. That I know of there is no “true” way to hard reset the vacuum. Your just able to reboot (By holding the power) and put the vacuum into WiFi paring mode (by holding the right number and power button)…Even when you log out, uninstall the app, reboot your phone, reinstall, sign back in, put the device into WiFi pairing mode, and set it back up the old map will instantly be there.

That got me thinking, I’ve “re-mapped” my space multiple times in multiple different houses and always renamed my map “Home” or “Town Home” so I wonder if it’s somehow holding onto those old maps internally or even by poor data management in the cloud. Then when you go to start your vacuum it doesn’t know which “home” to actually start running because there is all of these old maps named “home”. Thus the error everyone is having…

Today after getting 3 of these errors today I renamed my whole “map” something unique that I have never used before (SC Home), pressed start and the vacuum took right off with no issues. Thought it was too good to be true, when it was done cleaning that zone I immediately had it start another zone and it went and cleaned it without an issue.

Thoughts?

62

HI,

would be nice to have a list of zones from the API; can be stored in a input_select.
What you think ?

Based on json output above should be doable.

Simone

63

we tried to initially store them as attributes but they asked us not to do that, you are better off creating the input select by yourself since you know you have to use the app to create the zones anyways :slight_smile:

64

Edit: so looks like it’s not working from the app either. We had to move the base a few centimetres…apparently that might be enough to throw it off…if so I’m a bit dissapointed

Hi. First thanks for all the work on the neato integration!
I’m having a similar issue. We just got our D7 and when I try calling the service with a zone name the vacuum just moves out of the dock, raises an error about floor plan and goes back to the dock.
I can’t see anything in the HA logs even with debug enabled for neato which is something I find odd in general
I’m running 0.114.4 on a Pi4.

Sample Call:

entity_id: vacuum.nate
zone: Hallway

I ran the python script I found above and got the following info:

Boundary for plan1 {'version': 1, 'reqId': '1', 'result': 'ok', 'data': {'boundaries': [{'id': '70299035-ee7f-44b5-a8a5-36c4b83a0d3e', 'type': 'polygon', 'vertices': [[0.1672, 0.4883], [0.4633, 0.4883], [0.4633, 0.7564], [0.1672, 0.7564]], 'name': 'Bedroom', 'color': '#C46262', 'enabled': True}, {'id': 'ec6205b5-0525-4853-b112-29d11d758163', 'type': 'polygon', 'vertices': [[0.4922, 0.5715], [0.7616, 0.5715], [0.7616, 0.7604], [0.4922, 0.7604]], 'name': "Kid's bedroom", 'color': '#618BAF', 'enabled': True}, {'id': '4560d955-aef4-4b91-a5e9-79fe05bf6ee0', 'type': 'polygon', 'vertices': [[0.5586, 0.3171], [0.7797, 0.3171], [0.7797, 0.4739], [0.5586, 0.4739]], 'name': 'Kitchen', 'color': '#FFC974', 'enabled': True}, {'id': '0f19d0bb-1516-449f-82f6-bd75d9b55741', 'type': 'polygon', 'vertices': [[0.1045, 0.1794], [0.4613, 0.1794], [0.4613, 0.4833], [0.1045, 0.4833]], 'name': 'Living room', 'color': '#5B7BA5', 'enabled': True}, {'id': '1ccb0dae-5be4-4854-befa-885557c585c5', 'type': 'polygon', 'vertices': [[0.4581, 0.2078], [0.5697, 0.2078], [0.5697, 0.5645], [0.4581, 0.5645]], 'name': 'Hallway', 'color': '#E2D071', 'enabled': True}, {'id': 'ab7d7fc1-960e-4edc-904d-d25cdac3d979', 'type': 'polygon', 'vertices': [[0.5693, 0.5031], [0.7217, 0.5031], [0.7217, 0.5646], [0.5693, 0.5646]], 'name': 'Bathroom', 'color': '#E49770', 'enabled': True}, {'id': '2621aa21-264b-46af-80b0-21303d9fc9bc', 'type': 'polyline', 'vertices': [[0.423, 0.633], [0.4082, 0.6868]], 'name': '', 'color': '#000000', 'enabled': True}]}}
65

If you make any environmental changes to the dock or immediate cleaning area then you need to create a new map. The neato vacuums are very sensitive to changes. There is nothing we can do if the vacuum decides the map is not right, we just spit back whatever error neato sends to us.

66

Hi! Very similar issue to one of OPs: I let my Botvac D7 map the apartment (one floor, only plan in the machine), defined the zones and built a simple script to make the robot clean some of the in the sequence (area around cat toilets, actually :cat2:). Worked like a charm.
Now everyone with a Botvac knows that the maps need to be rebuilt from time to time given their pickiness with area around the base. Did that today. Deleted previous one, mapped new, gave it unique name, defined same zones, named them the same. And boom, when I run the script, all I get is a wrong floor error. Zone clean in the app works.
What’s the proper debug sequence? I’d like to leave re-mapping to the very end because of said cats :slight_smile:

67

turn on debug logging for the integration.

homeassistant.components.neato: debug and look at the logs that generate once per minute…you should see the map and zones you created in the logs.

1 Like
68

K, did that, got it. Stupid question, what does it tell me? I can see I have one saved map + raw map. And I can see the list of zones alright.

OK, I take that back: after the list of zones, I can see bunch of zones with empty names, is that normal? Certainly nothing I created intentionally. Should I submit part of the log here?

69

If you restart HA do you still see the issue? If you see the zones you expect to see them the service call should work.

70

The situation remains the same after restart. I see the zones I expected plus like five more with empty names.

71

im referring to the service call itself and not the logs

72

Sorry I never came back to this. Finally got to do some testing and everything seems to be working. Heck if I know why, I didn’t do any changes.