search

adocquin / kraken-dca

Dollar-Cost Averaging bot for cryptocurrency pairs on Kraken exchange.
GNU General Public License v3.0
44 stars 8 forks source link

Already DCA - but dind't so #11

Closed AndiMacTen closed 2 years ago

AndiMacTen commented 2 years ago

Hi, first of all, thank you for your awesome work! Currently I'm facing the problem that my script is responding with Already DCA but there wasn't any executed buy order since serveral days. The configured delay is pair: "XXBTZEUR" delay: 1. There's enough funds in my account. Do you have any idea how to troubleshoot this issue?

Thank you

adocquin commented 2 years ago

Hello,

Thanks for reporting this issue, I'll take a look at it.

Do you have any open order for this pair or another? When was the last order correctly executed? Can you post your configuration file with sensitive information removed, please?

AndiMacTen commented 2 years ago

Hi,

thanks for reaching out to me.

Yes, there are open buy and sell orders for this pair. They were there since I was start using the script I guess. The last order was executet on 01/19/22. After that order two normal buy orders have been filled.

My config file:

dca_pairs:

  • pair: "XXBTZEUR" delay: 1 amount: ***

Very simple. delay was set to 2 before, I tried to decrease it but no change in the behaviour. Usually I start the script via cron but also manually I get the Already DCA response.

AndiMacTen commented 2 years ago

Hi, I installed the script on another computer (Rpi) and tried to DCA from this one. Therefore I copied the config file incl. API keys to the Pi. Same result, I got the Already DCA response. Then I canceled the open buy orders for the pair I want to DCA and run the script (on the newly set up Rpi) again. This time without any tourbles. The order was executet as expected :) I try to reprocuce this behaviour in the next days and let you know

roswennen commented 2 years ago

The script seems to look at whether there is an existing order on Kraken for the pair irrespective whether it was put there by the script or by yourself in the past and if there is an open order it assumes it's a DCA and scips.

adocquin commented 2 years ago

Hello :wave:

Thanks for your comment roswennen. Yes, it's the default behavior of the API.

Implementing the feature of avoiding this issue would require the users to not drop the orders.csv file created when passing orders through the API. While it can be a constraint for the user, this is something I can add if more people think this should be the default.