According to Github there are 333 of you regularly updating your bots. I'm glad you are finding it useful :)

I was just curious how all of you are doing?

1. Which exchange(s) are you using? Coinbase Pro, Binance, or both?
2. How many bots are you running?
3. How much are you trading per bot?
4. Which markets are you trading?
5. What config is working well for you?

I'll start off...

1. I'm using Coinbase Pro only
2. I have 5 bots running (in case you didn't see Coinbase Pro now supports 10 portfolios!)
3. Up until yesterday I was trading £500 per bot. When ever the bots have a successful trade I transfer the profits to my bank account. I increased this to £1500 a bot yesterday.
4. I'm trading "ADA-GBP", "BCH-GBP", "BTC-GBP", "ETH-GBP", and "LTC-GBP". I was trading "XLM-EUR" but I found it too unreliable, too volatile for my liking. From my analysis ADA looks like a better option as it looks more stable and also more independent from Bitcoin and Ethereum.
5. I'm actually trying out a new config from this morning. I have disabled "sellatloss" for a few weeks and it has been working really well for me. The change I made this morning was to "disablebullonly", "disablebuyobv", and "disablebuyelderray". The reason I disabled them is because they were there to prevent losses but I have "sellatloss" disabled so they are redundant with that on. I would rather be more liberal with my trades and trade more often. So I'm only using EMA crossovers and MACD with sell at loss disabled. I'll let you know how this works out.

As an example my BTC-GBP config.json looks like this (with my keys removed):

{
    "coinbasepro" : {
        "api_url" : "https://api.pro.coinbase.com",
        "api_key" : "",
        "api_secret" : "",
        "api_passphrase" : "",
        "config" : {
            "base_currency" : "BTC",
            "quote_currency" : "GBP",
            "live" : 1,
            "sellatloss" : 0,
            "disablebullonly" : 1,
            "disablebuyobv" : 1,
            "disablebuyelderray" : 1
        }
    },
    "telegram" : {
        "token" : "",
        "client_id" : ""
    }
}

Hi All,

when the Bot was started it did not respect the buymaxsize present within the configurations and bought for the entire amount of the quote_currency.

"config" : { "base_currency" : "ADA", "quote_currency" : "USDT", "buymaxsize": 500, .... }

Regards.

Hi all, I just observed this message and the trade didn't happen:

BNB balance before order: 0.2927 BUSD balance before order: 0.0 04-05-2021 00:33:51 Binance marketSell list indices must be integers or slices, not str BNB balance after order: 0.2927 BUSD balance after order: 0.0

Running as:

                         Python Crypto Bot                                

           Release : v2.0.0 (commit: 6)                                   

          Bot Mode : LIVE - live trades using your funds!                 
       Bot Started : 2021-05-03 23:53:14.090838                           

      Sell At Loss : 1  --sellatloss 1                                    
 Sell At Resistance : True  --sellatresistance                            
   Trade Bull Only : True  --disablebullonly                              
     Buy Near High : True  --disablebuynearhigh                           
      Use Buy MACD : True  --disablebuymacd                               
       Use Buy OBV : True  --disablebuyobv                                
 Use Buy Elder-Ray : True  --disablebuyelderray                           
Sell Fibonacci Low : True  --disablefailsafefibonaccilow
Sell Fibonacci High : True  --disableprofitbankfibonaccihigh
Candlestick Reversal : True  --disableprofitbankreversal                    
          Telegram : True  --disabletelegram                              
               Log : True  --disablelog                                   
           Tracker : True  --disabletracker                               

*** smart switch from granularity '1h' (1 hour) to '15m' (15 min) ***

Describe the bug When attempting to run the container from the image repository using the below settings it fails with the following errors down in the container logs. This suggests that I am attempting to run a x86/x64 image on an armhf system which is likely as I am using the one from the image repository hosted in this repo.

I have also attempted to build the container for armhf and failed spectacularly. (see followup post in this report. )

btcusd    | 2021-11-24T19:38:48.485305374Z standard_init_linux.go:228: exec user process caused: exec format error
btcusd    | 2021-11-24T19:38:54.600144045Z standard_init_linux.go:228: exec user process caused: exec format error
btcusd    | 2021-11-24T19:39:01.195989348Z standard_init_linux.go:228: exec user process caused: exec format error

To Reproduce docker-compose.yml

version: "3.9"

services:
  btcusd:
    image: ghcr.io/whittlem/pycryptobot/pycryptobot:latest
    container_name: btcusd
    volumes:
      - ./market/binance.key:/app/keys/binance.key:ro
      - ./market/BTCBUSD/config.json:/app/config.json
      - ./market/BTCBUSD/pycryptobot.log:/app/pycryptobot.log
      - ./market/BTCBUSD/graphs:/app/graphs
      - /etc/localtime:/etc/localtime:ro
    environment:
      - PYTHONUNBUFFERED=1
    restart: always

config.json

{
    "binance": {
        "api_url": "https://api.binance.com",
        "config": {
            "base_currency": "BTC",
            "quote_currency": "BUSD",
            "live": 0,
            "sellatloss": 1,
            "disablelog": 0,
            "autorestart": 0,
            "enableinsufficientfundslogging": 1,
            "logbuysellinjson": 1,
            "graphs": 1,
            "websocket": 0,
            "stats": 0,
            "verbose": 1,
            "consolelog": 1,
            "consoleloglevel": "DEBUG"
        },
        "api_key_file": "/app/keys/binance.key"
    }
}

Expected behavior Docker container to run and start trading.

Desktop (please complete the following information):

• Raspberry pi Buster
• Docker version 20.10.11, build dea9396

Description

Here the description of the issue: https://github.com/whittlem/pycryptobot/issues/203

Fixes # (issue)

Type of change

Please make your selection.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update
• [ ] This change requires a new dependency
• [x] Code Maintainability / comments
• [x] Code Refactoring / future-proofing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added pytest unit tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules
• [x] I have checked my code and corrected any misspellings

This PR adds a Dockerfile and example docker-compose.yaml to allow for easier administration.

In order to enable the build in your repo, you should:

• create a PAT for your account (User > Settings > Developer settings > Personal Access Tokens) with the read and write package rights
• put the token into a secret variable for this repo (Settings > secrets > New secret). Give it the name "PACKAGE_TOKEN" as this is configured in the github action
• Change the visibility of the created "package" (User > Your Profile > Packages > pycryptobot/pycryptobot > Package settings > Change visibility

It is a bit of work, but it makes usability a lot easier :)

I also fixed all markdown-lint violations in the readme file.

You can check the actual container that was built out of this: ghcr.io/lvlie/pycryptobot/pycryptobot:latest

And I think the "action" log should also be visible as well: https://github.com/lvlie/pycryptobot/runs/2307818414?check_suite_focus=true

Describe the bug Errors at launch. It only affects one of my 3 portfolios on startup, as the format doesn't confirm to the specc here: https://github.com/whittlem/pycryptobot/blob/d530ab7d59364acfd4322f47bfc5ee9af35fe289/models/CoinbasePro.py#L192

To Reproduce Steps to reproduce the behavior:

1. launch using python3 pycryptobot.py
2. See error

Error Log

Traceback (most recent call last):
  File "pycryptobot.py", line 66, in <module>
    orders = account.getOrders(app.getMarket(), '', 'done')
  File "/home/pi/pycryptobot/BTC/models/TradingAccount.py", line 110, in getOrders
    self.orders = model.getOrders(market, action, status)
  File "/home/pi/pycryptobot/BTC/models/CoinbasePro.py", line 195, in getOrders
    df = resp.copy()[[ 'created_at', 'product_id', 'side', 'type', 'filled_size', 'specified_funds', 'executed_value', 'fill_fees', 'status' ]]
  File "/home/pi/.local/lib/python3.7/site-packages/pandas/core/frame.py", line 3030, in __getitem__
    indexer = self.loc._get_listlike_indexer(key, axis=1, raise_missing=True)[1]
  File "/home/pi/.local/lib/python3.7/site-packages/pandas/core/indexing.py", line 1265, in _get_listlike_indexer
    self._validate_read_indexer(keyarr, indexer, axis, raise_missing=raise_missing)
  File "/home/pi/.local/lib/python3.7/site-packages/pandas/core/indexing.py", line 1315, in _validate_read_indexer
    raise KeyError(f"{not_found} not in index")
KeyError: "['specified_funds'] not in index"

I've gone in to actually check the columns of resp, and it only contains the following:

['id', 'price', 'size', 'product_id', 'profile_id', 'side', 'type', 'time_in_force', 'post_only', 'created_at', 'done_at', 'done_reason', 'fill_fees', 'filled_size', 'executed_value', 'status', 'settled']

Desktop (please complete the following information):

• OS: Linux; Debian
• Version: latest git pull as of 2.0.6

Additional context Config file, aside from base_currency identical to working ones. :

{
     "coinbasepro" : {
         "api_url" : "https://api.pro.coinbase.com",
         "api_key" : "...",
         "api_secret" : "...",
         "api_passphrase" : "...",
         "config" : {
             "base_currency" : "BTC",
             "quote_currency" : "USD",
             "live" : 1,
             "sellatloss" : 0,
             "granularity": 60
         }
     },
     "telegram" : {
         "token" : "...",
         "client_id" : "..."
     }
}

Hello

i got an error message when attempting to buy Algo on binance this morning :

2021-04-25 08:00:00 | ALGOUSDT 1h | Close: 1.15 | BUY

ALGO balance before order: 0.0 USDT balance before order: 199.98 Order quantity after rounding and fees: 172.84 25-04-2021 10:47:14 Binance marketBuy APIError(code=-2010): Account has insufficient balance for requested action. ALGO balance after order: 0.0 USDT balance after order: 199.98

as you can see, i had ~200 usdt in my acount thanks

An exception which causes the program to quit.

On Raspberry Pi running bot from a Terminal screen. All dependencies were updated to the latest versions available and supported on the Raspberry Pi.

Logger screen:

/home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py:583: ValueWarning: A date index has been provided, but it has no associated frequency information and so will be ignored when e.g. forecasting. ' ignored when e.g. forecasting.', ValueWarning) /home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py:583: ValueWarning: A date index has been provided, but it has no associated frequency information and so will be ignored when e.g. forecasting. ' ignored when e.g. forecasting.', ValueWarning) /home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py:583: ValueWarning: A date index has been provided, but it has no associated frequency information and so will be ignored when e.g. forecasting. ' ignored when e.g. forecasting.', ValueWarning) /home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py:583: ValueWarning: A date index has been provided, but it has no associated frequency information and so will be ignored when e.g. forecasting. ' ignored when e.g. forecasting.', ValueWarning)

Restarting application after exception: KeyError('The end argument could not be matched to a location related to the index of the data.')

2021-06-15 05:00:00 | ETC-GBP | 3600 | Close: 41.9720 | ^ EMA12/26: 41.7507 > 41.4208 ^ | ^ MACD: 0.3298 > 0.3164 ^ | WAIT | Last Action: BUY | -26.1610% (delta: -14.305) /home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py:583: ValueWarning: A date index has been provided, but it has no associated frequency information and so will be ignored when e.g. forecasting. ' ignored when e.g. forecasting.', ValueWarning) /home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py:583: ValueWarning: A date index has been provided, but it has no associated frequency information and so will be ignored when e.g. forecasting. ' ignored when e.g. forecasting.', ValueWarning) ^[c/home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py:583: ValueWarning: A date index has been provided, but it has no associated frequency information and so will be ignored when e.g. forecasting. ' ignored when e.g. forecasting.', ValueWarning) /home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py:583: ValueWarning: A date index has been provided, but it has no associated frequency information and so will be ignored when e.g. forecasting. ' ignored when e.g. forecasting.', ValueWarning) KeyError('The end argument could not be matched to a location related to the index of the data.') Traceback (most recent call last): File "pandas/_libs/hashtable_class_helper.pxi", line 1039, in pandas._libs.hashtable.Int64HashTable.get_item KeyError: 1623744000000000000

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "pandas/_libs/index.pyx", line 446, in pandas._libs.index.DatetimeEngine.get_loc KeyError: Timestamp('2021-06-15 08:00:00')

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

Traceback (most recent call last): File "/home/pi/.local/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 2897, in get_loc raise KeyError(key) from err KeyError: Timestamp('2021-06-15 08:00:00')

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

Traceback (most recent call last): File "/home/pi/.local/lib/python3.7/site-packages/pandas/core/indexes/datetimes.py", line 627, in get_loc raise KeyError(orig_key) from err KeyError: '2021-06-15 08:00:00'

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py", line 170, in get_index_loc raise KeyError(str(e)) KeyError: 'only integers, slices (:), ellipsis (...), numpy.newaxis (None) and integer or boolean arrays are valid indices'

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "/home/pi/.local/lib/python3.7/site-packages/statsmodels/tsa/base/tsa_model.py", line 333, in get_prediction_index raise KeyError('The end argument could not be matched to a' KeyError: 'The end argument could not be matched to a location related to the index of the data.'

This error occurs while executing the code about after 20mins

2021-07-12 13:43:05 | BTC-EUR (BEAR) | 3600 | Current Price: 28200.93 Exception('GET (401) https://api.pro.coinbase.com/orders?status=done - request timestamp expired') Exception: GET (401) https://api.pro.coinbase.com/orders?status=done - request timestamp expired

Describe the bug Attempt to run bot and get an error message that there are no funds when I do have $100 available.

To Reproduce Steps to reproduce the behavior:

1. Run the bot command
2. get the error message

Expected behavior I was hoping that the bot would begin to run.

Screenshots See below

Desktop (please complete the following information): Raspberry Pi 4 Current code for bot from here Python 3

I'm running into a similar issue:

After I ran the "...--lastaction SELL" I got this error message:

I think this is related to other issues but I'm not sure how or what to do to fix this.
I'm attempting to start a bot for the first time using Coinbase Pro for DOT.

https://www.coinbase.com/advanced-trade

https://help.coinbase.com/en/coinbase/trading-and-funding/advanced-trade/what-is-advanced-trade

since transferring from coinbase to coinbasepro (deposits, etc....) are restricted to coinbase only. will the api setup have to change? like url, and im pretty sure ill need to generate a new api key pair.

Simulation Error at Test Buy

Hi,

I was wondering if anyone has run into this issue when running the simulation. I have not been able to pinpoint what it is in my config that would be causing the problem. I will attach that below as well.

Issue only seems to trigger when there is a test buy order executed.

William

{ "coinbasepro": { "api_url": "https://api.pro.coinbase.com", "config": { "base_currency": "ALGO", "quote_currency": "USD", "live": 0, "smartswitch": 1, "verbose": 1, "statdetail": 1, "sim": "fast" }, "api_key_file": "coinbase.key" } }

Originally posted by @wmespi in https://github.com/whittlem/pycryptobot/discussions/722

I am a newby to python - can you please explain how to resolve the issue below please.

c:\Crypto\Experiment\pycryptobot-main -Bitcoin\pycryptobot-main>python pycryptobot.py --live 1 Traceback (most recent call last): File "C:\Users\Administrator\AppData\Local\Programs\Python\Python39\lib\site-packages\pandas\core\indexes\base.py", line 5845, in _raise_if_missing raise KeyError(f"{not_found} not in index") KeyError: "['created_at', 'market', 'action', 'type', 'size', 'filled', 'fees', 'price', 'status'] not in index"

c:\Crypto\Experiment\pycryptobot-main -Bitcoin\pycryptobot-main>

After upgrading from v6.0.0 to 6.3.0 I noticed that I can't run the telegram bot anymore. I could solve the issue by checking out to the beta branch. Nevertheless I am reporting the issue which others may also encounter.

# python3.9 telegram_bot.py
2022-05-04 18:05:34,498 - telegram.helper - INFO - Telegram Bot is listening
Traceback (most recent call last):
  File "/home/h1/telegram_bot.py", line 922, in <module>
    main()
  File "/home/h1/telegram_bot.py", line 907, in main
    botconfig.setcommands(None, None)
  File "/home/h1/telegram_bot.py", line 260, in setcommands
    self.helper.send_telegram_message(
  File "/home/h1/models/telegram/helper.py", line 235, in send_telegram_message
    context.bot.send_message(
AttributeError: 'Updater' object has no attribute 'send_message'
^CException ignored in: <module 'threading' from '/usr/lib/python3.9/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.9/threading.py", line 1470, in _shutdown
    lock.acquire()

System info: NAME="Ubuntu" VERSION="20.04.4 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian

Describe the bug I'm trying to understand why it's not returning the balance correctly. 2022-04-30 22:00:56 WARNING Insufficient Funds! (BTC=0.0, USD=0.0)

To Reproduce Config file: { "coinbasepro": { "api_url": "https://api.pro.coinbase.com", "config": { "base_currency": "BTC", "quote_currency": "USD", "live": 1, "sellatloss": 1, "sellatresistance": 0, "trailingstoploss": -1.5, "trailingstoplosstrigger": 5, "nosellmaxpcnt": 3, "nosellminpcnt": -3, "disablebullonly": 0, "disablebuynearhigh": 1, "disablebuymacd": 0, "disablebuyobv": 1, "disablebuyelderray": 0, "disablefailsafefibonaccilow": 1, "disableprofitbankreversal": 0, "disabletracker": 1, "disabletelegram": 1, "autorestart": 0, "graphs": 1, "verbose": 1, "stats": 0, "enableinsufficientfundslogging": 1, "enabletelegrambotcontrol": 1, "websocket": 0, "disablelog": 0, "buypercent": 99, "sellpercent": 99, "buyminsize": 0, "sellsmartswitch": 0, "trailingbuypcnt": 0.5, "telegramtradesonly": 0, "granularity": "3600", "enableml": 0, "recvwindow": 20000 } }, "logger" : { "filelog": 1, "logfile": "pycryptobot.log", "fileloglevel": "DEBUG", "consolelog": 1, "consoleloglevel": "DEBUG" } }

Any insight into what I can do to set it straight? I've tried --recvWindow 20000 and I've tried to make sure system time is synced. Those were the only fixes I could find from googling around. I also tried the beta branch to see if any update would help.

Thanks.