Bot controller fails to start

Bug Reports
1

Bug info:It looks like the bot can’t start according to the price conditions that have been set

2

You should press start. Bot will be in monitoring state and will be listening for the price update, until conditions are met.

3

Will that waiting bot block one of the open places for the total amount of active bots?

4

Yes, sure.

6

Sorry I guess the bot controller is used so that the bot can start and activate at a certain price automatically. If we want a deal start on the price condition, isn’t there a static price filter?

Bot start and deal start are two different things #CMIIW

1 Like
7

Let me explain the logic.

  1. You set up a start condition: whether its a price or indicators.
  2. You press start. It wont actually start the bot. It will set bot to monitoring state. Bot will only listen for start conditions to trigger.
  3. When conditions are met, bot will be in open state and will start to trade.

So you can set up following: ASAP bot with price to start the bot greater than 1.05 USDT. Bot will listen for price update, and when price will greater than 1.05, bot will actually start and place ASAP deal.

We did this to be able to actually stop the bot and not listen for incoming event. Otherwise it wont be possible to stop it, without changing settings.

8

I understand.
This means after the bot stops according to the specified price (bot controller), we cannot restart the bot automatically until we press the start button again. What if we have hundreds or thousands of bots? Isn’t it less efficient sir?

9

No, you cannot restart bot automatically.

10

Let’s put aside the deal start condition.
In my opinion, stop bot is working fine, but to start/restart the bot automatically using the bot controller feature is still not possible.
Is there any solution for the bot to start automatically every time it reaches a certain price?

11

Start bot condition will automatically start the bot. Restart automatically after the bot have been stopped is not possible using bot controller. Only using webhook

1 Like
12

Then I am afraid that the bot controller doesn’t do what the fearure request asked for. A bot should be started and stopped according to the conditions and not be considered to be active if the bot is not started. And if I remember right stopping a bot also stops all deals as well. Therefore we have to be extra careful.

1 Like
13

The issue is that a monitoring bot is using resources, hence it needs to be counted towards the quota. Else a bad actor could open thousands of bot monitoring the price or indicators and use all resources for free.

The solution is to add a new stop bot action. Instead of closing the bot, return to monitoring status. That way it should be able to start and stop itself multiple times. Though it will always count as an active bots.

@maksym.shamko can we do this?

Edit: I spoke to maksym, this is the right way to accomplish what you want. It will be added tomorrow.

2 Likes
14

I fully agree that even checking a single signal for the bot has an impact. Probably it’s a little less than that of a single and multi-pair bot with only a single active deal at most, but it will take computing time. Is the implementation event-driven?

15

By the way, I still don’t understand this feature and still don’t understand what additional benefit it shall give us. My question still wasn’t fully answered:

16

Are the additional bot actions referred to “monitoring and close/leave/cancel deal”?

I think this could be a solution so the bot controller can start and stop automatically.

Thank You :pray::pray:

17

Still curious about the status of monitoring​:pray::pray:.
If a bot in monitoring status then the bot will not listen for incoming events until the bot status has changed to restart. is it right sir?

18

Active: operational and opening deals
Closed: not operational and not opening new deals, but there is an option to leave current deals running. Not listening for webhooks or monitoring indicators.
Monitoring: not operational and not opening new deals, but there is an option to leave current deals running. Listening for webhooks and monitors indicators.

1 Like
19

So when a bot is closed, its open deals will no longer be maintained by the bot, i.e. at most the limit orders of the deal that are already on the exchange will be executed, but no new orders will be added? In that case at least the new monitoring state is an improvement as it allows us to prevent a bot from opening new deals without risking to lose control over existing deals and without changing e.g. the start condition in the configuration. Is that monitoring state accessible by a switch in the bot overview as well?

20

When you stopping the bot you have options to: leave deals, cancel deals, close by limit/market. If you stoped the bot by leave, bot will maintain active deals until they are closed, but do not open new one.
The difference between monitoring and closed is that bot in closed state wont listen for start events, but in monitiring it will. In monitoring mode you can also start deal manually, which is no allowed in stopped bot with active deals. Any active deal in bot with stop or monitoring state will work as per normal ( trailing, indicators or whatever the setup is, will work until deal is closed)

1 Like
21

I see. So only a hard downgrade of the subscription will inevitably cancel open deals when it closes bots?