BadRequest error when using the /stats command about pycryptobot

[whittlem]

I may have fixed this already. Can you tell me the exact command and config you are using?

[alangrima]

Just updated but still getting the same error
This happens when running the /stats command for a pair on binance selected by the scanner. It also seems that the data.json does not contain any details.

Here is the config:

{
"binance": {
"api_url": "https://api.binance.com",
"config": {
"autorestart": 1,
"base_currency": "ETH",
"disablebuynearhigh": 1,
"enableinsufficientfundslogging": 1,
"enabletelegrambotcontrol": 1,
"granularity": "15m",
"live": 0,
"nobuynearhighpcnt": 1,
"nosellmaxpcnt": 3,
"nosellminpcnt": -9,
"quote_currency": "EUR",
"sellatresistance": 1,
"selllowerpcnt": -12,
"telegram": 1,
"trailingbuypcnt": 1,
"trailingstoploss": -1,
"trailingstoplosstrigger": 3,
"verbose": 0,
"websocket": 0,
"enable_pandas_ta": 1,
"autorestart": 1,
"graphs": 0,
"verbose": 1,
"stats": 0,
"enableinsufficientfundslogging": 1,
"enabletelegrambotcontrol": 1,
"disablelog": 0,
"buymaxsize": 20,
"buylastsellsize": 0,
"buyminsize": 0,
"sellsmartswitch": 0,
"granularity": 300
},
"api_key_file": "binance.key"
},
"coinbasepro": {
"api_url": "https://api.exchange.coinbase.com",
"config": {
"autorestart": 1,
"base_currency": "SHIB",
"disablebuynearhigh": 1,
"enableinsufficientfundslogging": 1,
"enabletelegrambotcontrol": 1,
"granularity": "15m",
"live": 0,
"nobuynearhighpcnt": 1,
"nosellmaxpcnt": 3,
"nosellminpcnt": -9,
"quote_currency": "EUR",
"sellatresistance": 1,
"selllowerpcnt": -12,
"telegram": 1,
"trailingbuypcnt": 1,
"trailingstoploss": -1,
"trailingstoplosstrigger": 3,
"verbose": 0,
"websocket": 0
},
"api_key_file": "coinbasepro.key"
},
"telegram" : {
"token" : "token",
"client_id" : "clientid",
"user_id" : "userid"
},
"scanner": {
"atr72_pcnt": 1.0,
"use_default_scanner": 1,
"enableexitaftersell": 1,
"enableleverage": 0,
"maxbotcount": 5,
"autoscandelay": 6,
"enable_buy_next": 1
}
}

[whittlem]

Ok, so you mean via the Telegram bot? You run /stats and you get an error?

[whittlem]

I have been able to re-create the issue but it's a bit of a strange case.

[whittlem]

It's fixed in v7.0.34