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
Bunq support in v4.7.4 #1443
Comments
Will give it a look later today 👍 |
references #1387 |
Will try it tonight, thanks for your work! |
Got error when i click the submit button in bunq import section
freshly installed 4.7.4 from develop branch |
@japsikado can you paste the full traceback and on what system are you. |
Thanks for letting me know! What OS are you using? |
I am using windows 10 `Debug information generated at 2018-05-23 13:59:41 Europe/Amsterdam for Firefly III version 4.7.4.
|
It means you need a working OpenSSL installation. Please check out this page for some extra info. |
You can also have a look at this issue: bunq/sdk_php#102 |
However, if you do nothing, and try again, Firefly III will give you a nice error message. I've just pushed a catch routine that should give you more background and a way to fix this. |
Hey! Thanks for the update! I just gave the 4.7.4 update a go and I seem to get stuck at running the import. The import job is still in the database as running, with no actually imported data. Bunq recognizes that the API key has been used, so that seems to be working. I get this in the application log. Anything I can/should try? ~ Edit: Debian 9.4, PHP 7.1 (FPM), nginx 1.10.3
|
That seems to be an error within the bunq SDK unfortunately. |
@JC5 This has to do with #1387 (comment) |
Ive given you a heads up 🙈 |
Haha ok I didn’t realize these were connected. Anything I can do? |
lock the dependency (bunq/sdk_php) in composer to the latest commit on develop until the next release. See https://stackoverflow.com/questions/21314381/how-to-correctly-require-a-specific-commit-in-composer-so-that-it-would-be-avail |
Will test it later this afternoon! Great work on it man! @JC5 |
Hmm, it seems that the docker image has no connection to the internet after pulling develop. Not sure if this has something to do with my system or not. Will continue investigating. Might be that the network bridge is broken. The Curl in the docker container is to old as well.
bunq/sdk_php requires curl version 7.54 and up for pinned key support. See bunq/sdk_php#7 |
I will create a PR to update the DockerFile to install install curl accordingly. |
👍 I've pushed a bunch of new code. Should be no operational changes, but testability has improved (coverage as well) and composer.lock is pinned to the commit you indicated. |
@jonathanjuursema Could you re-test when you have the time? |
I have upgraded my instance, and the import seem to be working. The only thing I saw was that the change done in #1398 has been gone, which is unfortunate as it makes importing a bit hard with multiple accounts. |
@paul999 can you re-add it ? Or at least give an option to auto create the asset account instead of canceling the import, create the asset account and then re-doing the import. |
I already have all of the accounts in my install, but they are set as default option to do not import. IIRC, if I look closely at the code this should already work, but it doesn't actually select the account. Another things I noticed is that if you do another import, you now get a list of errors when transactions are already imported:
I also have the idea it is going back a very short timeframe? With 4.7.3 it would go back from the start (I think?) now, it seems to just go back for the last 12? transactions. |
@paul999 I have to check but I thought the code is there:
I will verify if it works as expected. As for the import: I haven't changed anything in particular but I am not sure what time frame the bunq SDK offers by default. Perhaps I can extend the range or send parameters. I'll do some research. For future versions (beyond 4.7.4) I can build a time / range select thing. |
…ii/firefly-iii#1443 Update curl in docker #1443
Because there are users running this baby on RP2's so 0.3 seconds per transaction is already pushing it. Given the default of 30 seconds. The code should be able to simply keep POST-ing the job until it is finished, so I'd rather do that. And I'll do that, but don't hit me when I forget 😉 |
Running a bunq import on the most recent develop branch seems to work without any errors on my machine! @JC5, thanks a bunch for all you've done and probably will do. :) I don't have any duplicates anymore when importing internal transfers, so that's that. The only thing is that it doesn't import all transactions. It has transactions all the way back to when I started using bunq (Jan 8, 2018), but it seems to be missing random transactions in between. I'm not sure if this is something in Firefly or with the bunq API. Is this something known? A second import doesn't seem to import the missing transactions, but the duplicate detection works flawlessly. :) |
I have just had time to test and the import ran without errors! I am noticing the issue that @jonathanjuursema has as well. I have a transaction almost every day but notice the gaps in here: I am importing multiple accounts at once. |
@IcyPalm @jonathanjuursema This is definitely not on bunq's end. If you can see the transactions in the bunq app, then you should be able to see them via the API as well. |
@jonathanjuursema Please enable debug mode and either share the log with me (accepting that I may see private info) or try to find the error yourself. The importer will first download everything, and then import transactions. If you need more debug info, let me know. If the transaction is there, downloaded from bunq, it might not be imported later on. Either way, that's what I need to know. @IcyPalm Same thing really. It could be that the import fails but it should give you feedback on errors, even system errors. |
@JC5 with
Anywhere else I can check for errors? |
Make sure you set the log level to DEBUG. |
That did the trick. The only thing I can make out that seems strange is a whole bunch of If it helps, I can send you the anonymised log of the import. :) |
I quickly scanned through the debug logs but found nothing weird, except the same issue as @jonathanjuursema. Tomorrow I am going to dive deeper in the logs and anonymise if needed |
@jonathanjuursema That error is related to the creation of new expense and revenue accounts. The system is also able to process opening balance information (for asset accounts) and will tell you when that info isn't there. It's not a problem when that information is missing. I can't replicate your opening balance problem on the demo site. |
I've pushed some small updates, most notably Firefly III will now download the last 100 transactions. |
@JC5 I suppose the opening balance issue is because I was trying to set it to €0 on 1/1/2018, which is when I opened my account with bunq. I suppose it doesn't save the info if the opening balance is, €0, since other amounts indeed work fine! I suppose there's also little use for setting an opening balance of €0, coming to think of it. Also, looking through the bunq API docs, could the issue I and other people have regarding the idea that we were 'missing' some payments be because Firefly pulls 100 transactions per account? So that would mean that I would pull all transactions from an old account I used till February, and only the 100 transactions I did in May, for example, missing all transactions from February, March and April. |
Yes. That will be the situation with the next release. |
OK, I've pushed the last code. This will enable the rules engine automatically on new bunq imports. As for the "gaps": Firefly III will now download the last 100 transactions per account. There should be no gaps in this download but depending on your history this could mean the import only goes back so far. Code coverage is complete and everything seems to work just fine. As far as I can see, it's all ready for the release. Probably somewhere during this weekend I will make sure it gets released. New issues will be created afterwards to tackle the following feature requests.
|
@JC5 is it possible to store the payment id that bunq uses to identify this payment ? This will make it convenient for self made tools. Use Case: Or i dont recognize it and i want to ask bunq support about it etc etc. So TL;DR it would be nice to store the external reference. |
The external reference is stored, but it might not be visible yet. Check the |
Yes you're right its indeed there. So then yes, if this could be shown in the transaction details that would be nice. You can also use this info when importing. Filter ASC to get the latest |
It should be visible under both "external ID", "internal reference" and "bunq payment ID". 😁. The first two are user-editable. |
4.7.4 is live. 🎉 |
@JC5 will you still add support for only importing new transactions ? instead of always the last 100. The red "warnings" after the import is really not needed when not importing via CSV or something along those lines :) |
Yes, in 4.7.5 :) |
@OGKevin @HippoGrief @gldrenthe89 @paul999 @jonathanjuursema @Xeli @IcyPalm @Want100Cookies @FreekBloemhof @japsikado @SpaceK33z
Hi guys!
I've tagged all of you because you've worked with bunq + Firefly III, or have complained about its implementation.
Currently live in the
develop
-branch is new working code for the bunq-import routine that works on my machine, as developers tend to say.I would like to ask you to install a development version of Firefly III and test if it works as expected.
Since I am not sure what your technical expertise is, here are some general instructions.
.env.example
file to.env
and fill in all the details.BUNQ_USE_SANDBOX=false
at the bottom. You can switch to the sandbox if you want to.If you are a Docker fan, the latest develop build should contain the new Bunq code as well but you have to have a database already.
I am currently writing tests, so be sure to
git pull
regularly.Thanks in advance for your help!
Cheers,
James
The text was updated successfully, but these errors were encountered: