Back in 2023 I was looking for a divergence indicator on TradingView. I tested around ten of them — none did the job: too many missed or invalid divergences, barely configurable, and above all no hierarchy between signals. Every divergence looked the same regardless of quality. I ended up deciding to code my own.

Three years, several refactors and a few original concepts later, I wanted to share the journey — maybe some ideas will be useful to you, maybe you'll have feedback I haven't thought of.

Read this post to understand :)

1. The detection engine

First release: much more configurable than what existed at the time — min/max divergence length, overtaking tolerance on both price and oscillator, price/osc pivot offset… Already noticeably more accurate. But one thing kept bothering me: divergences only appeared once confirmed, meaning after the pivot. Logical on paper, but in practice you watch a valid divergence form right in front of you and can't do anything until it's validated. So...

2. Anticipated divergences

I added a mode where the engine looks for divergences as they form, before the pivot is confirmed. Displayed as dashed lines that disappear if price invalidates the structure, or solidify into a confirmed divergence if the setup holds. You see the divergence building in real time and you choose: wait for confirmation or pre-position. But all divergences — confirmed or anticipated — were still treated equally. A weak signal and a strong one looked identical. So...

3. Quality score

I added a score (0–100) weighting: divergence amplitude on both oscillator and price, duration, trend context, OB/OS depth, relative volume. The opacity of each diamond reflects its score — at a glance you know what deserves attention and what can wait. But for anticipated divergences, a score alone doesn't tell you whether they'll actually hold. So...

4. Confirmation probability

For each anticipated divergence, the engine computes a confirmation probability (2–98%, never absolute certainty). It accounts for the remaining margin between current values and the pivot level, market volatility, and how many bars are left before the pivot needs to be validated.

In practice the tooltip shows: ⧗3 (2h15) · ★78 · ρ64% — 3 bars remaining, score 78, 64% chance of confirmation. You focus on the high-probability ones and ignore the rest. That worked well — on one oscillator. So...

Anticipated hidden bear

5. Multi-oscillator confluence

The most reliable divergences are the ones you find across multiple oscillators at the same time. So I ported the engine to MACD, MFI, Stoch RSI, WaveTrend, CMF… then hit the next problem: stacking 5 panels is visually unmanageable.

https://preview.redd.it/91z85apjfo3h1.png?width=1014&format=png&auto=webp&s=fb78203b5886a10e182e9e776c0d8fdadea99a36

Inspired by VuManChu WaveTrend, I came up with a condensed layout: one main oscillator (WaveTrend), with diamonds plotted above and below on horizontal lines — each line represents a different oscillator. When multiple lines align on the same bar, the confluence is visible at a glance without switching panels.

Multi-oscillator confluence (zoom)

6. Filtering and alerts

Two independent layers. Visual filtering removes clutter: when divergences share a pivot or cross each other, the weaker one gets dimmed or deleted. Quality filtering hides anything below your score threshold.

For alerts: each oscillator fires its own (filtered by minimum score and probability), but the most useful is the confluence alert — "at least 3 oscillators in bull divergence within a 1-bar window." In practice you stop getting 50 pings a day and get 2–3 a week on setups that actually deserve opening a chart. When it fires, a vertical line appears on the chart — solid if fully confirmed, dotted if part of the confluence is still anticipated.

Wiseall RSI demo

What it doesn't do

• A divergence in isolation is not a trading signal. It's one input among others.
• Anticipated divergences disappear sometimes — that's their purpose.
• On 1m/5m, lots of noise. Designed to work best on 15m and above.

Give me feedbacks

If you want to try it, I've published a free public version — click "Add indicator/strategy" on TradingView and search for "Wiseball", you should find "RSI Super Advanced Divergences". One click to add, no account, no paywall.

If you're curious to see what the Multi-oscillator confluence indicator looks like, ask in comments.

Happy to get feedback — especially critical ones. If you've ever seen a detector miss an obvious divergence, drop the screenshot and I'll run it through mine and share the result.

And if you find it useful, a boost on the TradingView script is always appreciated and helps get it out there 🙂

A few things I'm genuinely curious about:

• When you use a divergence indicator, do you wait for confirmation before acting, or does an anticipated signal change anything for you in practice?
• Has a detector ever missed a divergence that was obvious to you visually? What was the setup — divergence length, oscillator, timeframe?
• The confluence alert (multiple oscillators aligning) — useful concept, or does it just delay the signal long enough that the move is already halfway done?
• On the scoring side: which dimension would you weight more — divergence amplitude, depth in the OB/OS zone, or duration?

Thanks.

Fabien

Back in 2023 I was looking for a divergence indicator on TradingView. I tested around ten of them — none did the job: too many missed or invalid divergences, barely configurable, and above all no hierarchy between signals. Every divergence looked the same regardless of quality. I ended up deciding to code my own.

Three years, several refactors and a few original concepts later, I wanted to share the journey — maybe some ideas will be useful to you, maybe you'll have feedback I haven't thought of.

To understand, scroll :)

1. The detection engine

First release: Wiseball RSI Super Advanced Divergences. Much more configurable than what existed at the time — min/max divergence length, overtaking tolerance on both price and oscillator, price/osc pivot offset… Already noticeably more accurate. But one thing kept bothering me: divergences only appeared once confirmed, meaning after the pivot. Logical on paper, but in practice you watch a valid divergence form right in front of you and can't do anything until it's validated. So...

2. Anticipated divergences

I added a mode where the engine looks for divergences as they form, before the pivot is confirmed. Displayed as dashed lines that disappear if price invalidates the structure, or solidify into a confirmed divergence if the setup holds. You see the divergence building in real time and you choose: wait for confirmation or pre-position. But all divergences — confirmed or anticipated — were still treated equally. A weak signal and a strong one looked identical. So...

3. Quality score

I added a score (0–100) weighting: divergence amplitude on both oscillator and price, duration, trend context, OB/OS depth, relative volume. The opacity of each diamond reflects its score — at a glance you know what deserves attention and what can wait. But for anticipated divergences, a score alone doesn't tell you whether they'll actually hold. So...

4. Confirmation probability

For each anticipated divergence, the engine computes a confirmation probability (2–98%, never absolute certainty). It accounts for the remaining margin between current values and the pivot level, market volatility, and how many bars are left before the pivot needs to be validated.

In practice the tooltip shows: ⧗3 (2h15) · ★78 · ρ64% — 3 bars remaining, score 78, 64% chance of confirmation. You focus on the high-probability ones and ignore the rest. That worked well — on one oscillator. So...

Anticipated hidden bear and tooltip (zoom)

5. Multi-oscillator confluence

The most reliable divergences are the ones you find across multiple oscillators at the same time. So I ported the engine to MACD, MFI, Stoch RSI, WaveTrend, CMF… then hit the next problem: stacking 5 panels is visually unmanageable.

Inspired by VuManChu WaveTrend, I came up with a condensed layout: one main oscillator (WaveTrend), with diamonds plotted above and below on horizontal lines — each line represents a different oscillator. When multiple lines align on the same bar, the confluence is visible at a glance without switching panels.

Multi-oscillator bear confluence (zoom)

6. Filtering and alerts

Two independent layers. Visual filtering removes clutter: when divergences share a pivot or cross each other, the weaker one gets dimmed or deleted. Quality filtering hides anything below your score threshold.

For alerts: each oscillator fires its own (filtered by minimum score and probability), but the most useful is the confluence alert — "at least 3 oscillators in bull divergence within a 1-bar window." In practice you stop getting 50 pings a day and get 2–3 a week on setups that actually deserve opening a chart. When it fires, a vertical line appears on the chart — solid if fully confirmed, dotted if part of the confluence is still anticipated.

Wiseball RSI Divergences

What it doesn't do

• A divergence in isolation is not a trading signal. It's one input among others.
• Anticipated divergences disappear sometimes — that's their purpose.
• On 1m/5m, lots of noise. Designed to work best on 15m and above.

If you want to try it, I've published a free public version on TradingView: "Wiseball RSI Super Advanced Divergences | Essential". One click to add, no account, no paywall.

If you're curious to see what the Multi-oscillator confluence indicator looks like, more info in comments.

Happy to get feedback — especially critical ones. If you've ever seen a detector miss an obvious divergence, drop the screenshot and I'll run it through mine and share the result.

And if you find it useful, a boost on the TradingView script is always appreciated and helps get it out there 🙂

A few things I'm genuinely curious about:

• When you use a divergence indicator, do you wait for confirmation before acting, or does an anticipated signal change anything for you in practice?
• Has a detector ever missed a divergence that was obvious to you visually? What was the setup — divergence length, oscillator, timeframe?
• The confluence alert (multiple oscillators aligning) — useful concept, or does it just delay the signal long enough that the move is already halfway done?
• On the scoring side: which dimension would you weight more — divergence amplitude, depth in the OB/OS zone, or duration?

Thanks.

Fabien