Skip to content

Date range

ConditionsFrom Pro

    Date range

    Oct 28, 2026, 4:00 PM UTC – Oct 29, 2026, 8:00 PM UTC

    • in range
    • Days since From
    This is how the node looks on the board. It has no inputs; on the right its values go to other nodes.

    True between two points in time. Is true while a candle closes between “From” and “Until”. If a field stays empty, the range is open on that side: only “From” means “from then on”, only “Until” means “until then”. With AND a chain passes alerts on only during this time, with NOT in front it mutes them during this time, for example around a rate decision. “Days since From” counts the whole days since “From”. Example: from Oct 28, 6 PM until Oct 29, 10 PM, NOT in front and then AND with your signal: no alerts in the hours around the event. For recurring events such as CPI or the Fed rate decision there is the Event node.

    Date range from Monday noon until Wednesday 8 AMEach dot is a candle close; the closes from Monday 12 noon until Wednesday 7 AM are inside the range.MondayTuesdayWednesday12 AM6 AM12 PM6 PM12 AM6 AM12 PM6 PM12 AM6 AM12 PM6 PM12 AM
    • candle close inside: true
    • before and after: false
    Three days of 1-hour candles. With “From Monday 12:00” and “Until Wednesday 8:00” the date range is true for the candles that close in that time, “From” included, “Until” no longer. With NOT in front it mutes alerts during that time, with AND it only lets them through then.

    The settings appear on the right under “Properties” once you click the node on the board. Below each field you find the same explanation as here.

    Default: empty · point in time, shown in your time zone in the editor, stored in UTC

    From this point in time the output is true, in your time zone. Empty: always has been.

    Default: empty · point in time, shown in your time zone in the editor, stored in UTC

    From this point in time the output is false again, in your time zone. Empty: no end.

    Blackout around an event: RSI below 30 notifies you by push, but not from Oct 28 at 4 PM until Oct 29 at 8 PM (UTC), for example around a rate decision.

    Example chain: Candle, RSI, Compare, Date range, NOT, AND, PushConnections: Candle → RSI, RSI → Compare, Date range → NOT, Compare → AND, NOT → AND, AND → Push.CandleBTC/USDT · 1hRSI14 candlesCompareRSI 14 below 30Date rangeOct 28, 2026, 4:00 PM UTC –Oct 29, 2026, 8:00 PM UTCNOTinverts the signalANDall inputs truePushat most every 4 h

    How to connect the nodes:

    1. Candle (Price) → RSI (Value)
    2. RSI (RSI) → Compare (Value)
    3. Date range (in range) → NOT (Signal)
    4. Compare (true/false) → AND (Signal 1)
    5. NOT (inverted) → AND (Signal 2)
    6. AND (all true) → Push (Trigger)

    On the board it reads: Oct 28, 2026, 4:00 PM UTC – Oct 29, 2026, 8:00 PM UTC

    Chain as JSON

    To try it, copy it and paste it in the editor under “Import”. Importing creates a new chain.

    date-range.json
    {
    "name": "Example: Date range",
    "version": 1,
    "nodes": [
    { "id": "c1", "type": "core.candle", "position": { "x": 40, "y": 40 }, "settings": { "pair": "BTC/USDT", "timeframe": "1h" } },
    { "id": "r1", "type": "core.rsi", "position": { "x": 260, "y": 40 }, "settings": { "length": 14 } },
    { "id": "k1", "type": "core.compare", "position": { "x": 480, "y": 40 }, "settings": { "operator": "below", "value": 30 } },
    { "id": "w1", "type": "core.date-range", "position": { "x": 40, "y": 170 }, "settings": { "from": "2026-10-28T16:00:00Z", "to": "2026-10-29T20:00:00Z" } },
    { "id": "x1", "type": "core.not", "position": { "x": 260, "y": 170 }, "settings": {} },
    { "id": "a1", "type": "core.and", "position": { "x": 700, "y": 40 }, "settings": {} },
    { "id": "p1", "type": "core.push", "position": { "x": 920, "y": 40 }, "settings": {} }
    ],
    "edges": [
    { "from": "c1.close", "to": "r1.in" },
    { "from": "r1.out", "to": "k1.in" },
    { "from": "w1.out", "to": "x1.in" },
    { "from": "k1.out", "to": "a1.in0" },
    { "from": "x1.out", "to": "a1.in1" },
    { "from": "a1.out", "to": "p1.in" }
    ]
    }

    Only matching types connect: number series to number series (round pin), signal to signal (square), message to message (diamond).

    Direction Pin Type Note
    Input – – No inputs: the data comes straight from the source.
    Output in range Signal (true/false) –
    Output Days since From Number series –
    • In messages the value is called “Days since From”.
    • Search also finds it under: date, date range, event, from until, expiry, blackout, news filter, rate decision, days since.

    What counts is the time a candle closes. “From” is included, “Until” is not. The times are stored in UTC in the chain; the editor shows them in your time zone. If “Until” lies before “From”, the range is empty. Days since From = ⌊(candle close − From) / 24 h⌋, empty before “From”.

    • Type in the chain: core.date-range · Version 1.0.0 · Category key cond
    • Settings in the chain: from (From), to (Until)
    • Pins in the chain: Output out, days
    • Reference tests in the manifest: 3 (with fixed price data: 500 candles of 1h)
    • How a node is built

    Version 2026.10.24.21 · Changelog