14

Waiting to trade… Safety switch is on – What does it mean?

A lot of people don’t understand why their Gunbot shows a message “Waiting to trade… Safety switch is on” from time to time.

First of all, it’s not an error. Then what does it mean? Ok, let’s start talking about TRADES_TIMEOUT parameter. After Gunbot buys a coin, the exchange takes some time to update the trading history. Here is where TRADES_TIMEOUT comes into scene, we need to wait some time to avoid some problems:

1- Avoid to buy multiple times if the bot doesn’t detect a previous purchase.

2- Avoid the bot to “think” the last bought price is an old purchase.

So, TRADES_TIMEOUT is a protection and it sets the number of seconds the bot will wait until it will be able to buy a coin after a purchase.

In conclusion, “Waiting to trade…Safety Switch is on…” is not an error, it just states that the bot is waiting the amount of seconds stated in TRADES_TIMEOUT parameter to avoid a problem. Obviously if you set TRADES_TIMEOUT to 0, you won’t see that message again, but it’s not recommended. The recommended values are 300 for Bittrex and 100 for Poloniex.

14 Comments

Avatar

david.pons.acc 7 January, 2018

Which is the recommended value for binance?

Thanks and regards,
David

Reply

    Avatar

    Aitor 8 January, 2018

    60 is Ok for Binance.

    Reply

Avatar

rus.bes13 7 January, 2018

Please advice TRADES_TIMEOUT for binance and cryptopia

Reply

    Avatar

    Aitor 8 January, 2018

    You can set TRADES_TIMEOUT to 60 on both exchanges.

    Reply

Avatar

adsfb 7 January, 2018

My bot was off for 4-5 days, today when I turned it on; I started to receive Safety Switch is on message. I have tried with a bunch of different coins for at least 30 minutes, below is an example. I have even set trades_timeout =0 but it still fails to buy.
Below is a sample message; I will be glad if you can asssit me.
Regards,
Devrim

GBXT_v7.0.2 BTC-POWR Round # 67
[90m————————————————————————————————[39m
[33mɢ[39m[32mƱ[39m[34mŋ[39m[35mɃ[39m[31m۝[39m[33mŁ[39m[90m XT Edition Scanning bittrex for trading opportunities [39m2018/01/08 00:34:25
[90m————————————————————————————————[39m
[90m2018/01/08 00:34:25[39m[33m: BTC-POWR Last Bid/Ask 0.00010768/0.00010887[39m
[90m————————————————————————————————[39m
EMA1: 0.0001092784767431785 === EMA2: 0.00010900244179461497
[90m————————————————————————————————[39m
[90m————————————————————————————————[39m
HIGH BB: 0.00011425 == SMA: 0.00011034 == LOW BB: 0.00010642
[90m————————————————————————————————[39m
[90m————————————————————————————————[39m
BTC/USD Money Flow Index is: 38.243998887096495
[90m————————————————————————————————[39m
[90m2018/01/08 00:34:25[39m[33m: Got Trading History[39m
[90m2018/01/08 00:34:25[39m[36m: Checking Open Orders[39m
Last trade P/L for BTC-POWR was: -6.946 %
[90m2018/01/08 00:34:25[39m[33m: Price to buy: 0.00010889343756000001[39m
[90m2018/01/08 00:34:25[39m[33m: Last Bid/Strategy Exit Point: 0.00010768/0.00006178942839776298[39m
[90m2018/01/08 00:34:25[39m[36m: Last Ask/Strategy Entry Point: 0.00010887/0.00010889343756000001[39m
[90m2018/01/08 00:34:25[39m: XTrend for BTC-POWR: [42m UP!!! [49m
[90m┌───────────────────[39m[90m┬────────────────[39m[90m┬────────────[39m[90m┬─────────────[39m[90m┬────────────[39m[90m┬─────────────┐[39m
[90m│[39m[31m [31mɢ[31m[33mƱ[31m[32mͶ[31m[34m฿[31m[35m๏[31m[31mŦ[31m[90m XT Edition[31m [39m[90m│[39m[31m [90mStop limit hit[31m [39m[90m│[39m[31m [90mCan we buy[31m [39m[90m│[39m[31m [90mCan we sell[31m [39m[90m│[39m[31m [90mPanic sell[31m [39m[90m│[39m[31m [90mCan average[31m [39m[90m│[39m
[90m├───────────────────[39m[90m┼────────────────[39m[90m┼────────────[39m[90m┼─────────────[39m[90m┼────────────[39m[90m┼─────────────┤[39m
[90m│[39m Core checks [90m│[39m [41m NO [49m [90m│[39m [42m YES [49m [90m│[39m [41m NO [49m [90m│[39m [41m NO [49m [90m│[39m [41m NO [49m [90m│[39m
[90m└───────────────────[39m[90m┴────────────────[39m[90m┴────────────[39m[90m┴─────────────[39m[90m┴────────────[39m[90m┴─────────────┘[39m
[90m2018/01/08 00:34:25[39m: Last Bid price BTC-POWR: [42m0.00010768[49m | Last Ask: [41m0.00010887[49m
[90m2018/01/08 00:34:25[39m: Balance BTC: [33m0.14282745[39m
[90m2018/01/08 00:34:25[39m: Balance POWR: [33m0[39m
[90m2018/01/08 00:34:25[39m: On Orders POWR: [33m0[39m
[36mProcessing strategy bbstepgain for BTC-POWR on bittrex[39m
BUY CYCLE
[90m2018/01/08 00:34:25[39m[36m: Entering buy cycle[39m
[1m[31m************************************************************************************************[39m[22m
Waiting to trade…Safety Switch is on…

Reply

    Avatar

    Aitor 8 January, 2018

    As you can read in the article above, “safety switch” is some kind of protection. It’s activated after a buy is made or after the bot has just started. So it’s something normal.

    Reply

Avatar

benana 17 January, 2018

Timout Buy by Bittrex is 300, and the Timeout Sell the same? (300)

Reply

    Avatar

    Aitor 18 January, 2018

    This article talks about TRADES_TIMEOUT parameter. For Bittrex 300 is ok. You can even lower it to 200.

    Reply

Avatar

Sander 21 January, 2018

The help text in the Strategies page for TRADES_TIMEOUT states ‘Timeout in MINUTES after (re)start or last trade’

Reply

Avatar

Jonny boy 23 January, 2018

set all TRADES_TIMEOUT to 0 made no difference tried 100, 200 same keep getting the message “wiating to trade.. safty switch on” . Thats at least 20 mins after starting it and with no previous buys or stock in the particluar pairs I am trying.

The TRADES_TIMEOUT makes no difference to the Wating to trade Safety Swtich is on error… Currenlty round 45 with it set on TRADES_TIMEOUT on 100 Bittrex. 7.0.2

Reply

    Avatar

    Jonny boy 23 January, 2018

    PLease see screen shot https://ibb.co/fc4TZG

    Reply

      Avatar

      jonny boy 23 January, 2018

      Thats with TRADES_TIMEOUT set to 60

      Reply

        Avatar

        Aitor 24 January, 2018

        TRADES_TIMEOUT protection acts just after starting the bot or after a buy is made, so it doesn’t matter if it’s round #3928, it can appear if they bot recently purchased that coin. Also be sure you set BOT_CCLEAN to 1 to get rid of chahing problems.

        Reply

    Avatar

    Aitor 24 January, 2018

    If you set TRADES_TIMEOUT to 0, you shoudln’t see that message. Are you sure you are saving the config.js file correctly? Note that if you edit config.js manually and then run the bot through the GUI, the changes you made would be overwritten.

    Reply

Submit Your Comment