Open patricknew78 opened 2 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!
(message by CodeOwnersMention)
neato documentation neato source (message by IssueLinks)
I hope I am wrong, but https://beehive.neatocloud.com redirects to a page that says Neato has ceased selling operations..
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.
Same issue, @lotharbach solution resolved it. Thanks!
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
Still error 500, can't add the integration back. Not a lot of thing we can do :-(
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
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?
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