-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue]: OAuth failed - invalid_grant - token was issued to another client #187
Comments
Have you tried the default redirect uri as mentioned in the readme as part of the application you configured at the daikin website? |
Have you restarted HA? Have you installed my home assistent? Have you tried to link to your local HA ip address? |
In my very first try some days ago I put my HA address. But then I deleted the app and put https://my.home-assistant.io/redirect/oauth And I also tried to put my local IP in the link account page. Try also the other method you explained after in the readme: |
I have no idea at this moment how to solve this, please open an issue on HA core to ask for a feature to retrieve the redirect_uri as used by HA so that you can use the same uri at the daikin portal |
Just chiming in here to say I suffer the same issue.
|
Created an upstream issue home-assistant/core#117169. I did had this on my system also when starting, but after a HA restart and using |
Nice! I noted you wrote "Home Assistant OS" as installation type, I am using the container in a kubernetes cluster... which probably makes things more complicated by several miles. I imagine that it won't be enough for me to know what Home Assistant sends as redirect_uri, I will need a way to actually set it... maybe.... I don't know, honestly guessing here :D |
Maybe contact @Daikin-Europe, maybe they can find what you are sending |
Did you got it working? |
@jwillemsen sorry, I have not been able to tinker with this, am out of town until this weekend! |
I could write either to Daikin or HA Core team, but I'm a total noob and not sure what to ask..and I'm afraid of the questions I could get as response :D |
Send them the error and what you already tried, you can also add a link to this issue |
Any updates? |
Hi, I don't know if I am right here but maybe I am lucky. I wanted to add the Daikin Onecta Integration to my Home Assistant, but I have problems with the Daikin Developer Portal. In particular I am not able to login to https://developer.cloud.daikineurope.com/ When I go to the site I see the "Continue with SSO" button. When I click it I get redirected to https://id.daikin.eu/ where I can insert my credentials. This seems to work. What I also see is that the url in my browser is: https://developer.cloud.daikineurope.com/login?loginError=internal+error&loginSuccess=false This happens every time, on every browser, with and without private mode. So it seems the issue is on Daikin side. Thanks in advance. |
See https://developer.cloud.daikineurope.com/docs/b0dffcaa-7b51-428a-bdff-a7c8a64195c0/business_validation for a email address to contact Daikin |
Thanks for the quick answer, but unfortunately no luck. I also only get redirected to the "Continue with SSO" page when I click this link where I am stuck in a loop. |
Have you restarted your system or use a different PC? |
Had a similar problem the other day, clear your browsers cookies/try a
private browser window.
I have made some more attempts at getting to work, tried to read the code
for both the integration and home assistant to see if I could deduce what
the redirect_url actually gets set to. But I have made no progress. Is
there a way to get more verbose logging perhaps?
fre 24 maj 2024 kl. 15:35 skrev muarqdnph4VPV6dyh ***@***.***
…:
Thanks for the quick answer, but unfortunately no luck. I also only get
redirected to the "Continue with SSO" page when I click this link where I
am stuck in a loop.
—
Reply to this email directly, view it on GitHub
<#187 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAASHYUASGKFSTJET5X3YG3ZD462FAVCNFSM6AAAAABHO52GDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZGU2TGMZZGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
All authorization is handled by HA, maybe ask if they can add some more logging to the HA application credentials support? I have created an issue to ask for a way to retrieve the redirect_uri, see home-assistant/core#117169 |
Yepp, saw the issue! Gj!
One thing I noted is that the code for HA seems to have moved on from the
version I have running, the line numbers in the logs don’t line up with the
source. Perhaps fixes are coming.
I tried to find the python for what I actually have running but I have no
idea where that lives inside this docker image :D
fre 24 maj 2024 kl. 16:12 skrev Johnny Willemsen ***@***.***>:
… All authorization is handled by HA, maybe ask if they can add some more
logging to the HA application credentials support? I have created an issue
to ask for a way to retrieve the redirect_uri, see
home-assistant/core#117169
<home-assistant/core#117169>
—
Reply to this email directly, view it on GitHub
<#187 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAASHYQ2MBWYVB2JHAOHULTZD5DFLAVCNFSM6AAAAABHO52GDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZGYZTIMRWHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
yes, even tried it on a different PC and on my Phone, everytime the same result. |
Ok. So I had some time now to dig into this. And the problem is that you have hard-coded the client id & secret in config_flow.py on lines 93 & 94. These should be the values you make the user enter as part of the flow. By the way you should probably generate new ones for yourself. Ahem. |
Ok now that is strange. When checking the repo here, you don't have those lines. But when I check the .py files in install that were grabbed by HACS, I have hard-coded client id & secret.... |
Do you have installed the latest version, in the past we had a client id/secret which was provided by Daikin |
No, re-installed. I still get a version installed that has a hard-coded client_id/secret. |
Try to remove it completely and install a fresh copy, did also had cases where HACS installed something differently as I thought |
Current installed version should be visible under |
Removed the repository in HACS. Removed the folder /config/custom/components/daikin_onecta. Restarted home assistant. Re-added the repository in HACS. Re-downloaded. I now have version 4.1.3 installed and the configuration flow worked flawlessly. |
I'm out of home these days so I can't operate on Ha yet. However I checked and I confirm I have id and secret hardcoded on my instance too. |
Good afternoon,
Since 3 days I'm trying to get this integration to work, but without success.
I signed up for the developer account, I created the APP as per instructions:
I get redirected to the Daikin website, I give permission, I link the account to my HA instance giving my internet address (not the local one) and when I get redirected to HA, this is the error:
This is the log:
I deleted everything I found in my HA instance related to the old daikin residential integration.
I've tried to delete the daikin app in dev portal and refresh the tokens 10 times, changing browser and deleting cookies. But nothing helped.
Could you please help me to solve the issue?
thanks
Michele
The text was updated successfully, but these errors were encountered: