🌸 SPRING SALE 🌸 Get 35% OFF with code: SPRINGSALE – Valid until April 22, 2025
Precision Trading Insights with Smart Institutional Order Flow
🌸 SPRING SALE 🌸 Get 35% OFF with code: SPRINGSALE – Valid until April 22, 2025
Precision Trading Insights with Smart Institutional Order Flow
Below are configurable alert features you can enable to keep track of specific cluster conditions
Note: This feature is still under development and is currently not working reliably
Triggers an alert if the cumulative timeframes (in seconds) within a cluster exceed a user-defined threshold.
For example, if you set the threshold to 5400 (which is 90 minutes in seconds), the alert fires whenever a cluster includes lines that collectively add up to 90 minutes or more (e.g., 60 + 30, or three Ă— 30 minutes).
Helps you detect “stronger” clusters where multiple lines indicate significant timeframes in the same area.
Instead of manually checking each timeframe combination, the alert notifies you automatically.
Threshold (Seconds): The numeric input representing how many total seconds must be reached or exceeded to trigger the alert.
Enable Alert: A boolean switch (checkbox) to turn this feature on or off.
Performance settings: If you want to narrow down the search for clusters, it makes sense to adjust the performance level so that not too many candles are analyzed for clusters. Therefore, it’s definitely reasonable to search for clusters using the “Low” performance setting.
Notifies you when the current price comes within a certain distance (in the chart’s currency) of any cluster’s top or bottom boundary.
For example, if you enter 1000, the alert triggers if the price moves within ±1000 units of the cluster’s upper or lower bound.
Monitors whether price is “close enough” to a potential support/resistance cluster without requiring you to watch every tick.
Particularly helpful if you want an early warning as price approaches key levels.
Distance: The “advance warning distance” in the chart’s currency. A setting of 0 triggers only when the price exactly touches the boundary; larger values create a buffer zone above/below the cluster.
BTC at 100,000 USD with Distance = 1000:
Alert fires if price rises to 99,000 from below, or falls to 101,000 from above.
This ensures you’ll know when price enters a 1,000 USD range around your cluster zones.
The alert functionality of the IOF Pro indicator is currently in Beta. This means that while the alerts are technically working, their practical usefulness is still limited — and that’s exactly why I’ve chosen not to label them as final features yet.
Below is an honest overview of the current limitations of each alert type:
This alert triggers whenever a High Order Block (HOB) is detected.
Issue: HOBs occur frequently, but many of them are short-lived or not very significant. As a result, this alert often leads to excessive notifications, most of which are not actionable.
In practice, older and more established HOBs are much more meaningful and can usually be spotted easily by visually scanning the chart.
This alert triggers when the current price gets close to any detected cluster.
Issue: Since multiple clusters may exist at once, and there is no prioritization of importance, this alert can become noisy and unfocused.
In many cases, it’s more effective to simply set a manual price alert in TradingView near a key level you plan to monitor.
This alert highlights areas with several overlapping breaker blocks.
Issue: The lack of deeper filtering or context makes the alert too broad to be truly helpful.
Most traders will find it easier to spot these zones visually rather than relying on the alert system in its current form.
All three alerts currently operate without contextual filtering. While they do technically identify valid structures, they do so without assessing their real-world significance or confluence with other market factors. For this reason, I’ve clearly labeled them as Beta features, to manage expectations and remain transparent.
There are several ideas on the roadmap for improving alerts in the future, including:
Combining multiple factors (confluences) to improve accuracy
Scoring or ranking clusters based on historical price reactions
Context-aware triggers that reference macro levels, such as Bitcoin structure, before signaling on altcoins
Realistically, implementing these improvements will likely require tools outside of Pine Script — such as a Python-based engine or external signal processor.
If you have any ideas, feature requests, or practical use cases you’d like to share, I’d love to hear from you!
© 2025 LumoSpectra
Made with Expertise, All Rights Reserved.