Edge Scanner v1.2.1

Range break fires on every real breakout again, saved range-break thresholds are kept exactly, quote-built volume stops double counting, and fresh installs get tested library versions.

Not financial advice. The sample setups are starting points, not a strategy.

Range break: fires again after price comes back inside

After a breakout, a quiet bar back inside the range should re-arm the trigger for the next breakout. It did not: the volume check ran first, so the quiet bar was ignored and the trigger stayed spent. In practice a range break setup gave at most one alert per direction per day.

• A return inside the range now re-arms it, however quiet the bar. Each real breakout alerts once.
• A quiet drift outside the range followed by a high-volume bar while still outside still fires, as before.
• Expect more range break alerts than on v1.2.0 and earlier.

Saved range break thresholds are no longer clipped

v1.1.6 converted saved setups from the old candle multiple to the new per-minute multiple and promised the same alerts. That held for most setups, but the result was capped at 30x, and a re-save capped it again. A setup saved as 10x on 60-minute candles needs 600x a minute and loaded as 30x, so it fired on far less volume than intended. Anything on 15-minute or longer candles, or above 6x on 5-minute candles, was affected.

• The limit is now 600x and the conversion is exact. A setup already re-saved at the capped value keeps that value; set it back by hand if needed (old multiple times the candle minutes).

Schwab quote-built bars

• Volume counted once. When Schwab's running day volume dipped slightly (a correction or a stale snapshot) and came back, the climb back was counted again, repeatedly if it flapped. Volume now counts only above the highest total seen.
• Small universes keep polling. With fewer than 300 symbols, if Schwab reported a lower real-bar limit, the overflow was moved to polling but nothing polled it. The poller now always runs when quote-built bars are on.

Startup: a taken port is reported at once

If an old scanner is still running, the new one used to warm up for several minutes and then stop with a traceback. It now checks the port first and says which program holds it and how to stop it.

Dependencies

A fresh install had no upper limits and pulled pandas 3, Starlette 1.7 and websockets 17 untested. The full test suite now passes on both the oldest and the newest supported versions, and each library is capped below its next major release. Minimums rose where that picks up a security fix: pyarrow 14.0.1, FastAPI 0.120.1, yfinance 1.2.2.

Also

• Setup validation errors say what is wrong ("unknown trigger ...") instead of always "a numeric field has an invalid value".

Update

git pull, then pip install -r requirements.txt, then npm --prefix dashboard-v2 run build, then restart the scanner. Or download the zip below.