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
Ignored buymaxsize #250
Comments
Hi, |
It works for me. "buymaxsize" was only accepting an int before but I've updated it to support both a float and int input. I've tried with arguments and in the config.json and I can see app.getBuyMaxSize() returns the correct value. The only code which uses this is:
I don't see anything obviously wrong. Can you confirm you are running the latest code with "git pull" and see if this is resolved now? |
I had the version from yesterday but i don't think there was change on this part after that. Michael I know you are only using coinbasepro ? I actually had the pb on binance. git pull this morning, We'll see on my next buy, i'll get back to you |
Yes I pull this morning, the first buy used all USDT in my wallet after that it got back to working properly. |
Confirmed, I just made a new pull and recreated the containers ... during the first purchase did not respect the buymaxsize and it has bought for the full amount of USDT. |
Here he also bought the full amount. Not respecting buymaxsize. I use Binance here |
@TICLAB you say it's working but @biskuizera19 say it's not? Are you both using Binance on the latest version? |
sorry I haven't tested it today with the latest pull |
Yes, I use Binance. The problem lies in the first purchase, subsequently the buymaxsize is respected correctly and only the first purchase that uses the entire sum of quote_currency |
Hi, I have the same problem (Binance and latest version). I add, that even with the "buypercent" option does not make BUY, while I tried version 2.13.1, so much older and purchases and sales are done correctly. |
still not working :'( |
@ronaldderksen, there seems to be an issue with "buymaxsize". You kindly implemented this for us but there is an issue related to it. Can you please take a look? @djhemp and @dthevenin, you commented on the PR as well. Do you use this feature and is it working for you? |
I will take a look this evening |
I had exactly the same issue with the 'buypercent'. These are probably rellated. |
one of my bot bought ALL my busd and now i'm stuck X'D. Please help asap with this issue :p Thanks guys !!! |
Can you post your config.json?, without keys and command line arguments? |
yep sure root@jeedom:/home/jeedom/delph/Config# more binance.json i see now... Maybe it should be an INT ??? Can the others having problem share if it's my config the problem or if they put their value as an int and still not working.. ? |
Yes, it should be int or float. If not it is silently ignored. I just reproduced that. This evening I will check the config parser. For now just update your config.json to: "buymaxsize" : 100 |
Thanks Ronald, i did that. I'll let you know |
It should work. I am running 13 bots, with this option, on binance. I forced, in code, a buy at startup and noticed the difference. Ronald |
In my case, however, the value was set correctly to int, see the first comment of the issue. |
When you start the pycryptobot. Do you see the line 'Max Buy Size'? This is what I see
|
| Log : False --disablelog | |
I created a PR, for type, checking for all parameters. But I cannot reproduce the problem when type is correct. I tried @TICLAB Do you know what triggered the buy? Do you have console output? |
Given the market trend, I turned off the bot, unfortunately I no longer have the logs. What I can say is that the total purchase happened when I recreated the containers in docker. Sorry for the delay in the response @ronaldderksen. |
Hi All,
when the Bot was started it did not respect the buymaxsize present within the configurations and bought for the entire amount of the quote_currency.
"config" : { "base_currency" : "ADA", "quote_currency" : "USDT", "buymaxsize": 500, .... }
Regards.
The text was updated successfully, but these errors were encountered: