Bot Controller: The bot does not turn back on after being turned off

After discussing it with Ares and not finding a completely logical solution, I’m bringing the problem to the developers behind the code to see what solution they might have.

Using the Bot Controller and ASAP in Combo Hedge:
°Start:
Condition: Supertrend downtrend 1h → Opens a short position.

°Stop (in monitoring mode to listen for new start signals):
Condition: RSI(15) lower than 30 → Stops the bot.

Problem: The bot started making trades in ASAP with only the ST downtrend bot controller configured, and then I added the Stop signal (RSI). It then successfully deactivated when the RSI was below 30. The problem is that when the price returns to the RSI level (above 30), the bot cannot be reactivated in any way. When it should be, since ‘Start: ST Downtrend=True’ and ‘Stop: RSI<30=False’

ID: https://app.gainium.io/bot/6915429f4f18d834c5ae36b6?a=1848&aid=share-bot&share=84d2efa8-040f-4f02-8548-2fb26d33f54f

***********************************************************

Test with a paper account:

Then, to see if the condition made sense for starting the bot, I used the same bot controller configuration on a simple DCA bot on a paper account, starting from scratch, and the bot started without problems, with the price in a similar condition. However, the bot hasn’t touched its stop-zone, so I don’t know if it will have the same problem as the hedge bot..

***********************************************************

Observation: I don’t know if what I’m saying is a bit silly, but I see that the bot appears to be running from here.

image

Could it be that it can’t be reactivated simply because, since the Long side is already running, the bot thinks it doesn’t need to turn on the Short side since the bot itself sees it as running?

We have received your bug report regarding the Bot Controller not reactivating after being turned off, and we will update you shortly. Thank you for providing the bot URL: Gainium app. We are investigating the issue with the bot’s reactivation logic, especially concerning the Combo Hedge and the potential conflict with the Long side already running. Your detailed explanation and testing on a paper account are very helpful.

Your start condition is to start when 1h Supertrend will be donwtrend. If you want to start when downtrend and/or rsi > 30, so you should add one to the start condition.

In bot events I can see it successfully triggered start bot and start deal, but was not enough balance.


The same problem in SOL paper bot. It started but has not enough balance to start the deal.

Also you mentioned in the task about hedge combo, but you sending links to one side DCA. However bots that belongs to hedge are completely separate so long and short status of bots shouldn’t affect each other.

Excuse me, I sent you the wrong link. That’s what happens when I don’t check them first.

The link I mistakenly sent you was for the paper account, and yes, I knew there was no balance in that account, but the main reason was to find out if the same configuration I use in the hedge allows me to turn it on without logical errors.

I’ve updated the thread with the Hedge bot link.

“Your start condition is to start when 1h Supertrend will be donwtrend. If you want to start when downtrend and/or rsi > 30, so you should add one to the start condition.”

In fact, it’s configured that way, an indicator for the start.

And before, for further confirmation, I had added an RSI greater than 30 to the start conditions, but it still didn’t start.

Start:
Supertrend 1hr downtrend
RSI(15)>30

Stop:
RSI(15)<30

________________________________________________________________

EDIT:

@maksym.shamko

New approach: In an attempt to see if it worked, I manually deactivated the bot, meaning the green status light turned gray. Then the activation signal took effect, and then it turned off again when the RSI < 30 signal touched that zone.

This is what I was saying about the general bot appearing as on (green light), and it was indicating that it didn’t need to be activated by the signal. If this turns out to be the problem, the long bot will turn on, the controller will interpret it as activated, and the short bot won’t work independently, turning itself on and off as desired.

I’ll have to keep looking into it. I look forward to your perspective on the matter.

After you added RSI > 30 to start condition I can see that short leg is working as you expected it to be. In turned into monitoring mode when RSI < 30 and in open mode when RSI > 30 and supertrend downtrend.

The hedge bot will still be green. Hedge bot is an abstraction over regular bots. it doesn’t have monitroing state, it just manage child bots. However short and long bots themselves has monitoring state in which they are turned on when conditions are met.

I can see many settings changes including stop state, start condition etc. From latest change (yesterday around 17 utc) bot successfully started and stopped using RSI (because supertreand is downtrend for a couple of days)

I cannot reproduce on my side the not start problem. Let me know it the problem persists. I will mark as not a bug since cannot reproduce it.

Thanks @maksym.shamko.
I see the bot is automating itself according to my needs, and I’m testing it with new conditions, but from what I can see, it’s working well.

What I do want to see now in the stop zone is which condition takes precedence over the other. I’m wondering if a Start indicator like the 1hr downtrend I use, which sends constant signals to trigger every hour, will work against a Stop indicator like the 15m RSI, which triggers every 15 minutes if the signal is True.

I assume they both work with an AND condition. Even if the Start condition is True and the Stop condition is False, it shouldn’t work.

Although I would like to see a reference indicator, like the one you usually see when viewing the bot list, with a green, gray, or red light indicating which side (Long or Short) of the bot is on or off. While it shows that the bot is in a trade, there’s no way to see which side of the bot is active or offline, waiting to start another trade.

Is there a way to see this, or has it not been implemented yet?

Dear @maksym.shamko: It used to shut down properly, but lately (November 16) it doesn’t seem to be doing that anymore. The Telegram bot doesn’t notify me when it turns on, but at least it does notify me every time it shuts down.

It’s worth noting that I haven’t changed any settings in the last few days.

Bot doesn’t started itself, because you have stop condition - close bot. You changed to minitoring only today.
Regarding start message will be fixed later this week. Messages not sending yet.