Neato Integration no longer working

[patricknew78]

The problem

After updating core on 8/26/24 my neato botvac integration no longer works. "Failed Setup, will retry: 400, message="Bad Request", url='https://beehive.neatocloud.com/oauth2/token

What version of Home Assistant Core has the issue?

core-2024.8.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

neato botvac

Link to integration documentation on our website

https://www.home-assistant.io/integrations/neato

Diagnostics information

2024-08-26 06:15:21.362 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato_**** failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @santobert, mind taking a look at this issue as it has been labeled with an integration (neato) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of neato can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign neato Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

neato documentation neato source _{^{(message by IssueLinks)}}

[WebSpider]

I hope I am wrong, but https://beehive.neatocloud.com redirects to a page that says Neato has ceased selling operations..

[lotharbach]

I had this error, reloading the integration did not work. I deleted the integration and added it back, had to re-login and re-authorize in the neato developer page, then it worked just perfectly fine again!

@WebSpider it was announced I belive in April that Neato will shut down. Their parent company promised 5 more years of service, spare parts and cloud services. I think this is just a technical issue with existing auth tokens on their side.

[sondercoder]

Same issue, @lotharbach solution resolved it. Thanks!

[prom00]

I had the integration working before, but it stopped working.

At the moment apps.neatorobotics.com/...... is returning an HTTP ERROR 500

Seems like there's some issues at neato's side

[Thibuko]

Still error 500, can't add the integration back. Not a lot of thing we can do :-(

[PeterDuh]

Vorwerk, Neato's parent company stopped selling Neato and will shut down operations as I read in a tech blog. The parent company will maintain the cloud for 5 years but obviously they already shut some parts down as it looks like?

[WiredWonder]

Vorwerk, Neato's parent company stopped selling Neato and will shut down operations as I read in a tech blog. The parent company will maintain the cloud for 5 years but obviously they already shut some parts down as it looks like?

The problem is not on the Neato/Vorwerk side. Their app works fine, and 5 minutes before I upgraded Home Assistant it worked. I was on 2024.7, I guess this was the last working version?

edit: deleting & re-adding the integration gets it working again. Hopefully someone can help debug this given the author of the integration is no longer supporting it.

Logger: pybotvac.account Source: components/neato/hub.py:30 First occurred: 4:34:26 PM (1 occurrences) Last logged: 4:34:26 PM Bad response from robots endpoint: expected str for dictionary value @ data['secret_key']. Got: {'serial': 'WTD01234AB-0123456', 'prefix': 'SN', 'name': 'Fred', 'model': 'xv-12', 'firmware': None, 'timezone': None, 'secret_key': None, 'purchased_at': None, 'linked_at': None, 'nucleo_url': 'https://nucleo.neatocloud.com:4443', 'traits': []}

[prom00]

Vorwerk, Neato's parent company stopped selling Neato and will shut down operations as I read in a tech blog. The parent company will maintain the cloud for 5 years but obviously they already shut some parts down as it looks like?

The problem is not on the Neato/Vorwerk side. Their app works fine, and 5 minutes before I upgraded Home Assistant it worked. I was on 2024.7, I guess this was the last working version?

edit: deleting & re-adding the integration gets it working again. Hopefully someone can help debug this given the author of the integration is no longer supporting it.

Logger: pybotvac.account Source: components/neato/hub.py:30 First occurred: 4:34:26 PM (1 occurrences) Last logged: 4:34:26 PM Bad response from robots endpoint: expected str for dictionary value @ data['secret_key']. Got: {'serial': 'WTD01234AB-0123456', 'prefix': 'SN', 'name': 'Fred', 'model': 'xv-12', 'firmware': None, 'timezone': None, 'secret_key': None, 'purchased_at': None, 'linked_at': None, 'nucleo_url': 'https://nucleo.neatocloud.com:4443', 'traits': []}

I have tried removing and re-adding it. However, this doesn't help either. While adding, it redirects to a page which returns error 500.

[ronaldt80]

I have tried removing and re-adding it. However, this doesn't help either. While adding, it redirects to a page which returns error 500.

I get the same error (500). Nonetheless the integration is back up. Coincidentally this weekend also the Neato app stopped working. Log out and log in in the app did the trick and following this i could also re add the integration.

What do your logs say when you get your error?

[prom00]

The error isn't inside HomeAssistant, but on the external URL from Neato:

https://apps.neatorobotics.com/oauth2/authorize?response_type=code&client_id=xxxx&redirect_uri=https://my.home-assistant.io/redirect/oauth&state=xxxxxxxx&client_secret=xxxxx&scope=public_profile+control_robots+maps

This simply returns an HTTP 500 error status in the headers.

[ronaldt80]

did you check the redirect url?. Needs to be the path to your externally accessible home assistant instance (see redirect uri)

[prom00]

did you check the redirect url?. Needs to be the path to your externally accessible home assistant instance (see redirect uri)

Yes it is redirected to my home assistant installation. But the problem is that the neato website returns the internal server error, which means it doesn't get past its own validation. The redirect never happens.

Guess it's time to write off the neato "app" functionality. For now I can still use the Neato app.

[callifo]

Mine just broke this morning, had been working flawlessly for quite a while.

2024-12-10 07:15:47.724 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:15:58.464 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:16:19.632 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:16:41.595 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:16:46.887 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:16:57.439 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:17:18.325 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:17:40.478 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:17:45.924 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:17:56.587 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:18:17.717 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.
2024-12-10 07:18:58.685 ERROR (MainThread) [homeassistant.helpers.config_entry_oauth2_flow] Token request for neato failed (invalid_grant): The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.

Tried deleting/readding, but now getting this:

I tried my android app, and it had logged me out. Upon attempting to relogin the login page looked different from memory, but it did succeed logging in fine.

[barryhartman]

I can confirm that removing and re-adding the integration today got the connection working again. But since we're dependent on Neato I don't know how long this will work....

Edit: And since the developer link (https://developers.neatorobotics.com/applications) does not work any more so you cannot add new integrations, perhaps wise to add this information to the already active alert on the home assistant website (https://www.home-assistant.io/integrations/neato/).

[Tonylolo]

I removed and re added the integration and it’s ok now.

Just map haven’t updated since 2 months.

[ronaldt80]

Same, no maps since October

[gandihar]

My integration just died over the weekend. Same as above, it threw an error 400 visible from the HA UI, logs complained about the auth key being invalid. I tried everything up to and including making a new integration on Neato's end, but it didn't work for me until I purged the old integration, and removed the application credentials in HA, created a new integration on their end (With the same settings), and re-added the integration in HA. Now it's working again like it was.

[loverso]

the developer link (https://developers.neatorobotics.com/applications) does not work any more

It is working now.

[jonikarbu]

My Neato D5 has been intermittently stopping working, and so far, disabling and re-enabling or reinstalling the integration has helped. However, now my robot had gone offline in both HA and the Neato app. I rebooted the robot, and now it’s accessible via the Neato app, but not through HA. Neither of the previously mentioned solutions worked, so I ended up uninstalling the application from the developer's site and creating a new one. It seems that HA can log in to some extent but cannot list any devices.

Are others experiencing similar problem?

[gandihar]

Mine has fallen off the network again this morning. It was fine until suddenly it was offline. I've rebooted the robot, re-logged into the Neato app, and they both say they're fine now, but HomeAssistant still shows the robot offline.

[neutrino85]

Same, pybotvac returns this : (SSLError(1, '[SSL: TLSV1_ALERT_INSUFFICIENT_SECURITY] tlsv1 alert insufficient security (_ssl.c:1007)

[kerowog]

@jonikarbu My d7 also went offline today. I removed the integration and added it again. I logged in but no device is loading. The Neato app works.

[Diegocampy]

@jonikarbu Anche il mio d7 è andato offline oggi. Ho rimosso l'integrazione e l'ho aggiunta di nuovo. Ho effettuato l'accesso ma nessun dispositivo si carica. L'app Neato funziona.

same situation same D7

[neutrino85]

The Neato App is down for me. https://beehive.neatocloud.com/sessions seems to be unreachable.

[kerowog]

The app also stopped working for me today.

[sondercoder]

Neato website shows 'D3-D7 servers under maintenance!' - I'd expect things to return to normal soon. This issue has nothing to do with this add-on.

[prom00]

The app takes a long time to load. After loading it now shows "TRY AGAIN". Seems like neato is officially dead now and they don't care about the promised 5 years support.

What I've been doing lately is just push the button on the robot and it starts cleaning, I've noticed that is has been having more issues cleaning lately -> more stuck on places where it wat never stuck before.

[bobbinz]

Neato website shows 'D3-D7 servers under maintenance!' - I'd expect things to return to normal soon. This issue has nothing to do with this add-on.

I hope it's this rather than the doom and gloom version.

Fingers crossed!

[bobbinz]

There is a fix for this at https://github.com/home-assistant/core/issues/138345#issuecomment-2663992270