search

whittlem / pycryptobot

Python Crypto Bot (PyCryptoBot)
Apache License 2.0
1.97k stars 738 forks source link

Binance Bots Keep failing with "Insufficient Funds" or "Data range too small" #511

Closed manosaaa77 closed 1 year ago

manosaaa77 commented 2 years ago

Describe the bug My Binance account has 1000 AUD balance and I am trying to trade on 4 pairs - BTCAUD, SOLAUD, XRPAUD and DOGEAUD. None of them have worked in the last week. I have been updating to the latest code base regularly and I am currently on v4.0.3. But the bots keep failing with Insufficient Funds or Data range too small errors.

Details about my installation: OS: Ubuntu 21.04 Hardware Config: intel i7, 32 GB RAM, 1 TB SSD HDD. Internet Speed: 50MBps, 9-10ms latency Python: v3.9.5 Exchange: Binance Account Balance: $1050 AUD Trading Pairs: BTCAUD, SOLAUD, XRPAUD and DOGEAUD PyCryptoBot version: 4.0.3 Telegram enabled: Yes Autorestart bots enabled: Yes

Could this be because my base currency is AUD and not one of EUR, USD or GBP? Could you please help operationalise my bots?

Regards, Manoj

Jaska80 commented 2 years ago

I also have same issue with BTC-EUR on Coinbase Pro. Bot did run for two days but for that i know it didn't do anything in that period of time.

SmartSelect_20210927-071232_Gallery

-Jaakko

edrickrenan commented 2 years ago

@Jaska80, based on your screenshot, there was a problem with the coinbasepro API, not related to the bot. I imagined that has been fixed.

@manosaaa77, can I close this issue or it's still happening?

Jaska80 commented 2 years ago

Hi, Yep that problem is fixed.Thank you.Regards JaakkoLähetetty laitteesta Galaxy -------- Alkuperäinen viesti --------Lähettäjä: Édrick Renan @.> Päivämäärä: 7.11.2021 13.41 (GMT+02:00) Saaja: whittlem/pycryptobot @.> Kopio: Jaska80 @.>, Mention @.> Aihe: Re: [whittlem/pycryptobot] Binance Bots Keep failing with "Insufficient Funds" or "Data range too small" (#511) @Jaska80, based on your screenshot, there was a problem with the coinbasepro API, not related to the bot. I imagined that has been fixed. @manosaaa77, can I close this issue or it's still happening?

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.