I would like to be able to turn on a combo bot using an indicator as a trigger (super Trend for example) and have the bot work with an ASAP configuration. Once there is an exit signal (stop or shut down Bot) let the bot that received the signal stop opening ASAP trades but, hold the last grid until it reaches takeprofit or stoploss.
There’s the bot controller that currently already offers webhooks.
Hi Gainium guys.
I’d like to revive this feature request to have Technical Indicators available as settings for the Take Profit and/or Stop Loss of the Combo bots, similar to that which is possible through the DCA bots. I know that this can be achieved through the Bot Controller and the ASAP Deal Start condition as explained by @d_yo_r but this is clunky and I’ve seen many instances (at least in backtests) where new deals were initiated when bot controller settings would not allow it. It makes me think that the ASAP + Bot Controller combination is not all that reliable.
I love the strategy of @John_Carballar to use combo bots with a bit of leverage, but in doing so it becomes critical to be able to define stop-loss criteria based on indicators. By having it as part of the core bot settings instead of relying on the Bot Controller, it will free up the bot controller to govern the overall on/off state our bot based on market conditions (which is what I believe it was designed for).
So please add technical indicators to the Take Profit and Stop Loss settings for Combo bots. Thanks.
This feature was already implemented. If you encounter an issue you can make a new bug report. There is no difference by having the indicators as part of the bot controller or part of the tp/sl section, the bot controller is part of the bot, not separated from it.
Hi @aressanch Thank you for the reply.
I understand in theory there should be no difference between the ASAP + Bot Controller method vs. a tp/sl defined by technical indicators - However, when I run backtests using the deal start setting vs. the exact same settings in the bot controller, I do end up with significantly different results. Also, with live implementation /forward testing, I note that with the Bot Controller, the deal is only started at the close of the candle/bar (probably when the conditions can be tested) whereas when using the deal start conditions the deal can open immediately if the conditions are met. So I am wondering if this timing issue is not causing the different outcomes when backtesting over a long term. I have not forward tested (just an observation at the moment).
If I’m not mistaken, the same logic should always be used to open deals.