Live SPOT trading bot doesn’t sell despite meeting the conditions

General
1

There are two entry conditions (a+b):

  • price below the 1-hour SMA - met
  • SMA3 4-hour < SMA20 4-hour - met
    The conditions were likely met when the bot was launched, and they are definitely met now. Therefore, the bot should have sold HTR, but it didn’t.
    Does it have to wait one or four hours after launch if it uses such MAs?
2

Both the condition on the 4h candle and the 1h candle have to be confirmed on candle close. Theoretically it should also be possible to check whether the conditions where met for the 1h candle before starting the bot, but I don’t know whether this has been implemented.

3

OK, thanks.

So, if I want a faster response, should I use SMA12 1h instead of SMA3 4h? Or SMA48 15m? Of course, I understand the possible differences in data.

4

Wrote from old account, sorry.

5

Let’s see what information Gainium can provide. I’m just a user. If the bot doesn’t check the conditions at the start, this could be a new topic for the Feature Requests channel. Once the bot has been running for at least the length of the longest time-frame candle, everything should work as expected. Otherwise, this would be something for Bug Reports.

6

Correct, the conditions are only evaluated at candle close. As @d_yo_r pointed out, if the conditions were met in a closed candle already it would be a bug report, if the candle wasnt closed yet it would be a feature requests. We already had a request to evaluate indicators on open candles, but doing so would significantly increase the number of operations and therefore the credit cost of the bot. If there is enough interest we will definetely look into it.

7

I think the question wasn’t about interbar evaluation here but to also check the conditions on the according candle close before the bot was started.

Like this

4h candles |           |
1h candles |  |  |  |  |

Let’s use * to mark when conditions were met on candle close and ? when it doesn’t matter.
Let’s use ° when the bot was started and # when it could be allowed to start its first deal.

Currently this would happen:

4h:  ?           *
1h:  ?  ?  ?  ?  *
bot:  °           #

But how about implementing something like this instead:

4h:  *           ?
1h:  *  ?  ?  ?  ?
bot:  °#      

4h:  *           ?
1h:  |  *  ?  ?  ?
bot:  °  #      

4h:  *           ?
1h:  |  |  *  ?  ?
bot:  °     #      

4h:  *           ?
1h:  |  |  |  *  ?
bot:  °        #

So the boot could start immediately when the condition was met.

8

I’m not sure if I understand correctly, so I’ll put it in my own words.
In my opinion: If the conditions for launching the bot, e.g., MA 1h>4h are met at the moment the bot is launched, it should work immediately -
without waiting for the conditions to be met AFTER launching the bot
It’s not a matter of life and death for me, but IMHO it’s logical.
Otherwise, setting, for example, weekly SMA drastically delays the moment of its launch.
EOT for me :slight_smile:

1 Like