• 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)

DeepSeek, like a real star, decided to rebrand itself — and our good old deepseek-chat model went on a well-deserved vacation, and it was replaced by deepseek-v4-pro and deepseek-v4-flash.

The adviser, not understanding the humor, tried to reach the old model and received an HTTP 400 response like "guy, where are you calling, there is no such model anymore."

What has changed:

Changed the model name in the code from deepseek-chat to deepseek-v4-pro.

Now the AI is back in touch, smarter than before and ready to predict gold movements, rather than drawing errors in logs.

If you have an older version, just download the updated version. Now the advisor is back online, and DeepSeek has stopped pretending to be unavailable. Profit for everyone and no 400 mistakes!
 

Attachments

NPNavigator said:
Hello, colleagues!

Now our "golden" AI advisor has stopped being stubborn as a sheep and has learned to obey his master.

What was added:

• Two new fields in the settings: LLM_BuyThreshold and LLM_SellThreshold

(search in the "AI Settings (DeepSeek)" group).

Previously, the thresholds were tightly sewn in:

prediction >= 0.65 → BUY, prediction <= 0.35 → SELL.

Now you decide for yourself with what confidence the AI should open a deal.

If you want, tighten the nuts to 0.8 and 0.2 in order to trade only "reinforced concrete" signals.

If you want, loosen to 0.6 and 0.4 and catch more movements (but with popcorn, because it can be stormy).

Now, instead of "the robot thinks you're a sucker and ignores your wishes," we have a "henpecked robot" - turn the sensitivity knob and watch as it obediently runs to open positions.

Try it, experiment, and share the results. Version 1.4 is already in the topic header. Profit for everyone!
Click to expand...
hello
i am facing "HTTP 400" error, removed EA from the chart and added again, but still same issue. please give me solution
 
For gold robots, I usually separate the signal logic from the execution assumptions. The same idea can look solid in a backtest, but I would want to compare it across spread regimes, then check out-of-sample behavior and forward-test drift. Session timing matters too, especially when liquidity thins out or the broker widens spread around news. If the result changes a lot when those inputs move, the edge is probably too fragile.
 
Otabek said:
hello
i am facing "HTTP 400" error, removed EA from the chart and added again, but still same issue. please give me solution
Click to expand...
The HTTP 400 error is not a glitch, it's DeepSeek that has granted an "amnesty" to old models and retired deepseek—chat. The counselor knocks on her door out of habit, and she says, "There's no such model anymore, come back tomorrow."

The full detailed analysis of this problem lies in message No. 62 — there I tell you what to replace the model with so that everything starts up again.

So scroll a little higher, read post No. 62, download the updated version — and let the gold work for us again, not on the log screen!
 
samshoshoEA said:
For gold robots, I usually separate the signal logic from the execution assumptions. The same idea can look solid in a backtest, but I would want to compare it across spread regimes, then check out-of-sample behavior and forward-test drift. Session timing matters too, especially when liquidity thins out or the broker widens spread around news. If the result changes a lot when those inputs move, the edge is probably too fragile.
Click to expand...
I am also in favor of having the logic of signals and execution live in different "apartments" — this makes it easier to understand who is messing up: the predictor neural network or the crooked hands of a broker with an extended spread on the news.

Everything looks beautiful on the backtest — the graph goes into space, no martingales are needed. But once you turn on a realistic spread, add slippage, and remove the Asian session with its ghost spikes— the Grail turns into a pumpkin.

The Expert Advisor already has a session filter and a spread check — this is the first echelon of defense against market brutality.

Comparing the behavior on different configurations is like a test drive of a car in ice and rain: if it drifts on a wet road, it means that the suspension is not very good, and the advantage is really fragile.

In short, the idea is sound — dig deeper, test harder.
 
NPNavigator said:
The HTTP 400 error is not a glitch, it's DeepSeek that has granted an "amnesty" to old models and retired deepseek—chat. The counselor knocks on her door out of habit, and she says, "There's no such model anymore, come back tomorrow."

The full detailed analysis of this problem lies in message No. 62 — there I tell you what to replace the model with so that everything starts up again.

So scroll a little higher, read post No. 62, download the updated version — and let the gold work for us again, not on the log screen!
Click to expand...
in new version of 1.5 i faced a new error: HTTP 1003, what doest that mean ?
 
Otabek said:
in new version of 1.5 i faced a new error: HTTP 1003, what doest that mean ?
Click to expand...
Error 1003 from DeepSeek means: "You're being too persistent, chill out." Literally, your account or IP address is temporarily blocked due to exceeding the request limits or violating the API terms of use. You may have accidentally staged a DDoS attack with your experiments.

What to do:

1. Check the balance and quotas in DeepSeek's personal account. It's possible that you just ran out of free tokens.

2. If you have several Expert Advisors or copies on different charts, they all break into the API at the same time, and DeepSeek turns on the bastion mode.

3. Wait a bit (usually the unit is removed after 15-30 minutes) and try again.
 
NPNavigator said:
Error 1003 from DeepSeek means: "You're being too persistent, chill out." Literally, your account or IP address is temporarily blocked due to exceeding the request limits or violating the API terms of use. You may have accidentally staged a DDoS attack with your experiments.

What to do:

1. Check the balance and quotas in DeepSeek's personal account. It's possible that you just ran out of free tokens.

2. If you have several Expert Advisors or copies on different charts, they all break into the API at the same time, and DeepSeek turns on the bastion mode.

3. Wait a bit (usually the unit is removed after 15-30 minutes) and try again.
Click to expand...
thanks, i was using paid tokens, but i each time i created a new api key and now for 1.5 version i was using the third api key since we started testing DeepGold EA
 
Otabek said:
thanks, i was using paid tokens, but i each time i created a new api key and now for 1.5 version i was using the third api key since we started testing DeepGold EA
Click to expand...
The third API key in a short time? Yes, you are already a VIP customer of DeepSeek! With such an expense of keys, you will soon be given branded mugs and calendars.

But seriously, you may not be burning your keys, but simply losing them due to locks. When the server receives a flurry of requests from one account (even with a new key), it still sees who is knocking, and it can no longer ban the key, but the entire account or IP.

Tip: don't change your keys like gloves, but look into DeepSeek's personal account and check the request limits per minute (RPM) and per day (TPD). Perhaps you are just hitting the ceiling of the paid tariff, and you need to either expand the quota, or pull the neural network a little less often.

By the way, the Expert Advisor has SpikeCooldownSec = 300, which is the pause between requests for spikes. If you reduced it to 5 seconds for the sake of "super-fast signals", the AI server simply turned on the "do not disturb" mode

So: one key, proven limits, a little patience, and DeepSeek will be your best friend again, not a moody star!
 
Hi,
same problem
I change the ea to the new one and today i have error HHTP 1003 on API Statut.
the key used is the same than used with previous version and solde on Deepseek is always positive.
 
NPNavigator said:
DeepSeek, like a real star, decided to rebrand itself — and our good old deepseek-chat model went on a well-deserved vacation, and it was replaced by deepseek-v4-pro and deepseek-v4-flash.

The adviser, not understanding the humor, tried to reach the old model and received an HTTP 400 response like "guy, where are you calling, there is no such model anymore."

What has changed:

Changed the model name in the code from deepseek-chat to deepseek-v4-pro.

Now the AI is back in touch, smarter than before and ready to predict gold movements, rather than drawing errors in logs.

If you have an older version, just download the updated version. Now the advisor is back online, and DeepSeek has stopped pretending to be unavailable. Profit for everyone and no 400 mistakes!
Click to expand...
Hi
I want to ask , is this can run on cent account just for the real test ?
 
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!
 
You must log in or register to reply here.
Back
Top