Signals & Overlays™ Alert Conditions

Signals & Overlays™ indicator has various alert conditions based on each signal mode included in the indicator. Once you are comfortable with our signal terminology you should be able to understand what each of these alerts does, these are described below:

AlertDescription
Any alert() function callTriggers when a user set condition is triggered (see section below)
Any ConfirmationTriggers when any confirmation signal (bullish/bearish normal/+) is displayed
Any Bullish ConfirmationTriggers when any bullish confirmation signal (normal/+) is displayed
Any Bearish ConfirmationTriggers when any bearish confirmation signal (normal/+) is displayed
Any Confirmation+Triggers when any confirmation + signal (bullish/bearish) is displayed
Any ContrarianTriggers when any contrarian signal (normal/+ bullish/bearish) is displayed
Any Bullish ContrarianTriggers when any bullish contrarian signal (normal/+) is displayed
Any Bearish ContrarianTriggers when any bearish contrarian signal (normal/+) is displayed
Custom AlertTriggers when a user set custom alert is triggered
Bullish ConfirmationTriggers when a normal bullish confirmation signal is displayed
Bearish ConfirmationTriggers when a normal bearish confirmation signal is displayed
Bullish Contrarian+Triggers when a bullish confirmation+ signal is displayed
Bearish Contrarian+Triggers when a bearish confirmation+ signal is displayed
Bullish ExitTriggers when a bullish exit signal is displayed
Bearish ExitTriggers when a bearish exit signal is displayed
Trend Catcher DownTriggers once the trend catcher starts decreasing (switch from green to red)
Trend Catcher UpTriggers once the trend catcher starts rising (switch from red to green)
Trend Tracer DownTriggers once the trend tracer starts decreasing (switch from green to red)
Trend Tracer UpTriggers once the trend tracer starts rising (switch from red to green)

Using Placeholders With Confirmation/Contrarian Alerts

When creating an alert using ‘Any Confirmation’ or ‘Any Contrarian’ it is possible to use placeholders so that the alert message returns the type of signal that triggered the alert.

In order to do so, paste the following line in the message field:

Bullish : {{plot("Bullish")}} | Bearish : {{plot("Bearish")}} | Bullish+: {{plot("Bullish+")}} | Bearish+ : {{plot("Bearish+")}}

Any Alert() Function Call

The any alert() function call alert condition allows to create one alert using various conditions, this allows to bypass the limit of one alert for free users as well as making the process of updating many alerts faster and easier.

To create such an alert go to the indicator settings, and scroll down to the ’ANY ALERT() FUNCTION CALL CONDITIONS’ section.

Toggle on the conditions of interest. Now create a new alert, in the first Condition drop-down menu select the LuxAlgo Premium indicator, in the second drop-down menu select Any alert() function call, you can then create the alert.

This alert would use once per bar close by default.

All-in-one alerts do not differ from regular alerts, they will be using the same indicator settings as the one used during their creation. Note however that you cannot set a custom message for all-in-one alerts, the message displayed when the selected conditions trigger will be the same as the one used in the same individual alert conditions.

Any Alert() Function Call Message

Users can set a custom message that will be used when an “any alert() function call” condition is triggered in the message field below the list of conditions. Users can use placeholders to customize messages and return useful information, the following placeholders are supported:

Symbol Placeholders

PlaceholderDescriptionExample
{default}Default message associated with the triggered condition"Bullish Confirmation Signal"
{ticker}Symbol ticker without the exchange prefix"MSFT"
{exchange}Symbol exchange/data source"COINBASE"
{sector}Sector of the symbol, na if the symbol has no sector"Technology Services"
{market}Symbol market type"Stocks"

Time Placeholders

PlaceholderDescriptionExample
{tf}Chart timeframe, includes “S” for seconds, “D” for days, “W” for weeks, “M” for months"15"
{time}Unix time in milliseconds in exchange timezone"1705331385158"
{year}Current year in exchange timezone"2024"
{month}Current month in exchange timezone"7"
{day}Current day of the month in exchange timezone"21"

Data Placeholders

PlaceholderDescriptionExample
{open}Opening price"1.2145"
{high}High price"1.2357"
{low}Low price"1.1983"
{close}Closing price"1.0569"
{volume}Current volume"45216"

Format as JSON

Use the following message template to receive “any alert() function call” messages in the JSON format:

{
  "alert": "{default}",
  "ticker": "{ticker}",
  "tf": "{tf}",
  "ohlcv":{
    "open": {open},
    "high": {high},
    "low": {low},
    "close": {close},
    "volume": {volume}
  },
  "bartime": {time}
}

Updating Alerts Using Any Alert() Function Call

If you already set an any alert() function call alert and want to change the indicator settings or want to toggle on another condition all you need to do is edit the alert you want to update, select the second instance of the indicator in the first Condition drop-down menu and then click on save.

Custom Alert Creator

Users wishing to construct more complex alerts using features within the toolkit and/or external indicators can use the Custom Alert Creator.

The custom alert creator allows alerting when various user-set conditions are met or when a sequence of conditions is complete.

A user wishing to be alerted when any bullish signal occurs while the smart trail is bullish could do it as follows:

A custom alert can be triggered as an any alert() function call if the setting is selected or as a regular alert when selected in the Tradingview alert creator menu.

Steps

Steps allow creating a sequence of conditions, which when met trigger an alert. When a condition with a step equal to 1 is met the next condition associated with step 2 will be evaluated (if enabled) and so on for higher steps (if any).

Conditions with the same associated step will require both conditions to be true in order for the condition associated with a higher step (if any) to be evaluated. This allows certain conditions to act as filters.

A user wishing to be alerted for any bullish confirmation signal classified as 1 or 2 by the AI classifier occurring after the smart trail turned bullish could do it as follows:

Make sure the AI Classifier is enabled.

Make sure steps are set such that they form a linear sequence. For example, if the lowest step is 2 or if the set steps are only 1 and 3 an error will be returned.

OR Step Operator

The “OR” step operator can be used to get alerted for any additional condition using “OR” as step, in addition to other set custom alert conditions.

Conditions using the “OR” step can be highlighted using a different color, which can be set from the Custom Alert Creator settings.

OR Step Operator

The “OR” step operator can be used to get alerted for any additional condition using “OR” as step, in addition to other set custom alert conditions.

Conditions using the “OR” step can be highlighted using a different color, which can be set from the Custom Alert Creator settings.

All Step Operator

The “All” step operator can be used to filter any set “Step” condition, including “OR” and “Invalidate”.

This step operator can be useful if all the steps in a sequence needs to obey a specific rule.

If a user has 2 steps set, and requires both of these to occur at a specific time interval such as 9am to 1pm, then we can use a “Session” condition using the “All” step, requiring our step 1 and step 2 to be occur between 9am and 1pm.

Invalidate Step

The “Invalidate” step allows to set a condition as an “invalidation condition”. When this condition is triggered while a sequence of conditions is incomplete, the sequence will restart at step 1.

If multiple steps are set as “Invalidate” any of the conditions being true will reset the sequence of conditions, as such not all of them are required to be true for the sequence of conditions to reset.

Example

Let’s take an example where we use 2 regular steps and one “Invalidate” step. The alert will trigger when step 2 trigger after step 1 has been triggered.

1

Step 1

Step 1 condition trigger, we will now evaluate step 2 from now on.

2

Invalidation Step

Invalidation step condition trigger, we reset the sequence and evaluate step 1 just after.

Invalidation Behaviors

Invalidation behaviors allows adding more restrictions to a sequence of conditions, users can use two different invalidation behaviors described below:

Invalidate On Step 1

The “Invalidate On Step 1” behavior allows to reset an incomplete sequence of conditions when the condition on step 1 trigger. This prevents the first step condition from happening in between other steps of the condition sequence.

This behavior is useful when the first step of our sequence of conditions needs to never be repeated during the sequence.

Example

Let’s take an example where we use 3 regular steps.

1

Step 1

Step 1 condition trigger, we will now evaluate step 2 from now on.

2

Step 2

Step 2 condition trigger, we will now evaluate step 3 from now on.

3

Step 1 Trigger

Step 1 condition trigger, we start evaluating step 2 from now.

Invalidate On Any Repeated Step

The “Invalidate On Any Repeated Step” behavior allows to reset an incomplete sequence of conditions when a step is triggered such that it does not respect the set order of conditions.

This behavior is useful when we want a perfectly ordered sequence of conditions to complete, without any step repeating itself.

Example

Let’s take an example where we use 3 regular steps.

1

Step 1

Step 1 condition trigger, we will now evaluate step 2 from now on.

2

Step 2

Step 2 condition trigger, we will now evaluate step 3 from now on.

3

Step 1 or 2 Trigger

Step 1 or 2 conditions trigger, we start evaluating step 1 from now.

Maximum Step Interval

Users can determine what is the maximum allowed horizontal distance (in bars) between two steps by enabling the “Maximum Step Interval” setting. This allows restricting steps separated by a large amount of bars.

If the amount of bars since a step exceed the set threshold, then the conditions sequence is reset, and we start evaluating from step 1 again.

Highlight Custom Alert Triggers

When a custom alert condition is set, a visual element is displayed at the bottom of the chart in order to more easily visualize when the custom alert conditions occurs (displayed by default).