[Issue]: Using a custom redirect_uri as part of the HA setup doesn't work (yet)
Closed this issue · 9 comments
When trying to add the master d0f23e0 i get redirected to the Daikin proxy after which it opens a proxy error.
I think the problem is that you are using a different redirect_uri
, see https://developer.cloud.daikineurope.com/docs/b0dffcaa-7b51-428a-bdff-a7c8a64195c0/getting_started for a reference that only onectaintegration://callback/
should work, but Daikin has added https://my.home-assistant.io/redirect/oauth
. You will have to wait until Daikin supports the creation of applications through the developer portal (where you can specify the redirect_uri) or see if you can support https://my.home-assistant.io/redirect/oauth
How could I remove the custom redirect_uri? It's not something I set on purpose.
So you're using the Home Assistant Cloud to access remotely your HA instance and you're able to add the integration?
I guess it's time for me to contribute by paying for the Nabu Casa Home Assistant Cloud.
No, I am not using nabu, just using it locally, works for me
I will try to find a better reference page tomorrow
Removing the URL from Settings/Network/Home Assistant URL didn't help. I had to add an empty
my:
in the configuration.yaml
file.
After which I removed my:
because the SmartThings integration stopped working, restarted HA, and both integrations continued to work.
Thanks a lot for your suggestions. I'll check tomorrow if the token is refreshed properly.