PyCryptoBot v7

[whittlem]

PyCryptoBot v7 is a major update. It's currently in beta for testing. If you find any issues or bugs please let me know here.

git reset --hard
git checkout beta
git pull
python3 -m pip install -r requirements.txt -U

[whittlem]

Issue raised from Telegram:

Hi,

Running pycryptobot Rev7, via Telegram. When starting the market scanner, I encountered the following error:

  File "/home/bots/rev7/pycryptobot/models/telegram/actions.py", line 453, in start_market_scan
    exchange_bots_started = self.helper.exchange_bot_ruuning_count(ex)
AttributeError: 'TelegramHelper' object has no attribute 'exchange_bot_ruuning_count' 

At first the incorrect spelling of "running" gave me a run around. But the spelling was consistently wrong.

I changed line 453 in actions.py to the following to fix it (added 'get_'):
exchange_bots_started = self.helper.get_exchange_bot_ruuning_count(ex)

Please have a look at your code and verify if that correction must be added.

[whittlem]

This should be fixed in v7.0.28. Please confirm.

[whittlem]

Issue raised from Telegram:

On another note: I did a fresh installation of Linux recently and noticed that regex is required - but it is not in the requirements.txt file.
Perhaps worth adding it there for completeness sake.

[whittlem]

This has been fixed already. Do a "git pull"

[whittlem]

Issue raised from Telegram:

When running the simulator, I am getting KeyError(1) message. The simulator will pause for a while while the yellow text is flashing.

It will continue after some time and then crash with a KeyError(2) message

[whittlem]

Can you please provide the config / command you ran to get this error?

[IGGI923]

I'm at the new beta and get this error:
Restarting application after exception: AttributeError("'TechnicalAnalysis' object has no attribute 'add_all'")
AttributeError("'TechnicalAnalysis' object has no attribute 'add_all'")

Tried to test the bot with this command:
python3 pycryptobot.py --market LTCBUSD --sim fast-sample --simstartdate "2022-10-10" --simenddate now --verbose 1

[whittlem]

I'll set up a key on Binance and see what it says. It is possible maybe I have a bug there but I'll check. Thanks guys

[whittlem]

I have not got this using Binance in test or sim modes. I will try live tonight and see what happens.

[whittlem]

Ok, guys... trying Binance live and see the issue.

pycryptobot % python3 pycryptobot.py --exchange binance
Bot1 2023-01-08 19:35:54 ADAUSDT 15m Error: GET (401) https://api.binance.com/api/v3/account - Invalid API-key, IP, or permissions for action.
Bot1 2023-01-08 19:35:54 ADAUSDT 15m Error: GET (401) https://api.binance.com/api/v3/account - Invalid API-key, IP, or permissions for action.
Bot1 2023-01-08 19:35:55 ADAUSDT 15m Error: GET (401) https://api.binance.com/api/v3/account - Invalid API-key, IP, or permissions for action.
Bot1 2023-01-08 19:35:55 ADAUSDT 15m Error: GET (401) https://api.binance.com/api/v3/allOrders - Invalid API-key, IP, or permissions for action.
Bot1 2023-01-08 19:35:55 ADAUSDT 15m Insufficient Funds! (ADA=0.0, USDT=0.0)

I will investigate and fix it this evening.

[whittlem]

This is fixed in v7.0.20

[IGGI923]

This error doesn't appear anymore. Now i get this one.

[i0on]

Hello. i use binance. standard parameters - I prescribe only a couple of BTC - USDT and my keys to the file. maybe this is not a beta problem, but when I try to run the bot, I get this

Bot1 2023-01-05 08:44:52 BTCUSDT 1h Error: GET (400) https://api.binance.com/api/v3/account - Not all sent parameters were read; read '2' parameter(s) but was sent '3'.
Bot1 2023-01-05 08:44:53 BTCUSDT 1h Error: GET (400) https://api.binance.com/api/v3/allOrders - Not all sent parameters were read; read '3' parameter(s) but was sent '4'.
Bot1 2023-01-05 08:44:53 BTCUSDT 1h Insufficient Funds! (BTC=0.0, USDT=0.0)
Bot1 2023-01-05 08:44:53 BTCUSDT 1h Insufficient funds, ignoring buy signal.

[whittlem]

I will take a look. Is this running the bot in live mode?

[whittlem]

Ok, switching to live I see it as well. I will fix it this evening.

pycryptobot % python3 pycryptobot.py --exchange binance
Bot1 2023-01-08 19:35:54 ADAUSDT 15m Error: GET (401) https://api.binance.com/api/v3/account - Invalid API-key, IP, or permissions for action.
Bot1 2023-01-08 19:35:54 ADAUSDT 15m Error: GET (401) https://api.binance.com/api/v3/account - Invalid API-key, IP, or permissions for action.
Bot1 2023-01-08 19:35:55 ADAUSDT 15m Error: GET (401) https://api.binance.com/api/v3/account - Invalid API-key, IP, or permissions for action.
Bot1 2023-01-08 19:35:55 ADAUSDT 15m Error: GET (401) https://api.binance.com/api/v3/allOrders - Invalid API-key, IP, or permissions for action.
Bot1 2023-01-08 19:35:55 ADAUSDT 15m Insufficient Funds! (ADA=0.0, USDT=0.0)

I will investigate and fix it this evening.

[whittlem]

This is fixed in v7.0.20

[afgvdp]

I ran the v7.0.20, the problem with the Binance API is fixed. Thank you!

[afgvdp]

I am trying to run Telegram_bot.py in v7.0.25, but I get this error when the bot tries to open a Bot with and old open trade:

PS: If it helps, when I start a new bot manually from Telegram, it works properly.

Config:

{
"binance": {
"api_url": "https://api.binance.com",
"api_key_file": "binance.key",
"config": {
"live": 1,
"sellatloss": 0,
"sellatresistance": 0,
"trailingstoploss": -1.5,
"trailingstoplosstrigger": 5,
"nosellmaxpcnt": 3,
"nosellminpcnt": -3,
"disablebullonly": 1,
"disablebuynearhigh": 1,
"disablebuymacd": 0,
"disablebuyobv": 1,
"disablebuyelderray": 0,
"disablefailsafefibonaccilow": 1,
"disableprofitbankreversal": 0,
"disabletracker": 1,
"disabletelegram": 0,
"autorestart": 1,
"graphs": 0,
"verbose": 0,
"stats": 0,
"enableinsufficientfundslogging": 1,
"enabletelegrambotcontrol": 1,
"websocket": 1,
"disablelog": 0,
"buymaxsize": 0,
"buypercent": 15,
"buyminsize": 0,
"sellsmartswitch": 0,
"trailingbuypcnt": 0.5,
"telegramtradesonly": 0,
"enableml": 0,
"use_sell_fee": 1
}
},
"scanner": {
"atr72_pcnt": 2.0,
"enableexitaftersell": 1,
"enableleverage": 1,
"use_default_scanner": 1,
"maxbotcount": 20,
"exchange_bot_count": 20,
"autoscandelay": 6,
"enable_buy_next": 1,
"autostart": 1,
"terminal_start_process": ""
},
"logger": {
"filelog": 1,
"logfile": "pycryptobot.log",
"fileloglevel": "DEBUG",
"consolelog": 1,
"consoleloglevel": "INFO"
}
}

[afgvdp]

More details, telegram log:

2023-01-14 15:02:30,461 - telegram.helper - DEBUG - cleandata started
2023-01-14 15:02:30,462 - telegram.helper - DEBUG - METHOD(get_active_bot_list) - DATA(active)
2023-01-14 15:02:30,463 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
2023-01-14 15:02:30,463 - telegram.helper - DEBUG - cleandata complete
2023-01-14 15:02:30,714 - telegram.helper - INFO - Telegram Bot is listening
2023-01-14 15:02:31,218 - telegram.helper - INFO - called start_open_orders
2023-01-14 15:02:31,409 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(BONDUSDT)
2023-01-14 15:02:31,409 - telegram.helper - DEBUG - METHOD(start_process) - DATA(BONDUSDT, binance, , telegram-open)
2023-01-14 15:02:31,410 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(BONDUSDT)
2023-01-14 15:02:41,441 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(TORNUSDT)
2023-01-14 15:02:41,441 - telegram.helper - DEBUG - METHOD(start_process) - DATA(TORNUSDT, binance, , telegram-open)
2023-01-14 15:02:41,441 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(TORNUSDT)
2023-01-14 15:02:51,466 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(CVPUSDT)
2023-01-14 15:02:51,466 - telegram.helper - DEBUG - METHOD(start_process) - DATA(CVPUSDT, binance, , telegram-open)
2023-01-14 15:02:51,466 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(CVPUSDT)
2023-01-14 15:03:02,827 - telegram.helper - DEBUG - METHOD(get_active_bot_list) - DATA(active)
2023-01-14 15:03:02,827 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
2023-01-14 15:03:03,027 - telegram.helper - INFO - called start_market_scan - scanner.py
2023-01-14 15:03:03,027 - telegram.helper - DEBUG - METHOD(read_config)
2023-01-14 15:03:03,218 - telegram.helper - INFO - Starting Market Scan
2023-01-14 15:19:22,462 - telegram.helper - DEBUG - Fido checking for hung bots..
2023-01-14 15:19:22,462 - telegram.helper - DEBUG - METHOD(get_hung_bot_list) - DATA(active)
2023-01-14 15:19:22,462 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
2023-01-14 15:19:22,654 - telegram.helper - DEBUG - stopping bots
2023-01-14 15:19:22,654 - telegram.helper - DEBUG - METHOD(get_active_bot_list) - DATA(active)
2023-01-14 15:19:22,655 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
2023-01-14 15:19:22,655 - telegram.helper - DEBUG - METHOD(get_active_bot_list_with_open_orders) - DATA(active)
2023-01-14 15:19:22,656 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
2023-01-14 15:19:22,656 - telegram.helper - DEBUG - METHOD(get_manual_started_bot_list) - DATA(telegram)
2023-01-14 15:19:22,657 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
2023-01-14 15:19:22,658 - telegram.helper - DEBUG - METHOD(get_active_bot_list) - DATA(active)
2023-01-14 15:19:22,658 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
2023-01-14 15:19:22,660 - telegram.helper - DEBUG - METHOD(get_exchange_bot_ruuning_count) - DATA(binance)
2023-01-14 15:19:22,660 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
2023-01-14 15:19:22,662 - telegram.helper - DEBUG - METHOD(get_exchange_bot_ruuning_count) - RETURN(0)
2023-01-14 15:19:22,853 - telegram.helper - INFO - starting binance - (USDT) bots
2023-01-14 15:19:22,857 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(MITHUSDT)
2023-01-14 15:19:22,858 - telegram.helper - DEBUG - METHOD(start_process) - DATA(MITHUSDT, binance, , scanner)
2023-01-14 15:19:22,858 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(MITHUSDT)
2023-01-14 15:19:28,888 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(ANCUSDT)
2023-01-14 15:19:28,888 - telegram.helper - DEBUG - METHOD(start_process) - DATA(ANCUSDT, binance, , scanner)
2023-01-14 15:19:28,889 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(ANCUSDT)
2023-01-14 15:19:35,138 - telegram.helper - DEBUG - Ignoring (LINKDOWNUSDT) Leverage Pairs (enableleverage is disabled)...
2023-01-14 15:19:35,139 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(REPUSDT)
2023-01-14 15:19:35,151 - telegram.helper - DEBUG - METHOD(start_process) - DATA(REPUSDT, binance, , scanner)
2023-01-14 15:19:35,160 - telegram.helper - DEBUG - METHOD(is_bot_running) - DATA(REPUSDT)
2023-01-14 15:26:06,121 - telegram.helper - INFO - Market Scan Complete
2023-01-14 15:50:44,397 - telegram.helper - DEBUG - METHOD(read_config)
2023-01-14 15:50:45,805 - telegram.helper - DEBUG - METHOD(get_active_bot_list) - DATA(active)
2023-01-14 15:50:45,806 - telegram.helper - DEBUG - METHOD(get_all_bot_list)

[afgvdp]

More details, telegram screenshot:

[whittlem]

This should be fixed in v7.0.28. Please confirm.

[afgvdp]

Yep, all good. Thanks legends!

[afgvdp]

I've found some issues in the Telegram App (I will be posting them):

1. No matter how many bots are open the Bot Count is (0). It does not recognize the active ones.
2. Everytime the telegram_bot runs the scanner, let's say every 6 hours, it opens all the bots, regardless of the ones already opened in the last scan.

It looks like the Telegram_Bot doesn't check for the bots or orders already opened.

[whittlem]

This may have been fixed by @markhollingworth in v7.0.28. Please confirm.

[afgvdp]

Yep, all good. Thanks legends!

[ArlanovCsb]

Hi. I got this error AttributeError("'PyCryptoBot' object has no attribute 'notifyTelegram'"). It happened when i ran the simulation and enabled the setting —"telegram": 1. Without it everything is fine.

[whittlem]

This should be fixed in v7.0.28. Please confirm.

[rsameys]

think i found an error in ''default_parser.py' related to config settings 'preventlosstrigger' & 'preventlossmargin'
Had these settings in my 'config.json' but i noticed that the default values were used.

Original code in 'default_parser.py'

    config_option_float(option_name="preventlosstrigger", option_default=1.0, store_name="nobuynearhighpcnt", value_min=0, value_max=100)
    config_option_float(option_name="preventlossmargin", option_default=0.1, store_name="nobuynearhighpcnt", value_min=0, value_max=100)

After i updated the code, my settings were taken instead of the default vallues.

    config_option_float(option_name="preventlosstrigger", option_default=1.0, store_name="preventlosstrigger", value_min=0, value_max=100)
    config_option_float(option_name="preventlossmargin", option_default=0.1, store_name="preventlossmargin", value_min=0, value_max=100)

[whittlem]

Not sure how I missed that. Thanks for reporting it. It's going to be fixed in the version I am releasing now.

[rsameys]

Such things happen. Have been a developer on IBM System 38 in my early
days before i became a support/system engineer. ;-)

Is also got errors when starting my Telegram bot with the message tat
only 'standard', 'scanner', 'telegram' were valid as 'starting method'.
When i changed in the code of "/models/telegram/actions.py"
''telegram-open" into "telegram" the errors were gone. Is this also a bug?

def start_open_orders(self, update, context):
"""Start bots for open trades (data.json)"""
self.helper.logger.info("called start_open_orders")
self.helper.send_telegram_message(update, "<b>Starting markets with open
trades..</b>", context=context, new_message=False)
self.helper.read_data()
for market in self.helper.data["opentrades"]:
if not self.helper.is_bot_running(market):
self.helper.start_process(
market,
self.helper.data["opentrades"][market]["exchange"],
"",
 "telegram-open",
)
sleep(10)
self.helper.send_telegram_message(update, "<i>Markets have been started</i>",
context=context)
sleep(1)
self.get_bot_info(None, None)

[afgvdp]

This one solved a problem for "open trades". Thank you!

[afgvdp]

Hi, I am getting this error lately for all my bots (websocket is enabled):

2023-02-05 23:19:37 HIVEUSDT 1h ConnectionError: https://api.binance.com
Bot1 2023-02-05 23:19:37 HIVEUSDT 1h Error: 'serverTime'
Bot1 2023-02-06 00:01:53 HIVEUSDT 1h Error: GET (400) https://api.binance.com/api/v3/allOrders - Timestamp for
this request is outside of the recvWindow. (hint: increase recvWindow with
--recvwindow <5000-60000>)

[whittlem]

Binance expects a response within a certain timeframe. If it doesn't complete in time it fails. The limits are quite low by default and if your connection to them is slow you need to increase it. Start your bot with something like --recvwindow 20000

Just increase or decrease it until you find the lowest value which works. This isn't a bot issue but the bot has options to resolve it.

You can also add the "recvwindow" option to your Binance configuration.

[afgvdp]

Hi, thank you, all set, let see how it perfoms :)

[afgvdp]

When running the scan, I get the following:

Programs\Python\Python310\lib\site-packages\pandas\core\dtypes\astype.py:189: RuntimeWarning: invalid value encountered in cast
return values.astype(dtype, copy=copy)

Then it works, but it appears not to be working properly when is launched from Telegram.

Thank you!

[afgvdp]

That's what happens when I try to launch the Scanner from the telegram:

2023-02-14 01:57:59,317 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
argument of type 'NetworkError' is not iterable
2023-02-14 16:13:01,772 - telegram.helper - ERROR - Exception while handling an update:
Traceback (most recent call last):
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\connectionpool.py", line 614, in urlopen
httplib_response = self._make_request(conn, method, url,
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\connectionpool.py", line 402, in _make_request
six.raise_from(e, None)
File "", line 2, in raise_from
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\connectionpool.py", line 398, in _make_request
httplib_response = conn.getresponse()
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\http\client.py", line 1374, in getresponse
response.begin()
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\http\client.py", line 318, in begin
version, status, reason = self._read_status()
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\http\client.py", line 287, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\utils\request.py", line 259, in _request_wrapper
resp = self._con_pool.request(*args, **kwargs)
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\request.py", line 68, in request
return self.request_encode_body(method, url, fields=fields,
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\request.py", line 148, in request_encode_body
return self.urlopen(method, url, **extra_kw)
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\poolmanager.py", line 244, in urlopen
response = conn.urlopen(method, u.request_uri, **kw)
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\connectionpool.py", line 665, in urlopen
retries = retries.increment(method, url, error=e, _pool=self,
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\util\retry.py", line 347, in increment
raise six.reraise(type(error), error, _stacktrace)
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\packages\six.py", line 685, in reraise
raise value.with_traceback(tb)
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\connectionpool.py", line 614, in urlopen
httplib_response = self._make_request(conn, method, url,
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\connectionpool.py", line 402, in _make_request
six.raise_from(e, None)
File "", line 2, in raise_from
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\vendor\ptb_urllib3\urllib3\connectionpool.py", line 398, in _make_request
httplib_response = conn.getresponse()
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\http\client.py", line 1374, in getresponse
response.begin()
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\http\client.py", line 318, in begin
version, status, reason = self._read_status()
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\http\client.py", line 287, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
telegram.vendor.ptb_urllib3.urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\ext\updater.py", line 646, in _network_loop_retry
if not action_cb():
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\ext\updater.py", line 597, in polling_action_cb
updates = self.bot.get_updates(
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\ext\extbot.py", line 222, in get_updates
updates = super().get_updates(
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\bot.py", line 130, in decorator
result = func(*args, **kwargs)
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\bot.py", line 2861, in get_updates
self._post(
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\bot.py", line 295, in _post
return self.request.post(
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\utils\request.py", line 356, in post
result = self._request_wrapper(
File "XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\telegram\utils\request.py", line 265, in _request_wrapper
raise NetworkError(f'urllib3 HTTPError {error}') from error
telegram.error.NetworkError: urllib3 HTTPError ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

Then, I get this on Telegram:

It seems that it's not working and takes the results of an old scanner.

Thank you!!

[afgvdp]

To complete the info, I have deleted the repository and cloned it again. Now, if I run the scanner manually, I get the following:

C:\PyCryptoBot\pycryptobot>scanner.py
C:XXXXXX\AppData\Local\Programs\Python\Python310\lib\site-packages\pandas\core\dtypes\astype.py:189: RuntimeWarning: invalid value encountered in cast
return values.astype(dtype, copy=copy)
Processing, please wait...
[1/421] 1INCHDOWNUSDT 0.24%
.
.
.
[421/421] ZRXUSDT 100.0%
←[2J
C:\PyCryptoBot\pycryptobot\scanner.py:110: FutureWarning: In a future version, object-dtype columns with all-bool values will not be included in reductions with bool_only=True. Explicitly cast to bool dtype instead.
print(
C:\PyCryptoBot\pycryptobot\scanner.py:110: FutureWarning: In a future version, object-dtype columns with all-bool values will not be included in reductions with bool_only=True. Explicitly cast to bool dtype instead.
print(
price volume atr72 atr72_pcnt buy_next
market
MITHUSDT 0.00345000 1714480 0.00030139 8.74000000 True
ANCUSDT 0.03151000 6645414 0.00147486 4.68000000 True
KEYUSDT 0.00443300 3621760 0.00019225 4.34000000 True
BEAMUSDT 0.06520000 3353735 0.00237500 3.64000000 True
BNBDOWNUSDT 0.01284000 625929 0.00041986 3.27000000 True

The interesting thing is that the pair MITHUSDT is not in Binance Spot anymore, neither ANCUSDT.

I don't know what it's happening.

Thank you for your help.

[afgvdp]

Definetly there is something wring with the Scanner. These are 2 different the scanner results, with a timeframe of 24h between them:

MITHUSDT 0.00345000 1714480 0.00030139 8.74000000 True
ANCUSDT 0.03151000 6645414 0.00147486 4.68000000 True
KEYUSDT 0.00443300 3621760 0.00019225 4.34000000 True
BEAMUSDT 0.06520000 3353735 0.00237500 3.64000000 True
BNBDOWNUSDT 0.01284000 625929 0.00041986 3.27000000 True

I think there is some bug in it, the 3 first results are just the same, which is pretty rare:

C:\PyCryptoBot\pycryptobot\scanner.py:110: FutureWarning: In a future version, object-dtype columns with all-bool values will not be included in reductions with bool_only=True. Explicitly cast to bool dtype instead.
print(
C:\PyCryptoBot\pycryptobot\scanner.py:110: FutureWarning: In a future version, object-dtype columns with all-bool values will not be included in reductions with bool_only=True. Explicitly cast to bool dtype instead.
print(
price volume atr72 atr72_pcnt buy_next
market
MITHUSDT 0.00345000 1714480 0.00030139 8.74000000 True
ANCUSDT 0.03151000 6645414 0.00147486 4.68000000 True
KEYUSDT 0.00443300 3621760 0.00019225 4.34000000 True
MDTUSDT 0.05435000 21145021 0.00229014 4.21000000 True
HFTUSDT 0.68740000 35368221 0.02829861 4.12000000 True

[afgvdp]

Hi Mark, Michael, I think I found a bug in the Telegram Bot, related to the Open Trades.

When I deleted and cloned the repository again the "opentrades" variable is missing in the data.json

{
"trades": {},
"markets": {},
"scannerexceptions": {},

Getting this error:

2023-02-15 23:14:13,239 - telegram.helper - DEBUG - METHOD(write_data) - DATA(data.json)
2023-02-15 23:14:13,247 - telegram.helper - DEBUG - cleandata started
2023-02-15 23:14:13,247 - telegram.helper - DEBUG - METHOD(get_active_bot_list) - DATA(active)
2023-02-15 23:14:13,247 - telegram.helper - DEBUG - METHOD(get_all_bot_list)
2023-02-15 23:14:13,248 - telegram.helper - DEBUG - cleandata complete
2023-02-15 23:14:13,458 - telegram.helper - INFO - Telegram Bot is listening
2023-02-15 23:14:13,952 - telegram.helper - INFO - called start_open_orders
Traceback (most recent call last):
File "C:\PyCryptoBot\pycryptobot\telegram_bot.py", line 921, in
main()
File "C:\PyCryptoBot\pycryptobot\telegram_bot.py", line 912, in main
botconfig.actions.start_open_orders(None, None)
File "C:\PyCryptoBot\pycryptobot\models\telegram\actions.py", line 74, in start_open_orders
for market in self.helper.data["opentrades"]:
KeyError: 'opentrades'

If I add it to the data.json file in the Datafolder, seems to work:

{
"trades": {},
"markets": {},
"scannerexceptions": {},
"opentrades": {}

Thank you.

[NGxDTV]

[Nicolas469]

Hi,

You can use logwidth and termwidth and set them both to 420 (that's the max value).

[NGxDTV]

Ouhmann.. Sorry. Thank you haha. I just didn't see it. Have a great day! :)

[NGxDTV]

[whittlem]

I will take a look. Can you share your config.json and the way you are running your bot? Or what you run that gives you that error so I can re-create it.

[NGxDTV]

I have tried several startup options, even the simplest one throws an error:

"--exchange kucoin --market BTC-USDT --sim fast --bbands_s1 1"

Here's the config (without scanner or telegram):

{
"kucoin": {
"api_url": "https://api.kucoin.com/",
"api_key_file": "kucoin.key",
"config" : {
"base_currency" : "ETC",
"quote_currency" : "USDT",
"live" : 0,
"websocket" : 0,
"buymaxsize": 10,
"buylastsellsize": 1,
"trailingbuypcnt": 0.5,
"dynamictsl": 1,
"trailingstoplosstrigger": 3,
"trailingstoploss": -1,
"tslmultiplier": 1.5,
"tsltriggermultiplier": 1.5,
"tslmaxpcnt": -5,
"trailingsellpcnt": -0.25,
"trailingsellimmediatepcnt": -1,
"trailingsellbailoutpcnt": -2.5,
"sellatloss": 1,
"selllowerpcnt": -2,
"preventloss": 1,
"preventlosstrigger": 1.25,
"preventlossmargin": 0.5,
"enable_pandas_ta": 1,
"enable_custom_strategy": 1,
"disablebullonly" : 1,
"disablebuynearhigh" : 1,
"disablebuymacd": 1,
"disablebuyema": 1,
"disablebuyobv": 1,
"disablebuyelderray": 1,
"disablefailsafefibonaccilow": 1,
"disableprofitbankreversal": 1,
"disabletracker" : 1,
"autorestart" : 1,
"enableinsufficientfundslogging": 1,
"telegrambotcontrol" : 1
}
}
}

There were no problems with Coinbase Pro, but I couldn't try it with the key because Coinbase Pro no longer exists for trading.

Thank you in advance!

[NGxDTV]

At --exitaftersell, it triggers even though no purchase was made:

Bot1 2023-03-09 09:25:00 ETC-USDT 5min 2023-03-09 09:25:00 | ETC-USDT | 5min | 18.2226 | SELL
Bot1 2023-03-09 09:25:00 ETC-USDT 5min ETC balance before order: 0.0
Bot1 2023-03-09 09:25:00 ETC-USDT 5min USDT balance before order: 53.4918
Bot1 2023-03-09 09:25:00 ETC-USDT 5min ETC balance after order: 0.0
Bot1 2023-03-09 09:25:00 ETC-USDT 5min USDT balance after order: 53.4918
Bot1 2023-03-09 09:29:39 ETC-USDT 5min Exit after sell! ("exitaftersell" is enabled)

For some reason, it is a static bool. You can't use --ema1226 or --macdsignal on KuCoin either. But exitaftersell doesn't make much sense for Docker.

minbuy is also set to 10.0
and max is set to 15.0

Since it's just a test. But for ETC, it is already stated that the last action was "BUY".

Thank you in advance! :)

[chingchungho]

I have had the bot running with docker-compose. It runs on coinbase with base and quote currency of ADA and EUR. However, when I run "python3 pycryptobot.py --statdetail 1" inside the container shell. I found that the Exchange value is "dummy", the market is "BTC-GBP" and the Bot Mode is "TEST". Which is totally different to my config.json's settings.

[chingchungho]

The last issue was gone after I updated to the latest version. But this time I get the error of unable to read coinbase.key

Traceback (most recent call last):
File "/app/pycryptobot.py", line 21, in
main()
File "/app/pycryptobot.py", line 12, in main
app = PyCryptoBot()
File "/app/controllers/PyCryptoBot.py", line 78, in init
super(PyCryptoBot, self).init(filename=self.config_file, exchange=exchange)
File "/app/models/BotConfig.py", line 180, in init
self.read_config()
File "/app/models/BotConfig.py", line 226, in read_config
coinbaseConfigParser(self, self.config[self.exchange.value], self.cli_args)
File "/app/models/config/coinbase_parser.py", line 66, in parser
raise RuntimeError(f"Unable to read {app.api_key_file}")
RuntimeError: Unable to read coinbase.key

[chingchungho]

The above issue was resolved after I mapped the config.key file to the container /app folder.

[chingchungho]

The latest issue:
I didn't get my docker bot run on coinbase with the error of insufficient funds where I should have funds inside for ADA-EUR market.