Hi All,
I was wondering if you can give me some guidance, I note that the newer models are no longer supported due a new API how do the old users stand? I have an D6 and a far as I can tell that still using the old API?
HA now reports that my model is not supported? why this is not a new model.
Regards
Have you got this solved? I have a D7 which use to work just fine and now I get The redirect uri included is not valid error…
Hi,
I have got a different Problem with the connection.
In my last instance the integration worked fine (Botvac D6), now I have changed my hardware and started a new Instance. So I did what I did before.
When I clicked on the link from the integration page, the redirection URL was invalid. I used the external url with https, tried different browsers and a different Homeassistant Instance, made different apps and changed everything i could think of. Same Problem. At last, I realized, that the URL, that opened the Neato Developer side for the oauth contains [..]redirect_uri=https://my.home-assistant.io/redirect/oauth[..].
Shouldn’t this be different? If I change it manually, the auth page starts but than 404 Warning. What did I miss in my configurations?
Thank you
OK,
Tried some ther things. I made a new Neato account, connected the vaccuum and removed every entry out of application_credentials and configuration.yaml, because I found in my logs, that this ist not the way. I also installed a new browser and only tried it with this homeassistant instance and the new neato account. no luck still wrong url
Got the same error - worked until today. Didnt update or anything, but just shut down my HA… once reopened, this error came " The redirect uri included is not valid. "
Tried to delete all API´s on the neato page, but no luck. created a new token, restarted HA after configuration were made.
Just sad this…
Have you tried the fixes proposed in the following discussion:
Neato Integration needs to be reconfigured after updating HA from 2020.12.1 to 2021.1.1 ?!? - Configuration - Home Assistant Community (home-assistant.io)
Hello,
I came here to say the same thing. I’ve been having trouble with my neatos for days and I am receiving the same url redirect error. I posted this in the discord channel because I’m suspicious the work that was done around OAuth on 6/7/2022 has something to do with this: OAuth application credentials for the Neato integration via the UI error · Issue #72989 · home-assistant/core · GitHub. I didn’t go to some of the extremes some of you have gone through to try to force a new URL (although I understand why) but I removed the instance of neato, restarted, and tried to add a new one and I got the same error (same as you). I had neato running since dec/jan timeframe under the old integration. After the release, everything looked ported correctly and was working for several days and then at some point it just started throwing errors in the last 2-ish weeks.
Have you noticed that the changes in 2022.6 require a different redirect url to be entered in the Neato app in their developer portal? I needed to change it because the integration could not refresh the old token. After that it worked for me without changes to HA. I could simply press reconfigure again.
According to the new docs the redirect url to supply in the developer portal should now be:
https://my.home-assistant.io/redirect/oauth
And maybe you should also check in the same browser if the oauth redirect is properly setup to go to your Home assistant instance:
I noticed it at the exact time you posted this and I have them both up and running. It wasn’t clear to me that I had to go into my neato dev account and adjust the redirect. It should’ve been (the redirect was in a box directly below the neato dev account hyperlink) but I didn’t think to put those two together because I haven’t been in that account in so long. Everything works!
This made no difference for me. Still get the "The redirect uri included is not valid. " error.
I am getting the same error as well now.
I have recreated the app in the dev portal with the latest redirect url, but still no luck.
The pwd are updated and my HA is reachable from the internet.
What can the issue be?
So I didn’t realize, cause I was trying to customize the redirect URI in Neato developer portal, but it literally needs to be exactly:
https://my. home-assistant.io
And then you need to visit:
https://my. home-assistant.io
And change your redirect URL to your duckdns or internal URL, then go back and reload or reconfigure the add-on. Now it works.
Thank you very much @barqers !
That was the issue. I was using my own external link for the redirect.
Problem solved.
Hi, I’ve had the same issue. I’ve read the comments in this thread, went to the Neato Developers Network Portal https://developers.neatorobotics.com/applications, changed the Redirect URI to https://my.home-assistant.io/redirect/oauth and now the integration is working again! Thanks!
Yes, got this woking!!! Thanks to everybody.
I’m finding this “helping me do things easier” is not helping much at all!
Firstly the credentials were wrong in the onboarding. They were left over ones from an app that I deleted in attempting to get this working. I had to manually go into /storage and change that in the application credentials there. Apparently there is supposed to be an integration for application credentials but I have not been prompted to install it and cant find it?
Secondly I am reverse proxied and this whole “my home assistant” integration is confusing to me. I know I need a secure reachable externally address which I have why do I have to use that specific URL now.
Like if you are gonna take total control of the onboarding of my stuff than can we some how make sure all the peices line up! Frustrating.
Why did I even have to “reintegrate” this integration I was already using the make a neato app and callback method for security?
I really need to clarify the setup:
open the link: https://developers.neatorobotics.com/applications
Configure/change your url to exaclty: https://my.home-assistant.io/redirect/oauth
Thank you! It worked for me as well
Thank you for this! Fixed my issue right away when I did this!
Thank you. Fixed it for me too. 