I was having the same problem until I followed dshokouhi’s suggestion listed above.
I opened a new browser window and in the address bar pasted in my external URL, I then logged into Home Assistant using my normal Home Assistant username and password. I was then able to add the Neato integration successfully.
I’m sorry, that you have these issues with your instance. It seems, that HA prefers the internal URL in your case. For the moment you could set your internal URL to the one with https to setup your robot. Switch it back afterwards. This should be fine.
EDIT:
I did some research. In fact HA chooses the current URL to build the redirect URI upon:
Therefore you can solve your problem by setting up your integration via your external URL as @cletus said.
I’m new to the world of Home assistant, I don’t know anything.
Thank you for your help.
I hope we will find a solution because there, I do not understand anything. why is it right with me that it does not work?
Am I right that your instance is available via this URL and you used this URL to set up your application at https://developers.neatorobotics.com/ ?
Please double check, that you used exactly this URL there.
And please remove the client_secret from your post as we should not know that
the strange url appears after emptying the firefox cache.
when I redo the request without clearing the cache, this is how it is written: c30826eac5 & redirect_uri = https: //di.duckdns.org: 8123 / auth / external / callback & state = eyJ0eXAiOiJKV1QiLCJhbGciOiJI
Maybe go back to the Neato Developer Network page, delete your app and create a new one. This will give you a new Client ID and Client Secret. Enter the new ID and Secret into your Configuration.yaml
I don’t know if the Client ID and Client Secret are in any way tied to the external URL, but it’s worth a try.
Having issues with the same integration…
Callback:
https:// ***************** .ui.nabu.casa/auth/external/callback
config.yaml has the following copy-pasted from the app created at ‘developers . neatorobotics . com’ #NEATO
neato:
client_id: 96c89248c37178bcba208a79e8e9c104************************* 33b
client_secret: d3097****************************************** cd33961591c6******
Defined scopes are
scopes:
public_profile
control_robots
maps
When authenticating i get the following error:
500 Internal Server Error
Server got itself in trouble
Respons is from:
’ https:// ****************** .ui.nabu.casa/auth/external/callback?code= *************************** 78004bc644555ebfd4d108&state=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJmbG93X*****************jYWViOThmYTBmZWQiLCJyZWRpcmVjdF91cmkiOiJodHRwczovL2oyNDRmaTF4a2ZweHE3MG03ZjV2azYyd3ozaXc3aXVrLnVpLm5hYnUuY2FzYS9hdXRoL2V4dGVybmFsL2NhbGxiYWNrIn0.8RtLXo6U2T0Rl6HSW8jPNf4_w2QX7byTLJmPc2BPQDM ’
I have a working spotify integration with the same callback, so I don’t know why this is not working…
I’m also trying to get this integration in place but not working, I have the Nabu Casa subscription and I’m not using duckdns, I have the provided nabu casa URL setup as my external URL and I’m getting the error that the redirection URL is not valid.
Not sure what I’ve misconfigured here, is the use of duckdns mandatory or the use of nabu casa allows not having to use duckdns?
sorry to re-open an old thread, but I just updated my HA installation after several months without any problem and now I get an issue with my Neato installation.
I followed all the hints above, but I still get the error message “The redirect uri included is not valid.”.
My external URL is reachable and I have used the new https://domain:port/redirect/oauth address to configure the Neato Dev App entry.
My internal and external URLs in HA are properly configured.
I see however that the link returned by HA when configuring the Neato integration contains this address ...redirect_uri=https://my.home-assistant.io/redirect/oauth&state=... which is strange.
Why that address and not the one I used in the Neato Dev App entry?