propose new bots in condor: multigrid strike, arbitrage,dman,xemm

[pierluigipanariello]

Good morning, I wanted to share some improvements I've made to Condor.
I've added the following bots:
Arbitrage_controller
dman_v3
multi_grid_strike
xemm_multiple_levels

All of which relate to the relevant controllers in hummingbot-api.
I've also attached some images.

[pierluigipanariello]

controller_handlers.py
the controller_handler.py attached is a new version that solve problem in (xemm,arb,dman,mgs) when insert total amount by keyboard

[cardosofede]

thanks for the contribution! @rapcmia let's test it

[rapcmia]

Commit ee2a11c

• Build local docker image and start using make deploy ❌
  
• Got same error on source when using make run ❌

  (base) eddga :: hummingbot/condor/46 ‹main*› » make run
  uv run python main.py
  Traceback (most recent call last):
    File "/home/eddga/hummingbot/condor/46/main.py", line 574, in <module>
      main()
      ~~~~^^
    File "/home/eddga/hummingbot/condor/46/main.py", line 561, in main
      register_handlers(application)
      ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
    File "/home/eddga/hummingbot/condor/46/main.py", line 227, in register_handlers
      from handlers.bots import (
      ...<4 lines>...
      )
    File "/home/eddga/hummingbot/condor/46/handlers/bots/__init__.py", line 24, in <module>
      from .archived import (
      ...<6 lines>...
      )
    File "/home/eddga/hummingbot/condor/46/handlers/bots/archived.py", line 25, in <module>
      from ._shared import get_bots_client, get_cached, set_cached
    File "/home/eddga/hummingbot/condor/46/handlers/bots/_shared.py", line 30, in <module>
      from .controllers import SUPPORTED_CONTROLLERS, get_controller
    File "/home/eddga/hummingbot/condor/46/handlers/bots/controllers/__init__.py", line 15, in <module>
      from .arbitrage_controller import ArbitrageControllerController
    File "/home/eddga/hummingbot/condor/46/handlers/bots/controllers/arbitrage_controller/__init__.py", line 8, in <module>
      from .config import DEFAULTS, EDITABLE_FIELDS, FIELD_ORDER, FIELDS, generate_id, validate_config
  ModuleNotFoundError: No module named 'handlers.bots.controllers.arbitrage_controller.config'
  make: *** [Makefile:41: run] Error 1
  

[pierluigipanariello]

Updates Made

I've fixed the reported issues (added arbitrage_controller/config.py) and added new controllers. Here are the details:

Newly Added Controllers:

• ✅ anti_folla_v1 - Contrarian strategy (VWAP, Donchian, OBV divergence, OBI, Volume Spike)
• ✅ macd_bb_v1 - MACD + Bollinger Bands for directional trading
• ✅ supertrend_v1 - SuperTrend indicator with confirmation

Fixes Applied:

• ✅ Fixed trailing_stop inconsistency between DEFAULTS and FIELDS
• ✅ Added cross-period validation (BB length >= MACD slow)
• ✅ Fixed perpetual candles (using spot connector for candles)
• ✅ Fixed MarkdownV2 error "can't find end of code entity"
• ✅ Added caption truncation for photos (max 950 characters)
• ✅ Added try/except for back navigation from photos (like DMan V3)

Tests Performed:

• ✅ Full wizard flows for all controllers
• ✅ Charts generated correctly (spot and perpetual)
• ✅ Back navigation working
• ✅ Automatic analysis with strategy suggestions

PR Updated:

• PR propose new bots in condor: multigrid strike, arbitrage,dman,xemm #46 has been updated with the new controllers
• All local tests passed

Let me know if there are any other issues to resolve. Thanks!

[rapcmia]

Commit 38f535b

• Build local docker image successfully and start condor make deploy ✅
• Found some syntax warning related to invalid escape sequences ❌
  
  • despite having these warnings, condor seem to start ok

Build local docker image and start using make deploy ❌

• This is fixed ✅
• /new bots window display all controller configs
  

---

Test in progress

• Multi GS, PMM v1, Arbitrage, XEMM multi levels

[rapcmia]

Test generic.multi_grid_strike

• These buttons does not do anything ❗
  
• When editing the controller config, the parameters does not match or missing the other grid ❌
  
• Successfully deployed and archived bot ✅

---

Test directional_trading.dman_v3 ✅

• Created and deployed controller config successfully
• Successfully update controller config

---

Test generic.arbitrage

• Setup with gateway connector
• On arbitrage setup, after adding the CEX trading pair (okx) it does not prompt for the DEX trading pair ❌
  
  • This resulted to jupiter/router getting the same market pair
  • rate_connector automatically set to the CEX connector selected, on my case id like to always make it default binance
• Updating controller-config
  
  • Successfully updated controller config ✅
  • Successfully deployed and archived bot ✅

[pierluigipanariello]

correct error (select pair in cex and in dex ), removed fake button ,solved minor error

[pierluigipanariello]

update 4 removed unused yml parameter and tested yml file

[pierluigipanariello]

"Hi @rapcmia @cardosofede, I've fixed the issues reported (arbitrage DEX pair and multi_grid_strike buttons) in the updates from last week and yesterday. Could you please re-run the tests when you have time? Thanks!"

[cardosofede]

hey @pierluigipanariello I'm glad to see how much are you working with condor!!! let me review wiht the team and see how to test. seems like you are adding a charts in the controllers folder... is that to display the chart in telegram?

[pierluigipanariello]

hey @pierluigipanariello I'm glad to see how much are you working with condor!!! let me review wiht the team and see how to test. seems like you are adding a charts in the controllers folder... is that to display the chart in telegram?

Sorry for the delay in responding, Fede. Yes, I implemented the graphs for Telegram. I wanted to implement other controllers in hummingbot-api to run strategies like macdbb, etc. I know you're in Sardinia, and I hope you're having a good holiday. The AI ​​management you're implementing is interesting, but I think it's useful to offer solutions for those who, for various reasons, don't want or can't use the AI. For example, I tested Deepseek and noticed that it often resets, meaning it has no memory of what I wrote a moment before, so I was forced to use other tokens for the same question. Ultimately, the strategies are the basic ones, so it makes sense to consult the AI ​​only for advice on market evolution, including based on geopolitical situations. It can now be said that the crypto market is aligning itself with the same dynamics that govern stock exchanges around the world. for this reason I think it is necessary to have generic bots that cover all the cases and limit the demand to AI to simple questions, which consume few tokens and related to market performance, trends, speculative orientation and various news even on standard markets that can influence the crypto world, and then ask which of the available bots to use and what parameters to use