Neato Botvac intregration using wrong callback

The Neato Botvac intregration hang up on me after the last update to december version.
I know Neato change their API as some change underwear but it should not be a problem for my D7 Connected, since the models the new API-trouble applies to is D8, D9 and D10 (if I recall right).

Anyways… The error I got were that my old token were old and needed renewal.
So, said and done. Sat up a new application at Neato Developer site.

I run a fairly common configuration with a valid SSL, a domain name and exposing a port to the internet.
So the callback URI is altered according to previous rules…
https://:/auth/external/callback

BUT! When adding the Neato Integration it does get stuck with resolving to “my.home-assistant.io” as can be seen in the below picture where I snipped the web-url.

bild

Is this a bug in the Integration not prestent in previous versions or am I or Neato doing something wrong?
Been running the application for 2 (or 3?) years so I know my way around the SSL-auth problems (I jumped down a rabbit hole with purchasing SSL’s and domains with this integration).

Does anyone have any advice or suggestion how to have Home Assitstant not calling for the wrong address?