-
Notifications
You must be signed in to change notification settings - Fork 22
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
API Access Not Working #7
Comments
I'm having the same problem. I hope this gets fixed/updated soon! |
The same issue. |
Does the token work if you run a curl request manually? curl -H "Authorization: Bearer <ACCESS_TOKEN>" https://api.youneedabudget.com/v1/budgets |
I just remembered we had this issue previously and it was due to a dependency package. I see they have new version available. I'll bump up dependency tomorrow or so and lets see if it solves the problem. |
Hi wxt9861, thanks for this integration! I am having the same issue with "verify API key". It works when I run the curl request manually. I get a proper JSON response from the API. But in Home Assistant, I get the log message, that the API key is not working. |
Can you test with v0.1.8? |
Have just tested it, but am still receiving the same error message. Is there a way for me to provide some additional debugging info? |
Ok, I cannot replicate unless I intentionally enter a wrong API key. Let's try this, if you can. At the very least, I want to figure out if the issue is coming from the component or the ynab-sdk package it uses to talk to YNAB api. If you can, get the apitest.py file and run it as a test. All it does is connect to ynab API and shows a summary of budgets. If it works, we know you can successfully connect to ynab and the issue is in this component. If you get an error, than the issue is possibly with the package or elsewhere. https://github.com/wxt9861/ynab/blob/bug_fix/apitest.py |
Thank you! This is the export I get from the function (modified):
My configuration in YNAB looks like this:
|
Thank you. So it looks like the ynab-sdk is working correctly and the issue is in the component. Let me try to figure out how I can replicate this on my end so we can fix it. |
I am still unable to replicate the issue however one of the issues with ynab_sdk is that it does not relay proper error codes, so it's hard to say exactly what is not working (ex: is it API key or something else?). I made some additions to the component to help us debug it (hopefully). This version pulls budget summary and lets you know how many budgets it found (with their IDs) in the debug log. Please try the beta version and let me know what you find. Run it with debugging turned on for ynab component and let me know what results you get. If you're going to paste debug log, please scrub it of any sensitive information.
https://github.com/wxt9861/ynab/releases/tag/v0.1.9b1 |
Update 3: I have a certain type of split transaction (mix of category and account) that is causing this issue:
When I create this kind of transaction in a test budget, that is working otherwise, it fails. As soon as I delete it, it is working fine. Have created an issue with the ynab-sdk: andreroggeri/ynab-sdk-python#83 Thanks again for your help! Hi thanks for your help! I have done some debugging by myself, and this caused the error in init.py:
I got this more detailled error message now:
Update 1:
I received the same response:
Update 2: Thank you! |
@lndnbrg I see that your issue request was closed with an update. I am going to update dependency here and release an updated version in the next few days. |
Closing issue as it was addressed in a dependency. |
I'm seeing the same issue as previously, on the latest release...no info except that the token doesn't work. Even created a new token and doesn't work. api_key is the only option I'm specifying in my config. I have a couple older budgets but specifying one doesn't seem to make a difference.
Logger: custom_components.ynab
Source: custom_components/ynab/init.py:209
Integration: ynab (documentation)
First occurred: 3:37:14 PM (1 occurrences)
Last logged: 3:37:14 PM
Could not retrieve data - verify API key
The text was updated successfully, but these errors were encountered: