search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
74.05k stars 31.08k forks source link

Neato Integration no longer working #124701

Open patricknew78 opened 3 months ago

patricknew78 commented 3 months ago

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_oauth2flow] 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] commented 3 months ago

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 commented 3 months ago

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

lotharbach commented 3 months ago

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 commented 3 months ago

Same issue, @lotharbach solution resolved it. Thanks!

prom00 commented 1 month ago

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 commented 1 month ago

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

PeterDuh commented 1 month ago

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 commented 6 days ago

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 commented 4 days ago

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 commented 4 days ago

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 commented 4 days ago

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. image

ronaldt80 commented 4 days ago

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

prom00 commented 3 days ago

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.