• Welcome back! Thank you for being a part of this Traders Community. Let's discuss and share :)
    Selamat datang kembali! Trimakasih telah menjadi bagian dari Komunitas Trader ini. Mari berdiskusi dan berbagi :)

New EA DeepGold LLM EA – when gold listens to artificial intelligence (well, almost)

hi
this error not exist in the previous version. perhaps backup to this one !
Hi! I understand the desire to roll back to a time when "everything worked and didn't buzz," but it's like a favorite bar that's closed for renovation, and the "deepseek-chat" sign is no longer lit. DeepSeek has officially retired the old model, so version 1.4 from message #54 will now knock on a closed door and receive an HTTP 400, which is no better than 1003, just another sad number.

We've moved to the new model because the old entrance has been closed. It will be easier to use deepseek-v4-flash now — it's really less picky. I can't say how soon, but I'll finish the version where you can choose between deepseek-v4-pro and deepseek-v4-flash.

So the rollback is a ticket to the depot, not to profit.
 
It seems that we have not an isolated case here, but a direct flash mob "HTTP 1003"! The DeepSeek server apparently decided that Doomsday had come and turned on the "fortress siege" mode for everyone at once.

It happens when DeepSeek has a global glitch, or they massively shake up access rules, and half of the users become "suspicious" simply for breathing.

What to do while they fix their neurons there:

• Don't change keys like crazy — it won't help, you'll only hit the limits. One key for everything.

• Check the SpikeCooldownSec in the settings — if it is too small (like 5 seconds), the server thinks that you are attacking it. Hold at least 300 (5 minutes) — let the neural network digest the previous query.

• Try a VPN or IP change — sometimes Cloudflare bans a specific range of addresses, not you personally. Moving to another country can virtually solve the problem.

• Look at the DeepSeek status (if they have a status page) - perhaps they are honestly writing there: "We've fallen, wait."

Well, remember: if the neural network does not respond, it does not mean that it does not love you. It's just that it's "Monday" for her. We are waiting for DeepSeek to stop acting up. Patience and green candles for everyone!
So based on this , the EA just active on NY Session ?
And i think the problem all of the EA Out there is about spread and the regime market.
 
Hi! I understand the desire to roll back to a time when "everything worked and didn't buzz," but it's like a favorite bar that's closed for renovation, and the "deepseek-chat" sign is no longer lit. DeepSeek has officially retired the old model, so version 1.4 from message #54 will now knock on a closed door and receive an HTTP 400, which is no better than 1003, just another sad number.

We've moved to the new model because the old entrance has been closed. It will be easier to use deepseek-v4-flash now — it's really less picky. I can't say how soon, but I'll finish the version where you can choose between deepseek-v4-pro and deepseek-v4-flash.

So the rollback is a ticket to the depot, not to profit.
Can we not use Phyton to do so, instead of relying on Deepseek engine?
settings/analysis in Py, trade taken surely use MT5
 
Can we not use Phyton to do so, instead of relying on Deepseek engine?
settings/analysis in Py, trade taken surely use MT5
You're absolutely right — Python is like a Swiss army knife with a laser sight for analysis and neural networks: flexible, powerful, a library wagon. But I deliberately went through the "all in one" on MQL5, and here's why:

1. The principle of "one button"

The ADVISOR should work according to the "downloaded —launched — forgotten" principle. One .ex5 file, no pythons, virtual environments, dependencies, or dancing with a tambourine. I opened the terminal, attached it to the chart, and the gold went. This is critical for beginners.

2. Combat reliability

When you have Python + MT5 + bridge between them, there are three points of failure. The Python script crashed, communication with the terminal was lost, the signal file was not read — hello, missed input. And the MQL5 Expert Advisor runs right in the terminal, without external dependencies. Spreads, ticks, and execution are all nearby.

3. Reaction speed

There is a delay through an external file: Python calculated → wrote → Adviser read → executed. While the file is going back and forth, the trend has already gone by 50 points. Within a single process, the signal goes directly to onTick() without intermediaries.

4. The Unix way is not yet for everyone

Splitting into components is cool for geeks and custom solutions. But 90% of the forum's users want a finished product, not a "build it yourself" constructor. Therefore, the first version is as simple and self—sufficient as possible.
 
For XAUUSD robots, I usually check whether the strategy depends on trend strength, spread widening, and session timing. A backtest alone can look good, but forward testing should confirm whether entries survive real broker execution, especially during news and low-liquidity hours. What conditions are you using to decide when the robot should stop trading?
 
For XAUUSD robots, I usually check whether the strategy depends on trend strength, spread widening, and session timing. A backtest alone can look good, but forward testing should confirm whether entries survive real broker execution, especially during news and low-liquidity hours. What conditions are you using to decide when the robot should stop trading?
Dear samshoshoEA, I think I am beginning to suspect that you are a very persistent AI bot that is testing my convergence response.

No kidding, but your question (for the third time in a thread) was discussed in detail in message No. 16 — it's right on the shelves. So we scroll a little higher, find post No. 16, and voila — the truth is there!

And if you are still a human being, I apologize for the false accusation of being a bot, it's just that the exact repetition is very suspiciously accurate.
 
Back
Top