A new update has been applied to the alert system in BBMA Dashboard Hunter.
What has been improved:
- Fixed duplicate alerts being triggered when switching chart timeframes.
- On timeframe changes, the dashboard now correctly preserves the current signal state instead of treating already active setups as new alerts.
- Removed a misleading Telegram WebRequest message that appeared during timeframe changes even when no real error was present.
- The Telegram WebRequest message is now only shown when there is an actual sending issue.
Result:
No more unnecessary alert retriggering when switching between M5, H1, D1, and other timeframes.
Cleaner reinitialization behavior when the dashboard reloads.
Less noisy and more accurate log output.
The chart tooltip also shows the alert trigger type. This tells you how the alert was fired, for example on a state change, after a cooldown period, or once per anchor bar. It makes it easier to understand not only which setup triggered, but also under which alert logic it was generated
BBMA Dashboard Hunter can now save alert overlay history and restore it after restarting MetaTrader or reloading the Expert Advisor.
How it works:
Every triggered alert can be stored in a history file inside the MT5 Files folder.
After restart, the dashboard reloads that history and redraws the alert lines with their hover text on the chart.
The hover text shows the alert time, setup name, and trigger type.
Relevant settings:
- Enable Alert Chart Overlay: draws alert lines and hover text on the chart
- Persist Alert History: saves and restores alert overlay history
- Alert History File: defines the base name of the history file
- Max Stored Alert Events: limits how many past alerts are kept
Notes:
The history file is created per symbol, so each chart symbol keeps its own alert history.
Removing the Expert Advisor clears the visible lines from the chart, but the saved history remains available for the next load if persistence is enabled.
Indicator BBMA Oma Ally OmniView v1.30 (2026-06-01)
Updated First Reentry logic:
First Reentry signals are now filtered more strictly. A First Reentry source is only valid if a matching signal of the same type has appeared since the last reentry a
nd no opposite signal of that same type has occurred in between. This applies to Momentum, CSAK, and CSAK2 on both buy and sell sides.
The goal is to avoid mixed or conflicting setups and show cleaner, more consistent First Reentry signals.
Update note:
Before installing the update, I recommend deleting the old .ex5 files first. MetaTrader sometimes keeps using cached or previously loaded .ex5 files instead of the newly copied ones, even after they have been overwritten. Removing the old files beforehand helps ensure that the platform loads the latest version correctly.
--
