New Neato Integration Installation Guide (OAuth2 for HA version 2021.1)

Community Guides
50

Having issues as well with Neato integration. When I follow the guide https://www.home-assistant.io/integrations/neato/ two things happen:

  • when I try to add the integration and I click the blue button to open the external site I get an Internal server error window and the integration seems to be created with two configuration.yaml references (?)
  • when I try to add the integration and wait without clicking the blue button the process ‘finishes’ and the integration seems to be created with one configuration.yaml reference (?)

I removed and readded the Home Assistant app in Neato Dev website, I use my Nabu Casa https url to setup the integration and made sure no former references to Neato vacuums are present in Home Assistant.

51

Tried one more time and this is the response in HA log:

Logger: pybotvac.robot
Source: /usr/local/lib/python3.8/site-packages/pybotvac/robot.py:190
First occurred: 5:53:22 PM (4 occurrences)
Last logged: 5:53:25 PM

Invalid response from https://nucleo.neatocloud.com/vendors/neato/robots/XXXXXXXX-XXXXXXXDXXXX/messages: required key not provided @ data[‘availableServices’]. Got: {‘version’: 1, ‘reqId’: ‘1’, ‘result’: ‘ko’, ‘data’: {}}

(I replaced my robot ID with X’s)

52

try to reset and reconnect the botvac using the neato app to fix the response from the API.

1 Like
53

Yup, it was a bit drastic but it indeed solved my issue. Thanks!

1 Like
54

Hi. I did have this integration working for my D4, but fiddled too much and ended up removing mobile app, removing stale machine at Neato, removed HA integration, and reinstalled everything from scratch, with fresh clientid/secret from the developer site. Since then:

  • the robot works from Google Home, so it’s paired with my wifi, but…
  • app won’t pair, yet I get notifications and new maps after cleaning (v weird)
  • reinstalling the HA integration gets me:

Logger: homeassistant.config_entries
Source: components/neato/init.py:118
First occurred: 10:43:29 (1 occurrences)
Last logged: 10:43:29

Error setting up entry Configuration.yaml for neato

… and yes, I use nabu casa, and, as I say, it was working before.

Any help appreciated!

55

Hello,
is there currently an issue with duckdns? I had the integration installed (with OAuth already), everything worked fine till like yesterday. Without any changes or updates, my BotVac D7 is suddenly unavailable (everything fine in the app). I deleted the integration and now I want to log in to HASS using my external IP through DuckDNS to reinstall the integration and I keep on getting errors, can’t even get to the log-in screen.
Or is that some known issue?

56

Hello,

I need some help:
I managed to make my home-assistance instance accessible via https through duckdns: If I put https://raspiabc.duck.dns:8123 (just an example) into my browser I see the HA login.

However, if I put https://raspiabc.duck.dns:8123/auth/external/callback into the Redirect URI on the Neato application the setup of the neato integration does not work. It says that my Redirect-URI request is not valid.

Any ideas?

regards,
Jan

57

are you using a valid SSL cert? can you access the link outside of your network?

58

I can connect form outside my network.

I followed this guide to make my HA accessible form outside my network https://www.splitbrain.org/blog/2017-08/10-homeassistant_duckdns_letsencrypt

But I think there is something wrong with the hook.sh. I wilk check this tonight.

regards,
Jan

59

hello, bought a new botvac D8
thet use a new MyNeato app? (android app & and also google home connection is different)
i can’t add this robot online to mine account.
so i can’t find this D8 in Home assistant…
is there a new way to connect?

60

What do you mean you can’t add it? Do you get an error? Going to need now info.

61

they use a new app:

on this app i can add mine robot, and this works fine

on the website ther is no option to add the D8
the develop website don’t sync with their new app i guess…
(i had a D7 in the past and that one worked)

neato
neato908×1015 109 KB

62

if its a new app and its not using the existing API then it may require a new integration…we’ll need to investigate more but will be difficult if none of us devs have a new botvac.

63

Yes, I’m having the same issue. I specifically bought a Neato vacuum because the Home Assistant support was so good. I didn’t realize the D8 wasn’t fully supported, though. I contacted support at the Developer Network, but they couldn’t provide any guidance. Actually, they said they’d take my information and follow up within an hour, but that was 2 days ago.

“Ok,i will have to escalate further to my colleagues to check where is the issue and i will send you an email with the details in the next hour”

Here’s hoping for an integration. I can help out however needed.

64

I just went through the same process. It looks like Neato created a totally separate app, user database, etc., but skipped the website and developer network. I’m trying to get an answer as to if it’s planned to open the dev network up to the new models. I’m fairly disappointed, it seems like they’ve crippled the new line in more ways than this…

1 Like
65

I have a case opened with Neato. Their customer support seems to be really responsive in communications. Let’s hope they can do something about support for the D8.

2 Likes
66

Same boat over here. Neato’s response to my “where’s the API” query on Twitter:

At the moment we’re not able offer any insight on API availability for the future. We apologize for this inconvenience and hope you enjoy your new D10!

@dshokouhi - would a packet capture help? I’d need some guidance on the workflows to trigger, but I’d be happy to do so if it would help the cause.

67

if it does not use the existing neato API then there is nothing we can do for the existing integration

68

Understood - was thinking it would help a ‘needed investigation for a new integration’.

69

That was a bit more specific than the answer I received, which was,

“Probably this feature it will be in a future update.”