Message: bitget {"code":"12001","msg":"0PUFFER can be used at most"} #10907
Comments
|
Have you check the exchange's wallet and make sure those coins are exist in your trading wallet? |
Yes, if I close the order by hand in the exchange, it's being close in on ft also. I think this is a Bitget behavior, But I don't know what causing this. ft make entry LIMIT_BUY without problems, but is unable to make sell order for some coins. thank you for the reply |
xmatthias
added
unsupported exchange
|
In theory, freqtrade supports every exchange ccxt supports, which would also include this exchange. If you encounter specific problems, we're happy to assist up to a certain point - but the expectation for new exchanges is that the user interested is doing the legwork / most of the testing work - which also assumes a somewhat familiarity with python / testing/debugging things in python. If you're new to python / development - you're almost certainly better of with one of the supported exchanges. Above and beyond this - your best bet is to enable The error from the exchange kindof suggests that the asset is tied up on the exchange (in a different order ? / ...) - or that the exchange rejects it for some other reason (the api docs only list this as error - but don't explain what it means). Considering that the adjustment stakes you're using are VERY low (clsoe to the supported trading limit) - it's also possible that the exchange rejects them as "too small" - even though they'd still very closely fit into the exchange limits. |
|
Thak you @xmatthias, I used freqtrade with Bitget in Jan-april 2024 time range (never seen errors like these), and restarted using it in 1 november 2024 with the NostalgiaForInfinityX5 strategy, and this is the first time I see these problems (which seems to occur with some pairs). I also opened an issue in the NostalgiaForInfinityX5 strategy project: iterativv/NostalgiaForInfinity#438 I just restarted FT with other problems extracted from logs: I think this is caused by some compatibility issue between ccxt and Bitget API... anyway, any help is welcome :) Thankyou |
|
I started freqtrade with not so useful, I think |
|
What's a
If that were the case, i'd think you'd encounter the same problem when buying. At any rate, that would be a ccxt problem. You can pretty much try an order manually with ccxt with the following code (make sure to eventually close the position on exchange - as that's obviously not tracked by freqtrade). import ccxt
exchange = ccxt.bitget({
'apiKey': '<yourApiKey>',
'secret': '<yoursecret>',
})
lm = exchange.load_markets()
exchange.verbose = True
res = exchange.create_order(
'<pair of your liking',
'market',
'sell', # or buy?
amount,
None, # or a rate if using limit
)
print(res)I did notice the strategy you're using - continuing after a few months essentially means it's a new strategy considering it's changing several times per day - so it's quite likely that limits were adjusted so the remainder is smaller - or anything similar to this. What you can try to confirm this: once that order fills, do a forceexit (limit or market) - and see if the position exists correctly when using a bigger amount. |
This comment has been minimized.
This comment has been minimized.
|
I'll close this as there's been no further feedback. If you figure something out around this - feel free to comment below so we can take a look - though considering it's not a supported / tested exchange - the things we can do for you will probably be limited. |
Describe your environment
Describe the problem:
Hi,
I'm experiencing an issue occurring with some pairs (bitget exchange):
follow a brief of freqtrade log:
why if the pair is PUFFER/USDT bitget complain about 0PUFFER ? is a ccxt/bitget problem?
how can I discover and blacklist the problematic pairs from the trading list before using? (It seems to only happen with new listed pairs at moment)
this is another pair with problems: LUCE/USDT (same error: 0LUCE can be used at most?)
Thank you for the support
Kind Regards
Steps to reproduce:
The text was updated successfully, but these errors were encountered: