You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
---
TRADE_OPTIONS:
KUCOIN_ANNOUNCEMENTS: TrueQUANTITY: 50PAIRING: USDTTEST: TrueSL: -3TP: 2ENABLE_TSL: TrueTSL: -4TTP: 2LOGGING:
LOG_LEVEL: DEBUGLOG_FILE: bot.logLOG_TO_CONSOLE: TrueTELEGRAM:
ENABLED: TrueNOTIFICATIONS:
STARTUP: True # welcome messageCOIN_ANNOUNCEMENT: True # detected new announcementCOIN_NOT_SUPPORTED: True # coin is not on gate.ioBUY_START: True # when entering positionBUY_ORDER_CREATED: True # when buy order is createdBUY_FILLED: True # when the buy order got filledSELL_START: True # when starting to sell SELL_FILLED: True # when sold
The text was updated successfully, but these errors were encountered:
Describe the bug
I have been trying this bot awhile and just noticed a case that bot bought API3 at highest price
4.982
and sold with-1.534 profit
.The Binance API says it released at
Fri Jan 21 2022 06:28:04 GMT+0000
but bot noticed this at06:28:29
(Telegram mesage timestamp).Actual behavior
Telegram message logs:
06:28:29
: New announcement detected: API306:28:33
: New announcement detected: API306:28:34
: starting buy placeorder with : announcementcoin='API3' | globals.pairing='USDT' | volume=33.0 | amount=6.623845845042151 x price='4.982' | side = buy | status='cancelled'06:28:34
: Order on API3 closed06:30:42
: sold API3 with -1.534 profit | -3.031% PNLExpected behavior
I'm not sure how we should tackle this problem but how about:
releaseDate
andtime.now
greater or equal than%d {seconds, minutes}
%%d
pump (during the starting buy stage) compared to%d {seconds, minutes}
agoor
modeScreenshots
https://www.tradingview.com/x/lLso7vnj/
Logs
-
Additional context
My config:
The text was updated successfully, but these errors were encountered: